| 1 |
On 11/18/2014 07:33 PM, Jauhien Piatlicki wrote: |
| 2 |
> On 11/18/2014 06:23 PM, hasufell wrote: |
| 3 |
>> On 11/18/2014 04:19 AM, heroxbd@g.o wrote: |
| 4 |
>>> Jauhien Piatlicki <jauhien@g.o> writes: |
| 5 |
>>> |
| 6 |
>>>> It would be probably good to have in the tree only the core components and move other stuff to the thematic overlays. |
| 7 |
>>>> |
| 8 |
>>>> Then we can have a clear understanding, how things should be: if |
| 9 |
>>>> something is a part of the core system, it goes to the tree, if |
| 10 |
>>>> something is a scientific packages, it lives in the science overlay, |
| 11 |
>>>> if something is a java stuff it lives in the java overlay, etc. |
| 12 |
>>> |
| 13 |
>>> This is a good idea. One difficulty: how to handle inter-overlay |
| 14 |
>>> dependence? Either the dependency should be expressed by overlay + |
| 15 |
>>> ebuild, or the dependent ebuild should be moved into the "core overlay". |
| 16 |
>>> I haven't figured out a clean solution yet. |
| 17 |
>>> |
| 18 |
>> |
| 19 |
>> git submodules? |
| 20 |
>> |
| 21 |
> |
| 22 |
> mmm, are you serious? ) |
| 23 |
> |
| 24 |
|
| 25 |
I really have no idea. It made sense for a moment. And then that moment |
| 26 |
was gone. |
Archives