[Nix-dev] Resolve conflicting packages by overloading?

[Joel Moberg]

Luca Bruno <lethalman88 <at> gmail.com> writes:

> 
> On 03/03/2015 00:02, Joel Moberg wrote:
> > If I install a package that provides a resource that already exist in
> > the environment I get a conflict, and from nix-env I get the
> > suggestion to change the priority.
> > Instead of setting priority, is there a way to instead specify which
> > resources in a package that are allowed to be overloaded in the user
> > environment?
> >
> > If this feature does not exist, could it be implemented?
> It could be implemented, it's about what symlink is chosen. Now the
> granularity is on package-level, but I guess it can be on file-level, if
> that's what you meant.
> 

Maybe it's better to keep granularity on package-level, I could just use a 
list of derivations and copy them to $out. I can't think of any case where 
file-level granularity would be better, it would not need copying but it's 
probably much harder to implement.