Sure, no problem. Currently, our build server uses some custom attributes in the PKGBUILD for additional metadata needed for things like release monitoring. I would like to start using .SRCINFO files on the server because they are easier to parse and also because it would be better convention-wise. Here's an example[1]. [1] https://github.com/Antergos/antergos-packages/blob/master/antergos/mate/mate... -- Dustin Falgout E-mail: dustin@falgout.us Github: lots0logs From: pacman-dev <pacman-dev-bounces@archlinux.org> on behalf of Allan McRae <allan@archlinux.org> Sent: Saturday, April 22, 2017 6:51 PM To: Discussion list for pacman development Subject: Re: [pacman-dev] [RFC] Make PKGBUILD attributes configurable On 23/04/17 09:36, Dustin Falgout wrote:
I would like a way to include custom attributes from the PKGBUILD in the output of the --printsrcinfo option. So basically, this...
pkgbase = pacman pkgdesc = A library-based package manager with dependency support pkgver = 5.0.1 pkgrel = 4 url = http://www.archlinux.org/pacman/ arch = i686 arch = x86_64 ... _custom_attribute1 = some value _custom_attribute2 = some value _custom_attribute3 = some value ...
pkgname = pacman
Bringing the mailing list back into this (seems our reply field is broken...) Can you give an example of what a custom attribute would be? Your example is still to vague to judge whether this would be something we wish to support. Thanks, Allan