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

[Jon Siwek (JIRA)]

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

Jon Siwek commented on BIT-1047:
--------------------------------

So more generally the problem is "the Bro distribution may update default settings in config files from version to version, but in the case a user has modified a config file, they're also responsible for checking the diff and doing a merge (against the distribution's new file named "<file>.example") after they've done `make install`".  Should we make the output of `make install` more clearly indicate warnings for such cases?

I'm just thinking that deleting old scripts during the `make install` process resolves the particular issue mentioned here, but there's still possibilities for other user-modified config files that are *not* bro scripts (e.g. broctl.cfg) to cause a similar issue if/when a config option were to be removed in a future version?
                
> 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