Dave Vasilevsky wrote:
Yes, we ought to do that. As an ugly hack in the meantime, why not read STDERR and look for the string '.patch: No such file or directory' ?
An easier hack would be to feed STDERR to patch. It will choke when there is an error:
sed 's|@PREFIX@|%p|g' %a/%n.patch 2>&1 | patch -p1
OTOH, there are many other situations where a package continues to build, sometimes even completes the build, although en error appeared but was ignored. The mailing lists are full of such cases. Should we hunt for all these cases and try to "fix" them?
-- Martin
------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ Fink-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fink-devel
