<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.Code, li.Code, div.Code
{mso-style-name:Code;
mso-style-link:"Code Char";
margin:0cm;
margin-bottom:.0001pt;
mso-add-space:auto;
font-size:11.0pt;
font-family:"Courier New";
mso-fareast-language:EN-US;}
p.CodeCxSpFirst, li.CodeCxSpFirst, div.CodeCxSpFirst
{mso-style-name:CodeCxSpFirst;
mso-style-link:"Code Char";
mso-style-type:export-only;
margin:0cm;
margin-bottom:.0001pt;
mso-add-space:auto;
font-size:11.0pt;
font-family:"Courier New";
mso-fareast-language:EN-US;}
p.CodeCxSpMiddle, li.CodeCxSpMiddle, div.CodeCxSpMiddle
{mso-style-name:CodeCxSpMiddle;
mso-style-link:"Code Char";
mso-style-type:export-only;
margin:0cm;
margin-bottom:.0001pt;
mso-add-space:auto;
font-size:11.0pt;
font-family:"Courier New";
mso-fareast-language:EN-US;}
p.CodeCxSpLast, li.CodeCxSpLast, div.CodeCxSpLast
{mso-style-name:CodeCxSpLast;
mso-style-link:"Code Char";
mso-style-type:export-only;
margin:0cm;
margin-bottom:.0001pt;
mso-add-space:auto;
font-size:11.0pt;
font-family:"Courier New";
mso-fareast-language:EN-US;}
span.CodeChar
{mso-style-name:"Code Char";
mso-style-link:Code;
font-family:"Courier New";}
span.EmailStyle19
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-GB link="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoNormal>Hi,<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I’m successfully using Cmake version 3.9.1 (on CentOS 6.9) to build a C++ project, and then using CPack (from CMake) to build two RPMs, a RUNTIME and a DEVEL. I have set the DEVEL to depend upon the RUNTIME using:<o:p></o:p></p><p class=MsoNormal>SET(CPACK_RPM_DEVEL_PACKAGE_REQUIRES "${PROJECT_NAME} == ${FULL_VERSION}-${RELEASE_STRING}%{?dist}")<o:p></o:p></p><p class=MsoNormal>This works exactly how I want it to; requiring that the DEVEL package have the exact same release version of RUNTIME installed. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I also use:<o:p></o:p></p><p class=MsoNormal>SET(CPACK_RPM_RUNTIME_DEBUGINFO_PACKAGE ON)<o:p></o:p></p><p class=MsoNormal>To make a separate debuginfo RPM for the code in my runtime RPM. This also works as intended, to a point. If a user has all three RPMs installed, then everything is fine. They then learn an update (of all three RPMs) has been placed in the repo, so they run ‘sudo yum update myRpm-devel’, knowing that this will also update the runtime package. Unfortunately this doesn’t update the debuginfo package, so they are no longer in-sync.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I searched around and tried to use a “CPACK_RPM_<COMPONENT_NAME>_DEBUGINFO_PACKAGE_REQUIRES” variable from CMake, but it didn’t work, and as I’m using CPack to generate my SPEC files I can’t see another way to modify them. CPack only generates two SPEC files, one for the DEVEL and one for the RUNTIME, and the additional instructions to generate the debuginfo are in the RUNTIME’s SPEC file. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Is there a way to set package-requires for debuginfo RPMs?<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Thanks,<o:p></o:p></p><p class=MsoNormal>Phil<o:p></o:p></p></div></body></html>