Pkg3: Unregistered Packages?
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 75
- Forks
- 23
- PR merge metrics
- No merged PRs in 30d
Description
I'm unclear as to how Pkg3 will handle unregistered packages. Is the expectation that all packages must be registered with at least a personal/private registry? Currently, it's very useful to run Pkg.clone to try out someone's changes. Similarly, declaring dependencies with just a git url in a DECLARE file provides a convenient way of developing a collection of inter-dependent packages prior to registering them.
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 reading the issue discussion and the linked DECLARE proposal, then compare its unregistered-package workflow with the referenced Pkg.clone usage. The issue does not identify implementation files, tests, or acceptance criteria; a maintainer would need to define the package-management behavior before development can begin.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- julia
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100