Allow filtered updates of packages matching a regex

[mavnn]

Especially useful for situations like "update all packages that start with my organisations prefix"

[forki]

do you have a small sample for this? Then I could add a regression test

[mavnn]

Of course.

Given dependency file:

source https://nuget.org/api/v2

nuget Castle.Windsor                           
nuget NUnit                             
nuget Microsoft.AspNet.WebApi.SelfHost

Then:

paket update nuget Microsoft.* --filter should update AspNet

paket update nuget [MN].* --filter will update NUnit and AspNet but leave Castle.Windsor untouched.

Without the --filter flag, package names are treated as exact matches. This is potentially important as . is a special character in regexs.

[forki]

can we remove that case and express it as UpdateFiltered of GroupName * PackageFilter?

[mavnn]

As in, escape .s and treat it as a filter? I think it would work. Hope your regression tests are good up to date though! :D

[mavnn]

Give me a few minutes and I'll see if all the tests pass.

[forki]

[mavnn]

My code obviously rules :)

[mavnn]

Mind pushing that test to my master branch? I'll add it to the pull request.

[mavnn]

Ah, ok - I'll grab it.

[forki]

40ecd39

[forki]

you need to run build.cmd runintegrationtests since we don't execute that target during standard build

[mavnn]

Should having working unit and integration tests now

[mavnn]

I removed this test as it's expectation didn't seem meaningful anymore. With pattern based updates, a pattern that didn't match any packages should be a no-op, not an exception.

The update package command still checks that the specific named package exists before calling UpdateFiltered

[forki]

Could also please write one or two samples in the docs of the update command?

[mavnn]

@forki crap. Push to wrong remote by mistake. Sorry.

[mavnn]

/me goes off to change default push repository

[forki]

no worries ;-)