On 10 Jul 2001 21:26:29 +0200, Christoph Egger wrote:
>
> On Tue, 10 Jul 2001, Christoph Egger wrote:
>
> >
> > Hi!
> >
> >
> > It's done: Code freeze!!
> >
> > Eric has committed the ChangeLog files.
> >
> > I have tagged libgii with 'version_0_8' (CVS doesn't allow
> > version_0.8, because of the '.'-char) and libggi with
> > 'version_2beta4'.
> >
> > So for everyone, who wanna help out with the packaging process: Get a
> > clean source from CVS. Both cvs update and cvs checkout has a param
> > known '-r <rev>', where <rev> is 'version_0_8' for libgii and
> > 'version_2beta4' for libggi.
> >
> >
> > Let's start NOW!! It's now Tue Jul 10 19:07:27 UTC 2001 as of this
> > writing.
>
>
> Now I have two source tarballs (libgii and libggi).
>
> I have called them as libgii_0.8.src.tar.bz2 and
> libggi_2.0b4.src.tar.bz2.
More common is libgii-0.8.src.tar.bz2 and libggi-2.0b4.src.tar.bz2, but
I don't care that much.
> Is the filename ok or is it somehow confusing?
>
> I start creating two binary tarballs for Linux/i386.
>
> Brian: Would you like to create binary tarballs for Linux/Alpha?
>
> Thayne: Would you like to create rpm's ?
The rpm spec files really need to be integrated into CVS and be a part
of autogen and the source tars. Binaries are quite questionable
because of varieties of platforms and library combinations. Source
tar's with included spec files or SRPMS are nearly 100% portable if
done right. The best way to do binary distributions is with staticly
linked files . . . it just doesn't work with the way GGI is setup.
> Anyone here, who creates debian packages for any platform?
>
>
>
> CU,
>
> Christoph Egger
> E-Mail: [EMAIL PROTECTED]
--
Thayne Harbaugh
