On Wed, 2008-07-23 at 22:27 -0400, Jesus Rodriguez wrote:
On Wed, Jul 23, 2008 at 09:50:13PM -0400, Mike McLean wrote:
> Jesus M. Rodriguez wrote:
>> So am I correct in my assumption that koji expects the scm
>> repository to house a single package?
> Yes. Furthermore, koji assumes that the simple command 'make srpm'
> issued from the checkout will create a single source rpm. There is not
> enough information passed to koji for it to handle anything otherwise.
> In your SCM layout with multiple packages, how do you generate the
> different srpms? Is there a real reason that they are all in one module?
We generate different srpms with the Makefile that exists in each
subdirectory. For example, if you want an srpm for the web module
cd spacewalk.git/web; make srpm
Want one for the java code, then cd spacewalk.git/java.
With SVN it seems completely doable because I could give the
path to repo/spacewalk/java and have koji checkout just that
directory. Seems to be a limitation of GIT in this case
(or we're using it wrong) :)
Well, git was intentionally written to be basically a state machine of
the entire project. So, housing more than one project in a single git
repo isn't wrong, but it does tie your various projects together at the
state machine level. This is why you can't checkout just one
subdirectory from git, you have to grab the entire project. I think I
heard mumblings of someone wanting to make subprojects work nicely in
git, but I haven't heard if it ever got off the ground.
Regardless though, koji won't work with what your current SCM layout
without modification to the koji code.
Doug Ledford <dledford(a)redhat.com>
GPG KeyID: CFBFF194
Infiniband specific RPMs available at