I don't fully understand your problem
Ok, I'm probably too vague.
I'm talking about restoring a "build environment", with old versions of packages, used for in an old release-tag compilation.
nb: I limit myself to the problem of restoring third-party packages (which come from GitHub, SourceForge, ...), each of these third-party code sources, are stored in their local SVN repositories, on my computer.
The versions of Lazarus and FCP being constant!my gut tells me you need to add the relevant lazarus package configuration to SVN too. > So that you restore it, version data inclusive.
Yes, I'm talking about that: let's say I saved, in the "release1.0.0" SVN-tag, everything I've used: all versioned third-party source codes (run-time and design-time *.lpk, configuration files, *.lpl files, packagefiles.xml, miscellaneousoption.xml, packegelinks.xml, etc).
Time is passing.
A bug is found in "release1.0.0", so I check-out "release1.0.0". Then, in my working copy, I have the source code of the "release1.0.0". I am happy.
==>
Now, I wonder if it's theoretically possible, to write a *.sh or *.bat script around the tool Lazbuild (that seems to be made for that), which could allow me to *automate* in this way:1°) the deletion from the Lazarus palette, of the components used too by "release1.0.0", but which are not necessarily in their correct version (it's probably a little paranoid);
2°) the recompilation of run-time *.lpk used by "release1.0.0";
3°) the recompilation of desig-time *.lpk used by "release1.0.0";
4°) the recompilation of Lazarus itself, in order to have the IDE with the correct versions of the visual components in their pallets, components recompiled in 3°)?