Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 30 Nov 2003 17:46:21 +0100
From:      Melvyn Sopacua <freebsd-current@webteckies.org>
To:        richardcoleman@mindspring.com, Andreas Klemm <andreas@FreeBSD.org>
Cc:        Kris Kennaway <kris@obsecurity.org>
Subject:   Re: 5.2-BETA and related ports issues
Message-ID:  <200311301746.27134.freebsd-current@webteckies.org>
In-Reply-To: <3FCA12B3.7070604@mindspring.com>
References:  <200311281553.hASFrURT003309@siralan.org> <20031130084800.GA64364@titan.klemm.apsfilter.org> <3FCA12B3.7070604@mindspring.com>

next in thread | previous in thread | raw e-mail | index | archive | help

--Boundary-02=_j7hy//Jkwam58mH
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Sunday 30 November 2003 16:54, Richard Coleman wrote:

> But it doesn't help if you need a port to start earlier than something
> in the base.  This could happen if you've replaced sendmail with
> postfix, and use maps from a remote database (openldap, postgresql,
> etc).  I'm sure there are other examples as well (nss_ldap, etc).

Then you can just as easily nuke the entire mailer.conf principle and symli=
nk=20
bin/postfix to etc/rc.d/050.postfix.sh.
Point being: these are customized setups that require skill to get even=20
remotely working, so one can assume that the person installing the port can=
=20
read instructions given in pkg-message.

I don't think any ports/package system is capable of correctly setting all=
=20
*runtime* dependencies especially when it allows it's users to change=20
configurations after installation without recording the changes back into t=
he=20
ports/pkg system.

However - to allow this flexibility, the ports system should try to respect=
=20
the installation prefix.
Nothing prevents a port from entering "If you need ${PORTNAME} to start bef=
ore=20
foo, symlink ${PREFIX}/etc/rc.d/${PORTNAME}.sh to /etc/rc.d/ and make sure=
=20
it's lexically sorted before foo" into pkg-message.

Then the statement in UPDATING can read:
find /etc/rc.d \! -type l -print | xargs rm -vf

and it will always apply.

Perhaps the patch below (or something similar) should be added as well to m=
ake=20
people aware of the local_startup system.

My 2c.
=2D-=20
Melvyn

=2D-- bsd.port.mk.orig	Sun Nov 30 17:22:22 2003
+++ bsd.port.mk	Sun Nov 30 17:29:21 2003
@@ -766,6 +766,9 @@
 #				  apply here.  It is recommended that you use
 #				  %%PREFIX%% for ${PREFIX}, %%LOCALBASE%% for
 #				  ${LOCALBASE} and %%X11BASE%% for ${X11BASE}.
+# INSTALLS_RCSCRIPT - If set, bsd.port.mk will check if ${LOCALBASE} is eq=
ual
+# 	 			  to ${PREFIX} or else suggest that ${PREFIX}/etc/rc.d should
+# 	 			  be added to local_startup in /etc/rc.conf
 # DOCSDIR		- Name of the directory to install the packages docs in
 #				  (default: ${PREFIX}/share/doc/${PORTNAME}).
 # EXAMPLESDIR		- Name of the directory to install the packages examples in
@@ -3127,6 +3130,10 @@
 	@${MKHTMLINDEX} ${PREFIX}/lib/X11/doc/html
 .endif
 .endif
+.endif
+.if defined(INSTALLS_RCSCRIPT) && ${LOCALBASE} !=3D ${PREFIX}
+	@${ECHO_MSG} "You should verify if ${PREFIX}/etc/rc.d is in local_startup"
+	@${ECHO_MSG} "in /etc/rc.conf or /etc/defaults/rc.conf"
 .endif
 .endif
=20

--Boundary-02=_j7hy//Jkwam58mH
Content-Type: application/pgp-signature
Content-Description: signature

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

iD8DBQA/yh7jOv9JNmfFN5URAigWAJ0SOdf6edIvZYQ+dtIGohlggEiXrgCfcY+V
EAP8MIO8zCuAV6SgCu6CAf0=
=+bCf
-----END PGP SIGNATURE-----

--Boundary-02=_j7hy//Jkwam58mH--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200311301746.27134.freebsd-current>