From: Sven Neumann <s.neumann@raumfeld.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] package infra: add mirror support
Date: Wed, 19 Oct 2011 10:12:39 +0200 [thread overview]
Message-ID: <1319011959.325.2.camel@sven> (raw)
In-Reply-To: <201110182339.00295.arnout@mind.be>
Hi,
On Tue, 2011-10-18 at 23:38 +0200, Arnout Vandecappelle wrote:
> > In a non-mandatory way it may be desirable.
> > That is if a package doesn't define it then we don't care.
> > Most of the time tarballs shouldn't change size & hash, though it
> > doesn't hold true for every project around.
>
> Size and hash should only change when you bump the version
Unfortunately it is not so uncommon for some projects to re-release with
the same version number if a bug sneaked into the released tarball. I
know that this should not be the case, but it happens every so often.
Not sure though what implications this has for the proposed buildroot
changes...
Regards,
Sven
next prev parent reply other threads:[~2011-10-19 8:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-18 14:14 [Buildroot] [PATCH 1/2] package infra: add mirror support Gustavo Zacarias
2011-10-18 14:14 ` [Buildroot] [PATCH 2/2] stunnel: add mirror site Gustavo Zacarias
2011-10-18 14:22 ` [Buildroot] [PATCH 1/2] package infra: add mirror support Thomas Petazzoni
2011-10-18 14:32 ` Thomas Petazzoni
2011-10-18 15:55 ` Michael S. Zick
2011-10-18 16:00 ` Gustavo Zacarias
2011-10-18 17:27 ` Thomas Petazzoni
2011-10-18 18:01 ` Gustavo Zacarias
2011-10-18 21:38 ` Arnout Vandecappelle
2011-10-19 8:11 ` [Buildroot] Adding hashes to package recipes Thomas Petazzoni
2011-10-19 8:12 ` Sven Neumann [this message]
2011-10-19 9:35 ` [Buildroot] [PATCH 1/2] package infra: add mirror support Arnout Vandecappelle
2011-10-19 12:59 ` Thomas Petazzoni
2011-10-19 16:37 ` Michael S. Zick
2011-10-19 16:59 ` Eric Bénard
2011-10-19 22:10 ` Arnout Vandecappelle
2011-10-18 16:02 ` Yann E. MORIN
2011-10-18 19:05 ` Arnout Vandecappelle
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=1319011959.325.2.camel@sven \
--to=s.neumann@raumfeld.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