Bug 1341 - Improve packageability of libspamc
Summary: Improve packageability of libspamc
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: Building & Packaging (show other bugs)
Version: SVN Trunk (Latest Devel Version)
Hardware: PC Linux
: P2 enhancement
Target Milestone: Future
Assignee: SpamAssassin Developer Mailing List
Depends on:
Reported: 2003-01-04 23:43 UTC by James Braid
Modified: 2015-04-13 22:05 UTC (History)
2 users (show)

Attachment Type Modified Status Actions Submitter/CLA Status
Add install rule to binaries.mk and required stuff to configure patch None Christoph Hohmann [NoCLA]
Let libspamc tell spamc whether it's compiled with SSL support patch None Magnus Holmgren [NoCLA]

Note You need to log in before you can comment on or make changes to this bug.
Description James Braid 2003-01-04 23:43:25 UTC
The Debian packages at http://people.debian.org/~duncf/debian/ and also the 
debian/ directory in CVS dont build or package libspamc.

I had a look at hacking in some rules to make & package libspamc but I dont 
know enough about the Debian packaging stuff to make it work properly.
Comment 1 Duncan Findlay 2003-01-05 17:40:10 UTC
This type of bug (i.e. specifically related to Debian packaging) needs to be
filed in the Debian BTS. (file against the package spamassassin)

I don't see myself fixing this soon... but I suppose eventually I should get
around to it.

Closing INVALID, not because the bug is INVALID, but rather this is the wrong
place to report it.
Comment 2 Christoph Hohmann 2003-08-04 16:22:58 UTC
The is not a Debian problem. The installer in the SpamAssassin package does not
install the library in a directory like {prefix}/lib. So it is not included in
the Debian package.

I have created a little patch to add this ability to the configure script and
the binaries.mk Makefile. You need the scripts "install-sh" and "mkinstalldirs"
from the automake package for it (just copy them to the directory where
configure is located). Then you have to run

make -f binaries.mk install

This will install the library (libspamc.so) and the header file (libspamc.h) in
the correct location. I did not understand the Makefile.PL stuff to add it
there. But I'm sure the SpamAssassin developers could add it and it would be
good if this ability could be added to the SpamAsssassin package.
Comment 3 Christoph Hohmann 2003-08-04 16:24:24 UTC
Created attachment 1215 [details]
Add install rule to binaries.mk and required stuff to configure
Comment 4 Magnus Holmgren 2007-03-22 07:22:40 UTC
I'm interested in this. There is a libspamc$(SHLIBEXT) target in spamc/
Makefile.in, but it's not used. What were the original plans for this?

Having a shared spamc library makes it easier to integrate various spplications 
with SpamAssassin.
Comment 5 Magnus Holmgren 2007-03-22 09:26:56 UTC
Created attachment 3885 [details]
Let libspamc tell spamc whether it's compiled with SSL support

Here is one thing I think is needed to decouple libspamc from spamc. Since
there is no SSL-related code at all in spamc.c, except for the version
information and option parsing, I think spamc should ask libspamc whether it is
compiled with SSL support. This gives many options: spamc can still be compiled
with libspamc statically, or it can be compiled dynamically. In the latter
case, one can choose to link with either libspamc or libsslspamc, or both
versions (with or without SSL support) can be called libspamc, and the
administrator can switch between them without rebuilding the spamc binary.
Comment 6 Magnus Holmgren 2007-03-24 14:21:34 UTC
So, please reopen, set severity to enhancement and change the summary to 
"Please make libspamc packageable" or something like that.
Comment 7 Duncan Findlay 2007-06-11 21:28:03 UTC
Looks like this should have been reopened a while ago... Oops.
Comment 8 Kevin A. McGrail 2015-04-13 22:05:01 UTC
Pushing to future as an enhancement

Christoph and Magnus, can you please file a CLA for your patches?