And Philip... I'm curious as to the environment you got mono NAnt to run
in. Cygwin, or the real deal in linux?
Suse Linux 8.0, shell script for the initial build, GVim text editor
---
This sf.net email is sponsored by:ThinkGeek
Welcome to
Ooh. Could you post the shell script? I'd like to work on putting
something together to help folks get bootstrapped into NAnt from Linux.
(Hmmm... this might be a better long-term approach on both platforms.
Instead of including a previous set of NAnt binaries)
Some maybe-not-so-useful
What about this one? I use the already-gotten dstInfo to test for
attribute we don't want and clear them if they exist. Shouldn't be a
lot of overhead in this case:
diff -u -r1.4 CopyTask.cs
--- src/NAnt.Core/Tasks/CopyTask.cs 26 Feb 2003 07:02:30 - 1.4
+++
Matthew,
This has not been committed yet. I'm of the mind now that this is just a lazy
mans attrib task. One can very easily just call an attrib before this task to
insure that it is not read only. However, if no one is opposed to this change,
I say put it in.
I'd really like to see my
Matthew Mastracci wrote:
I've manually applied Aaron's changes to my tree, cleaned up the style
to match the NAnt coding style and attached it to this message.
If noone objects, I'll check this in.
Looks ok to me.
?
Title: Message
On my
builds, I have a separate filethat just contains properties and nothing
else. For example,
?xml version="1.0" encoding="utf-8"
?project xmlns="http://tempuri.org/nant-vs.xsd"
name="Global Properties"
property name="isGlobalPropertyFileIncluded" value="true"
/!--
Hi Scott,
As agreed, I implemented an Available task that allows you to check for the
available of a file or directory resource.
I currently have two possible resource checks :
- File
- Directory
eg. available type=File resource=myfile.txt property=myfile.present
/
I used resource instead of
