public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Daniel Robbins <drobbins@gentoo.org>
To: vapier@gentoo.org
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] masking glibc-2.3.2-r3
Date: Fri, 05 Sep 2003 09:30:51 -0600	[thread overview]
Message-ID: <1062775850.27678.42.camel@ht.gentoo.org> (raw)
In-Reply-To: <200309050913.35962.vapier@gentoo.org>

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

On Fri, 2003-09-05 at 07:13, Mike Frysinger wrote:
> anyone have any qualms with me changing the masking on glibc-2.3.2-r3 from 
> KEYWORDS="-*" to package.mask ?
> ive been using it for quite sometime and was just about to update to NPTL-0.57 
> (released like 2 days ago) when i realized i still inject the latest unstable 
> version of glibc so that my glibc's dont get screwed up ... i prefer to put 
> masked stuff in package.mask and then unmask in package.unmask ...
> -mike

For core stuff, I especially recommend *not* using package.mask and
using KEYWORDS="-*" instead. Otherwise weird things can happen in
relation to the x86 and selinux profiles. package.mask doesn't work well
for profiles that share the same masking keyword, particularly when you
get around to removing the entry in package.mask.

Best Regards,

Daniel

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

  parent reply	other threads:[~2003-09-05 15:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-05 13:13 [gentoo-dev] masking glibc-2.3.2-r3 Mike Frysinger
2003-09-05 14:57 ` Kumba
2003-09-05 15:17   ` Mike Frysinger
2003-09-05 20:15     ` Martin Schlemmer
2003-09-06  6:23       ` Tony Clark
2003-09-05 20:15   ` Martin Schlemmer
2003-09-05 15:30 ` Daniel Robbins [this message]
2003-09-05 20:14 ` Martin Schlemmer

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=1062775850.27678.42.camel@ht.gentoo.org \
    --to=drobbins@gentoo.org \
    --cc=gentoo-dev@gentoo.org \
    --cc=vapier@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