Hello Ben, On Tuesday 15 Feb 2005 17:05, Benjamin Collar wrote: > On Tue, 2005-02-15 at 17:54 +0100, Natanael Copa wrote: > > This would require a comple list of all available packages. I guess a > > complete portage tree is out of the question for embedded. > > hmm. i was under the assumption (doh!) that the portage tree was there. > For this emerge.c, I need to have a better idea of what information is > actually available.
I'd guess you can't assume anything more than what's in /var/db/pkg and the
binpkg (the meta-data) itself.
> These are the "actions" I've so far defined for the emerge. What would
> be nice to know is, which data do each of these actions need, and where
> is this data found?
If I'm understanding you correctly, most of what you'll need will be in
ebuild.sh.
> FETCH { needs binhost, exact name & location of package ==> package
> index }
> UNMERGE { /var/db/pkg/$PN/CONTENTS }
> QUERY I'm not sure yet what this does
Query a package's installed state?
> SYNC { sync host. does bb have rsync?? }
I'm presuming this 'SYNC' action is for syncing the portage tree? Which will
most likely not exist.. Or is this for syncing binpkg's, a la 'FETCH' plus
more?
> LIST I'm not sure yet what this does
> UPDATE { FETCH }
> CLEAN What files does clean clean up, anyway?
Clean, as in remove an installed package.
Best,
Elfyn
--
Elfyn McBratney
http://beu.merseine.nu
beu on irc.freenode.net/savannah.[non]gnu.org
PGP Key ID: 0x69DF17AD
PGP Key Fingerprint:
DBD3 B756 ED58 B1B4 47B9 B3BD 8D41 E597 69DF 17AD
pgpVwIZnHVO4t.pgp
Description: PGP signature
