Re: Porteus, Sounds great, suggestion

Daniel Armyr wrote:
 >>> charley bay wrote:
 >>>
 >>>> * Ability to define a 'que' or 'bundle' of a set of packages so
 >>>>  we don't have to wait for one 'emerge' to complete before
 >>>> starting the next.
 >>>
 >
 > Oh, was that what you meant with the above. When I heard the word
 > queue, I thought about the ability to queue up ebuilds while one is
 > building. The situation would be as follows: I start emerging
 > ebuild1, a very large ebuild I realise I also want ebuild2. I tell
 > emerge to emerge ebuild2 as soon as ebuild1 is done. The next day I
 > have both ebuild1 and ebuild2 installed.
 >
 > While I am writing a letter, I would like one feature added to the
 > specs: It should be safe to run more than one emerge at the time.
 > This should be a documented feature, and to implement just requires a
 >  bit of care in how files are written and read.

These features could be easily added by creating a client/server
architecture for the package manager. A front end would send requests to
a server (doesn't have to be long-lived), which would process the
requests in the appropriate order.  Such an engine could then serve for
our autobuilding system, and possibly even for a P2P auto-building
system for stageballs and ISOs.

While these are very long term goals, I also want these features and
even know how to implement them... now we just have to spec it.... ;)

Cheers,

Zach