From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/cdrkit: standardize site URL
Date: Wed, 22 Oct 2014 15:22:31 +0200 [thread overview]
Message-ID: <20141022152231.1ecdf27a@free-electrons.com> (raw)
In-Reply-To: <1413983659-3496-1-git-send-email-kaszak@gmail.com>
Dear Karoly Kasza,
On Wed, 22 Oct 2014 15:14:19 +0200, Karoly Kasza wrote:
> Standardize download site URL using the Debian mirror.
>
> Signed-off-by: Karoly Kasza <kaszak@gmail.com>
> ---
> package/cdrkit/cdrkit.mk | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/package/cdrkit/cdrkit.mk b/package/cdrkit/cdrkit.mk
> index 3f2b429..e1392b6 100644
> --- a/package/cdrkit/cdrkit.mk
> +++ b/package/cdrkit/cdrkit.mk
> @@ -6,7 +6,7 @@
>
> CDRKIT_VERSION = 1.1.11
> CDRKIT_SOURCE = cdrkit_$(CDRKIT_VERSION).orig.tar.gz
> -CDRKIT_SITE = http://snapshot.debian.org/archive/debian/20101018T151929Z/pool/main/c/cdrkit/
> +CDRKIT_SITE = $(BR2_DEBIAN_MIRROR)/debian/pool/main/c/cdrkit
> CDRKIT_DEPENDENCIES = libcap bzip2 zlib
> CDRKIT_LICENSE = GPLv2
> CDRKIT_LICENSE_FILES = COPYING
Yeah, well, actually, I believe using snapshot.debian.org is a better
idea, since it guarantees that files won't be moved. While using
$(BR2_DEBIAN_MIRROR) means that we point to locations where tarballs
will disappear at some point. At least, we've seen that in the past.
So maybe we should rather get rid of BR2_DEBIAN_MIRROR and make sure
all packages downloading their source from Debian use
snapshot.debian.org instead.
Thoughts?
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-10-22 13:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-22 13:14 [Buildroot] [PATCH 1/1] package/cdrkit: standardize site URL Karoly Kasza
2014-10-22 13:22 ` Thomas Petazzoni [this message]
2014-10-22 15:09 ` Károly Kasza
2014-10-22 15:22 ` Thomas Petazzoni
2014-10-22 16:45 ` Arnout Vandecappelle
2014-10-23 7:50 ` Thomas Petazzoni
2014-10-23 7:51 ` Károly Kasza
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=20141022152231.1ecdf27a@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--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.