Page MenuHomeSolus

Update Guile to 2.2.6, latest stable
Needs ReviewPublic

Authored by cnasc on Sun, Aug 11, 3:54 PM.

Details

Reviewers
None
Group Reviewers
Triage Team
Summary

Update Guile to 2.2.6, replacing the legacy 2.0.x package.
Release notes for 2.2.0 can be seen here
Release notes for the following bugfix releases can be seen here

An effort was made to perform this update in T2935, but it was closed when the old patch format was deprecated.

Some distros package both the current stable Guile as well as legacy Guile builds (some going back as far as 1.8).
I'm unsure if Solus wants to offer several Guiles in parallel or only track the current stable, let me know if this
should be a new package instead of an update.

Test Plan

Build locally, install generated package, run and try several code snippets to make sure they behave as expected.
Note: may be worth looking at which packages have a dependency on Guile and double-check that they do not rely on
earlier versions?

Diff Detail

Repository
R1119 guile
Branch
master
Lint
No Linters Available
Unit
No Unit Test Coverage
cnasc created this revision.Sun, Aug 11, 3:54 PM
cnasc requested review of this revision.Sun, Aug 11, 3:54 PM
joebonrichie added a subscriber: joebonrichie.

You need to add abi_symbols and abi_used_libs files to the diff. For info libguile-2.0.so.22 has been bumped to libguile-2.2.so.1, all rev deps of this will need to be rebuilt. The pkgconfig name has also changed from pkgconfig(guile-2.0) to pkgconfig(guile-2.2). Already I know that weechat and autogen do not support the newest guile. GCC tools like gdb also do not support it. Until they do, I doubt we will create two guile packages unless we are forced to.

cnasc added a comment.Sun, Aug 11, 7:57 PM

Until they do, I doubt we will create two guile packages unless we are forced to.

I see, I'll close this then

For clarification, while I appreciate you putting the time in to make the patch it's just basically double the cost to maintain two versions of a package, especially, when few things support the new version at this point.

For clarification, while I appreciate you putting the time in to make the patch it's just basically double the cost to maintain two versions of a package, especially, when few things support the new version at this point.

No worries at all, I totally understand