You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What are your opinions on where the sub-commands should reside? In this repo or in scikit-build-core[cli]?
if we have it in this repo the dependencies in skbuild-core are minimized, but it is less flexible about changing the upstream api, like how we call cmake.configure, and vice-versa if we move the subcommands
in both cases there should be some integration testing that we can call from one-another
how will we handle the version dependencies? We'll keep backwards compatibility on this cli or move lower-upper bound dependency?
The text was updated successfully, but these errors were encountered:
I think inside this repo. That keeps scikit-build-core clean and with minimal dependencies. Since we control both packages, we can pin somewhat (>=0.6,<.7) - we can release a new version once we know 0.7 won't change the API, etc. Though the basics should be pretty stable, and scikit-build-core is supposed to be usable as a plugin.
What are your opinions on where the sub-commands should reside? In this repo or in
scikit-build-core[cli]
?cmake.configure
, and vice-versa if we move the subcommandsThe text was updated successfully, but these errors were encountered: