Daryl C. W. O'Shea wrote:
Bret Miller wrote:
Yep, I suspected as much. Now I have SA in three places,
four if you
count plugins.
More if you count the modules and the commandline tools.
I just had the crazy idea that I could keep rules in one
place. Is this
beginning to look unwieldy to anyone else? (rhetorical,
don't answer).
Well -- you could if you wanted to, but then you have to do some work
to deal
with it. You can't expect a tool which works one way to do something
else without doing anything.
You could, if you set the updates directory to
/usr/share/etc/mail/spamassassin/updates or something like that to keep
it in an updates folder under your site config... I'm not exactly sure
what the thinking was in moving the updates to /var/lib instead of
keeping them with /usr/share with the original rules. I wonder why
sa-update doesn't just create a version folder under /share/spamassassin
and use that... Certainly would be less to keep track of and purge when
you install a new version.
Updates are variable... they go in /var. Anywhere else wouldn't be
following FHS.
http://www.pathname.com/fhs/
Daryl
The point is really moot. What files are in what directories doesn't
really matter. It seems the idea is that anyone reading all the
documentation, and the wiki, should be able to discern what will go
where, in what order, why, and when.
DAve
--
Three years now I've asked Google why they don't have a
logo change for Memorial Day. Why do they choose to do logos
for other non-international holidays, but nothing for
Veterans?
Maybe they forgot who made that choice possible.
