Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

group specification does not honor case-sensitivity

See original GitHub issue

Description

When specifying a group in paket.dependencies, the resulting directory under packages does not match the case of the group name.

Repro steps

Create a paket.dependencies like:

group SomeGroup
source https://www.nuget.org/api/v2
nuget Newtonsoft.Json

Run .paket\paket.exe install

Expected behavior

The directory name under packages should be SomeGroup.

Actual behavior

The directory name under packages is somegroup.

On windows, this doesn’t matter much, but it does on *nix systems.

Issue Analytics

State:
Created 7 years ago
Comments:6 (3 by maintainers)

Top GitHub Comments

1reaction

flaubcommented, Nov 2, 2016

I’m using an external build system based on https://waf.io/. Therefore, I don’t use any paket.references files. Instead, I have a parser which understands paket.lock and can create the proper command line arguments for csc/mcs. We’ve been using this system for years to provide cross-platform builds (including native C/C++ bits).

It would be nice if my custom parser for paket.lock could simply use whatever the group name is in order to go searching inside of the packages directory to find libs and refs. It works OK on windows because the file system acts like it’s case insensitive.

My workaround is to simply use an all lower-case group name.

Can you describe why the directory is lowercased by design?

0reactions

flaubcommented, Nov 12, 2016

Thanks for the explanation. As mentioned I have a workaround so this really isn’t a big deal. Thanks for providing a system that doesn’t depend on MSBuild!!