In my instance the need for the filter changes were raw and historygenerator parts of the meso and bootstrap skin extensions to weewx.
On Monday, 27 November 2017 01:13:27 UTC+2, gjr80 wrote: > > Ok, poor choice of words on my behalf. I am not advocating users changing > the actual filter script, as I have pointed out this will lead to problems. > Rather users need to have a mechanism to customise the logwatch filter, > similar in broad concept to how users can use search list extensions to add > to the available tags in a report. > > Gary > > On Monday, 27 November 2017 05:25:25 UTC+10, vince wrote: >> >> On Sunday, November 26, 2017 at 3:26:19 AM UTC-8, gjr80 wrote: >>> >>> So I guess the issue is making sure there is a means of users being able >>> to customise the logwatch script such that the user customisations are >>> retained across upgrades >> >> >> >> I don't think you should even attempt to support that. If the user >> essentially hacks on the logwatch script, they are doing so at their own >> risk. >> > -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
