Remove github.com/VasilKalchev/RGBLED registration #6562
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.
It seems that a compliant release of this library was never created, meaning that although there is a registry entry, the library is not actually listed in the libraries index.
The registration occurred eight years ago (arduino/Arduino#6257) and the repository has since either been deleted or made private, so a release of the library will never come. Thus, removing the registration will not cause any harm.
The existence of this "ghost registration" is problematic because the duplicate name check system uses the libraries index. Since the library is not present there, the check doesn't see that the name "RGBLED" has already been registered and thus will allow registration of additional libraries with that name (e.g., #6509). In addition, its presence may cause confusion to the registry maintainers since we expect each registration to have a unique name.
Since the registration of the library provides no benefit and causes harm, it is removed.
Normally a removal operation in the registry must be accompanied by an operation on the "backend" machine. However, in this case there is no trace of the library on the "backend" machine because this only occurs when at least one release of the library has been indexed. So the removal is accomplished without any action needed on the "backend".