Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: Support for shared packages in external locations #472

Open
PMunkes opened this issue Aug 22, 2017 · 1 comment
Open

Feature Request: Support for shared packages in external locations #472

PMunkes opened this issue Aug 22, 2017 · 1 comment

Comments

@PMunkes
Copy link

PMunkes commented Aug 22, 2017

Using aliBuild in a shared environment would currently require every software developer to provide a full copy of the whole sw/ folder. This means that in our use case it takes up 10GB of disk quota for packages that could be shared. --remote-store already saves the compilation time for these shared packages, but does not remove the disk space requirement.
Doing this would simply require setting symbolic links to the shared $PACKAGE_ROOT directories. If combined with atomic builds and a flag (--prefer shared) to always take non-dev-mode packages from the shared location, if possible, it would provide a safe and stable development environment.

@ktf
Copy link
Member

ktf commented Aug 24, 2017

Yes agreed. Supporting environment from modules as we do support brew on mac is one of the things which we would like to add, however it's a bit tricky because we need a sort of database of all the hashes for the packages in sw, so that we can do the matching with the local hashes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants