[boost] Separate Boost CMake mailing list

[Edward Diener via Boost]

I think that a separate Boost CMake mailing list would be beneficial,
rather than have all the discussion about the move to CMake, as the
default Boost build system, as well as further uses of CMake with Boost
libraries and tools, on the developers mailing list. This is similar to
the way that Boost currently has a separate mailing list for Boost Build.


_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

[Rene Rivera via Boost]

On Jul 25, 2017 8:05 AM, "Edward Diener via Boost" <***@lists.boost.org>
wrote:

I think that a separate Boost CMake mailing list would be beneficial,
rather than have all the discussion about the move to CMake, as the default
Boost build system, as well as further uses of CMake with Boost libraries
and tools, on the developers mailing list. This is similar to the way that
Boost currently has a separate mailing list for Boost Build.


Unless you are developing cmake itself the comparison doesn't hold. A
separate list will exclude impromptu opinions that make such discussions
fruitful.

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

[Edward Diener via Boost]

Post by Edward Diener via Boost
I think that a separate Boost CMake mailing list would be beneficial,
rather than have all the discussion about the move to CMake, as the default
Boost build system, as well as further uses of CMake with Boost libraries
and tools, on the developers mailing list. This is similar to the way that
Boost currently has a separate mailing list for Boost Build.
Unless you are developing cmake itself the comparison doesn't hold. A
separate list will exclude impromptu opinions that make such discussions
fruitful.

My own limited experience with trying to understand and code with CMake
has shown me that the support for CMake on the official CMake users list
is atrocious. Maybe it is just me, but whatever questions I have ever
asked on that mailing list have been completely ignored. So I have, and
no doubt will have, many questions I will be asking Boost developers
about CMake which I cannot understand from the official CMake
documentation. Rather than use the Boost developers mailing list as the
place to ask those questions I feel that a separate Boost mailing list
would be better, so as not to clutter the developers mailing list with
CMake related posts. But I will go with whatever others decide.

Post by Edward Diener via Boost
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

[Peter Dimov via Boost]

Rather than use the Boost developers mailing list as the place to ask
those questions I feel that a separate Boost mailing list would be better,
so as not to clutter the developers mailing list with CMake related posts.
But I will go with whatever others decide.

I have always preferred the cross-pollination the main dev list creates, but
there's a legitimate disagreement to be had here.


_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

[Rene Rivera via Boost]

Post by Edward Diener via Boost
I think that a separate Boost CMake mailing list would be beneficial,
rather than have all the discussion about the move to CMake, as the default
Boost build system, as well as further uses of CMake with Boost libraries
and tools, on the developers mailing list. This is similar to the way that
Boost currently has a separate mailing list for Boost Build.
Unless you are developing cmake itself the comparison doesn't hold. A
separate list will exclude impromptu opinions that make such discussions
fruitful.

My own limited experience with trying to understand and code with CMake has
shown me that the support for CMake on the official CMake users list is
atrocious. Maybe it is just me, but whatever questions I have ever asked on
that mailing list have been completely ignored. So I have, and no doubt
will have, many questions I will be asking Boost developers about CMake
which I cannot understand from the official CMake documentation. Rather
than use the Boost developers mailing list as the place to ask those
questions I feel that a separate Boost mailing list would be better, so as
not to clutter the developers mailing list with CMake related posts. But I
will go with whatever others decide.


The same situation happened with the git transition. The questions and
answers where informative to everyone. We kept it on the main list but
tagged with "[githelp]" so as to allow for either mental or programmatic
filtering.

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

[Peter Dimov via Boost]

Post by Edward Diener via Boost
I think that a separate Boost CMake mailing list would be beneficial,

Already exists: https://lists.boost.org/mailman/listinfo.cgi/boost-cmake

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost