Messages

Hi Franco,

Thanks for your speedy response.  I understand it can be difficult and do not envy you guys for the work you put in etc but as an Admin I think of such scenarios :)

In part why I raised this request/question is that in some cases (not always) for example, you could have a pluggin Snort - Rev A installed and working fine, Rev B is released and you upgrade to that, find out its broken or "other issues" you then have to wait for the author the create/build Rev C - an unknown amount of time which could lead to a system critical feature not being available.

I was not suggesting that all revisions be kept or made available  but I think that 2 or 3 seems like a good number anyhow for roll back purposes.

Again 1 reason why I suggested this is from this exact experience on a different platform after upgrading a package/addon/pluggin.

Cheers

Hi all,

I was reading this thread about the possible design of making addons available to opnsense.

https://forum.opnsense.org/index.php?topic=13.0

As the thread was so old I though I'd start a  new one here with I think a very valid suggestion.  I'm not a programmer or package maintainer just your normal run of the mill Admin.

I think that opnsense should look into is to keeping previous verisions of packages to be available to install.

Sadly with pfsense if you upgrade a package and it kills your whole appliance or the package does not work as expected your are basically done.  Their is no roll back facility to the previous package that most likely was still operational.

Additionally if you have not upgraded a package for whatever reason and you re-install or recover your appliance (or wish to roll out multiple appliances) with a backup config you are forced to download the latest package again.

Just my thoughts :)

Cheers