Bug 25877 – portage should run `sync` after every merge

• Product: Portage Development
• Status: RESOLVED FIXED

[Description SpanKY 2003-08-04 08:34:27 UTC]

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

[Comment 1 Jason A. Mobarak (RETIRED) 2003-08-04 08:39:14 UTC]

I'll talk to Nick about this as I'm not sure where to add this.

[Comment 2 SpanKY 2003-08-04 16:45:25 UTC]

Created attachment 15510 [details, diff]
emerge-sync.patch

unless i'm mistaken i believe this is where it goes

[Comment 3 Patrick Kursawe (RETIRED) 2003-08-04 22:52:43 UTC]

I don't get the idea why having something emerged should be treated different from saving any file... how often does your box die?

[Comment 4 SpanKY 2003-08-05 20:41:17 UTC]

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 ! 

[Comment 5 SpanKY 2003-08-05 23:57:07 UTC]

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

[Comment 6 Brian Harring (RETIRED) 2004-08-17 00:54:36 UTC]

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.