Safer handling of extensions from the software library “readline 8.2”

English Programming/Scripting
1

The commit “readline-8.2 distribution sources and documentation” was performed on 2022-09-26.

The corresponding diff statistics are providing the information “110 files changed, 21540 insertions, 20923 deletions”.
Some function implementations were added also by this software update.

Now it seems that several software developers and system administrators are struggling with collateral evolution.
I became affected also in special ways according to the addition of the function “rl_trim_arg_from_keyseq” as I indicated it by the bug report “Fix the availability of the symbol “rl_trim_arg_from_keyseq” (for “bash 5.2.2”)”.

How would you like to achieve further improvements and fixes accordingly? :\

2

Contact the maintainer of the involved packages. Create bugreports. Follow the bugreports. Provide useful informations in the bugreport. Follow the relevant development communication channels…

It’s the nature of a rolling release that due to the fast evolvement sometimes, something won’t work as you expect.

If you don’t know how to compile your own additional kernel modules and you don’t wish to learn or keep a very close eye on what is being updated, please don’t use Tumbleweed.

Source: Portal:Tumbleweed - openSUSE Wiki

3

Which impressions do you get from mentioned technical details?

[QUOTE]It’s the nature of a rolling release that due to the fast evolvement sometimes, something won’t work as you expect.
[/QUOTE]
Would any more users like to influence the evolution in desirable directions? :\

4

:\

  • Will the chances grow for a proper reinstallation of the software package “libreadline8” (version 8.2) within a chroot environment for my affected system configuration?
  • Would you like to point further possibilities out for achieving consistent package dependencies?
5

I hope that selected software components can be activated so that a command interpreter does not annoy me with undesirable side-effects as it is temporarily happening with bash 5.2.2 because of undefined symbols on “a development system”.
Would you like to suggest any system configuration alternatives? :\