Re: Moving ATF tools code into the NetBSD tree

[Matt Thomas <matt%3am-software.com@localhost>]

On Jan 10, 2014, at 3:50 PM, Julio Merino <julio%meroh.net@localhost> wrote:

> Hello all,
> 
> As you know, the ATF tools have been deprecated for a long while and
> the intention has been to replace them with Kyua.  Unfortunately, that
> hasn't happened yet due to a couple of issues in Kyua that need
> addressing to satisfy the continuous testing machines' desires.  (The
> requests are reasonable but I just haven't had the energy to address
> them...)
> 
> I have (finally) gained interest again in addressing these issues and
> started working on a solution.  But, in the meantime and because that
> won't be trivial, I'd like to kiss goodbye to the deprecated ATF tools
> to simplify the maintenance of the upstream code and, especially, to
> make my packaging tasks for the various systems involved much simpler.
> 
> For this reason, I am considering the removal of the ATF tools code
> from the upstream distfile, removing the code from external/bsd/atf/
> and *moving* a copy of the deleted code into the non-external
> directories.
> 
> For example, atf-run's master code would move from
> external/bsd/atf/atf-run/ to usr.bin/atf-run/ (and still remain
> conditional on the MK_KYUA knob).
> 
> The implication of this move is the transfer of maintainership of the
> deprecated tools to the NetBSD project.
> 
> Somehow I think this is a good thing because I get the the impression
> that some people around here really want to tweak the ATF tools until
> Kyua is ready -- and the fact that the code lives in external may have
> been a detriment to doing so.
> 
> How does that sound?

Wrong.  We already keep local maintained stuff in external (netpgp).
So just leave it where it is.  kyua will be going someplcae else so
it just churn for no good reason.