[cmake-developers] [CMake 0015169]: CPackRPM: component-specific settings "fall through" to next component

Mantis Bug Tracker mantis at public.kitware.com
Mon Sep 22 15:36:45 EDT 2014


The following issue has been SUBMITTED. 
====================================================================== 
http://public.kitware.com/Bug/view.php?id=15169 
====================================================================== 
Reported By:                Sam Hartsfield
Assigned To:                
====================================================================== 
Project:                    CMake
Issue ID:                   15169
Category:                   CPack
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     new
====================================================================== 
Date Submitted:             2014-09-22 15:36 EDT
Last Modified:              2014-09-22 15:36 EDT
====================================================================== 
Summary:                    CPackRPM: component-specific settings "fall through"
to next component
Description: 
When component support is enabled in CPackRPM, component-specific settings get
applied not only to the specified component, but also to any subsequent
components. Some of these settings can be unset for the latter components, but
some cannot (e.g. CPACK_RPM_USER_BINARY_SPECFILE).

Steps to Reproduce: 
See attached example. For spec.in file, use a standard template (cpack -D
CPACK_RPM_GENERATE_USER_BINARY_SPECFILE_TEMPLATE=1 -G RPM).
====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2014-09-22 15:36 Sam Hartsfield New Issue                                    
2014-09-22 15:36 Sam Hartsfield File Added: CMakeLists.txt                    
======================================================================



More information about the cmake-developers mailing list