On 2011-12-19 08:06, Marco Leise wrote:
Am 11.12.2011, 23:12 Uhr, schrieb Jacob Carlborg <[email protected]>:
On 2011-12-10 23:32, J Arrizza wrote:
A few other potential twists.
- the installation step needs to be portable int that can install the
variant build artifacts into non-standard file system locations. For
example, the build artifacts for the windows build and the build
artifacts for the linux build need to end up in separate directories and
the Debug and Release builds need to end up in separate
directories. Another example is a Build server building multiple
projects.
- the package system itself needs to be portable in that it can be
installed in any directory. For example, if I want to source control the
entire package system then it would not be in a standard file-system
location. Also it implies there may be multiple installations of the
package system since I can have multiple branches.
For regulated industries that require the ability to recreate the
software environment for any released binary image, both of these would
be a terrific help for doing that.
John
Currently by default the package manager installs everything in (on
Posix) /usr/local/orbit/orbs. It's possible to override this using the
environment variable "ORB_HOME", if this variables is used packages
will be install into $ORB_HOME/orbs.
You have to have super user rights for the default. Maven installs
everything to ~/.maven by default, which will work out of the box.
I have thought of that as well, I've just picked a folder for now. It
can easily be changed in the code.
--
/Jacob Carlborg
