Gregor Riepl

Ok... that does make sense. It would be great have a full overview of the differences somewhere, though. Which resources would have naming issues? In any case, I don't think...

> > It would be great have a full overview of the differences somewhere, though > > Agreed. > #798 Thank you! I'll comment there if I encounter any particular...

Sure! Pipfile: ```toml [[source]] name = "pypi" url = "https://pypi.org/simple" verify_ssl = true [requires] [dev-packages] [packages] cdktf = "~=0.4.1" boto3 = "~=1.17.97" cdktf-cdktf-provider-aws = "~=1.0.103" ``` cdktf.json: ```hcl { "language":...

While splitting off the individual sub-libraries may certainly be a good idea, it doesn't solve the issue that the whole stb library is still unversioned. I'm a Debian package maintainer,...

That's awesome! Thank you very much!

On second thought... Is that version "official" or will the scheme be changed later? I can go ahead with your fork, but if the repository is going to be moved...

The concept is that you give an individual commit a "name", usually a release version. You can also do this retrospectively. The basics of tagging: https://git-scm.com/book/en/v2/Git-Basics-Tagging Github doesn't really have...

I don't think versions have to be tied together. Having a separate version for each header file would just mean they'll have to be packaged separately. If they all carry...

As for 2., I don't think that makes a lot of sense. If you tag individual header releases in the _same_ repo with different versions, that will make things very...

I respect your decision; while there's certainly value in having a central place to share code and collaborate, it creates a monoculture and that's rarely a good thing. Microsoft is...