Re: [gentoo-dev] autotools

2020-03-26 Thread Haelwenn (lanodan) Monnier
[2020-03-26 17:47:35+] 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.




[gentoo-dev] autotools

2020-03-26 Thread Samuel Bernardo
Dear all,

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

Thank you,

Samuel



signature.asc
Description: OpenPGP digital signature


[gentoo-dev] autotools-utils cmake-utils: use common BUILD_DIR var

2012-11-29 Thread Michał Górny
Currently, each of the mentioned eclasses has its own *_BUILD_DIR.
Therefore, if someone needs to provide a custom BUILD_DIR, he needs to
set it explicitly for the eclass. This is fine for ebuilds but not
really neat for eclasses.

The idea is simple: use a common BUILD_DIR instead. For compatibility,
export AUTOTOOLS_  CMAKE_BUILD_DIR as well but prefer the former one.
For most of the ebuilds this won't make a difference.

I'm attaching an example conversion of pygobject where this would
benefit. The idea is quite simple; ebuild calls

python_foreach_impl autotools-utils_src_...

python_foreach_impl() sets BUILD_DIR for each implementation,
autotools-utils phases use that and everything simply works!




Re: [gentoo-dev] autotools eclass - set default for WANT_AUTO*

2007-01-12 Thread Mike Frysinger
On Sunday 07 January 2007 11:27, Alon Bar-Lev wrote:
 1. Add default.

we've gone this route ... if/when an issue comes up where someone is 
inheriting autotools but they're using it conditionally, we'll revisit this

autotools.eclass:
[[ -z ${WANT_AUTOCONF} ]]  WANT_AUTOCONF=latest
[[ -z ${WANT_AUTOMAKE} ]]  WANT_AUTOMAKE=latest
-mike


pgpsl2mdH5eUe.pgp
Description: PGP signature


Re: [gentoo-dev] autotools eclass - set default for WANT_AUTO*

2007-01-12 Thread Alon Bar-Lev

On 1/12/07, Mike Frysinger [EMAIL PROTECTED] wrote:

On Sunday 07 January 2007 11:27, Alon Bar-Lev wrote:
 1. Add default.

we've gone this route ... if/when an issue comes up where someone is
inheriting autotools but they're using it conditionally, we'll revisit this

autotools.eclass:
[[ -z ${WANT_AUTOCONF} ]]  WANT_AUTOCONF=latest
[[ -z ${WANT_AUTOMAKE} ]]  WANT_AUTOMAKE=latest
-mike


Thanks!
After you commit this, I will go over all my packages and remove the
latest setting.

Best Regards,
Alon Bar-Lev.
--
gentoo-dev@gentoo.org mailing list



Re: [gentoo-dev] autotools eclass - set default for WANT_AUTO*

2007-01-12 Thread Mike Frysinger
On Friday 12 January 2007 13:14, Mike Frysinger wrote:
 if/when an issue comes up where someone is
 inheriting autotools but they're using it conditionally, we'll revisit this

seems Diego is two steps ahead ... set the vars to none :)
-mike


pgpt5VjQENLt7.pgp
Description: PGP signature


Re: [gentoo-dev] autotools eclass - set default for WANT_AUTO*

2007-01-12 Thread Mike Frysinger
On Friday 12 January 2007 13:37, Alon Bar-Lev wrote:
 After you commit this

Diego already did
-mike
-- 
gentoo-dev@gentoo.org mailing list



[gentoo-dev] autotools eclass - set default for WANT_AUTO*

2007-01-06 Thread Alon Bar-Lev

Hello,

Is there any reason why not setting latest as default for WANT_AUTO* 
variables?

I believe that an ebuild should set these variables only if there is 
some exception.

Best Regards,
Alon Bar-Lev.
-- 
gentoo-dev@gentoo.org mailing list



Re: [gentoo-dev] autotools eclass - set default for WANT_AUTO*

2007-01-06 Thread Mike Frysinger
On Saturday 06 January 2007 05:10, Alon Bar-Lev wrote:
 Is there any reason why not setting latest as default for WANT_AUTO*
 variables?

 I believe that an ebuild should set these variables only if there is
 some exception.

that seems like a not-too-shabby idea actually
-mike


pgp7qE8JnVb2f.pgp
Description: PGP signature


Re: [gentoo-dev] autotools eclass - set default for WANT_AUTO*

2007-01-06 Thread Kevin F. Quinn
On Sat, 6 Jan 2007 05:21:48 -0500
Mike Frysinger [EMAIL PROTECTED] wrote:

 On Saturday 06 January 2007 05:10, Alon Bar-Lev wrote:
  Is there any reason why not setting latest as default for
  WANT_AUTO* variables?
 
  I believe that an ebuild should set these variables only if there is
  some exception.
 
 that seems like a not-too-shabby idea actually

Not sure.  Would we run the risk that working ebuilds would start to
fail when newer autotools versions arrive?

-- 
Kevin F. Quinn


signature.asc
Description: PGP signature


Re: [gentoo-dev] autotools eclass - set default for WANT_AUTO*

2007-01-06 Thread Diego 'Flameeyes' Pettenò
On Saturday 06 January 2007 11:10, Alon Bar-Lev wrote:
 Is there any reason why not setting latest as default for WANT_AUTO*
 variables?
Because then stuff will magically work in stable, and break in ~arch, and 
you won't know why it's happening.

Instead if you follow the procedure (set the variables) you know that you 
asked for latest version, and you'll be able to check what the problem is.

Yes, I expect automake 1.11 to break even more, as they are coming around.

-- 
Diego Flameeyes Pettenò - http://farragut.flameeyes.is-a-geek.org/
Gentoo/Alt lead, Gentoo/FreeBSD, Video, Sound, ALSA, PAM, KDE, CJK, Ruby ...


pgpPAoqa6BKbF.pgp
Description: PGP signature


Re: [gentoo-dev] autotools eclass - set default for WANT_AUTO*

2007-01-06 Thread Mike Frysinger
On Saturday 06 January 2007 09:47, Kevin F. Quinn wrote:
 Mike Frysinger [EMAIL PROTECTED] wrote:
  On Saturday 06 January 2007 05:10, Alon Bar-Lev wrote:
   Is there any reason why not setting latest as default for
   WANT_AUTO* variables?
  
   I believe that an ebuild should set these variables only if there is
   some exception.
 
  that seems like a not-too-shabby idea actually

 Not sure.  Would we run the risk that working ebuilds would start to
 fail when newer autotools versions arrive?

which is no different from the current behavior ... we're sticking latest 
into all of our ebuilds now

besides, if code doesnt work with the latest autotools, it should be fixed ... 
it should not force older versions
-mike


pgpF6wLMwMqNA.pgp
Description: PGP signature


Re: [gentoo-dev] autotools eclass - set default for WANT_AUTO*

2007-01-06 Thread Mike Frysinger
On Saturday 06 January 2007 10:22, Diego 'Flameeyes' Pettenò wrote:
 On Saturday 06 January 2007 11:10, Alon Bar-Lev wrote:
  Is there any reason why not setting latest as default for WANT_AUTO*
  variables?

 Because then stuff will magically work in stable, and break in ~arch, and
 you won't know why it's happening.

i dont follow

 Instead if you follow the procedure (set the variables) you know that you
 asked for latest version, and you'll be able to check what the problem is.

what does it matter if all of the ebuilds declare latest or the eclass 
declares latest ?
-mike


pgpYF0D2Zuq7V.pgp
Description: PGP signature


Re: [gentoo-dev] autotools eclass - set default for WANT_AUTO*

2007-01-06 Thread Diego 'Flameeyes' Pettenò
On Saturday 06 January 2007 16:42, Mike Frysinger wrote:
 what does it matter if all of the ebuilds declare latest or the eclass
 declares latest ?
Weren't we going to allow declaring 1.10 1.9 soon, so that we could stop 
using latest ?

-- 
Diego Flameeyes Pettenò - http://farragut.flameeyes.is-a-geek.org/
Gentoo/Alt lead, Gentoo/FreeBSD, Video, Sound, ALSA, PAM, KDE, CJK, Ruby ...


pgpkB6OyboWhP.pgp
Description: PGP signature


Re: [gentoo-dev] autotools eclass - set default for WANT_AUTO*

2007-01-06 Thread Mike Frysinger
On Saturday 06 January 2007 11:05, Diego 'Flameeyes' Pettenò wrote:
 On Saturday 06 January 2007 16:42, Mike Frysinger wrote:
  what does it matter if all of the ebuilds declare latest or the eclass
  declares latest ?

 Weren't we going to allow declaring 1.10 1.9 soon, so that we could stop
 using latest ?

no, that was not the reason at all for the new syntax

the reason was so in the *eclass* you could translate latest to 1.10 1.9 and 
drop the need of executing that helper function in local scope
-mike


pgpShqVd4GWns.pgp
Description: PGP signature


Re: [gentoo-dev] autotools eclass - set default for WANT_AUTO*

2007-01-06 Thread Diego 'Flameeyes' Pettenò
On Saturday 06 January 2007 18:25, Mike Frysinger wrote:
 the reason was so in the *eclass* you could translate latest to 1.10 1.9
 and drop the need of executing that helper function in local scope
Right, but I thought the other one, too..

Well, I suppose it would do little harm at this point to default to latest, 
and be done with that, and allow specifying 1.10 1.9 in the future (when mips 
and ppc would keyword the wrapper) so that we cover that base too.

-- 
Diego Flameeyes Pettenò - http://farragut.flameeyes.is-a-geek.org/
Gentoo/Alt lead, Gentoo/FreeBSD, Video, Sound, ALSA, PAM, KDE, CJK, Ruby ...


pgpDycsPuoY17.pgp
Description: PGP signature


Re: [gentoo-dev] autotools eclass - set default for WANT_AUTO*

2007-01-06 Thread Mike Frysinger
On Saturday 06 January 2007 13:00, Diego 'Flameeyes' Pettenò wrote:
 On Saturday 06 January 2007 18:25, Mike Frysinger wrote:
  the reason was so in the *eclass* you could translate latest to 1.10
  1.9 and drop the need of executing that helper function in local scope

 Right, but I thought the other one, too..

 Well, I suppose it would do little harm at this point to default to latest,
 and be done with that, and allow specifying 1.10 1.9 in the future (when
 mips and ppc would keyword the wrapper) so that we cover that base too.

why not just get rid of the idea of latest ?  is there a scenario where 
autotools would be inherited but not actually used/added to DEPEND ?  i guess 
that's what this all comes down to really ...
-mike


pgp0Ea3AiNLsP.pgp
Description: PGP signature


Re: [gentoo-dev] autotools eclass - set default for WANT_AUTO*

2007-01-06 Thread Mike Frysinger
On Saturday 06 January 2007 13:32, Diego 'Flameeyes' Pettenò wrote:
 On Saturday 06 January 2007 19:23, Mike Frysinger wrote:
  why not just get rid of the idea of latest ?  is there a scenario where
  autotools would be inherited but not actually used/added to DEPEND ?  i
  guess that's what this all comes down to really ...

 If autotools were to be inherited by an eclass, and left to the eclass
 users to depending on the correct versions, I'd say.

and how likely is this situation ?
-mike


pgpFhtBLNG44J.pgp
Description: PGP signature


[gentoo-dev] autotools - 'make' infinite loop

2006-07-05 Thread Marcus Furlong
Hi,

I am trying to create an ebuild for the icecream monitor available at

  ftp://ftp.suse.com/pub/projects/icecream/icemon-kde3.tar.bz2

Running 'configure' goes fine, but running 'make' just keeps running
configure over and over. If there's any autotools gurus who can have a
quick look, it'd be much appreciated! :) I've spent ages trying to fix it
but to no avail, and upstream hasn't got time to look at it at the moment.

The latest version of sys-devel/icecream is required for configure to
complete the first time, the ebuild is here:

  https://bugs.gentoo.org/show_bug.cgi?id=139352

Many thanks to anyone who has a few minutes to look at it,

Marcus.

-- 
gentoo-dev@gentoo.org mailing list



Re: [gentoo-dev] autotools - 'make' infinite loop

2006-07-05 Thread Diego 'Flameeyes' Pettenò
On Wednesday 05 July 2006 22:05, Marcus Furlong wrote:
 Running 'configure' goes fine, but running 'make' just keeps running
 configure over and over.
It's commonly caused when the timestamp of configure and the sources for 
configure are messed up. Make sure no file has modification time in the 
future, and let the configure script to be regenerated forcefully before 
make.
If you're using kde eclass, just remove the 'configure' file before 
kde_src_compile, and the eclass will take care.

If the files have modification time in the future, you must run in src_unpack 
something like

find ${S} -type f -print0 | xargs -0 touch

-- 
Diego Flameeyes Pettenò - http://farragut.flameeyes.is-a-geek.org/
Gentoo/Alt lead, Gentoo/FreeBSD, Video, AMD64, Sound, PAM, KDE


pgpTu6gSG0jX7.pgp
Description: PGP signature