Skip to content

Update for peniko changes and pin git rev#256

Merged
dfrg merged 4 commits intomainfrom
peniko-updates
Jan 17, 2023
Merged

Update for peniko changes and pin git rev#256
dfrg merged 4 commits intomainfrom
peniko-updates

Conversation

@dfrg
Copy link
Copy Markdown
Collaborator

@dfrg dfrg commented Jan 17, 2023

This applies updates for the gradient API in peniko and pins the git dependency so prevent further breakage. Also removes Cargo.lock.

dfrg added 2 commits January 17, 2023 12:31
This applies updates for the gradient API in peniko and pins the git dependency so prevent further breakage. Also removes Cargo.lock.
Copy link
Copy Markdown
Contributor

@raphlinus raphlinus left a comment

Choose a reason for hiding this comment

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

The gradient changes look fine, thanks!

Comment thread Cargo.toml Outdated
smallvec = "1.8.0"
moscato = { git = "https://github.com/dfrg/pinot" }
peniko = { git = "https://github.com/linebender/peniko" }
peniko = { git = "https://github.com/linebender/peniko", rev = "ba96b90" }
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Do we want to pin the one above as well?

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

We can but I don't plan any further updates to moscato and it will go away as soon as googlefonts/fontations#191 lands.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

Added a pin just for consistency. Doesn't hurt!

Comment thread .gitignore
@@ -1 +1,2 @@
/target
Cargo.lock
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I'm not 100% sure what to do with this - having it for purely library use is not useful, but a nontrivial amount of development is the examples. I think ok to drop it as you've done here, but I'm curious if other people have thoughts.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

I don't have strong feelings on this, but I think I'll merge as to move forward and ask for commentary on zulip.

Copy link
Copy Markdown

@Speykious Speykious Jan 17, 2023

Choose a reason for hiding this comment

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

The Cargo book has an answer as to what to do with Cargo.lock:
https://doc.rust-lang.org/cargo/guide/cargo-toml-vs-cargo-lock.html

If you’re building a non-end product, such as a rust library that other rust packages will depend on, put Cargo.lock in your .gitignore. If you’re building an end product, which are executable like command-line tool or an application, or a system library with crate-type of staticlib or cdylib, check Cargo.lock into git.

It then links to this section of their FAQ which explains the reasoning behind this.

Thus (and I'm quite surprised myself as I believed the contrary until I searched it up just now) it seems like ignoring Cargo.lock for Xilem is actually a good idea.

@dfrg dfrg merged commit 3933c15 into main Jan 17, 2023
@dfrg dfrg deleted the peniko-updates branch January 17, 2023 18:01
DJMcNab added a commit to DJMcNab/vello that referenced this pull request Feb 15, 2024
@DJMcNab DJMcNab mentioned this pull request Feb 15, 2024
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.

3 participants