Hi. To demonstrate this issue first let's look at what happens when webapp-config-1.11 is invoked as such on a "clean" setup: # webapp-config --list-installs Fatal error: No virtual installs found for *-* Fatal error(s) - aborting OK, that's not a very nice message but it's expected behaviour with this version of webapp-config. Now let's see what happens when we do the same with a clean install of webapp-config-1.5.11: # webapp-config --list-installs * Fatal error: "/var/db/webapps" specifies no directory! webapp-config needs a valid directory to store/retrieve information. Pease correct your settings. * Fatal error(s) - aborting Why isn't this directory either automatically created by the ebuild or created on the fly by the WebappDB class in db.py? And what settings are there to correct? The directory appears to be hard-coded in the constructor. I don't see any reason why a user should have to attend to this before the tool works properly. So, I'm requesting to have a "keepdir /var/db/webapps" call in the ebuild itself. I suggest "keepdir" instead of "dodir" becuase if "keepdir" isn't used then I think the following scenario could occur (similar to bug 107756): 1) emerge webapp-config clean, /var/db/webapps is initially created and is empty 2) Later re-emerge webapp-config where /var/db/webapps is empty (for whatever reason) 3) Because /var/db/webapps exists but is empty and "keepdir" isn't used, portage will think it's OK to remove the dir and so we end up with the same problem all over again!
Absolutely valid point. Added keepdir in cvs. Thanks for the report!
