[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: death to kdeaddons, long live extragear!
From:       "Aaron J. Seigo" <aseigo () kde ! org>
Date:       2007-08-30 2:50:04
Message-ID: 200708292050.05295.aseigo () kde ! org
[Download RAW message or body]


On Wednesday 29 August 2007, Alexander Neundorf wrote:
> mention that cpack which comes with cmake has improved a lot in cvs, which
> will become cmake 2.6 later this year.
> cpack can now also create debian and RPM packages.
> Projects which want to create packages with cpack need to set a bunch of
> variables and then include CPack. While this makes things ugly if you do
> this directly in the cmake files, you can of course split this into a
> separate file: http://www.cmake.org/Wiki/CMake#CPack

neat. does it handle splitting things up, so that one can then for instance 
do:

cd kdebase/workspace/libs/plasma
make package

and come out with a libplasma.rpm and libplasma.deb? if so, that would be 
super. it seems to imply that it would as it uses the INSTALL directives, but 
i'm not sure as i haven't tried it yet and am already tired for the day.

if so, we could perhaps include some CPack directives in our projects to make 
packager's lives easier: packaging things separately would become a matter of 
a script recursing into various dirs and calling "make package" on it....

*thinks*

it would be -really- cool if there were per-project package targets generated 
as well so one could do `make libpasma-package plasma-package` or sth along 
those lines from the top level. =)

-- 
Aaron J. Seigo
humru othro a kohnu se
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43

KDE core developer sponsored by Trolltech

[Attachment #3 (application/pgp-signature)]

[prev in list] [next in list] [prev in thread] [next in thread]