public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Andreas K. Huettel" <dilfridge@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: perl-module.eclass: respect CFLAGS, LDFLAGS - please review
Date: Sun, 22 Jun 2014 20:13:59 +0200	[thread overview]
Message-ID: <201406222014.04385.dilfridge@gentoo.org> (raw)
In-Reply-To: <CAGfcS_=vtn23S=9KjipHABYqdPz+qc5r_ohSY8ZkCC7xMkxXwQ@mail.gmail.com>

[-- Attachment #1: Type: Text/Plain, Size: 1484 bytes --]

Am Sonntag, 22. Juni 2014, 15:31:43 schrieb Rich Freeman:
> On Sun, Jun 22, 2014 at 9:11 AM, Kent Fredric <kentfredric@gmail.com> wrote:
> > On 23 June 2014 01:02, Duncan <1i5t5.duncan@cox.net> wrote:
> >> The usual conditional for that is USE=custom-cflags or a similar variant
[...]
> > The problem with a USE flag here as such is the change this eclass makes
> > affects >900 packages in dev-perl/ , and its not easy to casually
> > determine which of those packages have any C bits where CFLAGS are even
> > meaningful.
> > 
> > Which would mean having >900 packages with a new IUSE value that did
> > nothing for a majority of them.

The numbers are even worse; the use flag would be added to ~1400 packages, and 
it would actually matter for only ~300.

> Would it make more sense to move filtering (and thus the flag) to
> packages that actually use it, instead of doing it in the eclass?  By
> the same logic you have >900 packages filtering CFLAGS when many of
> them don't even use CFLAGS.

Offhand I don't know any way how the eclass could "know" whether a perl 
package requires C building or not. Any heuristics would be a hack at best. It 
might even be preferable to manually add some variable to 300 packages in the 
ebuild (which then makes the eclass add a use-flag custom-cflags).
i.e.

PERL_CFLAGS_HANDLING=yes
inherit perl-module

-- 

Andreas K. Huettel
Gentoo Linux developer 
dilfridge@gentoo.org
http://www.akhuettel.de/


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

  reply	other threads:[~2014-06-22 18:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-22  9:41 [gentoo-dev] perl-module.eclass: respect CFLAGS, LDFLAGS - please review Andreas K. Huettel
2014-06-22  9:54 ` Michał Górny
2014-06-22 18:17   ` Andreas K. Huettel
2014-06-22 13:02 ` [gentoo-dev] " Duncan
2014-06-22 13:11   ` Kent Fredric
2014-06-22 13:31     ` Rich Freeman
2014-06-22 18:13       ` Andreas K. Huettel [this message]
2014-06-22 19:10         ` Kent Fredric
2014-06-22 19:24           ` Kent Fredric
2014-06-23  2:24         ` Duncan

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=201406222014.04385.dilfridge@gentoo.org \
    --to=dilfridge@gentoo.org \
    --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