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

fpm-deployment: update VERSION field in fpm.toml with actual version #702

Closed
wants to merge 1 commit into from

Conversation

perazz
Copy link
Member

@perazz perazz commented Mar 15, 2023

See #701, this update in the fpm deployment script updates the VERSION placeholder in fpm.toml so an actual version is printed.

I don't know how to test the deployment on my fork.

@perazz perazz marked this pull request as draft March 15, 2023 11:07
@jvdp1 jvdp1 marked this pull request as ready for review March 17, 2023 20:13
Copy link
Member

@jvdp1 jvdp1 left a comment

Choose a reason for hiding this comment

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

LGTM. Thanks @perazz for this PR.

@perazz perazz requested a review from arteevraina March 18, 2023 14:31
@arteevraina
Copy link
Member

I don't know how to test the deployment on my fork.

You can try running this script locally and try to generate the fpm compatible stdlib ? and look if the changes are reflected in fpm.toml.

Copy link
Member

@awvwgk awvwgk left a comment

Choose a reason for hiding this comment

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

Why is this change necessary? We already deploy the VERSION file correctly for the stdlib-fpm branch.

@perazz
Copy link
Member Author

perazz commented Mar 18, 2023

Currently, fpm.toml in the deployed branch reports version = "VERSION"; this proposed change updates that field with the actual version, i.e., version = "0.2.1"

@awvwgk
Copy link
Member

awvwgk commented Mar 18, 2023

Currently, fpm.toml in the deployed branch reports version = "VERSION"; this proposed change updates that field with the actual version, i.e., version = "0.2.1"

Maybe, I misunderstand something here, but this is exactly what is expected. The version is already deployed correctly in VERSION on the stdlib-fpm branch. It will be read dynamically by the fpm binary. So why do we need to change the manifest at all?

If I recall correctly, I actually implemented this feature of reading the version from a file in fpm for stdlib to have a single place to specify the version for both build systems (fpm and CMake).

@perazz
Copy link
Member Author

perazz commented Mar 19, 2023

Oh I see, version can be an external file. That .toml can only be read proprely by fpm then. If we were going to support stdlib as a metapackage, I thought it was intuitive for the fpm-specific deployment to have a manifest file that contains all relevant pieces of information.

@awvwgk
Copy link
Member

awvwgk commented Mar 19, 2023

That was unfortunately never true, especially due to the default names for the source directories as well as the automatic discovery of executables, the TOML manifest alone is usually incomplete. Running fpm will generate an internal representation which is complete, the two options are to have fpm dump the internal model or reimplements the whole logic supported by fpm.

@jvdp1
Copy link
Member

jvdp1 commented Jun 15, 2023

@perazz @awvwgk Is this PR still needed? Or could it be closed without merging it?

@perazz
Copy link
Member Author

perazz commented Jun 15, 2023

Please close without merging @jvdp1, thank you.

@jvdp1
Copy link
Member

jvdp1 commented Jun 15, 2023

Ok. Thank you.

@jvdp1 jvdp1 closed this Jun 15, 2023
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 this pull request may close these issues.

4 participants