Package Details: trizen 1:1.55-1

Git Clone URL: (read-only)
Package Base: trizen
Description: Trizen AUR Package Manager: A lightweight wrapper for AUR.
Upstream URL:
Keywords: aur manager package
Licenses: GPL3
Submitter: trizen
Maintainer: trizen
Last Packager: trizen
Votes: 237
Popularity: 16.111116
First Submitted: 2010-07-07 10:21
Last Updated: 2018-10-13 17:24

Dependencies (12)

Required by (7)

Sources (1)

Latest Comments

1 2 3 4 5 6 ... Next › Last »

zebulon commented on 2018-10-16 07:54

@trizen: thanks for doing this change, and thanks to damentz for the follow-up. The way this is not dealt with is much clearer. The sticky point was asking about "other packages" whereas it was not clear from the start what would be installed in the first place, by answering No. As it is now, trizen installs all of the split packages, and this is the logical default behaviour.

damentz commented on 2018-10-15 21:18

@trizen Thanks!

trizen commented on 2018-10-13 17:04

Thanks @damentz. In version 1.54, a simpler approach has been taken, by removing the question "Do you want to install other packages from this group?" and asking directly to select which packages to install, where the packages that are already installed, along with the main package specified during -S, are selected by default.

damentz commented on 2018-10-11 16:00

@trizen I think maybe what we need is a way to whitelist AUR packages so that trizen installs all split packages by default on packages the user decides they want going forward.

A good example are all the linux-* derivatives in the AUR. They all usually produce the binary (linux-*), docs (linux-*-docs), and headers (linux-*-headers). Most users just want to install all of these, and especially if the package is updated frequently, not have to have to explicitly answer 'Y' to installing the split packages every time.

Then there's packages like nvidia-vulkan that produce packages that mutually conflict (a binary kernel module package + a kernel module dkms package), and the user needs to select the right one for their needs.

I could see two ways of setting this - 1) through the trizen.conf file, and 2) have trizen remember the choices the user makes if the installation is successful.

This is all a lot of work however, so I understand if you would reject this idea due to its complexity. But great work on trizen! It's become my favorite pacman / aur wrapper since I jumped ship from yaourt. Thanks for all the hard work on it!

trizen commented on 2018-10-11 11:42

@zebulon Hi, thanks! I'm not quite sure if I understand your objection. The linux-ck group contains 2 packages. If you answer "N" (or just press ENTER) to the first question, it will install only "linux-ck". By answering "Y" you can chose which packages to install.

It's also possible to disable support for split packages by setting "split_packages => 0," in the configuration file. In this way, trizen will not ask about the other packages from a group and will install only the main packages specified during -S.

zebulon commented on 2018-10-11 06:42

Hi, great helper. I have a suggestion to improve group packages. When I install linux-ck, it compiles both linux-ck and linux-ck-headers. At the end of compilation, trizen displays this:

:: This group contains 2 packages:



=>> Do you want to install other packages from this group? [y/N]: y

=>> Select which packages to install 1> linux-ck 2> linux-ck-headers

Install [1 2]:

The weird part is to be asked " Do you want to install other packages from this group? [y/N]:" in the first place, and that pressing enter will respond N by default. Should not this step be skipped when the package is the only possible choice?

lpc123 commented on 2018-07-01 02:39

Thanks. Commenting out the line PKGDEST=/home/lpc123/packages in makepkg.conf solved the problem.

trizen commented on 2018-06-20 02:00

The value of makepkg_command should be "/usr/bin/makepkg -scf" only.

Additionally, try to comment out the line PKGDEST=/home/lpc123/packages in makepkg.conf to see if it changes anything.

lpc123 commented on 2018-06-19 00:16

I read the thread:

In trizen.conf, I have:

clone_dir => "/tmp/trizen-lpc123",

makepkg_command => "PKGDEST= /usr/bin/makepkg -scf"

movepkg => 0,

movepkg_dir => "/var/cache/pacman/pkg",

In makepkg.conf, I have:


I do not understand what is wrong, but when I try to do the upgrade, trizen says this before attempting to upgrade:

HEAD is now at d41b80f Version 1.50

Already up to date.

trizen commented on 2018-06-18 15:25

@lpc123 I suspect it's something related to pacman 5.1 and some settings in /etc/makepkg.conf, especially the PKGDEST option (see:

If this is the case, you can update to version 1.50 manually, which includes a fix for this particular issue:

git clone
cd trizen
makepkg -si