1 |
Tom Gillespie <tgbugs@×××××.com> writes:
|
2 |
|
3 |
> For historical curiosity there was also |
4 |
> https://github.com/domenkozar/g-pypi at one point (similar to |
5 |
> https://github.com/rafaelmartins/g-octave). Having used g-octave, the |
6 |
> primary issue is as Michał says, there are a lot of corner cases that |
7 |
> the generation doesn't handle correctly which lead to broken ebuilds |
8 |
> and maintenance headaches. Speaking for python, catching and |
9 |
> correcting the use of setup_requires and other insanity visited upon |
10 |
> us by the wonders of setuptools makes this a non-starter. |
11 |
|
12 |
Yes, I agree.
|
13 |
|
14 |
> If you have a set a known sane packages you could in theory write an |
15 |
> eclass that captures the regularities of those packages, but I'm not |
16 |
> sure eclasses are suggested for that use case. |
17 |
|
18 |
eclass is designed for eliminating duplicated code in ebuilds. Therefore
|
19 |
yes, it is the legitimate use of eclass.
|
20 |
|
21 |
Benda |