-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am Donnerstag, 15. Mai 2003 10:20 schrieb Frank Küster: > Michael Koch <[EMAIL PROTECTED]> schrieb: > > Am Mittwoch, 14. Mai 2003 16:43 schrieb Christoph Berg: > >> Re: Advice needed for packaging sigcperl library and SigC perl > >> module [Michael Koch <[EMAIL PROTECTED]>, Wed, May 14, 2003 at > >> 03:36:08PM +0200, <[EMAIL PROTECTED]>] > >> > >> > - libsigcperl-0.2 (the helper library) > >> > - libsigcperl-dev (the development files) > >> > - libsigc-perl (its a binary perl module) > >> > >> Why not libsigc-perl-0.2 and libsigc-perl-dev to be consistent? > > > > Hmm, the upstream name of this is "sigcperl" and wouldn't this > > naming scheme even more irritating ? > > Definitely. I would expect libsigc-perl to be some virtual package > for installing libsigc-perl-0.2 or libsigc-perl-0.1.3 or > libsigc-perl-bla.
Thats were my thoughts too. > Why does the library have the version in its number, but not the > development package? What about the development packages for the > to-come library libsigcperl-0.4? You are right. libsigcperl-0.2 and libsigcperl-0.2-dev are better when the API changes. This means I will use the following package names: libsigcperl-0.2 (the helper library) libsigcperl-0.2-dev (the development files) libsigc-perl (the binary perl modul) Michael - -- Homepage: http://www.worldforge.org/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+w1Y6WSOgCCdjSDsRAj5TAJ4hOAPWzQP6ifyJafB/lkafCYgacgCcCQFC TngVw/4HN+kONqHEWK8scNk= =i1ng -----END PGP SIGNATURE-----
