| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Kristian Benoit wrote: |
| 5 |
> # ebuild path/to/ebuild config" |
| 6 |
> |
| 7 |
> I'm trying to do the same as config does, but in as a preconfig that |
| 8 |
> would only be also called on user request. |
| 9 |
> |
| 10 |
|
| 11 |
I'm just idly thinking here, and I'm sorry if this has already been said |
| 12 |
better - but I could see some value in an *optional* src_preconfig() |
| 13 |
function that allows you to run a manual config such as in the make |
| 14 |
menuconfig case - not required, but if present the ebuild breaks out |
| 15 |
with the einfo message, then when you go to run emerge again detects the |
| 16 |
change and carries on. Course as soon as I type this I realize that |
| 17 |
would require even more finangling since you would want to avoid |
| 18 |
clobbering with features=clean flags. Not sure of the mechanics on how |
| 19 |
this is done for the portage emerge process, but even stopping the |
| 20 |
emerge process for those packages that *must* have a preconfig done |
| 21 |
would help (are there any though? I can think of one maybe, but not |
| 22 |
really anything to demand new functionality in portage yet). |
| 23 |
|
| 24 |
2 probably pointless cents on the matter, |
| 25 |
|
| 26 |
- -mike |
| 27 |
-----BEGIN PGP SIGNATURE----- |
| 28 |
Version: GnuPG v1.4.0 (GNU/Linux) |
| 29 |
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org |
| 30 |
|
| 31 |
iD8DBQFC1oxbq1ztTp5/Ti4RAh8hAJ4lgOVUpY5KKgwi5kuNuFNRqvt5rgCePCg1 |
| 32 |
GwezKKJ5hEJ3HU2XqL5DB7w= |
| 33 |
=sCo+ |
| 34 |
-----END PGP SIGNATURE----- |
| 35 |
-- |
| 36 |
gentoo-dev@g.o mailing list |
Archives