not yet, see https://bugs.archlinux.org/task/45591
On 15.08.2015 01:22, Taylor Lookabaugh wrote:
> Is there a possibility of a Co-Maintainer option in the AUR search
> critertia to list packages like the 'Search by' Maintainer option?
>
>
--
erdfisch
Stefan Auditor, Frank Holldorff & Fabian Lore
=== Signoff report for [community-testing] ===
https://www.archlinux.org/packages/signoffs/
There are currently:
* 4 new packages in last 24 hours
* 0 known bad packages
* 0 packages not accepting signoffs
* 0 fully signed off packages
* 20 packages missing signoffs
* 0 packages older than 14 days
mksrcinfo will include anything the PKGBUILD writes to stdout in the body
of the PKGBUILD (i.e. not in any prepare/build/package/etc. functions when
being sourced, for example:
pkgname=example
pkgver=1
echo "Hello world."
prepare() {}
build() {}
package() {}
... which will generate an .SRCINFO f
Maybe that’s a stupid question, but why do you need printing something to
stdout in a PKGBUILD, especially outside of any function ?
Bruno
Le 15 août 2015 11:56:51 GMT+02:00, Ido Rosen a écrit :
>mksrcinfo will include anything the PKGBUILD writes to stdout in the
>body
>of the PKGBUILD (i.e. n
On Sat, Aug 15, 2015 at 12:53 PM, Bruno Pagani
wrote:
> Maybe that’s a stupid question, but why do you need printing something to
stdout in a
> PKGBUILD, especially outside of any function ?
The only good reason I can think of, is to tell users that (and how) they
need to provide a source archive
