Diff for /wikisrc/kyua/import.mdwn between versions 1.7 and 1.8

version 1.7, 2012/09/14 20:46:36 version 1.8, 2013/02/01 22:20:03
Line 2 Line 2
 [[!toc levels=2]]  [[!toc levels=2]]
   
 **Project owner: [Julio Merino](mailto:jmmv@NetBSD.org).**    **Project owner: [Julio Merino](mailto:jmmv@NetBSD.org).**  
 **Status: under review by tech-userlevel@ as of 2012-09-03.**  **Status: under review by tech-userlevel@ as of 2013-02-01.**
   
 The import of Kyua into NetBSD to replace the deprecated ATF tools is  The import of Kyua into NetBSD to replace the deprecated ATF tools is
 planned to happen in NetBSD 7.0.  The ATF libraries will remain in place,  planned to happen in NetBSD 7.0.  The ATF libraries will remain in place,
Line 152  the review: Line 152  the review:
 * [Issue 40](http://code.google.com/p/kyua/issues/detail?id=40): Provide  * [Issue 40](http://code.google.com/p/kyua/issues/detail?id=40): Provide
   manpages instead of an info document.  **DONE**    manpages instead of an info document.  **DONE**
   
   * [Issue 47](http://code.google.com/p/kyua/issues/detail?id=47): Implement
     independent testers, which reduces the amount of C++ code and avoids the
     need of modifying `bsd.dep.mk`.  **DONE**
   
 ## Import Kyua into src  ## Import Kyua into src
   
 As the [[introductory page to Kyua|/kyua]] describes, Kyua has been  As the [[introductory page to Kyua|/kyua]] describes, Kyua has been
Line 173  The specific steps to perform this impor Line 177  The specific steps to perform this impor
    Kyua, and was split into its own package per the request of some users     Kyua, and was split into its own package per the request of some users
    that found this component useful on its own.     that found this component useful on its own.
   
 1. Import Kyua into `external/bsd/kyua-cli/`.  This yields a new kyua  1. Import the Kyua testers into `external/bsd/kyua-testers/`.  This yields two
    binary in `/usr/bin`, a lot of test programs in `/usr/tests/kyua-cli`     new binaries in `/usr/libexec` (`kyua-atf-tester` and
    (around 100) and some auxiliary files in `/usr/share/kyua`.     `kyua-plain-tester`) and a bunch of tests in `/usr/tests/kyua-testers`.
   
   1. Import the Kyua frontend into `external/bsd/kyua-cli/`.  This yields a
      new kyua binary in `/usr/bin`, a lot of test programs in
      `/usr/tests/kyua-cli` (around 100) and some auxiliary files in
      `/usr/share/kyua`.
   
 1. Protect all products of Lutok and Kyua with a new `MKKYUA` knob.  **Set  1. Protect all products of Lutok and Kyua with a new `MKKYUA` knob.  **Set
    `MKKYUA=no` by default.**  Once the ATF tools are removed, the existence     `MKKYUA=no` by default.**  Once the ATF tools are removed, the existence
Line 197  NetBSD/macppc builds (which are the port Line 206  NetBSD/macppc builds (which are the port
 consider that some other tricky architecture should be build-tested  consider that some other tricky architecture should be build-tested
 (sparc64?), let me know and I'll include it in the list.  (sparc64?), let me know and I'll include it in the list.
   
 The submission step to CVS, once all the code changes are ready locally,  The submission to CVS will be prepared locally and performed on a package
 and any post-commit validation checks will take a few hours.  Any build  basis (i.e. `lutok`, `kyua-testers` and `kyua-cli`, in this order).  These
 breakage should be addressed in a timely manner, but these should be very  are to be imported separately to simplify the review of the changes and to
 limited in scope and risk because the default will still be `MKKYUA=no` at  allow me to better test every individual change locally.  There may be an
 this point.  arbitrary amount of time between the submission of each package: this
   should not be a problem because these modules are still disabled due to
   `MKKYUA` being set to `no` by default.
   
 ## Adjust continuous testing systems to use Kyua  ## Adjust continuous testing systems to use Kyua
   
Line 350  use, or will soon use, C++ in their code Line 361  use, or will soon use, C++ in their code
 be able to remove all C++ support from base anytime soon due to this, while  be able to remove all C++ support from base anytime soon due to this, while
 at the same time keeping support for all the ports that NetBSD has.  at the same time keeping support for all the ports that NetBSD has.
   
 In the middle term, the  Thanks to the
 [testers project](http://code.google.com/p/kyua/wiki/TestersDesign) will  [testers project](http://code.google.com/p/kyua/wiki/TestersDesign), and
 get rid of a significant amount of tricky C++ code (and its additional set  starting with Kyua 0.6, a lot of the tricky OS-specific code in Kyua has
 of test programs) and replace it with plain and simpler C code.  been rewritten in plain C.  This paves the way to rewriting parts of the
   now-simpler frontend in C or Lua, if the use of C++ proves to be a serious
 In the long term, if the use of C++ still proves to be a problem, we can  problem in the future.
 reconsider rewriting most of the user interface in Lua and just providing a  
 few bits in C.  (I haven't researched any of this yet because my knowledge  
 of Lua is very limited.)  This will be investigated separtely when the time  
 permits.  
   
 In the short term, the replacement of ATF with Kyua does not make things  In the short term, the replacement of ATF with Kyua does not make things
 worse: this project just changes one chunk of code with another.  worse: this project just changes one chunk of code with another.

Removed from v.1.7  
changed lines
  Added in v.1.8


CVSweb for NetBSD wikisrc <wikimaster@NetBSD.org> software: FreeBSD-CVSweb