Remove the legacy C implementation from the source tree #104
Conversation
This file contains 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
This will still be available via git history, but it's no longer maintained, and the git submodule adds extra weight to a full checkout or Cargo download. Let's remove it from the main branch.
fenollp
approved these changes
Apr 20, 2022
|
Thanks all! |
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.
This branch:
legacy-c-implsubdirectory and the libfreetype submodule.legacy-c-implis still present.As discussed in #103.
@LinusCDE - IIUC this is more or less the approach you were suggesting.
@fenollp - renaming sounds definitely better than the status quo, but it would prevent the legacy c impl even from building without a bit of hacking, and this seems like a nice chance to declutter the repo. I don't feel that strongly though!