From: | "Chuck McDevitt" <cmcdevitt(at)greenplum(dot)com> |
---|---|
To: | "Andrew Dunstan" <andrew(at)dunslane(dot)net> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Problem with MSVC install script |
Date: | 2007-09-24 06:59:54 |
Message-ID: | EB48EBF3B239E948AC1E3F3780CF8F8802A1B27F@MI8NYCMAIL02.Mi8.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Well, I was checking out from a different cvs server, and had things set
to use CVS EDIT, where everything is read-only by default, until you
issue a cvs edit command.
So many files that aren't built by the build system, but just get copied
as-is, end up read-only.
But it would be true for any files set read-only.
> -----Original Message-----
> From: Andrew Dunstan [mailto:andrew(at)dunslane(dot)net]
> Sent: Sunday, September 23, 2007 7:45 PM
> To: Chuck McDevitt
> Cc: pgsql-hackers(at)postgresql(dot)org
> Subject: Re: [HACKERS] Problem with MSVC install script
>
>
>
> Chuck McDevitt wrote:
> >
> > I was trying out the msvc support, and ran into a minor problem in
> the
> > install.bat/install.pl
> >
> > If any files that are going to be installed are marked read-only,
> they
> > carry the read-only attribute with them when they get copied to the
> > install dir.
> >
> > Then, if you try to run install again, the new attempt will fail
> > because it can't overwrite the read-only file.
> >
> > I added this like to install.bat (just before the call to
install.pl)
> > to fix this for me:
> >
> > attrib /S -r %1\*
> >
>
>
> Which files are read-only?
>
> cheers
>
> andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2007-09-24 07:33:23 | Re: Problem with MSVC install script |
Previous Message | Brendan Jurd | 2007-09-24 06:33:22 | Bytea as C string in pg_convert? |