Package Details: hydrus 311-1

Git Clone URL: (read-only)
Package Base: hydrus
Description: Danbooru-like image tagging and searching system for the desktop
Upstream URL:
Licenses: WTFPL
Conflicts: hydrus-docs, hydrus-sources
Submitter: Score_Under
Maintainer: Score_Under
Last Packager: Score_Under
Votes: 14
Popularity: 0.208260
First Submitted: 2015-02-28 18:11
Last Updated: 2018-06-21 21:24

Latest Comments

Aelius commented on 2018-04-07 22:25

Regarding the official release archives

Indeed. To further explain the context for the benefit of others, the developer seems to have no experience or knowledge of OS best practices, general security concerns, or how to properly integrate software into any modern operating system. You can't package it as-is. He is receptive to suggestions and is respectful, but in general I think he is set in his ways. Another thing to point out is how he doesn't really use git- github is just a glorified webhost to him. No granular commits, no PR, no attention paid to issues. Just uploads a week's work in one commit. There are fewer commits than there are releases!

Because of this scattered haphazard strange development, changes are necessary when trying to integrate hydrus into a package manager. These changes either have to come from upstream, or the package maintainer. Since the dev doesn't use github-issues or accept PRs, if you want upstream changes you have to take your plight to either the imageboard or the discord. Both are filled with younger teens who also don't understand how computers works, and in general your voice will be drowned out by their insistence that the dev shouldn't waste time on things like that. Which is amusing, I don't think they appreciate how rare it is for a side project to consistently update week-by-week. There's plenty of development time to go around.

To be fair, some of the issues are inherit to targeting Windows as the primary platform.

Score_Under commented on 2018-04-07 12:47

@qlipsos, thanks for the heads up, I've added it to the requirements.

@irlittz, the split-package structure is mostly because it was easier to keep it that way. If it's causing problems I can easily switch it back. Regarding the official release archives, that's partly why I decided to create an AUR package in the first place. They contain a lot of packaged binary dependencies (which are an unnecessary risk), strip permissions (everything is 755), and end up with the incredible filesize of 176MB. Updates from git generally pull less than 1MB per version, which makes the whole process go a lot faster (considering download time and extraction time).

qlipsos commented on 2018-04-05 18:34

'gtkglext' was required in my case.

irlittz commented on 2018-01-25 10:46

Thanks! Is there a reason why your PKGBUILD still has the split-package structure or why you are not using the official release archives?

Score_Under commented on 2018-01-24 21:32

Apologies for keeping you waiting. I've finally pushed the 290 update (and included working recipes for 289 and 288 in the history just in case).

Score_Under commented on 2018-01-21 23:40

I see you've found the complications already - there is no python 2 version of wxpython 4+ on the AUR yet. I'm not too sure of the implications either of installing both wxwidgets 3.x and 4.x at the same time, though there are no filesystem-level conflicts.

irlittz commented on 2018-01-21 01:06

@Score_Under are there any complications in updating the package? The current release version seems to be at version 290.

Updated hydrus PKGBUILD:

Modified wxpython-phoenix PKGBUILD:

I'll ask the creator for wxpython-phoenix to turn it into a split package. The name might change. After installing both of these Hydrus 290 starts, however I had to manually specify the path to my Hydrus database using the -d option.

Score_Under commented on 2017-07-30 15:44

The python-lz4 manual update shouldn't be necessary any more - I've succeeded in taking ownership of the package and updated it to the latest version.

irlittz commented on 2017-07-30 14:31

@Score_Under thank you for updating! For anyone else wanting to install this now: you'll have to manually update the PKGBUILD for python2-lz4 and install it yourself. This is what I did Feel free to use, if you think it is adequate.

EDIT: Nevermind, apparently Score_Under has ownership of that package now, and it is updated. Thank you again.

irlittz commented on 2017-07-29 18:18

@Score_Under did you abandon this package? I'm asking because it would have been easily possible to create a temporary AUR package that provides/replaces python2-lz4 instead of waiting for more than a month for a change that is not coming. When you hopefully get around to doing this, adding hdf5 as a dependency will be needed.

All comments