purescript / purescript/pursuit
Handle package name collisions
Open
Nobody has claimed this yet.
- Dominant language
- Haskell
- Stars
- 174
- Forks
- 47
- PR merge metrics
- No merged PRs in 30d
Description
Looks like pulp publish will overwrite a previous package by the same name. Happened to me right now when I published https://github.com/jacereda/purescript-benchmark
There was already a package on Pursuit: https://github.com/cyrbon/purescript-benchmark
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 tracing how pulp publish handles a package name that already exists on Pursuit. The issue names no files or tests, so first establish the expected collision behavior and identify where publication currently permits an overwrite; done should be verified against the existing-package case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell
- Domain
- release
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100