From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] support/download/svn: generate reproducible svn archives
Date: Mon, 23 Dec 2019 23:19:46 +0100 [thread overview]
Message-ID: <20191223231946.3f57ebe1@windsurf> (raw)
In-Reply-To: <87zhfiu28h.fsf@dell.be.48ers.dk>
Hello,
+Alex in Cc. Alex, there's an open2300 question for you below.
On Mon, 23 Dec 2019 23:05:34 +0100
Peter Korsgaard <peter@korsgaard.com> wrote:
> > In practice, we have only two: fis and open2300. The other packages that
> > may use svn are those where the user would set the version, so they
> > would anyway be excluded from the hash check.
>
> Talking about those two packages, weren't we going to remove them? They
> are both very old and haven't been updated since they were added.
That's indeed another way. For the "fis" package, I think this is
reasonable, as even the use-case is very obsolete (RedBoot stuff). For
open2300, I'm not sure.
Alex: is open2300 still relevant today? You introduced this package in
Buildroot many years ago.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-12-23 22:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-22 21:31 [Buildroot] [PATCH] support/download/svn: generate reproducible svn archives Heiko Thiery
2019-12-22 21:36 ` Thomas Petazzoni
2019-12-22 21:40 ` Heiko Thiery
2019-12-22 21:54 ` Heiko Thiery
2019-12-22 21:57 ` Thomas Petazzoni
2019-12-23 17:16 ` Yann E. MORIN
2019-12-23 22:05 ` Peter Korsgaard
2019-12-23 22:19 ` Thomas Petazzoni [this message]
2019-12-23 22:36 ` Peter Korsgaard
2020-01-06 9:31 ` Alexandre Belloni
2019-12-30 9:58 ` Yann E. MORIN
2020-05-22 14:09 ` Yann E. MORIN
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=20191223231946.3f57ebe1@windsurf \
--to=thomas.petazzoni@bootlin.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