At 04:54 PM 24/07/2005 +0200, you wrote:

>Hello,
>
>I wish to download 1.5.2 for FreeBSD, so I went to download page on
>firebirdsql.org and it says:
>
># 11th January 2005 Classic for FreeBSD/i386 5.2.1 V1.5.2 (.tbz) (2.2mb)
># 4th January 2005 Classic for FreeBSD/i386 5.2.1 V1.5.2 (.tbz) (2.2mb)
>
>I really see no difference there?

Typo 1 - fixed.

>Except that one link points to:
>http://prdownloads.sourceforge.net/firebird/firebird-1.5.2-fbsd51.tbz

Typo 2 - changed to -fbsd53

>And other to:
>http://prdownloads.sourceforge.net/firebird/firebird-1.5.2-fbsd521.tbz
>
>I guess this is the right one (I have FreeBSD 5.2.1 and 5.4 at hand),
>but someone could correct the web page.
>
>When I look via sf.net project page I see these three packages:
>http://prdownloads.sourceforge.net/firebird/firebird-1.5.2-fbsd48.tgz
>http://prdownloads.sourceforge.net/firebird/firebird-1.5.2-fbsd521.tbz
>http://prdownloads.sourceforge.net/firebird/firebird-1.5.2-fbsd53.tbz
>
>So, now I'm somewhat confused. What is the status of FreeBSD packages?

Here's what Chris Knight posted to firebird-devel when he uploaded these
builds on Nov. 11 last year:

"I've just updated the package list for the FreeBSD binaries. The files
are as follows:

firebird-1.5.2-fbsd48 - Firebird 1.5.2 for FreeBSD/i386
4.8/4.9/4.10/4.11/4-stable
firebird-1.5.2-fbsd521 - Firebird 1.5.2 for FreeBSD/i386 5.2.1
firebird-1.5.2-fbsd53 - Firebird 1.5.2 for FreeBSD/i386 5.3

The FreeBSD Ports Tree has also had the Firebird port updated to 1.5.2,
so the FreeBSD 4.11 CDs should contain a Firebird 1.5.2 package. This
also means you can roll your own package from the Ports Tree (which is
what has been done above)."

>Is this package for FreeBSD 5.3 ok?

It should be. People are not supposed to put "not-OK" builds into the
release area.

>What can I do if I want to run FreeBSD 5.4, should I build Firebird from
>source?

You need to ask that question on firebird-devel, where there's some chance
Chris Knight will see it. You might like to consider building it yourself
and, if it's successful, we can put it into the pre-release area.

./heLen