From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Chris Larson <clarson@kergoth.com>, dvhart@linux.intel.com
Subject: Re: [PATCH 06/10] quilt: move empty quiltrc to native
Date: Fri, 20 Apr 2012 10:50:49 +0100 [thread overview]
Message-ID: <1334915449.3028.35.camel@ted> (raw)
In-Reply-To: <4F9100E0.4090200@linux.intel.com>
On Thu, 2012-04-19 at 23:23 -0700, Saul Wold wrote:
> On 04/19/2012 09:17 PM, Chris Larson wrote:
> > On Thu, Apr 19, 2012 at 3:44 PM, Saul Wold<sgw@linux.intel.com> wrote:
> >> The package.bbclass uses the native sysroot /usr/bin/quiltrc as an empty quiltrc
> >> to ensure that the user quiltrc does not affect our patching scheme. This ensures
> >> the correct file is in the correct sysroot.
> >
> > I assume this was meant to be patch.bbclass? Aside: ${bindir} really
> > isn't where that should go, as a point for future improvement :)
> Yes, patch.bbclass references $STAGING_NATIVE_BINDIR (I think that's
> it), Yeah, I thought about moving it, which I could still do in a second
> patch to the native sysroot /etc or /usr/share/quilt, this might be the
> better place.
>
> Thoughts?
I suspect that was a workaround where quilt was picking up things it
shouldn't on a system and we needed a quiltrc file but didn't stage
sysconfdir. I think we do stage sysconfdir for native packages now and
the fact it was using /usr is just historical detail which can be
removed.
Looking at the history, we added sysconfdir 2.5 years ago in:
http://git.yoctoproject.org/cgit.cgi/poky/commit/meta/classes/base.bbclass?id=dfd32b429a0a9bed09b75f59f0c7fb37f42c3ed9
The quiltrc fix was from two years before that:
http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=95554ee9b15e575a369d9686be6af45d3a6985fc
http://git.yoctoproject.org/cgit.cgi/poky/commit/meta/classes/patch.bbclass?id=0443d80b50e98bb329e30430bde5db67f09004e3
Regardless, lets just have one patch which moves this somewhere sensible
and makes it quilt-native only.
Cheers,
Richard
next prev parent reply other threads:[~2012-04-20 10:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-19 22:44 [PATCH 00/10] Updates and Packaging fixes Saul Wold
2012-04-19 22:44 ` [PATCH 01/10] binutils: add embedspu for ppc builds Saul Wold
2012-04-19 22:44 ` [PATCH 02/10] libgcc: Package additional *crt*.o files for PPC Saul Wold
2012-04-19 22:44 ` [PATCH 03/10] xserver-kdrive: Add xkb to existing docs list Saul Wold
2012-04-19 22:44 ` [PATCH 04/10] kernel: Fix packaging issue Saul Wold
2012-04-19 22:56 ` Darren Hart
2012-04-19 22:58 ` Saul Wold
2012-04-19 22:44 ` [PATCH 05/10] gcc: Add plugins package for ARM, fix /usr/incude packaging Saul Wold
2012-04-19 22:44 ` [PATCH 06/10] quilt: move empty quiltrc to native Saul Wold
2012-04-20 4:17 ` Chris Larson
2012-04-20 6:23 ` Saul Wold
2012-04-20 9:50 ` Richard Purdie [this message]
2012-04-19 22:44 ` [PATCH 07/10] sysstat: Upgrade to 10.0.3 Saul Wold
2012-04-19 22:44 ` [PATCH 08/10] lame: Upgrade to 3.99.5 Saul Wold
2012-04-19 22:44 ` [PATCH 09/10] sqlite3: Upgrade to 3.7.11 Saul Wold
2012-04-19 22:44 ` [PATCH 10/10] distro_tracking: Update Manual Check Saul Wold
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=1334915449.3028.35.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=clarson@kergoth.com \
--cc=dvhart@linux.intel.com \
--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