Hi Henne, The idea of the "archiving" is that when a new OpenFOAM version appears (6-month release cycle), it is fairly common for end users to require a back-to-back comparison of two or more versions before migrating to a new version as a production standard. They might want to verify that the lift/drag or separation point doesn't change by more than a certain amount, or that mesh coverage has improved etc. So ideally we try to keep the last 3 major versions maintained and available as RPMs to allow a fixed reference point of binaries for comparison. It would be relatively simple to generate a new package and copy across the old tar, spec, changes to it, but this would necessarily trigger a new rebuild for something that already exists. I hope that explains what I'm aiming for. Cheers, /mark On 4/21/21 7:19 PM, Henne Vogelsang wrote:
On 4/21/21 10:42 AM, Mark Olesen wrote:
I would then like to "archive" the current state (eg, 2106) appropriately:
What do you want to achieve with the "archive" step?
You create a science: