On Tue, 2009-06-02 at 17:43 +0000, Sven wrote: > (1) > All gems should be installed from ebuilds only. > > (2) > If an ebuild requires a gem, it has to be installed from the corresponding > ebuild. For all other gems, Gentoo leaves the choice to the user and tries to > work together as well as possible with RubyGems. > > Currently, reality is closer to (2) and I honestly don't believe it makes much > sense to build the infrastructure to convert all gems to ebuilds automatically > and timely enough for (1) to come true. If the delay were only hours, Ruby > devs > would rather use the RubyGems manager than waiting for the ebuild to appear.
My personal preference is still to follow [1] as much as possible, because it allows me to handle all dependencies of a particular application within a single system. At work we have a private overlay which contains meta-ebuilds for our web applications, and I can use that to set up a blank server for one of our web apps with one emerge command, or update existing servers to new dependencies. On the other hand I also don't believe that we should provide all 1500+ gems as ebuilds, either through a manual or automatic process. Right now our rule of thumb is to add gems when they are popular (e.g. rails), when they provide an application that has been requested, or when they are needed as dependencies for either one of those. We also have a Summer of Code project to break down the monolithic default gem installation into Gentoo phases so that we can have more fine-grained control over the build, test, and installation process. Hans
signature.asc
Description: This is a digitally signed message part
