public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jakub Moc <jakub@gentoo.org>
To: Mike Frysinger <gentoo-dev@lists.gentoo.org>
Subject: Re[2]: [gentoo-dev] punting the use.defaults feature
Date: Fri, 18 Nov 2005 16:59:31 +0100	[thread overview]
Message-ID: <1726602389.20051118165931@gentoo.org> (raw)
In-Reply-To: <20051118154312.GF24327@toucan.gentoo.org>

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


18.11.2005, 16:43:12, Mike Frysinger wrote:

> i see no reason to keep use.defaults around anymore, i think the rest of our
> config/profile system covers for it adequately and in a manner that doesnt
> confused people

Also, IIRC, saner alternatives have been suggested, like IUSE="+bleh" to enable
a use flag by default on a per-ebuild basis; use.defaults is something well
hidden from users, and USE flags automagically appearing/disappering after
emerge sync/installing an ebuild cause a lot of confusion.

>> - why has a mass of things been commited in there recently

> because they belong there

and break things/confuse people? What exactly is the benefit from this? Sorry,
I've apparently missed something, since I can't see much sense in committing
something just because it "belongs there"... Did not notice any call for adding
all that stuff either; actually - it's been done after someone requested to
remove one particular thing from use.defaults.

>> - confusing users

> the file has always confused people, whether they be user or dev

One more reason to get rid of it... :)

>> - rendering /etc/portage/package.keywords useless (install a dep for one
>> particular ebuild and enjoy the USE flag enabled globally)

> unrelated

Well, I don't think so... If I want to enable a feature for one specific ebuild
and a USE flag in /etc/portage/package.use pulls in a dep, that in turn enables
that use flag globally, it's obviously not what I intended and forces me to add
yet another -flag into make.conf

>> - causing unwanted results (I did not really install app-text/recode for the
>> purpose of enabling USE=recode globally and make it clash with half of php USE
>> flags e.g.)
>> - causing pointless breakage/bailing out in current ebuilds for users that have
>> not touched USE flags on their system at all

> you're confusing "feature" with "bug" ;)

I actually consider this feature to be a bug... :=)


--
jakub

[-- Attachment #2: Type: application/pgp-signature, Size: 183 bytes --]

  reply	other threads:[~2005-11-18 16:04 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-18 15:33 [gentoo-dev] use.defaults and pointless commits Jakub Moc
2005-11-18 15:37 ` [gentoo-dev] " Jakub Moc
2005-11-18 15:37 ` [gentoo-dev] " Donnie Berkholz
2005-11-18 15:43 ` [gentoo-dev] punting the use.defaults feature Mike Frysinger
2005-11-18 15:59   ` Jakub Moc [this message]
2005-11-18 19:18     ` Drake Wyrm
2005-11-18 19:31       ` Ciaran McCreesh
2005-11-18 19:45         ` Kurt Lieber
2005-11-18 20:03           ` Ciaran McCreesh
2005-11-18 20:08       ` Re[2]: " Jakub Moc
2005-11-18 20:31       ` Zac Medico
2005-11-18 23:14       ` Mike Frysinger
2005-11-20 19:55         ` Michael Marineau
2005-11-20 22:23           ` Spider (D.m.D. Lj.)
2005-11-20 23:06             ` Thomas de Grenier de Latour
2005-11-22 18:22               ` Marius Mauch
2005-11-22 19:00                 ` Mike Frysinger

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=1726602389.20051118165931@gentoo.org \
    --to=jakub@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