| 1 |
I think the minimum we can do right now is: |
| 2 |
having the ebuilds work in a totally independant way , for example using |
| 3 |
a directory exclusivly. |
| 4 |
and/or why not "not" deleting the source tree, so other pakages can use |
| 5 |
the already compiled object files ... |
| 6 |
this is totally "doable" as the strong point of emerge is the fact that |
| 7 |
it doesnt use the shared database stuff ... |
| 8 |
|
| 9 |
thank you guys again for this giant work . |
| 10 |
|
| 11 |
D. |
| 12 |
|
| 13 |
On Thu, 2001-12-06 at 07:04, Mikael Hallendal wrote: |
| 14 |
> tor 2001-12-06 klockan 02.51 skrev Miguel S. Filipe: |
| 15 |
> > While reading this, It reminded me of a thought i allready had. |
| 16 |
> > |
| 17 |
> > Why isn't portage more multi-task? What stops it from, while it's busy |
| 18 |
> > building something, downloading the packages that its going to |
| 19 |
> > (build/compile/install) next? |
| 20 |
> > This would speed up the merging process for those with slow internet |
| 21 |
> > connections, and it would not affect performance I believe. Is there any |
| 22 |
> > problem with this? Is it just dificult to implement, or its much more |
| 23 |
> > tricky and problematic that it seems? |
| 24 |
> |
| 25 |
> This has been discussed, also the possibility to download all packages |
| 26 |
> before starting to build (so that you can disconnect before starting to |
| 27 |
> build). |
| 28 |
> |
| 29 |
> Even on a fast connection it would be very nice to have the downloading |
| 30 |
> being done while compiling. |
| 31 |
> |
| 32 |
> Regards, |
| 33 |
> Mikael Hallendal |
| 34 |
> |
| 35 |
> -- |
| 36 |
> |
| 37 |
> Mikael Hallendal |
| 38 |
> Gentoo Linux Developer, Desktop Team Leader |
| 39 |
> CodeFactory AB, Stockholm, Sweden |
| 40 |
> |
Archives