one final note about that PKGBUILD On Wed, 24 Jul 2024 08:48:03 +0300 Wael wrote: > Note: Initially I was somewhat hesitant about the situation with the > libraries as one of them isn't tagged. I've since spoken to the > developer behind the project and it was clarified to me that the > un-tagged is tightly and closely developed to nncmpp and as such there > shouldn't be an issue. > In any case, the full tarballs now provided should also include > compatible versions. > There might still be an argument down the road of splitting the tagged
the fact that the libraries are not versioned, but their versions are tightly-coupled to each main program version, that is the fundamental issue to correct - publishing a complete source-ball is one way to correct it, as far as distribution is concerned; but there is a better and easier way to correct it ideally, the upstream would simply add git tags to those commits of the libraries - the forge would automatically present them as "releases"; and the upstream would not need to link them as git sub-modules - they could simply be noted as build dependencies in the README - but that is not a big concern, unless distros wanted to package those libraries separately i understand your motivation for asking the upstream to package all sub-projects into a single tarball; and that was awesome that the upstream did it - it is more work for the upstream though (proper release maintenance always is) - a complete source-ball is convenient; but the practical advantage to you is small - is not necessary for parabola to avoid using sourcing from VCS the reason is, the upstream VCS front-end can make tarballs of any commit on-the-fly - you could add those tarballs to the source=() array, then in prepare(), copy or symlink them into their expected location in the main code-base so the upstream does not need to do anything differently than they were doing before you asked for a complete source-ball - because the code is distributed by a forge, the complete source-ball is saving you only from manually identifying those two commit hashes of the libraries _______________________________________________ Dev mailing list Dev@lists.parabola.nu https://lists.parabola.nu/mailman/listinfo/dev
