Method To Deploy Non Standarized Software Packages In Heterogenious Environments With Make

Managing more than one environments with interconnected applications from different vendors it is difficult to maintain a common standard of how the software packages should be delivered by the vendor. Therefore it is difficult to maintain a common installation routine for all applications. To reduce the manual tasks and get a minimum of standardized procedure, even if there is no deployment tool available (for various reasons), using the build tool make can help. One prerequisite is to have all installable parts on a central machine available. The advantage of this method is that a) only available tools, commands, programs are used. No need to install expensive tools or ask a system administrator (aka root) to install things. b) make is only one binary has a small footprint and is practically available on every platform c) reduces manual work substantially and increases the quality of configuration tasks d) simple syntax, easy to learn This technical disclosure describes a method to deploy software packages of various kinds to one or more environments containing different versions of different operating systems by using make as a central deployment tool. Using only POSIX compliant commands, each variant of make (even Microsoft's nmake) is able to behave in the same manner.

Publication Date
07 November 2012

Tags
software packages


Download-publication


Click here to download link on ip.com


Click to share this page via your favorite social network.

LEARN MORE
Learn more about defensive publications with our examples and frequently asked questions

What we are trying to do?

We are attempting to mobilize the creativity and innovative capacities of the Linux and broader open source community to codify the universe of preexisting inventions in defensive publications that upon publication in the IP.COM database will immediately serve as effective prior art that prevents anyone from having a patent issued that claims inventions that have already been document in a defensive publication. In addition to creating a vehicle to utilize this highly effective form of IP rights management for known inventions, it is hoped that the community will use defensive publications as a means of codifying future inventions should the inventors prefer not to make their invention the subject of a patent disclosure and application.

Sponsors: