On Mon, Feb 26, 2018 at 10:49 AM, Mattia Verga <mattia.verga@xxxxxxxx> wrote:
Il 26/02/2018 09:25, Artur Iwicki ha scritto:
As far as I can see, previously this wasn't an issue, since joost (fpc & lazarus maintainer) didn't usually perform FPC & Lazarus updates, preferring to build new versions in Rawhide / early branched and have them roll out with the next Fedora release.I would say that Joost was too conservative (very poor communication and very long time between the release of a FPC or Lazarus stable release and when they were built in Fedora), but now we're on the other side: I would have expected FPC 3.0.4 and Lazarus 1.8.0 to be released only on Rawhide and F28, not also in F27 and F26.
_______________________________________________
Since many packages depends on FPC and Lazarus, pushing new releases on older Fedora branches throws in some risks about breaking dependent package builds. If this is not needed to fix some urgent bug, it's better not to do so.
I have to disagree a bit. If it's a major or minor update then we need to look at the pros vs cons, but a patch level update (assuming upstream is good about not making major ABI breaking changes) should be built for all released Fedora versions.
In the case of my package, cqrlog, they frequently use the latest modules so I would prefer they be available.
One option would be to do builds of both fpc and lazarus and submit buildroot overrides and let the maintainers of the other packages attempt to do scratch builds against them and report success or failure. Announcing on the devel list would take the least amount of effort but it would be nice to email all known maintainers of such packages using <package>-owner@xxxxxxxxxxxxxxxxx if there's a way to reasonably semi-automate it.
Thanks,
Richard
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
