From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: Bagas Sanjaya <bagasdotme@gmail.com>,
Buildroot Mailman <buildroot@buildroot.org>
Subject: Re: [Buildroot] <PACKAGE>_SOURCE with <PACKAGE>_SITE_METHOD = git can result to tar.gz with mismatched file extension
Date: Sat, 3 Dec 2022 19:14:01 +0100 [thread overview]
Message-ID: <20221203181401.GE3302@scaer> (raw)
In-Reply-To: <20221203182323.30a07da3@windsurf>
Thomas, All,
On 2022-12-03 18:23 +0100, Thomas Petazzoni spake thusly:
> On Sat, 3 Dec 2022 17:05:06 +0100
> "Yann E. MORIN" <yann.morin.1998@free.fr> wrote:
> > > Yann, thoughts? (1) seems easier to me, I don't know if the benefits of
> > > (2) are really relevant.
> > I think the only meaningful solution is to go for (1): detect and abort.
> > I too do not think letting packages each request a different compression
> > would be interesting...
> > If we believe that gzip is too slow/big, then we can think about
> > switching to another scheme globaly, but that's orthogonal...
> Actually, (2) would have an advantage: it would allow to migrate from
> one compression to another package per package, instead of requiring a
> flag day where we switch all VCS-fetched packages to the new
> compression.
Sure, but we already need a flag-day when we actually change the way we
generate the archives from VCS checkouts:
5b95a5dc27c0 support/download: change format of archives generated from git
c043ecb20ce6 support/download: change format of archives generated from svn
c92be85e3a29 support/download: make the svn backend more reproducible
Having a flag-day is not too bad, as we can quite easily script the hash
updates...
So, I still believe we should not allow _SOURCE when _SITE_METHOD is one
of our VCS backends.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-12-03 18:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 14:02 [Buildroot] <PACKAGE>_SOURCE with <PACKAGE>_SITE_METHOD = git can result to tar.gz with mismatched file extension Bagas Sanjaya
2022-12-03 14:52 ` Thomas Petazzoni via buildroot
2022-12-03 16:05 ` Yann E. MORIN
2022-12-03 17:23 ` Thomas Petazzoni via buildroot
2022-12-03 18:14 ` Yann E. MORIN [this message]
2022-12-04 12:31 ` Bagas Sanjaya
2022-12-04 14:05 ` 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=20221203181401.GE3302@scaer \
--to=yann.morin.1998@free.fr \
--cc=bagasdotme@gmail.com \
--cc=buildroot@buildroot.org \
--cc=thomas.petazzoni@bootlin.com \
/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