[opensuse-packaging] need help writing specfile for OBS
I hope i'm on the right ML with my problem. Please forgive me if not. I need to write a specfile for use with openSUSE Build Service and have problems with the source fetching and versioning part. The sources for the project are hosted at GitHub and i like to build a snapshot from the HEAD of the master branch. So the package version should contain a (generated) numerical part which increments on each build and the (short) hash of the latest commit. I believe that the tar_scm, set_version and recompress services are needed here. But i could not find a good tutorial or example for this. Thanx for help, Steffen -- DResearch Fahrzeugelektronik GmbH Otto-Schmirgal-Str. 3, 10319 Berlin, Germany Tel: +49 30 515932-237 mailto:sledz@dresearch-fe.de Fax: +49 30 515932-299 Geschäftsführer: Dr. Michael Weber, Werner Mögle; Amtsgericht Berlin Charlottenburg; HRB 130120 B; Ust.-IDNr. DE273952058 -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
Steffen Sledz <sledz@dresearch-fe.de> Wed, 26 Nov 2014 16:46:48 +0300:
I hope i'm on the right ML with my problem. Please forgive me if not.
I need to write a specfile for use with openSUSE Build Service and have problems with the source fetching and versioning part.
The sources for the project are hosted at GitHub and i like to build a snapshot from the HEAD of the master branch.
So the package version should contain a (generated) numerical part which increments on each build and the (short) hash of the latest commit.
I believe that the tar_scm, set_version and recompress services are needed here. But i could not find a good tutorial or example for this.
Thanx for help, Steffen
Hello! https://build.opensuse.org/package/view_file/home:Reki:leechcraft:masterbran... is OK for me. Usually I just update "%define LEECHCRAFT_VERSION " from `git describe` and it triggers archive creating and builds starting. Any questions? -- Best regards, Dmitriy DA(P).DarkneSS Perlow @ Linux x64 -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
Am 26.11.2014 um 16:39 schrieb Dmitriy Perlow:
Steffen Sledz <sledz@dresearch-fe.de> Wed, 26 Nov 2014 16:46:48 +0300:
I hope i'm on the right ML with my problem. Please forgive me if not.
I need to write a specfile for use with openSUSE Build Service and have problems with the source fetching and versioning part.
The sources for the project are hosted at GitHub and i like to build a snapshot from the HEAD of the master branch.
So the package version should contain a (generated) numerical part which increments on each build and the (short) hash of the latest commit.
I believe that the tar_scm, set_version and recompress services are needed here. But i could not find a good tutorial or example for this.
https://build.opensuse.org/package/view_file/home:Reki:leechcraft:masterbran... is OK for me. Usually I just update "%define LEECHCRAFT_VERSION " from `git describe` and it triggers archive creating and builds starting.
Any questions?
Thanx. All the examples were very helpful. The rpm build is working now. :) Now i try the next step: deb packages I've the same problem here. What should i write to the Source: and Files: fields of the dsc file in case of source archives generated by tar_scm and recompress. Steffen -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
Steffen Sledz <sledz@dresearch-fe.de> Thu, 27 Nov 2014 20:42:21 +0300:
Am 26.11.2014 um 16:39 schrieb Dmitriy Perlow:
Steffen Sledz <sledz@dresearch-fe.de> Wed, 26 Nov 2014 16:46:48 +0300:
I hope i'm on the right ML with my problem. Please forgive me if not.
I need to write a specfile for use with openSUSE Build Service and have problems with the source fetching and versioning part.
The sources for the project are hosted at GitHub and i like to build a snapshot from the HEAD of the master branch.
So the package version should contain a (generated) numerical part which increments on each build and the (short) hash of the latest commit.
I believe that the tar_scm, set_version and recompress services are needed here. But i could not find a good tutorial or example for this.
https://build.opensuse.org/package/view_file/home:Reki:leechcraft:masterbran... is OK for me. Usually I just update "%define LEECHCRAFT_VERSION " from `git describe` and it triggers archive creating and builds starting.
Any questions?
Thanx. All the examples were very helpful. The rpm build is working now. :)
Now i try the next step: deb packages
I've the same problem here. What should i write to the Source: and Files: fields of the dsc file in case of source archives generated by tar_scm and recompress.
Steffen
https://build.opensuse.org/package/show/home:DarkSS:deb/qlivebittorrent Feel free to write nothing special to dsc's Version&Files. -- Best regards, Dmitriy DA(P).DarkneSS Perlow @ Linux x64 -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
2014-11-26 14:46 GMT+01:00 Steffen Sledz <sledz@dresearch-fe.de>:
I hope i'm on the right ML with my problem. Please forgive me if not.
I need to write a specfile for use with openSUSE Build Service and have problems with the source fetching and versioning part.
The sources for the project are hosted at GitHub and i like to build a snapshot from the HEAD of the master branch.
So the package version should contain a (generated) numerical part which increments on each build and the (short) hash of the latest commit.
I believe that the tar_scm, set_version and recompress services are needed here. But i could not find a good tutorial or example for this.
Take a look here: https://en.opensuse.org/openSUSE:Build_Service_private_instance_software_liv... Note, that this is documentation about OBS private instance, so you will not need to do everything there when using build.o.o. But services are well documented there. Ondrej -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
participants (3)
-
Dmitriy Perlow -
Ondrej Holecek -
Steffen Sledz