From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Koen Kooi <koen@dominion.thruhere.net>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] Revert "kmod: Use base_libdir for installing libkmod"
Date: Thu, 17 May 2012 22:02:43 +0100 [thread overview]
Message-ID: <1337288563.7473.24.camel@ted> (raw)
In-Reply-To: <0FEE2025-8E84-4CBB-8568-483A55233BD7@dominion.thruhere.net>
On Thu, 2012-05-17 at 22:44 +0200, Koen Kooi wrote:
> Op 17 mei 2012 om 22:29 heeft Richard Purdie <richard.purdie@linuxfoundation.org> het volgende geschreven:
>
> > On Tue, 2012-05-15 at 13:54 -0700, Khem Raj wrote:
> >> On Tue, May 15, 2012 at 2:32 AM, Koen Kooi <koen@dominion.thruhere.net> wrote:
> >>> The commit breaks pkgconfig and after discussing it with the kmod and udev maintainers the conclusion was reached that putting the libraries in /lib instead of /usr/lib is not supported.
> >>>
> >>> This reverts commit 6b74f2461735272bd950a4f060dab6e778a36f92.
> >>
> >> while this is what I had initially it doesn't go well with kmod living in
> >> /sbin and accessing libraries from /usr due to our QA checks although
> >> I am all for simplifying it where we don't make this check at all.
> >
> > I've had requests for it along with a commitment to fix it and patches.
> > If we decide we don't want this, fine and that will be the case if
> > patches are not forthcoming to fix the QA issues. I don't think we've
> > reached that point at this with that yet.
> >
> > I've decided to accept this patch and "unbreak" meta-oe/udev at the
> > expense of screwing up OE-Core. I am however still deeply unhappy people
> > are trying to bypass OE-Core this way and then "blackmail" OE-Core using
> > breaking meta-oe as a reason. The whole systemd thing has been badly
> > handled and needs to get fixed properly.
>
> What does systemd have to do with this?
Why does meta-oe has its own udev recipe? Is systemd related to that at
all?
> This is about a broken commit breaking udev 182 for over a week.
OE-Core worked fine and the commit fixes QA warnings which are now back.
> If you have issues with systemd, send patches to meta-oe to fix it. Or
> at least bug reports that are more than the insinuations above.
I looked in the README and followed that to other README files but
couldn't find any indication about what to do with bugs other than write
patches which I obviously don't have.
When will you be sending the patch to fix the QA warning your revert has
introduced? Yes this is a rhetorical question since I've seen your view
on this problem previously.
Cheers,
Richard
next prev parent reply other threads:[~2012-05-17 21:13 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-15 9:32 [PATCH] Revert "kmod: Use base_libdir for installing libkmod" Koen Kooi
2012-05-15 20:54 ` Khem Raj
2012-05-17 20:29 ` Richard Purdie
2012-05-17 20:44 ` Koen Kooi
2012-05-17 21:02 ` Richard Purdie [this message]
2012-05-17 21:16 ` Tom Rini
2012-05-17 21:25 ` Paul Eggleton
2012-05-17 21:51 ` Otavio Salvador
2012-05-17 22:01 ` Paul Eggleton
2012-05-17 22:11 ` Otavio Salvador
2012-05-17 22:21 ` Paul Eggleton
2012-05-17 22:22 ` Phil Blundell
2012-05-17 22:50 ` Khem Raj
2012-05-17 23:00 ` Andreas Müller
2012-05-18 6:19 ` Koen Kooi
2012-05-18 8:16 ` Koen Kooi
2012-05-18 7:52 ` Koen Kooi
2012-05-18 10:29 ` Richard Purdie
2012-05-18 10:37 ` Koen Kooi
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=1337288563.7473.24.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=koen@dominion.thruhere.net \
--cc=openembedded-core@lists.openembedded.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