public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Torsten Veller <ml-en@veller.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: perl-module.eclass -- review
Date: Mon, 2 Mar 2009 13:08:15 +0100	[thread overview]
Message-ID: <20090302115515.TA82c8a.tv@veller.net> (raw)
In-Reply-To: <20090302065621.GL16405@curie-int.orbis-terrarum.net>

* "Robin H. Johnson" <robbat2@gentoo.org>:
> On Fri, Feb 27, 2009 at 03:08:52PM +0100, Torsten Veller wrote:
> > Please review the attached perl-module.eclass.
> > Patch linked below.
> Are you going to include the changes from Bug 254980 so that s390 can
> build their stages properly?
> 
> Specifically, going to EAPI2 and adding DEPEND="dev-lang/perl[!build]"
> to the eclass.

Currently the eclass doesn't set any dependencies.
If it is used the ebuild has to depend on perl if needed.


I see the following options:

1) Don't add DEPEND to the eclass.
   So if a package is used for stage-building we have to raise EAPI and
   depend on dev-lang/perl[-build] in the ebuild.

   The part I don't understand in the bug above is:
   Does adding dev-lang/perl[-build] automagically reinstall
   perl during stage-building
   (here portage stops and complains).


2) Add DEPEND conditionally to the eclass.
   To give ebuilds the chance to inherit perl-module.eclass
   (and currently also perl-app.eclass) and support perl conditionally,
   we have to add another global variable to check it.

   (Checking CATEGORY and perl? probably could be added additonally)


3) Add DEPEND.
   Always depend on dev-lang/perl and 
   if EAPI=2 then depend on dev-lang/perl[-build]


Comments?



  reply	other threads:[~2009-03-02 12:09 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-27 14:08 [gentoo-dev] perl-module.eclass -- review Torsten Veller
2009-02-28 11:28 ` [gentoo-dev] Re: perl-module.eclass -- review - 2 Torsten Veller
2009-03-02  3:34   ` Donnie Berkholz
2009-03-02  7:24     ` Torsten Veller
2009-03-02 12:01       ` Bo Ørsted Andresen
2009-03-03 11:13         ` Peter Volkov
2009-03-03 13:09           ` Bo Ørsted Andresen
2009-03-09  1:50             ` Donnie Berkholz
2009-03-09  8:02               ` Rémi Cardona
2009-03-02  6:56 ` [gentoo-dev] perl-module.eclass -- review Robin H. Johnson
2009-03-02 12:08   ` Torsten Veller [this message]
2009-03-02 17:51     ` [gentoo-dev] " Donnie Berkholz
2009-03-02 18:13       ` Robin H. Johnson
2009-03-05 14:47         ` [gentoo-dev] Re: perl-module.eclass -- review - 3 Torsten Veller
2009-03-02 18:10     ` [gentoo-dev] Re: perl-module.eclass -- review Robin H. Johnson

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=20090302115515.TA82c8a.tv@veller.net \
    --to=ml-en@veller.net \
    --cc=gentoo-dev@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