Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/donadigo/eddy
A debian package installer for elementary OS
https://github.com/donadigo/eddy
Last synced: about 17 hours ago
JSON representation
A debian package installer for elementary OS
- Host: GitHub
- URL: https://github.com/donadigo/eddy
- Owner: donadigo
- License: gpl-3.0
- Created: 2016-04-25T18:10:39.000Z (over 8 years ago)
- Default Branch: master
- Last Pushed: 2023-08-07T15:02:22.000Z (over 1 year ago)
- Last Synced: 2024-10-25T11:37:49.723Z (about 2 months ago)
- Language: Vala
- Homepage:
- Size: 795 KB
- Stars: 176
- Watchers: 4
- Forks: 33
- Open Issues: 28
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
- awesome-elementaryos - Eddy - Simple debian package installer [:white_check_mark:](https://appcenter.elementary.io/com.github.donadigo.eddy.desktop) (Applications / Accessories)
README
Eddy
A debian package installer for elementary OS
Install, update, uninstall and view information about debian packages.
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.
## Installation
### Dependencies
These dependencies must be present before building
- `valac`
- `gtk+-3.0`
- `granite`
- `packagekit-glib2`
- `unity`
You can install these on a Ubuntu-based system by executing this command:
`sudo apt install valac libgranite-dev libpackagekit-glib2-dev libunity-dev meson ninja-build libzeitgeist-2.0-dev gettext`
### Building
```
meson build && cd build
meson configure -Dprefix=/usr
ninja
```
### Installing & executing
```
sudo ninja install
com.github.donadigo.eddy
```
### Reporting bugs & debugging
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.
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:
`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.
This information could really help localizing and fixing the issue.