Re: [PROPOSAL] Enhancements to sa-update, discussion.. possibly for 4.1
| Newsgroups | gmane.mail.spam.spamassassin.devel |
|---|---|
| Message-ID | <[email protected]> |
On 7/17/25 7:49 PM, Michael Peddemors wrote: > On 2025-07-17 10:38, Michael Peddemors wrote: >> Proposal for sa-update changes. > > ... > >> channels. We also propose that those two functionalities be separated, (eg sa-init vs sa-update) as sa-update is generally only used by package maintainers and developers. > > Correction for clarity.. I mean that sa-update from the packaged initial rule set in flat files, is generally only used by maintainers and developers, while sa-update for 'updating' from mirrors is a different operation. > > sa-update might be run with '--install' parameter in automation tools as well (Ansible, Puppet, ...) in order to bootstrap new SpamAssassin servers, I cannot see any big improvements in splitting sa-update(1) code in two actually. Cheers Giovanni
OpenPGP_signature.asc
(application/pgp-signature, 840 B)
-----BEGIN PGP SIGNATURE----- wsF5BAABCAAjFiEEqg3TnG6R3qYMxl94+r7qCYlyWOUFAmh6dKwFAwAAAAAACgkQ+r7qCYlyWOWz 1xAAmquz65BgtjXKANLVYro8xZw+ScWB2GkqMtOmyyUNZS0Q2o8p+wC+j4A6gAcCMToiRkLuFi+Y nqEPFcpr3xIQtgAjEt8GBlxeW2XpXbLMssoPCpUD8/za3B8qdgK0GgYgMFflxdymwmIFRuyUyG1H DWlIWeZJdji7lSS6zRk3iVBeJ/Ukz+gsKtd2/3fRCQzaidPTC7fxRJ4q7GiQ1fxlhVQ8jhTdugqV 7yXfRx8ksUV53eKIKJ1Zb69Il2O0Fhpbf8De5C3pDLK0rKxEvXVnQu34LZmnxrd8KEcaApTF+ItE i1pBgObZY/0vbvhy743BeRf8klr/kBBMPySvM1GanV6/IUNsKBv4JmEFC67/RU+KAeoxo2O0gBOL StpId5z11hHgeyAsXLrrfY4m4+F+oBfgR0AG8vPnbIRTWaAkdgh/QN2u7GNjESdahKmfhckNGLl7 o6GmWaY9FC9SWt2JR98eAlPMl/BlW5rCBXYoDL24NFYoQNkK+IDk4U4fW+iI6/CKiywIRsPj4jYj b7+qO+63OrHyWg81R6G47ltD+1KgAcXCfPp+ZFK9zVNkMuSQVpn4Qv6Ddxg8MrzsFditFsRBi2+g lA8a65hbmqammSCPTYR2yKPZu48us53fhW6G3tyHzPQj9WciaUlV74bB+0tgiKW+Hixd/YrY1u4j xGk= =C9ZG -----END PGP SIGNATURE-----