From owner-freebsd-ports@FreeBSD.ORG Sat May 22 16:13:08 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 99C9616A4CE for ; Sat, 22 May 2004 16:13:08 -0700 (PDT) Received: from mtaw4.prodigy.net (mtaw4.prodigy.net [64.164.98.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3BB5A43D2F for ; Sat, 22 May 2004 16:13:08 -0700 (PDT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (1d6486f6e6d7623d543355252cb6d53d@adsl-67-115-73-128.dsl.lsan03.pacbell.net [67.115.73.128]) by mtaw4.prodigy.net (8.12.10/8.12.10) with ESMTP id i4MN2n7l003346; Sat, 22 May 2004 16:02:50 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 87392524A8; Sat, 22 May 2004 16:02:48 -0700 (PDT) Date: Sat, 22 May 2004 16:02:47 -0700 From: Kris Kennaway To: Rod Taylor Message-ID: <20040522230247.GA91261@xor.obsecurity.org> References: <1085247019.3359.913.camel@jester> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="5mCyUwZo2JvN/JJP" Content-Disposition: inline In-Reply-To: <1085247019.3359.913.camel@jester> User-Agent: Mutt/1.4.2.1i cc: freebsd-ports@freebsd.org Subject: Re: Default Passwords 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: Sat, 22 May 2004 23:13:08 -0000 --5mCyUwZo2JvN/JJP Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, May 22, 2004 at 01:30:20PM -0400, Rod Taylor wrote: > I've been working on porting Bricolage. Normally, the Bricolage make > process asks a large number of questions of the user. I can cut 90% of > those out (ports tree answers most) but there are a few that I'm not > sure what to do with. >=20 > One of those is the issue of a default password for the "bric" user > which connects to the database. Do I simply set the port to > IS_INTERACTIVE and allow it to ask the above question or are there > tricks to avoid it altogether? Things like passwords are usually done manually as post-install customization, e.g. editing the config files. If your port is going to be made into a package you have to do it this way anyway, since packages may not be interactive. Kris --5mCyUwZo2JvN/JJP Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAr9wWWry0BWjoQKURAiK3AJ9KdcbORCpg26yToPPTqLbaP51DIQCdGRjK f+G4CcuYH0GYE607/zL1tbY= =sURY -----END PGP SIGNATURE----- --5mCyUwZo2JvN/JJP--