Excerpts from Domen Kožar's message of Mon Apr 07 17:31:58 + 2014:
As soon as we allow more than one design pattern for sharing code between
packages,
package in my use cases means having same name and having most build
instructions be the same.
We do already have sharing for different
As Peti eventually shlevy requested I'm moving this discussion to the
nix-dev list. Not everybody is watching the github repository.
To keep my own maintanance effort low I'd like to spend the time
making the cupsd update patch and the fpm patch acceptable - but I need
help understanding what to
For me versionDerivation looks like a nicer solution, but I generally
tend to be OK with computations written in Nix.
I have been burnt by pythonPackages and even by linuxPackages providing
different subsets of modules for different core versions… so I do not
think versionedDerivation is worse
The main question that raises here is: Where are the limits?
As soon as we allow more than one design pattern for sharing code between
packages, we might have one more approach for code sharing every 6 months
making maintenance of different packages have a bigger learning curve for
no/little
