#SDK aliases
1 messages ยท Page 1 of 1 (latest)
It would be really cool to not have the whole github.com/dagger/dagger/... required in dagger.json
Technically it's merged upstream, and we should have a way of making it "special" - will also avoid typos, etc.
We shouldn't bundle it (at least for now) - that takes up lots of space, it should just be for the core sdks that are relatively stable
But we could have aliases - <prefix>/php and <prefix>/elixir would be really cool
cc @timber grove @pearl saffron @pure tinsel
contrib or x (for experimental)
Yeah, we used to use /x/ in the cue days for user contributed packages that weren't stable enough to go in our stdlib.
It was our "universe", before the "daggerverse". ๐
or could use dag/ for official but not bundled sdks
contrib is more common outside of Go. I've seen that in projects on different programming languages.
It usually means exactly what it is for the PHP SDK.
contrib is also the naming convention for one of Debian's package repositories
Pinging @indigo obsidian for ecosystem.
I like x because it's short, but I personally have not seen that before and wouldn't have known what it meant without the explanation.
I like contrib because it's quite clear what it is, but it is a bit longer. (And I might be bias because I have seen that one before)
That's my thoughts at least
another option is community/<sdk> - that's another fairly common one
community is very clear, I don't think anyone could misconstrue that one.
That naming convention is used in Blender for the same reason.
vote for community ๐
will throw something together then ๐
This allows users to use community/elixir to use the elixir SDK, and community/php to use the php SDK, without needing the full github.com/dagger/dagger/sdk/<sdk>/runtime@<version> URL ...
it depends on another pr i've been working on so we can get the version pinning working correctly ๐
that was โก fast
@dusky moth minor comment to resolve on that
My understanding is that you can now do --sdk=community/php but the full git url will be put in the dagger.json for the module?
tested this, nope, the dagger.json will have community/php
which is nice, since it'll stay up-to-date
oh, that's perfect
@pearl saffron mentioned we should allow explicitly pinning it though, i like that idea - you should be able to do community/php@specific-version if you want
that makes sense
potentially this is kinda cool as well - you could pin to a future version of an sdk if you can't upgrade for whatever reason (so i guess we should be a bit more conservative in updating engineVersion values for the sdks so we don't close that avenue)
Is it support a commit like community/php@<commit> ? Seeing from the PR, it should work out of the box.
yup, added that support after your suggestion ๐
Love it! ๐