On 2007-10-31 11:03, "Brian A. Seklecki" <[EMAIL PROTECTED]> wrote: >On Wed, 2007-10-31 at 13:54 +0200, Giorgos Keramidas wrote: >>On 2007-10-30 18:02, "Brian A. Seklecki" <[EMAIL PROTECTED]> wrote: >>> >>> As far as building goes, the variables in play are: >>> >>> DESTDIR, MAKEOBJDIRPREFIX, RELEASEDIR, CHROOTDIR, CVSROOT, >>> EXTSRCDIR, EXTDOCDIR, BUIILDNAME, RELEASETAG, NODOC, NOPORTS, >>> WORLD_FLAGS, LOCAL_SCRIPT >>> >>> For stage one of the release process, the following seem relevant: >>> >>> DESTDIR, MAKEOBJDIRPREFIX, RELEASEDIR >>> >>> For stage two: >>> >>> CHROOTDIR, CVSROOT, EXTSRCDIR, EXTDOCDIR, BUIILDNAME, RELEASETAG, NODOC, >>> NOPORTS, WORLD_FLAGS, LOCAL_SCRIPT >>> >>> Do you guys prefer to set these in make.conf(5) or as exported >>> environmental variables in the shell that spawn's make(1) ? >> >> make.conf is too invasive. I just set them in a shell script called >> `bldenv.sh' and saved in the release-checkout area :) > > I ask because I noticed that the following variablkes do not get > honored by "make release" that occurs inside the chroot() as spawned > by "make release" (presumably during release.5) > > DESTDIR, MAKEOBJDIRPREFIX, RELEASEDIR > > For example, OBJs get sent right into $CHROOTDIR/usr/obj/, which > really sucks.
I believe that's intentional, so re-running "make release" with different CHROOTDIR values will produce consistently "similar" binaries. _______________________________________________ firstname.lastname@example.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"