Hi all. I've noticed that several of our "essential" packages build shared libraries (for example, bzip2 and ncurses). This presents a bit of a quandry for the shared libraries policy.
If we impose the shared libraries policy on these packages, they'll be split into main and -shlibs. Should the "main" package be essential? Well, if it is, then nobody will ever be able to remove it in favor of main2. This defeats the purpose of the shared libraries policy. On the other hand, if it isn't essential, then some other packages which can currently rely on the presence of the essential package, might need a BuildDepends declaration. So I think either we declare that essential packages should not be split up, or else we have to have some transition period in which people are encouraged to add BuildDepends on some of the essential packages. Does anybody know how Debian handles this? -- Dave _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
