gregor herrmann wrote:
> On Tue, 23 Mar 2010 22:04:58 +0900, Ansgar Burchardt wrote:
> Count me in.
> A consistent schema is easier for searching, for downloading
> (source|binary) package, for finding a package's bugs or PTS page,
> for "blindly" adding dependencies ...

consistent_schema++ that is for sure. on the other hand if the demand for it is
based on searching and lookup, why don't we create a script to look up any Perl
module and return the proper Debian package name for it?

besides the listed packages, there are a couple of bundles. starting with
/perl(-base|-modules)?/, /libcatalyst-modules(-extra)?-perl/, etc. there will be
always exceptions, right?

one solution is what dh-make-perl uses - the apt-file index. should not be
really complicated to extract that part in the script that will accept
Module::Name or Module/Name.pm and return Debian package name.

the other way is the script I've committed recently [1] that returns the package
names with Perl versions.

one or the other, it would be really helpful to have a tool to look for Perl
module in Debian. the "root/base" package name hides a lot of module names that
are currently hidden inside.

cheers,
Jozef


[1] http://svn.debian.org/viewsvn/pkg-perl/scripts/apt-pm/script/apt-pm


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 4BA9E285.6060600@kutej.net">http://lists.debian.org/4BA9E285.6060600@kutej.net

On Wed, 24 Mar 2010, Stéphane Glondu wrote:


Carlo Segre a écrit :

2. the ifeffit source package is contrib and cannot be built by the
autobuilders because of its build time dependence on pgplot5.

The latter is causing me much grief and needs to be solved before I work
on consistency issues. Right now I have to build the package by hand on
whatever architectures I can get my hands on (I only have 8) and upload
all the binaries. The package has not migrated to testing for nearly 2
years because not all the architectures are present and until this is
resolved, there is really no point since it will only languish in unstable.


Why didn't you just ask removal of binary packages on architectures that
lack up-to-date packages?



Well, it was because of the inconsistencies in the buildd systems. Some
would build using non-free sources, others would not. This has now
changed and none will. Then there was the presence of the unofficial
buildd network that was used to build non-free packages. I had hoped that
this could be used. Now it is clear that this network is no longer
functioning. I will have to do precisely as you say.


Carlo

--
Carlo U. Segre -- Professor of Physics
Associate Dean for Graduate Admissions, Graduate College
Illinois Institute of Technology
Voice: 312.567.3498 Fax: 312.567.3494
segre@iit.edu http://www.iit.edu/~segre segre@debian.org

Hi,

Ansgar Burchardt <ansgar@43-1.org> writes:

> the Debian Perl Policy asks for packages for the Foo::Bar module to be
> named libfoo-bar-perl [1]. Some packages do not adhere to this scheme:
>
[...]
>
> Unless there are objections I will file bugs of severity "normal" in a
> few days for these packages.

The bugs are now filed with severity "wishlist" and user-tagged.
A list can be obtained from [1].

Regards,
Ansgar

[1] <http://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=perl-naming-policy;users=ansgar@2008.43-1.org>


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 87zl1ppxte.fsf@marvin.43-1.org">http://lists.debian.org/87zl1ppxte.fsf@marvin.43-1.org

On Tue, Mar 30, 2010 at 11:40 AM, Ansgar Burchardt <ansgar@43-1.org> wrote:
> Hi,
>
> Ansgar Burchardt <ansgar@43-1.org> writes:
>
>> the Debian Perl Policy asks for packages for the Foo::Bar module to be
>> named libfoo-bar-perl [1]. *Some packages do not adhere to this scheme:
>>
> [...]
>>
>> Unless there are objections I will file bugs of severity "normal" in a
>> few days for these packages.
>
> The bugs are now filed with severity "wishlist" and user-tagged.
> A list can be obtained from [1].
>
> Regards,
> Ansgar
>
> [1] <http://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=perl-naming-policy;users=ansgar@2008.43-1.org>
>
>
> --
> To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
> Archive: http://lists.debian.org/87zl1ppxte.fsf@marvin.43-1.org
>
>

Philosophical question: When does this sort of thing get taken care
of? In twenty years, will Debian (if it's still going) have myriad
misnamed libraries? I know one can

Shouldn't housecleaning like this be of higher priority, especially
say, when a new version has just been put out? That way, maintainers
would have months to slowly work on one package (and its associated
reverse-dependencies) at a time.

I do not know the technical constraints (no autobuild, etc), but
consistency is a valuable trait of an operating system.

--
Luke L.


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: c1775fd41003301204k21a4f8f5yf9fe76330ee4a366@mail. gmail.com">http://lists.debian.org/c1775fd41003301204k21a4f8f5yf9fe76330ee4a366@mail. gmail.com

On Wed, Mar 31, 2010 at 3:04 AM, Luke L <lukehasnoname@gmail.com> wrote:

> Philosophical question: When does this sort of thing get taken care
> of? In twenty years, will Debian (if it's still going) have myriad
> misnamed libraries? I know one can
>
> Shouldn't housecleaning like this be of higher priority, especially
> say, when a new version has just been put out? That way, maintainers
> would have months to slowly work on one package (and its associated
> reverse-dependencies) at a time.
>
> I do not know the technical constraints (no autobuild, etc), but
> consistency is a valuable trait of an operating system.

This sort of thing is automatically detectable, so there is now a
wishlist bug against lintian to detect it and warn the developer.
Unless people start ignoring lintian or new developers don't learn
that lintian exists, that should keep this problem at bay.

--
bye,
pabs

http://wiki.debian.org/PaulWise


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: q2pe13a36b31003302325h45317970r9077d31d96e656ee@ma il.gmail.com">http://lists.debian.org/q2pe13a36b31003302325h45317970r9077d31d96e656ee@ma il.gmail.com