[Bro-Dev] [JIRA] (BIT-1047) Delete old scripts before installing new ones

Jon Siwek (JIRA) jira at bro-tracker.atlassian.net
Wed Jul 31 14:09:06 PDT 2013

    [ https://bro-tracker.atlassian.net/browse/BIT-1047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13413#comment-13413 ] 

Jon Siwek commented on BIT-1047:

Yeah, I'm not too nervous about deleting previously installed scripts (ones that aren't intended to be user-modified), but I'm thinking that doesn't entirely solve things for the user -- they'll probably still get an error, it's just this time it's something like "in local.bro: can't load X: no such file" which will be more obvious than whatever it was before, but they'll still have to know that means to edit their local.bro to fix the problem.

So I've not got an argument against cleaning up stale scripts, just saying this is a more general thing that can happen with config files that users edit while meanwhile the upstream version of it changes.  More clearly indicating such situations at `make install` might help.  I'd prefer if everything were designed so configuration/customization weren't done at all by editing installed files in place, rather through additional files that may be created at predetermined locations (but which may override default settings in one of the installed config files).
> Delete old scripts before installing new ones
> ---------------------------------------------
>                 Key: BIT-1047
>                 URL: https://bro-tracker.atlassian.net/browse/BIT-1047
>             Project: Bro Issue Tracker
>          Issue Type: Improvement
>          Components: Bro
>            Reporter: Robin Sommer
>             Fix For: 2.2
> People keep having problems when they install a new Bro version 
> over the installation of an old one because scripts that have disappeared in the new version will keep sticking around from the previous installation. 
> We should simply remove the old scripts/base and scripts/policy before installing anything new. People aren't supposed to edit in there so that should be safe.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://bro-tracker.atlassian.net/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

More information about the bro-dev mailing list