Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] package/libva: Bump version to 1.4.0
Date: Tue, 07 Oct 2014 23:12:03 +0200	[thread overview]
Message-ID: <878ukrfuu4.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20141007210631.GA27580@free.fr> (Yann E. MORIN's message of "Tue, 7 Oct 2014 23:06:31 +0200")

>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:

Hi,

 > ... there are a few other good reasons we accept hashes:

 >   - it ensures a broken download is detected, so the user quickly knows
 >     that the tarball is broken because of the download; sometimes,
 >     upstreams breaks their distributions (e.g. the recent sourceforge
 >     breakage...).

 >   - non-compliant downloads are removed (rm -f) so they are not
 >     accidentally used in another context (e.g. I do share my BR2_DL_DIR
 >     with other stuff).

 >   - consequently, it helps the autobuilders prune their failed
 >     downloads.

 > But in the end there is no clear policy, except:

 >   - we *do* want hashes for security-related packages;
 >   - hashes for other packages are a nice bonus.

Agreed. It is in no way required, but nice - Especially if upstream
posts hashes.

-- 
Bye, Peter Korsgaard

      reply	other threads:[~2014-10-07 21:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-06 19:28 [Buildroot] [PATCH 1/3] package/libva: Bump version to 1.4.0 Bernd Kuhls
2014-10-06 19:28 ` [Buildroot] [PATCH 2/3] package/libva-intel-driver: " Bernd Kuhls
2014-10-06 19:28 ` [Buildroot] [PATCH 3/3] package/ffmpeg: Bump version to 2.4.2 Bernd Kuhls
2014-10-07 20:32 ` [Buildroot] [PATCH 1/3] package/libva: Bump version to 1.4.0 Peter Korsgaard
2014-10-07 20:58   ` Bernd Kuhls
2014-10-07 21:06     ` Yann E. MORIN
2014-10-07 21:12       ` 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=878ukrfuu4.fsf@dell.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --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