galeon 1.3.13a released - requires some work on the ebuild due to decompressing to galoen-1.3.13a folder. I haven't been able to come up with a clean solution for this.
Yeah, I really dislike how they name their releases. Here's a fixed ebuild for galeon-1.3.13a, please test.
Created attachment 26058 [details] galeon-1.3.13a ebuild
To fix the source directory naming problem, I did this: S="${WORKDIR}/${PN}-${PV/a}" I also had to comment out the 'intltoolize --force' line. It wouldn't build for me with it in there.
I decided to try it again with the 'intltool' line and it worked, can't say why. It's been about five days and several 'emerge -uUDv world's since I built it last (1.3.13a came out on 17 Feb) so maybe an update had something to do with it. Anyway, the old ebuild seems to work by simply redefining ${S}.
I'm confused. This ebuild requires the addition of one line to bump it to galeon-1.3.13a, which was released on 17 February. Yet it languishes, seemingly with no interest. But I know that there are still quite a few of us galeon users around. Meanwhile, mozilla-1.7_alpha, released two days later, showed up with my last rsync. So an ALPHA release with a 612 line ebuild can be written and tested before one that needs a single value to be redefined? That's what I don't get. I'm not suffering, since I can take care of myself, but there must be plenty of others that could benefit.
sorry this took so long, galeon 1.3.13a has been bumped in portage.
Thank you. And I see your better way of handling ${S}. Another lesson learned.
