From: Robert Schuster <theBohemian@gmx.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: RFC: feature request - wrap sources
Date: Fri, 21 Dec 2007 11:24:48 +0100 [thread overview]
Message-ID: <476B9470.2020607@gmx.net> (raw)
In-Reply-To: <1198230789.4636.25.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1125 bytes --]
Richard Purdie schrieb:
> On Fri, 2007-12-21 at 09:34 +0100, Robert Schuster wrote:
>> I have a feature request that should help dealing with those source
>> tarballs which do not contain a proper top level directory. The idea is
>> to allow to add a parameter 'wrap' to the SRC_URI entry denoting the
>> source tarball. If it is present (and 1) the unpacker creates a
>> directory named ${P} and unpacks the tarball therein.
>>
>> This would make it unneccessary to change S for such packages and
>> furthermore the work directory is not cluttered with files and folders
>> from inside the source tarball.
>>
>> Like it? (Any pointer where such code should be put?)
>
> Would it not be simpler just to specify an attribute like unpacksubdir
> which you could set to ${PN}-${PV}?
Specifying the directory to be created would be nice. However one of my
idea was that by using such a mechanism S would be correct.
Would it be possible to automatically set S to ${WORKDIR}/<anything> if
unpacksubdir=<anything> is used? If so we could have genericity and
saving boilerplate code. :)
Regards
Robert
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2007-12-21 10:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-21 8:34 RFC: feature request - wrap sources Robert Schuster
2007-12-21 9:53 ` Richard Purdie
2007-12-21 10:24 ` Robert Schuster [this message]
2007-12-21 11:16 ` Paul Sokolovsky
2007-12-21 13:57 ` Richard Purdie
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=476B9470.2020607@gmx.net \
--to=thebohemian@gmx.net \
--cc=openembedded-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.