Packages with diablo dependencies
Greg Lewis
glewis at eyesbeyond.com
Sun Feb 22 00:10:34 PST 2004
On Sat, Feb 21, 2004 at 11:46:00PM -0800, Kris Kennaway wrote:
> On Sun, Feb 22, 2004 at 12:39:07AM -0700, Greg Lewis wrote:
> > On Sat, Feb 21, 2004 at 11:35:54PM -0800, Kris Kennaway wrote:
> > > On Sat, Feb 21, 2004 at 11:25:39PM -0700, Greg Lewis wrote:
> > > > On Sat, Feb 21, 2004 at 04:48:47PM -0800, Kris Kennaway wrote:
> > > > > It looks like 51 ports now depend on the diablo ports to build; this
> > > > > means the packages cannot be built on bento, since the diablo packages
> > > > > are interactive and impossible to build there. Can you please do
> > > > > something about this?
> > > >
> > > > Last time this came up I volunteered the attached patch. Does it fix the
> > > > problem or not? I didn't hear whether it did or didn't. If it does fix
> > > > the problem I'll commit it. If not, can you suggest a variable the package
> > > > install script can test for to workaround things on bento?
> > >
> > > Well, I modified bento to set that variable in the build environment,
> > > and now it just hangs:
> > >
> > > [...]
> > > this Agreement which, in Foundation's opinion, reasonably preserves
> > > the intent of this Agreement. This Agreement is binding upon and
> > > shall inure to the benefit of Foundation and its successors and
> > > assigns. This Agreement represents the entire understanding of the
> > > parties, and superceded all previous communications, written or
> > > oral, relating to the subject of this Agreement.
> > >
> > >
> > > Do you agree to the above license terms? [yes or no]
> >
> > If it gets here its gotten too far. The idea of the patch was to bypass
> > this for bento.
> >
> > Are there _any_ special environment variables that bento sets when its
> > installing the packages for a build? All we need is something which
> > the package install script and test for and say "Ok, this is bento".
>
> I mentioned above that bento now sets PACKAGE_BUILDING in the build
> environment.
My bad. But obviously this isn't passed to the package install script
as it would exit before the licensing agreement if that environment setting
was passed on. Maybe pkg_add runs the scripts with a different
environment?
--
Greg Lewis Email : glewis at eyesbeyond.com
Eyes Beyond Web : http://www.eyesbeyond.com
Information Technology FreeBSD : glewis at FreeBSD.org
More information about the freebsd-java
mailing list