On Wed, Feb 13, 2019 at 10:02 AM Kurt Jaeger <[email protected]> wrote: > > Hi! > > > > IMO, ntl should be an optional dependency. Whether it should default to > > > being "on" depends on the benefits gained from including it. > > > > I must say I am not too familiar with optional dependencies in ports. > > It would be fine it e.g. pkg can detect that ntl is already installed, > > and provide flint2 > > linked against ntl, but I don't know if this is/can be implemented. > > That would not be possible. > > First, we need a patch for the flint2 port to link to ntl in the first > place. Then we can find a way to make this an option and only then > the question can be answered if the option should be default-on or -off.
Currently only ./configure (written by hand script, no autotools) built of flint2 supports building with ntl. (I understand the choice of cmake-based built instead, certainly) This is not a big problem to fix, but it's not instant. I've asked upstream whether they have plans for this. https://github.com/wbhart/flint2/issues/542 > > > The main setback with this option on is that libflint.so file will be > > bigger in size (probably because C++-related ABI is not too small), > > but we're talking about extra 10-15 Mb or so. > > That does not look like a major problem. What does yuri@, the maintainer, say > ? > > -- > [email protected] +49 171 3101372 One year to go ! _______________________________________________ [email protected] mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[email protected]"
