thiagokokada/burgaur

A delicious AUR helper. Made from cower.

burgaur

A delicious AUR helper. Made from cower.

Author:	[email protected]
Date:	2018-10-20
Copyright:	Thiago Kenji Okada
Version:	2.3
Manual section:	1
Manual group:	system

SYSNOPSIS

burgaur [OPTIONS]... [COMMANDS]...

DESCRIPTION

Burgaur is an AUR helper based on and strictly a superset of cower. It automates boring tasks that in cower you need to do by hand, like updating all your AUR system packages, or installing a new package from AUR including its dependencies.

It doesn't try to be everything (i.e. yaourt). Instead, it simply assumes that there is already a better tool to do some job and only tries to complement other tools.

It also has a better behavior with multiple packages than most AUR helpers, based on the behavior of pacaur. Basically, instead of the traditional "review one package, build one package, install one package, rinse and repeat", burgaur does the following:

• Review everything
• Lean back
• Build everything
• Install everything

This can speed up things considerably when you're building large packages or a great number of them.

OPTIONS

optional arguments

-h, --help	show this help message and exit
--cower-raw-options OPTIONS
	pass arguments directly to cower, no sanity check, may break things
--noconfirm	skip confirmation prompts during install process, passed to pacman/makepkg too, may be unsafe
--nodelete	do not remove temporary build directory after install
--noinstall	do not install packages after build, assume '--nodelete'
--nobuild	do not build packages, assume '--nodelete' and '--noinstall'
-c, --color WHEN
	use colored output. WHEN is 'never', 'always' or 'auto' (default)
--version	show program's version number and exit

update

-fu, --force-update TARGET
	update TARGET unconditionally
-su, --system-update
	update all AUR packages

install

-mi, --make-install PACKAGE
	make and install package from AUR, including dependencies
-si, --search-install TARGET
	list all packages with target name and let user choose which ones to install

CONFIGURATION

All configuration is done by setting environmental variables.

• BURGAUR_TARGET_DIR: set temporary directory for building packages (default: /var/tmp).
• BURGAUR_FILE_MANAGER: set desired file manager to verify packages before building it (default: mc).

EXAMPLES

Update all AUR packages

$ burgaur -su

Force-update all packages that contain '-git'

$ burgaur -fu=-git  # The equals (=) is necessary because of the dash (-)

Force-update a package

$ burgaur -fu burgaur-git

Install a package

$ burgaur -mi package

For problematic packages, you can temporarily change the package build directory (by default, on /var/tmp) and keep the resulting files for later use using:

$ BURGAUR_TARGET_DIR=mydir burgaur -mi package --nodelete

Or if you just want to build a package but not install it:

$ BURGAUR_TARGET_DIR=mydir burgaur -mi package --noinstall

Search (and install) with cower

$ burgaur -si "partial description"

SEE ALSO

• cower <https://github.com/falconindy/cower>
• makepkg <https://wiki.archlinux.org/index.php/Makepkg>

BUGS

Please report bugs to GitHub <https://github.com/m45t3r/burgaur/issues>.

burgaur's Issues

Add support for other file managers e.g. vifm

I suggest doing this by adding environmental variable BURGAUR_FILE_MANAGER.

Change how/where packages are downloaded

Rather than making a tmpdir in /var/tmp (should only be used for persistent storage), downloading to there, and then removing the directory, it should:

1. Ensure /tmp/burgaur exists
2. Download everything to /tmp/burgaur (no need for sanity checks, cower already does that)
3. Keep it there
   This eliminates the need for --nodelete and BURGAUR_TARGET_DIR (BUILDDIR can be set if one doesn't want to build in a tmpfs).

cower obsolete replaced by auracle

Hi

Cower is now obsolete and is being replaced with auracle

see here
https://lists.archlinux.org/pipermail/aur-dev/2018-January/004416.html

https://www.reddit.com/r/archlinux/comments/6ktsqg/auracle_the_next_generation_of_cower/

Would you like me to do a pull request or you can do it yourself or leave it alone.

Regards

Mimick pacaur behavior with multiple packages

Actually, I don't know if this is true (I never used pacaur), but someone said something in Google+ and left me curious. Yaourt (and burgaur) has the following behavior when installing multiple packages (or packages with multiple dependencies):

• Review some package
• Build somepackage
• Install some package
• Figure out something else from AUR needs to be built
• Review the new package and interrupt installation process.
  and so on

The above behavior is easier to think when doing code, and works, but may be annoying if you're building a great number of packages, since you need to constantly check if a package is already installed before going to the next one. This is the pacaur workflow (according to the comment from Tim JP in Google+):

• Review everything
• Lean back.
• Build everything
• Install everything.

I want to implement something like this (removing the old behavior, of course). Commit d6720e2 should already do the majority of the work. Now it's just some work to identify which functions call make_install, change them to use a list instead of passing each package one-by-one, pass everything to make_install and profit.