Re: Simultaneous Fedora and upstream git usage
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/11/2010 08:30 AM, Andy Shevchenko wrote: Every one who is use a git everyday knows that it has support of joining several repositories in one local repository (especially if it has a common base). I would use such feature for packages hosted in git repositories. So, the idea is to keep 2-in-1: - Fedora's git as a holder and main repository - upstream/* branches for an upstream sources (real package sources) Advantages are in keeping things together and simplify maintaining packages in Fedora with upstreamed patches (commits). It also reminds the Debian's scheme where the repository contains two branches and two kind of tags accordingly. Any suggestions or improvements to this scheme? I've been meaning to explore this path a bit, and add tooling in fedpkg to set it up initially. My first feeling is that it'd be a configuration that lives on your workstation, in your clone, not something pushed up to pkgs.fp.o. It would certainly help in getting patches to/from upstream, and help when we start exploring automated patch management within packages. - -- Jesse Keating Fedora -- Freedom² is a feature! identi.ca: http://identi.ca/jkeating -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iEYEARECAAYFAkyOoy0ACgkQ4v2HLvE71NWQXwCghuLl+PV0iRTIYzD+oLzvvAs9 LtwAn0QypwdUHtGocsVmi172HiyNwB2y =zin2 -END PGP SIGNATURE- -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Simultaneous Fedora and upstream git usage
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/11/2010 04:35 PM, Ben Boeckel wrote: What I remember from FUDCon Toronto was that fedpkg could download the tarball, explode it into /tmp or something, do a `git init; git commit -a -m Tarball` and then there'd be some way to export patches on top of this commit back into the Fedora repository and get the PatchXX: and %patchXX lines in the spec easily. Allowing maintainers to push full upstream repositories into the Fedora repositories isn't something I'd recommend doing. It also makes maintaining git-backed upstreams different than other version controls (imagine checking out Qt's repository to do a one liner change to the spec file). This is something slightly different than what Andy was talking about, and it is still on the horizon. - -- Jesse Keating Fedora -- Freedom² is a feature! identi.ca: http://identi.ca/jkeating -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iEYEARECAAYFAkyOo4YACgkQ4v2HLvE71NVc6QCfQAFMP261unU7uf8Ace/XJGqk SeAAoKA8ThW+Aykhv4DZckXUVtgYsVcx =1SIV -END PGP SIGNATURE- -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Simultaneous Fedora and upstream git usage
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/12/2010 08:55 AM, Ben Boeckel wrote: Ah. I remember some talk about getting a VCS tag in rpm. This is where it'd belong IMO. Maybe fedpkg can implement it until rpm gets it? The rpm spec could have a vcs tag, now. RPM just doesn't do anything with it. fedpkg can be made to look for such a tag when you ask it to create an upstream for that project, and if it doesn't find one in the spec prompt the user for one, or just fail and ask that the user supply one with whatever command they were running. - -- Jesse Keating Fedora -- Freedom² is a feature! identi.ca: http://identi.ca/jkeating -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iEYEARECAAYFAkyOpEkACgkQ4v2HLvE71NWZLACgpLrfF3x44gWBpHUbfQAi/5qQ UQgAoLdPxEq73i02vtWg+haIoMfLUZxS =Omt+ -END PGP SIGNATURE- -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Simultaneous Fedora and upstream git usage
On Sun, Sep 12, 2010 at 2:35 AM, Ben Boeckel maths...@gmail.com wrote: What I remember from FUDCon Toronto was that fedpkg could download the tarball, explode it into /tmp or something, do a `git init; git commit -a -m Tarball` and then there'd be some way to export patches on top of this commit back into the Fedora repository and get the PatchXX: and %patchXX lines in the spec easily. It's not what I would like to discuss, but it's really useful to such sources where upstream isn't a git-backed. Allowing maintainers to push full upstream repositories into the Fedora repositories isn't something I'd recommend doing. It also makes maintaining git-backed upstreams different than other version controls (imagine checking out Qt's repository to do a one liner change to the spec file). To be more clear, a) I'm talking about pull upstream to the _local_ repository; b) of course the feature should be optional, IOW fedpkg might have support of pulling remote sources from VCS (actually good to have VCS-URL inside spec); c) ... may be smth. else what I miss ... -- With Best Regards, Andy Shevchenko -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Simultaneous Fedora and upstream git usage
In article aanlktiml0uiaz825j_angmgn7e--bye2dsepm=gfy...@mail.gmail.com you wrote: To be more clear, a) I'm talking about pull upstream to the _local_ repository; b) of course the feature should be optional, IOW fedpkg might have support of pulling remote sources from VCS (actually good to have VCS-URL inside spec); c) ... may be smth. else what I miss ... Ah. I remember some talk about getting a VCS tag in rpm. This is where it'd belong IMO. Maybe fedpkg can implement it until rpm gets it? --Ben -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Simultaneous Fedora and upstream git usage
Every one who is use a git everyday knows that it has support of joining several repositories in one local repository (especially if it has a common base). I would use such feature for packages hosted in git repositories. So, the idea is to keep 2-in-1: - Fedora's git as a holder and main repository - upstream/* branches for an upstream sources (real package sources) Advantages are in keeping things together and simplify maintaining packages in Fedora with upstreamed patches (commits). It also reminds the Debian's scheme where the repository contains two branches and two kind of tags accordingly. Any suggestions or improvements to this scheme? -- With Best Regards, Andy Shevchenko -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Simultaneous Fedora and upstream git usage
On Sat, 2010-09-11 at 18:30 +0300, Andy Shevchenko wrote: Every one who is use a git everyday knows that it has support of joining several repositories in one local repository (especially if it has a common base). I would use such feature for packages hosted in git repositories. So, the idea is to keep 2-in-1: - Fedora's git as a holder and main repository - upstream/* branches for an upstream sources (real package sources) Advantages are in keeping things together and simplify maintaining packages in Fedora with upstreamed patches (commits). It also reminds the Debian's scheme where the repository contains two branches and two kind of tags accordingly. Any suggestions or improvements to this scheme? I think it's already been proposed on -devel as a logical extension of the current system. I can't recall exactly when or by who, though, sorry. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Simultaneous Fedora and upstream git usage
Adam Williamson awill...@redhat.com wrote: I think it's already been proposed on -devel as a logical extension of the current system. I can't recall exactly when or by who, though, sorry. What I remember from FUDCon Toronto was that fedpkg could download the tarball, explode it into /tmp or something, do a `git init; git commit -a -m Tarball` and then there'd be some way to export patches on top of this commit back into the Fedora repository and get the PatchXX: and %patchXX lines in the spec easily. Allowing maintainers to push full upstream repositories into the Fedora repositories isn't something I'd recommend doing. It also makes maintaining git-backed upstreams different than other version controls (imagine checking out Qt's repository to do a one liner change to the spec file). --Ben -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
