From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] stunnel: bump to version 4.44
Date: Sun, 16 Oct 2011 19:39:37 +0200 [thread overview]
Message-ID: <4E9B16D9.2070200@free-electrons.com> (raw)
In-Reply-To: <2247f2bf1f89d0ba0b3eba6b94afe5d1@zacarias.com.ar>
On 16/10/2011 14:53, Gustavo Zacarias wrote:
> On 16.10.2011 05:47, Maxime Ripard wrote:
>
>> There's a problem with that. They have a kind of silly policy to
>> store the archives. In the "main" folder, there is only the latest
>> version, while every other version are in obsolete/4.x/. So this will
>> break as soon as a new version will be released, and that was why I
>> put obsolete in the first place.
>>
>> Maxime
>
> Yes, i've noticed, however they don't keep a copy of the latest version
> in obsolete.
> As long as it's mirrored in sources.buildroot.net it should be safe.
But do we really need the latest version here ?
Also, how the mirror is generated ? At each release or at a given
frequency ? Because, in the first case, if a new version is released
between this commit and the release, we're screwed.
> Maybe fallback/alternate download URLs could be implemented?
Indeed, that's a good idea.
--
Maxime Ripard, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2011-10-16 17:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-15 21:23 [Buildroot] [git commit] stunnel: bump to version 4.44 Peter Korsgaard
2011-10-16 8:47 ` Maxime Ripard
2011-10-16 12:53 ` Gustavo Zacarias
2011-10-16 17:39 ` Maxime Ripard [this message]
2011-10-18 7:04 ` Peter Korsgaard
2011-10-18 14:18 ` Gustavo Zacarias
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=4E9B16D9.2070200@free-electrons.com \
--to=maxime.ripard@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox