On Friday, April 03, 2015 8:52:18 AM Stroller wrote: > > On Thu, 2 April 2015, at 4:37 pm, Grant Edwards <grant.b.edwa...@gmail.com> wrote: > > > > I prefer it this way. I do not want all the nice easy-to read/edit > > configuration stuff in /etc/portage encrypted some Windows Registry > > break-alike. > > What's bad about the Windows registry is that its proprietary file format is both poorly constructed (or, rather "lacking design") and obscure, and its reputation was for brittleness was built when it was stored on FAT file systems and corrupted when Windows crashed and had to be hard rebooted.
And that it became a central repository for *everything*, it wasn't too bad as just a COM registry on Windows 3.11. Microsoft's been pushing developers to use config files for years but they themselves keep using the registry poorly. Install the latest visual studio, then uninstall it and search your registry. You will find over 20,000 registry entries left behind. > If you want to store a lot of stuff, then databases are a valid solution. If there's something wrong with sqlite or BerkeleyDB then argue against them, but don't base your objections on a strawman. I agree that a binary db for portage is a good idea, only because it's ridiculous how long it takes portage to resolve dependencies. It could be just a cache that gets rebuilt after syncing or updating config files. -- Fernando Rodriguez
