From: Jeremy Rosen <jeremy.rosen@openwide.fr>
To: buildroot@busybox.net
Subject: [Buildroot] Review of FOSDEM 2014 meeting action points
Date: Wed, 8 Oct 2014 13:17:17 +0200 (CEST) [thread overview]
Message-ID: <1490631735.26304543.1412767037821.JavaMail.root@openwide.fr> (raw)
In-Reply-To: <20141008104845.495ad683@free-electrons.com>
----- Mail original -----
> Hello,
>
> In preparation for the upcoming developers meeting on
> Saturday/Sunday,
> I had a look at all the topics/action points from the FOSDEM 2014
> meeting, and tried to see which ones were implemented, which ones
> were
> not. The idea is to create some discussion around those action
> points,
> and see if anything needs to be done about the remaining one,
> discussed
> this week-end, etc.
>
> - BR2_PREFER_STATIC_LIB refactoring. The point is to clarify
> BR2_PREFER_STATIC_LIB, and separate three cases: static only,
> shared+static, shared only. Thomas P. was supposed to work on
> this,
> but nothing happened.
>
> - Hashes of download. This has been implemented by Yann, and merged,
> and more and more packages are gaining hash files.
>
> - SystemV/systemd init scripts. The idea was to do automatic
> installation of init scripts / service files located in
> package/<foo>/. Maxime Hadjinlian said he would work on this, but
> not much happened. On a related note, there is a need to separate
> the skeleton to not avoid Busybox-related init scripts in a pure
> systemd configuration.
>
> - Clarification of the meaning of Acked-by/Reviewed-by tag in the
> Buildroot manual. I think this has been done by Thomas DS. To be
> confirmed.
>
> - Evaluation of the patch acceptance process. The idea of a
> statistic
> of the list of pending patches in patchwork has not been fully
> implemented: Arnout has proposed a script, but it has never been
> converted into a cronjob to provide publicly visible statistics.
>
> Regarding Thomas P. taking over the commit access when Peter is
> away, this is happening more and more frequently.
>
> - Autouilder wishlist:
>
> - Run-time tests. Nothing has been done, since we had no GSoC to
> make progress on this.
>
> - Expand the number of autobuild machines: done, thanks to the
> autobuild-run script. Nathaniel Roach and Richard Braun are
> participating to the testing effort, and Peter has added more
> machines. We now have ~200-230 builds per day, up from ~100
> builds per day.
>
> - Click on a package and see the last failures of that package:
> this has been implemented.
>
> - Expose read-only SQL queries: not done, maybe a bit difficult
> security wise.
>
> - Genimages. No progress has been made on that front.
>
> - How to handle the uClibc problem.
>
> Recently, we've had less problems caused specifically by uClibc
> feature patches. And uClibc-ng has appeared, which is giving some
> hope of improvement.
>
> - Website and branding.
>
> A new http://buildroot.org has been put online, thanks to the work
> done by Maxime Hadjinlian.
>
> - Google Summer of Code
>
> One student (Hadrien Boutteville) participated. Unfortunately, it
> didn't work very well, and not many patches have been contributed.
>
> - Evaluation of BR2_EXTERNAL. Not sure exactly what was needed
> here. Jeremy Rosen was supposed to submit a patch, but I'm not
> sure
> if it happened, or even if something needs to happen.
>
The patch was more or less deprecated/implemented differently.
buildroot-submodules covers the underlying idea of that particular
action point : how complete is BR2_EXTERNAL, can we externalize
everything ? at this point, the answer is definitely yes, so
this can be considered closed
> - State of major patch sets
>
> - Systemd/udev support. Has been merged.
> - Perl package infra. Has been merged.
> - SELinux. Still not merged, but not really pushed actively
> anymore.
> - libdrm/mesa3d updates. A lot of things happened in this area,
> with now a clear owner/maintainer of this package (Bernd).
>
> - 'target' defconfigs vs. 'development' configs. This was supposed
> to be an addition to the Buildroot manual, but it never
> happened. Not sure this is very important.
>
> - Python packages: depends vs .select. Conclusion: we change the
> handling of optional python bindings: instead of selecting them
> automatically when python is enabled, we add explicit config
> symbols for them. ThomasDS will update the patches accordingly.
>
> Not sure what happened on this topic.
>
> - pkgparentdir removal. Has been done.
>
> Thomas
> --
> Thomas Petazzoni, CTO, Free Electrons
> Embedded Linux, Kernel and Android engineering
> http://free-electrons.com
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>
next prev parent reply other threads:[~2014-10-08 11:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-08 8:48 [Buildroot] Review of FOSDEM 2014 meeting action points Thomas Petazzoni
2014-10-08 8:54 ` Samuel Martin
2014-10-08 11:01 ` Maxime Hadjinlian
2014-10-08 16:14 ` Thomas Petazzoni
2014-10-08 16:24 ` Gustavo Zacarias
2014-10-08 16:18 ` Thomas Petazzoni
2014-10-08 11:17 ` Jeremy Rosen [this message]
2014-10-08 16:14 ` Thomas Petazzoni
2014-10-08 11:43 ` Thomas De Schampheleire
2014-10-08 16:16 ` Thomas Petazzoni
2014-10-08 16:40 ` Matthew Weber
2014-10-08 16:43 ` Thomas Petazzoni
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=1490631735.26304543.1412767037821.JavaMail.root@openwide.fr \
--to=jeremy.rosen@openwide.fr \
--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