[opensuse-packaging] Packaging Warpinator for openSUSE
Hello all, I am attempting to package Linux Mint's Warpinator[1] for openSUSE and have a few questions. First of all, Clem has elected to denote versions using Git tags instead of creating release tarballs. I was (unsurprisingly) unable to find any documentation on how to build an RPM in such a situation. My best guess would be to remove the '%setup' macro from '%prep' and replace it with something like git clone %{source} ${name} cd ${name} git checkout %{version} However, I'm not entirely clear on whether the '%setup' macro handles the download (and therefore I should include the git clone), or if there is some other piece of logic I need to edit (or even _can_ edit) to retrieve the source that I would then manipulate in '%prep.' Additionally, Meson is used to configure and Ninja to build/install. The wiki page on build system recipes[2] neither provided a macro for this setup nor make any mention of it, and a general search of the wiki was similarly unhelpful. However, I'd like to make sure that I have not missed any relevant documentation before I publish a specfile that calls the build commands directly, as this seems like a fairly nonstandard thing to do. Thanks in advance for your help! 1: https://github.com/linuxmint/warpinator 2: https://en.opensuse.org/openSUSE:Build_system_recipes -- Daniel Stevenson -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Tuesday 2020-07-28 19:46, Daniel Stevenson wrote:
First of all, Clem has elected to denote versions using Git tags instead of creating release tarballs.
Go to https://github.com/linuxmint/warpinator/tags , click .tar.gz. Problem solved.
I was (unsurprisingly) unable to find any documentation on how to build an RPM in such a situation. My best guess would be to remove the '%setup' macro from '%prep' and replace it with something like
git clone %{source} ${name} cd ${name} git checkout %{version}
However, I'm not entirely clear on whether the '%setup' macro handles the download
That would fall prey to network failures and unnoticed changes of source content, so automatic download is quite discouraged. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Tue, Jul 28, 2020 at 08:50:25PM +0200, Jan Engelhardt wrote:
On Tuesday 2020-07-28 19:46, Daniel Stevenson wrote:
First of all, Clem has elected to denote versions using Git tags instead of creating release tarballs.
Go to https://github.com/linuxmint/warpinator/tags , click .tar.gz. Problem solved.
I was (unsurprisingly) unable to find any documentation on how to build an RPM in such a situation. My best guess would be to remove the '%setup' macro from '%prep' and replace it with something like
git clone %{source} ${name} cd ${name} git checkout %{version}
However, I'm not entirely clear on whether the '%setup' macro handles the download
That would fall prey to network failures and unnoticed changes of source content, so automatic download is quite discouraged.
More than discouraged. AFAIK OBS builders have no Internet connectivity to prevent downloading anything as part of the package build. Apart from build reproducibility, there are obvious security concerns. Michal Kubecek -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Tuesday, July 28, 2020 3:33 PM, Michal Kubecek
On Tue, Jul 28, 2020 at 08:50:25PM +0200, Jan Engelhardt wrote:
On Tuesday 2020-07-28 19:46, Daniel Stevenson wrote:
First of all, Clem has elected to denote versions using Git tags instead of creating release tarballs.
Go to https://github.com/linuxmint/warpinator/tags , click .tar.gz. Problem solved.
I was (unsurprisingly) unable to find any documentation on how to build an RPM in such a situation. My best guess would be to remove the '%setup' macro from '%prep' and replace it with something like git clone %{source} ${name} cd ${name} git checkout %{version} However, I'm not entirely clear on whether the '%setup' macro handles the download
That would fall prey to network failures and unnoticed changes of source content, so automatic download is quite discouraged.
More than discouraged. AFAIK OBS builders have no Internet connectivity to prevent downloading anything as part of the package build. Apart from build reproducibility, there are obvious security concerns.
That makes sense now that I think about of it. Thanks, Jan, for pointing out that button; I don't know how I missed it. -- Daniel Stevenson -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
Am 28.07.20 um 19:46 schrieb Daniel Stevenson:
Additionally, Meson is used to configure and Ninja to build/install. The wiki page on build system recipes[2] neither provided a macro for this setup nor make any mention of it, and a general search of the wiki was similarly unhelpful. However, I'd like to make sure that I have not missed any relevant documentation before I publish a specfile that calls the build commands directly, as this seems like a fairly nonstandard thing to do.
Meson isn't widely used yet, so the Wiki page missing info is not unexpected. But there are macros: %build %meson [build options] %meson_build %install %meson_install You can have a look at Mesa [1], which is one of the few base packages building with Meson. Best regards, Aaron [1] https://build.opensuse.org/package/show/X11:XOrg/Mesa -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
Hi Daniel, On Tue, 2020-07-28 at 17:46 +0000, Daniel Stevenson wrote:
Hello all,
I am attempting to package Linux Mint's Warpinator[1] for openSUSE
Thanks for taking this up. I started working on this about a month back and packaged a few of its dependencies as well, but since then haven't been able to accord it much time to figure out the fixes for warpinator's build failures itself. Just mentioning this in case it helps you start, instead of starting from scratch. Packages here: https://build.opensuse.org/project/show/home:badshah400 Cheers, -- Atri Bhattacharya Tue 28 Jul 23:33:38 CEST 2020 Sent from openSUSE Tumbleweed on my laptop. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
participants (5)
-
Aaron Puchert -
Atri Bhattacharya -
Daniel Stevenson -
Jan Engelhardt -
Michal Kubecek