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.
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?
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
SYNC { sync host. does bb have rsync?? }
LIST I'm not sure yet what this does
UPDATE { FETCH }
CLEAN What files does clean clean up, anyway?
Ben
> What I did with my apk (yes, i'd like to use embedded emerge if it was
> possible) was I added a Packages.sha1.gz file together with the binary
> packages.
>
> If there is a list containing all the packages, an index, it would be
> possible do something like:
>
> wget -O - $PACKAGE_PATH/Packagelist | grep "$PACKAGE-[0-9]*"
>
> Both the wget and grep code is included in busybox but I don't know if
> there is any gentoo policy saying that there should be included a file
> list in the binary repository.
>
> --
> Natanael Copa
>
--
Benjamin Collar
Siemens AG
CT SE 2
Embedded Linux
089-636-53711
--
[email protected] mailing list
