On 09/02/18 23:46, Kevin Kofler wrote: > David Sommerseth wrote: >> Doesn't 'fedpkg mockbuild' resolve those test builds? To my knowledge, >> this is fairly close to what koji does under the hood. Then you'll have >> everything tested locally, git tree can be cleaned up and be in a >> reasonable shape before being pushed out. > > I'm surely not going to build those packages on my computer, that's what we > have Koji for! I doubt Koji was primarily built for "does this work?"-builds. It exists to build proper packages targeting Fedora repositories. >> If you want to make koji run the build, you can also use 'fedpkg build >> --scratch' and provide an SRPM (generated by 'fedpkg srpm'). This >> shouldn't need to be git pushed either to work. > > Then I have to waste a build (which wastes my time and Koji's resources) > because I'll have to build the last attempt (the one that ends up > succeeding) again as an official build later. It also takes extra time to > build and upload the SRPM compared to letting Koji compose it from dist-git, > which for a large package like qt5-qtwebengine is not negligible either. (I > have only so much upload speed on this asymmetric cable broadband > connection.) To me this is backwards and is lacking some logic. If you push things which does not build properly, you also waste a build. And if your build works but there are other non-critical typos, you still waste a build when you correct that. Testing builds is critical to ensure your .spec file is properly setup. If it happens locally or in a pre-built SRPM sent to koji, is not really that important. Here people use what is most convenient to them. To avoid bandwidth issues I know people (including myself) uses external hosts with a decent Internet link (you might even get access to some free resources, especially if targeting special platforms - like the Open Power Hub if doing POWER8 related stuff [1]). Use sshfs or similar approaches to a remote server which is used to update a .spec file from your local host and then use ssh on that host and do the heavy-lifting there directly. The bandwidth for a ssh connection is negligible compared to uploading large srpm packages. Plus the koji upload goes fairly fast. Or you could get a more reasonable and decent Internet connection at home/work with a better bandwidth. To me these complaints sounds more like insisting on not adopting to the reality. Getting all your expectations covered and expect the Fedora tooling around to adopt to your expectations just sounds backwards to me. [1] <https://research.redhat.com/powerlinux-openpower-development-hosting/> -- kind regards, David Sommerseth
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
