| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
On Monday 13 May 2002 15:46, Alexander Gretencord wrote: |
| 5 |
> Contrary to the other two mails, I'd not like this tradeoff. |
| 6 |
> |
| 7 |
> There is a third option: If someone wants say kmail and knode (which is |
| 8 |
> what I'd like from kdenetwork myself) then run the configure script for |
| 9 |
> kdenetwork once and then compile kmail and knode (and its dependencies like |
| 10 |
> libkdenetwork) and install them. Of course you couldn't just have child |
| 11 |
> packages in that case and have the kdenetwork script run the children one |
| 12 |
> after another. |
| 13 |
|
| 14 |
The problem is, there's no clean way to imlpement this with ebuilds (and even |
| 15 |
eclasses). How can I make the kdenetwork ebuild compile a selective list of |
| 16 |
'children' while only running configure once? Granted, there's emerge |
| 17 |
- --inject now, but an ebuild is _not_ supposed to be using that. Do you have |
| 18 |
some specific idea for an implementation in mind? |
| 19 |
|
| 20 |
- -- |
| 21 |
Dan Armak |
| 22 |
Gentoo Linux developer (KDE) |
| 23 |
Matan, Israel |
| 24 |
-----BEGIN PGP SIGNATURE----- |
| 25 |
Version: GnuPG v1.0.7 (GNU/Linux) |
| 26 |
|
| 27 |
iD8DBQE83/k3UI2RQ41fiVERAljvAJsGR2xCrzQhpEtDrNVnbOWAPBYQ7gCfdqxA |
| 28 |
KjfcXtv/RfuLgmpr/T6FWkc= |
| 29 |
=uYnd |
| 30 |
-----END PGP SIGNATURE----- |
Archives