On 2022-11-14 at 14:31 -0400, PICCORO McKAY Lenz wrote: > if there a system upgrade (mayor with stdlib and libc6 linking) your > packages totally do not handle this as mooth, just we must complety > removed to again reinstall
libc is extremely stable. A program linked against an older libc will work on a system with a newer libc. Even using "the old implementation" in some cases through versioning symbols. Actually a good thing, since a libc which broke in such case would easily end up in an unusable system. On 2022-11-14 at 18:48 -0500, Sam Varshavchik wrote: > I don't need a tutorial about Debian standards. I don't need to be scolded > by these "Debian standards" that I have an executable-is-not-world-readable > or a non-standard-setuid-executable-perm. Debian seems to know better how > individual software packages should be considered, then the packages > themselves. > > I'm just curious about the average number of lintian-overrides per package, > in Debian. I found Debian's standards to be such a distraction that I had to > write my own script that runs lintian and automatically converts its noise > into overrides. I would not be surprised to learn that many others do the > same. Debian has 59k packages. Of course they need to standarise things somewhat so each package doesn't do everything on its completely own way. Imagine administering a system where each package used a different standard on where should the system settings live? > > > In conclusion your packages are more "easy to produce" rather than > > "easy to manage in upgrades", > > especially major upgrades when the whole system changes.. I hope > you > > understand. > > I think I'll wait and let time decide which version is easier to work > with. > > > NOTE ABOUT MAILDROP AND WEBADMIN: those are provided, > > maildrop just packages separatelly, and webadmin in build in. > > No. > > maildrop and courier-maildrop are configured differently. Debian > either packages the standalone maildrop package only, or packages > Courier's maildrop as a standalone package. I'm familiar with the tale of the two maildrops. However, > Ditto for sqwebmail. what's the problem with sqwebmail? AFAIK there's only one sqwebmail version. And I'm not aware of issues arising on how it has been packaged. Regards _______________________________________________ Courier-imap mailing list Courier-imap@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-imap
