Skip to content

Add section on downloading binaries #28

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

Merged
merged 4 commits into from
Dec 15, 2021
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 25 additions & 1 deletion pages/how-to/installation.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,31 @@
# Installing fpm

This how-to guide covers the installation of the Fortran package manager (fpm) on various platforms.
This how-to guide covers the installation of the Fortran Package Manager (fpm) on various platforms.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would keep this lowercase

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is actually a general question since it should be consistent for all documents. Maybe we can do this change separately rather than in three different patches? This way we can also adapt the translation files in the same patch.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can do it in separate patches.

The choice boils down to whether we mean "Fortran Package Manager" as proper noun (I think so, and it allows abbreviating to fpm), in which case the correct spelling is to capitalize each word.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's make a separate patch and replace it in all files, maybe an automatic replacement in all files will work sufficiently well (also capturing the msgid's in the po files).

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree with Milan, we're referring to fpm as a proper noun and hence it should be capitalized as such.


## {fab}`apple` {fab}`linux` {fab}`windows` Download binaries

Binaries for macOS, Linux, and Windows (all on x86-64) are available for download for each release of fpm, as well as the latest (bleeding edge) release which mirrors the latest commit in the main branch of fpm.

Navigate to [fpm releases](https://github.com/fortran-lang/fpm/releases) to see all available releases.
The downloadable files are available at the bottom of each release section under "Assets".
Click on the appropriate link based on your OS.
For example, to download a macOS fpm binary, click on the link that has "macos" in its name.
After downloading, you'll need to make your binary executable.
On Linux and macOS, you can do this by typing

```
chmod +x fpm-0.5.0-linux-x86_64
```

Optionally, place the binary in a directory that's globally accessible (i.e. in the PATH environment variable on Linux and macOS).
You can also rename the binary to just "fpm" for easier use.

For Windows, both a self-contained binary and a Windows Installer for fpm are available.

:::{note}
Links that end with ".sha256" provide the cryptographic hashes that you can use to verify if the download of your binary was successful.
If you don't know what this is, don't worry and ignore these files.
:::

## {fab}`windows` MSYS2 package manager

Expand Down