Re: SableVM + SableVM-CP future merge in one tarball or not?

On Sun, 2005-17-04 at 12:36 -0400, David Bélanger wrote:
> Hi,
> 
> Gentoo always put both SableVM and SableVM-Classpath in the same ebuild
> (build script) for this reason:
> # karltk: According to Grzegorz Prokopski (gadek), the two tarfiles will
> # merge
> # into one in the future. For now, they consistently make concurrent
> # releases,
> # so I merged them into one ebuild.
> 
> Would they be merged eventually or not really.

They will be, as soon as Etienne has time to fetch me some new vendor
branches (like libpopt, jikes etc.) and I have time to integrate them
into the "supertarball".  This is scheduled for end of April/beginning
of May at the latest.

I already have the part needed to make sablevm and sablevm-classpath
into one tarball (including working make distcheck) but I want yet
to see at least libffi and libpopt integrated into the sablevm.  I ran
into problems on distcheck while using libffi as a convenience library,
I had not time to work on it since then.

> I guess not because we have the CP CVS snapshot option?

No, why?  This option does not change anything.

> If not, it might be preferable two have two packages in the Gentoo
> world.

Please don't ;-)  I'll be much happier when we just have a single
self-containing tarball.  And so will be our users.  Just look at
the most common problems on sablevm-user: libffi, libpopt, jikes...

Hope this clarifies the issue,

			Grzegorz B. Prokopski
-- 
Grzegorz B. Prokopski           <[email protected]>
SableVM - Free, LGPL'ed Java VM  http://sablevm.org
Why SableVM ?!?                  http://sablevm.org/wiki/Features
Debian GNU/Linux - the Free OS   http://www.debian.org