-
Notifications
You must be signed in to change notification settings - Fork 21
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
Expose tlapm_lib for other projects. #154
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: Karolis Petrauskas <[email protected]>
Signed-off-by: Karolis Petrauskas <[email protected]>
Signed-off-by: Karolis Petrauskas <[email protected]>
Signed-off-by: Karolis Petrauskas <[email protected]>
Signed-off-by: Karolis Petrauskas <[email protected]>
Signed-off-by: Karolis Petrauskas <[email protected]>
@kape1395 Is the idea we would publish TLAPM as a package to OPAM? Do you think it would be a good idea to split off the parser into its own package, since that is probably the only thing people would want to consume? |
That would be useful, but that's probably not only the parser. I once tried to make it publishable via OPAM, but the build failed when performed in OPAM while succeeding from the source directly. Something has to be double-checked. |
I think it might not make sense to publish all of TLAPM as an OPAM package, but things like the parser - which could be used in other projects, like a formatter - would make sense. I'll keep the idea of separating the parser out into its own source directory in the back of my mind, I'll be writing a lot of tests for it in the future. With regard to these changes, what would you say their objective is? |
No description provided.