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
Copy file name to clipboardExpand all lines: README.md
+22-6Lines changed: 22 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,7 +19,8 @@
19
19
20
20
Install, update, uninstall and view information about debian packages.
21
21
22
-
Eddy can also support other packaging formats such as .rpm thanks to it's PackageKit backend, although it's primary focus is managing debian packages and being designed for elementary OS.
22
+
Eddy can also support other packaging formats such as .rpm thanks to its PackageKit backend, although its primary focus
23
+
is managing debian packages and being designed for elementary OS.
23
24
24
25
## Installation
25
26
@@ -31,9 +32,12 @@ These dependencies must be present before building
31
32
-`packagekit-glib2`
32
33
-`unity`
33
34
34
-
You can install these on a Ubuntu-based system by executing this command:
35
+
You can install these on an Ubuntu-based system by executing this command:
When reporting a bug you should include as much information as possible, that is the system that you're running, what you did in order to have the bug appear and probably a simple list of steps on how to reproduce the issue, however it is not required as some issues are not easily reproducible.
55
+
## Running tests
56
+
After `meson build` is complete, run
57
+
```
58
+
ninja -C build
59
+
```
60
+
once, and after that each time there's a change in a unit test, run
61
+
```
62
+
meson test -C build
63
+
```
64
+
65
+
It should print OK on all the tests at the end of the output.
66
+
67
+
## Reporting bugs & debugging
68
+
When reporting a bug, you should include as much information as possible, that is the system that you're running, what you did in order to have the bug appear and probably a simple list of steps on how to reproduce the issue, however, it is not required as some issues are not easily reproducible.
53
69
54
-
Additionally you can include a debug log in the description of the issue. To get a full log of backend and application messages, you can execute Eddy in a terminal with the following command:
70
+
Additionally, you can include a debug log in the description of the issue. To get a full log of backend and application messages, you can execute Eddy in a terminal with the following command:
55
71
`G_MESSAGES_DEBUG=all com.github.donadigo.eddy --debug`, reproduce the bug in the application window and copy the terminal output to the issue's description.
56
72
This information could really help localizing and fixing the issue.
0 commit comments