https://issues.apache.org/SpamAssassin/show_bug.cgi?id=7090
--- Comment #5 from [email protected] --- Yes, but with this they wouldn't *have* to. They could do everything with one line in crontab: @daily /path/to/sa-update && /path/to/sa-compile --binpath /path/to/search (You could even add on to restart spamd on the end of that, depending on your setup.) Easy to write, easy to use, easy to remove, etc. Yes, this doesn't do anything that can't be done in other ways - it's just a convenience issue, but convenience can be important too. It's also a one-line 'this fixes your issue' for 'bug' reports like 5617 & 6736. Only downsides are that the path could be set badly - but that's the same for any *other* solution the admin uses - and code maintenance, but it's only 11 lines of code, that don't have any other interaction with the rest of the program. (I haven't looked at the test suite yet to see what might be needed there, but I can probably do a patch for that as well. The main question on that would be how thoroughly you'd want to test the regex.) Nothing prevents the admin from using a different solution to the issue of 're2c isn't in cron's path' - but I personally find the other alternatives ugly and/or awkward, and would prefer to be able to use this one, hence the request. ;) -- You are receiving this mail because: You are the assignee for the bug.
