My OperaA method for tracking locally compiled software
Wednesday, February 15, 2012 9:20:35 AM
I tend to use a wide variety of distros, particularly when testing Opera. Occasionally I find that one of my favourite utilities isn't available, is old or has been compiled with different options. At this stage I usually compile the software from source.
When compiling from source one would ideally create native packages. This offers several advantages, e.g. it allows transfer of the software to other machines (for install or backup) and makes things much simpler should you ever need to remove the software. The problem however is that some packaging formats are complex, require large configuration files and a fair bit of specific knowledge before you can make a native package. My own solution to this is a short and simple shell script that automates creation of very simple tar "packages" with an internal log.
When compiling from source one would ideally create native packages. This offers several advantages, e.g. it allows transfer of the software to other machines (for install or backup) and makes things much simpler should you ever need to remove the software. The problem however is that some packaging formats are complex, require large configuration files and a fair bit of specific knowledge before you can make a native package. My own solution to this is a short and simple shell script that automates creation of very simple tar "packages" with an internal log.
