[Slackbuilds-users] Reverting system/busybox to Default Build Configurations

[Lumin Etherlight]

Hello, fellow slackbuilders,

        I'm working on an update for busybox; hasn't been updated for
  a while, and is behind many versions.  Working on it, I found that
  the previous maintainer apparently included a custom build config
  with some substantial modifications.  I'm planning on reverting the
  configs to be as close as possible to the default shipped by busybox,
  with few minor modifications, like buildings statically, and without
  symlinks that replace normal path utilities.  I may later include an
  option to build dynamically, or a mechanism to load a custom .config
  file before building, but I'm afraid it would result in a huge number
  of edge cases during the installation process.

  Any thoughts on the following points:

     1. Is reverting to the default configs dangerous?  It may break
        people's workflows, but the busybox package update already
        includes a large number of upstream changes anyway.

     2. Is building statically by default and providing an option to
        build dynamically a reasonable approach?  The default builds
        dynamically, but current SlackBuild builds statically.

     3. Should the SlackBuild allow loading custom build configs?
        Or should we assume that if a user wants to build their own
        custom version they will know what to do?  Currently we ship a
        build config file, and even if we want to stay closer to default
        we most likely will still need to ship the build config file,
        as generating it from upstream package is an interactive menu
        process.

  ...would be appreciated :)


Thank you all,
I wish you a great day,
Lumin Etherlight