| 1 |
On Thu, 8 Sep 2011 20:10:23 +0200 |
| 2 |
Arfrever Frehtes Taifersar Arahesis <arfrever.fta@×××××.com> wrote: |
| 3 |
|
| 4 |
> 2011-09-08 19:03:56 Thomas Sachau napisał(a): |
| 5 |
> > Tomáš Chvátal schrieb: |
| 6 |
> > > Start collecting ideas for EAPI5. |
| 7 |
> > |
| 8 |
> > 2) USE-flag based support to install for different slots (e.g. |
| 9 |
> > python, ruby or php) |
| 10 |
> > |
| 11 |
> > The second one is already done in some eclasses, afaik php and |
| 12 |
> > ruby, but it might be a good idea to have a general framework for |
| 13 |
> > all slotted languages, so there is no need to re-implement the same |
| 14 |
> > for every language. |
| 15 |
> |
| 16 |
> It's better to have it implemented in eclasses. E.g. Python scripts |
| 17 |
> need to be specially handled |
| 18 |
> (python_merge_intermediate_installation_images() renames them (so |
| 19 |
> that their names include Python ABI), calls python_convert_shebangs() |
| 20 |
> if they don't have appropriate shebangs, and calls |
| 21 |
> python_generate_wrapper_scripts() to create appropriate wrapper |
| 22 |
> scripts). |
| 23 |
|
| 24 |
Eclasses itself can't handle this in really useful manner. PM needs to |
| 25 |
provide us with a nice ability to handle all that. Otherwise, we end up |
| 26 |
with more and more ugly hacks and needless rebuilds. |
| 27 |
|
| 28 |
The point in ABI slots should be to let PM build each slot |
| 29 |
independently and handle cross-slot depends. IOW, if I build one |
| 30 |
package for multiple python ABIs, I don't need every other python |
| 31 |
package built for all of them. |
| 32 |
|
| 33 |
Same goes for multilib -- I need 32-bit libs for wine, not for |
| 34 |
the whole system. And I want them being built when I start needing |
| 35 |
them, without requiring a rebuild of half of the system. And with |
| 36 |
separate USEflags. |
| 37 |
|
| 38 |
-- |
| 39 |
Best regards, |
| 40 |
Michał Górny |
Archives