All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phil Blundell <pb@pbcl.net>
To: "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: File conflicts in DL_DIR
Date: Wed, 12 Oct 2016 18:01:05 +0100	[thread overview]
Message-ID: <1476291665.16008.59.camel@pbcl.net> (raw)

I just ran into an annoying problem with two recipes whose upstreams
both use the same poor naming scheme for their downloadable tarballs
which causes the sources to collide in DL_DIR.  One of them is eudev,
which has:

SRC_URI = "https://github.com/gentoo/${BPN}/archive/v${PV}.tar.gz

This shows up as a source checksum error when the second package finds
what it thinks are its sources in DL_DIR, but of course they are not
the files that it wanted.

I couldn't immediately find any easy way to work around this
difficulty.  Setting "localpath=eudev_v{$PV}.tar.gz" in eudev's SRC_URI
looks superficially like it ought to do the right thing, but although
this changes the location that the fetcher will search for the
downloaded file it doesn't actually cause wget to put the file there so
this doesn't work either.

I suppose I could define DL_DIR in terms of ${PN}, which would
presumably fix this problem at the cost of causing all my previous
downloads to be repeated.  Or I could stop using eudev, or wait for one
of the two packages to release a new version. :-)  Any better
suggestions?

thanks

p.



             reply	other threads:[~2016-10-12 17:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-12 17:01 Phil Blundell [this message]
2016-10-12 17:30 ` File conflicts in DL_DIR Martin Jansa
2016-10-12 19:11   ` Burton, Ross
2016-10-12 19:29     ` Martin Jansa
2016-10-12 17:45 ` Christopher Larson
2016-10-12 18:03 ` Matt Madison
2016-10-13 21:03   ` Phil Blundell

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=1476291665.16008.59.camel@pbcl.net \
    --to=pb@pbcl.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 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.