HELP needed by experienced porter for simple review

Brooks Davis brooks at
Thu Dec 6 14:19:44 PST 2007

On Thu, Dec 06, 2007 at 10:22:06PM +0100, GP wrote:
>>> rc.conf
>>> It's a shame that I can't use a script placed in /files to change rc.conf
>>> during install/
>>> deinstall. I really liked that. But i guess I will settle with a dull
>>> pkg-message at the
>>> end, like the rest of you...
>> Well, no, it's not a shame.  The last thing we want to do as a community 
>> is enable all sorts of daemons that users don't know they have enabled. 
>> It's up to the owner of a box to enable a daemon **in the way** that they 
>> want it enabled.  For example, *none* of the daemons on my workstation 
>> listen for connections on its IP address - only on localhost.  If you 
>> enabled the daemon by default while installing the script, and I didn't 
>> have time to config it the way I wanted, and it got started (either by 
>> accident or by reboot) I would be pissed (not to mention possibly hacked.)
>> As porters our job is to make the software available for install *not* 
>> decide how or when it will be used.
> I principal I agree. My script asked if you wanted the lines added to 
> rc.conf or not.
> That can ofcause be a problem i you want to make install world or 
> something...
> But the current way is not very userfrendly - especially for non tech 
> desktop users.

If you really want to change this it would need to be done in a way that
all ports can use central infrastructure.  I'd probably be opposed to
having the prompting be part of the ports makefiles and propose putting
it in the various ports managment tools.  If we changed things so we
installed per-port defaults files those could serve as a template for
general tools to do automatic editing.

-- Brooks
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url :

More information about the freebsd-ports mailing list