From: William Hubbs <williamh@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] new eclass: systemd-next.eclass
Date: Sat, 13 Apr 2013 16:30:36 -0500 [thread overview]
Message-ID: <20130413213036.GA31703@linux1> (raw)
In-Reply-To: <20130413232724.07c19b9a@pomiocik.lan>
[-- Attachment #1: Type: text/plain, Size: 974 bytes --]
On Sat, Apr 13, 2013 at 11:27:24PM +0200, Michał Górny wrote:
> On Sat, 13 Apr 2013 14:43:14 -0500
> William Hubbs <williamh@gentoo.org> wrote:
>
> > this eclass is an alternative to systemd.eclass, and maintains
> > full compatibility with it; however, it expands it so that it can query
> > pkgconfig for the directory paths. It returns the same default paths as
> > systemd.eclass if there is an error with pkgconfig.
>
> Alternative? So now developers decide whether they want support systemd
> A or systemd B? And we fork packages so that users can have matching
> set of packages?
>
> If you listened, you would know that the only reason I didn't apply
> your patches to the eclass was that nothing used them. If you really
> want to commit your quasi-fork, I will update the eclass. You
> don't really have to play silly games like this.
Ok, that is the better aproach anyway, go ahead and update the eclass.
Thanks much. :-)
William
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2013-04-13 21:30 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
2013-04-13 21:22 ` Rich Freeman
2013-04-13 21:27 ` Michał Górny
2013-04-13 21:30 ` William Hubbs [this message]
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=20130413213036.GA31703@linux1 \
--to=williamh@gentoo.org \
--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