[opensuse-packaging] Tagging patches guidelines and package building patches
Hi, I'm packaging a software which needs internet connection in a test target in the Makefile, which is invoked by default. I've built a patch and submitted it upstream in order to build it on my systems (which are not connected to the internet) and on the build service. In the SPEC file, I'd like to implement the patch I made following the guidelines at: http://en.opensuse.org/openSUSE:Packaging_Patches_guidelines But I'm not sure my case is contemplated. Please note that the patch only modifies package building process (Makefile). Any suggestions? Thanks, Javier -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Le lundi 29 août 2011, à 15:04 +0200, Javier Conti a écrit :
Hi,
I'm packaging a software which needs internet connection in a test target in the Makefile, which is invoked by default. I've built a patch and submitted it upstream in order to build it on my systems (which are not connected to the internet) and on the build service.
In the SPEC file, I'd like to implement the patch I made following the guidelines at:
http://en.opensuse.org/openSUSE:Packaging_Patches_guidelines
But I'm not sure my case is contemplated. Please note that the patch only modifies package building process (Makefile).
Any suggestions?
Just use something like this: PATCH-FIX-UPSTREAM name-of-patch.patch bug-id -- Fix build system to... Vincent -- Les gens heureux ne sont pas pressés. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On 29 August 2011 15:15, Vincent Untz <vuntz@opensuse.org> wrote:
Le lundi 29 août 2011, à 15:04 +0200, Javier Conti a écrit :
Hi,
I'm packaging a software which needs internet connection in a test target in the Makefile, which is invoked by default. I've built a patch and submitted it upstream in order to build it on my systems (which are not connected to the internet) and on the build service.
In the SPEC file, I'd like to implement the patch I made following the guidelines at:
http://en.opensuse.org/openSUSE:Packaging_Patches_guidelines
But I'm not sure my case is contemplated. Please note that the patch only modifies package building process (Makefile).
Any suggestions?
Just use something like this:
PATCH-FIX-UPSTREAM name-of-patch.patch bug-id -- Fix build system to...
Thanks Vincent for the answer. I'm not shure if the bug-id upstream will be useful to openSUSE people, but I'll append the URL as a comment. Thanks, Javier
Vincent
-- Les gens heureux ne sont pas pressés. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
-- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On Monday, August 29, 2011 08:04:36 AM Javier Conti wrote:
In the SPEC file, I'd like to implement the patch I made following the guidelines at:
http://en.opensuse.org/openSUSE:Packaging_Patches_guidelines
Debian also has an elaborate patch tagging guideline that seems to address the same issues: http://dep.debian.net/deps/dep3/ Revolutionary concept: Could not you guys get togther and agree on a common format? That way package maintainers would only have to have one copy of a patch. Hey, why not just adopt debian's format? It addresses the same issues, and was created by resonably intelligent SW developers maintainers! It will probably work! Those guys maintain just as many patches and packages as you do. It was not invented here? -- Paul Elliott 1(512)837-1096 pelliott@BlackPatchPanel.com PMB 181, 11900 Metric Blvd Suite J http://www.free.blackpatchpanel.com/pme/ Austin TX 78758-3117
On 29/08/11 19:15, Paul Elliott wrote:
On Monday, August 29, 2011 08:04:36 AM Javier Conti wrote:
In the SPEC file, I'd like to implement the patch I made following the guidelines at:
http://en.opensuse.org/openSUSE:Packaging_Patches_guidelines
Debian also has an elaborate patch tagging guideline that seems to address the same issues: http://dep.debian.net/deps/dep3/
Revolutionary concept: Could not you guys get togther and agree on a common format? That way package maintainers would only have to have one copy of a patch.
Hey, why not just adopt debian's format? It addresses the same issues, and was created by resonably intelligent SW developers maintainers! It will probably work! Those guys maintain just as many patches and packages as you do.
It was not invented here?
Before entering threads uninformed and throwing around accusations, maybe you should educate yourself about the many discussions on this topic which have already happened. http://lists.opensuse.org/opensuse-packaging/2010-09/msg00014.html Regards, Tejas -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
participants (4)
-
Javier Conti
-
Paul Elliott
-
Tejas Guruswamy
-
Vincent Untz