Hi Gilbert,

I've setup src2pkg configs for courier-auth and courier-imap. The install line for both is 'make install-strip install-configure'.

From what I can see, the install-configure just takes a <name>.dist file and generates a <name> file. A diff on the 2 files show no changes.

However, when generating the package with src2pkg, it seems that it's a lottery as to whether the install-configure portion of the INSTALL_LINE is run or not. Any ideas?

Regards, Robby

I've had a look at the sources. The install-configure rule is using a perl script to install the configuration files. If the new files from the package are not the same as the old ones, then the old settings are folded into the new config file -commented out. But, it is all running with DESTDIR leading the path, so, the new config files would be put into the package unchanged. If you were installing directly with using no DESTDIR, then the code would be a great help to avoid trashing your configs. As it is, they are just copied into the new package. In order to make them work like normal config files with installpkg, you should add a line to the *.src2pkg script which renames them to include the '.new' suffix. This will keep them from overwriting existing configs on installation.
Depending on your src2pkg.conf settings, you may need to specify '-DEST' on the command-line as '-JAIL' doesn't work on these sources.

Strange that it sometimes works and other times not - weird. No matter, if the *.dist file exists then it can be overwritten. If the * file exists then it won't be overwritten as the file in the package is *.dist. That's ok with me ...