From: | "Magnus Hagander" <mha(at)sollentuna(dot)net> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Zeugswetter Andreas DCP SD" <ZeugswetterA(at)spardat(dot)at>, "Bruce Momjian" <bruce(at)momjian(dot)us>, <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [PATCHES] vcbuild bison check |
Date: | 2006-10-04 14:38:01 |
Message-ID: | 6BCB9D8A16AC4241919521715F4D8BCEA35781@algol.sollentuna.se |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
> >> The point was, that >= 2.2 won't be allowed when it comes out
> for
> >> win32, even if it should work.
>
> > Right. So I'd update it once we see a working version other than
> 1.875.
>
> No, we should ship it that way to start with. Otherwise we're
> going to get caught with no released source code that will allow
> 2.2.
>
> A look at ftp.gnu.org says that 2.2 was released 19-May-2006 and
> 2.3 was released 05-Jun-2006. So it's not like these versions are
> fresh off the boat. I think it's safe to assume that someone will
> bother to compile them for Windows, probably sooner not later.
> We should be making sure our code works with them, rather than
> making sure it doesn't.
Ok. So what you want is something that checks that it's >=1.875 but
specifically not 2.1?
Might be a while before I can submit an updated patch for that, may need
to rewrite the whole script in perl to do that :-( .bat files are
horribly limited in what they can do.
//Magnus
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-10-04 14:41:22 | Re: [PATCHES] vcbuild bison check |
Previous Message | Tom Lane | 2006-10-04 14:35:26 | Re: [PATCHES] vcbuild bison check |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-10-04 14:41:22 | Re: [PATCHES] vcbuild bison check |
Previous Message | Tom Lane | 2006-10-04 14:35:26 | Re: [PATCHES] vcbuild bison check |