<html><head><style type="text/css">.style1 {font-family: "Times New Roman";}</style></head><body>>- I don't have much knowledge about "make" and Makefile, but my opinion is that it is not the appropriate tool for installing dependencies. You can use DEB packages instead, which might be more suitable. Or just bash scripting, or listing the packages that need to be installed on the installation page.<BR>
<BR>
FWIW, everything that can be installed by standard package management, is already being installed that way. What you suggest is effectively what that particular make command is doing, but with minimized typing/copy/pasting.<BR>
<BR>
make -f Open-ILS/src/extras/Makefile.install <osname><BR>
<BR>
If you cat that Makefile.install file and give it a read (easier to follow than many bash scripts), it calls multiple other files depending on what osname you give it. Look at the files getting called for a given osname, and you'll find the list of DEB or RPM packages getting installed (along with the exact apt or yum command used to do it), among other things. (Repos to add if missing, CPAN modules to install, packages needing removed in favor of a compiled from source version, apache modules to enable, and so on.)<BR>
<BR>
I've found reading through them a pretty good way to see in complete detail what is going on with that step. Even with zero prior experience with it, I once found it quite easy to "add support" myself for a newly released os version, just to see if it would install and work there without any trouble. (It did!) One could absolutely use them as a guide to do all of it by hand, if desired.<BR>
<BR>
Hope that might be helpful for you, or for anyone else curious about how that part works. :)<BR>
<BR>
Cheers<BR>
-Jeremiah<BR>
<BR>
--------------------------------------<BR>
Jeremiah Miller | 503-507-9258 (cell)<BR>
Sysadmin | Albany Public Library<BR>
--------------------------------------<BR>
<BR>
______________<BR>
DISCLAIMER: This email may be considered a public record of the City of Albany and subject to the State of Oregon Retention Schedule. This email also may be subject to public disclosure under the Oregon Public Records Law. This email, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you have received this communication in error, please notify the sender immediately and destroy all copies of the original message.<BR>
<br><br><p style="font-family: Verdana; font-size:10pt; color:#666666;"><b>Disclaimer</b></p><p style="font-family: Verdana; font-size:8pt; color:#666666;">The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful.<br><br>This email has been scanned for viruses and malware, and may have been automatically archived by Mimecast, a leader in email security and cyber resilience. Mimecast integrates email defenses with brand protection, security awareness training, web security, compliance and other essential capabilities. Mimecast helps protect large and small organizations from malicious activity, human error and technology failure; and to lead the movement toward building a more resilient world. To find out more, visit our website.</p></body></html>