On Wed, 2020-12-16 at 00:48 +0000, Ken Moffat wrote: > I've been building a lot of blfs with jhalfs. but because the > filesystem is only 25GB I figured that at various stages I should > tar up the system so that I could revert to an earlier, less full, > system. That went ok, so after looking at texlive etc (10GB in > itself) I restored to a system with xorg, fluxbox, xfce, and the > epiphany, firefox and seamonkey browsers. > > Now I need to see which packages I have not yet tried to build. > > Easy, I thought: cat the various instpkg files and look for the > package names, then look at Config.in to see the total names for > MENU and CONFIG items, then for each package see if it was already > installed in one or other of the builds. > > That eventually seemed to be working, but the number of packages was > rather fewer than I'd guessed. So I looked at what was installed > and saw that firefox was not there, but also not in the list of > packages still to install. > > So I took another look at Config.in. That had last been updated on > 10th December before the run where I had added epiphany (that, and a > large number of other scripts, were in the scripts/ directory). > Looking at it, the graphweb items in Config.in only showed epiphany > and falkon. > > At that point I went back in to the menu, selected nothing, and it > decided that (only) epiphany was a target. Going with that, I've > now got all of epiphany, falkon (done in a separate kde run), > firefox and seamonkey showing up in Config.in. > > Now I have 1017 CONFIG_ items in BLFS Config.in (including LFS and > MENU items), my script now reports 736 items done, 209 still to do > which sounds a lot more likely than less than 400 already done. > > I'd noticed once or twice when trying brief configurations in the > menu that an old target would show up as TARGET0, but after going > back in it cleared itself out, unsure if that is related to this (or > maybe Config.in is supposed to only show items which have not been > installed ?). > > Is there any way to *force* Config.in to get refreshed/regenerated > to show everything ? >
Normally Config.in is regenerated when running make, if either: - the instpkg file has changed (this happens each time a package is successfully built) - one of the books has changed (as a result of "make update" or editing it) - in the rare cases where one of the .xsl files or other utility script has changed in the blfs_root tree. Of course, if you just run "make", Config.in is regenerated, but then the menu is displayed. If you just want to regenerate Config.in, type "make $(pwd)/Config.in" (the $(pwd) is needed because this is how the target is defined in the Makefile). Not sure about your "TARGET_0" observation. Normally, if Config.in has changed, and you save the configuration when exiting the menu, this shouldn't happen. Note that packages.xml has the whole list of packages (with their dependencies, which is another story), there is one tag "inst-version", which is present if the package is installed, and not present if the package is not installed. packages.xml gets regenerated in the same cases when Config.in is. Again, you can issue "make $(pwd)/packages.xml", if you just want to regenerate it. Enjoy :) Pierre -- http://lists.linuxfromscratch.org/listinfo/alfs-discuss FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
