Summary: | media-sound/squeezeboxserver: new version which bundles all perl modules | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Gunnar Eggen <geggen54> |
Component: | Current packages | Assignee: | Joe Peterson (RETIRED) <lavajoe> |
Status: | RESOLVED FIXED | ||
Severity: | enhancement | CC: | perl, qa, stuart |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
See Also: | https://bugs.gentoo.org/show_bug.cgi?id=394751 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Gunnar Eggen
2011-12-14 19:34:18 UTC
i don't think "binary build" is what you're looking for. when we do xxx-bin packages, we delete any bundled packages. what you're asking for is to specifically ignore that part of the Gentoo policy and bundle all required packages in the ebuild. i don't think that's a good idea, and i'm not sure it would even pass QA. (i do sympathize with your position ... but maybe you can be more proactive in getting people to stabilize perl modules) Since I propose two options, I filed another bug regarding the use of bundled modules by a useflag in the existing package. I completely understand the policy on bundling of modules and libraries, but I was hoping to remedy some of the consequences of this policy by letting users knowingly choose otherwise in extreme cases. When it comes to perl-modules, how do we on a general note handle packages that depends on different versions of the modules? Is it not supposed to happen? Slotting? How to handle stabilization when differrent packages depend on different minor versions of the modules? This package is known to be very "delicate", and can break on even minor version updates of the modules, so I would like to discuss different ways of handling this. New package media-sound/logitechmediaserver-bin added. See https://bugs.gentoo.org/show_bug.cgi?id=377825 for more information as to why this was finally made a -bin package. |