[Buildroot] Review of FOSDEM 2014 meeting action points

[Buildroot] Review of FOSDEM 2014 meeting action points

[Thomas Petazzoni]

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.

 - 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] Review of FOSDEM 2014 meeting action points

[Samuel Martin]

Hi all,

Just some more topics...

On Wed, Oct 8, 2014 at 10:48 AM, Thomas Petazzoni
<thomas.petazzoni@free-electrons.com> wrote:
> 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.

- Having the package patch/configure/build/install phases in the
build.log file (not just the N line of the build).
  You could even image having the config.log or CMakeCache.txt file
uploaded as well to help investigation.

>
>  - 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.
>
>  - 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



-- 
Samuel

[Buildroot] Review of FOSDEM 2014 meeting action points

[Maxime Hadjinlian]

Hi all,

On Wed, Oct 8, 2014 at 10:54 AM, Samuel Martin <s.martin49@gmail.com> wrote:
> Hi all,
>
> Just some more topics...
>
> On Wed, Oct 8, 2014 at 10:48 AM, Thomas Petazzoni
> <thomas.petazzoni@free-electrons.com> wrote:
>> 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.
I know.. shame on me.
I still have a branch with a beginning of something. I would *really*
like to finish this during the dev-days, it would be great.
>>
>>  - 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.
>
> - Having the package patch/configure/build/install phases in the
> build.log file (not just the N line of the build).
>   You could even image having the config.log or CMakeCache.txt file
> uploaded as well to help investigation.
>
>>
>>  - 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.
>>
>>  - 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
>
>
>
> --
> Samuel
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

[Buildroot] Review of FOSDEM 2014 meeting action points

[Jeremy Rosen]

----- 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
> 

[Buildroot] Review of FOSDEM 2014 meeting action points

[Thomas De Schampheleire]

Hi Thomas,

On Wed, Oct 8, 2014 at 10:48 AM, Thomas Petazzoni
<thomas.petazzoni@free-electrons.com> wrote:
>
>  - 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.

Has been updated in the manual, indeed.

>
>  - '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.

I will add this to my todo list for the manual, but do not expect this
to be fixed soon. I indeed don't think it is a very important aspect.

>
>  - 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.

This is still on my list, but currently not at the top.
Main topics I have now for 2014.11 is
a. extension of kconfig-package to linux and barebox, and
b. implement an autobuilder instance
c. remove deprecated packages
d. during the stabilization month: further manual enhancements

Best regards,
Thomas

[Buildroot] Review of FOSDEM 2014 meeting action points

[Thomas Petazzoni]

Dear Maxime Hadjinlian,

On Wed, 8 Oct 2014 13:01:56 +0200, Maxime Hadjinlian wrote:

> >>  - 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.
> I know.. shame on me.

No problem. The point of doing a review of the action points is
definitely *not* to put the blame on anybody.

> I still have a branch with a beginning of something. I would *really*
> like to finish this during the dev-days, it would be great.

Ok. Though from my perspective, active development could better take
place outside of the dev-days. Maybe focusing the dev-days on
cleaning up the patchwork backlog is a better idea.

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

[Buildroot] Review of FOSDEM 2014 meeting action points

[Thomas Petazzoni]

Dear Jeremy Rosen,

On Wed, 8 Oct 2014 13:17:17 +0200 (CEST), Jeremy Rosen wrote:

> >  - 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

Ok, thanks for the feedback!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

[Buildroot] Review of FOSDEM 2014 meeting action points

[Thomas Petazzoni]

Dear Thomas De Schampheleire,

On Wed, 8 Oct 2014 13:43:44 +0200, Thomas De Schampheleire wrote:

> >  - 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.
> 
> Has been updated in the manual, indeed.

Ok, thanks.

> >  - '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.
> 
> I will add this to my todo list for the manual, but do not expect this
> to be fixed soon. I indeed don't think it is a very important aspect.

Indeed.

> This is still on my list, but currently not at the top.
> Main topics I have now for 2014.11 is
> a. extension of kconfig-package to linux and barebox, and
> b. implement an autobuilder instance
> c. remove deprecated packages
> d. during the stabilization month: further manual enhancements

Seems like a good list :-)

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

[Buildroot] Review of FOSDEM 2014 meeting action points

[Thomas Petazzoni]

Dear Samuel Martin,

On Wed, 8 Oct 2014 10:54:04 +0200, Samuel Martin wrote:

> >  - 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.
> 
> - Having the package patch/configure/build/install phases in the
> build.log file (not just the N line of the build).

Indeed. Patches welcome :-)

>   You could even image having the config.log or CMakeCache.txt file
> uploaded as well to help investigation.

There is already a patch implementing this, from Romain Naour, see
"[PATCH 1/1] autobuild-run: Include the config.log file (when it
exists) in the tarball" on the list. I haven't reviewed it yet, but on
principle, it looks like something useful to do.

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

[Buildroot] Review of FOSDEM 2014 meeting action points

[Gustavo Zacarias]

On 10/08/2014 01:14 PM, Thomas Petazzoni wrote:
>>>>  - 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.
>> I know.. shame on me.
> 
> No problem. The point of doing a review of the action points is
> definitely *not* to put the blame on anybody.
> 
>> I still have a branch with a beginning of something. I would *really*
>> like to finish this during the dev-days, it would be great.
> 
> Ok. Though from my perspective, active development could better take
> place outside of the dev-days. Maybe focusing the dev-days on
> cleaning up the patchwork backlog is a better idea.

FYI i'm doing some cleanup regarding busybox/sysvinit init (sic) and
patches are flowing with what i'm finding out.
In the end with sysvinit it's difficult to deal with the PNP approach in
that if people want a normal booting system without busybox they'll need
to throw a bunch of packages into the mix.
I can compile a list of the usual ones and we can add some documentation
about it, but i don't think forcing (selecting) them is a good idea
since customizing the init process can drop the need for some.
I'll also do some systemd testing but it's really low priority for me.
I think the PKG_INSTALL_INIT_SYSV defines are good enough unless we want
to deal with runlevels (wouldn't make sense, at least for me), systemd
is a whole different story as we discussed before.
Regards.

[Buildroot] Review of FOSDEM 2014 meeting action points

[Matthew Weber]

All,

On Wed, Oct 8, 2014 at 3:48 AM, Thomas Petazzoni
<thomas.petazzoni@free-electrons.com> wrote:
> 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.
>
<snip>
>
>  - 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.

We are preparing an updated SELinux patch set and hope to have it
submitted in the Nov-Dec time frame (finally got some funding to
finish this work).  For this time around, we've been doing some extra
testing in hopes the merge doesn't break things to badly.  There are a
number of RFC items that we'll be posting in the weeks to come
(covering documentation, defconfig examples, handing target skeleton
changes, etc.)


-- 
Matthew L Weber / Pr Software Engineer
Airborne Information Systems / Security Systems and Software
MS 131-100, C Ave NE, Cedar Rapids, IA, 52498, USA
www.rockwellcollins.com

Note: Any Export License Required Information and License Restricted
Third Party Intellectual Property (TPIP) content must be encrypted and
sent to matthew.weber at corp.rockwellcollins.com.

[Buildroot] Review of FOSDEM 2014 meeting action points

[Thomas Petazzoni]

Dear Matthew Weber,

On Wed, 8 Oct 2014 11:40:37 -0500, Matthew Weber wrote:

> >    - SELinux. Still not merged, but not really pushed actively
> >      anymore.
> 
> We are preparing an updated SELinux patch set and hope to have it
> submitted in the Nov-Dec time frame (finally got some funding to
> finish this work).  For this time around, we've been doing some extra
> testing in hopes the merge doesn't break things to badly.  There are a
> number of RFC items that we'll be posting in the weeks to come
> (covering documentation, defconfig examples, handing target skeleton
> changes, etc.)

Great. SELinux is definitely interesting, but it's also a big thing,
with lots of packages with scary build systems that do not handle
cross-compilation very well. So it'll take a bit of time to review and
get merged. But we'll work with you to get this done.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com