Date: Tue, 26 Apr 2005 21:35:46 +0200 From: Jose M Rodriguez <josemi@freebsd.jazztel.es> To: Kris Kennaway <kris@obsecurity.org> Cc: Jose M Rodriguez <josemi@freebsd.jazztel.es> Subject: Re: problems with options in pkg cluster builds. Message-ID: <200504262135.48495.josemi@redesjm.local> In-Reply-To: <20050426192532.GA41681@xor.obsecurity.org> References: <200504260916.11192.josemi@redesjm.local> <20050426192532.GA41681@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
El Martes, 26 de Abril de 2005 21:25, Kris Kennaway escribi=F3: > On Tue, Apr 26, 2005 at 09:16:10AM +0200, Jose M Rodriguez wrote: > > Hi, > > > > I'm having problems with pkg cluster builds after latest changes to > > options code. > > > > I want force the way packages must be build from make.conf and > > pkgtools.conf, but seems that default config is chase due to > > options code. > > > > This is an automated build in a fresh chroot with PACKAGE_BUILDING > > and BATCH defined that used to work before. > > > > Any know method to disabled options code? > > > > Any hope that this change may be reverted and options processing is > > supressed when PACKAGE_BUILDING is defined? > > No, this was a deliberate change, so your port needs to accomodate > it. > There aren't my ports. I hate local patches. I Know this is deliberate. But it's not so simple to workaround as I=20 spect. I'm using local patches. And thinking in do the config and them=20 populate /var/db/ports from tarball in the beggin of the cluster=20 scripting. but this is really odd. =2D- josemi
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200504262135.48495.josemi>