Mike Auty wrote:
Yeah,
I agree that the updates should only affect that individual tree.
Whilst I can imagine cases where a move in the main tree should affect
overlay trees (such as recategorizing some net-misc ebuilds into a
net-proxy category), that could at least be emulated with a per-tree
move directive fairly easily.
It sounds as though the answer is that there currently no way to do
these kinds of moves, so what's the next step? Should I try and hack up
a version to deal with updates on a per tree basis? Is it actively
being developed and I'm just unaware of it? What can I do to help get
this feature into a future version of portage? It would be very useful
to have, because at the moment network administrator's can't quite use
overlays as a software management mechanism...
Thanks for you time,
As currently vdb/pkgdir don't track the repo where a package comes from
it's not possible to do it in a proper way (those are affected by moves,
not the repositories themselves).
Marius
--
gentoo-portage-dev@gentoo.org mailing list
