#SDK aliases

1 messages ยท Page 1 of 1 (latest)

dusky moth
#

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

potent atlas
#

contrib or x (for experimental)

dusky moth
#

i like both of those

#

x is common in go, but might not be elsewhere?

timber grove
#

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". ๐Ÿ™‚

potent atlas
#

or could use dag/ for official but not bundled sdks

timber grove
#

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.

pure tinsel
#

contrib is also the naming convention for one of Debian's package repositories

timber grove
#

Pinging @indigo obsidian for ecosystem.

pure tinsel
#

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

dusky moth
#

another option is community/<sdk> - that's another fairly common one

pure tinsel
#

community is very clear, I don't think anyone could misconstrue that one.

That naming convention is used in Blender for the same reason.

pearl saffron
#

vote for community ๐Ÿ™‚

dusky moth
#

will throw something together then ๐ŸŽ‰

dusky moth
#

it depends on another pr i've been working on so we can get the version pinning working correctly ๐Ÿ™‚

potent atlas
#

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?

dusky moth
#

which is nice, since it'll stay up-to-date

potent atlas
#

oh, that's perfect

dusky moth
#

@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

potent atlas
#

that makes sense

dusky moth
#

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)

pearl saffron
#

Is it support a commit like community/php@<commit> ? Seeing from the PR, it should work out of the box.

dusky moth
#

yup, added that support after your suggestion ๐Ÿ˜„

pearl saffron
#

Love it! ๐Ÿ˜„