Re: [CMake] cpack DEB generator docs
2012/6/18 Doug : > Yeah, I really should. :) > > Is this ok? Or shall I create a bug and attach the patch to that? (attach > patch; it's very minor; just missing 3 of the variables) It's ok and pushed to next. Merge topic 'CPackDeb-docUpdate' into next 264c156 CPackDeb add missing documentation for some CPACK_DEBIAN_xx variables. Pushing upstream next I did add extra informations you gave in your first mail for HOMEPAGE. -- Erk Le gouvernement représentatif n'est pas la démocratie -- http://www.le-message.org -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] cpack DEB generator docs
Yeah, I really should. :)
Is this ok? Or shall I create a bug and attach the patch to that? (attach
patch; it's very minor; just missing 3 of the variables)
doug@shadowmint:~/ext/cmake$ ./bin/cpack --help-variable-list |grep DEB <--
All in there now~
CPACK_RPM_PACKAGE_DEBUG
CPACK_DEBIAN_PACKAGE_ARCHITECTURE
CPACK_DEBIAN_PACKAGE_BREAKS
CPACK_DEBIAN_PACKAGE_CONFLICTS
CPACK_DEBIAN_PACKAGE_CONTROL_EXTRA
CPACK_DEBIAN_PACKAGE_DEBUG
CPACK_DEBIAN_PACKAGE_DEPENDS
CPACK_DEBIAN_PACKAGE_DESCRIPTION
CPACK_DEBIAN_PACKAGE_ENHANCES
CPACK_DEBIAN_PACKAGE_HOMEPAGE
CPACK_DEBIAN_PACKAGE_MAINTAINER
CPACK_DEBIAN_PACKAGE_NAME
CPACK_DEBIAN_PACKAGE_PREDEPENDS
CPACK_DEBIAN_PACKAGE_PRIORITY
CPACK_DEBIAN_PACKAGE_PROVIDES
CPACK_DEBIAN_PACKAGE_RECOMMENDS
CPACK_DEBIAN_PACKAGE_REPLACES
CPACK_DEBIAN_PACKAGE_SECTION
CPACK_DEBIAN_PACKAGE_SHLIBDEPS
CPACK_DEBIAN_PACKAGE_SUGGESTS
CPACK_DEBIAN_PACKAGE_VERSION
doug@shadowmint:~/ext/cmake$ ./bin/cpack --help-variable
CPACK_DEBIAN_PACKAGE_CONTROL_EXTRA
cpack version 2.8.8.20120618-g1d819-dirty
CPACK_DEBIAN_PACKAGE_CONTROL_EXTRA
Mandatory : NO
Default : -
This variable allow advanced user to add custom script to the
control.tar.gz
Typical usage is for conffiles, postinst, postrm, prerm.
Usage: SET(CPACK_DEBIAN_PACKAGE_CONTROL_EXTRA
"${CMAKE_CURRENT_SOURCE_DIR/prerm;${CMAKE_CURRENT_SOURCE_DIR}/postrm")
doug@shadowmint:~/ext/cmake$ ./bin/cpack --help-variable
CPACK_DEBIAN_PACKAGE_SUGGESTS
cpack version 2.8.8.20120618-g1d819-dirty
CPACK_DEBIAN_PACKAGE_SUGGESTS
Mandatory : NO
Default : -
see
http://www.debian.org/doc/debian-policy/ch-relationships.html#s-binarydeps
Allows packages to declare a suggested package install grouping.
doug@shadowmint:~/ext/cmake$ ./bin/cpack --help-variable
CPACK_DEBIAN_PACKAGE_RECOMMENDS
cpack version 2.8.8.20120618-g1d819-dirty
CPACK_DEBIAN_PACKAGE_RECOMMENDS
Mandatory : NO
Default : -
see
http://www.debian.org/doc/debian-policy/ch-relationships.html#s-binarydeps
Allows packages to declare a strong, but not absolute,
dependency on other packages.
doug@shadowmint:~/ext/cmake$
~
Doug.
On Mon, Jun 18, 2012 at 2:47 PM, Eric Noulard wrote:
> 2012/6/18 Doug :
> > Hm... I can't edit the wiki myself without going through the process of
> > getting an account.
>
> Then you should get an account :-)
>
> > Would it be possible to add just a note to this page:
> > http://www.vtk.org/Wiki/CMake:CPackPackageGenerators#DEB_.28UNIX_only.29
>
> I did it at the top:
>
> http://www.cmake.org/Wiki/CMake:CPackPackageGenerators#CPack_Package_Generators
>
> > Some of the supported options are not listed.
>
> As stated in the just-added paragraph. ALL the CPack variables should
> now be documented
> by the builtin documentation support of CPack 2.8.8 and up.
>
> > These are probably seldom used by most people, but they're actually quite
> > important if you're making configuration packages or virtual packages.
> > (and they _are_ supported, so there's no reason to scare people off by
> > making them think they aren't~)
> >
> > Already listed:
> > CPACK_DEBIAN_PACKAGE_ARCHITECTURE
> > CPACK_DEBIAN_PACKAGE_MAINTAINER
> > CPACK_DEBIAN_PACKAGE_DESCRIPTION
> > CPACK_DEBIAN_PACKAGE_DEPENDS
> > CPACK_DEBIAN_PACKAGE_RECOMMENDS
> > CPACK_DEBIAN_PACKAGE_SUGGESTS
> > CPACK_DEBIAN_PACKAGE_CONTROL_EXTRA
> >
> > Not listed, but supported in Source/CPack/cmCPackDebGenerator.cxx:
>
> cpack --help-variable-list | grep CPACK_DEBIAN_
>
> will give you the currently builtin-documented variables but...
> some variables you listed hereafter are not listed or the documentation
> is not as complete as the one you gave.
>
>
>
>
> > CPACK_DEBIAN_PACKAGE_HOMEPAGE
> > The URL of the web site for this package, preferably (when applicable)
> the
> > site from which the original source can be obtained and any additional
> > upstream documentation or information may be found. The content of this
> > field is a simple URL without any surrounding characters such as <>.
>
> [...]
>
> The builtin documentation is extracted from CPackDeb.cmake
> would you be able to provide a patch for this file:
>
> http://cmake.org/gitweb?p=cmake.git;a=blob;f=Modules/CPackDeb.cmake;h=fe81dc92c9ee7958e5cbb82d9990e659e8dbf484;hb=HEAD
>
> containing your update?
>
> The CPack builtin doc uses a basic markup which should be easy to
> understand.
>
>
> --
> Erk
> Le gouvernement représentatif n'est pas la démocratie --
> http://www.le-message.org
>
cpack-docs-fix.patch
Description: Binary data
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] cpack DEB generator docs
2012/6/18 Doug : > Hm... I can't edit the wiki myself without going through the process of > getting an account. Then you should get an account :-) > Would it be possible to add just a note to this page: > http://www.vtk.org/Wiki/CMake:CPackPackageGenerators#DEB_.28UNIX_only.29 I did it at the top: http://www.cmake.org/Wiki/CMake:CPackPackageGenerators#CPack_Package_Generators > Some of the supported options are not listed. As stated in the just-added paragraph. ALL the CPack variables should now be documented by the builtin documentation support of CPack 2.8.8 and up. > These are probably seldom used by most people, but they're actually quite > important if you're making configuration packages or virtual packages. > (and they _are_ supported, so there's no reason to scare people off by > making them think they aren't~) > > Already listed: > CPACK_DEBIAN_PACKAGE_ARCHITECTURE > CPACK_DEBIAN_PACKAGE_MAINTAINER > CPACK_DEBIAN_PACKAGE_DESCRIPTION > CPACK_DEBIAN_PACKAGE_DEPENDS > CPACK_DEBIAN_PACKAGE_RECOMMENDS > CPACK_DEBIAN_PACKAGE_SUGGESTS > CPACK_DEBIAN_PACKAGE_CONTROL_EXTRA > > Not listed, but supported in Source/CPack/cmCPackDebGenerator.cxx: cpack --help-variable-list | grep CPACK_DEBIAN_ will give you the currently builtin-documented variables but... some variables you listed hereafter are not listed or the documentation is not as complete as the one you gave. > CPACK_DEBIAN_PACKAGE_HOMEPAGE > The URL of the web site for this package, preferably (when applicable) the > site from which the original source can be obtained and any additional > upstream documentation or information may be found. The content of this > field is a simple URL without any surrounding characters such as <>. [...] The builtin documentation is extracted from CPackDeb.cmake would you be able to provide a patch for this file: http://cmake.org/gitweb?p=cmake.git;a=blob;f=Modules/CPackDeb.cmake;h=fe81dc92c9ee7958e5cbb82d9990e659e8dbf484;hb=HEAD containing your update? The CPack builtin doc uses a basic markup which should be easy to understand. -- Erk Le gouvernement représentatif n'est pas la démocratie -- http://www.le-message.org -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
[CMake] cpack DEB generator docs
Hm... I can't edit the wiki myself without going through the process of getting an account. Would it be possible to add just a note to this page: http://www.vtk.org/Wiki/CMake:CPackPackageGenerators#DEB_.28UNIX_only.29 Some of the supported options are not listed. These are probably seldom used by most people, but they're actually quite important if you're making configuration packages or virtual packages. (and they _are_ supported, so there's no reason to scare people off by making them think they aren't~) Already listed: CPACK_DEBIAN_PACKAGE_ARCHITECTURE CPACK_DEBIAN_PACKAGE_MAINTAINER CPACK_DEBIAN_PACKAGE_DESCRIPTION CPACK_DEBIAN_PACKAGE_DEPENDS CPACK_DEBIAN_PACKAGE_RECOMMENDS CPACK_DEBIAN_PACKAGE_SUGGESTS CPACK_DEBIAN_PACKAGE_CONTROL_EXTRA Not listed, but supported in Source/CPack/cmCPackDebGenerator.cxx: CPACK_DEBIAN_PACKAGE_HOMEPAGE The URL of the web site for this package, preferably (when applicable) the site from which the original source can be obtained and any additional upstream documentation or information may be found. The content of this field is a simple URL without any surrounding characters such as <>. CPACK_DEBIAN_PACKAGE_PREDEPENDS This field is like Depends, except that it also forces dpkg to complete installation of the packages named before even starting the installation of the package which declares the pre-dependency. CPACK_DEBIAN_PACKAGE_ENHANCES This field is similar to Suggests but works in the opposite direction. It is used to declare that a package can enhance the functionality of another package. CPACK_DEBIAN_PACKAGE_BREAKS When one binary package declares that it breaks another, dpkg will refuse to allow the package which declares Breaks to be unpacked unless the broken package is deconfigured first, and it will refuse to allow the broken package to be reconfigured. CPACK_DEBIAN_PACKAGE_CONFLICTS When one binary package declares a conflict with another using a Conflicts field, dpkg will refuse to allow them to be unpacked on the system at the same time. This is a stronger restriction than Breaks, which prevents the broken package from being configured while the breaking package is in the "Unpacked" state but allows both packages to be unpacked at the same time. CPACK_DEBIAN_PACKAGE_PROVIDES A *virtual package* is one which appears in the Provides control field of another package. The effect is as if the package(s) which provide a particular virtual package name had been listed by name everywhere the virtual package name appears. CPACK_DEBIAN_PACKAGE_REPLACES Packages can declare in their control file that they should overwrite files in certain other packages, or completely replace other packages. The Replaces control field has these two distinct purposes. ~ Doug. -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] CPack deb generator
Will try, thanks!
On Thu, Feb 19, 2009 at 21:53, Eric Noulard wrote:
> From CPackDeb.cmake I think you may include extra scripts in the
> control.tar.gz
> generated by CPack DEB generator.
>
> # CPACK_DEBIAN_PACKAGE_CONTROL_EXTRA
> # This variable allow advanced user to add custom script to the
> control.tar.gz (inside the .deb archive)
> # Typical examples are:
> # - conffiles
> # - postinst
> # - postrm
> # - prerm"
> # Usage:
> # SET(CPACK_DEBIAN_PACKAGE_CONTROL_EXTRA
> #"${CMAKE_CURRENT_SOURCE_DIR/prerm;${CMAKE_CURRENT_SOURCE_DIR}/postrm")
>
>
> Thus I would try to
> SET(CPACK_DEBIAN_PACKAGE_CONTROL_EXTRA
> "/path/to/your/postinst")
>
> where:
> /path/to/your/postinst
>
> is your custom post-installation script.
>
--
Bruno
http://iruel.net
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] CPack deb generator
2009/2/19 Bruno Antunes :
>
> Hello!
>
> Is there any way to include post-install events in CPack's DEB generator?
>From CPackDeb.cmake I think you may include extra scripts in the control.tar.gz
generated by CPack DEB generator.
# CPACK_DEBIAN_PACKAGE_CONTROL_EXTRA
# This variable allow advanced user to add custom script to the
control.tar.gz (inside the .deb archive)
# Typical examples are:
# - conffiles
# - postinst
# - postrm
# - prerm"
# Usage:
# SET(CPACK_DEBIAN_PACKAGE_CONTROL_EXTRA
#"${CMAKE_CURRENT_SOURCE_DIR/prerm;${CMAKE_CURRENT_SOURCE_DIR}/postrm")
Thus I would try to
SET(CPACK_DEBIAN_PACKAGE_CONTROL_EXTRA
"/path/to/your/postinst")
where:
/path/to/your/postinst
is your custom post-installation script.
--
Erk
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
[CMake] CPack deb generator
Hello! Is there any way to include post-install events in CPack's DEB generator? Thanks, -- Bruno http://iruel.net ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] CPack DEB generator: Installed-Size field
Rudoy, This must be a new requirement by newer apt-* stuff. Have a look at cmCPackDebGenerator.cxx. The code is pretty straighforward. You simply have to add the function that compute the size and then simply insert it at the right position. If you get it working, please send the patch back to the list. Thanks -Mathieu On Sat, Aug 9, 2008 at 2:15 PM, 0xd34df00d <[EMAIL PROTECTED]> wrote: > Hi there! > > First of all, thanks for the great software you write, CMake and CPack > really make development easier and more productive. > > I've noticed that .deb packages created by CPack don't contain > Installed-Size field, so dpkg (and, consequently, aptitude and other > package managers) think that installed size of the package is 0 bytes. > Is there a way to make CPack write that field to the control file? > That would be very useful, especially because CPack could > automatically calculate the size of install targets and keep the field > up-to-date. > > -- > Kind regards, > Rudoy Georg. > ___ > CMake mailing list > CMake@cmake.org > http://www.cmake.org/mailman/listinfo/cmake > -- Mathieu ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake
[CMake] CPack DEB generator: Installed-Size field
Hi there! First of all, thanks for the great software you write, CMake and CPack really make development easier and more productive. I've noticed that .deb packages created by CPack don't contain Installed-Size field, so dpkg (and, consequently, aptitude and other package managers) think that installed size of the package is 0 bytes. Is there a way to make CPack write that field to the control file? That would be very useful, especially because CPack could automatically calculate the size of install targets and keep the field up-to-date. -- Kind regards, Rudoy Georg. ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake
