public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: William Hubbs <williamh@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: systemd@gentoo.org, ssuominen@gentoo.org
Subject: Re: [gentoo-dev] rfc: patch systemd.eclass to use pkg-config if available
Date: Mon, 11 Mar 2013 18:05:21 -0500	[thread overview]
Message-ID: <20130311230521.GA20614@linux1> (raw)
In-Reply-To: <20130311234747.6c046150@pomiocik.lan>

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

On Mon, Mar 11, 2013 at 11:47:47PM +0100, Michał Górny wrote:
> On Mon, 11 Mar 2013 17:28:08 -0500
> William Hubbs <williamh@gentoo.org> wrote:
> 
> > On Mon, Mar 11, 2013 at 05:37:12PM -0400, Mike Gilbert wrote:
> > > On Mon, Mar 11, 2013 at 5:18 PM, William Hubbs <williamh@gentoo.org> wrote:
> > > > All,
> > > >
> > > > systemd, like udev, stores directory paths in a way that they can be
> > > > queried from pkg-config. However, the systemd.eclass currently does not
> > > > use this ability.
> > > >
> > > > The following patch models the systemd eclass after the udev eclass and
> > > > leaves the current defaults in place if there is an issue with
> > > > pkg-config.
> > > >
> > > > Any thoughts?
> > > >
> > > > William
> > > >
> > > 
> > > What problem are you trying to solve here?
> > > 
> > > We already know the values that pkg-config will return, so I fail to
> > > see the advantage of calling pkg-config in the eclass.
> > > 
> > > If we were to move the /usr/lib/systemd directory between two versions
> > > of systemd, then yes, using pkg-config would be helpful. Until/unless
> > > such a change occurs, I just don't see the point.
> > 
> > The reason for this is a topic that Samuli and I want to discuss with
> > the systemd team, probably on irc, but, basically, since gentoo does not
> > have the /usr merge, we think parts of systemd which are in /usr
> > should go in /, and this goes along with systemd upstream's recommendations
> > as well (look at how the autogen.sh script in the systemd git repo works
> > to see what I'm talking about).
> > 
> > This would also allow udev and systemd to share the /lib/systemd
> > directory, and we could install compatibility symlinks where necessary
> > to not break users' systems.
> 
> No. And I don't have the time to repeat that discussion again. Just no.

This was also the extent of your objections when I did bring it up to
you informally before. It would really help if you would explain your
position.

Thanks,

William


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

      reply	other threads:[~2013-03-11 23:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-11 21:18 [gentoo-dev] rfc: patch systemd.eclass to use pkg-config if available William Hubbs
2013-03-11 21:37 ` Mike Gilbert
2013-03-11 22:28   ` William Hubbs
2013-03-11 22:47     ` Michał Górny
2013-03-11 23:05       ` William Hubbs [this message]

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=20130311230521.GA20614@linux1 \
    --to=williamh@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=ssuominen@gentoo.org \
    --cc=systemd@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