Hi Am 01.11.2014 um 04:58 schrieb cpu memhd: > The ability to backup symbolic links and empty directories was never part of > apkg. Therefore, one would have to create them on the fly during bootup. > That's how I used to do it. > > The other improvements are: > > a) expandpath always ended up being /// when you passed it /, and would give > you double slashes in other situations. Also it did not handle "" as a valid > path, which should be--and now is treated as ".".
This is interesting, as I was preparing a few fixes for apkg on similar
goals, especially getting rid of unnecessary constructs in that IMHO
rather messy code. I willl have to start from scratch then.
this is my proposed expandpath()
#
# expandpath2 IMHO better
#
expandpath2 () {
case $1 in
/*) echo $1;;
*) echo `pwd`/`echo $1 | sed -e s/^[.][/]*//` | sed -e
s/[/]$// ;;
esac
}
>
> c) upgrade() now handles symlinks and empty dirs and very importantly, now
> commits only on confirmation at the very end.
OK
>
> Before, because of the interactive nature of upgrade it was possible to end
> up with a partially upgraded package because of a lost ssh session, or if you
> messed up while merging there was no ability to back out.
I am preparing a backup scenario which will allow to have a complete
secondary boot. I was doing this manually for a number of years but got
tired of this.
I don't like upgrade as the code has very little comments and appears to
be very static. I would like a process where we would publish all
packages along with the kernel images and initrd ( one version including
initmod ) for each arch for at least the most recent version. That way
an existing installation could be tailor made upgraded without hasssle
(hopefully)
>
> d) rundiff() now reflects symlink and empty dir changes.
> -jorge
>
>
Thanks for the details, does anything change for the user except for the
empty directory stuff?
cheers
Erich
smime.p7s
Description: S/MIME Cryptographic Signature
------------------------------------------------------------------------------
_______________________________________________ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
