It would be nice to add this in though so someone doesn't accidentally
take all that time and disk space compiling all for naught.
Thanks,
-Garrett
Isn't it already the default (except on current where it does not
run)?
Kris
Oh, duh.. forgot that it doesn't work on -CURRENT. I need to remove Java
support from OOo then ><..
Thanks Kris,
-Garrett
Gary,
See Kris's previous statement. I miscalculated that I was running
-CURRENT on my devel box and diablo-caffe hasn't been ported to
7-CURRENT yet.
All,
Is there some set of steps that are required for building diablo-caffe?
I wouldn't mind releasing some -CURRENT binaries if I could..
-Garrett
I agree++, but whom do we ``push''? AFAIK, we [FreeBSD users]
are pretty much a collection of volunteers albeit with some
$$$ contribs. Do we have a (barf) "Decider"!?
gary
> Thanks,
> -Garrett
> _______________________________________________
> freebs...@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-port...@freebsd.org"
--
Gary Kline kl...@thought.org www.thought.org Public Service Unix
> > I was just wondering if there was any way where we -- as a
> > group -- could push to make the default jdk / jre the diablo
> > packaged versions because frankly I don't want a system to assume
> > that I want to compile the 1.5 jdk / jre from scratch by first
> > installing the linux v1.4.2 of the jdk, and having to go through
> > the long and arduous process of compiling java, for little or no
> > benefit (the only benefit would be for different architectures
> > that aren't available in diablo-jdk/-jre, like sparc, powerpc).
>
> I agree++, but whom do we ``push''? AFAIK, we [FreeBSD users]
> are pretty much a collection of volunteers albeit with some
> $$$ contribs. Do we have a (barf) "Decider"!?
Let me suggest there be no "pushing". Bad organizational
karma.
There are two groups of people involved, both of which would
welcome a calm, well-considered proposition on this matter
(especially if it came with extra hands to do the work):
a) the folks who /provide/ Java(tm) in its various forms.
These can be found on the java@ mailing list.
b) the maintainers+committers of the ports that /use/ Java.
There are rather more of these:
huff@>> grep jdk /usr/ports/INDEX-7 | wc
426 16402 311797
(For the record, I'm a member of neither.)
Were I in your shoes, I'd start by _asking_ the folks on java@
why what you propose in not already the case.
No, I take that back: I'd start bu searching the (mailing list)
archives to see if this idea has surfaced before.
Robert Huff
The issue is that in 7.0 not all libraries have been bumped yet, even
though some of them are incompatible with their 6.x versions
(e.g. libthr/libpthread). So 6.x binaries that use those libraries
cannot run on 7.0.
I raised this issue again the other day and it's been investigated to
try and work out what the road blocks are, if any.
Kris