public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Nathan Smith <ndansmith@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] OpenRC available for testing.
Date: Wed, 2 Jan 2008 20:38:17 -0800	[thread overview]
Message-ID: <20080102203817.39a258d7@gmail.com> (raw)
In-Reply-To: <1199191260.2786.9.camel@uberpc.marples.name>

On Tue, 01 Jan 2008 12:41:00 +0000
Roy Marples <roy@marples.name> wrote:

> Hi List
> 
> 2008 is here and it's time for some change!
> 
> OpenRC is now ready for testing. There are no ebuilds in the tree, but
> some are available here [1] that offers a baselayout-2 shell that
> pulls in openrc-9999. I'll just offer a git ebuild for the time
> being, so bugs can be fixed fast without having to bump all the time.
> But it should be fairly smooth going.

I am wondering about the blocker on baselayout < 2.0 in your git
overlay ebuild for baselayout-2.  Is there some reason that the upgrade
path from baselayout-1 to -2 will not work for openrc?

-- 
Nathan Smith
ndansmith@gmail.com
-- 
gentoo-dev@gentoo.org mailing list



  parent reply	other threads:[~2008-01-03  4:42 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-01 12:41 [gentoo-dev] OpenRC available for testing Roy Marples
2008-01-01 12:45 ` Roy Marples
2008-01-01 13:23   ` Alon Bar-Lev
2008-01-01 15:06     ` Petteri Räty
2008-01-01 16:55       ` Alon Bar-Lev
2008-01-01 17:11         ` Roy Marples
2008-01-01 17:22         ` Alon Bar-Lev
2008-01-01 17:48           ` Roy Marples
2008-01-03  6:43           ` Alon Bar-Lev
2008-01-03  9:46             ` Roy Marples
2008-01-03 10:02               ` Alon Bar-Lev
2008-01-03 10:09                 ` Roy Marples
2008-01-01 19:16 ` Thomas Pani
2008-01-01 19:31   ` TimeBreach
2008-01-01 19:49   ` Roy Marples
2008-01-02 14:39     ` Alon Bar-Lev
2008-01-02 15:05       ` Roy Marples
2008-01-02 15:15         ` Alon Bar-Lev
2008-01-02 15:50           ` Roy Marples
2008-01-03 15:49         ` Mike Frysinger
2008-01-03 18:19           ` Roy Marples
2008-01-06 13:34             ` [gentoo-dev] " Steve Long
2008-01-09 21:26             ` [gentoo-dev] " Mike Frysinger
2008-01-09 21:48               ` Chris Gianelloni
2008-01-09 22:58                 ` Mike Frysinger
2008-01-03 15:50     ` Mike Frysinger
2008-01-03 16:24       ` Roy Marples
2008-01-03 17:58         ` Roy Marples
2008-01-09 21:27           ` Mike Frysinger
2008-01-02 16:52 ` Santiago M. Mola
2008-01-02 17:39   ` Roy Marples
2008-01-03  4:38 ` Nathan Smith [this message]
2008-01-03  9:49   ` Roy Marples
     [not found] ` <9e0cf0bf0801030055u3564058fy7f9595d4df86674a@mail.gmail.com>
2008-01-03  8:58   ` Alon Bar-Lev
2008-01-03  9:50     ` Roy Marples
2008-01-03 10:13       ` Roy Marples
2008-01-03 10:18         ` Richard Brown
2008-01-03 10:40           ` Roy Marples
2008-01-03 12:12             ` Santiago M. Mola
2008-01-06 13:45               ` [gentoo-dev] " Steve Long
2008-01-03 14:01           ` [gentoo-dev] " Wulf C. Krueger
2008-01-09 21:30             ` Mike Frysinger
2008-01-03 23:35           ` Luca Barbato
2008-01-03 11:43       ` Alon Bar-Lev

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=20080102203817.39a258d7@gmail.com \
    --to=ndansmith@gmail.com \
    --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