Skip to content

feat: a package manager #45

Description

@Jan0660

GitHub repositories would be the default way to add a package by:

Installing experience TBD:

Install-Package Jan0660/rcaron-omp

Packages 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-omp instead of Jan0660/rcaron-omp

Other:

  • can install from own git host/url
  • can install into a project

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    • Status
      Todo

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions