public inbox for gentoo-perl@lists.gentoo.org
 help / color / mirror / Atom feed
From: perl <perl@evolone.com>
To: gentoo-perl@lists.gentoo.org
Subject: [gentoo-perl] modules availability
Date: Fri, 19 Dec 2008 17:26:34 -0800	[thread overview]
Message-ID: <20081219172634.7f34508a@lappy.evolone.org> (raw)

List --

I got some skeptical inquiries about the state of gentoo support for perl, in the chat space... I don't know, myself, what it looks like, really. What is 'virtual' for? What is "Dual Lifed"? Where to find out if not on this mailing list's archives?

Anyway... AFAICT, everything "CPANTS" has as is_core, well, is in perl-core/. 

[I know crap about bash, but here's what I did:]

notfound="No matches found."; for atom in `perl checker.pl`; do iscore=` eix -Ace perl-core/$atom `;if [ "$iscore" != "$notfound" ] ; then echo $iscore; else isavail=` eix -Ace dev-perl/$atom `;if [ "$isavail" != "$notfound" ] ; then echo $isavail; else echo $atom $notfound; fi ; fi ;done 

"perl checker.pl" just calls this SQL:

select package from modules left join dist on (modules.dist=dist.id) where modules.is_core=1 group by package

... hopefully getting the complete list of core packages. It loops when the module is installed and prints after 

my $atom = $row->[0]) =~ s/(?:-[-.0-9a-z]+)*(?:\.tar\.gz|\.zip)$//; 
my $t = [ split /\//,$atom ]->[1] ;
$atom = ($t // $atom);
say $atom;

... to get the ebuild name from the tarball name.

[ Some of which makes me happy, just to use some new perl features. ;-) ]

So, I have to guess these results are errors from the CPANTS database, or just aren't core (or buildable) on my linux system. So that's pretty good coverage for perl-core.

CPAN-DistnameInfo No matches found.
Class-Config No matches found.
IPC_SysV No matches found.
Mac-iPhoto-Shell No matches found.
Net-FileShare No matches found.
Net No matches found.
PathTools No matches found.
Time-Object No matches found.
Win32 No matches found.
Win32-File-Summary No matches found.
Win32API-File No matches found.

As for the rest, I'm gathering them now.

grep "No match" results_notcore |wc -l && \
grep -v "No match" results_notcore |wc -l
14584
671

eix -c --in-overlay perl-experimental |wc -l
288

. . .

What would be cool is if we could move perl-"experimental" to be an *experimental overlay* of automatically created ebuilds that corresponds to CPAN.

Then it'd be nice to fix up a *maintained* perl overlay (gentoo-perl?) to be like a ppm repository (without the binary parts), maintained and advertised as such, for any perl modules that aren't part of the official gentoo tree. 

So if anyone wants, they have a place to grab something probably ready to go from overlays. If it needs fixing and gets fixed, it has a place to live that distinguishes it from the automatic ebuilds. 

CPANTS data has a binary flag for in (or not in) a couple of other distros. Maybe meeting that degree of support, or that of the activestate ppm repository would be a good starting benchmark..??

Cheers,

-- Michael Higgins



             reply	other threads:[~2008-12-20  1:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-20  1:26 perl [this message]
2008-12-21 14:06 ` [gentoo-perl] modules availability Michele Beltrame

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20081219172634.7f34508a@lappy.evolone.org \
    --to=perl@evolone.com \
    --cc=gentoo-perl@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox