Package Details: hydrus 624-1

Git Clone URL: https://aur.archlinux.org/hydrus.git (read-only, click to copy)
Package Base: hydrus
Description: Danbooru-like image tagging and searching system for the desktop
Upstream URL: http://hydrusnetwork.github.io/hydrus/
Licenses: WTFPL
Conflicts: hydrus-docs-dummy
Submitter: Score_Under
Maintainer: Score_Under (turtletowerz)
Last Packager: turtletowerz
Votes: 44
Popularity: 1.83
First Submitted: 2015-02-28 18:11 (UTC)
Last Updated: 2025-05-29 04:46 (UTC)

Dependencies (39)

Required by (3)

Sources (5)

Pinned Comments

turtletowerz commented on 2025-02-05 23:14 (UTC)

The AUR package for JpegXL support is outdated and does not build. If you need JpegXL support, follow the instructions in the comment I posted to update the PKGBUILD.

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 .. 13 Next › Last »

Score_Under commented on 2023-03-31 13:38 (UTC)

Can you elaborate on what issues you've had with those packages? If they are causing problems then that should probably be reported to the maintainers of those packages too

joehillen commented on 2023-03-30 18:55 (UTC)

It's not about space. It's about having a bunch of poorly managed packages that keep breaking and interfering with other stuff is why I remove them.

Score_Under commented on 2023-03-29 19:48 (UTC)

Given that there are a couple of people with complaints about installing the python dependencies for the documentation specifically, as much as I would like to say install gentoo (not just as a meme this time, since gentoo's approach is towards fine-grained customisation of this type of thing), I've instead put in a nasty hack in the PKGBUILD to change the build-time dependency list depending on whether docs are included or not. This is by no means a standard thing to do and likely won't play nice with AUR helpers, so you may need to build it with standard tools instead, but if you edit /etc/makepkg.conf and disable docs there, it will avoid pulling those dependencies in.

To clear up a misconception I've seen in the comments here, it does affect a lot of built-in help when you exclude the documentation:

  • Changelog is broken
  • Easy downloader import help is broken
  • Downloader sharing help is broken
  • Gallery URL generators help is broken
  • Downloader URL classes help is broken
  • Login scripts help is broken
  • Database migration help is broken
  • HTML subscriptions help is broken
  • Duplicates processing help is broken
  • Page parsers help is broken
  • Content parsers help is broken
  • HTML, JSON, Compound, and Context Variable formula help are all broken

I don't think this is an acceptable experience for beginner users of hydrus, and it is only reluctantly that I have made a change that beginners might accidentally fall head-first into.

@joehillen I notice that your copy-paste output there has "old version" empty for all those dependencies. Please consider answering "no" when asked if you want to remove make dependencies after installation, as that is the path of least resistance for everyone and costs you about 20MB while avoiding the repeated re-download and rebuild that seems to be the issue you're having.

If 20MB is too far out of your space budget then I question the use of Hydrus, which is very space-hungry by its nature.

joehillen commented on 2023-03-28 03:20 (UTC) (edited on 2023-03-28 03:21 (UTC) by joehillen)

I don't need/want any of this crap:

community/python-csscompressor                        0.9.5-5      No
community/python-editables                            0.3-2        No
community/python-ghp-import                           1.1.0-3      No
community/python-hatch-nodejs-version                 0.3.1-1      No
community/python-hatch-requirements-txt               0.3.0-1      No
community/python-hatchling                            1.13.0-1     No
community/python-livereload                           2.6.3-2      No
community/python-pyaml                                21.10.1-1    No
community/python-regex                                2023.3.23-1  No
community/python-tornado                              6.2.0-2      No
community/python-watchdog                             2.3.0-1      No

Aur (14)                                 Old Version  New Version  Make Only
aur/python-mergedeep                                  1.3.4-2      No
aur/python-mdx-gh-links                               0.2-1        No
aur/python-pyyaml-env-tag                             0.1-1        No
aur/mkdocs                                            1.4.2-1      No
aur/python-htmlmin2                                   0.1.13-1     No
aur/python-jsmin                                      3.0.1-1      No
aur/mkdocs-minify-plugin                              0.6.4-1      No
aur/pymdown-extensions                                9.10-1       No
aur/mkdocs-material-extensions                        1.1.1-1      No
aur/mkdocs-material                                   9.1.3-1      No

If I need to read the docs, I'll just go online.

joehillen commented on 2023-03-28 03:16 (UTC)

Just please remove the docs stuff from this package. Anyone using the AUR just wants the software. I've never seen another AUR package require the documentation as part of the build, and the mkdocs deps are a broken mess.

If anyone needs to build the docs, they should go build them from source themselves, which should really only be the Hydrus maintainers.

neopolitan commented on 2023-03-21 15:51 (UTC) (edited on 2023-03-21 15:52 (UTC) by neopolitan)

Thank you. I really appreciate having this pkgbuild available. And I prefer having the docs available to not.

Score_Under commented on 2022-12-14 12:54 (UTC)

This was a split PKGBUILD in 2016 but people didn't seem to like it because it interacted poorly with the AUR helpers they used. (read the comments from the second-last page for context). Since the mkdocs stuff is a makedep it can just be uninstalled after the package is built, or even never installed at all if you have a remote build host doing it for you. The DOC_DIRS variable is set in the PKGBUILD, which should allow for people to strip the docs out of the final package if they set the correct options in their makepkg.conf.

The only leftover parts of this process if you don't want docs are the need to render them in the first place and the need for the mkdocs tool to accomplish that. If you offload the building to a remote machine or chrooted build, then you never even need mkdocs installed on the machine running hydrus in the first place, so the only vestiges you get are the fact that the package files for it were downloaded, and the short couple of seconds extra in the packaging process to build the docs which might get discarded anyway.

I don't think people are asking for a split PKGBUILD. I think they're asking for multiple PKGBUILDs to completely remove the mkdocs step in this one, e.g. to quote HydrusUser "It's very annoying having to remove [mkdocs] every single time there's an update". Though of course doing so would mean that the docs package needs to be released separately, and there would be little guarantee for the users using AUR helpers that their versions are congruent between the doc and main packages. If people do want this split up into two separate pkgbases, I will take some convincing (alternatively I'm happy to appoint more co-maintainers).

QuartzDragon commented on 2022-12-14 08:26 (UTC)

@Score_Under

Various Arch packages also provide -docs packages, which are split off into their own package, but built from the same PKGBUILD.

Why not just make the docs optional?

Score_Under commented on 2022-12-13 11:11 (UTC)

The reason it's built this way right now is because it's all from the same sources. Now that the jsmin package has been orphaned and allowed to update again, the python2 dependency chain should be gone. Since docs installed seems to be the norm for Arch packages, what is the problem that having the docs installed, or having mkdocs installed, is causing for you?

andiandi commented on 2022-12-12 05:34 (UTC)

Wouldn't it be easier for all, if the package was split in hydrus and e.g. hydrus-docs? From looking at the PKGBUILD I do not see a reason not to do this. This seems to be the way many packages handle offline docs that are rather rarely needed.

« First ‹ Previous 1 2 3 4 5 6 7 8 9 .. 13 Next › Last »