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, Pennsylvania 19026
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
My feeling (not that anyone asked) is that if one bit changes after an
official release, then it's necessary to change the release name
*somehow*. I'm at the ready to update the web site if Marc makes 6.4.2
or 6.4.2.1 or 6.4.1-bis or whatever...
The Hermit Hacker <scrappy@hub.org> writes:
Show quoted text
If you guys are *sure* you want to do this, let's do it...tag what is
required, let me know when done, I'll package up a new one and put it out,
removing v6.4.1 and then Hal can make appropriate changes to the rest of
the site :(
Import Notes
Reply to msg id not found: TheHermitHackersmessageofMon28Dec1998153152-0400ASTReference msg id not found: Pine.BSF.4.05.9812281529410.351-100000@thelab.hub.org | Resolved by subject fallback