[LFS Trac] #1929: Use 'make install', when it can work, instead of 'cp', when installing single files.

[LFS Trac]

#1929: Use 'make install', when it can work, instead of 'cp', when installing
single files.
-----------------------------------------+----------------------------------
 Reporter:  robert@…                     |       Owner:  bdubbs@…                   
     Type:  enhancement                  |      Status:  assigned                   
 Priority:  lowest                       |   Milestone:  6.5                        
Component:  Book                         |     Version:  SVN                        
 Severity:  trivial                      |    Keywords:                             
-----------------------------------------+----------------------------------

Comment(by bdubbs@…):

 I've been working with this ticket and have found that using:

 {{{
 make -C ld EXEEXT=-new LIB_PATH=/usr/lib:/lib install-exec-local
 }}}

 does indeed take the place of
 {{{
 make -C ld LIB_PATH=/usr/lib:/lib
 cp -v ld/ld-new /tools/bin
 }}}

 However, I'm not sure this is a good approach.  Although it does show a
 different way of installing the program, it's not as clear as instructions
 we currently use.

 As far as using install instead of cp goes, I don't think that is a good
 idea unless we are changing some parameter such as permissions or
 owner/group at the same time.
 In addition, install does not handle recursive directories, so it really
 isn't appropriate in those conditions.

 Using more complex syntax where simple syntax works well detracts from the
 clarity of the instructions.

 I'm inclined to mark this as won't fix unless there is a better rationale
 than "It shows a different way."

-- 
Ticket URL: <http://wiki.linuxfromscratch.org/lfs/ticket/1929#comment:5>
LFS Trac <http://wiki.linuxfromscratch.org/lfs/>
Linux From Scratch: Your Distro, Your Rules.