--=-=-=
Content-Transfer-Encoding: quoted-printable


"Greg A. Woods" <woods@weird.com> writes:

> At Sun, 16 Jul 2006 08:28:00 -0400,
> Greg Troxel wrote:
>>=20
>> This will result in an updated system with no broken dependencies.  It
>> should be able to run in the background, stopping on build failure,
>
> Sounds very cool.  Seems like it really will avoid all "ABI" issues!
>
> (not sure it'll eliminate the need to build binary packages in a "safe"
> environment and then use those to update production systems though, but
> it might make it easier to do more kinds of work on the build machines)

No, it won't eliminate that, but rolling_replace in binary mode could
be used in conjunction with such a bulk build.

>> and rarely leaving the system in an unworking state.
>
> What are the possible causes of such failures?

Until all make replaces are done, there could be an ABI mismatch, and
a package build could fail, leaving a dependency replaced with a new
ABI and a package which depends not updated.

=2D-=20
        Greg Troxel <gdt@ir.bbn.com>

--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.4 (NetBSD)

iD8DBQFEunEj+vesoDJhHiURAqx6AJ9BNJxeDQYr8BRI975DwiiwbtLfqgCeLRJo
VZgzYUIUuAV5GZy4swwbvaA=
=pr8D
-----END PGP SIGNATURE-----
--=-=-=--