public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Thomas de Grenier de Latour <degrenier@easyconnect.fr>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Little prog to check compile-options for packages.
Date: Wed, 16 Apr 2003 19:36:41 +0200	[thread overview]
Message-ID: <20030416193641.631eee8f.degrenier@easyconnect.fr> (raw)
In-Reply-To: <3E9D5C66.6090405@home.se>


Nice script, thanks.

> I thik I am the only one in the world who is interested in this
> feature

I think that we are numerous to wonder which packages have to be rebuilt
after a USE flag change: For instance, if a user adds "gtk2" to his USE
flags, applications that support it will only use it after their next
update, whereas he may want to recompile this apps right now.

So my point is that your program could be even more useful if it could
show only diffs on flags that appear in the IUSE variable from their
ebuild. This would be a nice answer to the "what should I recompile?"
question.


Here are a few other ideas of possible improvements:

 * a few options: --cflags-only (-c), --useflags-only (-u), etc.

 * integration into "qpkg" (as yet another "Information Selection"
option). I know "qpkg" is still a bash script, but I think there are
plans for a python version, am I wrong?

 * taking ebuilds cflags filters into account. (Because if you go from
"-O2" to "-O3" in make.conf, and then wonder what packages have to be
recompiled for optimisation, those which filter "-O3" to "-O2" should
not be listed.)


Having said that, I won't blame you if you don't want to implement my
suggestions. I'm not a python programmer myself, and I really don't know
how hard it would be. :)

-- 
Thomas.

--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2003-04-16 17:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-16 13:36 [gentoo-dev] Little prog to check compile-options for packages Daniel Armyr
2003-04-16 17:36 ` Thomas de Grenier de Latour [this message]
2003-04-18 12:57   ` [gentoo-dev] Talk is cheap. Was: " Daniel Armyr
2003-04-18 13:07     ` Daniel Armyr
2003-04-20 13:48       ` Daniel Armyr
2003-04-22  8:27       ` Michael Kohl
2003-04-22 15:48         ` Daniel Armyr

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=20030416193641.631eee8f.degrenier@easyconnect.fr \
    --to=degrenier@easyconnect.fr \
    --cc=gentoo-dev@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