On Mon 28 Jul 2008 at 01:32PM, Shawn Walker wrote:
> As part of the work I'm doing for bug 2022 "make manifest request
> provide more information for download tracking", it seems there is some
> overlap with some of the possible hooks we want to put into place for
> "verbose mode" or "debugging."
>
> Specifically, I feel like my current solution for passing along the
> intent of the client's operation is hacky at best:
>
> http://cr.opensolaris.org/~swalker/pkg-2022/
>
> It seems like there is an opportunity here with the work on debug /
> verbose to find a better way to pass around operational information than
> adding a parameter to a few dozen subroutines.
>
> Will the verbose / debugging information changes generate and store the
> information in an internal structure as we go along and then dump that
> information in a human-readable format at appropriate intervals?
Shawn, since I own that bug I guess you're asking me?
It wasn't my plan thus far to build up a lot of in memory state as
part of either of verbose or debug.
In particular, debug information should be just that: information for
developers to use when diagnosing problems. It is by nature
unstructured, and volatile. I wouldn't want to commit to anything in
that regard as anything more than a simple mechanism.
For verbose output, I was simply thinking of redoing that which is
there now. In my mind, -v should to give more depth of information
about the plan.
> Particularly troublesome, to me at the moment, is how best to retrieve
> previous version information (if they're upgrading from an older package).
Why isn't that just a reference to an appropriate datum in the pkgplan?
-dp
--
Daniel Price - Solaris Kernel Engineering - [EMAIL PROTECTED] - blogs.sun.com/dp
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
