|
|||||||||||||||
|
Running OpenBSD-currentIf running OpenBSD-current one has to track source changes and more important changes to the ports tree. This may become more difficult the more third party software is installed on your OpenBSD system. Automatically update ports from sourceTracking current by source will require some attention to the installed 3rd party software. Here is not yet perfect solution for automating this. This is a script to automatically update installed ports via source from the ports tree. It uses the out-of-date script, provided by the ports tree in the infrastructure/build directory to pick all outdated ports. This means that all cases of outdated ports should be covered like
I put all this in a README file together with the script and some patches I am currently using on my ports tree. These can be accessed via anonymous cvs (Fingerprint: 2e:78:ac:03:2d:47:58:9a:9b:2e:77:d5:2e:16:79:f8) with the password 'anoncvs':
It is possible to browse the source. I think that a single file download is no longer appropriate, so if you like to use the script, please use the anoncvs checkout. Keeping track of library changesEventually there comes the time when you wish to delete old shared libraries from the harddisk. A new version is in the base system and you wonder if you can safely delete the lib? Sometimes ports, especially such ports that change not frequently, are still linked to the old libs. With the following shell script it is possible to list all executable files under a given path (for example /usr/local/bin in case of ports) that are linked to a specific library.
If you have the new libc.so.42.0 installed and wish to know which executables installed via ports are still using the libc.so.41.0 you could invoke the script like this:
There is an easier way to do this if you actually have installed the ports tree. In ${PORTSDIR}/infrastructure/build/ is an excellent script called out-of-date with a shiny output and much more information (see above for a useful script utilizing this). |