[Buildroot] [PATCH 1/2] uclibc-ng: enable fts in default config file.

[Waldemar Brodkorb <wbx@openadk.org>]

Hi Peter, Thomas,
Peter Korsgaard wrote,

> >>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
> 
>  > Hello,
>  > On Sat, 15 Jul 2017 17:15:51 +0200, Peter Korsgaard wrote:
> 
>  >> > Note that contrary to what Adam commit log says, the size increase is
>  >> > 7.5 KB.  
>  >> 
>  >> Hmm, 7.5KB isn't much - But fts isn't enabled by default in uClibc-nc,
>  >> it is a legacy BSD feature and it also isn't supported by musl.
> 
>  > Agreed.
> 
>  >> It is easy to enable uClibc options, but difficult to disable them again
>  >> later (as users of the affected packages get caught).
>  >> 
>  >> Looking around, it seems we are only talking about 3 packages (if the
>  >> annotations are correct):
>  >> 
>  >> git grep -l 'fts.h' **/Config.in
>  >> package/libcgroup/Config.in
>  >> package/libselinux/Config.in
>  >> package/libsemanage/Config.in
>  >> 
>  >> Do we care enough for selinux users on uClibc (libcgroup seems to only
>  >> be an optional dependency for gst1-rtsp-server) to let all other
>  >> uClibc-ng users pay?
> 
>  > I would personally say no. The driving reason for Adam was to be able
>  > to build the SELinux stuff. But indeed, if you're adding all the
>  > SELinux overhead on your system, you most likely have the filesystem
>  > space needed to switch to glibc.
> 
>  > So I'm fine if we decide to say "no". It should hopefully increase the
>  > pressure on the upstream projects to move away from a legacy BSD
>  > interface, and use the POSIX interface instead.
> 
> Ok, agreed. Adam, sorry but we prefer to keep things as they
> are. It should be fairly easy for uClibc-ng users wanting to enable
> selinux to notice that they need to change to glibc instead based on the
> comment:
> 
> comment "libselinux needs a glibc toolchain w/ threads, dynamic library"

But this is not the case, they don't need to switch to glibc.
The decision makes me sad, as it goes the opposite way I try to
develop in Buildroot. I added a lot of stuff f.e. to uClibc-ng to
allow to build and use systemd. The required systemd patches are
upstream. I regulary try to enable packages which are disabled for no
good reason for uClibc users. AutoFS next version will contain the
patch allowing to use uClibc-ng and libtirpc instead of Glibc.

And what about the people using an architecture which is not supported
by glibc? Like Sparc, ARC, Xtensa and Or1k? Or the no-MMU
architectures? 

We enabled Wordexp recently and I would really love to see this
enabled, too. Could you rethink about your decision?

best regards
 Waldemar