packagecontrol / packagecontrol/thecrawl
Invalid tompstoned packages in registry, which were actually renamed.
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 19
- Forks
- 7
- Avg merge
- 4h 53m
- Merged PRs (30d)
- 14
Description
Commit https://github.com/packagecontrol/thecrawl/commit/a3a3b124b8a1766d9ccc588e20b810e857f57429 re-adds various packages to the registry, which have not been removed from registry due to being too old, but were just renamed and moved to other locations in one step.
As a result existing packages' old names are listed as "removed" aka RIP.
With regards to older revisions of package_control_channel and the huge amount of package rename operations over time, there would need to be much more such entries, if it would be the goal to also list all former names of registered packages.
It would then only make sense if those entries would link to current packages' sites in rare case anyone wants to search an old packages.
Otherwise those entries don't make any sense.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing commit a3a3b124b8a1766d9ccc588e20b810e857f57429 and the issue discussion about renamed packages in the registry. Trace how old package names are classified as removed, including older package_control_channel rename entries. Done means the registry no longer presents renamed packages as invalid removals, with the intended handling of links or historical names agreed and verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100