You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
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.
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 ...
Currently, I tend to use the NuGet infrastructure. This would provide all required metadata, dependencies, and integrated support from the .NET side.
The text was updated successfully, but these errors were encountered: