On Mon, May 04, 2020 at 05:05:02PM +0200, Tomas Tomecek wrote:
For some tasks, the workflow is just fine and pretty
But for the other, it’s very gruesome - the moment you need to touch
patch files, the horror comes in. The fact that we operate with patch
files, in a git repository, is just mind-boggling to me.
I wouldn't quite call it gruesome, but maybe I've got Stockholm syndrome a
little bit. I just experienced this with a package I maintain where there
was a build failure caused by changes in glibc headers. There's an upstream
patch to fix that. The whole mechanism for pulling that patch from upstream
git and then adding it as a separate patch and changing the spec file to
apply it does seem somewhat Rube Goldbergian.
Would there be an interest within the community, as opt-in, to have
such source-git repositories created for respective dist-git
repositories? The idea is that you would work in the source-git repo
and then let packit handle synchronization with a respective dist-git
repo. Our aim is to provide the contribution experience you have in
... yeah, I'd be very interested in trying this.
Fedora Project Leader