Hi all!
The signon git repository [0] consists of
- the signond daemon
- the libsignon-qt client library
- the libsignon-extension library
- some authentication plugins (SASL, password, and some examples)
- unit tests for the daemon, library and plugins
- documentation for the daemon, library APIs and SASL plugin
The first MeeGo maintainer of this package decided to call it "libsignon", and
as a result we have packages named like this:
Wrote: /home/abuild/rpmbuild/SRPMS/libsignon-8.10-1.src.rpm
Wrote: /home/abuild/rpmbuild/RPMS/i586/libsignon-8.10-1.i586.rpm
Wrote: /home/abuild/rpmbuild/RPMS/i586/libsignon-saslplugin-8.10-1.i586.rpm
Wrote: /home/abuild/rpmbuild/RPMS/i586/libsignon-testplugin-8.10-1.i586.rpm
Wrote: /home/abuild/rpmbuild/RPMS/i586/libsignon-passwordplugin-8.10-1.i586.rpm
Wrote: /home/abuild/rpmbuild/RPMS/i586/libsignon-exampleplugin-8.10-1.i586.rpm
Wrote: /home/abuild/rpmbuild/RPMS/i586/libsignon-devel-8.10-1.i586.rpm
Wrote: /home/abuild/rpmbuild/RPMS/i586/libsignon-doc-8.10-1.i586.rpm
Wrote: /home/abuild/rpmbuild/RPMS/i586/libsignon-qt-doc-8.10-1.i586.rpm
Wrote: /home/abuild/rpmbuild/RPMS/i586/libsignon-tests-8.10-1.i586.rpm
Wrote: /home/abuild/rpmbuild/RPMS/i586/libsignon-debuginfo-8.10-1.i586.rpm
With the libsignon package containing both the library and the daemon. It all
seems a bit wrong to me, but I'm fairly new to RPMs so I'd like to hear your
opinions as well.
I'd like to split the packages a bit more, and to have something like:
signond
signond-tests
libsignon-qt
libsignon-qt-devel
libsignon-qt-doc
libsignon-qt-tests
libsignon-extension{,-devel,-doc,-tests}
signon-saslplugin{,-devel,-doc,-tests}
...
And turn libsignon as a metapackage depending on libsignon-qt (which in turn
will depend on signond), and libsignon-saslplugin a metapackage depending on
signon-saslplugin. Same for all other plugins.
Does all this make sense to you?
And if it does, any clues on how to implement this? In particular, I don't know
how to write the package names in the spec file (given that not all of them have
the same prefix).
Going even further: I'd like to change the source package name to "signon". Is
it something possible to do at this stage? Is it worth?
TIA,
Alberto
[0] http://gitorious.org/accounts-sso/signon
--
http://blog.mardy.it <-- geek in un lingua international!
_______________________________________________
MeeGo-packaging mailing list
[email protected]
http://lists.meego.com/listinfo/meego-packaging
