1 |
If it was something feasible to do, it would have been done already. |
2 |
|
3 |
Diego Elio Pettenò — Flameeyes |
4 |
flameeyes@×××××××××.eu — http://blog.flameeyes.eu/ |
5 |
|
6 |
|
7 |
On Tue, Jan 1, 2013 at 8:14 PM, Vadim A. Misbakh-Soloviov <mva@×××.name>wrote: |
8 |
|
9 |
> Hi there! |
10 |
> Long time ago I discovered that many language-specific packages |
11 |
> (libraries, webapps) written on languages like PHP, Ruby, Lua and so on |
12 |
> has (often) almost hardcoded dependence to be installed via their native |
13 |
> package managers (pecl, cpan, luarocks, gem, bundler and so on). |
14 |
> More of that, I discovered quite spiked way to install lang-specific |
15 |
> packages in portage (fakegem eclass, pecl-php eclass and so on). |
16 |
> Thinking in that way guided me to suggest to develop some kind of |
17 |
> compatibility layer between portage (and sandboxed installation) and |
18 |
> that lang-specific package managers. |
19 |
> So then it will be almost unneeded to, for example, write tons of new |
20 |
> local ebuilds when installing, for example new version of redmine. Or to |
21 |
> write tons of spikes when installing some PHP or Lua apps, designed for |
22 |
> pecl or luarocks respectively. |
23 |
> |
24 |
> But on the other hand — QA issues. I afraid, that it will make us |
25 |
> responsible to upstream failures (in users eyes). |
26 |
> |
27 |
> Anyway, let's discuss some ideas on that behaviour. |
28 |
> |
29 |
> |
30 |
> BTW, this post is mainly sponsored by great PITA about deploying rails |
31 |
> applications and trying to get them to work with system-wide dev-ruby/* |
32 |
> things installed (while upstream REQUIRES to use bundler). It is also |
33 |
> minor-sponsored by some kepler-project apps (Lua) and some PHP apps. |
34 |
> |
35 |
> |