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

Add a specific tag when getting operations #2

Merged
merged 1 commit into from
Oct 9, 2019

Conversation

hug-dev
Copy link
Member

@hug-dev hug-dev commented Oct 9, 2019

This would prevent importing breaking changes in the future!

Signed-off-by: Hugues de Valon hugues.devalon@arm.com

This would prevent importing breaking changes in the future!

Signed-off-by: Hugues de Valon <hugues.devalon@arm.com>
@hug-dev
Copy link
Member Author

hug-dev commented Oct 9, 2019

I will tag this repo 0.1.0 after this (as I did with parsec-operations). Then we can also specify the version of parsec-interface-rs that we use in parsec and parsec-test-client.

@@ -19,6 +19,7 @@ use std::process::{Command, Output};

const PROTO_FOLDER: &str = "target/parsec-operations/protobuf";
const PROTO_OUT_DIR: &str = "src/operations_protobuf/generated_ops";
const PARSEC_OPERATIONS_VERSION: &str = "0.1.0";
Copy link
Member

Choose a reason for hiding this comment

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

[NIT] This could be put in Cargo.toml to keep all dependencies specified in one place, but it might not be worth the effort

Copy link
Member Author

Choose a reason for hiding this comment

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

Are you thinking of doing the same than in parsec, ie:

[package.metadata.config]
mbed-crypto-version = "mbedcrypto-1.1.0"

I think that is a good idea!

Copy link
Member

Choose a reason for hiding this comment

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

That sounds good but it does mean more code in build.rs which might not be justified. Whether it's in Cargo.toml or build.rs doesn't feel like critical to me, but maybe someone seeing the code for the first time would find it easier to understand the dependencies

Copy link
Member Author

Choose a reason for hiding this comment

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

To keep things simpler and avoir making build.rs more complicated, I'll keep the tag in build.rs.

// TODO: using tagging and releases, this could maybe be faster: downloading a .zip release file
// and decompressing it.
// TODO: Downloading a release file and decompressing it might be faster here.
// TODO: Use semantic versioning to get the newest versions.
Copy link
Member

Choose a reason for hiding this comment

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

https://crates.io/crates/git2 this should come in handy, both for the semantic versioning check and for the command below.

Copy link
Member Author

Choose a reason for hiding this comment

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

If we use the release package instead we might just download it with wget I think. It would be useful if it can list the tags available on a repo so that we can choose the one compatible with our semantic version?

@hug-dev hug-dev merged commit 805eb59 into parallaxsecond:master Oct 9, 2019
@hug-dev hug-dev deleted the add-versioning branch October 9, 2019 12:26
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.

2 participants