Re: no{thing} build profiles
On 2018-10-23 16:55:00 +0200, Wouter Verhelst wrote:
> On Sun, Oct 21, 2018 at 12:13:27PM -0400, Marvin Renich wrote:
> > * Sune Vuorela <nospam@vuorela.dk> [181021 06:05]:
> > > On 2018-10-21, Jonas Smedegaard <jonas@jones.dk> wrote:
> > > > I disagree that libgpgme11 should depend/recommend/suggest gnupg at all:
> > > > As a library it cannot possibly declare how tight a relationship to
> > > > declare - instead, all _consumers_ of the library must declare whether
> > > > they depend/recommend/suggest gnupg.
> > >
> > > libgpgme is completely useless without gnupg. I think it is perfectly
> > > fine for these kind of relations, unless we really are in corner-case
> > > territory. See for example fam.
> >
> > I strongly agree with Jonas. Upstream links to libgpgme as a .so to
> > provide optional behavior. This requires libgpgme to be installed in
> > order to even run neomutt, whether the user wants the feature or not.
> > It is perfectly reasonable to want to install neomutt but want to _not_
> > install gnupg.
>
> Not in Debian.
>
> The Debian philosophy in this has always been to link against all
> libraries where possible, and to detect at runtime whether something can
> be used. [...]
This matches what Marvin said just above: Link against libgpgme (thus
depend on it) and let the user choose whether to install gnupg or not.
The availability of gnupg is checked at runtime.
--
Vincent Lefèvre <vincent@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
Reply to: