Rename libservo to servo#43141
Merged
Merged
Conversation
Signed-off-by: Jonathan Schwender <schwenderjonathan@gmail.com>
nicoburns
approved these changes
Mar 10, 2026
nicoburns
left a comment
Contributor
There was a problem hiding this comment.
Bigger diff than I expected. But LGTM.
mrobinson
approved these changes
Mar 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
As discussed on zulip we would like to rename
libservotoservo(again) before a future crates.io release.Servo is a library, so the
libprefix is somewhat redundant. We already renamed the binary of ServoShell toservoshell, to reduce confusion of users of what servo is.Note: This PR does not touch all occurrences of
libservo. Specifically CI job names remain untouched, since the risk of breaking something is higher here, harder to test for and the name not user facing.Testing: CI testing of this change should give us good confidence. Manual testing of
./mach docand./mach buildshowed no issues on macos. Full try run