On Tue, Nov 19, 2013 at 02:32:58PM +0400, Peter Lemenkov wrote:
2013/11/19 Richard W.M. Jones <rjones(a)redhat.com>:
> Several packages are using git for patch management. eg:
>
>
http://pkgs.fedoraproject.org/cgit/erlang.git/tree/erlang.spec#n46
>
http://pkgs.fedoraproject.org/cgit/libguestfs.git/tree/libguestfs.spec?h=...
>
http://pkgs.fedoraproject.org/cgit/qemu.git/tree/
>
http://pkgs.fedoraproject.org/cgit/ocaml.git/tree/ocaml.spec#n16
>
> Some of these packages have invented home-brewed methods to generate
> the Patch lines in the spec file, eg:
I hope we'll see some progress in RPM in regards to VCS integrations
soon. Because that's the main issue with RPM and related
infrastructure nowadays.
> More importantly, all are using random git repositories to store the
> exploded tree. This makes it difficult for co-maintainers and proven
> packagers to fit in with the patch management chosen by the
> maintainer. Usually they won't have access to the git repository for
> these patches, making it difficult to add patches and near impossible
> to upgrade to a new version.
I'm using
https://git.fedorahosted.org/git/ for that. For example
erlang is stored here:
https://git.fedorahosted.org/git/erlang.git
It contains a mirror of main upstream repo and few branches with
Fedora-related patches.
Peter, is the comment in the spec file wrong? It refers to two github
repos:
http://pkgs.fedoraproject.org/cgit/erlang.git/tree/erlang.spec#n46
In any case, fedorahosted would be an improvement, but AIUI it doesn't
automatically give access to co-maintainers and proven packagers.
Rich.
--
Richard Jones, Virtualization Group, Red Hat
http://people.redhat.com/~rjones
virt-top is 'top' for virtual machines. Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.
http://people.redhat.com/~rjones/virt-top