Difference between revisions of "Arch User Repository"

imported>Richard
imported>Richard
Line 68: Line 68:
* Download the tarball from the AUR preferably to ''~/Downloads''
* Download the tarball from the AUR preferably to ''~/Downloads''
(just click on the tarball from your browser and you should get it)
(just click on the tarball from your browser and you should get it)


* Make a sub-directory in downloads called builds-
 
* Make a sub-directory in downloads called builds:
  mkdir ~/Downloads/builds
  mkdir ~/Downloads/builds


-- Move the tarball to builds (foo is the name of the package you've downloaded).
-- Move the tarball to builds (foo is the name of the package you've downloaded):
  mv foo.tar.gz builds
  mv foo.tar.gz builds


Line 86: Line 86:




* To make/compile the package, run-
* To make/compile the package, run:
  makepkg -s
  makepkg -s
This will build the package and pull in any dependencies needed.
This will build the package and pull in any dependencies needed.
''Note that it won't pull a dependency from the AUR, only from the Manjaro Repos.''
''Note: it won't pull a dependency from the AUR, only from the Manjaro Repos.''


If you run   
If you run   
   ls
   ls
you'll probably find a few new files. You're interested in the one that ends with .pkg.tar.xz (usually)
you'll probably find a few new files. You're interested in the one that ends with .pkg.tar.xz (usually)


Line 104: Line 103:
This is essentially what most install scripts do for you.
This is essentially what most install scripts do for you.


''Note''-To install the package, instead of using ''sudo pacman -U foo.pkg.xz'' can also use:
''Note:'' Instead of using ''sudo pacman -U foo.pkg.xz'' can also use:
  makepkg -i
  makepkg -i  




Anonymous user