Re: RPM - Preventing uninstall and file conflicts.

On Wed, Nov 14, 2007 at 06:34:57PM -0700, Bob Proulx wrote:

> I want to emphasize that I think that list was all quite good!  I want
> to emphasize this because I am going to suggest that creating packages
> for configuration, while a solid and reliable system, is too heavy.
> Therefore I would not do it.  I think it is better to keep the scripts
> that configure the system in version control.  To be clear I think it
> is better to keep the scripts that set /etc/ config files in version
> control, not the /etc/ config files themselves in version control.

I fully agree, almost all of mt "config stuff" is scripting, not files,
but in the example I referred to example the original poster gave.

> I agree completely that using scripts to edit the configuration files
> on the machine is definitely the way to go.  But instead of putting
> them in packages I would have them in version control and have the
> system check them out from version control before running them.  The
> framework to implement this may certainly be put in a package and
> distributed that way.  But then when system changes are required I
> would make the changes in version control and let them propagate.

I agree that the contents of the package (scripts, spec file, etc.)
should be in version control, but I would use that subversion repo
(or whatever) as the source for building tarballs, that are the
source for your config RPM.  But there are many ways to deal with this.

-- 
--    Jos Vos <[email protected]>
--    X/OS Experts in Open Systems BV   |   Phone: +31 20 6938364
--    Amsterdam, The Netherlands        |     Fax: +31 20 6948204