On 10/31/13 10:06 , Kent Reed wrote: > On Thu, Oct 31, 2013 at 10:44 AM, Sebastian Kuzminsky <s...@highlab.com>wrote: > >> On 10/29/13 01:11 , Chris Morley wrote: >>> Just curious on the position we are at with UB and 2.6 status. >>> I haven't heard much lately and just want to make sure my >>> work stays in step with possible release schedule. >> >> We have a lot of work to do before 2.6 will be ready to release. >> Reviewing and merging the UB/RTOS/PRU/emcweb/etc branch is the biggest >> task, but there are plenty of others. I've tried to collect a list of >> all tasks here: >> >> http://wiki.linuxcnc.org/cgi-bin/wiki.pl?Todo-2.6 >> >> If i've missed anything that should be considered for the release, >> please add it to the end. >> >> If anyone wants to work on any of those items, feel free to do that too ;-) >> >> >> > Good to see the list. I explored issue #20 some 18 months ago but don't > recall why I stopped. I'll look at it again.
Thanks Kent! I started to look into it a little too, and I got excited by the [latex] filter. It's integrated into asciidoc (not a home-brewed add-on), and it purports to work for both html and pdf (which are the two backends we care about). [latex] was introduced in asciidoc 8.6.0, which is newer than the 8.5.2 that Jeff backported to Lucid and Hardy for us. So we'd need to refresh our backport of asciidoc. 8.6.6 is in Precise, and i verified that the Precise asciidoc 8.6.6 package installs cleanly on both Lucid and Hardy, so that part seems like it'll be easy... I think the way forward should be this: * Verify that asciidoc 8.6.6 with the [latex] filter can actually do what we want. * In a feature branch, switch our docs and our docs buildsystem over to use it. * Refresh our asciidoc backport packages, then merge the feature branch into master. > While building Master_user.pdf, the message "Images > 'images/lathe-diagram.png' not found" pops up. A curious circumstance > because the image seems to end up in the doc anyway. Maybe it just me, but > I prefer clean builds which don't throw these kinds of messages even if > they end up being harmless. It's not just you! I think we should strive for 0 warnings in our builds, so that actual problems are easier to spot. -- Sebastian Kuzminsky ------------------------------------------------------------------------------ Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
