Re: [Buildroot] [PATCH 1/1] package/systemd: Allow extra config options

[Arnout Vandecappelle <arnout@mind.be>]

On 08/01/2022 22:31, Norbert Lange wrote:
> Am Sa., 8. Jan. 2022 um 20:04 Uhr schrieb James Hilliard
> <james.hilliard1@gmail.com>:
>>
>> On Thu, Nov 26, 2020 at 8:28 AM Norbert Lange <nolange79@gmail.com> wrote:
>>>
>>> Systemd has very many options, adding a way for the user
>>> to set custom options can help customizations
>>> without changing buildroot files.
>>
>> I'm not sure this is a good idea, if a configuration option needs
>> customizability it
>> probably needs a specific kconfig option. Systemd config options tend to require
>> dependency selection and special handling so this seems likely to cause
>> spurious errors due to improper usage. Seems to be a pretty big footgun IMO.
> 
> Sure, you are aware that many of my buildroot patches are stuck in limbo
> since early 2020?

  Yes, due to various circumstances, maintainer time between Feb 2020 and May 
2021 has been very limited, and nobody in the community stepped up to review 
patches. We finally have a hackaton again where we're processing the backlog and 
we're making good progress. But we're not going to be able to fully catch up, so 
unless someone reviews and acks your patches, or unless they're trivial, they're 
likely to still face long delays in the coming months.

  It doesn't help to get your patches in faster, but it does help the community 
in general if you do reviews.

  Another thing that may help you get patches merged is if you collect them in a 
series and repost the entire series when something changes. Ideally you also 
carry patches from other people in that series. This makes life easier for the 
maintainers because it shows that it the series makes the whole more cohesive.


> Just doesnt seem feasible to timely fix everything and version bumps often leave
> more untapped options. Some part of the necessity would be just being pragmatic.
> 
> One example would be using the unified cgroups hierarchy
> (-Ddefault-hierarchy=unified), hybrid is pretty much deprecated,
> and some systemd features that buildroot allows to enable (OOMD for example)
> wont work without it.

  That's still a fairly recent series :-)


>> What systemd configure option would you want to be using that isn't
>> currently able to be enabled?
> 
> FYI those are the ones I currently use:
> 
> -Ddefault-hierarchy=unified \
> -Dutmp=false \
> -Ddefault-dnssec=no \
> -Didn=false \
> -Denvironment-d=false \
> -Dxdg-autostart=false \
> -Ddns-over-tls=false \
> -Ddefault-llmnr=no \
> -Ddns-over-tls=false \
> -Ddefault-mdns=no \
> -Dlz4=false

  Except for the unified hierarchy, all of these look like they should have been 
added when systemd was bumped and the option was created...


  Regards,
  Arnout

> 
> Norbert
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
> 
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot