> On Jun 12, 2015, at 12:11 PM, Adam Mercer <[email protected]> wrote: > > On Fri, Jun 12, 2015 at 11:09 AM, Daniel Powers <[email protected]> wrote: > >> That's the thing, when you build and install from source you really are >> stuck with having to track all of that manually. The only way you can be >> sure you've got all the needed fixes is to look at your source release date, >> and then apply all the patches that come out afterward. Once you've patched >> your source directory, you can then build your binaries/libs/etc again and >> reinstall. That's the only way I know to be sure your source built >> components have all the fixes. At least, that's the best I can come up with. > > OK, thanks. > > Cheers > > Adam
If you install from source and have PKG_CONFIG_PATH set to point to GLOBUS_LOCATION/lib/pkgconfig, you should be able to get the version for most things (I'm not sure if the executable-only packages install pkgconfig metadata): % pkg-config globus-common --modversion 15.30 We've lately been generating new snapshot installers that include all of the updated package sources whenever we publish advisories for GT6, so if you get the newest installer (currently globus_toolkit-6.0.1433516164.tar.gz) it will contain all of the updates. Unfortunately, we we don't have a convenient way to see exactly which packages were updated in each snapshot---you'd need to compare version numbers (from subpackage configure.ac files). I'll see if there's a easy way to generate a change manifest in the installer creation process. Joe
