| 1 |
Dan Armak wrote: |
| 2 |
|
| 3 |
>-----BEGIN PGP SIGNED MESSAGE----- |
| 4 |
>Hash: SHA1 |
| 5 |
> |
| 6 |
>Hello everyone, |
| 7 |
> |
| 8 |
>During the last week I've been working on separating the kde-base/* packages |
| 9 |
>into 'child' packages, a feature requested by some people. For example, |
| 10 |
>instead of kdenetwork we'd have separate kmail, knode, kppp etc. ebuilds. The |
| 11 |
>actual eclass framework to do this is ready. |
| 12 |
> |
| 13 |
>However, there is a problem. A 'parent' package (e.g. kde-base/kdenetwork) |
| 14 |
>will still exist since most people will want to merge all of it. There are |
| 15 |
>two ways to go: |
| 16 |
> |
| 17 |
>1. The parent and child packages will not be related. They will overwrite each |
| 18 |
>other's files. This is unacceptable. |
| 19 |
> |
| 20 |
>2. The parent package will depend on all of its children and install nothing |
| 21 |
>itself. Like kde-base/kde depends on kdebase kdenetwork etc., so will |
| 22 |
>kde-base/kdenetwork depend on net-www/konqueror, net-mail/kmail etc. This is |
| 23 |
>the approach I've taken so far. |
| 24 |
> |
| 25 |
>The problem is that while every 'child' package only compiles and installs the |
| 26 |
>relevant files, it still needs to run the complete configure script of its |
| 27 |
>parent package. In the admittedly worst-case example of kdebase, the script |
| 28 |
>takes ~1.5 minutes to execute on my P3-900. kdebase has 39 child packages, so |
| 29 |
>emerging kdebase with the new setup (i.e. emerging all child packages) will |
| 30 |
>take about an hour longer than emerging a monolithic kdebase takes now - |
| 31 |
>worse for slower computers. |
| 32 |
> |
| 33 |
>Most users won't accept this tradeoff of compile time for flexibility. So if |
| 34 |
>you have an alternative solution, please suggest it. Otherwise there won't be |
| 35 |
>any kde child packages. Speak now or remain forever silent :-) |
| 36 |
> |
| 37 |
>- -- |
| 38 |
>Dan Armak |
| 39 |
>Gentoo Linux developer (KDE) |
| 40 |
>Matan, Israel |
| 41 |
>-----BEGIN PGP SIGNATURE----- |
| 42 |
>Version: GnuPG v1.0.7 (GNU/Linux) |
| 43 |
> |
| 44 |
>iD8DBQE8348IUI2RQ41fiVERAqSWAJ92lM8cVCcH0bhefNNHbO+ww3VuHQCfVApF |
| 45 |
>gMSpHtMGOR7pgMKhdm8nJ/c= |
| 46 |
>=R1ij |
| 47 |
>-----END PGP SIGNATURE----- |
| 48 |
> |
| 49 |
>_______________________________________________ |
| 50 |
>gentoo-dev mailing list |
| 51 |
>gentoo-dev@g.o |
| 52 |
>http://lists.gentoo.org/mailman/listinfo/gentoo-dev |
| 53 |
> |
| 54 |
> |
| 55 |
> |
| 56 |
And couldn't those small intependent ebuilds being run in parallel? |
| 57 |
Would that shorten the compile-time? |
| 58 |
|
| 59 |
But has it's being said, it's ok to take longer compile times for more |
| 60 |
flexibility, after all if we're woried about the time it takes, we |
| 61 |
wouldn't be compiling things like kde, X and other BIG packages at all. |
Archives