in the off chance that a box should die soon after a successful emerge, i think it would be good to have portage make sure that all data has been synced with the harddrive ... the slight lost in performance would be highly beneficial imo over the chance that a bunk emerge is actually considered 'valid' by portage. note, i mean run sync after portage has qmerged, written /var/db/pkg/, and all that stuff ... so that is (1) call to sync per package
I'll talk to Nick about this as I'm not sure where to add this.
Created attachment 15510 [details, diff] emerge-sync.patch unless i'm mistaken i believe this is where it goes
I don't get the idea why having something emerged should be treated different from saving any file... how often does your box die?
i see it as a higher reliability factor and i make my box die pretty often ... i seem to have a knack for making 'stable' boxes not so stable, regardless of OS :) i demand a lot !
it seems to be working on my box ... i put a little print right after the sync call and every time ive emerged a package i see this: >>> sys-apps/reiserfsprogs-3.6.11 merged. SYNCING DISK ! :D >>> sys-apps/baselayout-1.8.6.10 merged. SYNCING DISK ! :D >>> app-crypt/keylookup-2.2 merged. >>> Recording app-crypt/keylookup in "world" favorites file... SYNCING DISK ! :D
Current version is a lil scary for people doing parallel merges (world file is read once, outside of the mergelist loop), but your request is in portage.
