[Slackbuilds-users] A question about maintaining perl/* slackbuilds.

[Zachary Storer]

Hello,

I'm currently working on a script to convert and test-build all of the
perl/* slackbuilds to use metacpan as their homepage, and www.cpan.org
as their download link. search.cpan.org is providing many dead links,
and users of sbotools are finding many dead download links, thus
forcing them to build manually.

To do this successfully, I need to update many of the perl/
slackbuilds to their latest version, and I want to do this in such a
way to where it won't break other modules, such as perl/perl-IO-Tty
and networks/mosh. Anyway, I also hope to update the modules in an
automated way by using
http://www.cpan.org/modules/02packages.details.txt.gz.

So my questions are:

1) If we decide to automate upgrading all of the perl/ slackbuilds to
use the latest version, how should we make sure it doesn't break other
slackbuilds that rely on that perl module?

2) If we decide to automate upgrading all of the perl/ slackbuilds,
should we have just a single maintainer for _all_ of the perl/
slackbuilds, or should we continue with having a different maintainer
for each perl slackbuild module?

3) #perl on freenode recommended that we use www.cpan.org for the
download link, if we decide to do this rather than using metacpan for
the download link, we will have to upgrade all perl/ slackbuilds to
their latest version, or we will have dead links. So, would you like
to use www.cpan.org for the download link, or would you rather use
metacpan for the download link until we make a decision on for my
question #2?

Note: I personally volunteer to help maintain perl/ slackbuilds if any
help is needed.

Also, please let me know if you have any questions.

Thanks,

Zac
---
Zachary Storer
zacts on irc