Package Details: pkgbrowser 0.28.1-3

Git Clone URL: https://aur.archlinux.org/pkgbrowser.git (read-only, click to copy)
Package Base: pkgbrowser
Description: A utility for browsing pacman databases and the AUR
Upstream URL: https://codeberg.org/kachelaqa/pkgbrowser
Licenses: GPL2
Submitter: kachelaqa
Maintainer: kachelaqa
Last Packager: kachelaqa
Votes: 282
Popularity: 1.84
First Submitted: 2011-04-20 18:18 (UTC)
Last Updated: 2024-09-16 22:12 (UTC)

Latest Comments

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

mser commented on 2021-05-10 20:56 (UTC) (edited on 2021-05-10 20:56 (UTC) by mser)

@kachelaqa

Hydrus, for example, usually supports both (using said python-qtpy). There's a known issue right now when using python-pyqt5 because of an oversight from the Hydrus developer (which is why I've forced pyside2 as dependency for now), but other than that there haven't really been any problems.

This is actually what prompted me to ask if PkgBrowser could potentially also support both. I generally like the idea of giving users the the option to choose if there's two (or more) dependencies that can largely be used interchangeably without requiring too much additional development effort. This adds some flexibility; e.g., in this particular case, if python-pyqt5 or pyside2 wasn't compatible with a new version of Python yet or if a bug got introduced in either package, users could then possibly easily switch to the other and continue using PkgBrowser (without having to manually downgrade a package or using some other workaround).

Anyway, I also get your point and I can see how you wouldn't want to deal with potential bugs or issues that arose from supporting both.

Thanks for the quick reply and the great software!

kachelaqa commented on 2021-05-10 19:55 (UTC)

@mser It's not just the lack of complete API compatibility. There are numerous undocumented internal and external behavioural differences, as well as a different set of potential bugs to work around. I doubt whether any abstraction layer could feasibly deal with them all.

mser commented on 2021-05-10 19:32 (UTC)

@kachelaqa

qt5-python-bindings doesn't imply that the packages that happen to provide it are interchangeable with each other

They are indeed (for the most part) API-compatible.

But I just realized PkgBrowser would have to use python-qtpy then (which is an abstraction layer and allows you to use either) instead of using python-pyqt5 directly; which would have to be changed upstream of course, so disregard my question.

kachelaqa commented on 2021-05-10 19:00 (UTC)

@mser pkgbrowser depends on python-pyqt5. qt5-python-bindings doesn't imply that the packages that happen to provide it are interchangeable with each other.

mser commented on 2021-05-10 18:50 (UTC)

Could the python-pyqt5 dependency be changed to qt5-python-bindings instead so either python-pyqt5 or pyside2 (the official Python Qt bindings) can be used?

Or is PkgBrowser not compatible with pyside2?

Kewl commented on 2021-03-24 21:35 (UTC) (edited on 2021-03-24 21:40 (UTC) by Kewl)

what is the use of python<3.10, is it expected to break with 3.10 ? Same about the pacman condition.

btw, soon the 10th anniversary of the tool!

Kr1ss commented on 2020-12-05 16:37 (UTC) (edited on 2020-12-05 16:43 (UTC) by Kr1ss)

@masterberg fakeroot is member of base-devel, hence it shouldn't be explicitely declared as makedepend. Same applies to make.

See the according paragraph in the PKGBUILD wiki.

masterberg commented on 2020-12-05 16:34 (UTC) (edited on 2020-12-05 16:36 (UTC) by masterberg)

Missing fakeroot and make package as build dependency

blackhole commented on 2020-12-03 06:27 (UTC)

Removed 'python<3.9' and rebuild package

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