Re: Shared pidgin releases and vcs-pkg
On Mon, May 25, 2009 at 12:35 AM, Richard Laager rlaa...@wiktel.com wrote: On Sun, 2009-05-24 at 14:13 +0300, Felipe Contreras wrote: Optionally, each package maintainer can push their patches to this repository so that other people can easily fetch them, and perhaps even share patches between distributions! This is an interesting idea. There was talk at UDSJaunty of Ubuntu wanting to do this distro-wide. Of course, they'd want to use BZR. Some downsides and points for discussion: 1) Competing DVCSes. Unless everyone is using the same one or you have really good tools that can keep multiple different repositories in sync, a lot of the benefits are lost. From what I have seem git is the most widely used: http://git.debian.org/ http://git.fedoraproject.org/ http://git.opensuse.org/ So it makes sense to use it. Also, git-bzr and git-hg tools work pretty well. 2) In Ubuntu's case, it's more useful if Debian is doing it first. Given that's not likely to happen for every project, they were talking about needing support in BZR for splicing stuff into the previous history as upstream and/or Debian get on board. If this happens, issue #1 makes it even worse. No DVCS deals with this case right now. Splicing in stuff would generally change all the revision IDs. I'm not sure what you mean by splicing, but it sounds like git graft points: http://git-scm.org/gitwiki/GraftPoint 3) You already pointed this one out: Also, I guess some maintainers might want the tarball contents as opposed to the versioned files, that could also be versioned in the same repo. The right way here, I think, is to have your releases branch come off of trunk. Assuming you started at 2.5.5, as an example: The 2.5.5 tag/revision on the releases branch would be a child of the 2.5.5 tag on trunk, minus files we don't distribute, plus the generated files. Then 2.5.6 would be a merge between 2.5.5 on the releases branch and 2.5.6 on trunk. As far as the contents go, it would be equal to 2.5.6 on trunk, minus files we don't distribute, plus the generated files for 2.5.6. Yeah, if you need releases that's the way to go I think. A piece of cake to do in git. 4) Is this really useful? Why aren't tarballs enough? I think defining some concrete use cases would be the best way to start designing such a setup. How about these: * Upstream makes a new release and the patches need to be rebased on top of it * Upstream makes a new release and some commits need to be backported to a maintainance branch * A vulnerability is found and another distro already made a release with a patch, you want it too Another advantage is that similar distros (ubuntu-debian, fedora-opensuse) can share most of the packaging stuff (.spec, debian/*). 5) Do we really want to encourage direct sharing of patches between distros? Wouldn't we want to get them upstream ASAP if they're useful and cut a new release? Yes, that would be ideal, but in my experience upstream does not make that easy. -- Felipe Contreras ___ vcs-pkg-discuss mailing list vcs-pkg-discuss@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/vcs-pkg-discuss
Re: Shared pidgin releases and vcs-pkg
On Mon, 2009-05-25 at 01:14 +0300, Felipe Contreras wrote: On Mon, May 25, 2009 at 12:35 AM, Richard Laager rlaa...@wiktel.com wrote: 5) Do we really want to encourage direct sharing of patches between distros? Wouldn't we want to get them upstream ASAP if they're useful and cut a new release? Yes, that would be ideal, but in my experience upstream does not make that easy. From my Gentoo point of view, I prefer not to ship any patches that are not already upstream. So having some kind of Git tree isn't so useful. -- Olivier Crête tes...@gentoo.org Gentoo Developer signature.asc Description: This is a digitally signed message part ___ vcs-pkg-discuss mailing list vcs-pkg-discuss@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/vcs-pkg-discuss
Re: Shared pidgin releases and vcs-pkg
On 05/24/2009 06:14 PM, Felipe Contreras wrote: Another advantage is that similar distros (ubuntu-debian, fedora-opensuse) can share most of the packaging stuff (.spec, debian/*). Fedora and Opensuse's specs are very different, so this is not an advantage. Warren Togami wtog...@redhat.com ___ vcs-pkg-discuss mailing list vcs-pkg-discuss@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/vcs-pkg-discuss
Re: Shared pidgin releases and vcs-pkg
Le dimanche 24 mai 2009, à 18:27 -0400, Olivier Crête a écrit : On Mon, 2009-05-25 at 01:14 +0300, Felipe Contreras wrote: On Mon, May 25, 2009 at 12:35 AM, Richard Laager rlaa...@wiktel.com wrote: 5) Do we really want to encourage direct sharing of patches between distros? Wouldn't we want to get them upstream ASAP if they're useful and cut a new release? Yes, that would be ideal, but in my experience upstream does not make that easy. From my Gentoo point of view, I prefer not to ship any patches that are not already upstream. So having some kind of Git tree isn't so useful. It's more or less the same for openSUSE -- we prefer to avoid adding patches, unless really needed. That being said, having everything in git can't hurt, and it might help for patches that we might need to keep around, indeed. In the case of pidgin, we have some patches since before I started contributing to openSUSE, and I have absolutely no idea what to do with them... If people are interested in reviewing them/pushing them upstream, help is welcome. You can easily download them from http://tmp.vuntz.net/opensuse-packages/browse.py?project=GNOME:Factorypackage=pidgin Cheers, Vincent -- Les gens heureux ne sont pas pressés. ___ vcs-pkg-discuss mailing list vcs-pkg-discuss@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/vcs-pkg-discuss
Shared pidgin releases and vcs-pkg
Hello maintainers of pidgin, I have a proposal for you. Personally I do all my package maintainance in git and I find it quite useful to be able to easily merge upstream and rebase my patches. There's also the vcs-pkg[1] initiative which has interesting package maintenance workflows based on git. So this is my idea: have a repository where all the pidgin releases are available in a form so that package mantainers can quickly fetch them. Optionally, each package maintainer can push their patches to this repository so that other people can easily fetch them, and perhaps even share patches between distributions! I've been working on an exact replica of Pidgin's mtn repository. I believe the latest instance of such task is as good as it's every going to get (which is quite good :). The tool (mtn git_export) is now officially part of mtn so everyone can do the conversion themselves and the results would be identical. My proposal would be my current pidgin-clone repository. But alternatively I could create another repository where only the tagged releases are available, so the size of the repo would be much smaller. Also, I guess some maintainers might want the tarball contents as opposed to the versioned files, that could also be versioned in the same repo. So, what do you think? [1] http://vcs-pkg.org/ -- Felipe Contreras ___ vcs-pkg-discuss mailing list vcs-pkg-discuss@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/vcs-pkg-discuss
