Re: Proposal to deprecated `fedpkg local`

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




Dne 27. 01. 21 v 18:53 Petr Menšík napsal(a):
Hi,

This would describe my usual workflow as well. fedpkg local is great for
checking soname did not change, patches apply, to debugging why my test
suites fail and how they behave. mock usual does not have even vim

You have vim on your host with your configuration, why would you need it in mock?


, let
alone gdb or something better.


GDB works in mock just fine.

Vít



In other words, i use fedpkg local a lot and would miss it much. I
understand what mockbuild is for, but for any iterative improvements
done to my package, fedpkg local is much better. Don't remove it,
please. Especially in bind, which includes latex documentation building,
are installed dependencies slowing one iteration significantly.

On 1/27/21 5:43 PM, Daniel P. Berrangé wrote:
On Wed, Jan 27, 2021 at 05:27:12PM +0100, Fabio Valentini wrote:
On Wed, Jan 27, 2021 at 5:24 PM Gwyn Ciesla via devel
<devel@xxxxxxxxxxxxxxxxxxxxxxx> wrote:
It's needed for testing builds against versions of packages not yet in mock. I use it almost every day. Losing it would make things like testing solib bumps harder.
I've done local test builds for soname bumps and similar things lots
of times, and I've never used (or thought about using) fedpkg local
for that.
I used "mock --chain" or a combination of "mock --postinstall
--no-clean" for those builds ... which is much closer to what koji
will do with your builds, and gives every build the clean environment
it deserves >:-)
If you want to closely replicate that koji will do, then no disagreement
that use of mock is the right tool (or just a koji scratch-build). That
just isn't a requirement much of the time though.

For adhoc development and debugging of RPM spec changes/updates, mock
gets in the way and slows things down. I could easily do 10-20 "local"
runs while getting an complex change working, and then finish off with
just one or two mock build or koji scratch-build to validate it in a
pristine build root env at the end. 


Regards,
Daniel


      
_______________________________________________
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: OpenPGP_signature
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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux