First off, thanks to Kris and Mel for the previous definitive answers.
Let me see if I can summarize this correctly...
1) It's important that administrators who are taking advantage of
pre-compiled packages (like me) use packages that have been compiled for
their particular base system.
2)
Gary Affonso wrote:
If I do, it seems to me that the absolute first thing I should do after
installing a release version would be to change where pkg_add -r is
sourcing packages from. Either to current if I like to live on the
edge or stable if I want to be a more conservative.
No, stable
I'm curious, why does pkg_add -r point to the release snapshot of
ports by default? Is the idea that a release is well-tested and that
any deviation from that (even security or bug-fix changes) is an unknown
that new users need to be shielded against when grabbing packages with
pkg_add
Gueven Bay wrote:
I'm curious, why does pkg_add -r point to the release snapshot of
ports by default? Is the idea that a release is well-tested and that
any deviation from that (even security or bug-fix changes) is an unknown
that new users need to be shielded against when grabbing packages
In the last episode (Sep 04), Kris Kennaway said:
Gary Affonso wrote:
I'm curious, why does pkg_add -r point to the release snapshot
of ports by default? Is the idea that a release is well-tested
and that any deviation from that (even security or bug-fix changes)
is an unknown that new users
On Tuesday 04 September 2007 16:40:27 Dan Nelson wrote:
Also, packages from the -stable directory may have
different/conflicting dependencies compared to existing packages on
your system. Imagine installing 6.2 before the x.org-7 update, then
trying to pkg_add -r a package from the -stable
