On Sun, Aug 16, 2009 at 09:08:41PM +0800, Zhang Sen wrote: > Of course we can notice such things ourselves and change the affected > recipes accordingly. But I would ask if anyone has some better ideas?
Conary does warn about all buildRequires that are listed in the recipe that it can't find a reason for. Since it can't know for certain that they aren't required for some other reason, it only warns about the possibility of the requirements being extraneous. _______________________________________________ Foresight-devel mailing list Foresight-devel@lists.rpath.org http://lists.rpath.org/mailman/listinfo/foresight-devel
