[MacPorts] #42728: autogen @5.17.4_0: autoopts-config produces a stray -R flag, breaks gnutls @3.1.22_0 build

[MacPorts]

#42728: autogen @5.17.4_0: autoopts-config produces a stray -R flag, breaks gnutls
@3.1.22_0 build
-----------------------------+-------------------
  Reporter:  jwhowse4@…      |      Owner:  mww@…
      Type:  defect          |     Status:  new
  Priority:  Normal          |  Milestone:
 Component:  ports           |    Version:  2.2.1
Resolution:                  |   Keywords:
      Port:  autogen gnutls  |
-----------------------------+-------------------

Comment (by devans@…):

 Replying to [comment:29 mschamschula@…]:
 > Replying to [comment:28 cal@…]:
 > > Double checking I think it is a good idea to provide a `+dane`
 variant, since (a) `DANE` is (unfortunately) still not very widely used
 and (b) `unbound` depends on `openssl`, which would lead to the ironic
 situation of `gnutls` depending on `openssl`. Of course, this is the new
 maintainer's call in the end.
 >
 > I just checked the dependencies for unbound, and indeed unbound depends
 on openssl (and expat). I think we may want to move unbound into a
 variant, making it an optional install.

 Done in my most recent patch, +dane variant, since it is only necessary
 for DANE functionality.  Default build does not depend on unbound.

 >
 > >
 > > I agree with your handling of the autogen dependency (i.e., using the
 local lib opts).
 >
 > Same here.
 >
 > > As for the trust store file, should we set that to the path of `curl-
 ca-bundle` or the file generated by `certsync`, i.e.
 `$prefix/etc/openssl/cert.pem`? Is the trust store format expected by
 GnuTLS compatible with the one used by OpenSSL? Pending further work on
 the followup to `certsync` we don't have a PKCS11 module, so that should
 stay empty for now.
 >
 > I think using the {{{curl-ca-bundle}}} is a good idea, however, this
 makes for another dependency.

 I wouldn't worry about dependencies too much.  I think the primary goal is
 full functionality without the user having to make too many technical
 decisions.  Will leave this part to you as maintainer, see
 {{{
 ./configure --help
 }}}

 in ${worksrcpath} for the appropriate configuration options.  Again this
 is only a default and will be over-ridden if the calling application
 desires to do so. So may not be terribly important.  A review of how the
 various dependents handle this might be useful down the road.  Let me or
 cal know when you think things are ready to commit.

-- 
Ticket URL: <https://trac.macports.org/ticket/42728#comment:30>
MacPorts <http://www.macports.org/>
Ports system for OS X