| 1 |
On Sat, 2006-02-18 at 08:24 +0000, Rohit Sharma wrote: |
| 2 |
> Hi there, |
| 3 |
> It just occurred to me that the emerges shall be much faster if emerges |
| 4 |
> were able to use config.cache set by other applications. The steps |
| 5 |
> during ./configure could be saved globally in an /etc/config.cache which |
| 6 |
> could be copied over by the current emerge step as it if was its own - |
| 7 |
> and be used. Could cut ./configure time by quite a bit. |
| 8 |
> |
| 9 |
> But since I am a very average guy and there are many people much smarter |
| 10 |
> than myself out there in gentoo, I think this idea has been discarded |
| 11 |
> long ago since there are incompatibilities amongst various software in |
| 12 |
> the way they do, if they do, create their config.cache. |
| 13 |
> |
| 14 |
> I was just curious. Have you considered it before? Please reply. |
| 15 |
> -- |
| 16 |
> Rohit Sharma |
| 17 |
Hi, |
| 18 |
On 'gentoo-portage-dev' ML there are such patch (for portage-2.1_preX) |
| 19 |
plus in portage there's a package: |
| 20 |
* dev-util/confcache |
| 21 |
Available versions: 0.3.3 0.4 0.4.1 |
| 22 |
Installed: 0.4.1 |
| 23 |
Homepage: http://dev.gentoo.org/~ferringb/confcache |
| 24 |
Description: global autoconf cache manager |
| 25 |
Both are working for me for 2-3 weeks w/o problems. |
| 26 |
Check the homepage/link in the package above. |
| 27 |
HTH.Rumen |
Archives