From: Trevor Woerner <twoerner@gmail.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] babeltrace: switch source URI
Date: Mon, 7 May 2018 11:48:45 -0400 [thread overview]
Message-ID: <20180507154845.GA17081@linux-uys3> (raw)
In-Reply-To: <CA+chaQfbViBTpaV3rOXd1Q9NBnViSLAjb-obywEi7y1rpJAz5w@mail.gmail.com>
Hi Martin,
On Mon 2018-05-07 @ 05:33:26 PM, Martin Jansa wrote:
> There is already a fix for this, see:
> http://lists.openembedded.org/pipermail/openembedded-core/2018-May/150423.html
Oops, I should have checked, sorry!
> Using github archives is even worse as they are regenerated from time to
> time.
Crazy! But good to know.
> Also when you really want to use v${PV}.tar.gz archive, then
> use downloadfilename parameter to fetch it with some more meaningful
> filename and to prevent possible conflicts with other badly named tarballs.
Oh, I see, in one's own DL_DIR. So (not that this patch is relevant anymore)
instead of:
-SRC_URI = "http://www.efficios.com/files/babeltrace/babeltrace-${PV}.tar.bz2 \
-"
+SRC_URI = "https://github.com/efficios/babeltrace/archive/v${PV}.tar.gz"
better:
-SRC_URI = "http://www.efficios.com/files/babeltrace/babeltrace-${PV}.tar.bz2 \
-"
+SRC_URI = "https://github.com/efficios/babeltrace/archive/v${PV}.tar.gz;downloadfilename=babeltrace-v${PV}.tar.gz"
In this case, would the checksums need a tweak too, or do they know to look
for the downloadfilename file name?
next prev parent reply other threads:[~2018-05-07 15:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-07 15:27 [PATCH] babeltrace: switch source URI Trevor Woerner
2018-05-07 15:33 ` Martin Jansa
2018-05-07 15:48 ` Trevor Woerner [this message]
2018-05-07 18:36 ` Martin Jansa
2018-05-08 9:38 ` Burton, Ross
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=20180507154845.GA17081@linux-uys3 \
--to=twoerner@gmail.com \
--cc=martin.jansa@gmail.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 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.