Summary: | media-gfx/slic3r pulls unstable version of perl and modules. | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Eric "me262" Mason <_me262> |
Component: | [OLD] Keywording and Stabilization | Assignee: | M. B. <tomboy64> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | 3dprint, perl, proxy-maint |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
See Also: | https://bugs.gentoo.org/show_bug.cgi?id=581894 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Eric "me262" Mason
2016-05-02 21:46:47 UTC
1. Mixing ~arch and arch is not "officially" supported, but we still do what we can where possible. 2. However, the work involved to avoid forcing perl-5.22 was semi-large and threatened risking complicating people's next upgrade. 3. Stabilization is happening very very soon, and Perl 5.22 will become "Stable", avoiding this bug being a problem. ( And had we satisfied #2, we'd make #3 harder ) There's nothing really to do here other than not mix arches or wait for stabilization. The problem should go away very shortly after we get bug #567482 done. Of note, you can add my overlay via "layman -a axs" to gain easy access to perl-core modules on par with dev-lang/perl-5.22. Then it's just a matter of keywording the various dev-perl and virtual packages. (In reply to Ian Stakenvicius from comment #2) > Of note, you can add my overlay via "layman -a axs" to gain easy access to > perl-core modules on par with dev-lang/perl-5.22. Then it's just a matter > of keywording the various dev-perl and virtual packages. slic3r is now in the gentoo main repo (which is why I was getting these problems). I was using it from axs until just recently. Good to know on the keywording and perl issues. I think I just need to work through "perl-cleaner --reallyall" mixed with "emerge -av1 --nodeps package" a bit on getting these updated to 5.22, which is looking like the main issue that the existing packages are locking to 5.20. I seem to be having this issue on another computer here from 5.18 to 5.20. I'm closing this one -- its not a bug to require ~arch deps when the package itself is ~arch. If slic3r was stable on any arch that would be another thing, but it's not. |