public inbox for gentoo-perl@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michael Cummings <mcummings@gentoo.org>
To: gentoo-perl@lists.gentoo.org
Subject: Re: [gentoo-perl] CPAN ebuild moans and groans
Date: Fri, 13 Jan 2006 12:10:53 -0500	[thread overview]
Message-ID: <1137172254.6159.13.camel@localhost> (raw)
In-Reply-To: <200601122332.18865.beaucox@hawaii.rr.com>

[-- Attachment #1: Type: text/plain, Size: 2230 bytes --]

Hey there Beu,
> 1) Who is it that made some CPAN builds lowercase (module-build,
> not Module-Build, net-server not Net-Server)? Bad idea. It would
> be easier (for my system, at least) to leave the names in the
> CPAN form.

At one point, the power that was wanted all gentoo ebuilds to be lower
case. for a few months or so, dev-perl wasn't granted its 'grandfather'
clause in this regard, hence why there are a few lowercase modules (not
counting the ones that are legitimately lower case, like
dev-perl/version). the hassle involved in moving an ebuild has warranted
fixing the ones like module-build tbh.

> 2) Lots of trouble with modules that indicate major versions
> with 2 digits and minor revisions with four; Module-Build
> for example:
>   ...
>   Module-Build-0.26
>   Module-Build-0.2610
>   Module-Build-0.2611
>   Module-Build-0.27
>   ...
Blame portage, not us. For a while there at least (pretty sure its still
the case, but who wants to find out the bad way?), portage would get
confused by the length of the strings in re: the version numbers. Then
you have modules with _'s and -'s in the middle and it all goes to pot.

> I bypassed this problem by making my ebuild file names as
> follows:
>   Foo-Bar-1137143770.0.2611.ebuild
> where 1137143770 is the 'epoch second' date of the tarball.
> I can then be sure the order is correct and put code
> in all ebuilds to get rid of the date-seconds:
>   MY_PV=${PV:11}  and so on.
> 
ick

> 3) I pull my tarballs from my local mirror. I am using my
> apache server to do this via SRC_URI="http://localhost/..."
> But sometimes the request goes to my defined gentoo mirror
> anyway. Why?
because you don't have nomirror in your ebuilds most likely. src_uri is
used when the mirrors don't have something (or when the mirror is doing
the nightly fetches)

> 4) How about adding file:/// and rsync:// support for
> SRC_URI?

not a portage feature, you'd need to court the portage folks on that
one.

hope this helps - tree's a bit large and around for years, and what with
me mucking in for 3+ of those years, a lot of things that were required
and/or a good idea at the time we're just plain ol' stuck with now

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2006-01-13 17:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-13  9:32 [gentoo-perl] CPAN ebuild moans and groans Beau E. Cox
2006-01-13 17:10 ` Michael Cummings [this message]

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=1137172254.6159.13.camel@localhost \
    --to=mcummings@gentoo.org \
    --cc=gentoo-perl@gentoo.org \
    --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