Chris 'Xenon' Hanson wrote: > While poking around, I see that there is a package for a static >version of bash: > >ftp://ftp.openbsd.org//pub/OpenBSD/3.8/packages/i386/bash-3.0.16p1-static.tgz
> 2. For an automated installer, how would the installer know where to >get the proper package? The URL above works for 3.8, but will be wrong >for 3.9. Is there an environment variable or string that the installer >can expand to get the "3.8" or "3.9" portion of the URL? And then, how >does it figure out the exact package filename for the static version of >bash for a OS release it's never seen before? Without a heavy-duty web >search,how would it know that the 3.8 static release of bash was named >bash-3.0.16p1-static.tgz? It'd be nice if the script doesn't immediately >break and need updating when 3.9 comes out. We have the mechanisms in place for updates to figure this out. One can also currently install a package without knowing the exact version, through pkg stems. More thorough search mechanisms will be present in the next release. And it's likely automatic determinations of correct default location to grab a package will work. For the case at hand, something like PKG_PATH=ftp://ftp.openbsd.org/pub/OpenBSD/3.9/packages/i386/ sudo pkg_add -i bash ought to more or less work. It's currently not possible to specify a specific flavor without a version number, but interactive mode copes nicely. Your example is a bit unfortunate, since we decided it was not worth it to have a separate -static bash version. All in due time... there are no mechanisms yet to deal with this kind of meta issue, at least providing a `reasonable' update path for people who used to have a static bash version (okay, we do have some, it will replace the static version with the normal version).
