public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev]  Re: Baselayout-2 progress?
Date: Sat, 1 Mar 2008 09:49:57 +0000 (UTC)	[thread overview]
Message-ID: <pan.2008.03.01.09.49.57@cox.net> (raw)
In-Reply-To: 47C8E29A.2020003@gentoo.org

Doug Klima <cardoe@gentoo.org> posted 47C8E29A.2020003@gentoo.org,
excerpted below, on  Fri, 29 Feb 2008 23:59:06 -0500:

>> Is direct upgrade from previous baselayout-2.0.0-rcX going to be
>> supported?  I was running that for some time and just now added and
>> upgraded to the via layman version.  There's a blocker, of course, as
>> openrc is now providing most of the files that baselayout did.
> 
> You just answered your own question. If another package now provides
> files that an existing package provides, they must be blockers.

Thus the "of course"...

> Considering baselayout-2.0.0_rcX was a masked version and never
> recommended, it's also not in the direct upgrade path. The proper
> upgrade is what you've detailed out below. Such are the risks when you
> unmask a package and install it on your machine.

Which is why I'm not particularly complaining, just asking.

Practically speaking, while it's not required by any means, some devs 
choose to acknowledge the symbiotic relationship between pre-release 
testers willing to take that risk and do the work to find and file bugs, 
thus helping to make the general release far less buggy, and the devs who 
depend on such testers for that function.  The testers do a favor for the 
devs with all that early testing and bug filing (sometimes with patches), 
and many devs choose to return it by providing a working upgrade path 
from the pre-releases to the general release.  Among other things, it 
makes for happier testers, who are then likely to be repeat testers, the 
next time an upgrade comes along.

It's also worth mentioning that a call for testers went out, so it's not 
as if those that answered it, particularly if the DID actively look for 
and file bugs as they found them, were doing it entirely of their own 
accord.  Again, it's doing the developer a favor, so it's a nice gesture 
if the developer chooses to return the favor by smoothing the upgrade 
path.  Not something he has to do, but something he /can/ do, to increase 
the chances of folks who already know the process again taking him up on 
the invitation, the next time he needs something tested. =8^)

So anyway, I thought it was worth asking about, in case it had slipped 
his mind or he hadn't thought of it.  No big deal either way, but it'd be 
a nice gesture if it's not too difficult to setup.

-- 
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

-- 
gentoo-dev@lists.gentoo.org mailing list



  parent reply	other threads:[~2008-03-01  9:50 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-29 14:12 [gentoo-dev] Baselayout-2 progress? Ed W
2008-02-29 14:16 ` Alon Bar-Lev
2008-02-29 15:56   ` Ed W
2008-02-29 16:02     ` Doug Klima
2008-02-29 16:15       ` Ed W
2008-02-29 16:30         ` Doug Klima
2008-02-29 17:07         ` Roy Marples
2008-02-29 18:32           ` Stefan Hellermann
2008-02-29 19:45             ` Roy Marples
2008-02-29 19:57               ` Stefan Hellermann
2008-02-29 20:15                 ` Doug Klima
2008-02-29 20:31                   ` Stefan Hellermann
2008-02-29 23:17                     ` Ed Wildgoose
2008-03-01  2:08           ` [gentoo-dev] " Duncan
2008-03-01  4:59             ` Doug Klima
2008-03-01  5:04               ` [gentoo-dev] Re: Blockers (was: Baselayout-2 progress?) Ciaran McCreesh
2008-03-01  9:49               ` Duncan [this message]
2008-03-01 10:50             ` [gentoo-dev] Re: Baselayout-2 progress? Roy Marles
2008-03-01 19:17               ` Duncan
2008-03-01 22:50           ` [gentoo-dev] " Bernd Steinhauser
2008-03-01 23:42             ` [gentoo-dev] " Duncan
2008-03-02  0:55               ` Bernd Steinhauser
2008-02-29 17:01     ` [gentoo-dev] " Roy Marples
2008-02-29 17:50       ` Benedikt Bšoehm
2008-02-29 23:19         ` Ed Wildgoose
2008-02-29 23:23       ` Ed Wildgoose
2008-03-01  0:56         ` Roy Marples
2008-03-01 22:26           ` Ed W
2008-03-01 22:29             ` Roy Marples
     [not found] <a2efU-75I-37@gated-at.bofh.it>
     [not found] ` <a2fYm-1sf-27@gated-at.bofh.it>
     [not found]   ` <a2g80-1Ez-25@gated-at.bofh.it>
     [not found]     ` <a2gUx-2Ys-43@gated-at.bofh.it>
     [not found]       ` <a2IQE-4Hb-9@gated-at.bofh.it>
     [not found]         ` <a2JCW-5X9-17@gated-at.bofh.it>
     [not found]           ` <a2KIK-7AU-9@gated-at.bofh.it>
2008-03-02 15:12             ` [gentoo-dev] " Vaeth

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.2008.03.01.09.49.57@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