From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: Moving the updated apache and associated ebuilds back into package.mask
Date: Sat, 16 Apr 2005 06:18:08 -0700 [thread overview]
Message-ID: <pan.2005.04.16.13.18.07.622107@cox.net> (raw)
In-Reply-To: 200504160656.43452@zippy.emcb.local
Elfyn McBratney posted <200504160656.43452@zippy.emcb.local>, excerpted
below, on Sat, 16 Apr 2005 06:56:34 +0100:
> A number of people have suggested putting these updated ebuilds back into
> package.mask, or lessening the impact of the upgrade from current stable
> apache to the new ~arch apache. So, I would like to solicit advice from the
> developer community as to how we can rectify this.
>
> The way I see it, we have three options:
> - package.mask (downgrades for those early adopters)
[snip]
As a user that tends to get a bit upset when perfectly working (on my
system) packages are package masked, forcing a downgrade, without clear
reason, here's my perspective.
* Put a clear explanation in the package-mask comment, particularly
indicating that it's safe to unmask and continue to use if you already
have it installed and working -- IOW, that it's not a security issue
causing the masking. Something like,
# Masked pending further development and testing. Current working
# installations may package.unmask to prevent # forced downgrade.
Or, reference a bug number instead of that "pending" language.
Again, just clearly indicate the reason for any masking that will force a
downgrade, particularly whether it's security related or not, and the
consequences of /not/ downgrading, thus giving the user, that is, the
local Gentoo system administrator, enough information to make a good
decision on whether they can /safely/ package.unmask it and continue to
use it, or not.
I must say... In general, the Gentoo devs already get high marks for this.
=8^) Only once have I had to ask what the force-downgrade masking was
about, because all the comment effectively said was "remasking this",
something I obviously already knew if I was looking at the comment in the
package.mask file. =8^( (Actually, I think that incident had to do with
keyword masking, but the point still stands. Clear comment explaining
why, and I'm a happy camper <g>; unclear comment, and I'm not, because
I've been deprived of the information necessary to effectively carry out
/my/ responsibilities as a Gentoo sysadmin.)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman in
http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-04-16 13:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-16 5:56 [gentoo-dev] Moving the updated apache and associated ebuilds back into package.mask Elfyn McBratney
2005-04-16 6:10 ` Lance Albertson
2005-04-16 12:38 ` Paul Varner
2005-04-19 19:31 ` Paul de Vrieze
2005-04-19 19:45 ` Elfyn McBratney
2005-04-19 20:51 ` Paul de Vrieze
2005-04-20 7:36 ` Christian Parpart
2005-04-20 8:59 ` Paul de Vrieze
2005-04-20 15:25 ` Christian Parpart
2005-04-21 13:13 ` Paul de Vrieze
2005-04-20 12:14 ` Lance Albertson
2005-04-20 15:22 ` Christian Parpart
2005-04-20 15:35 ` Lance Albertson
2005-04-20 22:38 ` Donnie Berkholz
2005-04-16 13:18 ` Duncan [this message]
2005-04-20 16:39 ` Francesco Riosa
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=pan.2005.04.16.13.18.07.622107@cox.net \
--to=1i5t5.duncan@cox.net \
--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