On Sat, Apr 09, 2005, Michael van Elst wrote:
> On Fri, Apr 08, 2005 at 03:48:17PM -0700, Mark Keller wrote:
>
> > Even if the config files are compatible between versions. It seems that at
> > least those two groups do a really good job of not changing config files
> > between minor and compatible revs. So we don't have to worry as much about
> > our config file getting clobbered. I don't think that is happening in the
> > openpkg rpm world.
>
> Possible, but that can be verified.
>
> If you track current I guess changes to the config files happen often
> as current just imports whatever config files are delivered by the
> 'vendor'.
Yes, that's the "price" for being on the bleeding edge ;-)
> If you update from one release to the next you will see even more
> drastic changes.
...and then it should be no problem if a manual intervention is required
as a release upgrade is always nothing one can expect to be 100%
painless although we try hard to make it as smooth as possible. Having
to resolve config file issues in this case is harmless as with a release
upgrade one is also primarily confronted with functionality changes of
the vendor products, etc.
> If you stay within a release and only install updates (i.e.
> security fixes et al) then, IMHO, there must not be any issue
> with config file updates.
Yes, it is even guarrantied that UPD-ate packages are 100% compatible
and can be applied without any manual intervention, including resolving
of any config file issues. That's why we always backport security
fixes to exactly the vendor version which was included in a release
and we never do an upgrade especially because of those potential
incompatibilities.
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
______________________________________________________________________
The OpenPKG Project www.openpkg.org
Developer Communication List openpkg-dev@openpkg.org
