Re: [AQT-dev] Releasing Tarballs.

[Mojca M. <moj...@gm...>]

Dear Donald,

On Thu, May 24, 2012 at 4:32 PM, Donald Curtis wrote:
> When new releases are made, would it be possible to put a source tarball in there as well.  It would be very helpful for incorporating AquaTerm into Mac Homebrew (http://github.com/mxcl/homebrew).

It's really nice to get an email from homebrew community, because I
planned to contact you anyway.

Per was very busy lately and didn't have much time to work on
AquaTerm. I would have requested inclusion of 1.1.0 into
MacPorts/Homebrew, but it had two ugly bugs that seemed a show-stopper
to me.

Recently Alexander and me fixed both, so I've been working on a new
release. The problem is that I don't have sufficient rights to change
anything on sourceforge. I only have commit rights for CVS and for one
of Git repositories (which would need modification, but I'm not
allowed to "git push -f" either).

I've transferred sources to
    http://github.com/AquaTerm/AquaTerm
I have made a stub webpage
    http://aquaterm.github.com/
and a test binary prerelease for 10.6 yesterday
    https://github.com/AquaTerm/AquaTerm/downloads
(I'll try to compile the final binary for 10.5)

I have never officially been part of AquaTerm development team, but I
would like to keep it alive for at least some more time, and Per
doesn't have any time to work on it. My current wishlist for the
release would be the following:
a) figuring out how to build some basic documentation
b) prepare a slightly better webpage, change references to point to
github instead of sourceforge
c) change references on sourceforge and maybe upload files there as
well (but I don't have sufficient rights for that)

And also (lower priority, for 1.1.2 maybe):
- fix compiler warnings (there are many for which I'm not sure what they do)
- put AquaTerm.xcodeproject on top level and make some basic directory
structure (I would need hints or more extensive testing to make sure
that I would get that right)

A wishlist for distributors contains the following:
a) don't make $prefix/lib/libaquaterm*.dylib
b) don't make $prefix/include/aquaterm/*
but fix gnuplot instead. See:
    https://github.com/mojca/gnuplot/blob/mojca2/m4/apple.m4

But I would need a few other slightly more experienced developers to
take a look at my modifications to gnuplot, test them in different
scenarios, propose any changes, and then help requesting the change in
gnuplot upstream.

I would be grateful if you would test the version of AquaTerm from
github and provide any feedback (and maybe a link to the recipe), so
that we could do other modifications if needed before release.
Hopefully you should not need any patches to build AquaTerm. If you
do, please ask.

Do you still need *.tar.gz files with sources now that AquaTerm well
be hosted on github?

(I have created a package for MacPorts, but didn't get any feedback
about it yet.)

Mojca

PS: I'm curious how one can build AquaTerm with command line tools
only (as Homebrew claims that command line tools should be enough). Is
that possible at all, or does one need additional
modifications/patches to avoid xcodebuild?