-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add "releases" and TEAPOT? #8
Comments
?? You mean release tag (branch)?
It is not so, currently? I mean it can be succesfully build within TEA infrastructure as any other tcl-module (e. g. tcl-thread, etc), and exactly so installed... See for example the test-build in Travis. Or I miss something?
Thanks! |
BTW, I'm not really familiar with TEA, 'cause don't use it... I've just my own infrastructure, as well as my own Tcl :) |
@sebres yeah - releases / tags - each "version" should be released with a tag so that for example a build script may look like this:
This one is how https://kitcreator.rkeene.org/fossil/index handles it TEAyou very well could be compliant - I honestly dont know the specifics of it either :-P I just know it makes compiling much simpler / automated for me :-) I know it usually means you need a tclconfig folder in your archive. It should be included so that manual steps dont have to be taken to get it (using the cvs command or w/e). -- You can see how they did it here: |
Definitely not. Because:
|
Ok, well it's your repo! It may work - I will try it if you could add releases as I don't personally want to use master and get different results on each compilation from our various system(s). I just see that most other repos are including the tclconfig part but it may not be necessary. Just hoping to see things standardized as possible to aid in tooling, etc. Either way - thanks again! |
BTW. The versioning here was made intentionally a bit stricter - because this module integrates self much deeper as normally, it is extream important, IMHO.
BTW. I should still change this model, because at least on Mac with 32-bit version number it has currently a known issue:
Apple's logic looks like this: x = 8; y = 6; z = 701;
(x << 16) | ( y << 8 ) | z; This means "z" should not exceed 255 (otherwise overrides "y"). |
Just a quick look here. Would be nice if you added version releases to this so we can have versioned archives / tarballs as well as support for the standardized TEA so build tools can automatically include.
Awesome to see this being worked on! Thanks for your hard work on it!
The text was updated successfully, but these errors were encountered: