On Thu, 9/12/13, Kent A. Reed <[email protected]> wrote: I personally lean away from shell-script cleverness* and toward creating explicit lists for each new distro ala Michael's "install-packages-for-build-on-12.04-pristine.sh". Speaking solely for myself, this approach improves clarity and ease of maintenance at the expense of redundancy. Good hunting! Regards, Kent I'm a big fan of software authors including *everything required* for their program to work, or at least providing a *complete* list of requirements, dependencies etc AND exactly where to get it all.
Throwing stuff out there by itself and expecting the users to "just figure it out" or "you should know how to set it up" or things like having it require a deprecated function from some support file five versions old is to put it mildly, just a bit irritating. If your code has such a requirement, write it so that obsolete file can be called from the program's own path instead of the OS's default location where the OS will either complain about it or automatically update it with the latest version and break the program. ------------------------------------------------------------------------------ How ServiceNow helps IT people transform IT departments: 1. Consolidate legacy IT systems to a single system of record for IT 2. Standardize and globalize service processes across IT 3. Implement zero-touch automation to replace manual, redundant tasks http://pubads.g.doubleclick.net/gampad/clk?id=51271111&iu=/4140/ostg.clktrk _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
