[Mono-list] SPAM-LOW: Re: NUnit Version - Upgrade soon?
atsushi at ximian.com
Fri Nov 28 04:39:04 EST 2008
Ahh, I get your point, that is a visible problem. Since I'm
just a volunteer to upgrade the version here, I am not at
the position to decide what we should include in our package.
nunit-console shell script is not actually used to build
mono and mcs (instead we use mono-wrapper and nunit-console.exe
directly) and this script can be removed if we just think about
mono and mcs.
When it comes to other modules, for example we use nunit-console
directly in Olive. So I assume we still sort of need a shell
I assume we could rename nunit-console to mono-nunit-console or
whatever, to explicitly indicate that it is for mono internals.
Is this the only concern, or is it just an example? :)
Charlie Poole wrote:
> Hi Atsushi,
>>> If you want to attract folks to Mono, then I think it's
>> important not
>>> to confuse them. :-)
>> If there's reasonable reason people get confused because of
>> my interpretation or effort on upgrading nunit version, then
>> I feel sorry ;)
> Even though this thread started as a result of your upgrade,
> I don't think the upgrade causes the confusion. I think it
> already existed for people who are moving from the Windows
> world to Linux+Mono and your upgrade just continues in the
> same way it has always been.
> Specifically, if I type "nunit-console" I get the version
> you install with NUnit. I can't change that without
> over-writing a file that is part of mono. But installs
> should not overwrite files created by other packages,
> so I have to create a comand like "nunit-console-25"
> and the old version remains the default when it makes
> more sense for the new version to be the default. Of
> course, an individual user can choose to rename these
> files and deal with package problems manually, but
> my install can't (shouldn't) make such a decision.
> Can you see the problem?
>> Atsushi Eno
> Mono-list maillist - Mono-list at lists.ximian.com
More information about the Mono-list