From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/4] pkg-infra: differentiate remote and local tarball filenames (branch yem/download)
Date: Sun, 23 Nov 2014 18:25:18 +0100 [thread overview]
Message-ID: <20141123172518.GD11143@free.fr> (raw)
In-Reply-To: <20141118220357.74bc954c@free-electrons.com>
Thomas, All,
On 2014-11-18 22:03 +0100, Thomas Petazzoni spake thusly:
> Dear Arnout Vandecappelle,
>
> On Tue, 18 Nov 2014 21:38:58 +0100, Arnout Vandecappelle wrote:
>
> > I think there are two reasons for the split:
> >
> > 1. _SOURCE can be dropped if it is <pkg>-<version>.tar.gz - this would be
> > difficult if we only had _SITE.
>
> True. But on the other hand, the fact that we use
> <pkg>-<version>.tar.gz by default has always confused newcomers a bit,
> and with .tar.xz becoming more and more adopted, having .tar.gz as the
> default is less obvious than it used to be.
>
> > 2. _PATH and _EXTRA_DOWNLOAD don't need to specify the full URL.
>
> Well, yes, but that's specifically the issue I raised: since you don't
> specify the full URL, there's no way for the package to download
> patches or other stuff from other places than <pkg>_SITE.
Well, I still find the split worthwhile.
Still, we could allow FOO_EXTRA_DOWNLOADS and FOO_PATCH to be
fully-qualified URIs. If they are not, prepend FOO_SITE to generate a
full URI.
Yes, I am writing a package that will download most of its files via
_EXTRA_DOWNLOADS (don't ask why, upstream is not doing release tarballs
for that component), and it would be *very* cumbersome to repeat the
_SITE for all of those files.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
prev parent reply other threads:[~2014-11-23 17:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-15 16:19 [Buildroot] [PATCH 0/4] pkg-infra: differentiate remote and local tarball filenames (branch yem/download) Yann E. MORIN
2014-11-15 16:19 ` [Buildroot] [PATCH 1/4] pkg-infra: always specify the local tarball name when calling DOWNLOAD Yann E. MORIN
2014-11-18 20:41 ` Arnout Vandecappelle
2014-11-23 17:02 ` Yann E. MORIN
2014-11-15 16:19 ` [Buildroot] [PATCH 2/4] pkg-infra: squash DOWNLOAD_INNER into DOWNLOAD Yann E. MORIN
2014-11-15 16:19 ` [Buildroot] [PATCH 3/4] pkg-infra: differentiate remote tarball name from local filename Yann E. MORIN
2014-11-18 20:54 ` Arnout Vandecappelle
2014-11-23 17:06 ` Yann E. MORIN
2014-11-23 17:18 ` Yann E. MORIN
2014-11-15 16:19 ` [Buildroot] [PATCH 4/4] docs/manual: document the new variable FOO_UPSTREAM_SOURCE Yann E. MORIN
2014-11-16 6:19 ` Baruch Siach
2014-11-16 22:13 ` Yann E. MORIN
2014-11-16 11:22 ` [Buildroot] [PATCH 0/4] pkg-infra: differentiate remote and local tarball filenames (branch yem/download) Thomas Petazzoni
2014-11-18 20:38 ` Arnout Vandecappelle
2014-11-18 21:03 ` Thomas Petazzoni
2014-11-18 21:50 ` Arnout Vandecappelle
2014-11-23 17:25 ` Yann E. MORIN [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=20141123172518.GD11143@free.fr \
--to=yann.morin.1998@free.fr \
--cc=buildroot@busybox.net \
/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.