[Pkg-electronics-devel] gnucap package.

[Felix Salfelder]

On Thu, Apr 19, 2018 at 08:18:36PM +0200, Carsten Schoenert wrote:
> The solution is really simple, answer yourself the question if gnucap
> can work without the plugins? Whenever the answer here is yes, a Depends
> is wrong.

Hi Carsten.

Perhaps I did not care enough about that. My main point was to have the
default plugins coinstallable. It now makes more sense either way.

> I'd say yes, as if not, why not to include the functionality directly
> within the gnucap package? Also if the answer is yes than
> gnucap-default-plugins0 can't be a Depends, but it's fine to recommend
> instead of suggest the package then.

Ok, this is a "Recommend" then. I think I now understand.

gnucap-default-plugins$n and libgnucap$n can now be installed for
various n, which wouldn't be possible if the plugins and /usr/bin/gnucap
are in one package. Also, somebody who upgrades gnucap will get the
plugins *unless* (s)he has disabled Recommends. With Recommends
disabled, the gnucap executable will end up crippled, but that will not
be our fault... All perfectly fine with me!

> Looking at your control file I don't see any recommended packages on
> gnucap-default-plugins0 nor reverse dependencies on gnucap. So what do
> you want to solve here? You do the packaging of gnucap, not for other

Ok, I put a "Suggests: gnucap" in gnucap-default-plugins0 then.

> Maybe not useless, but wrong in my eyes. You probably don't see the
> difference between depending and recommending.

I now do. I simply wasn't aware that "Recommend" is strong enough at
all.

Anyway, thanks for going that circle once again.

> > Perhaps I can do it in a fully reasonable way, once gnucap-conf is in
> > gnucap-common (and implemented with pkgconfig). currently it's a bit in
> > limbo anyway, as you noticed.
> > 
> >> The file README.Debian is the right place to explain the user important
> >> notes about the package(s) and their relationship if needed.
> > 
> > I will write this file, and get back to you.
> 
> Fine.

I started it. I am trying to address the gnucap-conf multiarch issue in
another branch, 'pkgconfig'. I totally need to package more of the other
stuff, to see how it plays. and test.

> Btw, libgnucap-dev needs some small addition to the short description,
> otherwise it looks like there is something forgotten.
> Maybe "GNU Circuit Analysis package, development library"

thanks a million
felix