Zero_Dogg’s blog

CCP 0.3 is out! The major new feature in this release is the addition of automatic uncommenting support.
CCP will now try to detect which options the user has uncommented from –oldfile and automatically uncomment them in the resulting –newfile. This should *greatly* decrease the amount of oprhaned options that occurs. Also added is an automatic testsuite to avoid regressions between versions and a –bug option that outputs a file containing useful information that can help fix a bug or solve a problem.

CCP can be downloaded from http://ccp.nongnu.org/download.html

This version contains multiple bugfixes, some which could cause various configuration files to not upgrade correctly. Among others, it fixes bug #15364.
In other news, the first package using CCP in Mandriva is out – which is squirrelmail :)

CCP version 0.1 has been released!
It can be downloaded from http://ccp.nongnu.org/download.html.

It’s also in Mandriva Linux (cooker) contrib.
The first package to use it is squirrelmail, which I updated today.

CCP can now autogenerate the templates, so it’s pretty much ready for real-life testing.
Here’s the same example used in earlier posts.

[0 zerodogg@drizzt ccp]$ cat example.conf
# Example configuration file
SystemVersion = 0.1
Mode = public
Extensions = off

[0 zerodogg@drizzt ccp]$ cat example.conf.rpmnew
# Example configuration file
SystemVersion = 0.1
Mode = private
Extensions = on
AllowUsers = yes

[0 zerodogg@drizzt ccp]$ ./ccp --oldfile example.conf --newfile example.conf.rpmnew
Merging changes between "example.conf" and "example.conf.rpmnew"...done

[0 zerodogg@drizzt ccp]$ cat example.conf
# Example configuration file
SystemVersion = 0.1
Mode = public
Extensions = off
AllowUsers = yes
[0 zerodogg@drizzt ccp]$

CCP (as I wrote about earlier) now has a project on savannah. It now works! It can be downloaded from the CVS repository.
However, it doesn’t use libconf yet, and thus only supports key = value files. It also doesn’t know how to create the templates by itself so those have to be written by hand for now (but this should be easy(ish) to implement I think).

Like i said it currently supports key = value files. Any format will do. It can for instance handle any of the following:

$Key = Value;
$Key=Value
$Key='Value'
$Key="Value"
$Key ="Value"
Key = Value
Key=Value
# Comment
: Comment
; Comment
[Section header that gets ignored]

It doesn’t support comments on the same line as a config option, but this can probably be added at some later time.
I haven’t written any documentation yet – but here’s the same usage sample I used before (edited to suit the way ccp now works).

/etc/example.conf:

# Example configuration file
SystemVersion = 0.1
Mode = public
Extensions = off

/etc/example.conf.rpmnew:

# Example configuration file
SystemVersion = 0.1
Mode = private
Extensions = on
AllowUsers = yes

/usr/share/example/config.ccptemplate:

# Example configuration file
SystemVersion = {CCP::CONFIG:SystemVersion}
Mode = {CCP::CONFIG::Mode}
Extensions = {CCP::CONFIG::Extensions}
AllowUsers = {CCP::CONFIG::AllowUsers}

Command:

$ ccp --template /usr/share/example/config.ccptemplate --oldfile /etc/example.conf --newfile /etc/example.conf.rpmnew
Merging changes between "/etc/example.conf" and "/etc/example.conf.rpmnew"...done

Resulting /etc/example.conf:

# Example configuration file
SystemVersion = 0.1
Mode = public
Extensions = off
AllowUsers = yes