[CMake] Bug fix requests for the *next* release of CMake...

[Kishore]

On Friday 30 Jul 2010 3:39:58 pm David Cole wrote:
> Could you elaborate on "full support for multiple components in cpack"
> either in another thread, or in a feature request bug in the bug tracker?
> 
> With NSIS on Windows and PackageMaker on Mac, we already have what I would
> consider "full support". Are you talking about extending that to additional
> CPack generators or is there something missing even in those generators in
> your opinion?

At the very basic level, i wish to see equal support for the other generators. 
Especially DEB and RPM. For the more advanced, like dependency between 
components, i would first need to check the level of support in NSIS. 
Nevertheless, DEB and RPM can benefit from inter component dependencies.

> 
> Thanks,
> David
> 
> On Fri, Jul 30, 2010 at 1:02 AM, Kishore 
<kitts.mailinglists at gmail.com>wrote:
> > I would like to see full support for multiple components in cpack.
> > 
> > On Tuesday 06 Jul 2010 12:01:17 am David Cole wrote:
> > > Hi all,
> > > 
> > > Now that we have released CMake 2.8.2 last Monday, and we have switched
> > 
> > to
> > 
> > > this new workflow using branches in the git repository, *now* would be
> > > a great time to prioritize bug fixes for the next release of CMake.
> > > 
> > > We are leaning towards quarterly releases from now on, scheduling them
> > > every 3 months. That would make the next release of CMake version 2.8.3
> > > and scheduled to have an "rc1" release candidate in approximately
> > > mid-September, 2010.
> > > 
> > > If you have a particular issue that you think should be fixed for
> > 
> > inclusion
> > 
> > > in 2.8.3, please bring it up now. Ideally, each issue will be discussed
> > 
> > as
> > 
> > > needed on the mailing list to come to any consensus about what should
> > > be done to fix it, and then an entry in the bug tracker may be used to
> > > keep
> > 
> > it
> > 
> > > on the radar screen, and to track activity related to it.
> > > 
> > > Patches are always welcome. Patches that include testing of any new
> > > features, or tests that prove a bug is really fixed on the dashboards,
> > > basically any patch with testing is preferred over a patch with no
> > 
> > testing.
> > 
> > > Also, if you are *adding* code, then you also probably need to add
> > 
> > *tests*
> > 
> > > of that code, so that the coverage percentage stays as is or rises.
> > > 
> > > Please discuss issues here as needed, and add notes to existing issues
> > > in the bug tracker that you are interested in seeing fixed for 2.8.3
> > > -- we will be looking at the mailing list and activity in the bug
> > > tracker to help prioritize the bug fixes that will occur in the next
> > > several weeks.
> > > 
> > > 
> > > Thanks,
> > > David Cole
> > > Kitware, Inc.
> > 
> > --
> > Cheers!
> > Kishore
> > _______________________________________________
> > 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

-- 
Cheers!
Kishore