Re: Hard coded package names in lintian

2007-12-16 Thread Russ Allbery
Luk Claes <[EMAIL PROTECTED]> writes: > I'm certainly ready to do a mass bug filing. There surely should be > documentation on how to transition from gtk1.2 to gtk2.0 by now... Yes, it says "rewrite the software to use the new APIs." I've not seen any simple transition, apart from some wide-rang

Re: Hard coded package names in lintian

2007-12-16 Thread Luk Claes
Russ Allbery wrote: > Luk Claes <[EMAIL PROTECTED]> writes: > >> So, libglib1.2ldbl, libgtk1.2 and maybe libgd2-xpm would qualify to be >> included? >> >> Do you want me to file a bug to include them or is mentioning them over >> here enough? > > Could you explain more why that would be? For the

Re: Hard coded package names in lintian

2007-12-16 Thread Luk Claes
Russ Allbery wrote: > Luk Claes <[EMAIL PROTECTED]> writes: > >> So, libglib1.2ldbl, libgtk1.2 and maybe libgd2-xpm would qualify to be >> included? > > libgd2-xpm isn't even in oldlibs and there's no hint in the package > description that it shouldn't be used. Is it really being phased out? Th

Re: Hard coded package names in lintian

2007-12-15 Thread Kumar Appaiah
On 16/12/2007, Russ Allbery wrote: > > So, libglib1.2ldbl, libgtk1.2 and maybe libgd2-xpm would qualify to be > > included? > > libgd2-xpm isn't even in oldlibs and there's no hint in the package > description that it shouldn't be used. Is it really being phased out? I am unsure about this, as th

Re: Hard coded package names in lintian

2007-12-15 Thread Russ Allbery
Luk Claes <[EMAIL PROTECTED]> writes: > So, libglib1.2ldbl, libgtk1.2 and maybe libgd2-xpm would qualify to be > included? libgd2-xpm isn't even in oldlibs and there's no hint in the package description that it shouldn't be used. Is it really being phased out? -- Russ Allbery ([EMAIL PROTECTED

Re: Hard coded package names in lintian

2007-12-15 Thread Russ Allbery
Luk Claes <[EMAIL PROTECTED]> writes: > So, libglib1.2ldbl, libgtk1.2 and maybe libgd2-xpm would qualify to be > included? > > Do you want me to file a bug to include them or is mentioning them over > here enough? Could you explain more why that would be? For the first two, do you think there ar

Re: Hard coded package names in lintian

2007-12-15 Thread Luk Claes
Russ Allbery wrote: > Luk Claes <[EMAIL PROTECTED]> writes: >> Russ Allbery wrote: > >>> Yes. If there are significant packages that become obsolete and >>> warrant a lintian warning to aid in a transition, please file a >>> wishlist bug against lintian and we'll include that check in the next >>

Re: Hard coded package names in lintian

2007-12-15 Thread Russ Allbery
Luk Claes <[EMAIL PROTECTED]> writes: > Russ Allbery wrote: >> Yes. If there are significant packages that become obsolete and >> warrant a lintian warning to aid in a transition, please file a >> wishlist bug against lintian and we'll include that check in the next >> release. >> debcheck is av

Re: Hard coded package names in lintian

2007-12-15 Thread Luk Claes
Russ Allbery wrote: > Kumar Appaiah <[EMAIL PROTECTED]> writes: >> In particular, if some package enters or leaves a black/whitelist, >> wouldn't a new lintian version be warranted in the current scheme of >> things? > > Yes. If there are significant packages that become obsolete and warrant a >

Re: Hard coded package names in lintian

2007-12-15 Thread Russ Allbery
Kumar Appaiah <[EMAIL PROTECTED]> writes: > While observing the lintian sources, I observed that Dep.pm has hard > coded package names for all the obsolete, essential packages etc. I was > wondering, why are these lists not generated at runtime? One reason > could be that I can't trust that the so

Hard coded package names in lintian

2007-12-15 Thread Kumar Appaiah
Dear QA and Lintian people, While observing the lintian sources, I observed that Dep.pm has hard coded package names for all the obsolete, essential packages etc. I was wondering, why are these lists not generated at runtime? One reason could be that I can't trust that the source of the data on th