Re: [nant-dev] Exec Task OS Specific
We currently only support two diffferent platforms, namely win32 and unix.
For win32, we support .NET 1.0, .NET 1.1, .NET CF 1.0, SSCLI 1.0 and Mono
1.0, while for unix we only support the Mono framework (and Mac OsX is
considered to be unix).
For Mono on unix we've configured the runtime engine to be mono, not mint.
So what we need is a way of determining that NAnt is running on Mac, so we
can create a third platform for Mac...
For now, you can change the runtime that's used by configuring the platform
node for unix in the NAnt configuration file
(src/NAnt.Console/NAnt.Console.exe.config before you build, or
bin/NAnt.exe.config after you've built NAnt).
Hope this helps,
Gert
- Original Message -
From: Stefan Bodewig [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, October 14, 2003 7:55 AM
Subject: Re: [nant-dev] Exec Task OS Specific
On Mon, 13 Oct 2003, Jaroslaw Kowalski [EMAIL PROTECTED] wrote:
exec program=${build.dir}/Ojb.Net.Tools.PoGen/pogen.exe
useruntimeengine=true
commandline=/repository ${resource.dir}/repository.xml /
Could that explain my Mac problems?
A boolean for useruntimeengine may not be enough for Mono support on
platforms where the JIT (mono) doesn't exist or at least work
reliably. On a Mac you'd need a way to specify mint as executable
instead.
Stefan
---
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers
---
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers
Re: [nant-dev] Exec Task OS Specific
The useruntimeengine attribute itself is actually documented in the help for
the nightly builds
(http://nant.sourceforge.net/nightly/help/tasks/exectask.html), but perhaps
we should make it more clear as to what it exactly does ...
Gert
- Original Message -
From: Met @ Uber [EMAIL PROTECTED]
To: Gert Driesen [EMAIL PROTECTED]
Cc: NAnt-Devel [EMAIL PROTECTED]
Sent: Monday, October 13, 2003 10:34 PM
Subject: Re: [nant-dev] Exec Task OS Specific
Apparently its just not documented, but the attribute itself works.
Thanks a lot. And that shouldn't break anything between OS's right?
On Mon, 2003-10-13 at 16:25, Met @ Uber wrote:
That sounds like exactly what I need, but would you mind showing me an
example of what your talking about? I don't see it in the 'exec' tasks
documentation.
~ Matthew
On Mon, 2003-10-13 at 16:17, Gert Driesen wrote:
nope, you should set the useruntimeengine attribute for the exec task
to
true if you want that behaviour ...
Gert
- Original Message -
From: Met @ Uber [EMAIL PROTECTED]
To: NAnt-Devel [EMAIL PROTECTED]
Sent: Monday, October 13, 2003 10:07 PM
Subject: [nant-dev] Exec Task OS Specific
Does the exec task use 'mono' when on Linux to run programs? For
example:
exec program=${build.dir}/Ojb.Net.Tools.PoGen/pogen.exe
commandline=/repository ${resource.dir}/repository.xml /
Does that get passed to the command prompt like so?
mono ${build.dir}/Ojb.Net.Tools.PoGen/pogen.exe /repository [snip]
Anyone know?
~ Matthew
---
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers
---
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers
---
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers
---
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers
Re: [nant-dev] Exec Task OS Specific
On Tue, 14 Oct 2003, Gert Driesen [EMAIL PROTECTED] wrote: So what we need is a way of determining that NAnt is running on Mac, so we can create a third platform for Mac... No, what you need is a way of determining whether you can use mono or have to fall back to mint. AFAIU mono is only stable for i386 based systems. For Mono 0.29 a stable JIT for PPC has been promised, so Mac = mint would be wrong then. I don't think you can autodetect it For now, you can change the runtime that's used by configuring the platform node for unix in the NAnt configuration file (src/NAnt.Console/NAnt.Console.exe.config before you build, or bin/NAnt.exe.config after you've built NAnt). You mean the runtimeengine attribute of framework? How is the framework node selected by NAnt? Hmm, I assume adding a mint config in addition to NAnt.Console.exe.config.linux and renaming the .linux to .mono and changing cp src/NAnt.Console/NAnt.Console.exe.config.linux bin/NAnt.exe.config in the Makefile to something more conditional would do. I'll try that and come back to you 8-) Stefan --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
Re: [nant-dev] Exec Task OS Specific
On 14 Oct 2003, Stefan Bodewig [EMAIL PROTECTED] wrote: Hmm, I assume adding a mint config in addition to NAnt.Console.exe.config.linux I was obviously looking at an out-of-date Makefile, sorry. Stefan --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
RE: [nant-dev] Licensing
IANAL If and when, Nant chooses to migrate to a different license, it will have to handle the copyrights of the contributers. Scott Hernandez and I briefly discussed this on the Draco.Net list. Scott wanted references, and I haven't responded because I had to take some time to look them up. Based on my research, I concluded the following: 1. NAnt is not a work for hire 2. Nant is a joint work 3. The implicit aggreement of joint work was the license then in effect. 4. Contributers own the copyright on their contributions. 5. Changing the implicit aggreement of joint work violates the contributers' copyright. 6. To change the implicit agreement, written consent is needed. REF general http://www.denniskennedy.com/opensourcelaw.htm http://www.fsf.org/licenses/license-list.html http://www.fsf.org/philosophy/enforcing-gpl.html http://www.openrevolt.org/ http://www.fsf.org/copyleft/gpl-faq.html http://www.fsf.org/copyleft/why-assign.html http://www4.law.cornell.edu/uscode/17/index.html http://biz.findlaw.com/intellectual_property/articles.html http://www.findlaw.com/01topics/10cyberspace/licensing/publications.html http://profs.lp.findlaw.com/copyright/copyright_3.html http://www.findlaw.com/01topics/23intellectprop/01copyright/index.html /general software-copyright http://www.gigalaw.com/articles/2000-all/hollander-2000-02-all.html http://www.fplc.edu/tfield/COPYSOF.htm http://www.netatty.com/copy.html http://profs.lp.findlaw.com/copyown/index.html /software-copyright ownership http://www.gigalaw.com/articles/2000-all/landau-2000-04-all.html /ownership work-for-hire http://www.gigalw.com/articles/2000-all/loc-2000-02-all.html /work-for-hire commentary http://www.crynwr.com/cgi-bin/ezmlm-cgi?3:mss:5943:200210:pcddoaoajaglbhghpe oe http://www.crynwr.com/cgi-bin/ezmlm-cgi?3:mss:5928:200210:pcddoaoajaglbhghpe oe http://biz.findlaw.com/intellectual_property/nolo/ency/B09BB4E7-5744-4131-8B 29ACD7CC408853.html http://biz.findlaw.com/intellectual_property/nolo/faq/BABFA71E-97C9-479F-8A9 D4C3DB2498663.html http://profs.lp.findlaw.com/copyown/copyown_3.html http://profs.lp.findlaw.com/copyright/index.html http://www.crynwr.com/cgi-bin/ezmlm-cgi?3:mss:33:199904:mjebdegliikloobhagjp /commentary /REF Hope this Helps, -- Tom. /IANAL --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
Re: [nant-dev] Licensing
On Tue, 14 Oct 2003, Tom Jordan [EMAIL PROTECTED] wrote: IANAL If and when, Nant chooses to migrate to a different license, it will have to handle the copyrights of the contributers. IANAL either, but what you say is 100% the same that I've seen happen in similar cases for other projects. At least under US law, all OS contributors retain their copyright unless they've signed a license agreement or something similar. Stefan --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
Re: [nant-dev] Licensing
Yes, this has always concerned me and is something I think we need to remedy on any future contributions. We need some kind of declaimer/license agreement that people submitting patches agree to. Then we can be free to make these kinds of changes without contacting a hundred people, or keeping track of each person who makes the smallest code change. For people who make small contributions (a few lines changed here or there) I'm sure they would be willing to hand over their copyright, whereas people who make large contributions should keep them. In a collaborative project like this it seems appropriate to have 5-15 (keeping the number small for manageability) copyright holders (who have made large contributions) who become the committee who decides license issues like this. Does anyone know if a scheme like this is possible and legal in the US? - Original Message - From: Stefan Bodewig [EMAIL PROTECTED] On Tue, 14 Oct 2003, Tom Jordan [EMAIL PROTECTED] wrote: IANAL If and when, Nant chooses to migrate to a different license, it will have to handle the copyrights of the contributers. IANAL either, but what you say is 100% the same that I've seen happen in similar cases for other projects. At least under US law, all OS contributors retain their copyright unless they've signed a license agreement or something similar. --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
Re: [nant-dev] Licensing
Isn't it common to assign copyright to on eor two people or some registered body ? So for apache projects its the apache foundation, for mono its Ximian etc I think at this stage we would have difficulty tracking down all contributers. Ian Scott Hernandez wrote: Yes, this has always concerned me and is something I think we need to remedy on any future contributions. We need some kind of declaimer/license agreement that people submitting patches agree to. Then we can be free to make these kinds of changes without contacting a hundred people, or keeping track of each person who makes the smallest code change. For people who make small contributions (a few lines changed here or there) I'm sure they would be willing to hand over their copyright, whereas people who make large contributions should keep them. In a collaborative project like this it seems appropriate to have 5-15 (keeping the number small for manageability) copyright holders (who have made large contributions) who become the committee who decides license issues like this. Does anyone know if a scheme like this is possible and legal in the US? - Original Message - From: Stefan Bodewig [EMAIL PROTECTED] On Tue, 14 Oct 2003, Tom Jordan [EMAIL PROTECTED] wrote: IANAL If and when, Nant chooses to migrate to a different license, it will have to handle the copyrights of the contributers. IANAL either, but what you say is 100% the same that I've seen happen in similar cases for other projects. At least under US law, all OS contributors retain their copyright unless they've signed a license agreement or something similar. --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
