Dear Mentors, I'm packaging the new shiny beta version of kmobiletools (www.kmobiletools.org).
This version is really different from the actual stable, and implements
two library and a plugins.
The first library is libkmobiletools, the foundation library of the sw.
The second is libkmobiletools_at.so, an engine that allows the
connection of AT based phones
The plug-in, allows the integration in kontact.
My first idea when I saw that there was a new plug-in was to split the
package in two: kmobiletools and kmobiletools-plugin-kontact.
After the inspection of the new code and the discover of the new library
I have a problem with the design of the new package structure, because
if I follow the splitting scheme written above I'll have:
kmobiletools - the real application;
libkmobiletools - the foundation library;
libkmobiletools-dev - libkmobiletools development files;
kmobiletools-plugin-kontact - the plugin;
libkmobiletools_at - the engine for AT based phone;
plus I should have 2 pseudo packages:
kmobiletools-engines - which depends on libkmobiletools_at because in
the near(?) future a new engine for GAMMU based phone
(probably something like libkmobiletools_gammu) will
be added
kmobiletools-plugins - which depends on kmobiletools-plugin-kontact, in
future more plugins will be added.
From my perspective 5 binary packages and 2 pseudo packages are too
much, I can delete the pseudo packages but 5 packages are still too
much.
What can I do in order to have a decent package separation without
splitting too much?
Regards
Francesco
--
:wq
pgpc74DJ8whfj.pgp
Description: PGP signature
