<div dir="ltr"><div class="gmail_default" style="font-family:tahoma,sans-serif">This version is clear and explicit for me. But I understand that this may be a bit confusing for some users.<br><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif">
I have more comments below, for Scott's concerns.<br>
<br>Thank you, guys!<br></div><div class="gmail_default" style="font-family:tahoma,sans-serif">Alex<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Mar 27, 2014 at 10:30 AM, Barros Pena, Belen <span dir="ltr"><<a href="mailto:belen.barros.pena@intel.com" target="_blank">belen.barros.pena@intel.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Thanks, Scott. Alex should review it when he has a chance.<br>
<br>
Cheers<br>
<br>
Belén<br>
<div><div><br>
On 26/03/2014 12:31, "Scott Rifenbark" <<a href="mailto:srifenbark@gmail.com" target="_blank">srifenbark@gmail.com</a>> wrote:<br>
<br>
>Hi Belen,<br>
><br>
><br>
>Here is a re-written version. Â I did not know how to cast that very last<br>
>sentence. Â It seemed to come from nowhere. Â The piece talks about two<br>
>commands, the build directory and two files (toaster.sqlite and<br>
>toastermain/setting.py). Â The manage.py thing comes<br>
> out of the blue. Â So, I just put it at the end. Â I imagine there is some<br>
>relationship between it and the rest of the information. Â If I knew the<br>
>relationship I could work it into the main stuff a little better.<br></div></div></blockquote><div><br><div class="gmail_default" style="font-family:tahoma,sans-serif">​<br></div><div class="gmail_default" style="font-family:tahoma,sans-serif">
[Alex]<br></div><div class="gmail_default" style="font-family:tahoma,sans-serif">manage.py is ​referring to this file in the tree: bitbake/lib/toaster/manage.py<br></div><div class="gmail_default" style="font-family:tahoma,sans-serif">
It's the main Django control script in the toaster project. Maybe we should<br>make this clear, and spell out the entire name ?<br></div><div class="gmail_default" style="font-family:tahoma,sans-serif"><br></div></div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>
<div>
><br>
><br>
><br>
>Also, I am not sure if the "build/" directory means literally the default<br>
>build directory, which is named "build", or if it means the build<br></div></div></blockquote><div> </div><div><div class="gmail_default" style="font-family:tahoma,sans-serif;display:inline">​[Alex] It's ​</div>
 <div class="gmail_default" style="font-family:tahoma,sans-serif;display:inline">​the build directory in the general sense, I assumed that the users<br>don't change this name, hence the 'build/' reference. How is it called in other <br>
pieces of documentation ?<br><br>​</div></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div>
>directory in a general sense, which could be named I suppose whatever the<br>
>user wants it to be named.<br>
><br>
><br>
>Finally, I am not mentioning the words "pre-requisites" or "requirements"<br>
>in the re-write even though the original text cast the information as<br>
>such. Â Really, what is here doesn't qualify as per-requisites. Â They are<br>
>more like "behaviors".<br>
><br>
><br>
>Hope this helps. Â Let me know if you need further work on it.<br>
><br>
><br>
>Scott<br>
><br>
><br>
>=============================================<br>
><br>
><br>
>When using the buildslist and builddelete commands, you need to consider<br>
>the following:<br>
><br>
><br>
>* For default configurations, your working directory must be the "build"<br>
>directory. Â Using these command from the "build" directory allows Toaster<br>
>to find the "toaster.sqlite" file, which is located in the "build"<br>
>directory.<br>
><br>
><br>
>* For other database configurations, it is possible that you can use<br>
>these commands from a directory other than the "build" directory. Â To do<br>
>so, the "toastermain/settings.py" file must be configured to point to the<br>
>correct database backend.<br>
><br>
><br>
>It is recommended to always call "manage.py" from the "build" directory.<br>
><br>
>==========================================================<br>
><br>
><br>
>On Wed, Mar 26, 2014 at 5:23 AM, Barros Pena, Belen<br>
><<a href="mailto:belen.barros.pena@intel.com" target="_blank">belen.barros.pena@intel.com</a>> wrote:<br>
><br>
>Hi Scott,<br>
><br>
>There is some more detail we need to add to the explanation about how to<br>
>delete builds from the Toaster database. This is Alex's explanation:<br>
><br>
>The buildslist and builddelete commands have some prerequisites in terms<br>
>of how they're invoked:<br>
><br>
>* in the default configuration, the current working directory needs to be<br>
>the 'build/' directory as to let the system find the "toaster.sqlite" file<br>
>in this directory<br>
><br>
>* in other database configuration, it may be possible to invoke from other<br>
>directories, provided that the toastermain/settings.py file is correctly<br>
>configured as to point to the correct database backend.<br>
><br>
>I recommend to always call manage.py from the "build/" directory.<br>
><br>
>Thanks!<br>
><br>
>Belén<br>
><br>
><br>
><br>
>On 19/03/2014 21:55, "Scott Rifenbark" <<a href="mailto:srifenbark@gmail.com" target="_blank">srifenbark@gmail.com</a>> wrote:<br>
><br>
><br>
>>Here is a quick section on deleting a build from the toaster database.<br>
>><br>
>>-----------------------------------<br>
>><br>
>>Deleting a Build from the Toaster Database<br>
>><br>
>><br>
>>You can use the manage.py command, which is located in the<br>
>>/poky/bitbake/lib/toaster directory to identify and delete builds from<br>
>>the Toaster database. Â Follow these steps to delete a build:<br>
>><br>
>><br>
>>1. Identify the build: Â Run the following command from the toaster<br>
>>directory to display a user-readable, tabbed list of build IDs and<br>
>>identification information:<br>
>><br>
>><br>
>> Â Â ./manage.py buildslist<br>
>><br>
>><br>
>>2. Delete a specific build: Using the build ID displayed in the previous<br>
>>step, run the following command to delete a specific build:<br>
>><br>
>><br>
>> Â Â ./manage.py <build_id><br>
>><br>
>><br>
>>The build and all related information is deleted from the Toaster<br>
>>database. Â The deletion operation traverses the ForeignKey relationships<br>
>>recursively.<br>
>><br>
>><br>
>><br>
>><br>
>><br>
>>On Wed, Mar 19, 2014 at 10:52 AM, Barros Pena, Belen<br>
>><<a href="mailto:belen.barros.pena@intel.com" target="_blank">belen.barros.pena@intel.com</a>> wrote:<br>
>><br>
>>Hi Scott,<br>
>><br>
>>There is one more thing that needs to be documented: how to delete builds<br>
>>from the Toaster database.<br>
>><br>
>><a href="https://bugzilla.yoctoproject.org/show_bug.cgi?id=4625" target="_blank">https://bugzilla.yoctoproject.org/show_bug.cgi?id=4625</a><br>
>><br>
>>There is a file in the /poky/bitbake/lib/toaster directory called<br>
>>manage.py. You can run that file with additional commands. There are 2<br>
>>commands relevant to delete builds:<br>
>><br>
>>1. buildslist<br>
>>This command is run ./manage.py buildslist and it will show you a<br>
>>user-readable tabbed list of build ids and identification information<br>
>><br>
>>2. builddelete<br>
>>This command is run ./manage.py <build_id> and will delete the build with<br>
>>the specified id AND ALL related information (traversing the ForeignKey<br>
>>relationships recursively) from the database.<br>
>><br>
>>Alex, feel free to add anything that might be missing above.<br>
>><br>
>>Since it looks like pretty much everything related to Toaster will be<br>
>>documented in the wiki for 1.6, we should probably do the same with this<br>
>>one too, but I might add the information to the Toaster manual in the YP<br>
>>website as well.<br>
>><br>
>>If you have any questions, let us know.<br>
>><br>
>>Thanks!<br>
>><br>
>>Belén<br>
>><br>
>><br>
>><br>
>>On 18/03/2014 16:47, "Barros Pena, Belen" <<a href="mailto:belen.barros.pena@intel.com" target="_blank">belen.barros.pena@intel.com</a>><br>
>>wrote:<br>
>><br>
>>>Hi Scott,<br>
>>><br>
>>>As I mentioned, we would like to document how to set up a Toaster<br>
>>>instance<br>
>>>in a remote host. Alex Damian sent an email to the mailing list<br>
>>>explaining<br>
>>>the process back in February. This is it:<br>
>>><br>
>>><a href="https://lists.yoctoproject.org/pipermail/toaster/2014-February/000464.ht" target="_blank">https://lists.yoctoproject.org/pipermail/toaster/2014-February/000464.ht</a><br>
>>>m<br>
>>>l<br>
>>><br>
>>>We are thinking of documenting this in the wiki for the moment, with<br>
>>>maybe<br>
>>>a link to it from the existing Toaster section in the Development<br>
>>>Manual.<br>
>>><br>
>>>Just contact any of us, or the Toaster mailing list, if you have any<br>
>>>questions.<br>
>>><br>
>>>Thanks for your help with this!<br>
>>><br>
>>>Belén<br>
>>><br>
>><br>
>><br>
>>>--<br>
>>>_______________________________________________<br>
>>>toaster mailing list<br>
>>><a href="mailto:toaster@yoctoproject.org" target="_blank">toaster@yoctoproject.org</a><br>
>>><a href="https://lists.yoctoproject.org/listinfo/toaster" target="_blank">https://lists.yoctoproject.org/listinfo/toaster</a><br>
>><br>
>><br>
>><br>
>><br>
>><br>
>><br>
>><br>
>><br>
>><br>
>><br>
>><br>
>><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
<br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br><div dir="ltr">Alex Damian<div>Yocto Project<br></div><div>SSG / OTCÂ </div></div>
</div></div>