On Mon, 24 Jul 2006 17:50:42 +0200 "Kevin F. Quinn" <[EMAIL PROTECTED]> wrote: | > As I said (and you seemed to have ignored), mandating tree access | > to use the vdb or a standalone binpkg repository == no go. | | I didn't ignore it - I didn't get it when you first said it. What | you're saying (?) is that to install a binpkg (for example), if the | tree is present it would resolve the category that the binpkg was | created under (that is now aliased) to the new category using the | alias data in the tree, and store stuff in the vdb under that new | category, purging out the entry in the vdb from the old category | (hence using tree data in the standalone case). Obviously this is | the correct behaviour when the tree is present. | | I'd suggest that in the absence of a tree, operations would assume no | aliasing (since all aliases at the time the vdb or binpkg were created | would already have been resolved), so the system state is still | consistent with the aliasing in force when the packages were built.
Won't work, which is a large part of why this thing isn't as simple as you're assuming. The only way of handling it correctly is to keep track, with *each individual binary / vdb entry*, of all the names that have pointed to it at any given time between when it was created and current... Think through all the cases involving alias changing, removing etc. There're rather a lot of them, and a solution that handles all said cases sanely is unfortunately not going to be anything like straighforward. -- Ciaran McCreesh Mail : ciaran dot mccreesh at blueyonder.co.uk -- gentoo-dev@gentoo.org mailing list
