Thread: postgresql-6.4.1.tar.gz

Hi,

it would have been a much cleaner solution to increment
the version number after realizing, that a wrong version
has been distributed.
To distribute another software with the same version
number - even if the wrong version was available only for 
a very short time - is definitely a no no.

Edmund
-- 
Edmund Mergl          mailto:E.Mergl@bawue.de
Im Haldenhau 9        http://www.bawue.de/~mergl
70565 Stuttgart       fon: +49 711 747503
Germany

[Charset iso-8859-2 unsupported, filtering to ASCII...]
> Hi,
> 
> it would have been a much cleaner solution to increment
> the version number after realizing, that a wrong version
> has been distributed.
> To distribute another software with the same version
> number - even if the wrong version was available only for 
> a very short time - is definitely a no no.

It was Marc's call.

--  Bruce Momjian                        |  http://www.op.net/~candle maillist@candle.pha.pa.us            |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026
 

> > it would have been a much cleaner solution to increment
> > the version number after realizing, that a wrong version
> > has been distributed.
> > To distribute another software with the same version
> > number - even if the wrong version was available only for
> > a very short time - is definitely a no no.
> It was Marc's call.

But still not too late to fix. I think Edmund has a very valid point. We
should be releasing v6.4.2 to eliminate any ambiguity in which version
people are running.

It is much easier to say: "If you are running v6.4.1, then kill it and
install v6.4.2."

This is important imho. Sorry I was out of town and not contributing to
the discussion earlier...
                        - Tom

Thomas G. Lockhart wrote:
> 
> It is much easier to say: "If you are running v6.4.1, then kill it and
> install v6.4.2."

BTW , 6.4.1 didn't solved the -lcrypt problem in Makefile for libpgtcl
:-(

I had to add it manually. I was testing that on two different computers,
with RedHat 5.1 and 5.2 versions, still the same problem.

As I recall, there was someone at a moment that claimed that the problem
was solved, he send me a patch and I tested it and it worked. Was that
patch included at that time ?

-- 
Constantin Teodorescu
FLEX Consulting Braila, ROMANIA