[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
On Tue, Aug 29, 2000 at 06:48:10PM +0200, Marc Espie wrote:
> On Wed, Aug 23, 2000 at 05:07:25AM +0200, Hubert Feyrer wrote:
> > > etc .. I know there are other things in the queue that would simlify some
> > > of the pkg_* tools .. like libpax allowing for no temporary extraction area
> > > and such .. again, not sure of the status.
> > Won't this prevent rollback functionality if it's found that the pkg
> > cannot be installed at a late stage?
> Right now, rollback is mostly necessary because the package is installed
> directly without checking for problems first. Checking that the packing-list
> won't cause trouble means rollback won't be necessary in many cases...
> considering that @exec/@unexec pairs mean rollback isn't safe in many cases,
> avoiding rollback alltogether looks like a good idea...
We could always copycat the behavior of aix packages. It behaves similarly
to a filesystem. When a package operation is begun, it is entered into the
database in some way as being in progress. If at any point the package aborts
abnormally, it is left in an 'unclean state' and a 2nd utility is run to
'clean up' before that particular package can be dealt with/upgraded ..
Speaking of 'upgrade' functionality .. if we speak of future plans, surely
this would be part of them?
Todd Fries .. firstname.lastname@example.org
To unsubscribe: send mail to <email@example.com>
with "unsubscribe bsdports" in the body of the message