Recruit additional maintainers or archive the project

[hormelcookies]

This has become a critical build dependency for many, many project and it is essentially unmaintained. Pull requests languish without any review, most issues go unanswered, etc. etc.

If you are unable to recruit additional maintainers, I recommend archiving the project to let users know that it is deprecated and they should move to another tool.

[travis-leith]

I came here to open an issue, saw that there are 708 unresolved issues, and decided against it.

[smoothdeveloper]

@hormelcookies / @travis-leith are you facing any blocking or specific issues?

Paket works great, I doubt anyone wants the project to be "archived".

Just to understand, are either of you volunteering?

[smoothdeveloper]

@forki, would you mind creating a discussion area for the project and move this "issue" to it?

Thanks!

[travis-leith]

@smoothdeveloper sorry for sounding unappreciative. It was not my intention, but in hindsight, that is how it landed.

To answer your question about a specific issue, I posted in the f# slack, didn't get a response then came here to post it, and decided against it as it seems minor against over 700 other outstanding issues.

[smoothdeveloper]

@travis-leith I see, it seems to be a support question for the specific scenario and command line you are looking after.

In your case, it seems you still need to add somenugetlib into the mynewproject, could you try dotnet paket add somenugetlib -p mynewproject (making sure there is a mynewproject/mynewproject.*proj file there)?

https://fsprojects.github.io/Paket/paket-add.html

you may post the complete output if still stuck, consider trying with the --verbose flag if nothing strikes as indicating an issue.

[travis-leith]

Doesn't seem to be doing what I expect. It is difficult to paste output without violating some security policy, but the specific call I am using is dotnet paket add Microsoft.Extensions.Configuration -p src\Configuration\Configuration.fsproj This does not result in the creation of src\Configuration\paket.references, instead it adds an entry to .\paket.references. This may be some weirdness related to the structure of the SAFE template. There is a .\Build.fsproj which may be confusing paket somehow?

[smoothdeveloper]

@travis-leith I am not sure about the specifics related to safe project template structure.

What you are after is adding a single line with Microsoft.Extensions.Configuration to src/Configuration/paket.references, assuming paket.dependencies at the root was already updated to mention this particular package.

[travis-leith]

In that case I think I have misunderstood how paket works. I thought it will automatically creates src/Configuration/paket.reference if it does not already exist. Are you saying I should manually create and maintain this file? If I do nothing, how does paket know/record the fact that Microsoft.Extensions.Configuration should only be added to src/Configuration?

[smoothdeveloper]

I've tried the command and it does create the paket.references, but it was in a simple "console" project.

If you create that src/Configuration/paket.references file with Microsoft.Extensions.Configuration and the same package is defined nuget Microsoft.Extensions.Configuration in the root paket.dependencies, I'd expect the paket install or paket restore (if the .lock file is already generated with this package, from previous install) to work.

In which case, you can bypass using the command lines, or figure out what is occuring in your particular case.

[isaacabraham]

@smoothdeveloper sorry for sounding unappreciative. It was not my intention, but in hindsight, that is how it landed.

To answer your question about a specific issue, I posted in the f# slack, didn't get a response then came here to post it, and decided against it as it seems minor against over 700 other outstanding issues.

@travis-leith basically paket add will (IIRC) simply look in the current folder for the references file to add to. This isn't really a SAFE issue, it's more about the fact that there's a project in the current directory that you're in, so paket is modifying that references file.