hi yall, IMHO....
since nant's namespace was restructured , the usability and extensibility via nant-contrib has suffered enormously, it seems to me. it's very hard to get a good binary image working across .NET 1.0 and 1.1. And it's hard to get a matching source image including nant-contrib and nant -- they're both important. it seems the current structure is as follows, which i believe is problematic: nant source produces daily nant bin, which is available w/ some arbitrary nant-contrib bin. nant-contrib source is available on its own. building it depends on some arbitrary nant bin. i may not have gotten the above exactly, but it seems to me nonetheless that the package visibility is backwards. what would make sense to me would be the following: nant-contrib depends on nant. nothing else. how to do this? when someone changes nant, they should somehow make sure they didn't break nant-contrib. when someone gets nant (source/bin), they only get nant (because they're not dependent on nant-contrib) when someone gets nant-contrib (source/bin), they get both the latest nant-contrib and the latest nant (source/bin) because they work together. ? /jean ____________ Jean Rajotte +1 416-574-1767 ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
