On Tue, 2005-02-15 at 10:56 -0500, Ned Ludd wrote: > On Tue, 2005-02-15 at 16:25 +0100, Benjamin Collar wrote: > > Hello list > > > > just wanted to let you know: I didn't drop off the earth. I worked on > > the emerge.c a little this weekend. So far I've been learning a bit of > > busybox's structure, planning the emerge.c, and integrating some of > > busybox's api. Nothing worth testing so far, though. > > If you mail me offlist what you have so far I can bbify it and send it > back to you. > > > Next week I'll have some vacation, so I'll have time to work on it. > > >
> > I have a question, though: what's the INDEX file? I don't exactly find > > one on my system, and I'm not sure what I'm supposed to be doing to > > update it. Any hints? > Sadly I've learned new info about the file known as INDEX. portage no > longer uses this if I understand the python portage developers right. > It now uses some has data stored in a metadata.idx that's cpickle > format. This is useless to us as it's python compiled bytecode or other. I just filed a bug for the inclusion of flat text INDEX files. It's a one liner change to ebuild.sh bug #82132 This will give use the means to take our PORTAGE_BINHOST from our mini make.conf fetch the INDEX (--list a set of pkgs we can fetch/install) -- Ned Ludd <[EMAIL PROTECTED]> -- [email protected] mailing list
