[2020-03-26 17:47:35+0000] Samuel Bernardo:
> I send this email to ask you for your help for the better approach to
> translate the following autoreconf command to an ebuild:
>
> > |autoreconf -i -f ./configure \ --prefix=/usr \
> > --libexecdir=/usr/lib/snapd \
> > --with-snap-mount-dir=/var/lib/snapd/snap \ --enable-apparmor \
> > --enable-nvidia-biarch \ --enable-merged-usr|
> I realise that eautoreconf from autotools.eclass doesn't accept any
> parameters, so how would you advise me to reproduce it inside an ebuild
> using the available functions and eclasses?
>
> My goal is to create an ebuild from latest snapd pkgbuild:
> https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=snapd
Not sure if this would work out-of-the-box but this is how it is usually done:
src_prepare() {
default
eautoreconf
}
src_configure() {
econf \
--with-snap-mount-dir=/var/lib/snapd/snap \
--enable-nvidia-biarch \
--enable-merged-usr \
$(use_enable apparmor)
}
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.
