juliagoda / kuser Goto Github PK

How to use the program and what it can do

1. Write descriptive titles and subtitles
2. Use annotated screenshots
3. Show examples and end results

• Update image and text files
• Update links

Creating unit tests will be necessary to accommodate future pull requests and to monitor regression errors

Describe the bug
Version v16.08.03 does not compile with KF5/KF6 libraries

To Reproduce
Steps to reproduce the behavior:

1. Go to https://pkgs.org/download/kuser
2. Click on the package of your choice for the format (rmp, deb, etc.)
3. Scroll down to the "Download" category
4. Click on the URL next to "Binary Package"
5. Save the package on your system
6. Try to install and run the program

Expected behavior
The program should build and install without any problems with the help of the current compiler and libraries

Actual behavior
Doesn't compiles/work as expected

Desktop (please complete the following information):

• Arch Linux
• own kernel
• kuser v16.08.03

• Rename ChangeLog to CHANGELOG.md
• CODE_CONVENTIONS.md
• CODE_OF_CONDUCT.md
• GLOSSARY.md
• CONTRIBUTING.md
• CONTRIBUTORS.md
• CREDITS.md
• README.template
• Rename COPYING to LICENSE
• Remove TODO

• customizing CMakeLists.txt for new version of cmake
• adapting to modern convention of running a project with cmake

Link: https://docs.salome-platform.org/latest/dev/cmake/html/various.html

Some degree of task automation would be useful. Below is a proposal for workflows:

• Codecov
• Create pull request
• arch-pkgbuild-action
• build-deb-action
• build-rpm-action
• action-gh-release
• Issue templates
• Stale
• CMake based projects
• Labeler
• Coverity Scan

Changing the code in terms of repetitions found, dependency compliancy, future code expansion, etc.

It would be good to organize the files in case the project grows and more files of different types that will appear in the future.

Link: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2018/p1204r0.html

There is outdated information in the README