any problems with this pkgbuild?

oliver · 2014-05-16 18:48:33

This is the first time I'm attempting this so I've picked something I think looks nice and easy

# Maintainer: oliver <ohemming@gmail.com>

pkgname=compute
pkgver=1.0.4
pkgrel=1
pkgdesc="compute is command-line program which performs simple calculation on input files"
arch=('i686' 'x86_64')
url="http://compute.teamerlich.org/"
license=('GPL3')
depends=('gperf')
source=("https://s3.amazonaws.com/agordon/compute/src/${pkgname}-${pkgver}.tar.gz")
md5sums=('8b8634e10d8bde512c17ca0f1f097583')

build() {
  cd "$srcdir/$pkgname-$pkgver"
  ./configure --prefix=/usr
  make
}

package() {
  cd "$srcdir/$pkgname-$pkgver"
  make DESTDIR="$pkgdir/" install
}

Couple of questions:
1) does anything stand out as missing or wrong?
2) how do pkg maintainers keep up to date on upstream changes? Is there another pkg out there that periodically checks for them?

Thanks

Trilby · 2014-05-16 18:57:49

Looks good to me except that gperf is a makedepends, and I'm not sure it is needed after that. I have the package installed and removed gperf without any negative side effects.

For question 2 - you either keep an eye out, or just wait for a user to flag your package out of date - the second way is much easier. As long as you respond promptly to such a flag, no body would mind at all. If it's out of date but never flagged ... then obviously it isn't bothering anyone

I do prefer vcs builds myself (this has a git version available) but this may not make great general advice.

EDIT: in response to the below - this was an additional "oh nice" when I built this. It doesn't depend on anything that is not in the base group.

Last edited by Trilby (2014-05-16 19:00:38)

graysky · 2014-05-16 18:58:50

At first glance it seems fine... are you sure about the only dependency (I am not implying otherwise)? Only way I know to keep up on new version is to manually check and update as needed.

oliver · 2014-05-16 19:08:43

graysky wrote:

At first glance it seems fine... are you sure about the only dependency (I am not implying otherwise)? Only way I know to keep up on new version is to manually check and update as needed.

yeah - like Trilby said, the only things I saw there would be part of base-devel

Trilby - thanks - I'll swap depends for makedepends

stqn · 2014-05-16 20:51:34

If the package is on sourceforge you can subscribe to the RSS feed for new downloadable files for example. Projects also often have a blog where new releases are announced (RSS feed, again). Or web forums, mailing lists… And sometimes twitter if you can bear it.

oliver · 2014-05-16 22:09:35

thanks for the advice everyone... PKGBUILD is now in AUR

Stefan Husmann · 2014-06-07 20:16:17

Very minor issue: we normally try to avoid repeating the pkgname in the pkgdesc to keep descriptions short.

oliver · 2014-06-08 00:22:39

thanks... I'll modify it if/when an update comes from upstream unless you think it deserves immediate attention

Arch Linux

#1 2014-05-16 18:48:33

any problems with this pkgbuild?

#2 2014-05-16 18:57:49

Re: any problems with this pkgbuild?

#3 2014-05-16 18:58:50

Re: any problems with this pkgbuild?

#4 2014-05-16 19:08:43

Re: any problems with this pkgbuild?

#5 2014-05-16 20:51:34

Re: any problems with this pkgbuild?

#6 2014-05-16 22:09:35

Re: any problems with this pkgbuild?

#7 2014-06-07 20:16:17

Re: any problems with this pkgbuild?

#8 2014-06-08 00:22:39

Re: any problems with this pkgbuild?

Board footer