2015-11-08 13:34 GMT+01:00 Markus Rickert <rick...@fortiss.org>: > Hi, > > it is currently not possible to modify the component part of the package > name for Debian packages generated by CPack. For component-based packaging, > the name is currently composed of > "${CPACK_PACKAGE_NAME}${CPACK_DEB_PACKAGE_COMPONENT_PART_NAME}", where the > latter is set to "-${CPACK_DEB_PACKAGE_COMPONENT}". >
This is a long standing issue with related bugs: http://public.kitware.com/Bug/view.php?id=12997 http://public.kitware.com/Bug/view.php?id=12574 http://public.kitware.com/Bug/view.php?id=11050 http://public.kitware.com/Bug/view.php?id=13015 http://public.kitware.com/Bug/view.php?id=15042 which is shared (at least) by CPackRPM and CPackDeb > > The use of CPACK_PACKAGE_NAME here does not match the behavior of > non-component-based packaging, where CPACK_DEBIAN_PACKAGE_NAME can be > defined. > > With CPACK_PACKAGE_NAME set to "foo" and CPACK_DEBIAN_PACKAGE_NAME set to > "libfoo", a component "libraries" that gathers the libraries in a project > then defaults to, e.g., "foo-libraries", rather than "libfoo" (without a > component part) in the control file. > > These conventions can also differ between, e.g., Debian/Ubuntu and Fedora. > The former would expect libraries in "libfoo", headers in "libfoo-dev", and > documentation in "libfoo-doc", the latter however rather "foo"/"foo-devel" > or "libfoo"/"libfoo-devel". > > I've included two possible patches for this. The first one adds a fully > configurable component package name via > CPACK_DEBIAN_<COMPONENT>_PACKAGE_NAME, the latter only allows to set the > part name appended to CPACK_DEBIAN_PACKAGE_NAME (with "-<COMPONENT>" still > the default behavior). > > It would be great if one of those solutions could be integrated, as this > enables better matching of CPack and upstream conventions. A similar patch > could also be added to CPackRPM. > > Best regards, > > Markus Rickert > > -- > > Powered by www.kitware.com > > Please keep messages on-topic and check the CMake FAQ at: > http://www.cmake.org/Wiki/CMake_FAQ > > Kitware offers various services to support the CMake community. For more > information on each offering, please visit: > > CMake Support: http://cmake.org/cmake/help/support.html > CMake Consulting: http://cmake.org/cmake/help/consulting.html > CMake Training Courses: http://cmake.org/cmake/help/training.html > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/cmake-developers > -- Eric
-- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers