libpthread -- it is generally under the program's control which modules
to load, a general rule is just too much
I've been using this modification for over a year without problems.
course a too-large hammer, but in addition to overriding checks it
appears to change behavior in some cases when no overrides are
necessary. Therefore, use pkg_add -U as before first, and only try -f
if that fails. (This is temporary and should be replaced by -D to
omit only the exact depends check as soon as that's in tree.)
update", so if it's going to fail because of a known vulnerability it
does so before uninstalling anything. I've been carrying this patch
for some three years with no ill effects. Ok by agc@.
"make replace" is defined to replace a package with a newer version,
and update depdending packages to depend on the new version. It has
long been understood that this is not always safe, with the responses
being "tell people to be careful" and the unsafe_depends variable
scheme and pkg_rolling-replace. In the DESTDIR case, make replace is
implemented by pkg_add -U. Usually, this is fine - even if the
ABI/shlib majors have changed, the package is replaced, and then a
later make replace of unsafe_depends=YES packages, either manually or
via pkg_rolling-replace, will bring the system to where it should be.
However, there are pinned dependencies on osabi where the depending
package will not accept the new version, and that causes pkg_add -U to
fail. This is incorrect, as a) those packages don't depend on the
osabi exact version any more than packages depending on jpeg depeend
on the particular shlib major, yet jpeg dependencies aren't pinned.
And, osabi changing version is not necessarily an ABI change -
consider 5.0_STABLE just before 5.1RC1 and just after, where only the
version string changed.
Therefore, add -f to pkg_add -U so that the update will succeed.
hardcoding the logic into the pkginstall scripts. As discussed in
tech-pkg@.
Note: The current pkginstall/shell code is overly complicated. It looks
like it can be simplified but, at the moment, given that I do not understand
the need for such complexity, I'm just doing this tiny change.
Note 2: The ability to update /etc/services, which was also discussed, will
come later once this change proves to be stable.
The [1]GNU project and the GCC developers are pleased to announce the
release of GCC 4.4.4.
This release is a bug-fix release, containing fixes for regressions in
GCC 4.4.3 relative to previous releases of GCC.
