New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dev-scheme/guile: Add 2.2.6 SLOT=2.2 + patches #12401
Conversation
Bug: https://bugs.gentoo.org/689408 Closes: https://bugs.gentoo.org/598986 Closes: https://bugs.gentoo.org/590904 Closes: https://bugs.gentoo.org/629004 Signed-off-by: Cyprien Nicolas <cyprien@nicolas.tf>
aec512e
to
13f9a73
Compare
Copyright policy changePlease note that on 2018-09-15 Trustees have approved new Gentoo copyright policy. All contributions made to Gentoo need to follow this policy. If you include the Signed-off-by line in your commit message, you indicate that you have read the policy and agree to its terms. For more detailed explanation, please see the new Gentoo copyright policy explained article. Pull Request assignmentSubmitter: @fulax dev-scheme/guile: @gentoo/scheme Linked bugsBugs linked: 689408, 598986, 590904, 629004 In order to force reassignment and/or bug reference scan, please append Docs: Code of Conduct ● Copyright policy (expl.) ● Devmanual ● GitHub PRs ● Proxy-maint guide |
Hi, Can you please explain your idea with introduction of slotting? |
Hi @Amynka My idea is to stop breaking packages like texmacs or lilypond, while keeping up with guile releases for toolchain packages like autogen. No slot means we can only have one guile branch in gentoo. the guile-2.0 stabilization was required by autogen for toolchain updates, while we knew it would break packages like texmacs and other at that time. We are currently in the same situation regarding lilypond and guile-2.2. SLOT will allow us to keep those packages around. Upstream, guile-2.2 is on maintenance for a year or so, and guile-3.0 will be released in the coming months, and offers huge performance improvements. But I guess it will also break packages compatible with guile-2.0 or 2.2, so slots will enable us to provide guile-3.0 without breaking the whole ~arch depending packages. My plan was to slot guile 2.2, see how it goes, then retro-slot guile 2.0, and keep guile-1.8 for texmacs (whose developers are concerned about the guile-2 performance issues and maybe will go with 3.0). But I'm not a gentoo dev, I haven't been able to organize my time when I took the quizzes years ago, after slotting guile in the lisp overlay. So I have to trust your judgement on this. I am convinced that SLOTing guile is the way to go, but I do not have the power to provide the maintenance effort it might require, I volunteer for proxy-maintenance, but the time I can devote to this is currently reduced to 2 to 3 weekends each month. Thanks |
Let us know if you want to move forward with this. We'd need to try emulate the Lua and Python eclasses for consumers. |
Bug: https://bugs.gentoo.org/689408
Closes: https://bugs.gentoo.org/598986
Closes: https://bugs.gentoo.org/590904
Closes: https://bugs.gentoo.org/629004
Signed-off-by: Cyprien Nicolas cyprien@nicolas.tf