/var/db/pkg/${CATEGORY}/${PACKAGE} directory contains many useful for debug purposes data. For example: # ls -1 /var/db/pkg/dev-db/tora-3.2-r2/ BDEPEND BUILD_TIME CATEGORY CBUILD CFLAGS CHOST CONTENTS COUNTER CXXFLAGS DEFINED_PHASES DEPEND DESCRIPTION EAPI environment.bz2 FEATURES HOMEPAGE INHERITED IUSE IUSE_EFFECTIVE KEYWORDS LDFLAGS LICENSE NEEDED NEEDED.ELF.2 PF PKGUSE RDEPEND repository REQUIRES SIZE SLOT tora-3.2-r2.ebuild USE But this set is not complete. I suggest to extend saved ebuild with patch files, applied during installation. From FILESDIR and userpatches (in the same or different archive).
/var/db/pkg is package-manager private data; portage is storing data there that it needs to enable various functions. It doesn't need patches in filesdir stored in the vdb to function, so they are not stored. Sure we can store the patches in the vdb but then I'd ask "what purpose does this serve for portage?" What functionality is being enabled by it? -A
(In reply to Alec Warner from comment #1) > /var/db/pkg is package-manager private data; portage is storing data there > that it needs to enable various functions. It doesn't need patches in > filesdir stored in the vdb to function, so they are not stored. > > Sure we can store the patches in the vdb but then I'd ask "what purpose does > this serve for portage?" What functionality is being enabled by it? > > -A I was confused with human-readability of data in /var/db/pkg/… For these purposes applied patches is useful addition. For automatically proceed (machine readable data) portage internal metadata it is useless.
I think this is pretty much a duplicate of bug 303403, although bug 303403 has some utility (being able to re-emerge stuff). *** This bug has been marked as a duplicate of bug 303403 ***
