Hi, Marc Weber <[EMAIL PROTECTED]> writes:
> Then put all new files of > /usr/include > into package > libNAme-dev > > and all new files of > /usr/lib > into package > libNAme ? Yes. > So in this case you would create an expression the way it's now > package_lib_and_includes > > Then you would additionally create > package_lib (only copy lib to new destination and hope there are no > references left to the old destination) > package_dev_includes > (only copy includes to new destination and hope there are no > references left to the old destination) Oh, right, so the builder of, say, `package_lib' would be along the lines of "cp $package_lib_and_includes/lib/* $out/lib", right? So `package_lib_and_includes' would need to be an argument of `package_lib'. But then, would that really work? `$package_lib_and_includes/lib/*' may contain self-references to its store path that would need to be changed. Is this done automatically? Also, AIUI, there would be no sharing between `package_lib_and_includes' on one hand and `package_lib' and `package_includes' on the other, since each of them would end up having its own store path, right? If so, that would be an important limitation of this approach. Thanks, Ludovic. _______________________________________________ nix-dev mailing list [email protected] https://mail.cs.uu.nl/mailman/listinfo/nix-dev
