[asterisk-bugs] [Asterisk-GUI 0010581]: Makefile in tools subdirectory assumes write permissions to /sbin and doesn't include $(DESTDIR)

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=10581 
====================================================================== 
Reported By:                djflux
Assigned To:                bkruse
====================================================================== 
Project:                    Asterisk-GUI
Issue ID:                   10581
Category:                   General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     assigned
Asterisk Version:            SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 1463 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             08-28-2007 07:33 CDT
Last Modified:              08-28-2007 09:30 CDT
====================================================================== 
Summary:                    Makefile in tools subdirectory assumes write
permissions to /sbin and doesn't include $(DESTDIR)
Description: 
If one is trying to install the asterisk-gui to a different destination
directory with $(DESTDIR) like the regular Asterisk source, the Makefile
doesn't contain that variable.  

For example, I was building as a non-root user and wanted to put the
resultant code in a different folder and the tools Makefile tried to put
the tools in /sbin to which I don't have permissions.

I will attach a patch for tools/Makefile that adds $(DESTDIR)
====================================================================== 

---------------------------------------------------------------------- 
 bkruse - 08-28-07 09:30  
---------------------------------------------------------------------- 
Waiting for disclaimer to go through :)

I made that awhile back as one of the directories were messed up in making
zapscan install, because we manually call /sbin/zapscan when calling it
from the GUI.

If its installed in DESTDIR, or /bin, for example, the /sbin/zapscan will
fail to run. Of course, we could try not using the full path, and hope that
$PATH has the place in which zapscan exists, but with our current system,
from the GUI, I cannot tell if the command was successful or not.

What do you think?

-bk 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
08-28-07 09:30  bkruse         Note Added: 0069548                          
======================================================================