public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "jano" <jano@portablehole.net>
To: <gentoo-dev@gentoo.org>
Subject: Re: [gentoo-dev] multitasked emerge (download while build ...)
Date: Thu, 6 Dec 2001 09:13:07 -0800 (PST)	[thread overview]
Message-ID: <32998.63.204.248.196.1007658787.squirrel@www.portablehole.net> (raw)
In-Reply-To: <1007633747.490.1.camel@djamil>

I doubt I have to mention this, but for the sake of "being careful" to make
sure the programs downloaded are finished before attempting to compile them.
:)  Would it be useful to be able to toggle parallel downloading/compiling?
Only case I can see it helpful would be with a fairly antiquated machine.

> I think the minimum we can do right now is:
> having the ebuilds work in a totally independant way , for example
> using a directory exclusivly.
> and/or why not "not" deleting the source tree, so other pakages can use
> the already compiled object files ...
> this is totally "doable" as the strong point of emerge is the fact that
> it doesnt use the shared database stuff ...
>
> thank you guys again for this giant work .
>
> D.
>
> On Thu, 2001-12-06 at 07:04, Mikael Hallendal wrote:
>> tor 2001-12-06 klockan 02.51 skrev Miguel S. Filipe:
>> > While reading this,  It reminded me of a thought i allready had.
>> >
>> > Why isn't portage more multi-task? What stops it from, while it's
>> > busy  building something, downloading the packages that its going to
>> >  (build/compile/install) next?
>> >  This would speed up the merging process for those with slow
>> >  internet
>> > connections, and it would not affect performance I believe. Is there
>> > any  problem with this? Is it just dificult to implement, or its
>> > much more  tricky and  problematic that it seems?
>>
>> This has been discussed, also the possibility to download all packages
>> before starting to build (so that you can disconnect before starting
>> to build).
>>
>> Even on a fast connection it would be very nice to have the
>> downloading being done while compiling.
>>
>> Regards,
>>   Mikael Hallendal
>>
>> --
>>
>> Mikael Hallendal
>> Gentoo Linux Developer, Desktop Team Leader
>> CodeFactory AB, Stockholm, Sweden
>>
>
>
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev





  reply	other threads:[~2001-12-06 17:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-03 22:12 [gentoo-dev] Evolution 1.0 in Portage Mikael Hallendal
2001-12-04 13:54 ` djamil essaissi
2001-12-05 15:39   ` Mikael Hallendal
2001-12-06  1:51     ` [gentoo-dev] Multiple emerges at the same time. ("multi-tasking" in portage) Miguel S. Filipe
2001-12-06  6:04       ` [gentoo-dev] multitasked emerge (download while build ...) Mikael Hallendal
2001-12-06 10:15         ` djamil essaissi
2001-12-06 17:13           ` jano [this message]
2001-12-06 17:53             ` Daniel Robbins
2001-12-06  6:41       ` [gentoo-dev] Multiple emerges at the same time. ("multi-tasking" in portage) Daniel Robbins

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=32998.63.204.248.196.1007658787.squirrel@www.portablehole.net \
    --to=jano@portablehole.net \
    --cc=gentoo-dev@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox