--EVF5PPMfhYS0aIcm
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Jul 15, 2005 at 04:11:45PM +0200, Hubert Feyrer wrote:
>=20
> On Fri, 15 Jul 2005, Allen Briggs wrote:
> >I'm inclined to say that there should be a transition period where
> >vnconfig is a hard link to vndconfig.  I don't run the command by
> >hand, but it seems that the name change is not strictly necessary,
> >and I'd hate to break scripts, etc., by removing vnconfig immediately.
> >At least make a mention of it in a public place (CHANGES or something)
> >and provide some time (a release cycle?) for the transition.
>=20
> I see that we move things around all the time, without providing backward=
=20
> compatibility. And it was suggested to rename vnconfig to vndconfig to=20
> match the driver's name (vnd(4)), so the thing was mis-named in the first=
=20
> place, and I won't jump through even more hoops to get this done.

Wait. You're saying we should do something because it's the right thing=20
(naming the program vndconfig), but in the same breath you're saying you=20
won't do something that is also the right thing (making a transition=20
point)? That's not very nice. :-)

I think the renaming is the only thing I object to in all of this.

> Of course I intend to make an entry in src/doc/CHANGES that it was=20
> renamed, and I'll even go into src and htdocs and change all places (I'm=
=20
> tempted to start rambling about how others don't change documentation whe=
n=20
> code changes...).
>=20
> As an alternative, I can leave it at vnconfig.

How about this as an alternative (assuming my make syntax is right :-) :

LINKS=3D	${BINDIR}/vnconfig ${BINDIR}/vndconfig
MKINKS=3D vnconfig.8 vndconfig.8

I'm not sure if you need to include bsd.links.mk. I suspect it's already=20
included.

I'm not at all opposed to having vndconfig. I'd like that. A lot. However=
=20
we've had "vnconfig" since NetBSD 1.0, and I think we should continue the=
=20
name. Given that keeping it only costs a dirent worth of disk (for the=20
second link), it's rather cheep.

I also would like us to keep the original source files around. I'm a big=20
fan of revision history. While it may not matter for these files, we do=20
have 29 revisions for the man page and 32 for the program. I'd rather they=
=20
stay where we can easily find them. :-)

Take care,

Bill

--EVF5PPMfhYS0aIcm
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (NetBSD)

iD8DBQFC1/WfWz+3JHUci9cRAhZpAJ94py0edVj6UmxLe9HaruQ/rEALNwCfbsaI
7B9kdhK8UCFLxglK5LpuDP8=
=PNCb
-----END PGP SIGNATURE-----

--EVF5PPMfhYS0aIcm--