Skip to content
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

Closed
wants to merge 1 commit into from

Conversation

fulax
Copy link

@fulax fulax commented Jul 7, 2019

@gentoo-bot gentoo-bot added assigned PR successfully assigned to the package maintainer(s). no bug found No Bug/Closes found in the commits. labels Jul 7, 2019
@fulax fulax changed the title dev-scheme/guile: Add 2.2.6 SLOT=2.2 + patches dev-scheme/guile: Add 2.2.6 SLOT=2.2 + patches [please reassign] Jul 7, 2019
@gentoo-bot gentoo-bot changed the title dev-scheme/guile: Add 2.2.6 SLOT=2.2 + patches [please reassign] dev-scheme/guile: Add 2.2.6 SLOT=2.2 + patches Jul 7, 2019
@gentoo-bot gentoo-bot added assigned PR successfully assigned to the package maintainer(s). no bug found No Bug/Closes found in the commits. and removed assigned PR successfully assigned to the package maintainer(s). no bug found No Bug/Closes found in the commits. labels Jul 7, 2019
@fulax fulax changed the title dev-scheme/guile: Add 2.2.6 SLOT=2.2 + patches dev-scheme/guile: Add 2.2.6 SLOT=2.2 + patches [please reassign] Jul 8, 2019
@gentoo-bot gentoo-bot changed the title dev-scheme/guile: Add 2.2.6 SLOT=2.2 + patches [please reassign] dev-scheme/guile: Add 2.2.6 SLOT=2.2 + patches Jul 8, 2019
@gentoo-bot
Copy link

Copyright policy change

Please 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 assignment

Submitter: @fulax
Areas affected: ebuilds
Packages affected: dev-scheme/guile

dev-scheme/guile: @gentoo/scheme

Linked bugs

Bugs linked: 689408, 598986, 590904, 629004


In order to force reassignment and/or bug reference scan, please append [please reassign] to the pull request title.

Docs: Code of ConductCopyright policy (expl.) ● DevmanualGitHub PRsProxy-maint guide

@gentoo-bot gentoo-bot added assigned PR successfully assigned to the package maintainer(s). bug linked Bug/Closes found in footer, and cross-linked with the PR. and removed assigned PR successfully assigned to the package maintainer(s). no bug found No Bug/Closes found in the commits. labels Jul 8, 2019
@gentoo-repo-qa-bot
Copy link
Collaborator

Pull request CI report

Report generated at: 2019-07-08 17:22 UTC
Newest commit scanned: 13f9a73
Status: ✅ good

Issues already there before the PR (double-check them):
https://qa-reports.gentoo.org/output/gentoo-ci/6aa1c37/output.html#app-emulation/docker-credential-helpers
https://qa-reports.gentoo.org/output/gentoo-ci/6aa1c37/output.html#dev-java/icedtea
https://qa-reports.gentoo.org/output/gentoo-ci/6aa1c37/output.html#dev-libs/amdgpu-pro-opencl
https://qa-reports.gentoo.org/output/gentoo-ci/6aa1c37/output.html#dev-libs/libgcrypt
https://qa-reports.gentoo.org/output/gentoo-ci/6aa1c37/output.html#dev-libs/libtasn1
https://qa-reports.gentoo.org/output/gentoo-ci/6aa1c37/output.html#dev-python/lxml
https://qa-reports.gentoo.org/output/gentoo-ci/6aa1c37/output.html#dev-util/ftjam
https://qa-reports.gentoo.org/output/gentoo-ci/6aa1c37/output.html#media-fonts/noto
https://qa-reports.gentoo.org/output/gentoo-ci/6aa1c37/output.html#net-im/prosody
https://qa-reports.gentoo.org/output/gentoo-ci/6aa1c37/output.html#net-irc/psybnc
https://qa-reports.gentoo.org/output/gentoo-ci/6aa1c37/output.html#net-libs/gnutls
https://qa-reports.gentoo.org/output/gentoo-ci/6aa1c37/output.html#net-misc/calicoctl
https://qa-reports.gentoo.org/output/gentoo-ci/6aa1c37/output.html#net-print/cndrvcups-common-lb
https://qa-reports.gentoo.org/output/gentoo-ci/6aa1c37/output.html#net-print/cndrvcups-lb
https://qa-reports.gentoo.org/output/gentoo-ci/6aa1c37/output.html#sys-apps/dcfldd
https://qa-reports.gentoo.org/output/gentoo-ci/6aa1c37/output.html#sys-cluster/openstack-meta

@Amynka Amynka self-assigned this Sep 15, 2019
@Amynka
Copy link
Contributor

Amynka commented Sep 15, 2019

Hi, Can you please explain your idea with introduction of slotting?

@fulax
Copy link
Author

fulax commented Sep 21, 2019

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

@thesamesam
Copy link
Member

@Amynka Are you okay with the principle of slotting based on this? Upstream seem to intend for multiple versions to be installed in parallel, to allow moving forward while older consumers haven't yet.

@fulax In general, a few weekends a month is enough.

@thesamesam
Copy link
Member

thesamesam commented Dec 4, 2021

@Amynka Are you okay with the principle of slotting based on this? Upstream seem to intend for multiple versions to be installed in parallel, to allow moving forward while older consumers haven't yet.

@fulax In general, a few weekends a month is enough.

Let us know if you want to move forward with this. We'd need to try emulate the Lua and Python eclasses for consumers.

@thesamesam thesamesam closed this Dec 4, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
assigned PR successfully assigned to the package maintainer(s). bug linked Bug/Closes found in footer, and cross-linked with the PR.
Projects
None yet
5 participants