Rename package for local use without VCS nonsense. #1
Conversation
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
1 participant
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.
See https://github.com/ClaimLynx/wiki/wiki/Custom-Transphporm.
Composer looks for a package by its canonical name at Packagist/GitHub and whatever VCS is configured in
satis.jsonfor ClaimLynx. But it has to match the name in the package'scomposer.jsonfile. But a fork of a GitHub project, such as our fork oflevel-2/transphpormhas to have the same package name as the original. These are incompatible aims.This commit will make this ClaimLynx copy no longer a "fork" because it will rename the package name, but that will hopefully make Satis and all our projects which want to include this library work correctly.