Package Details: pasystray 0.6.0-3

Git Clone URL: https://aur.archlinux.org/pasystray.git (read-only)
Package Base: pasystray
Description: PulseAudio system tray (a replacement for padevchooser)
Upstream URL: https://github.com/christophgysin/pasystray
Licenses: LGPL
Groups: multimedia
Conflicts: pasystray
Submitter: christoph.gysin
Maintainer: christoph.gysin
Last Packager: christoph.gysin
Votes: 92
Popularity: 5.844042
First Submitted: 2012-10-20 09:08
Last Updated: 2016-07-26 04:44

Pinned Comments

christoph.gysin commented on 2016-07-27 19:10

PLEASE NOTE!

This package builds two packages: pasystray and pasystray-gtk2. You can't install them both, you'll need to pick which one to use. pasystray is the recommended one, which uses gtk3. pasystray-gtk2 which is built against gtk2 is provided if you don't want to install gtk3.

To build the package, run:

$ makepkg -s

To install, run either:

$ sudo pacman -U pasystray-<version>.pkg.tar.xz

or

$ sudo pacman -U pasystray-gtk2-<version>.pkg.tar.xz

Please note that "makepkg -i" will try to install both packages, and fail with a conflict. The same happens with yaourt.

Latest Comments

christoph.gysin commented on 2016-08-22 09:19

I still think that yaourt and co. are at fault for not handling split packages correctly and always wanting to install all of them. But this is not a discussion platform. Please take this to the aur-general mailing list and find concencus with the arch developers about the packaging guidelines. Should they decide that I am at fault, the documentation should be updated accordingly, and I will happily change how pasystray is packaged.

No further begging here will change anything, so don't waste your time.

lukasm commented on 2016-08-22 05:58

Please split the packages again! Although we can create packages like this, it is not the intended usage, as conventions for package managers diverge from this behavior.

As a temporal fix for all that want to install pasystray with yaourt: When it asks to modify PKGBUILD, apply the following changes:
1) remove pasystray-gtk2 from pkgname
2) remove <cp -r $srcdir/$_pkgname{,-gtk2}-$pkgver> from the build function
3) modify <for gtk in "" 2; do> to "for gtk in ""; do>

Then install the usual way. Afterwards it won't comply anymore that pasystray is not up to date.

3onyc commented on 2016-08-21 19:34

What was the reasoning behind having this build 2 conflicting packages? most people use yaourt to install things from the AUR and that just breaks their installs.

Could you reconsider and properly split both packages again? Thanks!

epicepee commented on 2016-08-16 20:28

aura is throwing errors as well, and it gives no clear way to install just one package. Please take the conventional path here, if you can; your software otherwise works very nicely.

HotblackDesiato commented on 2016-08-09 04:07

Please split this into two package like other package maintainers. Many thanks!

TrevorBramble commented on 2016-07-30 05:02

@christoph.gysin: Please do the conventional, expected thing.

joehillen commented on 2016-07-27 19:54

@christoph.gysin Why do you insist on making it complicated? Just split the packages.

christoph.gysin commented on 2016-07-27 19:10

PLEASE NOTE!

This package builds two packages: pasystray and pasystray-gtk2. You can't install them both, you'll need to pick which one to use. pasystray is the recommended one, which uses gtk3. pasystray-gtk2 which is built against gtk2 is provided if you don't want to install gtk3.

To build the package, run:

$ makepkg -s

To install, run either:

$ sudo pacman -U pasystray-<version>.pkg.tar.xz

or

$ sudo pacman -U pasystray-gtk2-<version>.pkg.tar.xz

Please note that "makepkg -i" will try to install both packages, and fail with a conflict. The same happens with yaourt.

javallone commented on 2016-07-27 17:26

I don't think the problem here is yaourt's. The Arch wiki recommends using the -i argument to makepkg for installing AUR packages, which also doesn't work for this package. So either Arch's own tools AND yaourt have bugs, or you're misusing the split package feature.

It seems like split packages are generally used for either splitting a single package into several optional components (binaries and documentation for example) or for building two different versions that can co-exist (a python-3 and python-2.7 build for example). I'm with @joehillen: Merging two packages that conflict with each other just seems to be a problem.

christoph.gysin commented on 2016-07-27 17:14

@joehillen How about no? If there is a bug in yaourt, please report it and fix it in yaourt.

All comments