Some 'depexp' nits

Some 'depexp' nits

[Gary Thomas]

I hope this is the correct list.

I was just using '-u depexp' and noticed a few small things.
   $ bitbake my-qt5-image -u depexp
   This UI is only compatible with the -g option

Perhaps this should be worded more strongly, like this?
   This UI requires the -g option

Also, after running successfully, I closed the window (using
the close WM button) and got this:
   $ bitbake my-qt5-image -u depexp -g
   Unable to cleanly stop: No such command

There didn't seem to be any other way to exit the program, so
at least this should be clean.

Are these valid concerns/observations?  Would you entertain patches
for these items?

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

Re: Some 'depexp' nits

[Paul Eggleton]

Hi Gary,

On Thursday 07 November 2013 08:04:47 Gary Thomas wrote:
> I hope this is the correct list.
> 
> I was just using '-u depexp' and noticed a few small things.
>    $ bitbake my-qt5-image -u depexp
>    This UI is only compatible with the -g option
> 
> Perhaps this should be worded more strongly, like this?
>    This UI requires the -g option

Sounds like a good idea yes.

> Also, after running successfully, I closed the window (using
> the close WM button) and got this:
>    $ bitbake my-qt5-image -u depexp -g
>    Unable to cleanly stop: No such command
> 
> There didn't seem to be any other way to exit the program, so
> at least this should be clean.

There is now a bug open for the latter issue:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=5445

> Are these valid concerns/observations?  Would you entertain patches
> for these items?

Yes, that would be great.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre

Re: Some 'depexp' nits

[Gary Thomas]

On 2013-11-07 09:25, Paul Eggleton wrote:
> Hi Gary,
>
> On Thursday 07 November 2013 08:04:47 Gary Thomas wrote:
>> I hope this is the correct list.
>>
>> I was just using '-u depexp' and noticed a few small things.
>>     $ bitbake my-qt5-image -u depexp
>>     This UI is only compatible with the -g option
>>
>> Perhaps this should be worded more strongly, like this?
>>     This UI requires the -g option
>
> Sounds like a good idea yes.
>
>> Also, after running successfully, I closed the window (using
>> the close WM button) and got this:
>>     $ bitbake my-qt5-image -u depexp -g
>>     Unable to cleanly stop: No such command
>>
>> There didn't seem to be any other way to exit the program, so
>> at least this should be clean.
>
> There is now a bug open for the latter issue:
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=5445
>
>> Are these valid concerns/observations?  Would you entertain patches
>> for these items?
>
> Yes, that would be great.

Can I send them against the Poky/Yocto tree?  Or should it be the
separate bitbake tree (which is where?)?

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

Re: Some 'depexp' nits

[Chris Larson]

[-- Attachment #1: Type: text/plain, Size: 1570 bytes --]

On Thu, Nov 7, 2013 at 9:36 AM, Gary Thomas <gary@mlbassoc.com> wrote:

> On 2013-11-07 09:25, Paul Eggleton wrote:
>
>> Hi Gary,
>>
>> On Thursday 07 November 2013 08:04:47 Gary Thomas wrote:
>>
>>> I hope this is the correct list.
>>>
>>> I was just using '-u depexp' and noticed a few small things.
>>>     $ bitbake my-qt5-image -u depexp
>>>     This UI is only compatible with the -g option
>>>
>>> Perhaps this should be worded more strongly, like this?
>>>     This UI requires the -g option
>>>
>>
>> Sounds like a good idea yes.
>>
>>  Also, after running successfully, I closed the window (using
>>> the close WM button) and got this:
>>>     $ bitbake my-qt5-image -u depexp -g
>>>     Unable to cleanly stop: No such command
>>>
>>> There didn't seem to be any other way to exit the program, so
>>> at least this should be clean.
>>>
>>
>> There is now a bug open for the latter issue:
>> https://bugzilla.yoctoproject.org/show_bug.cgi?id=5445
>>
>>  Are these valid concerns/observations?  Would you entertain patches
>>> for these items?
>>>
>>
>> Yes, that would be great.
>>
>
> Can I send them against the Poky/Yocto tree?  Or should it be the
> separate bitbake tree (which is where?)?


http://git.openembedded.org/, mirrored at https://github.com/openembedded/.
Submit the patches against the separate bitbake repo to the bitbake-devel
list.
-- 
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics

[-- Attachment #2: Type: text/html, Size: 2578 bytes --]

Re: Some 'depexp' nits

[Gary Thomas]

On 2013-11-07 09:46, Chris Larson wrote:
>
> On Thu, Nov 7, 2013 at 9:36 AM, Gary Thomas <gary@mlbassoc.com <mailto:gary@mlbassoc.com>> wrote:
>
>     On 2013-11-07 09:25, Paul Eggleton wrote:
>
>         Hi Gary,
>
>         On Thursday 07 November 2013 08:04:47 Gary Thomas wrote:
>
>             I hope this is the correct list.
>
>             I was just using '-u depexp' and noticed a few small things.
>                  $ bitbake my-qt5-image -u depexp
>                  This UI is only compatible with the -g option
>
>             Perhaps this should be worded more strongly, like this?
>                  This UI requires the -g option
>
>
>         Sounds like a good idea yes.
>
>             Also, after running successfully, I closed the window (using
>             the close WM button) and got this:
>                  $ bitbake my-qt5-image -u depexp -g
>                  Unable to cleanly stop: No such command
>
>             There didn't seem to be any other way to exit the program, so
>             at least this should be clean.
>
>
>         There is now a bug open for the latter issue:
>         https://bugzilla.yoctoproject.__org/show_bug.cgi?id=5445 <https://bugzilla.yoctoproject.org/show_bug.cgi?id=5445>
>
>             Are these valid concerns/observations?  Would you entertain patches
>             for these items?
>
>
>         Yes, that would be great.
>
>
>     Can I send them against the Poky/Yocto tree?  Or should it be the
>     separate bitbake tree (which is where?)?
>
>
> http://git.openembedded.org/, mirrored at https://github.com/openembedded/. Submit the patches against the separate bitbake repo to the bitbake-devel list.

I sent a patch, but I never received it from the list although
I can find it in the list archives.  This made me think I had
messed up somehow, so I ended up sending it three times :-(

Did you (or anyone) actually see it?  Did I do something wrong?

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

Re: Some 'depexp' nits

[Burton, Ross]

On 8 November 2013 12:28, Gary Thomas <gary@mlbassoc.com> wrote:
> I sent a patch, but I never received it from the list although
> I can find it in the list archives.  This made me think I had
> messed up somehow, so I ended up sending it three times :-(

As it is on the archives it made it to the list...  maybe you
accidently turned off delivery of the list mails, or that list doesn't
send your own messages back to you (I know gmail at least recognises
mails that you sent and doesn't show them in your inbox).


Ross

Re: Some 'depexp' nits

[Gary Thomas]

On 2013-11-08 05:37, Burton, Ross wrote:
> On 8 November 2013 12:28, Gary Thomas <gary@mlbassoc.com> wrote:
>> I sent a patch, but I never received it from the list although
>> I can find it in the list archives.  This made me think I had
>> messed up somehow, so I ended up sending it three times :-(
>
> As it is on the archives it made it to the list...  maybe you
> accidently turned off delivery of the list mails, or that list doesn't
> send your own messages back to you (I know gmail at least recognises
> mails that you sent and doesn't show them in your inbox).

I do get my posts (send from my desk using Thunderbird), but not
it seems patches sent directly from git.  Perhaps they are being
filtered somehow.

So, did you see the patch (by email, not archives)?

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

Re: Some 'depexp' nits

[Burton, Ross]

On 8 November 2013 13:20, Gary Thomas <gary@mlbassoc.com> wrote:
> So, did you see the patch (by email, not archives)?

Personally, I'm not on bitbake-list (yet).

Ross

Re: Some 'depexp' nits

[Richard Purdie]

On Fri, 2013-11-08 at 06:20 -0700, Gary Thomas wrote:
> On 2013-11-08 05:37, Burton, Ross wrote:
> > On 8 November 2013 12:28, Gary Thomas <gary@mlbassoc.com> wrote:
> >> I sent a patch, but I never received it from the list although
> >> I can find it in the list archives.  This made me think I had
> >> messed up somehow, so I ended up sending it three times :-(
> >
> > As it is on the archives it made it to the list...  maybe you
> > accidently turned off delivery of the list mails, or that list doesn't
> > send your own messages back to you (I know gmail at least recognises
> > mails that you sent and doesn't show them in your inbox).
> 
> I do get my posts (send from my desk using Thunderbird), but not
> it seems patches sent directly from git.  Perhaps they are being
> filtered somehow.
> 
> So, did you see the patch (by email, not archives)?

I saw it three times...

Cheers,

Richard