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?<div><br></div><div>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?<br>
<br></div><div>Thanks,</div><div>David</div><div><br><div class="gmail_quote">On Fri, Jul 30, 2010 at 1:02 AM, Kishore <span dir="ltr"><<a href="mailto:kitts.mailinglists@gmail.com">kitts.mailinglists@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">I would like to see full support for multiple components in cpack.<br>
<div><div></div><div class="h5"><br>
On Tuesday 06 Jul 2010 12:01:17 am David Cole wrote:<br>
> Hi all,<br>
><br>
> Now that we have released CMake 2.8.2 last Monday, and we have switched to<br>
> this new workflow using branches in the git repository, *now* would be a<br>
> great time to prioritize bug fixes for the next release of CMake.<br>
><br>
> We are leaning towards quarterly releases from now on, scheduling them<br>
> every 3 months. That would make the next release of CMake version 2.8.3<br>
> and scheduled to have an "rc1" release candidate in approximately<br>
> mid-September, 2010.<br>
><br>
> If you have a particular issue that you think should be fixed for inclusion<br>
> in 2.8.3, please bring it up now. Ideally, each issue will be discussed as<br>
> needed on the mailing list to come to any consensus about what should be<br>
> done to fix it, and then an entry in the bug tracker may be used to keep it<br>
> on the radar screen, and to track activity related to it.<br>
><br>
> Patches are always welcome. Patches that include testing of any new<br>
> features, or tests that prove a bug is really fixed on the dashboards,<br>
> basically any patch with testing is preferred over a patch with no testing.<br>
> Also, if you are *adding* code, then you also probably need to add *tests*<br>
> of that code, so that the coverage percentage stays as is or rises.<br>
><br>
> Please discuss issues here as needed, and add notes to existing issues in<br>
> the bug tracker that you are interested in seeing fixed for 2.8.3 -- we<br>
> will be looking at the mailing list and activity in the bug tracker to<br>
> help prioritize the bug fixes that will occur in the next several weeks.<br>
><br>
><br>
> Thanks,<br>
> David Cole<br>
> Kitware, Inc.<br>
<br>
</div></div>--<br>
Cheers!<br>
<font color="#888888">Kishore<br>
</font><div><div></div><div class="h5">_______________________________________________<br>
Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
<br>
Visit other Kitware open-source projects at <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
<br>
Please keep messages on-topic and check the CMake FAQ at: <a href="http://www.cmake.org/Wiki/CMake_FAQ" target="_blank">http://www.cmake.org/Wiki/CMake_FAQ</a><br>
<br>
Follow this link to subscribe/unsubscribe:<br>
<a href="http://www.cmake.org/mailman/listinfo/cmake" target="_blank">http://www.cmake.org/mailman/listinfo/cmake</a><br>
</div></div></blockquote></div><br></div>