[Mono-dev] xbuild

[Gladish, Jacob]

But it's a pretty straight forward use case. I sync my code from revision control. In this particular case, I'm using perforce. Perforce brings files down from the depot read-only. To edit, you must "check out" files. My log configuration is sync'd up read only. I build and the file gets moved into the output directory. I build again and it fails. I cannot confirm how msbuild on windows is dealing with this, but it definitely allows it.

My opinion is that since this is not some random file, but a file that the build is being asked to create, it should get overwritten. It's certainly a usability issue.


> -----Original Message-----
> From: Ankit Jain [mailto:radical at gmail.com]
> Sent: Tuesday, July 28, 2009 5:50 AM
> To: Gladish, Jacob
> Cc: mono-devel-list at ximian.com
> Subject: Re: [Mono-dev] xbuild
>
> On Mon, Jul 27, 2009 at 9:48 PM, Gladish, Jacob<Jacob.Gladish at sig.com>
> wrote:
> > I decided to give xbuild a try today and was pretty impressed on how
> well it was working.
>
> Glad to hear that :)
>
> > I have a project with a few .config files checked into revision control
> that wind up being read-only. When I run xbuild it errors out trying to
> overwrite a read-only file from a previous run in the output directories.
> I'm not if this is a bug or not. I am owner of target file and modebits
> are all -r--r--r--.
>
> No, error'ing out on trying to overwrite a read-only file, not a bug.
>
> -Ankit
>
>
>
> --
> Blog : http://www.ankitjain.org/blog

IMPORTANT: The information contained in this email and/or its attachments is confidential. If you are not the intended recipient, please notify the sender immediately by reply and immediately delete this message and all its attachments. Any review, use, reproduction, disclosure or dissemination of this message or any attachment by an unintended recipient is strictly prohibited. Neither this message nor any attachment is intended as or should be construed as an offer, solicitation or recommendation to buy or sell any security or other financial instrument. Neither the sender, his or her employer nor any of their respective affiliates makes any warranties as to the completeness or accuracy of any of the information contained herein or that this message or any of its attachments is free of viruses.