problems with options in pkg cluster builds.

[Jose M Rodriguez]

El Martes, 26 de Abril de 2005 21:56, Kris Kennaway escribió:
> On Tue, Apr 26, 2005 at 09:35:46PM +0200, Jose M Rodriguez wrote:
> > El Martes, 26 de Abril de 2005 21:25, Kris Kennaway escribi?:
> > > 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 spect.
> >
> > I'm using local patches.  And thinking in do the config and them
> > populate /var/db/ports from tarball in the beggin of the cluster
> > scripting.
> >
> > but this is really odd.
>
> You'll have to explain what problem you're seeing.
>

I can't be able to make pktools.conf and make.conf supersede ports 
default options from a fresh chroot cage without and /var/db/ports dir

Maybe my fault, but ... any clues?

--
  josemi
> Kris