Hey LibreDWG maintainers! Although there are still some questions policy-wise:
|$ grep -nHF '???' $(git ls-files) |HACKING:2: "???" means that there is still some question to resolve; |HACKING:20: - [??? other] |HACKING:25: in without updating it. Once we get to (??? SOME-MILESTONE), we plan |HACKING:29: This means that as of (??? START-DATE) the commit logs should follow |HACKING:76: - [??? more topics here] |HACKING:78:* [??? other exceptions] |doc/LibreDWG.texi:88:@*[??? libtool version info ?...@* |doc/LibreDWG.texi:94:@c [???] For first release, there is no history. However, might me want |doc/LibreDWG.texi:107:process; the specification is approximately [??? percent ???] complete. |doc/LibreDWG.texi:110:approximately [??? percent ???]. |doc/LibreDWG.texi:117:@item FOO[???] variant |doc/LibreDWG.texi:130:@item [???] |doc/LibreDWG.texi:177:[???] |doc/LibreDWG.texi:187:[???] |doc/LibreDWG.texi:234:[???] |doc/LibreDWG.texi:243:The highest level function for encoding a bitstream to a file is [???]. |doc/LibreDWG.texi:266:[???]) and any other program(s) or manual(s) involved. |src/dwg.spec:1873: //FIELD(view_mode, RC); //??? 4bits , i think the mechanisms for "make dist" are all in place now. To play: $ sh autogen.sh $ ./configure [--enable-trace] $ make $ make check $ make install $ make dist Please let me know of any problems you encounter. In particular, i haven't had a chance to try a srcdir!=builddir flow and so am interested in failure reports for that situation. I'm going to take a break from LibreDWG for a few days to do Other Stuff, but will be back towards end of week. Happy hacking, thi
