Closed wulfgarpro closed 9 months ago
It's because they haven't released the patches I submitted to the upstream. The only feasible way is to fork so that I can publish to crates.io:
Since you asked, join https://github.com/rust-headless-chrome/rust-headless-chrome/pull/442#issuecomment-1881736676 and ask to release a new version. I also don't want to spend time maintaining my own fork of rust-headless-chrome
.
Thanks for the explanation.
How about, instead, you specify the git repo dependency until it's released? See https://doc.rust-lang.org/cargo/reference/specifying-dependencies.html#specifying-dependencies-from-git-repositories, for more information.
On Thu, 18 Jan 2024, 6:05 pm Hollow Man, @.***> wrote:
It's because they haven't released the patches I submitted to the upstream:
- rust-headless-chrome/rust-headless-chrome#442 https://github.com/rust-headless-chrome/rust-headless-chrome/pull/442 for rust-headless-chrome/rust-headless-chrome#441 https://github.com/rust-headless-chrome/rust-headless-chrome/issues/441
- rust-headless-chrome/rust-headless-chrome#439 https://github.com/rust-headless-chrome/rust-headless-chrome/pull/439 for rust-headless-chrome/rust-headless-chrome#436 https://github.com/rust-headless-chrome/rust-headless-chrome/issues/436 and #31 https://github.com/HollowMan6/mdbook-pdf/issues/31
Since you asked, join rust-headless-chrome/rust-headless-chrome#442 (comment) https://github.com/rust-headless-chrome/rust-headless-chrome/pull/442#issuecomment-1881736676 and ask to release a new version. I also don't want to spend time maintaining my own fork of rust-headless-chrome.
— Reply to this email directly, view it on GitHub https://github.com/HollowMan6/mdbook-pdf/issues/37#issuecomment-1897918689, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAHJHNBV7ULRQ77FRHMIQJLYPDCU5AVCNFSM6AAAAABB7NVKTWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOJXHEYTQNRYHE . You are receiving this because you authored the thread.Message ID: @.***>
It's because they haven't released the patches I submitted to the upstream. The only feasible way is to fork so that I can publish to crates.io:
Thanks for the explanation. How about, instead, you specify the git repo dependency until it's released? See https://doc.rust-lang.org/cargo/reference/specifying-dependencies.html#specifying-dependencies-from-git-repositories for me information.
Then I can't publish mdbook-pdf to crates.io. Read carefully to see the note in the link you mentioned:
Note: crates.io does not allow packages to be published with dependencies on code published outside of crates.io itself
Looks like a new version was released last week: https://github.com/rust-headless-chrome/rust-headless-chrome/releases/tag/v1.0.9.
Now updated and released v0.1.8
Hi, thanks for
mdbook-pdf
!Why was
rust-headless-chrome
replaced bymdbook-pdf-headless_chrome
in 7250bba20eee89f79d5d5d4eea8050d6f4789a79?I'd rather use the non-forked version of
rust-headless-chrome
. For now I'm patchingmdbook-pdf
at rev 9ea2011de98e30d6f3a04c6b8fe665e71fc29ada.