-- Gwyn Ciesla she/her/hers ------------------------------------------------ in your fear, seek only peace in your fear, seek only love -d. bowie Sent with ProtonMail Secure Email. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Wednesday, January 27, 2021 11:16 AM, Vít Ondruch <vondruch@xxxxxxxxxx> wrote: > Dne 27. 01. 21 v 18:03 Gwyn Ciesla via devel napsal(a): > > > -- > > Gwyn Ciesla > > she/her/hers > > > > ---------------------------- > > > > in your fear, seek only peace > > in your fear, seek only love > > -d. bowie > > Sent with ProtonMail Secure Email. > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ > > On Wednesday, January 27, 2021 11:00 AM, Vít Ondruch vondruch@xxxxxxxxxx wrote: > > > > > Dne 27. 01. 21 v 17:38 Daniel P. Berrangé napsal(a): > > > > > > > On Wed, Jan 27, 2021 at 05:17:24PM +0100, Vít Ondruch wrote: > > > > > > > > > Hi, > > > > > I wonder, what would be the sentiment if I proposed to deprecated the > > > > > `fedpkg local` command. I don't think it should be used. Mock should be the > > > > > preferred way. Would there be anybody really missing this functionality? > > > > > While I understand that mock has the benefit of providing a well > > > > > defined build environment, with less scope for things going wrong, > > > > > that just isn't important to me most of the time. In fact I often > > > > > want to build against what I have installed locally, explicitly > > > > > not against what mock has in its build root. > > > > > So overall "fedpkg local" has the benefit that it is much faster > > > > > to run the build and simpler to get it to build what I want. > > > > > While there is certainly penalty in using mock, running repetitive > > > > > builds together with `--no-clean` option will hardly slow you down. Just > > > > > a few numbers. > > > > > > 1. Starging from scratch after `mock --scrub=all`, every package have to > > > be downloaded and installed: > > > $ time mock -r fedora-rawhide-x86_64 rubygem-net-ssh-5.2.0-2.fc34.src.rpm > > > ... snip ... > > > real 0m47,188s > > > user 0m41,841s > > > sys 0m6,040s > > > > > > > > > 2. With warm cache, only the BRs are installed, running right after the > > > previous build: > > > $ time mock -r fedora-rawhide-x86_64 rubygem-net-ssh-5.2.0-2.fc34.src.rpm > > > ... snip ... > > > real 0m13,182s > > > user 0m9,885s > > > sys 0m2,701s > > > > > > 3. Without build root cleanup: > > > $ time mock -r fedora-rawhide-x86_64 rubygem-net-ssh-5.2.0-2.fc34.src.rpm -n > > > ... snip ... > > > real 0m7,563s > > > user 0m6,139s > > > sys 0m1,194s > > > > > > > > > I think this is acceptable penalty for keeping my system unpolluted and > > > giving me easy opportunity to start from scratch if I messed up or if my > > > dependencies have changed or what not. > > > > Great! And you can keep doing that! That's a good thing to have. fedpkg local also works without network access, like on a train, if you have all your BuildRequires in place. > > No difference here. Mock works fine without network, if you have your > caches populated. True. Question; What problem would be solved by removing fedpkg local that isn't addressed by documentation? > 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
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ 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
