[CMake] [cmake-developers] Support for multiple components in cpack

[Dr. Stefan Sablatnög]

Hi all,

first of all many thanks for considering to provide such a functionality.
I tried it on an small example yesterday and it worked as expected
(I patched against cmake 2.8.2), a larger test will follow as soon as I
find the time.

One minor thing (maybe a different issue?), 
I am not quite sure of yet is how to handle the destination 
of the packages? Is there already way to produce (or copy) the packages
to a user defined place (we usually put our final deliveries under revision 
control, so it would be ideal if the package would be in the "right" place 
automatically after each build.)

thanks
Stefan

-----Original Message-----
From: cmake-bounces at cmake.org [mailto:cmake-bounces at cmake.org] On Behalf Of
Eric Noulard
Sent: Dienstag, 3. August 2010 00:57
To: Clinton Stimpson
Cc: cmake-developers at cmake.org; cmake at cmake.org
Subject: Re: [CMake] [cmake-developers] Support for multiple components in
cpack

2010/8/2 Clinton Stimpson <clinton at elemtech.com>:
>>
>> Waiting for feedback before going on
>
> So I wondered if we were basically getting 3 modes out of this:
>
> 1. put multiple components in one components aware package (nsis,
packagemaker,...).
> 2. put multiple components in one non-component aware package (tar.gz,
.zip...).
> 3. put multiple components in multiple packages (all cpack generators).
>
> And how does one choose the behavior they want?

1. or 3. depends on the package capability.
Typically NSIS and PackageMaker may prefer 1. but you cannot do 1. with
DEB or RPM so you have to go with 3.

2. may always be an option because it was the behavior we had before the
component support and ALL CPack generator may handle an all-in-one package.
We could add an OPTION like CPACK_COMPONENT_ALL_IN_ONE which
would basically tell CPack to ignore the component aspect.

3. is an option for any current packages including tar.gz, zip etc...
    (and probably even NSIS and PackageMaker).

So I would say that depending on the generator "intrinsic" capabilities
it should (in that order)

chose 2) if CPACK_COMPONENT_ALL_IN_ONE is True
chose 1) if possible
chose 3) if possible
chose 2) as a failover.


-- 
Erk
Membre de l'April - « promouvoir et défendre le logiciel libre » -
http://www.april.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