On Monday, June 9, 2003, at 05:54 PM, jfm wrote:
On Tuesday, Jun 10, 2003, at 00:27 Europe/Brussels, Max Horn wrote:
Still don't see the point: if at some point we have a gettext2-shlibs, then it will at some point become essential, too. Period. The "old" gettext-shlibs wouldn't stop being essentia - after all, why should it? The only reason would be "shorter bootstrap time" - but I don't think it would actually work, unless the new gettext is 100% source compatible, we'd still need the old gettext anyway.
I would have thought that the "old" gettext-shlibs would naturally stop being essential
as soon as there is a version of dpkg depending on a newer one.
Where is my misunderstanding ??
Packages will still be linked against the old gettext-shlibs, and if its not essential or depended on, it will be removable, which will break things.
The new header -dev pacakges (gettext-dev & gettext2-dev) cannot be "Essential" because they have to be swapped out at will by packages. If they aren't "Essential", then they won't always be there. If they aren't always there, then they MUST be BuildDepended on, so they get installed when needed. A->B->C :) Thus:
I agree with drm here, unless we are going to have the same set of essential packages at the same versions (the current ones :) forever, we need to add depends on them to everything. It isn't that hard, it can all be scripted as i said.
-Ben
------------------------------------------------------- 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
