From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] package/imagemagick: change download url to github
Date: Tue, 20 Jun 2017 14:40:14 +0200 [thread overview]
Message-ID: <871sqeg7dd.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20170620141021.5ecdcd3e@windsurf.lan> (Thomas Petazzoni's message of "Tue, 20 Jun 2017 14:10:21 +0200")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
Hi,
>> > I indeed hadn't seen the stupid name for the tarball. On my side, I
>> > find it a bit annoying that we have to rely on sources.b.o to make
>> > things work, so having upstream location that are working on the long
>> > run is much better when possible. But I agree that the tarball name is
>> > really silly here, and the risk of conflict with other packages is real.
>>
>> That is exactly my concern. So what do we do? Leave it like this so
>> s.b.o isn't needed or revert to get back a sane tarball name?
>>
>> There's pro/cons to both, but I think I would prefer to revert.
> Perhaps we could revert *and* talk to the upstream developers and ask
> them to keep the tarballs at the same place, instead of (re)moving
> them ?
That is certainly worth a try. It is imagemagick though, so you never
know. They seem to really remove all <version>-<minor> except the latest
<minor> in each series.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2017-06-20 12:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-18 7:45 [Buildroot] [PATCH 1/2] package/imagemagick: change download url to github Bernd Kuhls
2017-06-18 7:45 ` [Buildroot] [PATCH 2/2] package/imagemagick: bump version to 7.0.6-0 Bernd Kuhls
2017-06-18 13:53 ` [Buildroot] [PATCH 1/2] package/imagemagick: change download url to github Thomas Petazzoni
2017-06-18 19:13 ` Peter Korsgaard
2017-06-19 13:29 ` Thomas Petazzoni
2017-06-20 12:04 ` Peter Korsgaard
2017-06-20 12:10 ` Thomas Petazzoni
2017-06-20 12:40 ` Peter Korsgaard [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=871sqeg7dd.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox