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