http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5752
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
------- Additional Comments From [EMAIL PROTECTED] 2007-12-20 01:48 -------
(In reply to comment #4)
> (In reply to comment #3)
> > As someone who packages SpamAssassin,
> > I'd want a way to download the rules as a tarball for packaging purposes.
>
> There already is a way to get a tarball of the rules... wget, or whatever, the
> sa-update update tarball. Or you can get the rules from SVN.
Installation's a bit of a bummer though right now. :(
here's a proposal. Currently, sa-update does this for each channel:
- nslookup the TXT record for the current version
- nslookup/HTTP get the mirrors list
- HTTP get the appropriate .tar.gz file for that version under one of the
mirrors
- GPG verify the package
- unpack the tar.gz in a tmp dir
- lint check it
- extract into /var/lib/spamassassin, using a good deal of paranoia
In other words, it's doing two main tasks here; the first 3 steps are the
downloading of the appropriate package from our server via HTTP, and the
latter 4 steps are an appropriately-paranoid extraction step.
Why don't we add a switch to sa-update ("--install"?) which, once given a
.tar.gz
and its .asc and .sha1 verification stamps, will install that ruleset.
That way, people who don't want to require net use for the initial setup
can bundle those 3 files, and run "sa-update --install foo.tar.gz foo.tar.gz.asc
foo.tar.gz.sha1" at the end of "make install".
Who knows, maybe it'd be appropriate for *us* to bundle one of these in our
release tarballs, too...
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
