On 08/12/10 03:47 PM, [email protected] wrote:
On Thu, Aug 12, 2010 at 03:23:47PM -0700, Brock Pytlik wrote:
...
I don't understand why you don't want to allow the user some method
of stopping a potentially very long running action short of nuking
their entire depot. I'm fine with simple mechanisms, but not when
the desire for code simplicity makes users lives more difficult. If
they can't queue up more than one background task, I think some kind
of abort really is necessary (and I'd argue even with the ability to
queue up background processes, abort would be useful).
What's the use case for this? Wouldn't it lead to more errors if
we allow the index to be partially built? In Shawn's proposal, the only
way you can end up with a partial index is if the software crashes or is
kill(2)'d.
The partial index thing doesn't really matter anymore. The depot server
and any utilities that access the repository in a read/write mode will
automatically deal with that scenario.
I just don't feel that I need to provide a formal task management
interface for the depot server yet as we didn't already have one and
it's certainly not as important as other things that need to be done.
For now, pkgrepo via filesystem access is the best option.
Cheers,
-Shawn
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
