2009/4/20 Oliver Charles :

Hi all,

I used to use Arch a while ago, and packaged quite a few Perl modules [1]. After switching operating systems, I've come back to Arch - and I need to be a good maintainer of my packages :)

I remember when I wrote these how frustrating it was manually writing just about every package for the dependancy tree. Personally, I'm of the stance that you should choose one package manager and stick with it - either all CPAN or fully Pacman/AUR. However, I've seen quite a few packages that do not do this. Instead, they rely on the fact that Build.PL and Makefile.PL are both capable of installing dependancies from CPAN.

Like I said, I personally don't like this approach of mixing 2 package managers, it just seems like a recipe for confusing both package managers.

Could anyone shed some light on what the *correct* procedure is - and also if there any tools out there that will scrape CPAN to build packages, before I write my own (in Perl, of course ;)

You can use perl-cpanplus-pacman [1] or pacpan [2] (webpage [3]). [1]: http://aur.archlinux.org/packages.php?ID=5954 [2]: http://aur.archlinux.org/packages.php?ID=23495 [3]: http://xyne.archlinux.ca/info/pacpan

On Mon, Apr 20, 2009 at 12:05, Oliver Charles wrote:

Thanks, so it seems I should be managing all dependancies via Pacman/Aur (even if they are fetched by CPAN). Pacpan looks great - I'll get that now!

--    Oliver Charles / aCiD2

You may also want a look at http://wiki.archlinux.org/index.php/Perl_Package_Guidelines

On Mon, Apr 20, 2009 at 15:55, Oliver Charles wrote:

On Mon, Apr 20, 2009 at 8:35 PM, Daenyth Blank wrote:

...

You may also want a look at http://wiki.archlinux.org/index.php/Perl_Package_Guidelines

Yea I saw that, it really doesn't tell me much other than how to write a PKGBUILD for Perl, which I kinda already knew :)

I'll update it with links to those CPAN managers Abhishek linked me to.

--    Oliver Charles / aCiD2

Strange, I could have sworn there used to be more useful info there than that... hmm..