02:20 <FromGitter> <naqvis> for bindings generation I use `crystal_lib` and then do some cleanups

17:24 <riza> https://lobste.rs/s/umicte/give_up_github#c_vdm1qa this person raises a few good points, which might apply to the shardfile spec

17:25 <FromGitter> <Blacksmoke16> how so?

17:25 <FromGitter> <Blacksmoke16> isnt really anything tightly coupling shards to GH

17:26 <riza> specifically their comment about special treatment for github hosted dependencies

17:26 <FromGitter> <Blacksmoke16> there isnt tho?

17:27 <FromGitter> <Blacksmoke16> you need to explicitly say `github: foo/bar`

17:31 <riza> I guess I view having a "github" type there to be special treatment

17:32 <riza> any git repo can already be used, no need for proliferation of github/gitlab/gitxxx

17:32 <FromGitter> <Blacksmoke16> that bullet calls out `package.json` having short codes for other sources, but if you just use `foo/bar` it defaults to GH

17:33 <FromGitter> <Blacksmoke16> > contrast to Nix + nixpkgs that only allows a short code like sourcehut:~user/repo for several common forges or the full URL (with no specialer, shorter treatment for GitHub, just github:user/repo)

17:33 <FromGitter> <Blacksmoke16> i took that to mean its not special if you need to say its GH, but would be special treatment if you just did like `my_shard: foo/bar` and it assumes `github.com/foo/bar`

17:37 <riza> I agree that was their intent, which is why I said it might apply to the shardfile spec

17:38 <riza> just something to keep in mind is all