Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mages package repository #50

Open
FlorianRappl opened this issue Jul 11, 2016 · 2 comments
Open

Mages package repository #50

FlorianRappl opened this issue Jul 11, 2016 · 2 comments

Comments

@FlorianRappl
Copy link
Owner

One thing that is crucial for any kind of language (however, especially for a scripting language) is to be connected to some kind of package repository. I don't want to create a whole new infrastructure, hence this hasn't been discussed so far. But I think there are some ways around it ...

  • Using the NuGet package infrastructure; essentially giving special tags and only content to a package. The content would be copied 1-1 with the convention that the "main" file should be named "index.ms".
  • Using GitHub Gists. Packages would be limited to one file and versioning (optional) would be done via Git as it is backed into GitHub Gists.
  • Using Git repositories independent of the origin. More complex, yet more files / possibilities.
  • Alternatively, other package managers such as bower or npm may be an option.

Currently, I tend to use the NuGet infrastructure. This would provide all required metadata, dependencies, and integrated support from the .NET side.

@FlorianRappl
Copy link
Owner Author

Regarding the git repositories: One could define paths to git repositories as package feeds, e.g., "https://github.com/FlorianRappl/MagesPackages" could be the primary feed. Then a convention could be used to retrieve packages:

  • master is used for a list of all packages incl. meta-data (each package is a sub-directory with a README.md, and a package.json file (+ auxiliary content files, whatever seems reasonable)
  • each package lives in its own (orphan) branch, i.e., versioning is taken by git via hashes
  • submitting a package is done via a PR
  • downloading a package is more or less straightforward

@FlorianRappl
Copy link
Owner Author

I think the repositories feed is the way to do it. It would involve creating a bit of custom tooling (for consuming, producing, and managing packages), but it would be worth the effort in my opinion. It should be considered quite minimalistic (at least at first). It would allow anyone to create his / her own feed easily.

@FlorianRappl FlorianRappl removed this from the 3.0.0 milestone Jul 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant