Difference between revisions of "How to build a development environment from source control"
(Created page with 'This article explains the various ways you can build a development environment for EPrints source contributions. If you have a method not listed here then please add it. Instruct…') |
|||
| Line 1: | Line 1: | ||
This article explains the various ways you can build a development environment for EPrints source contributions. If you have a method not listed here then please add it. Instructions assume familiarity with EPrints and the command line. You can use repositories built in this way to test contributions to EPrints source before pushing them to the git remote. | This article explains the various ways you can build a development environment for EPrints source contributions. If you have a method not listed here then please add it. Instructions assume familiarity with EPrints and the command line. You can use repositories built in this way to test contributions to EPrints source before pushing them to the git remote. | ||
| − | ==Ubuntu== | + | If you find bugs with any of these instructions please update them |
| − | Take a clean ubuntu build | + | |
| + | ==Ubuntu 14.04== | ||
| + | |||
| + | Take a clean ubuntu 14.04 build | ||
<pre> | <pre> | ||
sudo su | sudo su | ||
Revision as of 12:45, 18 November 2015
This article explains the various ways you can build a development environment for EPrints source contributions. If you have a method not listed here then please add it. Instructions assume familiarity with EPrints and the command line. You can use repositories built in this way to test contributions to EPrints source before pushing them to the git remote.
If you find bugs with any of these instructions please update them
Ubuntu 14.04
Take a clean ubuntu 14.04 build
sudo su apt-get install git echo "deb http://deb.eprints.org/ nightly/ deb-src http://deb.eprints.org/ source/" > /etc/apt/sources.list.d/eprints.nightly.list apt-get update apt-get build-dep eprints
