Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature/separate nunit #2

Merged
merged 4 commits into from
Apr 18, 2014
Merged

Conversation

haf
Copy link
Contributor

@haf haf commented Apr 18, 2014

I would like to have this separate since I'm integrating it into Fuchu, Suave and FSharp.Actor.

eiriktsarpalis added a commit that referenced this pull request Apr 18, 2014
@eiriktsarpalis eiriktsarpalis merged commit afbdf62 into nessos:master Apr 18, 2014
@eiriktsarpalis
Copy link
Contributor

Good idea, thanks!

@haf haf deleted the feature/separate-nunit branch April 18, 2014 19:52
@eiriktsarpalis
Copy link
Contributor

@haf I'm having a few misgivings on this. While removing a dependency on NUnit from the core stuff is nice, I still need NUnit support for the nuget package. On the other hand, publishing a separate PerfUtil.NUnit sounds like overkill: the addition is too small, nonetheless not entirely trivial.

Thoughts?

@haf
Copy link
Contributor Author

haf commented Apr 24, 2014

Why is it too trivial to publish a separate nuget? It's not trivial from a consumer side to get an unneeded dependency and there's no code requirement for the dependency either. I think it's nicer to publish more nugets, thereby having more granular nugets for exactly the type of functionality the consumer is after.

@eiriktsarpalis
Copy link
Contributor

This will probably need a FAKE script.

@eiriktsarpalis
Copy link
Contributor

Done. Nuget has been updated

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants