-
-
Notifications
You must be signed in to change notification settings - Fork 49
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
[Feature] KitX Project Development Auxiliary Utility #275
Labels
enhancement
New feature or request
Comments
I have already been thinking on this thing, temporarily named |
This isssue can close after cheese config files merged into KitX source tree, thank you. |
To accommodate this new auxiliary tool, I am re-architecting the KitX project. |
Tracked by #228 . |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
🪦 Is your feature request related to a problem? Please describe.
I think Crequency need a development auxiliary utility to help maintainer develop KitX or other software.
🪧 Describe the solution you'd like
The utility needs to have the following features:
Package management is important for multi-package software like KitX.
It should support check package version and report version-conflit problems when initializing.
Like Git Submodule, but submodule is too weak(must have SSH pubkey) to initializing KitX, we can use development auxiliary utility to initializing subpackages(the utility support multi ways to get subpackages, but we MUST reserve submodule infomation).
The utility should support building, packaging, distributing project packages(and subpackages). We should distribute source-code package and binary package for multi platforms. It should check building requirements and it MUST support the building of multi-program-language packages.
It's a very import feature but we often neglecting. We can run linting in this way to launch multi languages' lint program.
It can generate documention like
man
manual in GNU/Linux. Generate a HTML documment or NLS support for include file is a good idea.Support CI/CD is a good feature. We can use this to make CI/CD script easier.
The utility should have NLS support. Because it faces developers. We can use this to improve development efficiency.
🧾 Describe alternatives you've considered
No response
📎 Additional context
No response
The text was updated successfully, but these errors were encountered: