in reply to CPAN namespace help for Parse::DebControl

I see there's a DPKG-Tools package on CPAN. Maybe your module would fit nicely inside that package? It seems that your module would be most useful to those people that already handle dpkgs anyway.

Another idea would be to put it into the Archive:: namespace, which is already well-established. E.g.

I find it nicer to flesh out existing (and fitting, of course) namespaces rather than creating new ones.

Update: By the way, I don't find it so necessary to have "Parse" in the name. Many Perl modules do parsing, and most of the time it is just enough to name the thing that your module is dealing with (in this case: control files). It is implied that you parse those files in order to read/write them :).

  • Comment on Re: CPAN namespace help for Parse::DebControl

Replies are listed 'Best First'.
Re: Re: CPAN namespace help for Parse::DebControl
by JayBonci (Curate) on Apr 28, 2003 at 16:56 UTC
    I thought about the Archive::Debian namespace. My main objection with putting it in there, is that it's going to get lost. So many things in the distro are in that control format, and Archive isn't the first place I'd look for a parser.

    With Archive::Ar now complete, and with this module, I am going to be creating an Archive::Debian module that does debian .deb creation in pure perl / architecture independantly. This means that you could make fink debs, or debs even for win32 if you wanted.

    It mainly will solve my problem of wanting debian package analysis utilities on RedHat without porting the binary libraries.

    I agree with you that Debian::Control sounds good (because there's a lot of use for it, and the intended audience would know what it's for), but there are many wiser than I, and I'd like to see what some other more experience CPANites have to say.

        --jaybonci
[reply]

In Section Seekers of Perl Wisdom