I'm maintain the geda source package, which builds the geda
and libgeda2 binary packages. (The split is just for policy-compliance;
they come from the same upstream source and libgeda2 isn't much use
to any other package at present).
Now the upstream maintainer has split the source into three separate
parts: gschem, libgeda, and symbols. I can quite easily package
these separately, creating gschem, libgeda2, libgeda-dev, and geda-symbols,
and maybe a geda umbrella package..
But I figure the extra packages are going to be hassle for porters.
It seems likely that all three will be released together upstream.
Building gschem will need libgeda2, libgeda-dev and geda-symbols installed.
This looks like trouble for porters/autobuild daemons.
Any comments? It seems easiest to create all the binary packages but
from one source. (Multiple source is probably easier for me to maintain
Hamish Moffatt VK3SB (ex-VK3TYD).
CCs of replies from mailing lists are welcome.