# Fpm version 0.5.0 released **URL:** \ **Category:** Announcements\ **Created:** [November 21, 2021, 3:51pm UTC](https://fortran-lang.discourse.group/t/fpm-version-0-5-0-released/2314 "2021-11-21T15:51:20Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![awvwgk](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/awvwgk/32/154_2.png) [@awvwgk](https://fortran-lang.discourse.group/u/awvwgk)\ **Post date:** [November 21, 2021, 3:51pm UTC](https://fortran-lang.discourse.group/t/fpm-version-0-5-0-released/2314/1 "2021-11-21T15:51:20Z")
We just released version 0.5.0 of the Fortran package manager: > **[Release Fpm version 0.5.0 · fortran-lang/fpm](https://github.com/fortran-lang/fpm/releases/tag/v0.5.0)** > > Alpha release update for the Fortran package manager (fpm). > Changes > > > tests are only build for fpm test and not by default anymore (#572) > > > environment variables for setting Fortran and C compiler ... We have a large number of bug fixes in this release and made plenty of improvements to the tooling around fpm, like the continuous delivery and the Windows installer. New features include the possibility for better compiler/linker selection and the improved build backend (test are only build when needed, link dependencies are properly tracked). Please, let us know what you think. Many thanks to everybody who contributed to this release. We are really happy to see code contributions from ten developers in this release! ---
**Author:** ![certik](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/certik/32/4_2.png) [@certik](https://fortran-lang.discourse.group/u/certik)\ **Post date:** [November 21, 2021, 5:24pm UTC](https://fortran-lang.discourse.group/t/fpm-version-0-5-0-released/2314/2 "2021-11-21T17:24:09Z")
@awvwgk, thanks for releasing fpm and thanks for maintaining it and pushing it forward. We all really appreciate it. What are some of the features you would like to see in the next release? Here is one issue that might not be difficult to implement: > > > Currently fpm's output is very verbose and it's hard to see what is going on. A …bunch of commands (typically compiler invocations) are printed to stdout. Instead, let's do something like Rust's Cargo does: > \`\`\` > $ cargo build > Compiling libc v0.2.103 > Compiling autocfg v1.0.1 > Compiling proc-macro2 v1.0.26 > Compiling unicode-xid v0.2.2 > Compiling syn v1.0.72 > Compiling pkg-config v0.3.19 > Compiling cfg-if v1.0.0 > Compiling serde\_derive v1.0.130 > ... > Compiling path\_abs v0.5.1 > Compiling encoding v0.2.33 > Building \[============\> \] 79/150: encoding, proc-macro-hack... > \`\`\` > Or the Julia's Pkg: > \`\`\` > julia\> import Pkg > > julia\> Pkg.add("SymEngine") > Resolving package versions... > Installed RecipesBase ─── v1.1.2 > Installed MPC\_jll ─────── v1.2.1+0 > Installed SymEngine\_jll ─ v0.6.0+1 > Installed SymEngine ───── v0.8.6 > Downloaded artifact: SymEngine > Downloaded artifact: MPC > Updating \`~/.julia/environments/v1.6/Project.toml\` > \[123dc426\] + SymEngine v0.8.6 > Updating \`~/.julia/environments/v1.6/Manifest.toml\` > \[3cdcf5f2\] + RecipesBase v1.1.2 > \[123dc426\] + SymEngine v0.8.6 > \[2ce0c516\] + MPC\_jll v1.2.1+0 > \[3428059b\] + SymEngine\_jll v0.6.0+1 > \[781609d7\] + GMP\_jll > \[3a97d323\] + MPFR\_jll > Precompiling project... > 6 dependencies successfully precompiled in 4 seconds (48 already precompiled) > \`\`\` > > Note that Julia's Pkg prints all kinds of nice progress markers that all disappear when it is done, so the above output only captures the final result. I recommend you try the above commands yourself to see what I mean. > > The final output of Cargo seems cleaner and it seems it contains all the information you need to know, which is which package got built and which version. We can also print which Fortran compiler was used (I am not sure). > > P.S I thought I already opened up an issue for exactly this, but I can't find it, so I opened a new one. that would make the output look great. If anybody here is looking for an issue to contribute, this might be a good one to get involved with the fpm development. ---
**Author:** ![Carltoffel](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/carltoffel/32/1680_2.png) [@Carltoffel](https://fortran-lang.discourse.group/u/Carltoffel)\ **Post date:** [November 22, 2021, 10:37am UTC](https://fortran-lang.discourse.group/t/fpm-version-0-5-0-released/2314/3 "2021-11-22T10:37:11Z")
Since I had the issue, someone else might run into it, too: Note that `fpm` changed the default branch name to **main**. Therefore, if you used the `fpm` repository prior to this release, you might want to run `git switch main` in order to get the most recent version. _(You might have to run_ `git fetch` _first)_