On Mon, Oct 7, 2019 at 4:15 PM Ankur Sinha <sanjay.ankur@xxxxxxxxx> wrote: > > Out of curiosity, what workflow do existing package maintainers user > while packaging new software? Is it `fedpkg` based with a folder for the > spec to work in? (I still use rpmbuild + mock/koji-scratch builds). > > -- > Thanks, > Regards, > Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha > Time zone: Europe/London I do the same, probably because this is how I learned to do things back when I first started packaging. I'll start by writing a spec and building it on my own system with rpmbuild -ba. In principle I could do this with mock instead, but it is just faster to build locally and not have to wait for mock to download and install the base system and all the package dependencies, especially when I'm building multiple times as I test things. (It is even worse if I try to do this with a scratch build; at least with mock I'm only waiting on my own system to download and install things). Then, once I have things working with rpmbuild, I'll make sure it builds in mock and that the dependencies are correct. So if I'm writing a new spec, it's something like this: 1. cd ~/rpmbuild/SPECS 2. make new foo.spec file (rpmdev-newspec? take an existing one and adapt it?) 3. spectool -g foo.spec -c ~/rpmbuild/SOURCES 4. dnf builddep foo.spec to install deps locally 5. rpmbuild -ba until it builds (and is guideline compliant) 6. rpmbuild -bs && mock ../SRPMS/foo*.src.rpm until it builds (and is guideline compliant) 7. Upload somewhere when it is ready for review I agree that this might not be the ideal workflow to teach new packagers, but I don't think it is terrible. Ben Rosser _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
