Dne 07. 10. 19 v 16:26 Zbigniew Jędrzejewski-Szmek napsal(a): > On Mon, Oct 07, 2019 at 03:15:02PM +0100, Ankur Sinha 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). > I do: > mkcd foo (bash alias to do mkdir foo && cd foo) > git init > git remote add origin blah (literally this, otherwise fedpkg complains, *) > emacs foo.spec & > spectool -g *spec (**) > fedpkg --release master local > mock $(ls -t1r *.src.rpm|tail -n1) (literally this, so I always try to build the latest package) This ^^ is my workflow as well (although I think there is missing `touch sources` ;) ). There are two reasons: 1) I really don't want to install every dependency of every package I ever touch on my computer. I always use mock and I never use rpmbuild. That way, I am still able to keep my main system even without GCC and I have never missed it. And just FTR, I would not be able to build ruby while Ruby is installed on my system. 2) fedpkg would not be needed if rpmbuild would be sanely able to do something like `fedpkg --release master srpm` but even so basic think requires either shuffling with files on FS or specifying million of working directories. I really don't understand why this was never improved. Vít _______________________________________________ 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
