Date: Wed, 13 Feb 2019 11:02:45 +0100 From: Kurt Jaeger <pi@freebsd.org> To: Dima Pasechnik <dimpase+freebsd@gmail.com> Cc: freebsd-ports@freebsd.org, Peter Jeremy <peter@rulingia.com> Subject: Re: [flint2] feature request - linking with ntl Message-ID: <20190213100245.GN2748@home.opsec.eu> In-Reply-To: <CAAWYfq3bxFagPHXgfbm0EtWb9ZHP2UopHcsQoJvoYd=AWPGykQ@mail.gmail.com> References: <CAAWYfq2iu2_qqEtT1A9bE_SNnBdUrH3ou4C1UyRpKT3VeBOYFQ@mail.gmail.com> <20190213050556.GH19533@server.rulingia.com> <CAAWYfq3bxFagPHXgfbm0EtWb9ZHP2UopHcsQoJvoYd=AWPGykQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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. > 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 ? -- pi@opsec.eu +49 171 3101372 One year to go !
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190213100245.GN2748>