Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Cannot find a manifest file." (Installation issue) #2576

Closed
ShalokShalom opened this issue Mar 31, 2021 · 4 comments · Fixed by #2578
Closed

"Cannot find a manifest file." (Installation issue) #2576

ShalokShalom opened this issue Mar 31, 2021 · 4 comments · Fixed by #2578

Comments

@ShalokShalom
Copy link
Contributor

Description

As in the Readme described, is this how I attempt to install Fake on my Linux machine:

dotnet tool restore

This is the result:

Cannot find a manifest file.
For a list of locations searched, specify the "-d" option before the tool name.
No tools were restored.

Repro steps

Please provide the steps required to reproduce the problem

  1. dotnet tool restore

Expected behavior

Fake can be installed with dotnet fake build

Actual behavior

The above error message appears.

Related information

  • Operating system KaOS
  • Branch rolling
  • .NET Runtime, CoreCLR or Mono Version 5.0.201
  • Indications of severity
  • Version of FAKE (4.X, 5.X)
  • (if performance issue) Performance information, links to performance testing scripts
@ShalokShalom
Copy link
Contributor Author

I got just informed, that the build instructions in the Readme are just to hack on the project, not to actually use it.

I highly suggest, to include the following Installation instructions also in the Readme.

@yazeedobaid
Copy link
Collaborator

The build instructions in the Readme are brief steps for the contribution guide/building FAKE locally.
As for usage details they can be found on FAKE website. Including them in Readme is more of a duplicate in my opinion from a maintenance point of view.

@ShalokShalom
Copy link
Contributor Author

Better duplicate the information as put thousands through the process finding that

@ShalokShalom
Copy link
Contributor Author

Fixed in #2578

@yazeedobaid yazeedobaid linked a pull request Apr 30, 2021 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants