poky-extras
Hi Bruce/Darren,
My attention was drawn to the existence of poky-extras. This was really a short term gap filling repository and I think the time has come to remove it. There are basically two chunks of code in there.
The meta-linaro pieces in there haven't been touched in two years and are therefore dead. I think we should delete them to alleviate any confusion.
The kernel pieces have been touched more recently. Some moved into the core, mostly its just example boiler plate type code now. I think this needs moving to a better named repository if its still wanted/useful, or we delete it. I personally don't have a strong preference.
Can someone take care of sorting this out?
I did notice there is an empty checksums.ini file in there!
Cheers,
Richard
Quoted 10 lines · Richard Purdie
Hi Bruce/Darren,
My attention was drawn to the existence of poky-extras. This was really a short term gap filling repository and I think the time has come to remove it. There are basically two chunks of code in there.
The meta-linaro pieces in there haven't been touched in two years and are therefore dead. I think we should delete them to alleviate any confusion.
Quoted 6 lines
The kernel pieces have been touched more recently. Some moved into the core, mostly its just example boiler plate type code now. I think this needs moving to a better named repository if its still wanted/useful, or we delete it. I personally don't have a strong preference.
Can someone take care of sorting this out?
I can take care of finding it a new home. I use the repo daily, and keep bumping it with examples with each new kernel update or release. I was working on some urlremapper code for the layer, to replace the old boiler plate "uncomment this" examples that are current in the recipes .. that work has been backgrounded, but I can pick it up again as part of relocating the changes.
I'm out of the office for the next week and a half, but can have a look after that. Does that timeframe work ?
Bruce
Quoted 7 lines
I did notice there is an empty checksums.ini file in there!
Cheers,
Richard
Quoted 25 lines · Bruce Ashfield
Quoted 10 lines · Richard Purdie
Hi Bruce/Darren,
My attention was drawn to the existence of poky-extras. This was really a short term gap filling repository and I think the time has come to remove it. There are basically two chunks of code in there.
The meta-linaro pieces in there haven't been touched in two years and are therefore dead. I think we should delete them to alleviate any confusion.
Quoted 6 lines
The kernel pieces have been touched more recently. Some moved into the core, mostly its just example boiler plate type code now. I think this needs moving to a better named repository if its still wanted/useful, or we delete it. I personally don't have a strong preference.
Can someone take care of sorting this out?
I can take care of finding it a new home. I use the repo daily, and keep bumping it with examples with each new kernel update or release. I was working on some urlremapper code for the layer, to replace the old boiler plate "uncomment this" examples that are current in the recipes .. that work has been backgrounded, but I can pick it up again as part of relocating the changes.
Quoted 2 lines
I'm out of the office for the next week and a half, but can have a look after that. Does that timeframe work ?
Yes, its not urgent and I don't want to remove something people use. I do think that this would better as a meta-yocto-kernel or something similar. How about we simply rename it to that and delete meta-linaro from it?
Cheers,
Richard
Quoted 26 lines · Richard Purdie
Quoted 25 lines · Bruce Ashfield
Quoted 10 lines · Richard Purdie
Hi Bruce/Darren,
My attention was drawn to the existence of poky-extras. This was really a short term gap filling repository and I think the time has come to remove it. There are basically two chunks of code in there.
The meta-linaro pieces in there haven't been touched in two years and are therefore dead. I think we should delete them to alleviate any confusion.
Quoted 6 lines
The kernel pieces have been touched more recently. Some moved into the core, mostly its just example boiler plate type code now. I think this needs moving to a better named repository if its still wanted/useful, or we delete it. I personally don't have a strong preference.
Can someone take care of sorting this out?
I can take care of finding it a new home. I use the repo daily, and keep bumping it with examples with each new kernel update or release. I was working on some urlremapper code for the layer, to replace the old boiler plate "uncomment this" examples that are current in the recipes .. that work has been backgrounded, but I can pick it up again as part of relocating the changes.
Quoted 7 lines
Quoted 2 lines
I'm out of the office for the next week and a half, but can have a look after that. Does that timeframe work ?
Yes, its not urgent and I don't want to remove something people use. I do think that this would better as a meta-yocto-kernel or something similar. How about we simply rename it to that and delete meta-linaro from it?
Agreed. That's an effective way to clarify what's left in the layer. I'll take care of cleaning up the contents later.
If it's just the rename, I assume Michael can take care of it and there's nothing immediate for me to do.
Cheers,
Bruce
Quoted 6 lines
Cheers,
Richard
All I need is the name to make some initial changes.
Scott
Quoted 67 lines
-----Original Message-----
From: Bruce Ashfield [mailto:[email protected]]
Sent: Friday, June 28, 2013 6:03 AM
To: Richard Purdie
Cc: Hart, Darren; yocto; Rifenbark, Scott M; Michael Halstead
Subject: Re: poky-extrasQuoted 5 lines · Richard Purdie
Quoted 4 lines · Bruce Ashfield
Quoted 3 lines · Richard Purdie
Hi Bruce/Darren,
My attention was drawn to the existence of poky-extras. This was
really
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
a short term gap filling repository and I think the time has come to remove it. There are basically two chunks of code in there.
The meta-linaro pieces in there haven't been touched in two years
and
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
are therefore dead. I think we should delete them to alleviate any confusion.
The kernel pieces have been touched more recently. Some moved into
the
Quoted 1 line
Quoted 1 line
Quoted 1 line
core, mostly its just example boiler plate type code now. I think
this
Quoted 1 line
Quoted 1 line
Quoted 1 line
needs moving to a better named repository if its still
wanted/useful, or
Quoted 5 lines
Quoted 5 lines
Quoted 3 lines
we delete it. I personally don't have a strong preference.
Can someone take care of sorting this out?
I can take care of finding it a new home. I use the repo daily, and
keep
Quoted 1 line
Quoted 1 line
bumping it with examples with each new kernel update or release. I
was
Quoted 2 lines
Quoted 2 lines
working on some urlremapper code for the layer, to replace the old boiler plate "uncomment this" examples that are current in the
recipes ..
Quoted 4 lines
Quoted 4 lines
that work has been backgrounded, but I can pick it up again as part of relocating the changes.
I'm out of the office for the next week and a half, but can have a
look
Quoted 6 lines
Quoted 1 line
after that. Does that timeframe work ?
Yes, its not urgent and I don't want to remove something people use. I do think that this would better as a meta-yocto-kernel or something similar. How about we simply rename it to that and delete meta-linaro from it?
Agreed. That's an effective way to clarify what's left in the layer. I'll take care of cleaning up the contents later.
If it's just the rename, I assume Michael can take care of it and there's nothing immediate for me to do.
Cheers,
Bruce
Quoted 6 lines
Cheers,
Richard
Quoted 1 line · Scott M
All I need is the name to make some initial changes.
Personally, I'm fine with 'meta-yocto-kernel'. Naming things is never easy, so I won't agonize over whether or not an "extras" should be on the end. But the name should be clear that it isn't the main yocto kernel, it's just a few crappy bbappends that make working with it locally easier for some :)
So my only counter proposal is: meta-yocto-kernel-extras
I'm going to de-crapify the bbappends so they are more useful, and have started on that work, but haven't finished it yet.
Bruce
Quoted 71 lines
Scott
Quoted 67 lines
-----Original Message-----
From: Bruce Ashfield [mailto:[email protected]]
Sent: Friday, June 28, 2013 6:03 AM
To: Richard Purdie
Cc: Hart, Darren; yocto; Rifenbark, Scott M; Michael Halstead
Subject: Re: poky-extrasQuoted 5 lines · Richard Purdie
Quoted 4 lines · Bruce Ashfield
Quoted 3 lines · Richard Purdie
Hi Bruce/Darren,
My attention was drawn to the existence of poky-extras. This was
really
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
a short term gap filling repository and I think the time has come to remove it. There are basically two chunks of code in there.
The meta-linaro pieces in there haven't been touched in two years
and
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
are therefore dead. I think we should delete them to alleviate any confusion.
The kernel pieces have been touched more recently. Some moved into
the
Quoted 1 line
Quoted 1 line
Quoted 1 line
core, mostly its just example boiler plate type code now. I think
this
Quoted 1 line
Quoted 1 line
Quoted 1 line
needs moving to a better named repository if its still
wanted/useful, or
Quoted 5 lines
Quoted 5 lines
Quoted 3 lines
we delete it. I personally don't have a strong preference.
Can someone take care of sorting this out?
I can take care of finding it a new home. I use the repo daily, and
keep
Quoted 1 line
Quoted 1 line
bumping it with examples with each new kernel update or release. I
was
Quoted 2 lines
Quoted 2 lines
working on some urlremapper code for the layer, to replace the old boiler plate "uncomment this" examples that are current in the
recipes ..
Quoted 4 lines
Quoted 4 lines
that work has been backgrounded, but I can pick it up again as part of relocating the changes.
I'm out of the office for the next week and a half, but can have a
look
Quoted 6 lines
Quoted 1 line
after that. Does that timeframe work ?
Yes, its not urgent and I don't want to remove something people use. I do think that this would better as a meta-yocto-kernel or something similar. How about we simply rename it to that and delete meta-linaro from it?
Agreed. That's an effective way to clarify what's left in the layer. I'll take care of cleaning up the contents later.
If it's just the rename, I assume Michael can take care of it and there's nothing immediate for me to do.
Cheers,
Bruce
Quoted 6 lines
Cheers,
Richard
I would favor adding "extras" into the name then so there is no confusion over it being the main thing.
Quoted 97 lines
-----Original Message-----
From: Bruce Ashfield [mailto:[email protected]]
Sent: Friday, June 28, 2013 6:41 AM
To: Rifenbark, Scott M
Cc: Richard Purdie; Hart, Darren; yocto; Michael Halstead
Subject: Re: poky-extrasQuoted 1 line · Scott M
All I need is the name to make some initial changes.
Personally, I'm fine with 'meta-yocto-kernel'. Naming things is never easy, so I won't agonize over whether or not an "extras" should be on the end. But the name should be clear that it isn't the main yocto kernel, it's just a few crappy bbappends that make working with it locally easier for some :)
So my only counter proposal is: meta-yocto-kernel-extras
I'm going to de-crapify the bbappends so they are more useful, and have started on that work, but haven't finished it yet.
Bruce
Quoted 18 lines
Scott
Quoted 15 lines
-----Original Message-----
From: Bruce Ashfield [mailto:[email protected]]
Sent: Friday, June 28, 2013 6:03 AM
To: Richard Purdie
Cc: Hart, Darren; yocto; Rifenbark, Scott M; Michael Halstead
Subject: Re: poky-extrasQuoted 5 lines · Richard Purdie
Quoted 4 lines · Bruce Ashfield
Quoted 3 lines · Richard Purdie
Hi Bruce/Darren,
My attention was drawn to the existence of poky-extras. This was
really
Quoted 1 line
Quoted 1 line
Quoted 1 line
a short term gap filling repository and I think the time has come
to
Quoted 24 lines
Quoted 24 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
remove it. There are basically two chunks of code in there.
The meta-linaro pieces in there haven't been touched in two years
and
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
are therefore dead. I think we should delete them to alleviate any confusion.
The kernel pieces have been touched more recently. Some moved into
the
Quoted 1 line
Quoted 1 line
Quoted 1 line
core, mostly its just example boiler plate type code now. I think
this
Quoted 1 line
Quoted 1 line
Quoted 1 line
needs moving to a better named repository if its still
wanted/useful, or
Quoted 5 lines
Quoted 5 lines
Quoted 3 lines
we delete it. I personally don't have a strong preference.
Can someone take care of sorting this out?
I can take care of finding it a new home. I use the repo daily, and
keep
Quoted 1 line
Quoted 1 line
bumping it with examples with each new kernel update or release. I
was
Quoted 2 lines
Quoted 2 lines
working on some urlremapper code for the layer, to replace the old boiler plate "uncomment this" examples that are current in the
recipes ..
Quoted 8 lines
Quoted 8 lines
Quoted 4 lines
Quoted 4 lines
that work has been backgrounded, but I can pick it up again as part of relocating the changes.
I'm out of the office for the next week and a half, but can have a
look
Quoted 3 lines
Quoted 1 line
after that. Does that timeframe work ?
Yes, its not urgent and I don't want to remove something people use.
I
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
do think that this would better as a meta-yocto-kernel or something similar. How about we simply rename it to that and delete meta-
linaro
Quoted 19 lines
Quoted 18 lines
Quoted 1 line
from it?
Agreed. That's an effective way to clarify what's left in the layer. I'll take care of cleaning up the contents later.
If it's just the rename, I assume Michael can take care of it and there's nothing immediate for me to do.
Cheers,
Bruce
Quoted 6 lines
Cheers,
Richard
Quoted 9 lines · Bruce Ashfield
Quoted 1 line · Scott M
All I need is the name to make some initial changes.
Personally, I'm fine with 'meta-yocto-kernel'. Naming things is never easy, so I won't agonize over whether or not an "extras" should be on the end. But the name should be clear that it isn't the main yocto kernel, it's just a few crappy bbappends that make working with it locally easier for some :)
Quoted 4 lines
So my only counter proposal is: meta-yocto-kernel-extras
I'm going to de-crapify the bbappends so they are more useful, and have started on that work, but haven't finished it yet.
No strong feelings here. I just wiped out meta-linaro from there (hoping Darren won't mind) and that checksums.ini file.
Cheers,
Richard
Quoted 10 lines · Richard Purdie
Quoted 9 lines · Bruce Ashfield
Quoted 1 line · Scott M
All I need is the name to make some initial changes.
Personally, I'm fine with 'meta-yocto-kernel'. Naming things is never easy, so I won't agonize over whether or not an "extras" should be on the end. But the name should be clear that it isn't the main yocto kernel, it's just a few crappy bbappends that make working with it locally easier for some :)
Quoted 7 lines
Quoted 4 lines
So my only counter proposal is: meta-yocto-kernel-extras
I'm going to de-crapify the bbappends so they are more useful, and have started on that work, but haven't finished it yet.
No strong feelings here. I just wiped out meta-linaro from there (hoping Darren won't mind) and that checksums.ini file.
That's fine, I was just thinking about that last week when I saw Linaro has a meta-linaro. That's where it belongs, so buh-bye. :-)
Signature · 3 lines
Darren Hart Intel Open Source Technology Center Yocto Project - Technical Lead - Linux Kernel
Hi,
I updated the dev-manual section that tells the user what is in this repo and shows an example of cloning it. Nothing changes except for the name, which I switched to 'meta-yocto-kernel-extras'. To me, it appears that the contents of the repo still contain the kernel BitBake append files that you edit to point to your locally modified kernel source files as described in the text. Within the entire YP documentation set, this little area is the only reference to the old 'poky-extras' repo. Here is the link to see the changes - http://www.yoctoproject.org/docs/1.5/dev-manual/dev-manual.html#meta-yocto-kernel-extras-repo.
I am assuming that the name of the repo will indeed be changed to 'meta-yocto-kernel-extras'. If I don't hear from anyone, I will assume everything is good.
Thanks,
Scott
Quoted 34 lines
-----Original Message-----
From: Hart, Darren
Sent: Friday, June 28, 2013 10:08 PM
To: Richard Purdie
Cc: Bruce Ashfield; Rifenbark, Scott M; yocto; Michael Halstead
Subject: Re: poky-extrasQuoted 10 lines · Richard Purdie
Quoted 9 lines · Bruce Ashfield
Quoted 1 line · Scott M
All I need is the name to make some initial changes.
Personally, I'm fine with 'meta-yocto-kernel'. Naming things is never easy, so I won't agonize over whether or not an "extras" should be on the end. But the name should be clear that it isn't the main yocto kernel, it's just a few crappy bbappends that make working with it locally easier for some :)
Quoted 6 lines
Quoted 4 lines
So my only counter proposal is: meta-yocto-kernel-extras
I'm going to de-crapify the bbappends so they are more useful, and have started on that work, but haven't finished it yet.
No strong feelings here. I just wiped out meta-linaro from there
(hoping
Quoted 1 line
Darren won't mind) and that checksums.ini file.
That's fine, I was just thinking about that last week when I saw Linaro has a meta-linaro. That's where it belongs, so buh-bye. :-)
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Technical Lead - Linux Kernel
I can change the name shortly. Is there any reason to keep a read-only copy available at the current location temporarily?
Michael Halstead
Yocto Project / Sys Admin
Quoted 40 lines · Scott M
Hi,
I updated the dev-manual section that tells the user what is in this repo and shows an example of cloning it. Nothing changes except for the name, which I switched to 'meta-yocto-kernel-extras'. To me, it appears that the contents of the repo still contain the kernel BitBake append files that you edit to point to your locally modified kernel source files as described in the text. Within the entire YP documentation set, this little area is the only reference to the old 'poky-extras' repo. Here is the link to see the changes - http://www.yoctoproject.org/docs/1.5/dev-manual/dev-manual.html#meta-yocto-kernel-extras-repo.
I am assuming that the name of the repo will indeed be changed to 'meta-yocto-kernel-extras'. If I don't hear from anyone, I will assume everything is good.
Thanks,
ScottQuoted 31 lines
-----Original Message-----
From: Hart, Darren
Sent: Friday, June 28, 2013 10:08 PM
To: Richard Purdie
Cc: Bruce Ashfield; Rifenbark, Scott M; yocto; Michael Halstead
Subject: Re: poky-extrasQuoted 9 lines · Richard Purdie
Quoted 8 lines · Bruce Ashfield
Quoted 1 line · Scott M
All I need is the name to make some initial changes.
Personally, I'm fine with 'meta-yocto-kernel'. Naming things is never easy, so I won't agonize over whether or not an "extras" should be on the end. But the name should be clear that it isn't the main yocto kernel, it's just a few crappy bbappends that make working with it locally easier for some :)
Quoted 5 lines
Quoted 4 lines
So my only counter proposal is: meta-yocto-kernel-extras
I'm going to de-crapify the bbappends so they are more useful, and have started on that work, but haven't finished it yet.
No strong feelings here. I just wiped out meta-linaro from there
(hoping
Quoted 1 line
Darren won't mind) and that checksums.ini file.
That's fine, I was just thinking about that last week when I saw Linaro has a meta-linaro. That's where it belongs, so buh-bye. :-)
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Technical Lead - Linux Kernel
Quoted 2 lines · Michael Halstead
I can change the name shortly. Is there any reason to keep a read-only copy available at the current location temporarily?
Not really. Unless Bruce is using it in some automated scripts that need to be updated.
--
Darren
Quoted 47 lines
Michael Halstead
Yocto Project / Sys AdminQuoted 40 lines · Scott M
Hi,
I updated the dev-manual section that tells the user what is in this repo and shows an example of cloning it. Nothing changes except for the name, which I switched to 'meta-yocto-kernel-extras'. To me, it appears that the contents of the repo still contain the kernel BitBake append files that you edit to point to your locally modified kernel source files as described in the text. Within the entire YP documentation set, this little area is the only reference to the old 'poky-extras' repo. Here is the link to see the changes - http://www.yoctoproject.org/docs/1.5/dev-manual/dev-manual.html#meta-yocto-kernel-extras-repo.
I am assuming that the name of the repo will indeed be changed to 'meta-yocto-kernel-extras'. If I don't hear from anyone, I will assume everything is good.
Thanks,
ScottQuoted 31 lines
-----Original Message-----
From: Hart, Darren
Sent: Friday, June 28, 2013 10:08 PM
To: Richard Purdie
Cc: Bruce Ashfield; Rifenbark, Scott M; yocto; Michael Halstead
Subject: Re: poky-extrasQuoted 9 lines · Richard Purdie
Quoted 8 lines · Bruce Ashfield
Quoted 1 line · Scott M
All I need is the name to make some initial changes.
Personally, I'm fine with 'meta-yocto-kernel'. Naming things is never easy, so I won't agonize over whether or not an "extras" should be on the end. But the name should be clear that it isn't the main yocto kernel, it's just a few crappy bbappends that make working with it locally easier for some :)
Quoted 5 lines
Quoted 4 lines
So my only counter proposal is: meta-yocto-kernel-extras
I'm going to de-crapify the bbappends so they are more useful, and have started on that work, but haven't finished it yet.
No strong feelings here. I just wiped out meta-linaro from there
(hoping
Quoted 1 line
Darren won't mind) and that checksums.ini file.
That's fine, I was just thinking about that last week when I saw Linaro has a meta-linaro. That's where it belongs, so buh-bye. :-)
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Technical Lead - Linux Kernel
Signature · 3 lines
Darren Hart Intel Open Source Technology Center Yocto Project - Technical Lead - Linux Kernel
Quoted 8 lines · Darren Hart
Quoted 2 lines · Michael Halstead
I can change the name shortly. Is there any reason to keep a read-only copy available at the current location temporarily?
Not really. Unless Bruce is using it in some automated scripts that need to be updated.
--
Darren
The name has been changed. Shall we update the description or is "Supplementary metadata layers to extend the Poky core
<https://git.yoctoproject.org/cgit/cgit.cgi/meta-yocto-kernel-extras/>"
still appropriate?
Thanks,
Michael Halstead
Yocto Project / Sys Admin
Quoted 45 lines
Quoted 45 lines
Michael Halstead
Yocto Project / Sys AdminQuoted 40 lines · Scott M
Hi,
I updated the dev-manual section that tells the user what is in this repo and shows an example of cloning it. Nothing changes except for the name, which I switched to 'meta-yocto-kernel-extras'. To me, it appears that the contents of the repo still contain the kernel BitBake append files that you edit to point to your locally modified kernel source files as described in the text. Within the entire YP documentation set, this little area is the only reference to the old 'poky-extras' repo. Here is the link to see the changes - http://www.yoctoproject.org/docs/1.5/dev-manual/dev-manual.html#meta-yocto-kernel-extras-repo.
I am assuming that the name of the repo will indeed be changed to 'meta-yocto-kernel-extras'. If I don't hear from anyone, I will assume everything is good.
Thanks,
ScottQuoted 31 lines
-----Original Message-----
From: Hart, Darren
Sent: Friday, June 28, 2013 10:08 PM
To: Richard Purdie
Cc: Bruce Ashfield; Rifenbark, Scott M; yocto; Michael Halstead
Subject: Re: poky-extrasQuoted 9 lines · Richard Purdie
Quoted 8 lines · Bruce Ashfield
Quoted 1 line · Scott M
All I need is the name to make some initial changes.
Personally, I'm fine with 'meta-yocto-kernel'. Naming things is never easy, so I won't agonize over whether or not an "extras" should be on the end. But the name should be clear that it isn't the main yocto kernel, it's just a few crappy bbappends that make working with it locally easier for some :)
Quoted 5 lines
Quoted 4 lines
So my only counter proposal is: meta-yocto-kernel-extras
I'm going to de-crapify the bbappends so they are more useful, and have started on that work, but haven't finished it yet.
No strong feelings here. I just wiped out meta-linaro from there
(hoping
Quoted 1 line
Darren won't mind) and that checksums.ini file.
That's fine, I was just thinking about that last week when I saw Linaro has a meta-linaro. That's where it belongs, so buh-bye. :-)
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Technical Lead - Linux Kernel
Quoted 11 lines · Michael Halstead
Quoted 6 lines · Darren Hart
Quoted 2 lines · Michael Halstead
I can change the name shortly. Is there any reason to keep a read-only copy available at the current location temporarily?
Not really. Unless Bruce is using it in some automated scripts that need to be updated.
The name has been changed. Shall we update the description or is "Supplementary metadata layers to extend the Poky core" still appropriate?
We can change it to something like "Supplementary linux-yocto kernel development metadata" unless Bruce has any better description.
Cheers,
Richard
Quoted 9 lines · Richard Purdie
Quoted 8 lines · Michael Halstead
Quoted 6 lines · Darren Hart
Quoted 2 lines · Michael Halstead
I can change the name shortly. Is there any reason to keep a read-only copy available at the current location temporarily?
Not really. Unless Bruce is using it in some automated scripts that need to be updated.
Quoted 6 lines
Quoted 3 lines
The name has been changed. Shall we update the description or is "Supplementary metadata layers to extend the Poky core" still appropriate?
We can change it to something like "Supplementary linux-yocto kernel development metadata" unless Bruce has any better description.
Bruce is out this week with limited email access. He isn't terribly picky on naming and that description should work as good as any.
Signature · 3 lines
Darren Hart Intel Open Source Technology Center Yocto Project - Technical Lead - Linux Kernel
I think the name is meta-yocto-kernel-extras. That is what I have pushed to the docs.
Scott
Quoted 34 lines
-----Original Message-----
From: Hart, Darren
Sent: Monday, July 01, 2013 10:28 AM
To: Richard Purdie
Cc: Michael Halstead; Bruce Ashfield; Rifenbark, Scott M; yocto; Zanussi, Tom
Subject: Re: poky-extrasQuoted 4 lines · Richard Purdie
Quoted 3 lines · Michael Halstead
Quoted 2 lines · Darren Hart
Quoted 1 line · Michael Halstead
I can change the name shortly. Is there any reason to keep a
read-only
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 1 line
copy available at the current location temporarily?
Not really. Unless Bruce is using it in some automated scripts
that need
Quoted 9 lines
Quoted 6 lines
Quoted 2 lines
to be updated.
The name has been changed. Shall we update the description or is "Supplementary metadata layers to extend the Poky core" still appropriate?
We can change it to something like "Supplementary linux-yocto kernel development metadata" unless Bruce has any better description.
Bruce is out this week with limited email access. He isn't terribly picky on naming and that description should work as good as any.
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Technical Lead - Linux Kernel
Quoted 14 lines · Darren Hart
Quoted 13 lines · Richard Purdie
Quoted 11 lines · Michael Halstead
Quoted 6 lines · Darren Hart
Quoted 2 lines · Michael Halstead
I can change the name shortly. Is there any reason to keep a read-only copy available at the current location temporarily?
Not really. Unless Bruce is using it in some automated scripts that need to be updated.
The name has been changed. Shall we update the description or is "Supplementary metadata layers to extend the Poky core" still appropriate?
Quoted 5 lines
Quoted 2 lines
We can change it to something like "Supplementary linux-yocto kernel development metadata" unless Bruce has any better description.
Bruce is out this week with limited email access. He isn't terribly picky on naming and that description should work as good as any.
Yup, and apparently my access when it comes back .. makes me read email in random order!
The description and resolution are all fine with me.
Bruce
Quoted 10 lines
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Technical Lead - Linux Kernel_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto
--
"Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end"
Quoted 2 lines · Michael Halstead
I can change the name shortly. Is there any reason to keep a read-only copy available at the current location temporarily?
It can't hurt, but I also can't think of a really compelling reason that it is absolutely required. By the name alone, we can be sure that nothing core to a build uses it, or fetches it, and that anyone with a copy can continue to use their local copy under the current name .. until they track down the new repo name.
Cheers,
Bruce
Quoted 48 lines
Michael Halstead
Yocto Project / Sys AdminQuoted 40 lines · Scott M
Hi,
I updated the dev-manual section that tells the user what is in this repo and shows an example of cloning it. Nothing changes except for the name, which I switched to 'meta-yocto-kernel-extras'. To me, it appears that the contents of the repo still contain the kernel BitBake append files that you edit to point to your locally modified kernel source files as described in the text. Within the entire YP documentation set, this little area is the only reference to the old 'poky-extras' repo. Here is the link to see the changes - http://www.yoctoproject.org/docs/1.5/dev-manual/dev-manual.html#meta-yocto-kernel-extras-repo.
I am assuming that the name of the repo will indeed be changed to 'meta-yocto-kernel-extras'. If I don't hear from anyone, I will assume everything is good.
Thanks,
ScottQuoted 31 lines
-----Original Message-----
From: Hart, Darren
Sent: Friday, June 28, 2013 10:08 PM
To: Richard Purdie
Cc: Bruce Ashfield; Rifenbark, Scott M; yocto; Michael Halstead
Subject: Re: poky-extrasQuoted 9 lines · Richard Purdie
Quoted 8 lines · Bruce Ashfield
Quoted 1 line · Scott M
All I need is the name to make some initial changes.
Personally, I'm fine with 'meta-yocto-kernel'. Naming things is never easy, so I won't agonize over whether or not an "extras" should be on the end. But the name should be clear that it isn't the main yocto kernel, it's just a few crappy bbappends that make working with it locally easier for some :)
Quoted 5 lines
Quoted 4 lines
So my only counter proposal is: meta-yocto-kernel-extras
I'm going to de-crapify the bbappends so they are more useful, and have started on that work, but haven't finished it yet.
No strong feelings here. I just wiped out meta-linaro from there
(hoping
Quoted 1 line
Darren won't mind) and that checksums.ini file.
That's fine, I was just thinking about that last week when I saw Linaro has a meta-linaro. That's where it belongs, so buh-bye. :-)
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Technical Lead - Linux Kernel
Quoted 5 lines
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto
--
"Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end"