On Sunday, 19 May 2019 16:44:16 CEST Brian (bex) Exelbierd wrote: > On Sun, May 19, 2019 at 2:23 PM Robert-André Mauchin <zebob.m@xxxxxxxxx> > wrote: > > > > > > Hello, > > > > > > > > golang(github.com/jacobsa/ogletest) is only needed for tests by oglemock. > > So you just need to bootstrap oglemock with tests disabled then build > > ogletest then rebuild oglemock unboostrapped. > > > Thank you for the quick reply! > > This makes sense, and I had a feeling this would be the case. > > I appreciate the spec files you sent in your second email. > > I am not seeing a document that explains how I submit the entire app > for build/update. > > I know I can do `fedpkg build` in the various repos, but how do I get > them to all see each other? in other words, I need oglemock to be > built without tests, build ogletest, then rebuild oglemock and then > build the other dependencies then build the actual app and have this > happen when they all have access to the various dependent files. I > have not had to package something this complex before. > > I don't see a section in the Packaging guide that addresses the > command sequence for this. Perhaps it is buried in the wiki on a page > that isn't obvious to me? > > Can you point me at a document? Not sure I understand the problem. You build each package independently as usual, doing `fedpkg build` in each repo. Once the package is build in Rawhide, it is available to others (might have a delay up to 20mn). For the bootstrap, you just switch for bcond_without to bcond_with bootstrap, then commit and rebuild. No need to bump the Release, we have ~bootstrap autodetected for Release. If you build in branched, you do fedpkg build fedpkg update Then do a buildroot override so that the build is available to other: fedpkg override create --duration 15 --notes "Buildroot override for X" Then wait repo for the build: koji wait-repo f30-build --build=foo-1.1.1-1.fc30 And then continue with your next builds > > I am assuming I can just submit the package and all dependencies in > teh same BZ for review so I am more thinking about the build stage. > No. 1 package = 1 review. You'll need a Review Request for each deps. _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
