What is policy about auto-editing config files on port install / deinstall?

Miroslav Lachman 000.fbsd at quip.cz
Wed Jan 2 20:47:17 UTC 2013


Is somewhere written policy or portmgr recommendation about ports 
behavior on install / deinstall?
I am talking about some ports doing "nasty" things.

Some ports are stopping services on deinstall, some not.
Some ports are editing "my config files" on deinstall, so even on 
upgrade procedure I must check if port did some changes before I can 
restart target daemon.

For example some Apache modules (mod_bw, mod_xsendfile...) are 
commenting out load_module lines in httpd.conf so I got syntax error on 
Apache restart after upgrade of mentioned module and Apache failed to 
start.

These inconsistencies are really boring.

I know it is made by AP_GENPLIST, but not all modules are using it and I 
think it is really bad idea to touch user's config files this way.

I prefere not to change my files in any way (on install and on 
deinstall), just print message "what should user do". Because this 
auto-editing is doing more problems than benefits on each upgrade.

Miroslav Lachman


More information about the freebsd-ports mailing list