Gentoo Archives: gentoo-dev

From: "Haelwenn (lanodan) Monnier" <contact@×××××××××.me>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] autotools
Date: Thu, 26 Mar 2020 18:07:46
Message-Id: 20200326180737.GC5066@cloudsdale.the-delta.net.eu.org
In Reply to: [gentoo-dev] autotools by Samuel Bernardo
1 [2020-03-26 17:47:35+0000] Samuel Bernardo:
2 > I send this email to ask you for your help for the better approach to
3 > translate the following autoreconf command to an ebuild:
4 >
5 > > |autoreconf -i -f ./configure \ --prefix=/usr \
6 > > --libexecdir=/usr/lib/snapd \
7 > > --with-snap-mount-dir=/var/lib/snapd/snap \ --enable-apparmor \
8 > > --enable-nvidia-biarch \ --enable-merged-usr|
9 > I realise that eautoreconf from autotools.eclass doesn't accept any
10 > parameters, so how would you advise me to reproduce it inside an ebuild
11 > using the available functions and eclasses?
12 >
13 > My goal is to create an ebuild from latest snapd pkgbuild:
14 > https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=snapd
15
16 Not sure if this would work out-of-the-box but this is how it is usually done:
17
18 src_prepare() {
19 default
20 eautoreconf
21 }
22
23 src_configure() {
24 econf \
25 --with-snap-mount-dir=/var/lib/snapd/snap \
26 --enable-nvidia-biarch \
27 --enable-merged-usr \
28 $(use_enable apparmor)
29 }
30
31 But as AUR has basically no quality requirement also consider that maybe it doesn't need eautoreconf at all, which can be nice to avoid.