Here's the point: there is a new version of gettext with a new major version number for the library. In an ideal world, we would have gettext-shlibs, gettext-dev, gettext2-shlibs, and gettext2-dev all available. (This is what I am trying to achieve, in fact.)
Now, which of these are essential? Well, clearly we don't want the -dev packages to be essential. We *do* want the gettext-shlibs to be essential for now, since dpkg depends on it. However, at some future date we will probably want to compile dpkg with gettext2-shlibs instead of gettext-shlibs, and so we'll want to change which one is essential. If other packages have not been required to specify their dependency on gettext-shlibs, things will break at that stage. -- Dave ------------------------------------------------------- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
