This is a discussion on Re: [stunnel-users] Moving binaries to /usr/bin within the Stunnel Users forums, part of the Networking and Network Related category; --===============1611641296== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="huq684BweRXVnRxX" Content-Disposition: ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
--===============1611641296== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="huq684BweRXVnRxX" Content-Disposition: inline --huq684BweRXVnRxX Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Sep 22, 2007 at 06:18:29PM +0200, Michal Trojnara wrote: > On Saturday 22 September 2007 07:50, Andrew Schulman wrote: > > > The Debian package of stunnel changed the default location of the > > > binaries, from /usr/sbin to /usr/bin. This is because we consider that > > > stunnel is not an admin only tool, but is useful to regular users (as > > > it does not require root privileges for several common use cases). > > > > I did the same in Cygwin (or maybe the previous packager did; anyway Cy= gwin > > puts the main executable in /usr/bin), for the same reason. >=20 > My comment to all port maintainers, if my opinion as the mainstream autho= r is=20 > somehow relevant: Indeed it is :) > I don't recommend implementing any changes that break mainstream=20 > compatibility. I agree with the idea. Unfortunately, I'm now sort of forced to do this because a) If I don't, I'll be breaking the LSB, and thus, Debian policy. =20 b) The change is already done (indeed, it was done by the previous maintainer quite a while ago). Changing it back now will just bring pointles breakage to users. Actually, the point of my mail was to see if I could stop carrying this divergence, by having the change incorporated here, upstream. I read your answer as saying 'no', and that's fine by me. The change has not been a support burden so far, so I will keep it. That's I think, the correct compromise, as it's Debian's (and not mainstream's) requirements I'm serving with it. --huq684BweRXVnRxX Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFG9Wc+AZmDGK3JvCgRAlTRAJ9b9TAefnAy9PO4gTKzSD p866MQPgCfQxaG Wi1r4/04O5mwjKlAesMtkp4= =qlzq -----END PGP SIGNATURE----- --huq684BweRXVnRxX-- --===============1611641296== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ stunnel-users mailing list stunnel-users@mirt.net http://stunnel.mirt.net/mailman/listinfo/stunnel-users --===============1611641296==-- |