From: William Hubbs <williamh@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: Samuli Suominen <ssuominen@gentoo.org>
Subject: Re: [gentoo-dev] new eclass: systemd-next.eclass
Date: Sat, 13 Apr 2013 15:57:07 -0500 [thread overview]
Message-ID: <20130413205707.GA31433@linux1> (raw)
In-Reply-To: <CAGfcS_kf9yGzaiPEKmHPMiqmrMgnsU2W=+PUjaasdaTdbA08WA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1130 bytes --]
On Sat, Apr 13, 2013 at 04:15:03PM -0400, Rich Freeman wrote:
> On Sat, Apr 13, 2013 at 3:43 PM, William Hubbs <williamh@gentoo.org> wrote:
> > I am sending this out for review so we can commit it to the tree
> > when we commit our alternate systemd ebuild in a few days. This will be
> > set up so that users can choose which systemd package they want to
> > install, and it will default to the current systemd package.
>
> Did I miss some kind of announcement for what is going on here? An
> additional implementation in portage along with an eclass probably is
> worth some kind of intro on-list. I don't think you need to seek
> approval/etc, but it would be nice to know what your goals/etc are.
> Is this just a different installation/configuration approach, or is
> this some kind of upstream fork?
It is not an upstream fork, it is a configuration/installation
approach that follows upstream's recommendations for install locations.
It also allows the user more choices wrt which parts of systemd are
built or installed and allows more fine-grained use dependencies for
other packages.
William
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2013-04-13 20:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-13 19:43 [gentoo-dev] new eclass: systemd-next.eclass William Hubbs
2013-04-13 20:15 ` Rich Freeman
2013-04-13 20:41 ` Diego Elio Pettenò
2013-04-13 20:57 ` William Hubbs [this message]
2013-04-13 21:22 ` Rich Freeman
2013-04-13 21:27 ` Michał Górny
2013-04-13 21:30 ` William Hubbs
2013-04-13 23:41 ` Markos Chandras
2013-04-14 0:49 ` William Hubbs
2013-04-14 5:47 ` Michał Górny
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=20130413205707.GA31433@linux1 \
--to=williamh@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=ssuominen@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