Subject: use of NO_PATCH considered unhelpful
To: None <firstname.lastname@example.org>
From: Andrew Brown <email@example.com>
Date: 12/26/2002 14:41:22
i note that for pkgs that exist only in pkgsrc (ie, there is no other
distribution point, such as pkglint, digest, etc), NO_PATCH is
typically set (well...defined) in the makefile. of course, if there
*were* to be patches, it would be just as straightforward for one to
fix the actual code than to make a patch. simpler, even.
however it makes it rather difficult to apply *local* patches to these
in the case of pkglint (which i was just mucking with), adding a
do-extract target to the makefile (to do the copying from the files
directory to the work directory) and unsetting NO_PATCH made
everything happy again.
is there any reason this new idea might not be encouraged?
|-----< "CODE WARRIOR" >-----|
firstname.lastname@example.org * "ah! i see you have the internet
email@example.com (Andrew Brown) that goes *ping*!"
firstname.lastname@example.org * "information is power -- share the wealth."