Switch docs over to suggest using bootstrap with configure and make
This commit is contained in:
parent
15c5b332e7
commit
41dbb27a4f
@ -198,26 +198,10 @@ Clone the MediaGoblin repository and set up the git submodules::
|
||||
git submodule init && git submodule update
|
||||
|
||||
|
||||
And set up the in-package virtualenv::
|
||||
|
||||
(virtualenv --python=python2 --system-site-packages . || virtualenv --python=python2 .) && ./bin/python setup.py develop
|
||||
|
||||
.. note::
|
||||
|
||||
We presently have an **experimental** make-style deployment system. if
|
||||
you'd like to try it, instead of the above command, you can run::
|
||||
Set up the hacking environment::
|
||||
|
||||
./bootstrap.sh && ./configure && make
|
||||
|
||||
This also includes a number of nice features, such as keeping your
|
||||
viratualenv up to date by simply running `make update`.
|
||||
|
||||
Note: this is liable to break. Use this method with caution.
|
||||
|
||||
You then need to make a local copy of mediagoblin.ini, if you don't have one::
|
||||
|
||||
cp --no-clobber mediagoblin.example.ini mediagoblin.ini
|
||||
|
||||
The above provides an in-package install of ``virtualenv``. While this
|
||||
is counter to the conventional ``virtualenv`` configuration, it is
|
||||
more reliable and considerably easier to configure and illustrate. If
|
||||
|
Loading…
x
Reference in New Issue
Block a user