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

Implement manual registry #1

Open
certik opened this issue Jul 21, 2020 · 2 comments
Open

Implement manual registry #1

certik opened this issue Jul 21, 2020 · 2 comments

Comments

@certik
Copy link
Member

certik commented Jul 21, 2020

The details are discussed at:

fortran-lang/fpm#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" = "https://somewhere/package1-0.1.5.tar.gz"
"0.1.6" = "https://somewhere/package1-0.1.6.tar.gz"

[stdlib]
"1.0.0" = {git="htttps://github.com/fortran-lang/stdlib", tag="v1.0.0"}
"latest" = {git="htttps://github.com/fortran-lang/stdlib", branch="master"}  # This would checkout the latest master

We can discuss if we should allow the "latest" --- perhaps we should simply only allow specific versions, that seems to be the case with other package managers.

@certik
Copy link
Member Author

certik commented Jul 22, 2020

We now have the initial TOML file (https://github.com/fortran-lang/fpm-registry/blob/235aebc6968408e2e5468168d2873aaeef7cd07a/registry.toml), now we need to implement CI that will check that it is formatted correctly, and then to generate our rich metadata JSON file.

@certik
Copy link
Member Author

certik commented Jul 22, 2020

Regarding the "latest" --- I think we should allow it. I think it will allow fpm to download the latest development version of the package (and then lock the particular latest git commit in fpm.lock). So fpm search can list all versions plus the latest and users can choose.

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

No branches or pull requests

1 participant