Hello,
On 1 Apr 2021, at 09:31, Adolf Belka adolf.belka@ipfire.org wrote:
Hi All,
After a lot of work I have successfully built the new version of perl without any errors.
As Michael had warned, there were a huge number of packages that needed to have their rootfiles updated to reflect the change in version number that is in the directory path for many files.
I have installed the iso, that resulted from my build, into my vm testbed and everything that I tested worked fine with no hiccups.
From which version to which did you jump?
I would expect that some parts of the web UI are not compatible with newer versions of Perl.
Next thing I will do is the commits for each changed package.
My understanding is that for the common packages I only need to provide the changed rootfile in the patch but for the addons I have to update the PAK_VER number if the rootfile has changed so they will have a combination of lfs and rootfile in the patch.
Yes, please commit any changes of the LFS files and rootfiles of the same package together. We technically can probably not go back if something breaks in only one module, but this is then possible to rewiew in reasonable time.
I will make the perl change into a series of patches, the primary one for perl and each other package will have its own patch.
Yes, there will be tons of dependencies and packages might bring perl bindings (e.g. rrdtool) which will need to be touched, too.
It might even be helpful for me to push the git branch somewhere so that I do not have to pull each patch separately :)
https://wiki.ipfire.org/devel/git/pull-requests
This will mean that I will be sending a huge number of patches in to patchwork later today/tomorrow. If I should be doing this another way, because of the large number of packages in the series, let me know what I should do differently.
No, go ahead. I do not think there is a better or worse time for this :)
Thank you for putting all this time into this.
-Michael
Regards,
Adolf.
-- Sent from my laptop