yaourt: pacman frontend

wain · 2006-10-05 11:44:06

Homepage: http://archlinux.fr/yaourt-en/

yaourt is a pacman frontend whith a lot of features like:

- AUR support (search, easy install, vote etc..)
- interactiv search + install (with AUR Unsupported results integrated)
- building packages directly from ABS cvs sources
- search output colorised (skinable) + always show the repository where a package came from
- handling config files .pacnew/.pacsave
- managing alpm database backup (save, restore, query database directly on backup file)
- alert user when new orphans are detected and check the database integrity with testdb after each operation
- downloading PKGBUILD directly from ABS cvs or AUR Unsupported
- statistics on installed packages
Yaourt can be run as a non-privileged user (safest for AUR unsupported packages).
Root password will be required only when it is necessary.

USAGE: yaourt [OPTION...] <parameter>
example:
$ yaourt [regexp] : search for matching strings (with *) and allows to install it
$ yaourt -S [packagename]: download package from repository, and fallback on AUR
$ yaourt -S [list file] : download all packages stored in the first column of the given file
$ yaourt -Ss [regexp] : search remote repositories and AUR for matching strings
$ yaourt -Syu --aur : upgrade system + packages from aur
$ yaourt -Sybu --aur : upgrade by building PKGBUILD + packages from aur
$ yaourt -Syu --devel : upgrade all cvs/svn/mercurial packages (from aur)

OPTIONS:
yaourt's options are the same as pacman, so check the pacman man page for more info
yaourt adds/enhances options marked with '*'

General:
(-h, --help) give this help list
(-V, --version) give program version
--noconfirm do not ask for any confirmation
--tmp /where/you/want use given directory for temporary files
--lightbg change colors for terminal with light background
--nocolor don't use any color
--textonly good for scripting yaourt's output
--stats display various statistics of installed pacakges

Install:
(-S, --sync) <package> * download package from repository, and fallback on aur
(-S, --sync) <file> * download all packages listed on the first column of the file
(-S, --sync) -b * builds the targets from source
(-S, --sync) -c, --clean remove old packages from cache directory (use -cc for all)
(-S, --sync) -d, --nodeps skip dependency checks
(-S, --sync) -f, --force force install, overwrite conflicting files
(-S, --sync) -g, --groups view all members of a package group
(-S, --sync) -i, --info * view package (or PKGBUILD from AUR) information
(-S, --sync) -l, --list * list all packages belonging to the specified repository
(-S, --sync) -p, --print-uris print out download URIs for each package to be installed
(-S, --sync) --export <destdir> * export packages for local repository
(-S, --sync) --ignore <pkg> skip some package
(-U, --upgrade) <file.pkg.tar.gz> upgrade a package from <file.pkg.tar.gz>
(<no option>) <file.pkg.tar.gz> * upgrade a package from <file.pkg.tar.gz>
(-G, --getpkgbuild) <pkg> * Retrieve PKGBUILD and local sources for package name
--asdeps Install packages non-explicitly to be installed as a dependency

Upgrade:
-Su, --sysupgrade upgrade all packages that are out of date
-Su --aur * upgrade all aur packages
-Su --devel * upgrade all cvs/svn/mercurial/git/bazar packages
-Sud, --nodeps skip dependency checks
-Suf, --force force install, overwrite conflicting files
-Su --ignore <pkg> skip some package
-Sy, --refresh download fresh package databases from the server
Note: yaourt always shows new orphans after package update

Downgrade:
-Su --downgrade * reinstall all packages which are marked as "newer than extra or core" in -Su output
(this is specially for users who experience problems with [testing] and want to revert back to current)

Local search:
(-Q, --query) -e, * list all packages explicitly installed
(-Q, --query) -d, * list all packages installed as a dependency for another package
(-Q, --query) -t * list all packages unrequired by any other package
-Qdt * list missed packages installed as dependecies but not required
-Qet * list top level packages explicitly installed
(-Q, --query) -g, --groups view all members of a package group
(-Q, --query) -i, --info view package information (use -ii for more)
(-Q, --query) -l, --list list the contents of the queried package
(-Q, --query) -o <string> * search for package that owns <file> or <command>
(-Q, --query) -p, --file will query the package file [package] instead of db
(-Q, --query) -s, --search * search locally-installed packages for matching strings
(-Q) --backupfile <file> * query a database previously saved in a tar.bz2 file (with yaourt --backup)
Example: you want to reinstall archlinux with the same packages as your backup pacman-2008-02-22_10h12.tar.bz2
just run yaourt -Qet --backupfile pacman-2008-02-22_10h12.tar.bz2 > TopLevelPackages.txt
To reinstall later, just run yaourt -S TopLevelPackages.txt

Remote search:
(-S, --sync) -s [string] * search remote repositories and AUR for matching strings
<no option> [string] * search for matching strings + allows to install (interactiv)

-Sq --depends <pkg> * list all packages which depends on <pkg>
-Sq --conflicts <pkg> * list all packages which conflicts with <pkg>
-Sq --provides <pkg> * list all packages which provides <pkg>

Clean:
(-C, --clean) * manage, show diff .pacsave/.pacnew files
(-C, --clean) -c * delete all .pacsave/.pacnew files
(-C, --clean) -d, --database * clean database (show obsolete repositories)
(-S, --sync) -c remove old packages from cache
(-S, --sync) -c -c remove all packages from cache
(-R, --remove) <package> remove packages
(-R, --remove) -c, --cascade remove packages and all packages that depend on them
(-R, --remove) -d, --nodeps skip dependency checks
(-R, --remove) -k, --dbonly only remove database entry, do not remove files
(-R, --remove) -n, --nosave remove configuration files as well
(-R, --remove) -s, --recursive remove dependencies also (that won't break packages)
Note: yaourt always shows new orphans after package removal

Backup:
(-B, --backup) [directory] * backup pacman database in given directory
(-B, --backup) <file.tar.bz2> * restore a previous backup of the pacman database

Runing yaourt as a non-privileged user requiers some entries in sudoers file:
- pacman (remove package + refresh database + install AUR's package)
- pacdiffviewer (manage pacsave/pacnew files)

Download yaourt:

AUR: http://aur.archlinux.org/packages.php?d … =1&ID=5863
or

[archlinuxfr]
Server = http://repo.archlinux.fr/i686

[archlinuxfr]
Server = http://repo.archlinux.fr/x86_64

Last edited by wain (2008-03-18 21:09:39)

tomk · 2006-10-05 12:03:55

We can purge comments from the AUR page, if you like.

wain · 2006-10-05 16:16:20

tomk wrote:

We can purge comments from the AUR page, if you like.

no thanks

cromo · 2006-10-05 23:39:35

There's a spelling mistake:
"==> Do you want to update this packages ? [Y/n]"

Regarding the issue that we discussed in yaourt's comments in AUR:
no, there is no other package built during kpowersave compilation here, although it has makedepend of unsermake, that was installed earlier from AUR using yaourt. This could be the case I think.

==> kpowersave dependencies:
 - powersave (already installed)
 - kdelibs (already installed)
 - kdebase (already installed)
 - dbus-qt3 (already installed)
[b] - unsermake (package that provides unsermake already installed)[/b]
 - pkgconfig (already installed)

EDIT: nope, I edited PKGBUILD and removed unsermake from makedepends, but it still compiles the package twice.

detto · 2006-10-06 17:44:37

Nice tool!
Ive got a feature request: List packages that are not needed by anything else (orphans) BUT including explicity installed ones.

wain · 2006-10-06 19:51:43

detto wrote:

Nice tool!
Ive got a feature request: List packages that are not needed by anything else (orphans) BUT including explicity installed ones.

Thank you. What do you mean bye "including explicity installed ones" ?

cromo wrote:

There's a spelling mistake:
"==> Do you want to update this packages ? [Y/n]"
Regarding the issue that we discussed in yaourt's comments in AUR:
no, there is no other package built during kpowersave compilation here, although it has makedepend of unsermake, that was installed earlier from AUR using yaourt. This could be the case I think.
EDIT: nope, I edited PKGBUILD and removed unsermake from makedepends, but it still compiles the package twice.

ok, I tried to reproduce this problem with several people. Without any success for the moment. Is "kpowersave" the only package with which that occurs ?
Could you send the complete log of compilation to me?

detto · 2006-10-06 20:59:09

wain wrote:

Thank you. What do you mean bye "including explicity installed ones" ?

IIRC the switch "-Qt" will search for packages that:
a) are installed as dependencies
b) are not needed by any other package anymore

What i think would be pretty neat is that it also has a swich for searching packages that:
a) are installed as dependencies AND explicity installed (e.g.: pacman -S xterm)
b) are not needed by any other package anymore

My english isnt best for explaining it that detailed. I hope you get that or someone else has a clue what i want to express :oops:

cheers,
detto

wain · 2006-10-06 21:11:11

detto wrote:

What i think would be pretty neat is that it also has a swich for searching packages that:
a) are installed as dependencies AND explicity installed (e.g.: pacman -S xterm)
b) are not needed by any other package anymore
My english isnt best for explaining it that detailed. I hope you get that or someone else has a clue what i want to express :oops:
cheers,
detto

Isn't this already what "yaourt -Qe" does ?

detto · 2006-10-06 21:40:00

wain wrote:

Isn't this already what "yaourt -Qe" does ?

:shock:
S**t !! ...must have overlooked that one. Thats the thing i meant im sure, thx for pointing me to it mate.

cheers,
detto

wain · 2006-10-22 14:40:42

cromo wrote:

There's a spelling mistake:
"==> Do you want to update this packages ? [Y/n]"
Regarding the issue that we discussed in yaourt's comments in AUR:
no, there is no other package built during kpowersave compilation here, although it has makedepend of unsermake, that was installed earlier from AUR using yaourt. This could be the case I think.
==> kpowersave dependencies:
 - powersave (already installed)
 - kdelibs (already installed)
 - kdebase (already installed)
 - dbus-qt3 (already installed)
[b] - unsermake (package that provides unsermake already installed)[/b]
 - pkgconfig (already installed)
EDIT: nope, I edited PKGBUILD and removed unsermake from makedepends, but it still compiles the package twice.

Sorry for the delay. I realize the problem occurs only when you build package form aur as root. This bug is fixed in yaourt 0.4.7

There is a known problem in yaourt -C (pacdiffviewer):
it just doesn't work with mlocate or rlocate. slocate is necessary at this time.

cromo · 2006-10-27 16:07:05

Indeed, I was always running it with sudo, I thought it's the way it's meant to be. I just realized I can run yaourt without sudo and yaourt will ask for password when there's a need. Nice!

BTW. I found another bug. When I run yaourt -Syu I get:

cromo@kromka:~$ yaourt -Syu
Yaourt 0.4.8: Archlinux package manager
:: Synchronizing package databases...
 testing                  [################] 100%       0K     0.1K/s  00:00:04
:: current is up to date
:: extra is up to date
:: unstable is up to date
:: community is up to date
:: bluez-libs: local (3.7-3) appears to be newer than repo (current/3.7-1)
:: bluez-utils: local (3.7-4) appears to be newer than repo (current/3.7-2)
:: kmobiletools: local (0.5_beta1-1) appears to be newer than repo (extra/0.4.3.3-1)
:: Above packages will be skipped.  To manually upgrade use 'pacman -S <pkg>'
error: no targets specified
usage:  pacman {-S --sync} [options] [package]
options:
  -c, --clean         remove old packages from cache directory (use -cc for all)
  -d, --nodeps        skip dependency checks
                          // cut //
  -r, --root <path>   set an alternate installation root
  -b, --dbpath <path> set an alternate database location

Thing is about what happens after the "To manually upgrade use 'pacman -S <pkg>'"part.

wain · 2006-10-28 10:12:35

cromo wrote:

Indeed, I was always running it with sudo, I thought it's the way it's meant to be. I just realized I can run yaourt without sudo and yaourt will ask for password when there's a need. Nice!

BTW. I found another bug. When I run yaourt -Syu I get:

cromo@kromka:~$ yaourt -Syu
Yaourt 0.4.8: Archlinux package manager
:: Synchronizing package databases...
 testing                  [################] 100%       0K     0.1K/s  00:00:04
:: current is up to date
:: extra is up to date
:: unstable is up to date
:: community is up to date
:: bluez-libs: local (3.7-3) appears to be newer than repo (current/3.7-1)
:: bluez-utils: local (3.7-4) appears to be newer than repo (current/3.7-2)
:: kmobiletools: local (0.5_beta1-1) appears to be newer than repo (extra/0.4.3.3-1)
:: Above packages will be skipped.  To manually upgrade use 'pacman -S <pkg>'
error: no targets specified
usage:  pacman {-S --sync} [options] [package]
options:
  -c, --clean         remove old packages from cache directory (use -cc for all)
  -d, --nodeps        skip dependency checks
                          // cut //
  -r, --root <path>   set an alternate installation root
  -b, --dbpath <path> set an alternate database location

Thing is about what happens after the "To manually upgrade use 'pacman -S <pkg>'"part.

This is a bug in srcpac:
http://bugs.archlinux.org/task/5696

cromo · 2006-11-01 01:43:10

I see. Thanks for your reply though.

veek · 2007-01-25 00:05:00

Reviving a bit of an old thread here, but I think it's worth it.

I just wanted to tell you Wain, yaourt is working brilliantly. I just upgraded
to the latest version. It's much faster! Also the automatic synchronizing
and updating of packages built from AUR is beautiful.

Keep up the awesome work!

Susu · 2007-02-15 01:01:07

Hey, I will give it a try. I like the idea of handling pacsave/pacnew files.

Susu · 2007-02-15 21:26:39

yaourt is pretty nice. One thing I'm still missing: Merging of pacsave/pacnew with the possibility of a backup

wain · 2007-02-15 23:11:08

Susu wrote:

yaourt is pretty nice. One thing I'm still missing: Merging of pacsave/pacnew with the possibility of a backup

you want to say to backup the file before editing it with diff ?

Susu · 2007-02-16 20:01:54

I want a possibility to "automagically" merge an existing (and modified) config with a pacnew, and before merging making a backup of the config, I'd modified.

wain · 2007-03-07 21:37:51

Susu wrote:

I want a possibility to "automagically" merge an existing (and modified) config with a pacnew, and before merging making a backup of the config, I'd modified.

automagically it's difficult I will see what I can do for this.

Next release will fix cromo's claws-rssyl bug and add light background support + some rewrite for pacman3/makepkg3.

hierarchicalpolymorphist · 2007-03-08 23:58:23

Great job on yaourt!

Although I do have a complaint...the name is a bit awkward to spell, and it can't be typed as quickly as 'pacman'...so I did something (see my sig) hope you guys don't mind

wain · 2007-03-09 09:11:29

hierarchicalpolymorphist wrote:

Great job on yaourt!
Although I do have a complaint...the name is a bit awkward to spell, and it can't be typed as quickly as 'pacman'...so I did something (see my sig) hope you guys don't mind

Yes I know
yaourt is the french word for yoghourt

I use this alias:

alias y='yaourt'

3nd3r · 2007-03-09 09:20:49

/me is currently using
alias pacman='sudo yaourt'

3nd3r · 2007-03-11 05:34:54

I have to say, I love this app. I could not live without it )))))

Susu · 2007-03-13 14:38:53

wain wrote:

Susu wrote:
I want a possibility to "automagically" merge an existing (and modified) config with a pacnew, and before merging making a backup of the config, I'd modified.
automagically it's difficult I will see what I can do for this.

Thank you. I like yaourt, it's a wonderful tool I don't want to miss anymore.

Zer0 · 2007-03-14 04:03:14

I cant remember the last time I used stock pacman.. I can't wait for the next release of yaourt!

Arch Linux

#1 2006-10-05 11:44:06

yaourt: pacman frontend

#2 2006-10-05 12:03:55

Re: yaourt: pacman frontend

#3 2006-10-05 16:16:20

Re: yaourt: pacman frontend

#4 2006-10-05 23:39:35

Re: yaourt: pacman frontend

#5 2006-10-06 17:44:37

Re: yaourt: pacman frontend

#6 2006-10-06 19:51:43

Re: yaourt: pacman frontend

#7 2006-10-06 20:59:09

Re: yaourt: pacman frontend

#8 2006-10-06 21:11:11

Re: yaourt: pacman frontend

#9 2006-10-06 21:40:00

Re: yaourt: pacman frontend

#10 2006-10-22 14:40:42

Re: yaourt: pacman frontend

#11 2006-10-27 16:07:05

Re: yaourt: pacman frontend

#12 2006-10-28 10:12:35

Re: yaourt: pacman frontend

#13 2006-11-01 01:43:10

Re: yaourt: pacman frontend

#14 2007-01-25 00:05:00

Re: yaourt: pacman frontend

#15 2007-02-15 01:01:07

Re: yaourt: pacman frontend

#16 2007-02-15 21:26:39

Re: yaourt: pacman frontend

#17 2007-02-15 23:11:08

Re: yaourt: pacman frontend

#18 2007-02-16 20:01:54

Re: yaourt: pacman frontend

#19 2007-03-07 21:37:51

Re: yaourt: pacman frontend

#20 2007-03-08 23:58:23

Re: yaourt: pacman frontend

#21 2007-03-09 09:11:29

Re: yaourt: pacman frontend

#22 2007-03-09 09:20:49

Re: yaourt: pacman frontend

#23 2007-03-11 05:34:54

Re: yaourt: pacman frontend

#24 2007-03-13 14:38:53

Re: yaourt: pacman frontend

#25 2007-03-14 04:03:14

Re: yaourt: pacman frontend

Board footer