Package Details: hydrus 571-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: custom
Conflicts: hydrus-docs-dummy
Submitter: Score_Under
Maintainer: Score_Under
Last Packager: Score_Under
Votes: 40
Popularity: 0.99
First Submitted: 2015-02-28 18:11 (UTC)
Last Updated: 2024-04-18 14:00 (UTC)

Latest Comments

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

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?

And1G 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.

ardency commented on 2022-12-12 03:54 (UTC)

@HydrusUser You might find it useful to use an AUR helper that supports the removal of makedepends packages automatically after an install, or add an alias to do this. See here: https://bbs.archlinux.org/viewtopic.php?id=176614

HydrusUser commented on 2022-12-11 20:42 (UTC)

Without MkDocs, Hydrus will simply ask you if you want to open a webpage for the online version of the help menu instead. I'd imagine that the number of users that need an offline help is extremely small, so I personally don't see the need to keep MkDocs. It's very annoying having to remove it every single time there's an update.

Score_Under commented on 2022-12-01 02:15 (UTC)

@Firegem I don't want to stop building docs if possible, as that impacts the help menu in the program, so for now I've forked the AUR package in question (python-jsmin), and hopefully it'll be disowned at some point so I can revert it again. Hopefully people's AUR helpers should cotton on and realise that they don't need to pull in the original problematic version but I don't know how intelligent those tools are in terms of dependency solving.

BTW, python2-bin should solve the problem for people who don't want to build the package themselves, or if the worst comes to the worst, I'm hosting the deps prebuilt by an automated jenkins thing (https://gurren.score.moe/jenkins/job/pkgbuilds/)

firegem commented on 2022-11-29 06:08 (UTC)

I think this package should stop building documentation. There's no reason to expect people to download and compile python2 by default. Also see: https://github.com/hydrusnetwork/hydrus/issues/1243

ardency commented on 2022-11-25 00:34 (UTC)

I was able to solve the ongoing upstream issue by replacing python-qtpy from community with python-qtpy-git from AUR. This installed v2.3.0, which contains the fix. Hopefully the community package can be updated soon, as this release has been out for over two weeks!

HydrusUser commented on 2022-10-22 20:10 (UTC)

"If you want to manually apply the patch you can do so removing from the pkgbuild the lines marked with - in the patch and adding lines marked with + in the patch. All lines not starting with - or + are there to show where the changes should be made and are not part of those changes."

Thank you for explaining this. I was able to edit the build files, and it built and updated Hydrus successfully. Thanks for the help!

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