Huie-Ying Lee writes:
> I can change the relevant lines as below, if that looks better.
>
> #Port forwarding
> #AllowTcpForwarding yes
I think it's a little less surprising that way, so I prefer it, but
now that I understand the project a good bit better, it's not a
significant issue.
> > Why not just change the way it installs, so that it installs as
> > "AllowTcpForwarding yes" by default, and leaves it unchanged on
> > upgrade or patch?
> >
> >
> Right, that's our goal also. What would be the right release binding ?
Patch/micro is the right release binding. What's missing is the
description of how the delivery will work. Something like this:
Since we're changing a default value, and we want to avoid
suprise on upgrade, and since we can't tell whether a user has
intentionally configured the "no" value or whether it was just
left at the default, we will do the following for the patch
delivery:
- If the system is initially installed from freshbitted
packages containing this change, then the system will have
AllowTcpForwarding set to "yes" by default. The release
notes for the release containing this change will note the
difference.
- When upgrading or patching an existing system (installed
before this fix was introduced), the AllowTcpForwarding
value will not be changed. A release note (for the update
release) and README for the patch will be included to tell
users what to do if they want the new value.
--
James Carlson, Solaris Networking <james.d.carlson at sun.com>
Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
