Date: Tue, 20 Jan 2004 14:03:11 -0500 From: Joe Marcus Clarke <marcus@FreeBSD.org> To: Marius Strobl <marius@alchemy.franken.de> Cc: Oliver Eikemeier <eikemeier@fillmore-labs.com> Subject: Re: HEADS UP: New bsd.*.mk changes Message-ID: <1074625391.757.86.camel@gyros> In-Reply-To: <20040120194157.K93730@newtrinity.zeist.de> References: <1074590694.85583.20.camel@shumai.marcuscom.com> <400D2939.5090203@fillmore-labs.com> <1074617147.757.16.camel@gyros> <20040120171315.GH94636@FreeBSD.org> <1074619795.757.43.camel@gyros> <1074621917.757.61.camel@gyros> <20040120194157.K93730@newtrinity.zeist.de>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-LxU0hTc24QenD9MuJ2co Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Tue, 2004-01-20 at 13:41, Marius Strobl wrote: > On Tue, Jan 20, 2004 at 01:05:17PM -0500, Joe Marcus Clarke wrote: > > On Tue, 2004-01-20 at 13:02, Marius Strobl wrote: > > > On Tue, Jan 20, 2004 at 12:29:55PM -0500, Joe Marcus Clarke wrote: > > > >=20 > > > > I agree. This approach seems the most flexible. As for not being = able > > > > to do non-root installs, this is a bogus argument as one could simp= ly > > > > override PORT_DBDIR as they would PKG_DBDIR (even with the original > > > > patch). > > > >=20 > > >=20 > > > I was taking about non-root builds, e.g. single ports checked out > > > outside of PKGBASE to do maintenance work, not non-root installs. In > > > an environment where non-root installs are done your argument is vali= d. > > > Not being able to do non-root builds compilcates the job of maintaine= rs. > >=20 > > As I said, non-root builds could override PORT_DBDIR the same way you > > could override PKG_DBDIR. You could point that to a directory to which > > you could write. What am I missing? > >=20 >=20 > In general I'd like to further on be able to build a port as non-root > and install als root, with default PREFIX, PKG_DBDIR and PORT_DBDIR. Ah, I follow you. > I don't see how this currently should work, if I set PORT_DBDIR to a > directory I can write to before I build the port as non-root it won't > neither read an existing OPTIONSFILE in the default location nor write > a possibly changed OPTIONSFILE to the new location. I could move around > the OPTIONSFILE before and after installing the port but that's really > messy. > At a first glance I don't see a reason why creation of PORT_DBDIR if > not already existing and writing of the OPTIONSFILE can't be done in > e.g. the fake-pkg target or a new target that's executed directly > before or after fake-pkg. This may work, but it would require some reworking of the existing architecture, and, depending on patch complexity, may require another test build on bento. Did you have something specific to review? Joe --=20 Joe Marcus Clarke FreeBSD GNOME Team :: marcus@FreeBSD.org gnome@FreeBSD.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome --=-LxU0hTc24QenD9MuJ2co Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQBADXtvb2iPiv4Uz4cRAtZtAJ98EbWFhitGuz50KtIOZEM+JM5vkwCdGejC 82ADPfj03jOPjpJBfQAKo/Q= =kLtq -----END PGP SIGNATURE----- --=-LxU0hTc24QenD9MuJ2co--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1074625391.757.86.camel>