https://wiki.archlinux.org/api.php?action=feedcontributions&user=Penguin&feedformat=atomArchWiki - User contributions [en]2024-03-29T13:46:05ZUser contributionsMediaWiki 1.41.0https://wiki.archlinux.org/index.php?title=Aurbuild&diff=21826Aurbuild2007-03-10T00:31:35Z<p>Penguin: Updated to current man page</p>
<hr />
<div>[[Category:Package management (English)]]<br />
[[Category:Utilities (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
''Contributed by Tyler Gates <TGates81 at gmail dot com>''<br />
<br />
Thread:<br />
http://bbs.archlinux.org/viewtopic.php?t=14872<br />
<br />
Source:<br />
http://developer.berlios.de/project/showfiles.php?group_id=7176<br />
<br />
Aur:<br />
http://aur.archlinux.org/packages.php?K=aurbuild<br />
<br />
<br />
<br />
NAME<br />
aurbuild - A utility to build and install packages from the AUR.<br />
<br />
<br />
SYNOPSIS<br />
aurbuild [options] [package] <package><br />
<br />
<br />
DESCRIPTION<br />
aurbuild is a utility to build and install packages from the AUR. It will retrieve the tarball containing necessary build<br />
files, invoke makepkg through under privileged user to build the package and pacman to install it. A menu is available to<br />
view or edit the build files if needed.<br />
<br />
OPTIONS<br />
A dependency installation method must be passed to aurbuild before it attempts to build a package.<br />
<br />
<br />
-b, --builddeps<br />
Build missing dependencies from source using the abs tree. makedepends and depends will be evaluated and satisfied<br />
in that order. It is wise to run abs refresh your abs tree before building.<br />
<br />
<br />
-s, --syncdeps<br />
Sync missing dependencies using pacman to retrieve prebuilt *.pkg.tar.gz binaries. makedepends and depends will be<br />
evaluated and satisfied in that order.<br />
<br />
<br />
-o "OPTS", --builder-opts="OPTS"<br />
This will pass options directly to the builder of choice (currently makepkg or versionpkg) as selected from the menu<br />
during the build process. Be sure to encapsulate your options in double quotes to ensure they are passed down cor-<br />
rectly to the builder. Please note aurbuild will always pass -f to makepkg by default and some options will not work<br />
as an under-privileged build user. Also note the use of this switch is optional and normally not needed to build<br />
most packages. Below is an example:<br />
<br />
<br />
Example:<br />
makepkg -Bn --> aurbuild -so "-B -n --foo" -OR- aurbuild --syncdeps --builder-opts="-B -n --foo"<br />
<br />
<br />
-a, --auto-build<br />
This will bypass the menu and build and install the package if the PKGBUILD is detected being flagged safe by a<br />
Trusted User from AUR. If this option is used and the PKGBUILD is not detected safe, the menu will be displayed. Use<br />
this as a modifier to --builddeps or --syncdeps, it cannot be used alone.<br />
<br />
<br />
Example:<br />
aurbuild -sa foo<br />
<br />
<br />
-e, --save<br />
Save the build files extracted from the tarball in AUR to the directory /var/tmp/aurbuild/pkgbuilds/<PKGNAME>.<br />
<br />
<br />
-l, --local<br />
Look in /var/tmp/aurbuild/pkgbuilds/, aurbuild's --save location, for the build files instead of AUR.<br />
<br />
<br />
-f, --official<br />
Build official packages using /var/abs/ as the PKGBUILD root. NOTE: packages will only be as up to date as your abs<br />
tree is! To update it run the command abs. This is switch is also used when aurbuild finds community packages. See<br />
the section COMMUNITY PACKAGES for more details.<br />
<br />
<br />
<br />
-u, --upgrade<br />
Upgrade out-of-date packages installed from unsupported AUR. This will check aur's website for each aur package so<br />
it may take a while. Each package will be evaluated and upgraded one by one displaying a confirmation message. Use<br />
this as a modifier to --syncdeps or --builddeps. Additionally, --auto-build may be used to bypass the menu if<br />
detected safe.<br />
<br />
Example:<br />
aurbuild -sua<br />
<br />
<br />
-c, --clean<br />
Clean the build directory /var/tmp/aurbuild/build. This may be necessary if several failed builds have not been<br />
properly dealt with. See FAILED BUILDS for more details.<br />
<br />
<br />
-n, --noconfirm<br />
Bypass any confirmation message by answering yes.<br />
<br />
<br />
-x, --noinstall<br />
Add this switch to not install the package after it has been built. Be sure you have set your PKGDEST variable in<br />
/etc/makepkg.conf if you wish to keep the built package without being deleted.<br />
<br />
<br />
-r, --revision<br />
Check CVS/SVN/MERCURIAL servers for the latest revisions on qualified PKGBUILD's via versionpkg during an --upgrade<br />
session. Note this updates the PKGBUILD so choosing versionpkg over makepkg is not necessary.<br />
<br />
<br />
-m, --rm-make-deps<br />
Remove unneeded make dependencies after a successful build. You will be prompted before proceeding.<br />
<br />
<br />
-S, --search<br />
Use this to search AUR for a single [keyword]. Results are piped to the less viewer.<br />
<br />
-V, --vote<br />
Cast a vote for each [package]. You will be prompted for your AUR account information to login. A cookie will be<br />
created and located in ~/.aurbuild/aurcookie.lwp.<br />
<br />
<br />
-S, --unvote<br />
Unvote for each [package].<br />
<br />
<br />
-h, --help<br />
Display the help message and exit.<br />
<br />
<br />
-v, --version<br />
Display version number and exit.<br />
<br />
<br />
PACKAGE<br />
This will be the name of the package as defined in AUR minus any version numbers or compression extensions. More than one<br />
package may be installed at a time by separating each with a space. This is especially useful when aur packages depend on<br />
other aur packages. Say foo3 requires foo2 and foo2 requires foo1. The line given to aurbuild would be as follows:<br />
<br />
<br />
Example:<br />
aurbuild -s foo1 foo2 foo3<br />
<br />
<br />
THE MENU<br />
The menu will be displayed as text on your terminal indicating its safe status as per Trusted User. It will display a cor-<br />
responding number to each build file extracted from the tarball to view or edit if desired. If a .install file is found and<br />
the package is not marked safe, you will be forced to view it in your editor. Once you are finished, you may choose to<br />
either build and/or install the package via makepkg and pacman, build and/or install through versionpkg (makepkg wrapper to<br />
handle SVN/CVS/Mercurial packages) and pacman, skip the package, or quit all together without building. Aurbuild will exam-<br />
ine the variables in the PKGBUILD and try guess which builder to use. For instance, if CVS/SVN/MERCURIAL variables are<br />
found, a star will be placed next to versionpkg in the menu with [V] at the choice selection indicating versionpkg is pre-<br />
ferred and preselected.<br />
<br />
<br />
WARNING: Editing build files should only be done by users who know what they are doing!<br />
<br />
<br />
YOUR EDITOR<br />
aurbuild utilizes the EDITOR environment variable as the editor to be use in the menu. If you do not have one specified, it<br />
will default to nano. You can create an EDITOR variable in ~.bashrc as shown below. It may be necessary to logout and login<br />
again.<br />
<br />
<br />
Example:<br />
#<br />
# ~.bashrc<br />
#<br />
export EDITOR="vim"<br />
<br />
<br />
UNDER PRIVILEGED BUILDING<br />
The logic behind building packages as an under privilege user is safety. If for example during the build process a file<br />
wants to be moved into the root file system i.e. from a poor PKGBUILD, makepkg will catch the permission error and exit. As<br />
you may or may not know, makepkg needs to install all of it's files into $startdir/pkg/ so that it may be compressed and<br />
given to pacman to install and keep track of. Had it been run as root user and a file was moved into the root file system<br />
during build, the package would still have been built and pacman would not be able to track that one file. The problem with<br />
building a package as regular user however, is that permissions of the files may inherit those of the user. This is where<br />
fakeroot comes into play. fakeroot allows a package to be built resembling the root user so that files may be owned by<br />
root, yet regular root permissions are denied. fakeroot is a required dependency. Aurbuild solves this by temporarily drop-<br />
ping down to a designated and under privileged build user and returning to root once the build has been complete.<br />
<br />
<br />
FAILED BUILDS<br />
Should a package fail to build, aurbuild will retain the build directory in /var/tmp/aurbuild/build/<pkgname>.<pid> by<br />
default. In some cases the package can be fixed and makepkg can be run manually with success. When a package builds success<br />
fully under aurbuild it's build files are deleted automatically.<br />
<br />
<br />
PACKAGE LOCATION<br />
aurbuild closely adheres to makepkg configurations and behavior. So if you wish to keep the package you built, uncomment<br />
and set the export PKGDEST= variable in /etc/makepkg.conf to the location you wish to store the packages. A generally<br />
accepted location is /home/pkgs although it is purely a matter of preference. Appropriate write and execute permissions to<br />
this directory will be necessary to the aurbuild user or group. If this variable is not set, aurbuild will delete the pack-<br />
age along with its temporary work directory in which it was built in /var/tmp/aurbuild/build/<pkgname>.<pid>.<br />
<br />
<br />
PACKAGE INSTALLATION<br />
If a package is built successfully, it is installed via pacman -U. If you do not wish for this behavior, set the --no-<br />
install switch. Note if you do not have PKGDEST set in /etc/makepkg.conf, the package and it's build directory will be<br />
deleted.<br />
<br />
<br />
SOURCE FILES<br />
If possible, aurbuild will attempt to copy any source files used for the build into pacman's src directory in<br />
/var/cache/pacman/src. This will prevent unnecessary multiple download sessions if the package needs to be built again in<br />
the future.<br />
<br />
<br />
COMMUNITY PACKAGES<br />
Because the AUR has the same database for unsupported packages as well as community, aurbuild is often able to detect<br />
either one. If a community package is found, aurbuild will prompt and propose to build the package via aurbuild <CURRENT<br />
DEP RESOLVE OPT> --official <PKGNAME>. This will force aurbuild to look in /var/abs/ for the desired PKGBUILD instead of<br />
AUR's website. NOTE: packages built using --official will only be as up to date as your abs tree is! Run the command abs to<br />
update it.<br />
Should a package fail to build, aurbuild will retain the build directory in /var/tmp/aurbuild/build/<pkgname>.<pid> by<br />
default. In some cases the package can be fixed and makepkg can be run manually with success. When a package builds success<br />
fully under aurbuild it's build files are deleted automatically.<br />
<br />
<br />
PACKAGE LOCATION<br />
aurbuild closely adheres to makepkg configurations and behavior. So if you wish to keep the package you built, uncomment<br />
and set the export PKGDEST= variable in /etc/makepkg.conf to the location you wish to store the packages. A generally<br />
accepted location is /home/pkgs although it is purely a matter of preference. Appropriate write and execute permissions to<br />
this directory will be necessary to the aurbuild user or group. If this variable is not set, aurbuild will delete the pack-<br />
age along with its temporary work directory in which it was built in /var/tmp/aurbuild/build/<pkgname>.<pid>.<br />
<br />
<br />
PACKAGE INSTALLATION<br />
If a package is built successfully, it is installed via pacman -U. If you do not wish for this behavior, set the --no-<br />
install switch. Note if you do not have PKGDEST set in /etc/makepkg.conf, the package and it's build directory will be<br />
deleted.<br />
<br />
<br />
SOURCE FILES<br />
If possible, aurbuild will attempt to copy any source files used for the build into pacman's src directory in<br />
/var/cache/pacman/src. This will prevent unnecessary multiple download sessions if the package needs to be built again in<br />
the future.<br />
<br />
<br />
COMMUNITY PACKAGES<br />
Because the AUR has the same database for unsupported packages as well as community, aurbuild is often able to detect<br />
either one. If a community package is found, aurbuild will prompt and propose to build the package via aurbuild <CURRENT<br />
DEP RESOLVE OPT> --official <PKGNAME>. This will force aurbuild to look in /var/abs/ for the desired PKGBUILD instead of<br />
AUR's website. NOTE: packages built using --official will only be as up to date as your abs tree is! Run the command abs to<br />
update it.<br />
<br />
<br />
COLOR OUTPUT<br />
The use of color is determined by the USE_COLOR= variable in /etc/makepkg.conf. If you wish to turn it off, set it to 'n'.<br />
<br />
<br />
SEE ALSO<br />
pacman is the ArchLinux package manager.<br />
<br />
makepkg is the package-building tool that comes with pacman.<br />
<br />
<br />
AUTHORS<br />
Tyler Gates <TGates81@gmail.com><br />
<br />
qpkg can be found here:<br><br />
-> http://aur.archlinux.org/packages.php?K=qpkg<br><br />
<br><br />
Or in the personal repository of dma147:<br><br />
[dma147]<br><br />
Server = http://arch.linux-stats.org/pkgs<br><br />
<br></div>Penguinhttps://wiki.archlinux.org/index.php?title=Aurbuild&diff=15135Aurbuild2006-09-03T22:28:08Z<p>Penguin: /* aurbuild */</p>
<hr />
<div>[[Category:Scripts]]<br />
[[Category:AUR]]<br />
<br />
== aurbuild ==<br />
''Contributed by Tyler Gates <TGates81 at gmail dot com>''<br />
<br />
Thread:<br />
http://bbs.archlinux.org/viewtopic.php?t=14872<br />
<br />
Source:<br />
http://developer.berlios.de/project/showfiles.php?group_id=7176<br />
<br />
Aur:<br />
http://aur.archlinux.org/packages.php?K=aurbuild<br />
<br />
<br />
Aurbuild is a continuation of project originally created by Dusty<br />
Phillips (Dusty). It is a utility to build and install packages from the AUR.<br />
<br />
<br />
'''OVERVIEW'''<br />
<br />
Prior to build, both dependencies (makedepends() and depends() array) will be checked and automatically either: a)built and installed from source using makepkg and abs using -b or --builddeps switch or b)installed directly through pacman as needed using -s or --syncdeps switch.<br />
Example using -b:<br />
aurbuild -b packagename<br />
Packages may also be strung together. This is usefull when building a package that relies on another that also resides in AUR. Ie. fxdesktop relies on fox. The syntax would go as follows:<br />
aurbuild -s fox fxdesktop<br />
Through an interactive and dynamic [http://infiditus.homelinux.org/arch/projects/aurbuild/screenies/menusafe-1.png menu], files packed in the tarball can be viewed or edited as needed using your global EDITOR variable on your machine. ''CAUTION: EDIT THESE FILES AT YOUR OWN RISK! IMPROPER EDITING MAY RESULT IN A BROKEN SYSTEM! '' If you do not have a global editor defined (echo $EDITOR gives you nothing), you may set one up in your ~.bashrc file as follows otherwise aurbuild will default to nano:<br />
export EDITOR="your_editor"<br />
You can logout and login for the change to take effect, or just run `source ~/.bashrc`.<br />
<br />
<br />
A ''SAFE:'' status will be given at the top of the menu to indicate that a Trusted User has flagged the files safe. It is recommended to NOT edit these files if flagged safe unless you need the package taylored to your needs. <br />
<br />
The menu may be bypassed if the package is flagged safe by appending -a or --auto-build as a modifier to the dependency installation method. Ie: <br />
aurbuild -sa package<br />
If not detected safe, the menu will be given. The --auto-build switch is recommended for beginner users and those not familiar with PKGBUILD's.<br />
<br />
<br />
Once you are ready to build, aurbuild will check the dependencies and invoke makepkg to build the package and use sudo pacman to install it transparently.<br />
<br />
<br />
Operations can be (and highly recommended) run as regular user through<br />
the use of fakeroot and a properly set-up sudo account. This is desirable because fakeroot allows the package to be built with root rights and permissions yet disallows overwriting anything to the root filesystem during the build proccess. This may occur in the event of an improper PKGBUILD.<br />
Additionally, aurbuild will source the PKGBUILD for its own purposes and gracefully exit on improper (and therefore potentialy destructive) bash syntax.<br />
The role of sudo is to install the package and it's missing dependencies via pacman.<br />
<br />
<br />
A built-in search function using -S switch will search AUR for a single [keyword] and will be viewed using less.:<br />
aurbuild -S keyword<br />
[http://infiditus.homelinux.org/arch/projects/aurbuild/screenies/search-0.png screenshot]<br />
<br />
<br />
'''INSTALLATION'''<br />
<br />
To get aurbuild, download and install the latest package from the [http://infiditus.homelinux.org/arch/projects/aurbuild/ source link] at the top of the page. The /pkg directory contains the prebuilt package while /src contains the source and PKGBUILD. Once downloaded, install the package:<br />
pacman -U /path/to/package.pkg.tar.gz<br />
<br />
As mentioned earlier, aurbuild requires a properly set-up sudo account. This should be detected by pacman as a dependency once aurbuld is installed. To set sudo, you'll need to edit the sudoers file. This should be done through the visudo program only. Simply switch to root user and enter:<br />
visudo<br />
There you'll find the lines<br />
# Uncomment to allow people in group wheel to run all commands<br />
# %wheel ALL=(ALL) ALL<br />
<br />
# Same thing without a password<br />
#%wheel ALL=(ALL) NOPASSWD: ALL<br />
<br />
Simply uncomment one or the other and check that your user is added to the wheel group:<br />
groups username<br />
To add them to the group do:<br />
gpasswd -a username wheel<br />
<br />
<br />
'''WHERE DO PACKAGES GO?'''<br />
<br />
Aurbuild behaves identical to makepkg. That is packages are built in the current working directory unless specified otherwise in /etc/makepkg.conf. The "current working directory" will be a temporary hidden folder in $HOME where the package and other work files are placed. This hidden directory will be deleted along with your built package once aurbuild is finished. If you wish to keep the package, uncomment and set the "export PKGDEST=" variable in /etc/makepkg.conf to a desired destination directory. This allows makepkg (and aurbuild as it calls on makepkg) to store all built packages in a centralized location. Note this directory should have user write permissions as aurbuild will (hopefully) be run as user most of the time.<br />
<br />
<br />
'''KEEPING PACKAGES UP-TO-DATE'''<br />
<br />
Through the use of the --upgrade or -u switch, aurbuild will read your local database maintained by pacman, determine which packages are from unsupported AUR and check AUR for any updates one-by-one. This option must be accompanied by a dependency install method, either --builddeps, -b or --syncdeps, -s.<br />
aurbuild -su<br />
<br />
<br />
'''SAVING BUILD FILES'''<br />
<br />
Build files extracted from the tarball in AUR may be saved to your machine as ~.aursave using --save or -e switch. It may be used as an additional switch when building a package from AUR:<br />
aurbuild -be foo<br />
or by itself to only download the build files and exit:<br />
aurbuild -e foo<br />
<br />
Additionally, a --local or -l switch is provided to look in ~/.aursave for the specified package instead of aur. Note that the contents of this directory may be reorganized into other parent and child directories at your discretion as long as the original directory name is preserved and not more than one of them using the same name exists.<br />
<br />
<br />
'''ADDITIONAL INFORMATION'''<br />
<br />
A manpage is included with this program which will cover all these points and more.<br />
man aurbuild<br />
<br />
<br />
'''DISCLAIMER:''' AUR packages in unsupported CANNOT BE TRUSTED indiscriminately. Use at your own risk!<br />
<br />
== qpkg - Another script which can do the same ==<br />
qpkg is a python script, written and contributed by Alexander 'dma147' Mieland, with which you can search for packages in '''all''' known repositories (official, TUR, PUR, etc...). You also can install packages directly from AUR (like aurbuild), but there is more... with qpkg you also can configure your pacman configuration to use user repositories (adding, removing and list repositories to pacman configuration).<br />
<br />
qpkg can be found here:<br><br />
-> http://aur.archlinux.org/packages.php?K=qpkg<br><br />
<br><br />
Or in the personal repository of dma147:<br><br />
[dma147]<br><br />
Server = http://arch.linux-stats.org/pkgs<br><br />
<br></div>Penguinhttps://wiki.archlinux.org/index.php?title=Aurbuild&diff=11274Aurbuild2006-04-12T00:32:50Z<p>Penguin: </p>
<hr />
<div>[[Category:Scripts]]<br />
[[Category:AUR]]<br />
<br />
== aurbuild ==<br />
''Contributed by Tyler Gates <TGates81 at gmail dot com>''<br />
<br />
Thread:<br />
http://bbs.archlinux.org/viewtopic.php?t=14872<br />
<br />
Source:<br />
http://infiditus.homelinux.org/arch/projects/aurbuild/<br />
<br />
Aur:<br />
http://aur.archlinux.org/packages.php?K=aurbuild<br />
<br />
<br />
Aurbuild is a continuation of project originally created by Dusty<br />
Phillips (Dusty). It is a utility to build and install packages from the AUR.<br />
<br />
<br />
'''OVERVIEW'''<br />
<br />
Prior to build, both dependencies (makedepends() and depends() array) will be checked and automatically either: a)built and installed from source using makepkg and abs using -b or --builddeps switch or b)installed directly through pacman as needed using -s or --syncdeps switch.<br />
Example using -b:<br />
aurbuild -b packagename<br />
Packages may also be strung together. This is usefull when building a package that relies on another that also resides in AUR. Ie. fxdesktop relies on fox. The syntax would go as follows:<br />
aurbuild -s fox fxdesktop<br />
Through an interactive and dynamic [http://infiditus.homelinux.org/arch/projects/aurbuild/screenies/menusafe-1.png menu], files packed in the tarball can be viewed or edited as needed using your global EDITOR variable on your machine. ''CAUTION: EDIT THESE FILES AT YOUR OWN RISK! IMPROPER EDITING MAY RESULT IN A BROKEN SYSTEM! '' If you do not have a global editor defined (echo $EDITOR gives you nothing), you may set one up in your ~.bashrc file as follows otherwise aurbuild will default to nano:<br />
export EDITOR="your_editor"<br />
You can logout and login for the change to take effect, or just run `source ~/.bashrc`.<br />
<br />
<br />
A ''SAFE:'' status will be given at the top of the menu to indicate that a Trusted User has flagged the files safe. It is recommended to NOT edit these files if flagged safe unless you need the package taylored to your needs. <br />
<br />
The menu may be bypassed if the package is flagged safe by appending -a or --auto-build as a modifier to the dependency installation method. Ie: <br />
aurbuild -sa package<br />
If not detected safe, the menu will be given. The --auto-build switch is recommended for beginner users and those not familiar with PKGBUILD's.<br />
<br />
<br />
Once you are ready to build, aurbuild will check the dependencies and invoke makepkg to build the package and use sudo pacman to install it transparently.<br />
<br />
<br />
Operations can be (and highly recommended) run as regular user through<br />
the use of fakeroot and a properly set-up sudo account. This is desirable because fakeroot allows the package to be built with root rights and permissions yet disallows overwriting anything to the root filesystem during the build proccess. This may occur in the event of an improper PKGBUILD.<br />
Additionally, aurbuild will source the PKGBUILD for its own purposes and gracefully exit on improper (and therefore potentialy destructive) bash syntax.<br />
The role of sudo is to install the package and it's missing dependencies via pacman.<br />
<br />
<br />
A built-in search function using -S switch will search AUR for a single [keyword] and will be viewed using less.:<br />
aurbuild -S keyword<br />
[http://infiditus.homelinux.org/arch/projects/aurbuild/screenies/search-0.png screenshot]<br />
<br />
<br />
'''INSTALLATION'''<br />
<br />
To get aurbuild, download and install the latest package from the [http://infiditus.homelinux.org/arch/projects/aurbuild/ source link] at the top of the page. The /pkg directory contains the prebuilt package while /src contains the source and PKGBUILD. Once downloaded, install the package:<br />
pacman -U /path/to/package.pkg.tar.gz<br />
<br />
As mentioned earlier, aurbuild requires a properly set-up sudo account. This should be detected by pacman as a dependency once aurbuld is installed. To set sudo, you'll need to edit the sudoers file. This should be done through the visudo program only. Simply switch to root user and enter:<br />
visudo<br />
There you'll find the lines<br />
# Uncomment to allow people in group wheel to run all commands<br />
# %wheel ALL=(ALL) ALL<br />
<br />
# Same thing without a password<br />
#%wheel ALL=(ALL) NOPASSWD: ALL<br />
<br />
Simply uncomment one or the other and check that your user is added to the wheel group:<br />
groups username<br />
To add them to the group do:<br />
gpasswd -a username wheel<br />
<br />
<br />
'''WHERE DO PACKAGES GO?'''<br />
<br />
Aurbuild behaves identical to makepkg. That is packages are built in the current working directory unless specified otherwise in /etc/makepkg.conf. The "current working directory" will be a temporary hidden folder in $HOME where the package and other work files are placed. This hidden directory will be deleted along with your built package once aurbuild is finished. If you wish to keep the package, uncomment and set the "export PKGDEST=" variable in /etc/makepkg.conf to a desired destination directory. This allows makepkg (and aurbuild as it calls on makepkg) to store all built packages in a centralized location. Note this directory should have user write permissions as aurbuild will (hopefully) be run as user most of the time.<br />
<br />
<br />
'''KEEPING PACKAGES UP-TO-DATE'''<br />
<br />
Through the use of the --upgrade or -u switch, aurbuild will read your local database maintained by pacman, determine which packages are from unsupported AUR and check AUR for any updates one-by-one. This option must be accompanied by a dependency install method, either --builddeps, -b or --syncdeps, -s.<br />
aurbuild -su<br />
<br />
<br />
'''SAVING BUILD FILES'''<br />
<br />
Build files extracted from the tarball in AUR may be saved to your machine as ~.aursave using --save or -e switch. It may be used as an additional switch when building a package from AUR:<br />
aurbuild -be foo<br />
or by itself to only download the build files and exit:<br />
aurbuild -e foo<br />
<br />
Additionally, a --local or -l switch is provided to look in ~/.aursave for the specified package instead of aur. Note that the contents of this directory may be reorganized into other parent and child directories at your discretion as long as the original directory name is preserved and not more than one of them using the same name exists.<br />
<br />
<br />
'''ADDITIONAL INFORMATION'''<br />
<br />
A manpage is included with this program which will cover all these points and more.<br />
man aurbuild<br />
<br />
<br />
'''DISCLAIMER:''' AUR packages in unsupported CANNOT BE TRUSTED indiscriminately. Use at your own risk!<br />
<br />
<br />
== qpkg - Another script which can do the same ==<br />
qpkg is a python script, written and contributed by Alexander 'dma147' Mieland, with which you can search for packages in '''all''' known repositories (official, TUR, PUR, etc...). You also can install packages directly from AUR (like aurbuild), but there is more... with qpkg you also can configure your pacman configuration to use user repositories (adding, removing and list repositories to pacman configuration).<br />
<br />
qpkg can be found here:<br><br />
-> http://aur.archlinux.org/packages.php?K=qpkg<br><br />
<br><br />
Or in the personal repository of dma147:<br><br />
[dma147]<br><br />
Server = http://arch.linux-stats.org/pkgs<br><br />
<br></div>Penguinhttps://wiki.archlinux.org/index.php?title=Aurbuild&diff=7322Aurbuild2005-12-20T00:33:59Z<p>Penguin: </p>
<hr />
<div>[[Category:Scripts]]<br />
[[Category:AUR]]<br />
<br />
== aurbuild ==<br />
''Contributed by Tyler Gates <TGates81 at gmail dot com>''<br />
<br />
Thread:<br />
http://bbs.archlinux.org/viewtopic.php?t=14872<br />
<br />
Source:<br />
http://infiditus.homelinux.org/arch/projects/aurbuild/<br />
<br />
Aur:<br />
http://aur.archlinux.org/packages.php?K=aurbuild<br />
<br />
<br />
Aurbuild is a continuation of project originally created by Dusty<br />
Phillips (Dusty). It is a utility to build and install packages from the AUR.<br />
<br />
<br />
'''OVERVIEW'''<br />
<br />
Prior to build, both dependencies (makedepends() and depends() array) will be checked and automatically either: a)built and installed from source using makepkg and abs using -b or --builddeps switch or b)installed directly through pacman as needed using -s or --syncdeps switch.<br />
Example using -b:<br />
aurbuild -b packagename<br />
Packages may also be strung together. This is usefull when building a package that relies on another that also resides in AUR. Ie. fxdesktop relies on fox. The syntax would go as follows:<br />
aurbuild -s fox fxdesktop<br />
Through an interactive and dynamic [http://infiditus.homelinux.org/arch/projects/aurbuild/screenies/menusafe-1.png menu], files packed in the tarball can be viewed or edited as needed using your global EDITOR variable on your machine. ''CAUTION: EDIT THESE FILES AT YOUR OWN RISK! IMPROPER EDITING MAY RESULT IN A BROKEN SYSTEM! '' If you do not have a global editor defined (echo $EDITOR gives you nothing), you may set one up in your ~.bashrc file as<br />
export EDITOR="your_editor"<br />
You may have to logout and login for the change to take effect.<br />
<br />
<br />
A SAFE: status will be given at the top of the menu to indicate that a Trusted User has flagged the files safe. It is recommended to NOT edit these files if flagged safe unless you need the package taylored to your needs. <br />
<br />
The menu may be bypassed if the package is flagged safe by appending -a or --auto-build as a modifier to the dependency installation method. Ie: <br />
aurbuild -sa package<br />
If not detected safe, the menu will be given. The --auto-build switch is recommended for beginner users and those not familiar with PKGBUILD's.<br />
<br />
<br />
Once you are ready to build, aurbuild will check the dependencies and invoke makepkg to build the package and use sudo pacman to install it transparently.<br />
<br />
<br />
Operations can be (and highly recommended) run as regular user through<br />
the use of fakeroot and a properly set-up sudo account. This is desirable because fakeroot allows the package to be built with root rights and permissions yet disallows overwriting anything to the root filesystem during the build proccess. This may occur in the event of an improper PKGBUILD.<br />
Additionally, aurbuild will source the PKGBUILD for its own purposes and gracefully exit on improper (and therefore potentialy destructive) bash syntax.<br />
The role of sudo is to install the package and it's missing dependencies via pacman.<br />
<br />
<br />
A built-in search function using -S switch will search AUR for a single [keyword] and will be viewed using less.:<br />
aurbuild -S keyword<br />
[http://infiditus.homelinux.org/arch/projects/aurbuild/screenies/search-0.png screenshot]<br />
<br />
<br />
'''INSTALLATION'''<br />
<br />
To get aurbuild, download and install the latest package from the [http://infiditus.homelinux.org/arch/projects/aurbuild/ source link] at the top of the page. The /pkg directory contains the prebuilt package while /src contains the source and PKGBUILD. Once downloaded, install the package:<br />
pacman -U /path/to/package.pkg.tar.gz<br />
<br />
As mentioned earlier, aurbuild requires a properly set-up sudo account. This should be detected by pacman as a dependency once aurbuld is installed. To set sudo, you'll need to edit the sudoers file. This should be done through the visudo program only. Simply switch to root user and enter:<br />
visudo<br />
There you'll find the lines<br />
# Uncomment to allow people in group wheel to run all commands<br />
# %wheel ALL=(ALL) ALL<br />
<br />
# Same thing without a password<br />
#%wheel ALL=(ALL) NOPASSWD: ALL<br />
<br />
Simply uncomment one or the other and check that your user is added to the wheel group:<br />
groups username<br />
To add them to the group do:<br />
gpasswd -a username wheel<br />
<br />
<br />
'''WHERE DO PACKAGES GO?'''<br />
<br />
Aurbuild behaves identical to makepkg. That is packages are built in the current working directory unless specified otherwise in /etc/makepkg.conf. The "current working directory" will be a temporary hidden folder in $HOME where the package and other work files are placed. This hidden directory will be deleted along with your built package once aurbuild is finished. If you wish to keep the package, uncomment and set the "export PKGDEST=" variable in /etc/makepkg.conf to a desired destination directory. This allows makepkg (and aurbuild as it calls on makepkg) to store all built packages in a centralized location. Note this directory should have user write permissions as aurbuild will (hopefully) be run as user most of the time.<br />
<br />
<br />
'''KEEPING AURBUILD UP-TO-DATE'''<br />
<br />
Because aurbuild is in AUR, it can easily be updated by issuing the command:<br />
aurbuild -s aurbuild<br />
<br />
<br />
DISCLAIMER: AUR packages in unsupported CANNOT BE TRUSTED indiscriminantly. Use at your own risk!<br />
<br />
== qpkg - Another script which can do the same ==<br />
qpkg is a python script, written and contributed by Alexander 'dma147' Mieland, with which you can search for packages in '''all''' known repositories (official, TUR, PUR, etc...). You also can install packages directly from AUR (like aurbuild), but there is more... with qpkg you also can configure your pacman configuration to use user repositories (adding, removing and list repositories to pacman configuration).<br />
<br />
qpkg can be found here:<br><br />
-> http://aur.archlinux.org/packages.php?K=qpkg<br><br />
<br><br />
Or in the personal repository of dma147:<br><br />
[dma147]<br><br />
Server = http://arch.linux-stats.org/pkgs<br><br />
<br></div>Penguinhttps://wiki.archlinux.org/index.php?title=Aurbuild&diff=7321Aurbuild2005-12-20T00:28:12Z<p>Penguin: </p>
<hr />
<div>[[Category:Scripts]]<br />
[[Category:AUR]]<br />
<br />
== aurbuild ==<br />
''Contributed by Tyler Gates <TGates81 at gmail dot com>''<br />
<br />
Thread:<br />
http://bbs.archlinux.org/viewtopic.php?t=14872<br />
<br />
Source:<br />
http://user-contributions.org/users/penguin/projects/aurbuild/<br />
<br />
Aur:<br />
http://aur.archlinux.org/packages.php?K=aurbuild<br />
<br />
<br />
Aurbuild is a continuation of project originally created by Dusty<br />
Phillips (Dusty). It is a utility to build and install packages from the AUR.<br />
<br />
<br />
'''OVERVIEW'''<br />
<br />
Prior to build, both dependencies (makedepends() and depends() array) will be checked and automatically either: a)built and installed from source using makepkg and abs using -b or --builddeps switch or b)installed directly through pacman as needed using -s or --syncdeps switch.<br />
Example using -b:<br />
aurbuild -b packagename<br />
Packages may also be strung together. This is usefull when building a package that relies on another that also resides in AUR. Ie. fxdesktop relies on fox. The syntax would go as follows:<br />
aurbuild -s fox fxdesktop<br />
Through an interactive and dynamic [http://user-contributions.org/users/penguin/projects/aurbuild/screenies/menusafe-1.png menu], files packed in the tarball can be viewed or edited as needed using your global EDITOR variable on your machine. ''CAUTION: EDIT THESE FILES AT YOUR OWN RISK! IMPROPER EDITING MAY RESULT IN A BROKEN SYSTEM! '' If you do not have a global editor defined (echo $EDITOR gives you nothing), you may set one up in your ~.bashrc file as<br />
export EDITOR="your_editor"<br />
You may have to logout and login for the change to take effect.<br />
<br />
<br />
A SAFE: status will be given at the top of the menu to indicate that a Trusted User has flagged the files safe. It is recommended to NOT edit these files if flagged safe unless you need the package taylored to your needs. <br />
<br />
The menu may be bypassed if the package is flagged safe by appending -a or --auto-build as a modifier to the dependency installation method. Ie: <br />
aurbuild -sa package<br />
If not detected safe, the menu will be given. The --auto-build switch is recommended for beginner users and those not familiar with PKGBUILD's.<br />
<br />
<br />
Once you are ready to build, aurbuild will check the dependencies and invoke makepkg to build the package and use sudo pacman to install it transparently.<br />
<br />
<br />
Operations can be (and highly recommended) run as regular user through<br />
the use of fakeroot and a properly set-up sudo account. This is desirable because fakeroot allows the package to be built with root rights and permissions yet disallows overwriting anything to the root filesystem during the build proccess. This may occur in the event of an improper PKGBUILD.<br />
Additionally, aurbuild will source the PKGBUILD for its own purposes and gracefully exit on improper (and therefore potentialy destructive) bash syntax.<br />
The role of sudo is to install the package and it's missing dependencies via pacman.<br />
<br />
<br />
A built-in search function using -S switch will search AUR for a single [keyword] and will be viewed using less.:<br />
aurbuild -S keyword<br />
[http://user-contributions.org/users/penguin/projects/aurbuild/screenies/search-0.png screenshot]<br />
<br />
<br />
'''INSTALLATION'''<br />
<br />
To get aurbuild, download and install the latest package from the [http://user-contributions.org/users/penguin/projects/aurbuild/ source link] at the top of the page. The /pkg directory contains the prebuilt package while /src contains the source and PKGBUILD. Once downloaded, install the package:<br />
pacman -U /path/to/package.pkg.tar.gz<br />
<br />
As mentioned earlier, aurbuild requires a properly set-up sudo account. This should be detected by pacman as a dependency once aurbuld is installed. To set sudo, you'll need to edit the sudoers file. This should be done through the visudo program only. Simply switch to root user and enter:<br />
visudo<br />
There you'll find the lines<br />
# Uncomment to allow people in group wheel to run all commands<br />
# %wheel ALL=(ALL) ALL<br />
<br />
# Same thing without a password<br />
#%wheel ALL=(ALL) NOPASSWD: ALL<br />
<br />
Simply uncomment one or the other and check that your user is added to the wheel group:<br />
groups username<br />
To add them to the group do:<br />
gpasswd -a username wheel<br />
<br />
<br />
'''WHERE DO PACKAGES GO?'''<br />
<br />
Aurbuild behaves identical to makepkg. That is packages are built in the current working directory unless specified otherwise in /etc/makepkg.conf. The "current working directory" will be a temporary hidden folder in $HOME where the package and other work files are placed. This hidden directory will be deleted along with your built package once aurbuild is finished. If you wish to keep the package, uncomment and set the "export PKGDEST=" variable in /etc/makepkg.conf to a desired destination directory. This allows makepkg (and aurbuild as it calls on makepkg) to store all built packages in a centralized location. Note this directory should have user write permissions as aurbuild will (hopefully) be run as user most of the time.<br />
<br />
<br />
'''KEEPING AURBUILD UP-TO-DATE'''<br />
<br />
Because aurbuild is in AUR, it can easily be updated by issuing the command:<br />
aurbuild -s aurbuild<br />
<br />
<br />
DISCLAIMER: AUR packages in unsupported CANNOT BE TRUSTED indiscriminantly. Use at your own risk!<br />
<br />
== qpkg - Another script which can do the same ==<br />
qpkg is a python script, written and contributed by Alexander 'dma147' Mieland, with which you can search for packages in '''all''' known repositories (official, TUR, PUR, etc...). You also can install packages directly from AUR (like aurbuild), but there is more... with qpkg you also can configure your pacman configuration to use user repositories (adding, removing and list repositories to pacman configuration).<br />
<br />
qpkg can be found here:<br><br />
-> http://aur.archlinux.org/packages.php?K=qpkg<br><br />
<br><br />
Or in the personal repository of dma147:<br><br />
[dma147]<br><br />
Server = http://arch.linux-stats.org/pkgs<br><br />
<br></div>Penguinhttps://wiki.archlinux.org/index.php?title=Aurbuild&diff=6766Aurbuild2005-12-12T12:58:56Z<p>Penguin: /* aurbuild */</p>
<hr />
<div>[[Category:Scripts]]<br />
[[Category:AUR]]<br />
<br />
== aurbuild ==<br />
''Contributed by Tyler Gates <TGates81 at gmail dot com>''<br />
<br />
Thread:<br />
http://bbs.archlinux.org/viewtopic.php?t=14872<br />
<br />
Source:<br />
http://user-contributions.org/users/penguin/projects/aurbuild/<br />
<br />
Aur:<br />
http://aur.archlinux.org/packages.php?K=aurbuild<br />
<br />
<br />
Aurbuild is a continuation of project originally created by Dusty<br />
Phillips (Dusty). It is a utility to build and install packages from the AUR.<br />
<br />
<br />
'''OVERVIEW'''<br />
<br />
Prior to build, both dependencies (makedepends() and depends() array) will be checked and automatically either: a)built and installed from source using makepkg and abs using -b or --builddeps switch or b)installed directly through pacman as needed using -s or --syncdeps switch.<br />
Example using -b:<br />
aurbuild -b packagename<br />
Packages may also be strung together. This is usefull when building a package that relies on another that also resides in AUR. Ie. fxdesktop relies on fox. The syntax would go as follows:<br />
aurbuild -s fox fxdesktop<br />
Through an interactive and dynamic [http://user-contributions.org/users/penguin/projects/aurbuild/screenies/menusafe-1.png menu], files packed in the tarball can be viewed or edited as needed using your global EDITOR variable on your machine. ''CAUTION: EDIT THESE FILES AT YOUR OWN RISK! IMPROPER EDITING MAY RESULT IN A BROKEN SYSTEM! '' If you do not have a global editor defined (echo $EDITOR gives you nothing), you may set one up in your ~.bashrc file as<br />
export EDITOR="your_editor"<br />
You may have to logout and login for the change to take effect.<br />
<br />
<br />
A SAFE: status will be given at the top of the menu to indicate that a Trusted User has flagged the files safe. It is recommended to NOT edit these files if flagged safe unless you need the package taylored to your needs. <br />
<br />
The menu may be bypassed if the package is flagged safe by appending -a or --auto-build as a modifier to the dependency installation method. Ie: <br />
aurbuild -sa package<br />
If not detected safe, the menu will be given. The --auto-build switch is recommended for beginner users and those not familiar with PKGBUILD's.<br />
<br />
<br />
Once you are ready to build, aurbuild will check the dependencies and invoke makepkg to build the package and use sudo pacman to install it transparently.<br />
<br />
<br />
Operations can be (and highly recommended) run as regular user through<br />
the use of fakeroot and a properly set-up sudo account. This is desirable because fakeroot allows the package to be built with root rights and permissions yet disallows overwriting anything to the root filesystem during the build proccess. This may occur in the event of an improper PKGBUILD.<br />
Additionally, aurbuild will source the PKGBUILD for its own purposes and gracefully exit on improper (and therefore potentialy destructive) bash syntax.<br />
The role of sudo is to install the package and it's missing dependencies via pacman.<br />
<br />
<br />
A built-in search function using -S switch will search AUR for a single [keyword] and will be viewed using less.:<br />
aurbuild -S keyword<br />
[http://user-contributions.org/users/penguin/projects/aurbuild/screenies/search-0.png screenshot]<br />
<br />
<br />
'''INSTALLATION'''<br />
<br />
To get aurbuild, download and install the latest package from the [http://user-contributions.org/users/penguin/projects/aurbuild/ source link] at the top of the page. The /pkg directory contains the prebuilt package while /src contains the source and PKGBUILD. Once downloaded, install the package:<br />
pacman -U /path/to/package.pkg.tar.gz<br />
<br />
As mentioned earlier, aurbuild requires a properly set-up sudo account. This should be detected by pacman as a dependency once aurbuld is installed. To set sudo, you'll need to edit the sudoers file. This should be done through the visudo program only. Simply switch to root user and enter:<br />
visudo<br />
There you'll find the lines<br />
# Uncomment to allow people in group wheel to run all commands<br />
# %wheel ALL=(ALL) ALL<br />
<br />
# Same thing without a password<br />
#%wheel ALL=(ALL) NOPASSWD: ALL<br />
<br />
Simply uncomment one or the other and check that your user is added to the wheel group:<br />
groups username<br />
To add them to the group do:<br />
gpasswd -a username wheel<br />
<br />
<br />
'''WHERE DO PACKAGES GO?'''<br />
<br />
Aurbuild behaves identical to makepkg. That is packages are built in the current working directory unless specified otherwise in /etc/makepkg.conf. The "current working directory" will be a temporary hidden folder in $HOME where the package and other work files are placed. This hidden directory will be deleted along with your built package once aurbuild is finished. If you wish to keep the package, uncomment and set the "export PKGDEST=" variable in /etc/makepkg.conf to a desired destination directory. This allows makepkg (and aurbuild as it calls on makepkg) to store all built packages in a centralized location. Note this directory should have user write permissions as aurbuild will (hopefully) be run as user most of the time.<br />
<br />
<br />
'''KEEPING AURBUILD UP-TO-DATE'''<br />
<br />
Because aurbuild is in AUR, it can easily be updated by issuing the command:<br />
aurbuild -s aurbuild<br />
<br />
Or, you can add the following to /etc/pacman.conf and pacman will keep it up-to-date:<br />
[penguin]<br />
Server = <nowiki>http://user-contributions.org/users/penguin/repo</nowiki> <br />
<br />
<br />
DISCLAIMER: AUR packages in unsupported CANNOT BE TRUSTED indiscriminantly. Use at your own risk!<br />
<br />
== qpkg - Another script which can do the same ==<br />
qpkg is a python script, written and contributed by Alexander 'dma147' Mieland, with which you can search for packages in '''all''' known repositories (official, TUR, PUR, etc...). You also can install packages directly from AUR (like aurbuild), but there is more... with qpkg you also can configure your pacman configuration to use user repositories (adding, removing and list repositories to pacman configuration).<br />
<br />
qpkg can be found here:<br><br />
-> http://aur.archlinux.org/packages.php?K=qpkg<br><br />
<br><br />
Or in the personal repository of dma147:<br><br />
[dma147]<br><br />
Server = http://arch.linux-stats.org/pkgs<br><br />
<br></div>Penguinhttps://wiki.archlinux.org/index.php?title=Activating_numlock_on_bootup&diff=5156Activating numlock on bootup2005-10-23T04:14:28Z<p>Penguin: /* Activating Numlock on Bootup */</p>
<hr />
<div>[[Boot Process]]<br />
[[Category:Boot Process]]<br />
== Activating Numlock on Bootup ==<br />
<br />
<br />
'''Virtual Consoles 1-6'''<br />
<br />
To activate the numlock during normal bootup in virtual consoles 1-6 (vc/n), add the following line to /etc/rc.local:<br />
for i in $(seq 6); do /usr/bin/setleds -D +num < /dev/vc/${i} >/dev/null; done<br />
<br />
<br />
'''X windows'''<br />
<br />
If you use startx to start your X windows session, simply install the numlockx package and add it to your ~/.xinitrc file.<br />
<br />
<br />
''Install numlockx:''<br />
pacman -S numlockx<br />
<br />
<br />
''Add it to ~/.xinitrc before "exec":''<br />
#!/bin/sh<br />
#<br />
# ~/.xinitrc<br />
#<br />
# Executed by startx (run your window manager from here)<br />
#<br />
<br />
numlockx &<br />
<br />
exec your_window_manager</div>Penguinhttps://wiki.archlinux.org/index.php?title=User_talk:Penguin&diff=5155User talk:Penguin2005-10-23T04:04:14Z<p>Penguin: </p>
<hr />
<div></div>Penguinhttps://wiki.archlinux.org/index.php?title=Activating_numlock_on_bootup&diff=5154Activating numlock on bootup2005-10-23T03:56:28Z<p>Penguin: </p>
<hr />
<div>[[Boot Process]]<br />
== Activating Numlock on Bootup ==<br />
<br />
<br />
'''Virtual Consoles 1-6'''<br />
<br />
To activate the numlock during normal bootup in virtual consoles 1-6 (vc/n), add the following line to /etc/rc.local:<br />
for i in $(seq 6); do /usr/bin/setleds -D +num < /dev/vc/${i} >/dev/null; done<br />
<br />
<br />
'''X windows'''<br />
<br />
If you use startx to start your X windows session, simply install the numlockx package and add it to your ~/.xinitrc file.<br />
<br />
<br />
''Install numlockx:''<br />
pacman -S numlockx<br />
<br />
<br />
''Add it to ~/.xinitrc before "exec":''<br />
#!/bin/sh<br />
#<br />
# ~/.xinitrc<br />
#<br />
# Executed by startx (run your window manager from here)<br />
#<br />
<br />
numlockx &<br />
<br />
exec your_window_manager</div>Penguinhttps://wiki.archlinux.org/index.php?title=User_talk:Penguin&diff=5153User talk:Penguin2005-10-23T03:37:43Z<p>Penguin: </p>
<hr />
<div>== Turning on Numlock at Bootup ==<br />
<br />
<br />
'''Virtual Consoles 1-6'''<br />
<br />
To activate the numlock during normal bootup in virtual consoles 1-6 (vc/n), add the following line to /etc/rc.local:<br />
for i in $(seq 6); do /usr/bin/setleds -D +num < /dev/vc/${i} >/dev/null; done<br />
<br />
<br />
'''X windows'''<br />
<br />
If you use startx to start your X windows session, simply install the numlockx package and add it to your ~/.xinitrc file.<br />
<br />
<br />
''Install numlockx:''<br />
pacman -S numlockx<br />
<br />
<br />
''Add it to ~/.xinitrc before "exec":''<br />
#!/bin/sh<br />
#<br />
# ~/.xinitrc<br />
#<br />
# Executed by startx (run your window manager from here)<br />
#<br />
<br />
numlockx &<br />
<br />
exec your_window_manager</div>Penguinhttps://wiki.archlinux.org/index.php?title=Aurbuild&diff=5128Aurbuild2005-10-21T11:35:18Z<p>Penguin: /* aurbuild */</p>
<hr />
<div>[[Category:Scripts]]<br />
[[Category:AUR]]<br />
<br />
== aurbuild ==<br />
''Contributed by Tyler Gates <TGates81@gmail.com>''<br />
<br />
Thread:<br />
http://bbs.archlinux.org/viewtopic.php?t=14872<br />
<br />
Source:<br />
http://user-contributions.org/users/penguin/projects/aurbuild/<br />
<br />
Aur:<br />
http://aur.archlinux.org/packages.php?K=aurbuild<br />
<br />
<br />
Aurbuild is a continuation of project originally created by Dusty<br />
Phillips (Dusty). It is a utility to build and install packages from the AUR.<br />
<br />
<br />
'''OVERVIEW'''<br />
<br />
Prior to build, both dependencies (makedepends() and depends() array) will be checked and automatically either: a)built and installed from source using makepkg and abs using -b or --builddeps switch or b)installed directly through pacman as needed using -s or --syncdeps switch.<br />
Example using -b:<br />
aurbuild -b packagename<br />
Packages may also be strung together. This is usefull when building a package that relies on another that also resides in AUR. Ie. fxdesktop relies on fox. The syntax would go as follows:<br />
aurbuild -s fox fxdesktop<br />
Through an interactive [http://user-contributions.org/users/penguin/projects/aurbuild/screenies/aurbuild_ss-0.png menu prompt], an editor of choice can be used to view or edit the PKGBUILD as desired. Once finished editing/viewing as needed, aurbuild will check the dependencies and invoke makepkg to build the package and pacman to install it. [http://user-contributions.org/users/penguin/projects/aurbuild/screenies/aurbuild_ss2-0.png screenshot]<br />
<br />
Operations can be (and highly recommended) run as regular user through<br />
the use of fakeroot and a properly set-up sudo account. This is desirable because fakeroot allows the package to be built with root rights and permissions yet disallows overwriting anything to the root filesystem during the build proccess. This may occur in the event of an improper PKGBUILD.<br />
Additionally, aurbuild will source the PKGBUILD for its own purposes and gracefully exit on improper (and therefore potentialy destructive) bash syntax.<br />
The role of sudo is to install the package and it's missing dependencies via pacman.<br />
<br />
<br />
A built-in search function using -S switch will search AUR for a given keyword and spit back the results piped to less:<br />
aurbuild -S keyword<br />
[http://user-contributions.org/users/penguin/projects/aurbuild/screenies/search-0.png screenshot]<br />
<br />
<br />
'''INSTALLATION'''<br />
<br />
To get aurbuild, download and install the latest package from the [http://user-contributions.org/users/penguin/projects/aurbuild/ source link] at the top of the page. The /pkg directory contains the prebuilt package while /src contains the source and PKGBUILD. Once downloaded, install the package:<br />
pacman -U /path/to/package.pkg.tar.gz<br />
<br />
As mentioned earlier, aurbuild requires a properly set-up sudo account. This should be detected by pacman as a dependency once aurbuld is installed. To set sudo, you'll need to edit the sudoers file. This should be done through the visudo program only. Simply switch to root user and enter:<br />
visudo<br />
There you'll find the lines<br />
# Uncomment to allow people in group wheel to run all commands<br />
# %wheel ALL=(ALL) ALL<br />
<br />
# Same thing without a password<br />
#%wheel ALL=(ALL) NOPASSWD: ALL<br />
<br />
Simply uncomment one or the other and check that your user is added to the wheel group:<br />
groups username<br />
To add them to the group do:<br />
gpasswd -a username wheel<br />
<br />
<br />
'''WHERE DO PACKAGES GO?'''<br />
<br />
Aurbuild behaves identical to makepkg. That is packages are built in the current working directory unless specified otherwise in /etc/makepkg.conf. The "current working directory" will be a temporary hidden folder in $HOME where the package and other work files are placed. This hidden directory will be deleted along with your built package once aurbuild is finished. If you wish to keep the package, uncomment and set the "export PKGDEST=" variable in /etc/makepkg.conf to a desired destination directory. This allows makepkg (and aurbuild as it calls on makepkg) to store all built packages in a centralized location. Note this directory should have user write permissions as aurbuild will (hopefully) be run as user most of the time.<br />
<br />
<br />
'''KEEPING AURBUILD UP-TO-DATE'''<br />
<br />
Because aurbuild is in AUR, it can easily be updated by issuing the command:<br />
aurbuild -s aurbuild<br />
<br />
Or, you can add the following to /etc/pacman.conf and pacman will keep it up-to-date:<br />
[penguin]<br />
Server = <nowiki>http://user-contributions.org/users/penguin/repo</nowiki> <br />
<br />
<br />
DISCLAIMER: AUR packages in unsupported CANNOT BE TRUSTED indiscriminantly. Use at your own risk!<br />
<br />
== qpkg - Another script which can do the same ==<br />
qpkg is a python script, written and contributed by Alexander 'dma147' Mieland, with which you can search for packages in '''all''' known repositories (official, TUR, PUR, etc...). You also can install packages directly from AUR (like aurbuild), but there is more... with qpkg you also can configure your pacman configuration to use user repositories (adding, removing and list repositories to pacman configuration).<br />
<br />
qpkg can be found here:<br><br />
-> http://aur.archlinux.org/packages.php?K=qpkg<br><br />
<br><br />
Or in the personal repository of dma147:<br><br />
[dma147]<br><br />
Server = http://arch.linux-stats.org/pkgs<br><br />
<br></div>Penguinhttps://wiki.archlinux.org/index.php?title=Aurbuild&diff=4010Aurbuild2005-10-12T00:19:53Z<p>Penguin: /* aurbuild */</p>
<hr />
<div>[[Category:Scripts]]<br />
[[Category:AUR]]<br />
<br />
== aurbuild ==<br />
''Contributed by Tyler Gates <TGates81@gmail.com>''<br />
<br />
Thread:<br />
http://bbs.archlinux.org/viewtopic.php?t=14872<br />
<br />
Source:<br />
http://user-contributions.org/users/penguin/projects/aurbuild/<br />
<br />
Aur:<br />
http://aur.archlinux.org/packages.php?K=aurbuild<br />
<br />
<br />
Aurbuild is a continuation of project originally created by Dusty<br />
Phillips (Dusty). It is a utility to build and install packages from the AUR.<br />
<br />
<br />
'''OVERVIEW'''<br />
<br />
Prior to build, both dependencies (makedepends() and depends() array) will be checked and automatically either: a)built and installed from source using makepkg and abs using -b or --builddeps switch or b)installed directly through pacman as needed using -s or --syncdeps switch.<br />
Example using -b:<br />
aurbuild -b packagename<br />
Packages may also be strung together. This is usefull when building a package that relies on another that also resides in AUR. Ie. fxdesktop relies on fox. The syntax would go as follows:<br />
aurbuild -s fox fxdesktop<br />
Through an interactive [http://user-contributions.org/users/penguin/projects/aurbuild/screenies/aurbuild_ss-0.png menu prompt], an editor of choice can be used to view or edit the PKGBUILD as desired. Once finished editing/viewing as needed, aurbuild will check the dependencies and invoke makepkg to build the package and pacman to install it. [http://user-contributions.org/users/penguin/projects/aurbuild/screenies/aurbuild_ss2-0.png screenshot]<br />
<br />
Operations can be (and highly recommended) run as regular user through<br />
the use of fakeroot and a properly set-up sudo account. This is desirable because fakeroot allows the package to be built with root rights and permissions yet disallows overwriting anything to the root filesystem during the build proccess. This may occur in the event of an improper PKGBUILD.<br />
Additionally, aurbuild will source the PKGBUILD for its own purposes and gracefully exit on improper (and therefore potentialy destructive) bash syntax.<br />
The role of sudo is to install the package and it's missing dependencies via pacman.<br />
<br />
<br />
A built-in search function using -S switch will search AUR for a given keyword and spit back the results piped to less:<br />
aurbuild -S keyword<br />
[http://user-contributions.org/users/penguin/projects/aurbuild/screenies/search-0.png screenshot]<br />
<br />
<br />
'''INSTALLATION'''<br />
<br />
To get aurbuild, download and install the latest package from the [http://user-contributions.org/users/penguin/projects/aurbuild/ source link] at the top of the page. The /pkg directory contains the prebuilt package while /src contains the source and PKGBUILD. Once downloaded, install the package:<br />
pacman -U /path/to/package.pkg.tar.gz<br />
<br />
As mentioned earlier, aurbuild requires a properly set-up sudo account. This should be detected by pacman as a dependency once aurbuld is installed. To set sudo, you'll need to edit the sudoers file. This should be done through the visudo program only. Simply switch to root user and enter:<br />
visudo<br />
There you'll find the lines<br />
# Uncomment to allow people in group wheel to run all commands<br />
# %wheel ALL=(ALL) ALL<br />
<br />
# Same thing without a password<br />
#%wheel ALL=(ALL) NOPASSWD: ALL<br />
<br />
Simply uncomment one or the other and check that your user is added to the wheel group:<br />
groups username<br />
To add them to the group do:<br />
gpasswd -a username wheel<br />
<br />
<br />
'''KEEPING AURBUILD UP-TO-DATE'''<br />
<br />
Since aurbuild is in AUR, it can easily be updated by issuing the command:<br />
aurbuild -s aurbuild<br />
<br />
Or, you can add the following to /etc/pacman.conf and pacman will keep it up-to-date:<br />
[penguin]<br />
Server = <nowiki>http://user-contributions.org/users/penguin/repo</nowiki> <br />
<br />
<br />
DISCLAIMER: AUR packages in unsupported CANNOT BE TRUSTED indiscriminantly. Use at your own risk!<br />
<br />
== qpkg - Another script which can do the same ==<br />
qpkg is a python script, written and contributed by Alexander 'dma147' Mieland, with which you can search for packages in '''all''' known repositories (official, TUR, PUR, etc...). You also can install packages directly from AUR (like aurbuild), but there is more... with qpkg you also can configure your pacman configuration to use user repositories (adding, removing and list repositories to pacman configuration).<br />
<br />
qpkg can be found here:<br><br />
-> http://aur.archlinux.org/packages.php?K=qpkg<br><br />
<br><br />
Or in the personal repository of dma147:<br><br />
[dma147]<br><br />
Server = http://arch.linux-stats.org/pkgs<br><br />
<br></div>Penguinhttps://wiki.archlinux.org/index.php?title=Aurbuild&diff=2918Aurbuild2005-10-12T00:09:51Z<p>Penguin: /* aurbuild */</p>
<hr />
<div>[[Category:Scripts]]<br />
[[Category:AUR]]<br />
<br />
== aurbuild ==<br />
''Contributed by Tyler Gates <TGates81@gmail.com>''<br />
<br />
Thread:<br />
http://bbs.archlinux.org/viewtopic.php?t=14872<br />
<br />
Source:<br />
http://user-contributions.org/users/penguin/projects/aurbuild/<br />
<br />
Aur:<br />
http://aur.archlinux.org/packages.php?K=aurbuild<br />
<br />
<br />
Aurbuild is a continuation of project originally created by Dusty<br />
Phillips (Dusty). It is a utility to build and install packages from the AUR.<br />
<br />
<br />
'''OVERVIEW:'''<br />
<br />
Prior to build, both dependencies (makedepends() and depends() array) will be checked and automatically either: a)built and installed from source using makepkg and abs using -b or --builddeps switch or b)installed directly through pacman as needed using -s or --syncdeps switch.<br />
Example using -b:<br />
aurbuild -b packagename<br />
Packages may also be strung together. This is usefull when building a package that relies on another that also resides in AUR. Ie. fxdesktop relies on fox. The syntax would go as follows:<br />
aurbuild -s fox fxdesktop<br />
Through an interactive [http://user-contributions.org/users/penguin/projects/aurbuild/screenies/aurbuild_ss-0.png menu prompt], an editor of choice can be used to view or edit the PKGBUILD as desired. Once finished editing/viewing as needed, aurbuild will check the dependencies and invoke makepkg to build the package and pacman to install it. [http://user-contributions.org/users/penguin/projects/aurbuild/screenies/aurbuild_ss2-0.png screenshot]<br />
<br />
Operations can be (and highly recommended) run as regular user through<br />
the use of fakeroot and a properly set-up sudo account. This is desirable because fakeroot allows the package to be built with root rights and permissions yet disallows overwriting anything to the root filesystem during the build proccess. This may occur in the event of an improper PKGBUILD.<br />
Additionally, aurbuild will source the PKGBUILD for its own purposes and gracefully exit on improper (and therefore potentialy destructive) bash syntax.<br />
The role of sudo is to install the package and it's missing dependencies via pacman.<br />
<br />
<br />
A built-in search function using -S switch will search AUR for a given keyword and spit back the results piped to less:<br />
aurbuild -S keyword<br />
[http://user-contributions.org/users/penguin/projects/aurbuild/screenies/search-0.png screenshot]<br />
<br />
<br />
'''INSTALLATION:'''<br />
<br />
To get aurbuild, download and install the latest package from the [http://user-contributions.org/users/penguin/projects/aurbuild/ source link] at the top of the page. The /pkg directory contains the prebuilt package while /src contains the source and PKGBUILD. Once downloaded, install the package:<br />
pacman -U /path/to/package.pkg.tar.gz<br />
<br />
As mentioned earlier, aurbuild requires a properly set-up sudo account. This should be detected by pacman as a dependency once aurbuld is installed. To set sudo, you'll need to edit the sudoers file. This should be done through the visudo program only. Simply switch to root user and enter:<br />
visudo<br />
There you'll find the lines<br />
# Uncomment to allow people in group wheel to run all commands<br />
# %wheel ALL=(ALL) ALL<br />
<br />
# Same thing without a password<br />
#%wheel ALL=(ALL) NOPASSWD: ALL<br />
<br />
Simply uncomment one or the other and check that your user is added to the wheel group:<br />
groups username<br />
To add them to the group do:<br />
gpasswd -a username wheel<br />
<br />
<br />
<br />
DISCLAIMER: AUR packages in unsupported CANNOT BE TRUSTED indiscriminantly. Use at your own risk!<br />
<br />
== qpkg - Another script which can do the same ==<br />
qpkg is a python script, written and contributed by Alexander 'dma147' Mieland, with which you can search for packages in '''all''' known repositories (official, TUR, PUR, etc...). You also can install packages directly from AUR (like aurbuild), but there is more... with qpkg you also can configure your pacman configuration to use user repositories (adding, removing and list repositories to pacman configuration).<br />
<br />
qpkg can be found here:<br><br />
-> http://aur.archlinux.org/packages.php?K=qpkg<br><br />
<br><br />
Or in the personal repository of dma147:<br><br />
[dma147]<br><br />
Server = http://arch.linux-stats.org/pkgs<br><br />
<br></div>Penguin