From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Kilian Zinnecker <kilian.zinnecker@mail.de>,
Arnout Vandecappelle via buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] Buildroot docker image
Date: Sun, 10 Dec 2023 18:02:47 +0100 [thread overview]
Message-ID: <20231210180247.24316308@windsurf> (raw)
In-Reply-To: <ZXXBnuTeg_LcSWgZ@landeda>
On Sun, 10 Dec 2023 14:48:14 +0100
"Yann E. MORIN" <yann.morin.1998@free.fr> wrote:
> M: strictly mandatory
> T: optional, but helps use pre-built toolchains
> S: optional, speeds up the build
> C: needed to run check-package et al.
> R: needed to run the runtime test-suite
>
> Bazaar, mercurial and subversion are optional, and only required when a
> package is bzr-, hg-, or svn-hosted, but if we want this image to be
> usable generally, it should have all three.
>
> Since mercurial is a python package, we can't drop python3, and the
> remaining modules are relatively small in comparison to the rest.
>
> Getting a more minimal image would be just about dropping qemu. That
> would make for an image that we could not use in the CI, and that would
> not be usable to test the changes done to Buildroot. I don't think that
> would mkae for a good image.
It's mainly Python3 that is important to drop. Python3 is not part of
our mandatory requirements, and it's a very frequent sources, as people
don't have an easily accessible container to test Buildroot builds
without Python3, so they forget BR2_TARGET_UBOOT_NEEDS_PYTHON3 or
similar options.
We have exactly two packages that use Mercurial.
pygame has the comment "stable 1.9.1 release requires V4L which has
been wiped out of recent Linux kernels, so use latest mercurial
revision until next stable release is out.", but there's a recent
pygame 2.5.2 release from September 2023. And pygame is now on Github:
https://github.com/pygame/pygame.
The other one is dvb-apps, which hasn't seen a single commit since
March 2014: https://linuxtv.org/hg/dvb-apps. We could consider it
obsolete/unmaintained maybe? :-)
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-12-10 17:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-01 6:51 [Buildroot] Buildroot docker image Kilian Zinnecker via buildroot
2023-09-01 7:19 ` Arnout Vandecappelle via buildroot
2023-09-02 7:42 ` Thomas Petazzoni via buildroot
2023-12-03 11:47 ` Kilian Zinnecker via buildroot
2023-12-09 21:29 ` Arnout Vandecappelle via buildroot
2023-12-10 12:17 ` Thomas Petazzoni via buildroot
2023-12-10 19:28 ` Peter Korsgaard
2023-12-10 13:48 ` Yann E. MORIN
2023-12-10 13:51 ` Yann E. MORIN
2023-12-10 17:02 ` Thomas Petazzoni via buildroot [this message]
2023-12-10 18:46 ` 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=20231210180247.24316308@windsurf \
--to=buildroot@buildroot.org \
--cc=kilian.zinnecker@mail.de \
--cc=thomas.petazzoni@bootlin.com \
--cc=yann.morin.1998@free.fr \
/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