On Thu, 2014-01-09 at 11:15 -0800, Alec Warner wrote: > > > I think the opposition to this idea primarily falls on reliability. > There have been a number of hacks to portage over the years to keep it > functioning during upgrades of itself, even down to the non-standard > place where its .py files are stored (/usr/lib/portage/pym?) So the > real question is when we move to a plug-in architecture, how do we > add, remove, upgrade the plugins without breaking the actual package > manager? > > > -A >
Well, a good point. But, this is the sync module, not some of the critical pkg installation code. Another thing, once a module is loaded, the source file could be removed and/or replaced without adverse effects depending what the code does. That is not always the case though. Portage/emerge does not sync and install ebuilds simultaneously, so that problem is not a concern. Also a lock file could be used to prevent another emerge process form interfering with an ongoing sync run. Just like it does now for merging completed builds. -- Brian Dolbec <dol...@gentoo.org>
signature.asc
Description: This is a digitally signed message part
