Am Wed, 13 Feb 2019 17:04:54 +0100 schrieb Olaf Hering <o...@aepfle.de>:
> To avoid such situation upfront, the submission should be done from a new > "Staging" project. This prj should contain pkgs like libx264 and libx265. And > as we learned a few hours ago, also fdk-aac and everything else that may > break compilation of direct dependencies. Once an update for these libraries > does not cause build breakage it is ready for submission to "Essentials". Now the "Staging" project exists, and I copied the admins from the four other prjs. I think everyone is welcome to be a prj maintainer in "Staging", to be able to branch into the prj and provide updates to these libs. I think the simplest way to do the suggested staging is to inherit the entire "Essentials" prj. Then individual pkgs that do change API and SONAME can be branched into "Staging" once an update is pending. When all is green in "Staging", that branched pkg can be submitted back with 'osc sr --cleanup' to really remove it again. I think there are a few pkgs in Multimedia that do link directly to libx264/5 and aac. Here a simple _link from "Staging" to the origin would be enough to do the build testing. When there is nothing in "Staging", <build> can remain disabled to save build power. Also <debuginfo> is not strictly required. There are currently some pkgs in "Essentials" that do not really belong there, nothing depends on them, they just extend the buildtime of that prj. For example all of ladspa-*, *exfat*, *roar*, the KMPs and a few others could be moved to Multimedia or Extra. I think the actual move could be as simple as 'osc sr --cleanup -m "useful commit msg" Multimedia', not sure if the <build> flags would be copied as well. Comments welcome. Olaf
pgpeoj0FV1VmO.pgp
Description: Digitale Signatur von OpenPGP
_______________________________________________ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
