Wneh having an ebuild with the same name in my local portage, using PORTDIR_OVERLAY, as in portage....when syncing the ebuilds are updated correctly in main portage tree, but the newly synced files from the files dir end up in local portage instead of main portage tree. THXS Brad Cowan bradlyatc@cowancomputers.com
Now if the versions are the same IMHO portage should always take the ebuild from the main portage tree also, but syncing should never be able to "see", or write to the overlaid "local"portage tree during syncing THxs
Can you give me an example of *exactly* what happens so I can look into this? The sync code doesn't have anything in it that even peeks at the local overlay, as far as I can remember.
Ok....here's what happened (note: I haven't tried to reproduce it) I was working on upgrading ebuild blah, and was working on it from my overlaid portage tree...after submitting the ebuild...when it went out to the mirrors I hadn't removed it from my overlaid portage tree, thus creating ebuild blah in both the main and overlaid portage trees. When I synced I ended up getting the updated ebuild script in my main portage tree, but all the files from the files dir of the ebuild from the main portage tree somehow synced to my overlaid portage tree ebuild files dir.
