public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Kazantsev <mk.fraggod@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Migration to baselayout2 / openrc
Date: Sat, 10 Oct 2009 18:16:59 +0600	[thread overview]
Message-ID: <20091010181659.17f0af00@coercion> (raw)
In-Reply-To: <20091010100119.GA5805@solfire>

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

On Sat, 10 Oct 2009 12:01:19 +0200
meino.cramer@gmx.de wrote:

>  for this weekend I planned to migrate to baselayout 2
>  finally.
...
>  Especially "masked by: missing keyword" let me doubt whether 
>  or not it is sane to migrate....
> 
>  How to proceed here ?

I'd suggest to delay the update 'till it hits stable.

"Stable" and "testing" are different branches, after all, and if you
mix them, results should be pretty much unpredictable, since both are
tested as-is.
So any package in your ("stable") branch will have baselayout-1
compatible script running with openrc and baselayout-2 scripts, which
are _known_ to be incompatible in some cases.
Of course, hitting "stable" branch should mean that package spent some
time in "testing" and init-script has been modified to be compatible
with both branches, but still I doubt that the overal result should be
more stable than "testing" branch, since no-one has really tested your
particular package mix.

-- 
Mike Kazantsev // fraggod.net

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  parent reply	other threads:[~2009-10-10 12:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-10 10:01 [gentoo-user] Migration to baselayout2 / openrc meino.cramer
2009-10-10 10:55 ` Mick
2009-10-10 11:43 ` Alan McKinnon
2009-10-10 12:16 ` Mike Kazantsev [this message]
2009-10-12  5:33 ` Eray Aslan
2009-10-12  8:14   ` Dale
2009-10-12 12:41   ` Momesso Andrea
2009-10-14 12:34 ` daid kahl

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=20091010181659.17f0af00@coercion \
    --to=mk.fraggod@gmail.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