From owner-freebsd-ports@FreeBSD.ORG Thu Dec 2 05:35:21 2004 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2156A16A4CE; Thu, 2 Dec 2004 05:35:21 +0000 (GMT) Received: from hex.databits.net (hex.databits.net [216.118.117.77]) by mx1.FreeBSD.org (Postfix) with ESMTP id E513C43D49; Thu, 2 Dec 2004 05:35:20 +0000 (GMT) (envelope-from will@csociety.org) Received: by hex.databits.net (Postfix, from userid 1001) id 48AAA57AE2; Wed, 1 Dec 2004 23:35:20 -0600 (CST) Date: Wed, 1 Dec 2004 23:35:20 -0600 From: Will Andrews To: clement@FreeBSD.org, ache@freebsd.org, dinoex@FreeBSD.org, sumikawa@FreeBSD.org, ports@rbt.ca, kiwi@oav.net, se@FreeBSD.org, anders@FreeBSD.org Message-ID: <20041202053520.GX18619@hex.databits.net> Mail-Followup-To: clement@FreeBSD.org, ache@freebsd.org, dinoex@FreeBSD.org, sumikawa@FreeBSD.org, ports@rbt.ca, kiwi@oav.net, se@FreeBSD.org, anders@FreeBSD.org, ports@FreeBSD.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="jJVMc5+FiwMz9o91" Content-Disposition: inline User-Agent: Mutt/1.5.6i cc: ports@FreeBSD.org Subject: htpasswd split-out w/ HTTPD ports X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 05:35:21 -0000 --jJVMc5+FiwMz9o91 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, I am emailing you because you are a maintainer of a port which installs the htpasswd utility. This utility hasn't changed much in usage since the NCSA httpd days, but is still distributed with every HTTP server, causing needless conflicts. In particular, on my server I need both Apache 2 and thttpd installed. The *ONLY* thing that conflicts between the two is htpasswd and htpasswd.1. I assume there are other similar conflicts, but have not looked at them yet. Basically, this is a strawman implementation. To resolve this, I've created a patch for www/{thttpd,apache2} and made a new htpasswd port which uses the thttpd implementation (mainly for simplicity). Please see: http://firepipe.net/ports/htpasswd/ for my suggested method. At the very least, I would like apache2 and thttpd to cooperate (so I don't have to keep removing the stupid CONFLICTS every time I need to upgrade or install). I suspect it may be beneficial for others, but will leave it up to you all to decide. Please give me feedback regardless. Note that the apache2 and thttpd patches do not add a dependency on the htpasswd port, because I'm not sure if it's necessary. However, for POLA, they probably should be included. Thanks for your time. Regards, --=20 wca --jJVMc5+FiwMz9o91 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBrqmXF47idPgWcsURAjxyAJkBLa5rjxprcGn6uHcPinZl+28n4gCeKL2C 7MtaDPpW+Mx/9JdrMUMRhm4= =lYBk -----END PGP SIGNATURE----- --jJVMc5+FiwMz9o91--