-
Notifications
You must be signed in to change notification settings - Fork 4
Import installer scripts and nutconf tool #161
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
Conversation
…_http() => nutscan_scan_xml_http_range()
…use more library paths
6c3e82f to
c181a4d
Compare
|
Coverage also complains about C++ quality (probably needs to be at least quiesced before PR merge, at best actually solved, to not block builds): Overall: |
… impact of nutconf codebase quality by default
…nutconf... for CI farm)
2cfeaa5 to
a43b1bb
Compare
|
For now, neutered this by |
|
Note: the build failures are reported by upstream NUT CI farm check of this PR, since the codebase is not clean enough to pass the "medium" warnings level yet. IPM2 farm is more relaxed and has no qualms with this submission. |
...and of IPSS_Unix installer/helper scripts
fed7ec2 to
169d3c5
Compare
Got this to build; usability not tested so far (
nutconf --helpdoes not crash at least)C++ style there needs several patterns of face-lift:
Historic note: effort is related to upstream-NUT feature not merged yet, with networkupstools#6 for context