| 1 |
Sorry about not reading the initial mail twice, |
| 2 |
what you really wanted were that portage should start to compile |
| 3 |
A as soon as it has what that is required, and download B (and possibly C) |
| 4 |
while it start to, and compiles A. What I've suggested will not do that. |
| 5 |
|
| 6 |
=) |
| 7 |
|
| 8 |
Christian |
| 9 |
|
| 10 |
> I belive it could be achieved by doing this: |
| 11 |
> |
| 12 |
> emerge --fetchonly A B && emerge A B |
| 13 |
> or |
| 14 |
> emerge -f A B && emerge A B |
| 15 |
> for short |
| 16 |
> |
| 17 |
> Even though it would be nice to have a flag like --fetchfirst (so that |
| 18 |
> one do not need to list the ebuilds twice, I still think the |
| 19 |
> portage-system will have to go through it twice.) |
| 20 |
> |
| 21 |
> BTW what is the id-bug-number of your bug? |
| 22 |
> (I believe that it would be nice if we post that as a reference in |
| 23 |
> situations like this.) |
| 24 |
> |
| 25 |
> All the best, |
| 26 |
> Christian |
| 27 |
> |
| 28 |
>> Hi! |
| 29 |
>> |
| 30 |
>> On Tue, 13 Aug 2002, Dan Naumov wrote: |
| 31 |
>>> Submit this suggestion to Gentoo BugZilla. |
| 32 |
>> OK, I did. How long time can it take to develop and commit such a |
| 33 |
>> feature to the main portage tree? |
| 34 |
>> |
| 35 |
>> Zizi |
| 36 |
>> |
| 37 |
>> |
| 38 |
>> _______________________________________________ |
| 39 |
>> gentoo-dev mailing list |
| 40 |
>> gentoo-dev@g.o |
| 41 |
>> http://lists.gentoo.org/mailman/listinfo/gentoo-dev |
| 42 |
> |
| 43 |
> |
| 44 |
> |
| 45 |
> _______________________________________________ |
| 46 |
> gentoo-dev mailing list |
| 47 |
> gentoo-dev@g.o |
| 48 |
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev |
Archives