On Tue, Jun 6, 2017 at 7:14 AM, Vít Ondruch <vondruch@xxxxxxxxxx> wrote: > So what would be your workflow here? You would start update of the > package by "fedpkg upload" to upload the new tarball and let dist-git to > explode it? And what would be next? My ideal workflow would be to use pagure (repo with exploded source) just like I use github/gitlab/bitbucket these days. Hence if I am owner I commit directly or perhaps I file pull-request against the package source. Then once commit is merged, package maintainer tells koji to build the package. Note that Koji *has* support to build directly from git repo referenced in your spec. We just don't use this feature in Fedora, because up until pagure came along there was no suitable code hosting/collaboration platform available to Fedora package maintainers. > > I thought that the exploded tree would be more passive, i.e. it would > mirror just the basic tarball, possibly each Koji build would result in > some release branch containing also the applied patches, but it seems > you want to use it more actively .... Not only more actively, I would like to use it almost exclusively. In my opinion move into this direction would be hands down the best change for package maintainers in years. Also I personally think such possibility is also necessary if Fedora wants to attract new contributors in era of Github. Because let's be honest, plain dist-git (spec+patches) is just terrible experience compared to what people are used to upstream. Just my 0.02... Michal _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
