public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-amd64@lists.gentoo.org
Subject: [gentoo-amd64]  Re: Sun and GPL
Date: Mon, 28 May 2007 17:46:05 +0000 (UTC)	[thread overview]
Message-ID: <pan.2007.05.28.17.46.01@cox.net> (raw)
In-Reply-To: 20070528071415.415b75f1@mandalor.homelinux.net

"Conway S. Smith" <beolach@comcast.net> posted
20070528071415.415b75f1@mandalor.homelinux.net, excerpted below, on  Mon,
28 May 2007 07:14:15 -0600:

> Last I heard, Gentoo/FBSD was stalled, due to licensing terms.  But it
> was some time ago, has that changed?

I don't believe it's stalled now.  Among other things, Roy is designing
Baselayout-2 to be friendlier to Gentoo/FBSD.  Baselayout-2 is a pretty 
recent development, and definitely still masked as it's still in serious 
development.  (FWIW, I've been running 1.13.0_alphaXX for some time, 
since it was hard masked tho it seems to be ~arch now, but I've not tried 
2.0 yet, at all.)

The worst recent blow, AFAIK, was when Flameeyes quit, as that was his 
baby (well, one of them, he was incredibly productive all over the 
place).  Fortunately, he's back, but taking it a bit slower this time, 
mainly focusing on GFBSD.

BTW, his blog at http://farragut.flameeyes.is-a-geek.org/ has some very
interesting entries re the thread topic, and this subthread, and gcc
as well.

First, his latest entry explains a bit about coming back (the links
include date and title):
http://farragut.flameeyes.is-a-geek.org/articles/2007/05/27/shedding-a-light-on-my-return

Second, back on the second page, he discusses his work on OpenJDK.
He's mainly interested in getting it to work for GFBSD since the
FBSD version is old and vulnerable, but he's getting it working
on Gentoo Linux first.  Apparently, it DOES compile on amd64, but
may require a bit of tweaking due to path lengths.  Anyway, worth
reading for anyone following the GPLv2ing of Java, particularly
as it applies to Gentoo and specifically, Gentoo/amd64.

Three entries:
http://farragut.flameeyes.is-a-geek.org/articles/2007/05/09/openjdk-and-gentoo-freebsd
http://farragut.flameeyes.is-a-geek.org/articles/2007/05/10/my-fiddling-with-openjdk
http://farragut.flameeyes.is-a-geek.org/articles/2007/05/15/openjdk-the-vulnerabilities-and-you

Finally, as one who has unmasked gcc-4.2.0 locally, and recompiled
my entire system (that'll work with it, I've about a half-dozen
packages that won't), this entry on gcc 4.3 and the problems
it's going to cause is interesting:
http://farragut.flameeyes.is-a-geek.org/articles/2007/05/11/gcc-4-3-it-will-be-a-bloodshed

Hmm... the g2planet RSS feed doesn't seem to be carrying flameeyes
blog again yet.  Having just read a bunch of it, and found
all that interesting stuff, I'm going to have to rss-feed it directly...

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

-- 
gentoo-amd64@gentoo.org mailing list



  reply	other threads:[~2007-05-28 17:49 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-26 19:07 [gentoo-amd64] Can I run a complete desktop remotely? Mark Knecht
2007-05-26 19:37 ` Olivier Crête
2007-05-27 15:40   ` Mark Knecht
2007-05-27 15:56     ` Peter Davoust
2007-05-27 16:04     ` Richard Freeman
2007-05-27 16:56     ` YoYo Siska
2007-05-26 19:49 ` Aleksey Kunitskiy
2007-05-26 19:53 ` Conway S. Smith
2007-05-26 20:29   ` Simon Cooper
2007-05-26 22:24     ` Conway S. Smith
2007-05-26 21:47   ` Nuitari
2007-05-26 22:20     ` [gentoo-amd64] " Duncan
2007-05-27  0:00       ` Duncan
2007-05-26 22:51     ` [gentoo-amd64] " Conway S. Smith
2007-05-27  6:48       ` Joerg Gollnick
2007-05-27 10:57         ` Richard Freeman
2007-05-27 11:11         ` [gentoo-amd64] Sun and GPL Isidore Ducasse
2007-05-27 23:32           ` [gentoo-amd64] " Duncan
2007-05-28  0:41             ` Isidore Ducasse
2007-05-28  3:42               ` Wil Reichert
2007-05-28  6:12                 ` Naga
2007-05-28  3:56               ` Boyd Stephen Smith Jr.
2007-05-28  9:25                 ` Richard Freeman
2007-05-28 10:42                   ` Boyd Stephen Smith Jr.
2007-05-28 10:56                     ` robert burrell donkin
2007-05-28 11:52                     ` Duncan
2007-05-28 16:23                     ` Hemmann, Volker Armin
2007-05-28 17:28                       ` Nuitari
2007-05-28 11:14               ` Duncan
2007-05-28 13:14                 ` Conway S. Smith
2007-05-28 17:46                   ` Duncan [this message]
2007-05-28 18:38                     ` [gentoo-amd64] Baselayout 2 (Was: Sun and GPL) Sebastian Redl
2007-05-28 22:56                       ` [gentoo-amd64] " Duncan
2007-05-29  0:50                         ` Wil Reichert
2007-05-30  0:33                           ` Florian D.
2007-05-30  4:09                             ` Joshua Hoblitt
2007-05-30  4:38                               ` Wil Reichert
2007-05-30  7:39                                 ` Duncan
2007-05-30  7:43                                 ` Isidore Ducasse
2007-05-30 22:57                                 ` Joshua Hoblitt
2007-05-30  9:12                               ` Florian D.

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=pan.2007.05.28.17.46.01@cox.net \
    --to=1i5t5.duncan@cox.net \
    --cc=gentoo-amd64@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox