You are not logged in.
Pages: 1
Topic closed
I'd like to install a package from the AUR which requires me to modify the source in order to configure it. What's the best way to do this? Should I just download the source and make install (to /usr/local) myself? Should I create a patch and modify the PKGBUILD?
Forgive me if this has been answered already. I found it difficult to formulate an effective search term.
Last edited by jonlorusso (2013-12-29 04:36:25)
Offline
There's some useful stuff here, though I don't know if that is the best way to go. What are the advantages of installing it as a package, rather than maintaining the source myself?
Offline
You don't need to use makepkg for simple packages like this, but it is a good idea to learn how to do it and have pacman track the installed package before you decide to freestyle it.
Download the tarball, extract it. Build it with makepkg. Make your changes and then rebuild and install it. Rinse and repeat.
Offline
I'd like to install a package from the AUR which requires me to modify the source in order to configure it. What's the best way to do this? Should I just download the source and make install (to /usr/local) myself? Should I create a patch and modify the PKGBUILD?
Forgive me if this has been answered already. I found it difficult to formulate an effective search term.
IMO, it's usually best to keep the package manager in on the loop when installing anything, which implies you should be doing things with a PKGBUILD at some point. So I guess my answer is ... just modify the PKGBUILD. You don't even need a patch for that (unless you want the package maintainer to change the PKGBUILD in the AUR).
Offline
Download the tarball, extract it. Build it with makepkg. Make your changes and then rebuild and install it. Rinse and repeat.
The reason I though I needed a patch is that, it seems like my modifications always get overridden:
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Found st-0.4.1.tar.gz
==> Validating source files with md5sums...
st-0.4.1.tar.gz ... Passed
==> Extracting sources...
-> Extracting st-0.4.1.tar.gz with bsdtar
==> Removing existing pkg/ directory...
==> Starting build()...
Is there some way to skip the (re)extract via makepkg?
Thanks--
Offline
Ah nevermind --help is your friend:
-e, --noextract Do not extract source files (use existing src/ dir)
Offline
man makepgk
is even friendlier
Please remember to mark your thread as [Solved] by editing your first post and prepending it to the title.
Offline
Yea, just replace the url source in the makepkg with the package's name and put it in the same folder as the makepkg. Then you have to use --skipinteg option because it won't pass the md5sums.
Last edited by xtraroot (2013-12-29 12:02:11)
Offline
The *correct* thing to do is to patch in prepare()
Last edited by Mr.Elendig (2013-12-29 13:23:55)
Evil #archlinux@libera.chat channel op and general support dude.
. files on github, Screenshots, Random pics and the rest
Offline
besides leaving comment on the package, how do I feedback a fix to a package?
For example, the conflict of brave-beta-bin is marked as brave-beta-bin, but it should be brave-bin actually.
How do I "fork and submit a pull request" of the PKGBUILD file?
package under reference: https://aur.archlinux.org/packages/brave-beta-bin
Offline
aabbcc1241, please do not necrobump old threads like this one. As far as I know, leaving a comment is the only way to give feedback to an aur package. You can also use the Submit Request button on the right to ask for a merge / deletion.
Offline
1. Don't expect people to immediately answer to an AUR comment
2. There usually are email addresses that can be used to contact the maintainer
3. Definitely do not necrobump a completely unrelated solved thread.
https://wiki.archlinux.org/index.php/Co … bumping.22
Closing.
Last edited by V1del (2018-10-03 21:56:00)
Offline
Pages: 1
Topic closed