Re: use_autogen

2017-12-25 Thread Ryan Schmidt
On Dec 25, 2017, at 12:38, Mojca Miklavec wrote: > On 23 December 2017 at 16:38, Ryan Schmidt wrote: >> Should we add a "use_autogen" (or "use_autogen_sh") option to MacPorts base? > > What about use_bootstrap.sh? (This is one I would need at the moment, &g

Re: use_autogen

2017-12-25 Thread Mojca Miklavec
On 23 December 2017 at 16:38, Ryan Schmidt wrote: > Should we add a "use_autogen" (or "use_autogen_sh") option to MacPorts base? What about use_bootstrap.sh? (This is one I would need at the moment, but it's only used in 9 other ports rather than 200.) I support t

Re: use_autogen

2017-12-24 Thread Ryan Schmidt
On Dec 23, 2017, at 10:18, Ken Cunningham wrote: > can you add environment variables to "use_autoconf"? > > some of these autogen.sh scripts automatically run configure if you don't set > one. Yes, you can add environment variables to any MacPorts "command". Just like destroot, build, and con

Re: use_autogen

2017-12-23 Thread Ken Cunningham
can you add environment variables to "use_autoconf"? some of these autogen.sh scripts automatically run configure if you don't set one. K > On Dec 23, 2017, at 7:38 AM, Ryan Schmidt wrote: > > Should we add a "use_autogen" (or "use_autogen_sh") o

use_autogen

2017-12-23 Thread Ryan Schmidt
Should we add a "use_autogen" (or "use_autogen_sh") option to MacPorts base? We already have "use_autoconf", "use_automake" and "use_autoreconf". Each of these add the autoconf, automake, libtool dependencies, and set up the right command to