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

Support system-level profiles #981

Closed
technomancy opened this issue Feb 4, 2013 · 4 comments
Closed

Support system-level profiles #981

technomancy opened this issue Feb 4, 2013 · 4 comments
Assignees
Milestone

Comments

@technomancy
Copy link
Owner

This would be useful for systems like Debian that want to offer a system-wide repository mirror.

@djpowell
Copy link
Contributor

I see that these profiles are merged in with plain merge. So if you put {:user { whatever }} in /etc/leiningen/profiles.clj, then all of whatever is nuked by the existence of a :user profile in ~/.lein/profiles.clj, without warning.

Is that intended?

@hypirion
Copy link
Collaborator

@djpowell Yes, that is the intent. The priority is default profiles, system profiles, user profiles, project profiles and then finally project map profiles (the later, the better).

@djpowell
Copy link
Contributor

So, for the use-case described in the original issue; if you define a system-wide :repositories mirror for :user at system level, then the mere existence of :user at the user profile, will deactivate that mirror, even if there is no :repositories key at user level?

Given that user-level :user will almost always exist, this doesn't seem to help with the original use-case?

@technomancy
Copy link
Owner Author

Yeah, so this was requested by the guy doing Debian packaging, but I think it's not really useful unless we add another activated-by-default profile. Maybe :system.

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

No branches or pull requests

3 participants