Skip to content

Conversation

@Grimler91
Copy link
Member

We do not want to have multiple versions of the same package if it can be avoided. We already have guile 3.0, and no package at the moment depends on guile18, so we can remove it.

Only reason to keep guile 1.8 around is for programs that do not support newer guile versions. A better solution is to fix those programs instead though.

@Grimler91 Grimler91 requested a review from TomJo2000 as a code owner January 19, 2026 15:40
We do not want to have multiple versions of the same package if it can
be avoided. We already have guile 3.0, and no package at the moment
depends on guile18, so we can remove it.

Only reason to keep guile 1.8 around is for programs that do not
support newer guile versions. A better solution is to fix those
programs instead though.
@Grimler91 Grimler91 changed the title rmpkg(main/guile18): in favour of guile 3.0 instead rmpkg(main/guile18): in favour of guile 3.0 Jan 19, 2026
Copy link
Member

@robertkirkman robertkirkman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I approve of this, especially if you have checked the mirror download traffic for this package and already seen it's not getting frequent downloads.

Debian already removed their Guile 1.8 package many years ago.

While maintaining the guile 3 package, I considered removing guile18 before, but I couldn't find the git history of what it was necessary for in Termux, so I left it untouched because I wasn't sure if it was still needed or not.

@robertkirkman
Copy link
Member

Oh, but maybe you intended to move the package to the disabled-packages folder rather than deleting the files entirely? I had heard that generally, all packages removed should be moved to the disabled-packages folder rather than deleting the code, but I'm not sure if that applies to everything or not.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants