syncopt

If you're tired of updating the software on multiple machines, the syncopt script and associated work practices can be a useful solution to your problem. This approach doesn't rely on a vendor's packaging scheme, so you can use syncopt or the vendor's system, or even both. The idea is to install the software once on a central machine and then use syncopt to attach it to all clients (often via cron).

Syncopt is easy to use and flexible, making it possible to control what is installed locally on a machine and what is served remotely from a central server (for disk space or other reasons). It keeps out of the way of the "vendor's namespace" to avoid conflicts with the vendor's install and protect any additions from damage by vendor upgrades and patches.

Some key features of syncopt include its lightweight nature, its allowance for optional package installations, the ability to install multiple versions of the same package, centralized control over the default package version, and customizability regarding which packages are local and which version is the default.

To make an instance of something local to a client machine using Local Package Install, you can simply remove the local symlink, make a stub directory, or edit the .syncopt file. Running syncopt syncs everything, and you can install a new package by syncing the generic link and the version-specific local directory. To undo a local package install or bring a client into sync after a new package install, simply remove the local copy, edit the .syncopt file, and run syncopt as necessary.

Overall, if you need to keep multiple machines' software installations up to date, syncopt is a customizable, lightweight solution that can simplify the process and give you more control over the outcome.