Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Graeme Gregory <dp@xora.org.uk>
To: openembedded-devel@lists.openembedded.org
Subject: Re: RFC: allow subdir for SRC_URI entries
Date: Tue, 13 Jan 2009 14:35:58 +0000	[thread overview]
Message-ID: <496CA6CE.4070607@xora.org.uk> (raw)
In-Reply-To: <gki5if$jm$1@ger.gmane.org>

Koen Kooi wrote:
> On 13-01-09 14:18, Robert Schuster wrote:
>> Hi folks,
>> I desperately need this patch. ;)
>>
>> It allows one to specify ";subdir=<DIR>" in SRC_URI entries. Having the
>> effect that the respective file is either unpacked or copied into that
>> very directory which is treated as:
>>
>> ${WORKDIR}/<DIR>
>>
>> It is not really ${WORKDIR} but the cwd when do_unpack is run. In most
>> cases this is ${WORKDIR}. If it is something else the recipe writer will
>> have a reason for that.
>>
>> With this patch we can finally deal easily with tarbombs.
>
> I have another use case:
>
> Multiple git:// uris in SRC_URI.
>
> When building ffmpeg from git you need to checkout libswscale from git
> as well and move it in ${S}, which breaks since *every* git repo is
> put in WORKDIR/git
>
> While speaking about the git fetcher:
>
> foo_2.0+git.bb: git://foo/bar;branch=pm
> foo_2.1+git.bb: git://foo/bar;branch=master
>
> That will trigger a russian roulette which branch it's going to fetch
> or unpack, you can end up with 2.1+git trying to checkout the pm branch.
For this maybe we should make name= format used when we use
SRCREV_FORMAT more generic?

Graeme




      reply	other threads:[~2009-01-13 14:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-13 13:18 RFC: allow subdir for SRC_URI entries Robert Schuster
2009-01-13 13:39 ` Koen Kooi
2009-01-13 14:35   ` Graeme Gregory [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=496CA6CE.4070607@xora.org.uk \
    --to=dp@xora.org.uk \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox