paket outdated ignores version constraints

[agross]

paket.dependencies

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

nuget Castle.Windsor ~> 3.2

paket.lock:

NUGET
  remote: http://nuget.org/api/v2
  specs:
    Castle.Core (3.2.0)

paket outdated tells me there is a new version that clearly violates my version constraint

$ paket outdated
Paket version 0.9.6.0
Parsing paket.dependencies
Resolving packages:
  - fetching versions for Castle.Core
    - exploring Castle.Core 3.3.1
Outdated packages found:
  * Castle.Core 3.2.0 -> 3.3.1
06.09s - ready.

paket update updates according to the version constraint:

$ paket update
Paket version 0.9.6.0
Parsing paket.dependencies
Resolving packages:
  - fetching versions for Castle.Core
    - exploring Castle.Core 3.2.2
Locked version resolutions written to paket.lock
Castle.Core 3.2.2 unzipped to packages\Castle.Core
02.87s - ready.

I think there's a value in paket outdated supporting both

• a "show me updates according to my constraints" model (it should be the default)
• a "show me updates regardless of my constraints" model (e.g. paket outdated --ignore-constraints)

[forki]

didn't we define the defaults like documented? http://fsprojects.github.io/Paket/paket-outdated.html

--strict gives what you want.

[theimowski]

IMO --strict might be misleading, as we already use the same keyword for the strict mode

[forki]

ha I found it: #183

But I'm open to change it.

[forki]

So how do we want to name the new parameter if we change the defaults?

[forki]

I still need a name fot the new -- option. @agross ?

[agross]

I vote for --ignore-constraints