istinnjazz wrote:what is the aufs layer priority in that case?
order is: base modules first , user modules, then changes
each layering on top of the last, potentially overwriting an underlying file..
so, yes changes takes priority..
istinnjazz wrote:Is there a possibility that might be a conflict?
yes, this could present a problem..
running #pacman -Syu
will complain of duplicated database entries if package(s) are in more than one place(modules or changes)
if it also wants to upgrade that package it/they can probly be removed from the changes folder using :
#pacman -R --root=/path/to/changes <package(s)>
(i think thats the right command)
as opposed to just pacman -R <package> which will put whiteouts in the changes folder(which effectively removes the package completely from the live system)
istinnjazz wrote:what about a clean function for the savefile that can remove some old outdated duplicated files that are older than core?
but beyond my feeble scripting abilities...
istinnjazz wrote:So if savefile has previous versions of the updated core files will the system know and refine this?
the system knows nothing..