[anaconda][rhel7-branch][PATCH] Add a subpackage for the help content

Martin Kolman mkolman at redhat.com
Wed Nov 26 17:25:05 UTC 2014


To get some help content versioning and to prepare the ground for having a separate
help content package in the future, add a subpackage for holding the help content files.

The subpackage has its own version to ease the eventual future transition to a standalone package
- could that be an issue for some of the compose tools are dependency solvers ?

Also a note about the interesting way how RPM handles version definition in spec files:

It is defined by the Version: keyword and subpackages can use it to define a separate version from
the main package one. To work with the version value the %{version} macro can be used,
*however* once the subpackage uses the Version: keyword to set its version, the %{version}
macro no longer points to the main package version but to the subpackage one.

This behavior is quite unfortunate as sub package definitions are above the %prep, %build
and %install sections, meaning every usage of the %{version} in these section macro will return the
subpackage version, even if you want to get the version of the main package. And even using %define *above*
the subpackage definition to remember the main package version does not work, as all macros are apparently
expanded only once used.

So as I have not been able to find a better way, I've just hacked around it by using the #VERSION# special variable
that gets substituted for the actual version by the makefile and should thus be exempt from the above described
%{version} handling madness.

Any suggestion how to solve this in a nicer way will be appreciated! :)


Martin Kolman (1):
  Add help content subpackage (#1072033)

 anaconda.spec.in | 27 +++++++++++++++++++++++++++
 1 file changed, 27 insertions(+)

-- 
1.9.3



More information about the anaconda-patches mailing list