From: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>
To: Jimi Damon <jdamon@gmail.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Proper way to rename a downloaded file in SRC_URI
Date: Tue, 18 Jul 2017 11:53:22 -0500 [thread overview]
Message-ID: <1500396802.2753.15.camel@linux.intel.com> (raw)
In-Reply-To: <a76f0673-66cb-6c0a-8b55-faedf0cc1821@gmail.com>
On Tue, 2017-07-18 at 09:40 -0700, Jimi Damon wrote:
> I have a recipe that I built for building jzmq, however one of the
> issues I have is with the naming of the release files from the github
> site.
>
> Unlike czmq which has downloads ( zip and tar.gz ) that are named
> czmq-${PV}.tar.gz, the downloads from jzmq are just called v
> ${PV}.tar.gz.
>
>
>
> How can I rename this file upon download so that the filename is in
> fact unique to this package ?
at the SRC_URI value, you may use the downloadfilename standard option.
http://www.yoctoproject.org/docs/2.3/mega-manual/mega-manual.html#var-SRC_URI
>
>
> I can definitely see that the file v3.1.0.tar.gz in my downloads
> directory is not unique and could conflict with another package that
> is similarly named for its releases.
>
>
> My workaround right now is to use the specific SHA string and use the
> git:// protocol, but it would be a bit easier to just use the released
> version and change the filename for saving it in downloads.
>
>
>
>
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
prev parent reply other threads:[~2017-07-18 16:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-18 16:40 Proper way to rename a downloaded file in SRC_URI Jimi Damon
2017-07-18 16:47 ` Paul Eggleton
2017-07-18 16:53 ` Leonardo Sandoval [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=1500396802.2753.15.camel@linux.intel.com \
--to=leonardo.sandoval.gonzalez@linux.intel.com \
--cc=jdamon@gmail.com \
--cc=yocto@yoctoproject.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.