Hello Natanael,
>
> Paul Traina mentioned some issues with the current apkg (lrp) format:
>
>
>> 2) It's insanely tedious to upgrade the software because the configs
>> are still stored with the binaries, and there are no tools for merging
>> diffs between the configs (e.g. ucf).
>
> What I have been trying to with Alpine, is to sparate the local backup
> of the configs from the package manager. Completely. This opens for
> switching to any package manager. I could use deb, ipkg, whatever.
>
> To do the backups of the configs, I am thinking CVS/SVN. Add a file to
> the local backup list and later commit it to floppy or usb stick.
>
> So, you install a package:
> ipkg install shorewall
>
> add the config files to the "local backup list": lbu_add /etc/shorewall/*
>
> And then you store your configs to floppy:
> lbu_commit floppy
>
> lbu_add and lbu_commit are wrapper scripts. the backend could be other
> scripts that mount the media (usb drive or floppy) or it could be a
> subversion/cvs repository.
>
> The "local backup" is not several lrp's but one tar.gz archive for
> everything. Simplifying what goes where. (where should /dev/dsp be backed
> up?)
>
> preferrible this should be wrapped into a script.
>
> ----
> pkg-install:
> #!/bin/sh
>
>
> $INST="ipkg install"
>
>
> $INST $1
>
>
> lbu_add `cat /var/lib/lrpkg/$PKG.list` ----
>
>
> Or something like that. I havent wrapped it yet, but you get the idea.
> By wrapping it, you can easy change package manager later.
>
>
> Then during boot, Alpine installs all packages read from a package list
> (a plain textfile) and after installing all packages, it looks for the
> local backup file and unpacks it if found. This happens before any services
> are started.
>
> Yes you do lose, having the configs in separate files but you solve alot
> of other things.
>

There is a very big problem with seperating the configs from the packages
itself. You loose the consistency between the two. For example, if you
update shorewall from version 2.x to 3.x (where the format of config files
change), shorewall won't work anymore. Also with other programs config
files, formats and items change between releases.

An other, maybe less important problem is that when you "try" a package
the config file of that package will polute the local repository of config
files (after you delete the package, the config files are still present)
while with config inside a package this won't be the case.

Eric



-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642

_______________________________________________
leaf-devel mailing list
leaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/leaf-devel

Reply via email to