Conversation
if we're strict about the verbiage, this is a repository not a channel and it is joined together with other repositories into the final public channel https://github.com/wbond/packagecontrol.io/blob/master/app/html/docs/channels_and_repositories.html#L7 ... assuming I understand this correctly of course note that sublimelsp calls their version of same "repository"
|
Although the libraries channel is mostly also just a repository? https://github.com/packagecontrol/channel/blob/main/repository.json ... I'm confused 😵💫 |
|
Yes, this is not a channel. We actually have three repository files here in this repo. And the main repository is packages.json which links to the other ones. The "project" (we would say (git) repository) at "packagecontrol/channel" is named channel because deathaxe likely wanted to claim that name, it hosts a library repository and outputs via GitHub actions the library channel which is part of Package Control (the client) settings. In "thecrawl" I call this whole part "the registry" because that is a name that is not confusing. The really confusing part is that on wbond's channel repo we have the true initial "channel.json" (<- wrong name) which we use as the seed for the registry. This channel.json is only a link to other files. So the really initial seed of the crawler is literally called "channel.json" and the final product is also called "channel.json". And these are very different things. Why is this called "private" here in the README. It is very public. "Public registry for SublimeLinter plugins." avoids a lot of this, and is probably okay for end-users. |
|
Even more words: "Private repository for SublimeLinter plugins." This clashes in multiple ways. A user would say, well that is a public (git) repository, wth? The whole project (repository) is used as a registry (Make a PR. Then you get listed.) The file packages.json is itself registered at wbond. The first chapter at https://github.com/wbond/package_control_channel#package-control-default-channel is good. |
Yes, I like that.
Indeed, the word "repository" is very unfortunate here. Especially since the PC client package has an "add repository" command, and as a user, how I am supposed to understand what input that takes other than "oh I bet I can paste my GitHub repo url in there"? Oh, and guess what: in that context that is in fact what it means, so there a "repository" is a git repository. But it also has a "new repository" command. And guess what? That creates a new "package control repository" json file. /rant Breathe in breathe out ... Anyway, this thing here, and actually also the libraries thing, are perhaps "repositories", but certainly "registries", and most definitely not "channels". I'll do my best to document, one thing at a time etc.
That is indeed good. |
|
I think that's good. Forgot that it is still open. |
2 participants
So, I'm reviewing documentation for the site etc. If we're strict about the verbiage, this is a repository not a channel and it is joined together with other repositories into the final public channel.
https://github.com/wbond/packagecontrol.io/blob/master/app/html/docs/channels_and_repositories.html#L7
... assuming I understand this correctly of course. Note that sublimelsp calls their version of same "repository": https://github.com/sublimelsp/repository