On 7/23/06, Neil Bothwick <[EMAIL PROTECTED]> wrote:
On Sun, 23 Jul 2006 02:42:43 -0600, Trenton Adams wrote:

> Let's say openldap had a problem. So, we decide to mask the latest
> version of openldap, in an effort to roll back to the version that was
> working.  Well, we find out that openldap still does not work.  So, we
> finally determine that it is library W.  So, now we mask library W, in
> an attempt to roll back to the version that was working.  Oh no, now
> we find out that library W is used by 20 other packages, that require
> the latest version of library W in order to work.  So, now we have to
> mask library W, and 20 packages in order to get our openldap system
> functional, assuming you cared about the 20 other broken packages,
> which may break other packages, which may break yet other packages.
>
> Wouldn't it be nice to just go "emerge --revert-portage", which goes
> back to the last exported copy of the portage, that you had from
> subversion?  Boy, would that ever be convenient.  It would be simple
> enough to store a local history of portage tags that the user was
> using in the past.

Wouldn't that revert the whole of portage, not just the parts affecting
ldap, W and the rest? All of a sudden emerge world wants to downgrade
previously upgraded programs, some of which may have been updated for
security reasons. This means the user has to go through the Changelogs,
ebuild and package.mask to find out why they are being downgraded and
whether to apply the downgrade. this would be far more work that package
masking a few updates dependent on W, which could probably be scripted.

Yes, it would revert the whole portage, and that would be desired, so
as to be up quickly.  It could potentially take hours to figure out
which packages are being affected by a broken updated package.

But, perhaps it would be better to write a utility that will downgrade
a package, as well as all dependencies.  Or does this already happen
when you downgrade?


--
Neil Bothwick

BASIC: Bill's Attempt to Seize Industry Control



--
gentoo-user@gentoo.org mailing list

Reply via email to