On Sat, Aug 28, 2010 at 11:21:10AM +0200, martin f krafft wrote: > If this is the case, then the database should be moved from > /var/lib/apt-xapian-index to /var/cache/apt-xapian-index, as > specified by the FHS. > > Otherwise, the database will e.g. be backed up (my backup tools > ignore /var/cache, but not /var/lib), which is just a waste.
The database itself should be moved to /var/cache/apt-xapian/index indeed. The rest of /var/lib/apt-xapian-index should not, though. Now, the strategy. When doing a non-incremental rebuild, update-apt-xapian-index creates a new dir, /var/lib/apt-xapian-index/index.N, and when the rebuild is finished it atomically updates /var/lib/apt-xapian-index/index to point to the new index, then it removes the old indices. The trick to a smooth move could be to have it create the new indices in /var/cache/apt-xapian-index/index.N, then removing the old indices both in /var/cache and in /var/lib. The advantage to that is that the point of entry to the index does not change (/var/lib/apt-xapian-index/index), so we gain proper FHS usage with a fully transparent migration. There is going to be some careful testing to do, though. Ciao, Enrico -- GPG key: 4096R/E7AD5568 2009-05-08 Enrico Zini <enr...@enricozini.org>
signature.asc
Description: Digital signature
