Best practices for patch management on RPM based packages?

2011-09-06 Thread Richard Shaw
Most of the packages I work with have very few patches so it's not all that difficult, but there are a couple of packages I'm working with that have a lot of patches and one of them has a very active upstream (which is a good thing!) but that also means that the patches need frequent adjustment. I

Re: Best practices for patch management on RPM based packages?

2011-09-06 Thread Panu Matilainen
On 09/06/2011 05:16 PM, Richard Shaw wrote: > Most of the packages I work with have very few patches so it's not all > that difficult, but there are a couple of packages I'm working with > that have a lot of patches and one of them has a very active upstream > (which is a good thing!) but that also

Re: Best practices for patch management on RPM based packages?

2011-09-06 Thread Paul Wouters
On Tue, 6 Sep 2011, Richard Shaw wrote: > Most of the packages I work with have very few patches so it's not all > that difficult, but there are a couple of packages I'm working with > that have a lot of patches and one of them has a very active upstream > (which is a good thing!) but that also me

Re: Best practices for patch management on RPM based packages?

2011-09-06 Thread Toshio Kuratomi
On Tue, Sep 06, 2011 at 09:16:44AM -0500, Richard Shaw wrote: > Most of the packages I work with have very few patches so it's not all > that difficult, but there are a couple of packages I'm working with > that have a lot of patches and one of them has a very active upstream > (which is a good thi

Re: Best practices for patch management on RPM based packages?

2011-09-06 Thread Adam Jackson
On Tue, 2011-09-06 at 09:16 -0500, Richard Shaw wrote: > Most of the packages I work with have very few patches so it's not all > that difficult, but there are a couple of packages I'm working with > that have a lot of patches and one of them has a very active upstream > (which is a good thing!) bu

Re: Best practices for patch management on RPM based packages?

2011-09-06 Thread Richard Shaw
Thanks for the suggestions so far. I think quilt works ok with Fedora scm (or RPM Fusion cvs) since everything lives in one directory. I'm trying to get it to place nice with rpmbuild because not everything I'm working on is in Fedora or RPM Fusion. Also, I like to use rpmbuild as kind of a sandb

Re: Best practices for patch management on RPM based packages?

2011-09-06 Thread Matej Cepl
Dne 6.9.2011 16:29, Panu Matilainen napsal(a): >> I like the idea of quilt but I can't seem to find the magic recipe to >> get it to integrate with rpmbuild. What's wrong with quilt setup specname.spec ? Best, Matěj -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproje

Re: Best practices for patch management on RPM based packages?

2011-09-06 Thread Panu Matilainen
On 09/06/2011 09:53 PM, Matej Cepl wrote: > Dne 6.9.2011 16:29, Panu Matilainen napsal(a): >>> I like the idea of quilt but I can't seem to find the magic recipe to >>> get it to integrate with rpmbuild. Please mind your quotes, I didn't write the above. > What's wrong with > > quilt setup specna

Re: Best practices for patch management on RPM based packages?

2011-09-06 Thread Enrico Scholz
Richard Shaw writes: > I like the idea of quilt but I can't seem to find the magic recipe to > get it to integrate with rpmbuild. I use an %apply macro in ways like | %apply -n4 -p1 which is equivalent to | %patch4 -p1 on ordinary hosts. But defining this macro as | %apply(p:n:b:)

Re: Best practices for patch management on RPM based packages?

2011-09-06 Thread Richard Shaw
On Tue, Sep 6, 2011 at 2:23 PM, Panu Matilainen wrote: > On 09/06/2011 09:53 PM, Matej Cepl wrote: >> Dne 6.9.2011 16:29, Panu Matilainen napsal(a): I like the idea of quilt but I can't seem to find the magic recipe to get it to integrate with rpmbuild. > > Please mind your quotes, I did

Re: Best practices for patch management on RPM based packages?

2011-09-06 Thread Richard Shaw
I think I've gotten over the first hurdle. I ended up using the following command: $ quilt setup -d rpmbuild/BUILD --sourcedir rpmbuild/SOURCES/ rpmbuild/SPECS/.spec Now that doesn't fix the persistence issue since anything in BUILD/ will be deleted on the next run of rpmbuild... In this case 'pa

Re: Best practices for patch management on RPM based packages?

2011-09-06 Thread Richard Shaw
On Tue, Sep 6, 2011 at 3:17 PM, Richard Shaw wrote: > I think I've gotten over the first hurdle. I ended up using the > following command: > > $ quilt setup -d rpmbuild/BUILD --sourcedir rpmbuild/SOURCES/ > rpmbuild/SPECS/.spec Well not so fast... I don't know why, but even though I'm telling it

Re: Best practices for patch management on RPM based packages?

2011-09-06 Thread Mathieu Bridon
On Tue, 2011-09-06 at 15:04 -0500, Richard Shaw wrote: > > On 09/06/2011 09:53 PM, Matej Cepl wrote: > >> What's wrong with > >> > >> quilt setup specname.spec > > Because rpmbuild segregates everything, quilt doesn't seem to know how > to handle that. > > When you create the directory tree for r

Re: Best practices for patch management on RPM based packages?

2011-09-06 Thread Jesse Keating
On Sep 6, 2011, at 6:52 PM, Mathieu Bridon wrote: > On Tue, 2011-09-06 at 15:04 -0500, Richard Shaw wrote: >>> On 09/06/2011 09:53 PM, Matej Cepl wrote: What's wrong with quilt setup specname.spec >> >> Because rpmbuild segregates everything, quilt doesn't seem to know how >> to ha