freetds: Move back to stable version

[stronk7 (Eloy Lafuente)]

With r99639 the freetds port was moved to 0.92.405

0.92 is a development version and 405 is already 1.5y old.

More yet, it has some important issues handling LOBs and restrictions about logging/debugging, that seem to be enabled by default, conflicting with any attempt to disable it @ freetds.conf. Also a lot of issues have been fixed since 405 till today, many of them backported to 0.91.

So this is a request to move back to 0.91 (stable version) point 103.

I've switched here, using it from MSSQL, and it really seems to be quicker and more stable.

For your consideration. The change is trivial. The only point is that it implies a "downgrade" (version.wise).

Ciao :-)

[stronk7 (Eloy Lafuente)]

s/using it from MSSQL/using it from PHP ;-)

[ryandesign (Ryan Carsten Schmidt)]

Thanks for letting us know. I didn't know 0.92.x wasn't stable. 0.92.402 is the "largest" version number in the ​stable downloads directory so if it's not actually stable then that's confusing.

If 0.92.x is not stable, then we can go back to 0.91.x, but doing so will require that the port's epoch gets increased. I'm also not sure yet how we'll construct a working livecheck for this situation.

[stronk7 (Eloy Lafuente)]

Yeah, it's confusing, and their recent move to git (​https://gitorious.org/freetds/freetds) did it really worse. But if you search 0.92 was never announced (​http://freecode.com/projects/freetds/releases) and if you look to any other distribution (homebrew, centos, debian... you will see that all them are using 0.91.x and 0.92 is only available like freetds-dev). We can ask in the mailing list too.

I think that, for some time... they were putting both 0.91 and 0.92 tgz in the stable directory... but then... then moved 0.92 to the current directory, keeping stable only for 0.91 (looking a t the dates and numbers).

About the livecheck, I'm sorry I don't know much (sure you are the doctor there, lol). Sounds to me that, perhaps, we could "hardcode" the 0.91 in the regexp, so only those are looked (but I really don't know how they are supposed to work). Something like: (0\.91\.\d+). Later, if 0.92 becomes released... it can be changed again.

I'm attaching an example that sets the portfile to 0.91.102 and, executing the livecheck with it, correctly detects that 0.91.103 is available, so seems to work. Again, I've no idea about all that stuff, be warned, lol.

Thanks and ciao :-)

[stronk7 (Eloy Lafuente)]

102 with simple livecheck detecting 103 existence.

[stronk7 (Eloy Lafuente)]

Offtopic: The new patch also deletes the ibiblio mirror, it seems to be really, really outdated, with the patched version being from 2012. (​http://mirrors.ibiblio.org/freetds/stable/)

[ryandesign (Ryan Carsten Schmidt)]

Thanks for the patch and for the additional information. I also found discussion on the freetds mailing list last year about this version number confusion, with no satisfactory resolution. I have composed a message to their list to ask them to please comment on it again, but cannot send it yet because my subscription to their list has not yet been approved. I'll wait to commit your patch until I have confirmation from the developers as to what the current stable version actually is. Note again that because the version number decreases, we will need to increase the epoch (from its default value of 0 to a higher value, such as 1).

[ryandesign (Ryan Carsten Schmidt)]

Yes we could hardcode the 0.91 branch in the livecheck, but the point of livecheck is to inform the maintainer when a newer version is available; hardcoding 0.91 would prevent us from learning when a later version such as 0.92 is stable. In my message I will ask the developers about this as well.

[ryandesign (Ryan Carsten Schmidt)]

​http://lists.ibiblio.org/pipermail/freetds/2014q2/028924.html

[ryandesign (Ryan Carsten Schmidt)]

r122219

[stronk7 (Eloy Lafuente)]

Cool, thanks!