public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Matt Rickard <frogger@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] i hate KEYWORDS=-*
Date: Mon, 4 Aug 2003 20:12:35 -0400	[thread overview]
Message-ID: <20030804201235.10a2dae7.frogger@gentoo.org> (raw)
In-Reply-To: <200307301039.24918.vapier@gentoo.org>

Sorry for the belated reply, but it seems we still haven't done anything
about this -- and it frustrated me enough today that I decided to revive
this thread :)

> so i guess people are using KEYWORDS=-* because they dont want ppl
> easily emerging a package that will break them ... specifically the
> latest gcc/glibc ebuilds ... now while i agree that they are not
> suitable for stable or unstable systems, and maybe too risky even for
> package.mask, it is a pita to emerge these suckers and then safely
> keep them on youur system ...

I don't see what KEYWORDS=-* does that package.mask doesn't?  Just mark
the packages unstable, package.mask them, and throw in a comment in
package.mask saying "This will most likely completely break your
system".  

Problem solved.  Users don't get the package, and developers can easily
unmask it if needed.  This certainly beats the screwing around you need
to do now to get these packages built.

> 
> what i propose is that people who make ebuilds with KEYWORDS=-* add in
> an extra little word, namely 'pleasebreakme'.  that is, from now on,
> have it read:
> KEYWORDS="-* pleasebreakme"

I don't see any reason for this.  Isn't this the exact reason we have
package.mask?

--
Matt Rickard
frogger@gentoo.org

--
gentoo-dev@gentoo.org mailing list


      parent reply	other threads:[~2003-08-05  0:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-30 14:39 [gentoo-dev] i hate KEYWORDS=-* Mike Frysinger
2003-07-30 15:17 ` Dhruba Bandopadhyay
2003-07-30 22:38   ` Mike Frysinger
2003-08-05  0:12 ` Matt Rickard [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=20030804201235.10a2dae7.frogger@gentoo.org \
    --to=frogger@gentoo.org \
    --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