-
Notifications
You must be signed in to change notification settings - Fork 0
Open
Labels
enhancementNew feature or requestNew feature or request
Milestone
Description
GitHub repositories would be the default way to add a package by:
Installing experience TBD:
Install-Package Jan0660/rcaron-ompPackages would just be git repos, GitHub by default.
Would be able to install:
- a specific version
- would not auto-update
- when updating all packages, would remind that the package does not auto-update
- latest stable(no version suffix)
- latest prerelease(with version suffix)
- latest commit(be able to select branch)
- check if GitHub CI successful by default
- packages would use semantic versioning
- if major version increments, a normal package updating would not update
- have a global(user) package store, when a package is installed into a project, it would symlink there
Ideas:
- package manifest would state for what rcaron version it is, if it is breaking, then something something have like a command to check all user's packages are valid with the next version
- this would be a little yucky since packages would have to increment their major version because of RCaron itself
- user would be able to wait before updating to a new major RCaron version for all their packages to be compatible with it (better than the alternative of updating and packages being inexplicably broken though)
- would have to use a separate breaking version property or shift version numbers to 0.MAJOR.MINOR.PATCH
- could theoretically also have a "known list" in the future so one could install
rcaron-ompinstead ofJan0660/rcaron-omp
Other:
- can install from own git host/url
- can install into a project
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
enhancementNew feature or requestNew feature or request
Projects
Status
Todo