PKGBUILD: on makedepends

hi. i am putting together a PKGBUILD. there are certain dependencies required for cutting a release, rolling a version, etc. but, for just downloading the sources and building, these dependencies are not needed. can i leave dependencies *out* of makedepends that are only used for non-mainline b

Re: PKGBUILD: on makedepends

hi, mpan, > Hello. makepkg does not support chosing between different > configurations. One PKGBUILD, one build type. If multiple build > configurations are needed, write (or generate) multiple PKGBUILDs. thanks for the reply. i apologize, my question was very poorly phrased. simpler: in

Re: PKGBUILD: on makedepends

Georg, Polarian, and kpcyrd, thanks much! that's what made sense. cheers, Greg

Re: PKGBUILD review.

Fabio, a newbie question: > there is validpgpkeys but is not checked in source=() would that suggest changing source=("git+https://gitlab.com/minecraftchest1/steamdeck-file-share-tool#tag=$pkgver";) to something like this source=("git+https://gitlab.com/minecraftchest1/steamdeck-f

git in makedepends?

hi, again. if git is needed only for the "source" line of PKGBUILD (i.e., to download, and optionally verify, the source file(s)), does git need to be listed in "makedepends"? cheers, Greg

Re: git in makedepends?

Fabio, et al., thanks! > > if git is needed only for the "source" line of PKGBUILD (i.e., to > > download, and optionally verify, the source file(s)), does git need to > > be listed in "makedepends"? > > Yes

request for review of PKGBUILD

hi. i'm trying to submit my first package to AUR. my package files are here: https://git.sr.ht/~minshall/aur-orgtbl-query/tree if anyone has a chance to look over my PKGBUILD (and any other of the files), and has any comments, i'm all ears. cheers, Greg

Re: request for review of PKGBUILD

Doug, thanks for the reply. > The only real issue I see is using $pkgdir in the build function. It's > not well defined at that point, and should not be relied on. Using > that as a prefix doesn't really make sense anyway, prefix is for the > install location, such as /usr/ or /opt/$pkgname/. ah

Re: request for review of PKGBUILD

hi, Caleb, thanks very much. > Hence almost all the PKGBUILD files in Arch official repos and the AUR > have override build system defaults from source packages to set the > prefix to be appropriate for package-manager managed paths rather than > end user source installs. thanks. `./configure -

Re: request for review of PKGBUILD

Bert, et al., > The general method is to keep the automation not in the repository > (path) where the PKGBUILD and .SRCINFO reside. aurpublish[1] for > example helps you set up a single source repository. Any packaging > utilities can live in the repository root while subfolders contain the > PKGB

Re: AUR unavailable because of broken refs

Leonidas, thanks for the update and the detailed information. and, i join you in thanking the DevOps team. cheers, Greg (random user)

Re: [aur-general] poe-git maintainership

Jonathon Fernyhough via aur-general wrote: > You might want to give them a little more time. that makes sense to me, too. but, am i right that it would also be legitimate, and even typical, for the package author to add a "poe" package to AUR? i.e, my sense is that quite often both "foo" and "

Re: [aur-general] New AUR Metadata Archives

Kevin, great -- thanks very much! i find the metadata archives very valuable. cheers, Greg