The modifications to make 3.1.5 build on rh9 entail the generation of
additional patches in the patches directory. These patches are necessary for
rh9, but not for rh8 or other distros. They may or may not be harmless, and
should probably not be applied for other distros. This leads me to a couple
of questions.
1) Is there a mechanism that can deal with patches that should only be applied
on a particular rev of a particular distro? For example, right now I have
the spec file 'figuring out' the distro and adding the required patches to
the patches directory when the vendor is redhat and the distro version is
'9'. This allows the rpm to build on rh8 and rh9 without modifying the spec
file, but it means that there are patches that have to be dragged around
outside the systemimager tarball.
2) There are two ways that I can create the necessary patches. I can write a
"patch that creates a patch" or I can provide the patch in source form. The
question is, which is preferable? In the first example, you can do something
in the spec file like
Patch1: patch-to-make-a-patch
%prep
%setup
%patch1
In the second case, you can do something like
Source1: plain-old-patch-file
%prep
%setup
%{__cp} %{SOURCE1} patches/subpackage.10whatever.patch
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Sisuite-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/sisuite-devel
