| 1 |
On Monday 13 May 2002 12:01, Dan Armak wrote: |
| 2 |
> Hello everyone, |
| 3 |
> |
| 4 |
> During the last week I've been working on separating the kde-base/* |
| 5 |
> packages into 'child' packages, a feature requested by some people. For |
| 6 |
> example, instead of kdenetwork we'd have separate kmail, knode, kppp etc. |
| 7 |
> ebuilds. The actual eclass framework to do this is ready. |
| 8 |
> |
| 9 |
> However, there is a problem. A 'parent' package (e.g. kde-base/kdenetwork) |
| 10 |
> will still exist since most people will want to merge all of it. There are |
| 11 |
> two ways to go: |
| 12 |
> |
| 13 |
> 1. The parent and child packages will not be related. They will overwrite |
| 14 |
> each other's files. This is unacceptable. |
| 15 |
> |
| 16 |
> 2. The parent package will depend on all of its children and install |
| 17 |
> nothing itself. Like kde-base/kde depends on kdebase kdenetwork etc., so |
| 18 |
> will kde-base/kdenetwork depend on net-www/konqueror, net-mail/kmail etc. |
| 19 |
> This is the approach I've taken so far. |
| 20 |
> |
| 21 |
> The problem is that while every 'child' package only compiles and installs |
| 22 |
> the relevant files, it still needs to run the complete configure script of |
| 23 |
> its parent package. In the admittedly worst-case example of kdebase, the |
| 24 |
> script takes ~1.5 minutes to execute on my P3-900. kdebase has 39 child |
| 25 |
> packages, so emerging kdebase with the new setup (i.e. emerging all child |
| 26 |
> packages) will take about an hour longer than emerging a monolithic kdebase |
| 27 |
> takes now - worse for slower computers. |
| 28 |
> |
| 29 |
> Most users won't accept this tradeoff of compile time for flexibility. So |
| 30 |
> if you have an alternative solution, please suggest it. Otherwise there |
| 31 |
> won't be any kde child packages. Speak now or remain forever silent :-) |
| 32 |
|
| 33 |
Contrary to the other two mails, I'd not like this tradeoff. |
| 34 |
|
| 35 |
There is a third option: If someone wants say kmail and knode (which is what |
| 36 |
I'd like from kdenetwork myself) then run the configure script for kdenetwork |
| 37 |
once and then compile kmail and knode (and its dependencies like |
| 38 |
libkdenetwork) and install them. Of course you couldn't just have child |
| 39 |
packages in that case and have the kdenetwork script run the children one |
| 40 |
after another. |
| 41 |
|
| 42 |
Alex |
| 43 |
|
| 44 |
-- |
| 45 |
"They that can give up essential liberty to obtain a little temporary safety |
| 46 |
deserve neither liberty nor safety." |
| 47 |
Benjamin Franklin |
Archives