[Nix-dev] warning if trying to install a package but it fails an assert.

[Michael Raskin]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

	Maybe we should reverse the situation?
	Obviously, we should try to avoid building just what we need each time
and always ending up with a bunch of near-identical builds.
	We can already have .passthru.function in any package that needs it. So
it looks reasonable to use the following tactics:
	1. check needed flags
	2a. if everything needed is present in the passed package, use what is
provided
	2b. if something is missing, warn the user (now it's user's decision
whether reduced RAM/HDD usage is worth tuning configuration), add needed
flags and build the dependency using .passthru.function

	In that case, we have zero-effort possibility for the user to simply
install any package and a tool to hunt down duplicates manually by
tuning configuration. What drawbacks does it have relative to making the
user always hunt down all such problems?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQEcBAEBAgAGBQJJS2MAAAoJEE6tnN0aWvw3KQwH/05bcbOpTjuehqy+UHqXBZHg
AMdgj3fB1HExlRf3V++Gdn9dJD1ETL+KeCsEGD4Te28TCQROPqyfY9QVCQFYjjZu
70Fm6FI41u7WcuGOQn+UKwaK7QyW2c7TtI3fYX3inP84cpiBMPfIJIC3mp8ij9Xe
dxh62D0gsm4+HKtP3jjJV4abe0dXtAp96Wk9GZRyZKtB9sU3l2FmpsxaYtduyV2E
Pqm1Phwx4VZrRN7wG/08gPxXHJk1tCYmDiUGJm71WQ6XcCNV1CiwPhz8YR7r8plC
o3b+4k9rVuuPWOBW29/5/pQV9FRAZdWI9NowGCwdsD/d1ifoQEta04O7Fzdn138=
=WmKL
-----END PGP SIGNATURE-----