Package: xlibs Version: 4.2.1-16 Severity: normal Followup-For: Bug #233818
Hi, First I have to start off to say I have the greatest respect for the X packages Debian provides. Most certainly is not a job many are capable of, the quality of the packages are typically extremely high, and those who complain the official packages take too long obviously have not had a poke around the Internet too see what the XFree packages require before they hit the offical Debian, unstable branch. Great Work. I do need to chime in on this one though. While I can see the reason you need to enforce a clean of xlib6g on machines, the way it is being done by the new packages, there is no simple (equivs) means of being able to override the decision, which could be a good thing for many systems, is a bad one for those who do have packages depending on xlib6g (most notably netscape). Not having much experience with packaging things, it looks like (hey I could be way off here) that a conflict against the last official version of xlib6g would clean out the systems that don't care about xlib6g, but would also allow people to create a dummy package to provide it. Although how many of us that require netscape 4.crap are probably few and far between. Surely altering the Conflict/Replace to be version dependant, giving some of us an easy fix would not be bending over backwards? At the end of the day I will (and must) respect your decision, your expertise with packaging and X is going to be beyond mine by a factor I can not imagine, I can only thank you for listening to my request. Thanks again for your hard work on Xfree and Debian, it is much appreciated. Regards, Stewart James
