Mailing List Archive: Update alternatives packages for spfquery in Debian and derivatives

Julian,

Now that the update alternatives patch for libspf2 is approved and built for
the next Ubuntu release, I've been experimenting with it a bit (both the
pyspf-spfquery and libspf2-spfquery are update alternatives aware now).

A couple of points now that I understand this better...

I think it would be useful to have pyspf provide separate binary packages for
the SPF library (spf.py) and the spfquery so that the library doesn't get
removed by update alternatives. I'd appreciate some help with the debian/
changes for that.

Second, I see that you made your spfd update alternatives friendly. Are there
spfd's other than M:S:Q's that we need to consider for that too?

Scott K

-------
To unsubscribe, change your address, or temporarily deactivate your subscription,
please go to http://v2.listbox.com/member/?list_id=1007

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Scott Kitterman wrote:
> I think it would be useful to have pyspf provide separate binary
> packages for the SPF library (spf.py) and the spfquery so that the
> library doesn't get removed by update alternatives. I'd appreciate some
> help with the debian/ changes for that.

Look at the mail-spf-perl source package (if in doubt, the upstream one).
The main part in creating multiple binary packages is having multiple
binary package sections in debian/control. However, you need to take care
in debian/rules and debian/${binpkg}.install that things get installed
into the correct packages. It's difficult to give generic advice on that.
I suggest you give it a try and report back with any problems you
encounter.

> Second, I see that you made your spfd update alternatives friendly.

I assume you mean those in Mail::SPF and M:S:Q (as those are the SPF
libraries I have assumed maintenance of).

> Are there spfd's other than M:S:Q's that we need to consider for that
> too?

What do you mean? update-alternatives isn't exactly concerned about
individual instances of a file, just about its (common) name. The
specific u-a configuration for specific instances of the file must be
taken care of by the individual Debian packages (or more exactly, their
postinst/prerm scripts) in which the specific instances of the file are
distributed.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFFvLqlwL7PKlBZWjsRAo5cAJ4lS6pQzLuFvQUZQDZoTLnfXLNsFwCg4V4q
1rlUKpBYg4PkBXJH+f10te8=
=w5wT
-----END PGP SIGNATURE-----

-------
To unsubscribe, change your address, or temporarily deactivate your subscription,
please go to http://v2.listbox.com/member/?list_id=1007