paket install creates the empty directory paket-files
Nobody has claimed this yet.
- Dominant language
- F#
- Stars
- 2.1k
- Forks
- 528
- Avg merge
- 1d 12m
- Merged PRs (30d)
- 54
Description
Description
The empty directory paket-files is created on paket install. This does not
create serious problems but it makes me think that I specified something in
paket.dependencies, so that I have to check this directory, as far as
it is created. Also, I have to remove it or add to .gitignore.
Is this empty folder created by design?
If this is not done for some technical reasons, can this empty folder be avoided?
This empty folder was not created some time ago (but quite a few versions ago).
Repro steps
paket.dependencies
source https://www.nuget.org/api/v2
nuget Invoke-Build
Command
paket install
Expected behavior
There is no empty folder paket-files.
Actual behavior
There is an empty folder paket-files.
Known workarounds
After paket install manually check that the folder is empty to be sure that
you do not have anything unexpected in paket.dependencies and either remove
this folder or make sure it is included in your .gitignore
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue with the shown paket.dependencies content by running paket install, then trace which install entry point creates paket-files. Done means the command no longer leaves an empty paket-files directory while preserving any required files or directories.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fsharp
- Domain
- build-system, cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100