MantisBT - CMake
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0012141CMake(No Category)public2011-04-30 05:502016-06-10 14:31
ReporterRosen Diankov 
Assigned ToKitware Robot 
PrioritynormalSeverityfeatureReproducibilityN/A
StatusclosedResolutionmoved 
PlatformDebianOSOS Version
Product VersionCMake 2.8.4 
Target VersionFixed in Version 
Summary0012141: Add Debian Source Generator Module
DescriptionWe just finished a new debian source package generator script for cmake:

https://openrave.svn.sourceforge.net/svnroot/openrave/trunk/modules-cmake/DebSourcePPA.cmake [^]

This is based on the initial UploadPPA.cmake file (
http://purplekarrot.net/blog/dputCMake.html [^] ) by Daniel Pfeifer,
except it adds 4 new cool features:

1. Simultaneous output of multiple debian source packages for each
distribution. Users can specify them by

set(CPACK_DEBIAN_DISTRIBUTION_RELEASES karmic lucid maverick natty)

and 4 dsc files, 4 changes files, 4 debian.tar.gz files, and one
src.orig.tar.gz file will be outputted. These can be sent directly to
launchpad via dput

2. Automatically generates symbols and run-time dependencies from the
build dependencies

3. Custom copy of source directory via CPACK_DEBIAN_PACKAGE_SOURCE_COPY

4. Handles distro and release specific dependencies through: DEPENDS_DISTRO_RELEASE, DEPENDS_DISTRO, DEPENDS. For example:

CPACK_DEBIAN_PACKAGE_DEPENDS_UBUNTU_LUCID


The usage of this file for generating packages for the OpenRAVE project can be
seen here:

https://launchpad.net/~openrave/+archive/release/+packages [^]
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
Attached Files? DebSourcePPA.cmake (12,479) 2011-04-30 05:50
https://public.kitware.com/Bug/file/3840/DebSourcePPA.cmake
Issue History
Date ModifiedUsernameFieldChange
2011-04-30 05:50Rosen DiankovNew Issue
2011-04-30 05:50Rosen DiankovFile Added: DebSourcePPA.cmake
2011-05-27 01:18Rosen DiankovNote Added: 0026629
2011-05-27 06:53Eric NOULARDNote Added: 0026632
2012-08-11 11:09David ColeStatusnew => backlog
2012-08-11 11:09David ColeNote Added: 0030261
2016-06-10 14:28Kitware RobotNote Added: 0041836
2016-06-10 14:28Kitware RobotStatusbacklog => resolved
2016-06-10 14:28Kitware RobotResolutionopen => moved
2016-06-10 14:28Kitware RobotAssigned To => Kitware Robot
2016-06-10 14:31Kitware RobotStatusresolved => closed

Notes
(0026629)
Rosen Diankov   
2011-05-27 01:18   
Does anyone know what is happening with this getting this into cmake? are there any problems that need to be resolved?
(0026632)
Eric NOULARD   
2011-05-27 06:53   
From my side I know,

Lack of time for the review/tests/etc.... which are necessary
for the integration.

Now since the proposed "patch" is a new module you should follow the
procedure described here:
http://www.itk.org/Wiki/CMake:Module_Maintainers [^]

you'll see that a bug entry is not the appropriate way to apply for a new module.
Now I remember I suggested you to open a bug report because I thought this
may become a CPack source generator, so I'll try to handle the bug when I get
more free time. In the meantime you may apply for adding this as a CMake module
and apply for being the module maintainer.

You can do that on CMake ML.
(0030261)
David Cole   
2012-08-11 11:09   
Sending old, never assigned issues to the backlog.

(The age of the bug, plus the fact that it's never been assigned to anyone means that nobody is actively working on it...)

If an issue you care about is sent to the backlog when you feel it should have been addressed in a different manner, please bring it up on the CMake mailing list for discussion. Sign up for the mailing list here, if you're not already on it: http://www.cmake.org/mailman/listinfo/cmake [^]

It's easy to re-activate a bug here if you can find a CMake developer who has the bandwidth to take it on, and ferry a fix through to our 'next' branch for dashboard testing.
(0041836)
Kitware Robot   
2016-06-10 14:28   
Resolving issue as `moved`.

This issue tracker is no longer used. Further discussion of this issue may take place in the current CMake Issues page linked in the banner at the top of this page.