>> > Mark some files in ${sysconfdir} as configuration files so they are
>> not blindly overwritten when upgrading
>>
>> I would suggest a pre-/post processing in the packages, like debian
>> does.
>> If a config file exists or is changed, the current File will be
rotated
>> or, if possible, left as it is and the new
>> file is installed beside the changed one.
>The opkg does not touch a present config file, but installs the new
file with the name *-opkg
>So if you do a find /etc -name \*-opkg you see the conflicts.
>Any sensible conversion from old to new config file should be made by
the package itself.
As I experienced, opkg exits with an error code if a config file already
exists, so if you want to create an image, the process will break at
that error.
It wasn't possible to create an image automatically then.
_______________________________________________
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
