[packagekit] Assertion `backend->priv->locked != FALSE' failing during init

[Thomas Wood]

On Wed, 2008-03-19 at 16:55 +0000, Richard Hughes wrote:
> On Wed, 2008-03-19 at 16:51 +0000, Thomas Wood wrote:
> > On Wed, 2008-03-19 at 16:27 +0000, Richard Hughes wrote:
> > > On Wed, 2008-03-19 at 16:22 +0000, Thomas Wood wrote:
> > [...]
> > > Out of interest, what message are you trying to propagate to the user at
> > > init time?
> > 
> > Uuuh, debug messages? :-)
> 
> I think pk_warning and pk_debug might be better for that :-)

    if (level == OPKG_NOTICE)
            pk_backend_message (backend, PK_MESSAGE_ENUM_NOTICE, msg);
    if (level == OPKG_ERROR)
            pk_backend_message (backend, PK_MESSAGE_ENUM_WARNING, msg);

So, what are these enums for and how are they different to
pk_warning/pk_debug?



> 
> > Probably not of interest to end users, but could be interesting to front
> > ends?
> 
> I don't think frontends should be parsing the output of Messages() -
> unless you can think of a good reason why that would rock....
> 
> > If this isn't the purpose of pk_backend_message(), then I should
> > probably stop (ab)using it.
> 
> Well, I use it for debugging (the DAEMON constant) so I can't really
> talk. You can remove the lock check if you wish, that's fine with me,
> and probably logically correct.


I think that really depends on what the defined use case is for
pk_backend_message().

Regards,

Thomas


-- 
OpenedHand Ltd.

Unit R Homesdale Business Center / 216-218 Homesdale Road /
Bromley / BR1 2QZ / UK             Tel: +44 (0)20 8819 6559

Expert Open Source For Consumer Devices - http://o-hand.com/
------------------------------------------------------------