Hi,
>>"Jason" == Jason Gunthorpe <[EMAIL PROTECTED]> writes:
Jason> Baggage? Manoj :>
Sorry ;-)
Jason> PkgOrder would probably also be a good choice, but a dare say
Jason> that APT is a bit faster :>
That's true, and is probably more scalable because of the
memory mapping that you do. Mayeb you should consider supplying the
entry points like pkg-order provides to scripts? Like, read from the
stdin; commands like:
> load status /path/to/status-file
> load new /path/to/package/file
> order
> no-deps
and so one? In other words, allow simple manipulations to be
done to the data loaded, and return results as strings?
With that, I can fork a child, which sets stdin/stdout to
pipes, and execs the commandline interpreter, with the parent process
feeding commands to the interpreter, looking at the data output, and
feeding some more commands in. This would make apt very script
friendly.
If this sounds interesting, we can workout what commands can
be easily supported by apt. This may well finally kill off the need
for pkg-order.
manoj
--
One girl can be pretty -- but a dozen are only a chorus. Scott
Fitzgerald, "The Last Tycoon"
Manoj Srivastava <[EMAIL PROTECTED]> <http://www.datasync.com/%7Esrivasta/>
Key C7261095 fingerprint = CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
