I would like to request a binary build for squeezeboxserver (or soon to be Logitech Mediaserver). As a user I see several reasons for this: 1. The package depends strictly on ALOT of perl libraries, which makes us fall behind on new versions, waiting for new/updated perl packages to make it in to the tree. 2. Stable users have to show extreme caution when keywording/updating the needed perl modules, as even minor changes in versions can break this fragile but very much needed software. 3. I guess we'll never see this package ever hitting stable, due to all the strict dependencies. I might be wrong here, but my guess is that this software has a rather large userbase, and steps should be taken to make this as easy as possible to maintain both for users and the maintainers (who is doing a great job btw), and eventually hit stable. I see two possible solutions here. The first is to add a separate squeezeboxserver-bin package, that uses the bundled libraries. The second option is to enable the use of bundled libraries in the existing package by a useflag or other means. Both these options present the users with the option of installing a version which doesn't need all that extra care, but the first option even eases the job of the maintainers and might even lead to it hitting stable in the future. I am aware of the risks regarding bundled libraries, but this is something users can decide for themselves as both options will be available. Reproducible: Always
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.
