From: Dave Nebinger <dnebinger@joat.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] What happens with masked packages?
Date: Wed, 22 Feb 2006 17:44:31 -0500 [thread overview]
Message-ID: <43FCE94F.1060802@joat.com> (raw)
In-Reply-To: <200602221612.33988.bss03@volumehost.com>
Boyd Stephen Smith Jr. wrote:
>
> I hate how emerge / portage calls a missing keyword "masked". It's really
> not the same thing as being in package.mask (so called "hard-masked").
[snip]
> Right now, we see package.mask, -*, and sometimes even ~ARCH being used to
> indicate instability from upstream. For example, the gcc-4.1 ebuilds work
> perfectly, yet are marked -*. As another example, there was a bit of time
> when the KDE 3.5_beta2 ebuilds worked fine (and were ~ARCH) but they were
> package.mask'ed.
Unfortunately we are in such a state that you don't really know if a
soft-masked package is soft-masked because the ebuild is unstable or
whether the package itself is as yet considered unstable; I don't think
the soft-masking is used in a consistent way even though the gentoo devs
might believe it is.
With hard-masked packages it's pretty clear that you shouldn't use them
unless you *really* know what you're doing.
But with soft-masked packages it's not as clear. Even if it were the
case that soft-masking indicates only ebuild instability, the ebuild
controls how the package is compiled, installed, configured... A bad
ebuild could really mess up your system even if the package itself has
no problems.
The handbook clearly suggests that you should avoid even soft-masked
packages for production systems, although we would all be able to say
where we've used a soft-masked package with no issues.
Recently there was a thread going on about a user with a soft-masked
glibc and a problem with "mdns off" in /etc/host.conf; glibc is such a
critical system component, imagine what you'd need to do if the
soft-masked glibc resulted in a corrupt library, the core library that
all of your system components use in one fashion or another. No boot,
no shell, no command execution, no remote access to fix, etc. You're
left booting from a recovery disk to try to either restore from your
latest backup (if you're making backups) or rebuilding components trying
to get the system back to a workable state.
To that end, you should consider the consequences of using those
soft-masked packages and whether you're willing to deal with them in the
face of failures.
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-02-22 22:53 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-22 19:55 [gentoo-user] What happens with masked packages? Thierry de Coulon
2006-02-22 20:02 ` Dave Nebinger
2006-02-22 20:38 ` Thierry de Coulon
2006-02-22 21:38 ` Rafael Bugajewski
2006-02-22 22:12 ` Boyd Stephen Smith Jr.
2006-02-22 22:44 ` Dave Nebinger [this message]
2006-02-22 22:53 ` Thierry de Coulon
2006-02-22 23:08 ` Boyd Stephen Smith Jr.
2006-02-24 17:31 ` Ciaran McCreesh
2006-02-24 20:57 ` Boyd Stephen Smith Jr.
2006-02-25 18:57 ` Ciaran McCreesh
2006-02-25 19:34 ` Boyd Stephen Smith Jr.
2006-02-25 23:47 ` Mariusz Pękala
2006-02-26 5:16 ` Boyd Stephen Smith Jr.
2006-02-26 16:34 ` Mariusz Pękala
2006-02-26 17:06 ` Bo Andresen
2006-02-26 20:40 ` Boyd Stephen Smith Jr.
2006-02-26 23:25 ` John J. Foster
2006-02-27 0:15 ` Bo Andresen
2006-02-27 0:57 ` Boyd Stephen Smith Jr.
2006-02-27 3:44 ` Zac Slade
2006-02-26 16:11 ` Ciaran McCreesh
2006-02-26 23:29 ` John J. Foster
2006-02-27 0:11 ` Ciaran McCreesh
2006-02-27 1:26 ` John J. Foster
2006-02-27 17:17 ` Ciaran McCreesh
2006-02-27 17:33 ` Dave Nebinger
2006-02-27 18:51 ` Ciaran McCreesh
2006-02-22 21:27 ` Boyd Stephen Smith Jr.
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=43FCE94F.1060802@joat.com \
--to=dnebinger@joat.com \
--cc=gentoo-user@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