-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi Folks,
Few questions/points about the Koji git workflow.
* We have different way to build RPMs in Koji
1/ From source rpm ; you can build any source RPM you submit to the system. e.g: koji build storage7-el7 myNVR.src.rpm
2/ From git ; you send koji an URL + #commit e.g: koji build storage7-el7 "git+https://git.centos.org/git/rpms/tzdata.git?#e24d98" (For that I need to patch kojid so it supports git.c.o schema i.e not having a .spec file directly at / in git)
The proposal is to have both solutions supported but : - - Building from src.rpm will be only trigger by git.c.o and will require special permission. - - SIG users can build their packages but the code need to be in git.c.o (traceability).
What do you think ? Is there a use case where building from src.rpm would be required ?
* Now speaking about the SIG what is the plan for the branches naming ? c${MAJOR}-${SIGNAME} ? I will need to generate this string to checkout the correct branch in git.
Thanks to Fabian the koji installation is being puppetized, and we hope to have some SIG beta-users on board soon.
- -- Thomas
On 07/29/2014 03:59 PM, Thomas Oulevey wrote:
The proposal is to have both solutions supported but :
- Building from src.rpm will be only trigger by git.c.o and will
require special permission.
- SIG users can build their packages but the code need to be in
git.c.o (traceability).
What do you think ? Is there a use case where building from src.rpm would be required ?
Yes, there is. It's quite often that I do scratch builds in Fedora using locally ( as in "on my workstation") generated src.rpm. Usually (but not always ) this is the case when I do a fedpkg clone from a Fedora release and try to rebuild on an EPEL target.
wolfy
On Tue, 2014-07-29 at 14:59 +0200, Thomas Oulevey wrote:
The proposal is to have both solutions supported but :
- Building from src.rpm will be only trigger by git.c.o and will
require special permission.
- SIG users can build their packages but the code need to be in
git.c.o (traceability).
What do you think ? Is there a use case where building from src.rpm would be required ?
I'm thinking about my server-manager web application, that comes bundled with the particular versions of some external libraries: the package needs more than one Source tarballs listed in the spec file.
How they will be issued to the build system?
Does the src.rpm solution fit this case?
On 07/30/2014 10:41 AM, Davide Principi wrote:
On Tue, 2014-07-29 at 14:59 +0200, Thomas Oulevey wrote:
The proposal is to have both solutions supported but :
- Building from src.rpm will be only trigger by git.c.o and will
require special permission.
- SIG users can build their packages but the code need to be in
git.c.o (traceability).
What do you think ? Is there a use case where building from src.rpm would be required ?
I'm thinking about my server-manager web application, that comes bundled with the particular versions of some external libraries: the package needs more than one Source tarballs listed in the spec file.
How they will be issued to the build system?
That's an easy one. You just list Source0, Source1... Sourcen etc and koji does the rest
Does the src.rpm solution fit this case?
not necessarily. the situation is in no way different to the case where you have a single source. the only requirement is that all source files must be in git.c.o ( or a lookaside cache.. )
-
Davide Principi -
Manuel Wolfshant -
Thomas Oulevey