#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):

 * cc: jk...@… (removed)
 * cc: jkeenan (added)


Comment:

 I have uploaded a replacement for my last submitted patch.  The bug --
 which was of my own creation -- was actually located several lines above
 the `foreach` loop I discussed in my previous post.

 I was able to test this safely by following this procedure:

 1.  Create a throwaway directory, say ''/home/user/pseudoinstall''.

 2.  Do a fresh `svn co` of trunk, then apply
 [https://trac.parrot.org/parrot/attachment/ticket/426/diff.install_tools.patch
 diff.install_tools.patch].

 3.  Configure with a `prefix`:  `perl Configure.pl
 --prefix=/home/user/pseudoinstall`.  When configuration is done you can
 check ''Makefile'' and ''lib/Parrot/Config/Generated.pm'' to check where
 everything is going to be installed.

 4.  Call `make` and either `make install` or `make install_dev`.  You
 should see everything you need being installed under
 ''/home/user/pseudoinstall''.  For example, you should be able to call:
 `/home/user/pseudoinstall/bin/parrot --version`.

 5.  You can then dispose of the ''pseudoinstall'' directory when you're
 through with roadtesting ''install_files.pl'' and
 ''install_dev_files.pl''.

 Please let us know what results you get or problems you encounter.  Thank
 you very much.

 kid51

-- 
Ticket URL: <https://trac.parrot.org/parrot/ticket/426#comment:14>
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