On 01/01/2013 22:12, Michael Orlitzky wrote: > > In lieu of that, what we do is create ebuilds like > www-apps/redmine-dependencies. I manually parse the Gemfile for the > (R)DEPENDs. My life would be a lot easier if we had something like > gentoo-haskell's hackport that could parse a Gemfile and spit out an > ebuild. But in any case, it's a poor substitute for doing it right.
If it could be possible, we would have done. Really, Gemfiles and .gemspecs are just a pain in the ass and most of the time they don't really represent what they purport to. As Ciaran said (wth? do I start 2013 agreeing with Ciaran?), they don't follow their own rules half the times, which is why we still hand-craft Ruby ebuilds, and why we often can't update to "the latest and greatest" package out there: sometimes the latest and greatest is also broken. In general, for what concerns Rails app, packaging them in any form is a bad idea. How do you actually manage it, when the source code of the app _is_ the app itself? It's not like you can say "here are the configuration file for webapp X".. It could be possible for webapp-config to come to our help there, but it would require for it to be rewritten to take Rails into account, as right now it doesn't. I know because it was trying to get an ebuild for Typo that I came to install my own blog (instead of using Gentoo Infra's b2evo) and thus create the monstrosity that you all know nowadays. -- Diego Elio Pettenò — Flameeyes flamee...@flameeyes.eu — http://blog.flameeyes.eu/
signature.asc
Description: OpenPGP digital signature
