On Mon, Apr 18, 2005 at 01:52:18PM +1000, Martin Costabel wrote:
> Jack Howarth wrote:
> >In creating these packages, I did notice one feature that fink lacks, the

s/lacks/fails to document in the Packaging Manual/

> >ability to specify a Build-Conflicts field. This would have been very nice
> >to have to make sure the glut package was deinstalled when freeglut was
> >built and that the freeglut package was deinstalled when glut was built.
> >This is handy just to make sure the builds aren't leaky and picking up
> >headers and libs from the wrong glut that might be installed.

There would be the same situation if a freeglut got released that had
a bug in it, or really even any feature or #define change between
versions. This situation has occured, where an installed libfoo-dev or
libfoo-shlibs propagates errors or other features into the build of a
new version of libfoo*. It's always a symptom of a mistake in the
build process (for example, there was an old libtool that reliably
caused this), so that's what must be fixed.

Otherwise we may as well have a general feature whereby any .info that
supplies a -shlibs implicitly adds a BuildConflicts on all packages
that it supplies.

dan

-- 
Daniel Macks
[EMAIL PROTECTED]
http://www.netspace.org/~dmacks



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fink-devel

Reply via email to