5 Feb 09:17
Re: GCM release
Philip Van Hoof <spamfrommailing <at> freax.org>
2003-02-05 08:17:35 GMT
2003-02-05 08:17:35 GMT
On Wed, 2003-02-05 at 03:57, Will LaShell wrote: > Heya, I'm looking at all the packages for the 5th toe release and I'm > checking out gcm. All I can say is -WOW- I love it. This thing is > -cool- We so need it out there and talked about. Great work man. Okay, I am very glad that you like the application. Tells me that I did not make this application for nothing> There are a couple of problems I'm seeing though. First when I opened > the tarball, the configure script didn't work. The symlinked libtool and > automake scripts will not work. End users and package compilers will > need local copies of those tools in the release. I would be more than happy if somebody with the proper knowledge of buildscripts could help me. If you see fixes that you can do then do not hesitate to contact me and provide patches. > Do you think you can fix this up and make a new release? The next release that I will be responsible for will be the 2.1.0 or unstable release. I don't know if this release will get packages by the packagers (debian and redhat). I will also maintain the next stable branche called 2.2.0. This branche will be developed in parallel with 2.1.0 of course. When a first release of 2.2.0 will be finished: I don't know
this highly depends on the amount of contributions and people wanting to help me. At this moment I am the only active developer of the package .. and I can tell you that it is becoming a lot of code to manage. -- -- Philip Van Hoof <spamfrommailing <at> freax.org> ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com
> There are a couple of problems I'm seeing though. First when I opened
> the tarball, the configure script didn't work. The symlinked libtool and
> automake scripts will not work. End users and package compilers will
> need local copies of those tools in the release.
I would be more than happy if somebody with the proper knowledge of
buildscripts could help me. If you see fixes that you can do then do not
hesitate to contact me and provide patches.
> Do you think you can fix this up and make a new release?
The next release that I will be responsible for will be the 2.1.0 or
unstable release. I don't know if this release will get packages by the
packagers (debian and redhat). I will also maintain the next stable
branche called 2.2.0. This branche will be developed in parallel with
2.1.0 of course. When a first release of 2.2.0 will be finished: I don't
know
RSS Feed