#426: install_files.pl and install_dev_files.pl have a fair bit of duplicate 
code
---------------------+------------------------------------------------------
 Reporter:  wayland  |       Owner:  jkeenan 
     Type:  patch    |      Status:  assigned
 Priority:  normal   |   Milestone:          
Component:  install  |     Version:  0.9.1   
 Severity:  medium   |    Keywords:  install 
     Lang:           |       Patch:  new     
 Platform:           |  
---------------------+------------------------------------------------------
Changes (by jkeenan):

  * owner:  => jkeenan
  * status:  new => assigned


Comment:

 Replying to [comment:2 wayland]:
 > 1. As regards testing, sure.  Tell me where you want the test file, and
 what you want it called, and I should hopefully be able to handle it from
 there.
 >

 Excellent. I have created t/tools/install/ for this purpose.  If you grep
 the tests in t/configure/ and t/steps/ for File::Temp and
 IO::CaptureOutput, you'll find plenty of examples of how we capture the
 ''print'' statements' output, how we set up temporary directories for safe
 testing, etc.

 I'll write some documentation for Parrot::Install.

 Because we're looking to release 1.0 next week, I recommend planning to
 commit this to trunk only after the release.  But in the meantime I've
 created the ''install_tools'' branch to hold the code.  You can submit
 patches to TT and I'll apply them to the branch as we go along.

 Thank you very much.[[BR]]
 kid51

-- 
Ticket URL: <https://trac.parrot.org/parrot/ticket/426#comment:3>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets

Reply via email to