Re: Porteus, Sounds great, suggestion

On 7/8/03 5:24 PM, "Charley Bay" <[email protected]> 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.
> 

I don't quite follow here, you want all your builds running at same time?
What kind of machines you running on ;)

> * Peer2Peer, a local script, or some way to
> 'distribute' binaries.  In other words, if I have
> five identical machines, one machine should do the
> optimized build and then propagate the binaries to
> the other four machines (no need for additional
> build operations on the other machines, since they
> have identical hardware, and that should relieve some
> load from the distro server).  This is necessary for
> schools (25 machines in a classroom), and many
> businesses, and maybe embedded.
>

This has been on my scopes for a _long_ time and I assure you we will have
proper binary distribution methods, as well as local deployment capability,
etc.  I for one am very very dedicated to this type of functionally, and I'm
sure other devs are as well.  This type of stuff is essential to acceptance
in the corporate markets.

I've done this sort of thing for both my servers and workstations that ran
Gentoo for a long time, and in fact I built the only (to date) released
version of GRP for Gentoo (for both ppc and x86 arches .. The whole
shebang), so I have a pretty good handle on how (and how not) to approach
this stuff I think ;)

 
> * Better search support for packages, and maybe some
> 'header' block or better description of the contents
> in a package.   It's a minor issue, but it would
> be nice if 'emerge --search something' gave me a
> good 'header description' of what the package
> provides (text prose).  And, things like the Gentoo
> package distribution web site is fine if you already
> know what package you want, but it's not very easy to
> browse.

I wrote a tool for gentoo's portage, called portigate, that gives much more
advanced searching than emerge does...It allows you to search by almost any
of the metadata options portage tracks, directly from the portagedb.  I will
add my code for this into the donations for porteus, I'm sure we can get
most of that stuff working fairly easily, even still within python (time
permitting of course).  It's probably best if we spin the search tool off
into a separate entity from emerge.  I'm not sure how Jon feels on this one,
but I'll talk to him about it tonight and make sure he has access to the
code for it.

Mark (Gerk)