Re: mercury: should this package be removed?
I filed the initial ITA, but have then been unable to make much progress because of other commitments (including being
overseas for a while).
Unfortunately, although I'm back now, unforeseen personal circumstances mean I won't be able to do anything in the
immediate future (next 2-3 weeks at least) either, and getting something releasable would be later than that.
If someone wants to adopt it, please do, and I'll help as much as I can. Otherwise I _will_ get to it, but it may not be
for a while.
As for the gcc-3.4 vs. gcc-4.1, I'd had a good look at that, and it depends which version:
The Release Of The Day does indeed compile with gcc-4.1
The latest release (0.13.1) which was the one I was looking at packing (to avoid a ROTD ending up in stable) does not -
it does require gcc-3.4 (there's only a couple of places where it is broken under gcc-4.1/gcc-4.2, but it would take
someone with more knowledge than me to fix that).
I use 0.13.1, but the version to package depends on:
* when there is going to be another release (I don't know this)
* whether most current users use 0.13.1 or ROTD (I don't know but can find this out).
Cheers,
Roy Ward.
Barry Freese wrote:
Hi folks,
Sorry for all of the CCs but all of you have expressed interest in
fixing/adopting this package (with the exception of QA).
Do any of you still have an interest and/or a plan to fix this
package? According to the Mecury website, it is supposed to build with
gcc-4.1 which would be a hell of a lot better than gcc-3.x.
Is that not the case? This thing has been orphaned a while and has an
RC bug over a year old. If no-one wants to fix it up, I will request
removal within the week.
If I can help with packaging or fixing this thing, please feel free to
contact me and will gladly help if I can. Otherwise it's a goner. :-)
Thank you!
Barry deFreese
Reply to: