fpm-registry
fpm-registry copied to clipboard
fortran-lang
Centralized registry of fpm packages
See https://github.com/fortran-lang/fpm/issues/421 for details. Please collect references in @fortran-lang projects to files inside this repository such that we can fix those links after renaming.
Our current workflow for building the package index is committing it to the default branch. Instead a separate branch or an upload of the package index seems preferable to me....
The index build currently warns for unknown entries in manifests like, *categories*, *keywords*, *homepage* and *install*. Those entries are valid as defined in the manifest reference in the fpm repository...
Should the ```fpm.toml``` file contain information about the size of the package? The subroutines ```new_package``` and ```check```, in the module ```fpm_manifest_package```, contain 18 keywords with information about a package, ```name```,...
Right now if somebody submits a PR with a duplicate name of a new package, such as: ```diff --- a/registry.toml +++ b/registry.toml @@ -2,6 +2,9 @@ "1.7.0" = {git="https://github.com/wavebitscientific/datetime-fortran", tag="v1.7.0"}...
It's currently difficult to diagnose CI failures when submitting new packages because of how [github actions outputs `stdout` and `stderr`](https://github.community/t/stdout-stderr-output-not-in-correct-order-in-logs/16335). In short, the relevant part of the error message is...
I wonder why we require `license`, `maintainer`, `author` and `copyright` to be present in the package manifest of a submitted package. Shouldn't `license` and `maintainer` be sufficient for a package...
I just checked out this registry for fpm and noticed some rough edges. It is somewhat related to #1, but maybe worth a separate issue. Specifying a project with multiple...
The details are discussed at: https://github.com/fortran-lang/fpm/issues/34 We should have a TOML file with a package name and a version / url combo for each version, something like: ``` [package1] "0.1.5"...
Registers: https://github.com/certik/fortran-utils/, as requested in https://github.com/fortran-lang/fpm/issues/17
