<html><head></head><body><div style="color:#000; background-color:#fff; font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:16px"><div id="yui_3_16_0_ym19_1_1477760095652_15156">Hello all:</div><div id="yui_3_16_0_ym19_1_1477760095652_15088" dir="ltr">contrary to most of you think; I still see cvsup update efficiency by file and compiler recompile only updated sources method as the most advanced build/update system of what I have seen in this world. Please keep it that way<br></div><div dir="ltr" id="yui_3_16_0_ym19_1_1477760095652_15132"><br></div><div dir="ltr" id="yui_3_16_0_ym19_1_1477760095652_15209">Thanks in advance<br></div><div id="yui_3_16_0_ym19_1_1477760095652_15230"><span></span></div> <div class="qtdSeparateBR"><br><br></div><div class="yahoo_quoted" style="display: block;"> <div style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 16px;"> <div style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 16px;"> <div dir="ltr"><font size="2" face="Arial"> El Sábado 29 de octubre de 2016 15:42, Rodney M. Bates <rodney_bates@lcwb.coop> escribió:<br></font></div> <br><br> <div class="y_msg_container"><br clear="none"><br clear="none">On 10/28/2016 10:44 AM, Olaf Wagner wrote:<br clear="none">> On Fri, 28 Oct 2016 09:42:38 -0500<br clear="none">> "Rodney M. Bates" <<a shape="rect" ymailto="mailto:rodney_bates@lcwb.coop" href="mailto:rodney_bates@lcwb.coop">rodney_bates@lcwb.coop</a>> wrote:<br clear="none">><br clear="none">>> I agree, we very much need to make a new release. There has been a lot<br clear="none">>> of development since the last one, especially for having a small developer<br clear="none">>> community.<br clear="none">>><br clear="none">>> I have often thought I would be willing to do the work to do it, but every<br clear="none">>> time, I get stuck not having any idea what needs to be done. For one<br clear="none">>> thing, I presume it entails verifying that things build and work on all<br clear="none">>> the various targets, which would further entail having access to one<br clear="none">>> of each of them.<br clear="none">>><br clear="none">>> Are such machines available? Any advice on how to proceed?<br clear="none">><br clear="none">> I think the most important thing would be to have an agreement on<br clear="none">> - which platforms will be part of the release<br clear="none">> - how the release will be packaged and deployed.<br clear="none">><br clear="none">> I'd advise to concentrate on a small number of important platforms,<br clear="none"><br clear="none">OK, let's hear some nominations for important platforms.<br clear="none"><br clear="none">I need AMD64_LINUX and LINUXLIBC6. For the future, I would probably want<br clear="none">a Windows version, and there are some others using Windows regularly, I think.<br clear="none"><br clear="none">Jay, where can we look for the latest more-aptly-renamed platform names?<br clear="none"><br clear="none">or<br clear="none">> to have a simple standard procedure for all platforms (for example<br clear="none">> cross-compiled bootstrap archives)<br clear="none"><br clear="none">Are these just tar files of /usr/local/cm3? Do we want to keep using<br clear="none">cminstall?<br clear="none"><br clear="none">We are still requiring several static libraries (that are not part of CM3).<br clear="none">These present installation problems, as most distros now do not include them<br clear="none">by default, and, worse, it is quite a detective job to track from a name<br clear="none">like "libmumble.a not found" to what package needs to be installed. We<br clear="none">probably want to configure to use mostly dynamic libraries. Or maybe<br clear="none">be able to use either?<br clear="none"><br clear="none">and more convenient support for some<br clear="none">> of them (for example Debian packages).<br clear="none">><br clear="none"><br clear="none">Yes, this would be very good. Then they could go in package archives, and<br clear="none">installation would be much easier. But we would also need to decide how<br clear="none">to break things up into packages. E.g., would the stuff in groups like<br clear="none">do-cm3-comm and do-cm3-ui be separate? Just matching what is in the various<br clear="none">do-cm3-* scripts or the named groups in pkginfo.txt won't work, because they<br clear="none">are highly non-disjoint. We need a partition.<br clear="none"><br clear="none">Also, my understanding about packages is that, while putting together a<br clear="none">package that will work is not too difficult, some Linux distros have<br clear="none">stringent requirements about package contents that are a lot more work<br clear="none">to create.<br clear="none"><br clear="none"><br clear="none">> Olaf<br clear="none">><br clear="none"><br clear="none">-- <br clear="none">Rodney Bates<br clear="none"><a shape="rect" ymailto="mailto:rodney.m.bates@acm.org" href="mailto:rodney.m.bates@acm.org">rodney.m.bates@acm.org</a><div class="yqt1817595207" id="yqtfd63251"><br clear="none">_______________________________________________<br clear="none">M3devel mailing list<br clear="none"><a shape="rect" ymailto="mailto:M3devel@elegosoft.com" href="mailto:M3devel@elegosoft.com">M3devel@elegosoft.com</a><br clear="none"><a shape="rect" href="https://m3lists.elegosoft.com/mailman/listinfo/m3devel" target="_blank">https://m3lists.elegosoft.com/mailman/listinfo/m3devel</a><br clear="none"></div><br><br></div> </div> </div> </div></div></body></html>