From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH] bin_package.bbclass: emphasize setting of S with "subdir"
Date: Sat, 04 Apr 2020 14:18:08 +0100 [thread overview]
Message-ID: <5f1c53fb3f52a4d124bf9a8bf646639b6edfccb8.camel@linuxfoundation.org> (raw)
In-Reply-To: <alpine.LFD.2.21.2004040856460.14065@localhost.localdomain>
On Sat, 2020-04-04 at 09:01 -0400, Robert P. J. Day wrote:
> On Sat, 4 Apr 2020, Richard Purdie wrote:
>
> > On Sat, 2020-04-04 at 08:00 -0400, rpjday@crashcourse.ca wrote:
> > > Clarify the setting of "S" so there is absolutely no confusion.
> > >
> > > Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>
> > >
> > > ---
> > >
> > > diff --git a/meta/classes/bin_package.bbclass
> > > b/meta/classes/bin_package.bbclass
> > > index cbc9b1fa13..4e74557967 100644
> > > --- a/meta/classes/bin_package.bbclass
> > > +++ b/meta/classes/bin_package.bbclass
> > > @@ -14,8 +14,8 @@
> > > #
> > > # SRC_URI = "http://foo.com/foo-1.0-r1.i586.rpm;subdir=foo-1.0"
> > > #
> > > -# Then the files would be unpacked to ${WORKDIR}/foo-1.0,
> > > otherwise
> > > -# they would be in ${WORKDIR}.
> > > +# Then the files would be unpacked to S=${WORKDIR}/foo-1.0,
> > > otherwise
> > > +# they would be in S=${WORKDIR}.
> > > #
> >
> > I strongly disagree actually. Setting subdir in SRC_URI does not
> > change
> > the value of S. What happens is what the comment says, its unpacked
> > to
> > ${WORKDIR}/foo-1.0, or ${WORKDIR}. The value of S remains at
> > whatever
> > its set to.
>
> so if one inherits bin_package and uses a "subdir" option, what is
> installed (via tar) is the entire subdir directory structure, as in
>
> foo-1.0/*
That sounds more confusing.
The source component of SRC_URI that has subdir set against it is
extracted to ${WORKDIR}/<subdir> rather than ${WORKDIR}/. Nothing more,
nothing less.
> unless the recipe explicitly sets S to match it, is that it? that
> might be worth noting in the comments, then.
S has nothing to do with this so stop trying to include it.
Cheers,
Richard
next prev parent reply other threads:[~2020-04-04 13:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-04 12:00 [PATCH] bin_package.bbclass: emphasize setting of S with "subdir" rpjday
2020-04-04 12:49 ` [OE-core] " Richard Purdie
2020-04-04 12:52 ` rpjday
2020-04-04 13:01 ` rpjday
2020-04-04 13:18 ` Richard Purdie [this message]
2020-04-04 13:29 ` rpjday
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=5f1c53fb3f52a4d124bf9a8bf646639b6edfccb8.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=rpjday@crashcourse.ca \
/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