|
3 週之前 | |
---|---|---|
.github/ISSUE_TEMPLATE | 2 月之前 | |
.tx | 7 年之前 | |
core | 1 月之前 | |
help | 1 月之前 | |
hscommon | 1 月之前 | |
images | 1 月之前 | |
locale | 1 月之前 | |
pkg | 1 月之前 | |
qt | 3 週之前 | |
qtlib | 1 月之前 | |
.ctags | 4 年之前 | |
.gitignore | 7 月之前 | |
.travis.yml | 1 月之前 | |
CREDITS | 3 月之前 | |
LICENSE | 6 年之前 | |
Makefile | 1 月之前 | |
README.md | 3 週之前 | |
Windows.md | 1 月之前 | |
build.py | 3 週之前 | |
macos.md | 1 月之前 | |
package.py | 1 月之前 | |
requirements-extra.txt | 1 月之前 | |
requirements.txt | 1 月之前 | |
run.py | 1 月之前 | |
setup.nsi | 1 月之前 | |
tox.ini | 1 月之前 | |
win_version_info.temp | 1 年之前 |
dupeGuru is a cross-platform (Linux, OS X, Windows) GUI tool to find duplicate files in a system. It is written mostly in Python 3 and has the peculiarity of using multiple GUI toolkits, all using the same core Python code. On OS X, the UI layer is written in Objective-C and uses Cocoa. On Linux, it is written in Python and uses Qt5.
The Cocoa UI of dupeGuru is hosted in a separate repo: https://github.com/arsenetar/dupeguru-cocoa
Still looking for additional help especially with regards to:
This folder contains the source for dupeGuru. Its documentation is in help
, but is also
available online in its built form. Here’s how this source tree is organized:
For windows instructions see the Windows Instructions.
For macos instructions (qt version) see the macOS Instructions.
When running in a linux based environment the following system packages or equivalents are needed to build:
Note: On some linux systems pyrcc5 is not put on the path when installing python3-pyqt5, this will cause some issues with the resource files (and icons). These systems should have a respective pyqt5-dev-tools package, which should also be installed. The presence of pyrcc5 can be checked with which pyrcc5
. Debian based systems need the extra package, and Arch does not.
To create packages the following are also needed:
dupeGuru comes with a makefile that can be used to build and run:
$ make && make run
$ cd <dupeGuru directory>
$ python3 -m venv --system-site-packages ./env
$ source ./env/bin/activate
$ pip install -r requirements.txt
$ python build.py
$ python run.py
To generate packages the extra requirements in requirements-extra.txt must be installed, the steps are as follows:
$ cd <dupeGuru directory>
$ python3 -m venv --system-site-packages ./env
$ source ./env/bin/activate
$ pip install -r requirements.txt -r requirements-extra.txt
$ python build.py --clean
$ python package.py
This can be made a one-liner (once in the directory) as:
$ bash -c "python3 -m venv --system-site-packages env && source env/bin/activate && pip install -r requirements.txt -r requirements-extra.txt && python build.py --clean && python package.py"
The complete test suite is run with Tox 1.7+. If you have it installed system-wide, you
don’t even need to set up a virtualenv. Just cd
into the root project folder and run tox
.
If you don’t have Tox system-wide, install it in your virtualenv with pip install tox
and then
run tox
.
You can also run automated tests without Tox. Extra requirements for running tests are in
requirements-extra.txt
. So, you can do pip install -r requirements-extra.txt
inside your
virtualenv and then py.test core hscommon