On 2019/05/11 19:19, Marc Espie wrote: > On Sat, May 11, 2019 at 01:22:58AM +0200, Antoine Jacoutot wrote: > > On Sat, May 11, 2019 at 01:08:29AM +0200, Christian Weisgerber wrote: > > > Here's a draft for CONFIGURE_STYLE=autoreconf. No man page parts > > > yet. > > As far as the basic infrastructure changes go, things look fine. > This makes for one new variable to document (AUTORECONF) which > is nice. > > Haven't seen any problems there. > > > Oh for sure we want to default to 'autoreconf -fi'. > > But we need to be able to also set it to autogen.sh if needed. Because > > sometimes > > autoreconf will not work before some other autoshit are run first (or stuff > > like gettextize etc.) which autogen.sh takes care of. > > Anything needed besides setting AUTORECONF on those ports ?
Not usually. Sometimes they need "sh ./autogen.sh" instead (it's not uncommon for these to have a #!/bin/bash) but that's not a problem. > > > He has also raised two questions: > > > * Which autotools dependencies do we want to enable by default? > > > I put autoconf and automake there, but libtoolize (from libtool) > > > is often needed, too. Sometimes autopoint (from gettext-tools) > > > is required. > > > > As far as I am concerned I don't mind enforcing these build dependencies. > > Beware of build loops though. If you add these unconditionally, then > you can't benefit from autoreconf anywhere in the build path leading > to autopoint or libtoolize > > For now, that's just > archivers/xz > converters/libiconv > devel/autoconf/2.67 > devel/gettext > devel/gettext-tools > devel/help2man > devel/libtool > devel/metaauto > > So, it looks fine for now... > Let's assume gnu isn't going to do something stupid in the near > future... libtoolize (for the .m4 file) makes sense (I would suggest making it a RUN_DEPENDS for autoconf ports, except there's a circular dep). It's very often needed, and there's no automatic mechanism to show a missing bdep on this so it's very often missed. I'd prefer not to add gettext-tools; - the common tools are poisoned in WRKDIR/bin anyway, so the missing dep will usually be noticed in this case - it's common to switch CONFIGURE_STYLE between autoconf and gnu during the life of a port (sometimes input files need patching, other times they don't and you don't want to add the dependencies). having to add a bdep on gettext-tools because you switched from auto(re)conf to gnu seems a bit counterintuitive. > (as for dpb dependencies proper, all things that take time building > among these of these are critical enough that they get to be built > first in any case) > > > > * Should we set NOCONFIGURE=1 in the environment by default, as > > > many autogen.sh scripts use this in order not to run configure? > > > > I am in favor of this. Otherwise we end up running configure twice... yes I think this makes sense too. > To be clear, you're talking about > AUTOCONF_ENV += NOCONFIGURE=1 > if CONFIGURE_STYLE is autoreconf, right ? >
