Lucas Nussbaum wrote:
> I don't know anything about mercury, but maybe it would be a better plan
> to package rotds, and find and fix bugs in them, instead of trying to
> get an old version in debian, and then switching to a brand new release
> just before lenny.
>
> Note that you could also decide to include a rotd in lenny, if upstream
> hasn't released anything by then...
>
> I think that the answer to that actually is "our priority is our users".
> What's the most useful choice for our users? ;)
Well, the most useful thing for users is to have a somewhat recent version of
Mercury ;-)
As for the release vs. rotd, I'm really in two minds on that - gcc-3.4 is very old (I thought I saw a post somewhere
suggesting that gcc-3.4 getting retired from Debian at some point, although I was unable to find the post when I went
back to look for it). Also mercury-0.13.1 is a year old, and the rotds are very good.
On the other hand, at least one of the reasons that the previous version of Mercury never made it to testing/stable is
that it got caught in the rotd versions - the maintainer didn't want a rotd ending up in stable. Also, as a user I use
0.13.1 for all my Mercury development, so it is at least a viable option.
If anyone else reads this (and I could check on the Mercury mailing list as well and ask the other users directly), I'm
open to suggestions on this.
There's also another delay on me spending time on this - I'm shortly going away
till end of Jan.
Cheers,
Roy Ward.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
