<div dir="ltr"><div><div>I do not think it is that important to be able to cache old versions<br></div>most users will not need to go back to an older version of a package,<br>however, they still should be able to install an older version in case<br></div><div>it is necessary .<br></div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><span style="color:rgb(153,153,153)"><span style="color:rgb(0,0,0)">Aaron Carlisle</span><br></span><div><span style="color:rgb(153,153,153)"><br>Picture taker | Bit cruncher | Pixel pusher | Document writer | Artist<br></span></div><div><span style="color:rgb(153,153,153)">Project administrator for the Blender 3D Documentation Project</span></div></div></div></div>
<br><div class="gmail_quote">On Sat, Jul 1, 2017 at 4:26 AM, Ellwood Zwovic <span dir="ltr"><<a href="mailto:gandalf3@blendermonkey.com" target="_blank">gandalf3@blendermonkey.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">My report for week 5:<br>
<a href="https://wiki.blender.org/index.php?title=User:Gandalf3/GSoC_2017/Reports#Week_5" rel="noreferrer" target="_blank">https://wiki.blender.org/<wbr>index.php?title=User:Gandalf3/<wbr>GSoC_2017/Reports#Week_5</a><br>
<br>
== Week 5 ==<br>
<br>
What I did this week:<br>
<br>
* Implemented basic asynchronous communication between blender and<br>
subprocesses.<br>
* Added very basic repository fetching<br>
* Wrote some documentation:<br>
<a href="https://developer.blender.org/diffusion/BPMA/browse/master/README.md" rel="noreferrer" target="_blank">https://developer.blender.org/<wbr>diffusion/BPMA/browse/master/<wbr>README.md</a><br>
<br>
=== Questions ===<br>
<br>
Where should the local package list be stored? Is $BLENDER_USER_CONFIG a<br>
good place?<br>
<br>
On a related note, should package files be kept around even after<br>
installation?<br>
For instance, pacman keeps every package ever downloaded in<br>
/var/cache/pacman/pkg<br>
This allows for fairly painless rollbacks, which is particularly helpful<br>
as the arch repositories don't keep old versions of packages around.<br>
On the other hand, this can easily eat up disk space. Pacman provides<br>
tools for cleaning the cache up, but they must be manually invoked.<br>
<br>
Does this approach seem appropriate for Blender?<br>
Would it be better to clean up such a cache automatically? (e.g.<br>
deleting based on age, or by number of versions behind the current version)<br>
Or would it be preferable to simply not keep a cache at all? (perhaps<br>
making it the repository's responsibility to keep old versions)<br>
<br>
=== Plans for next week ===<br>
<br>
Clean up and extend repository generation and fetching. Implement<br>
package fetching (continued from last week). Get started on real UI.<br>
<br>
<br>
Ellwood<br>
<br>
<br>
______________________________<wbr>_________________<br>
Soc-2017-dev mailing list<br>
<a href="mailto:Soc-2017-dev@blender.org">Soc-2017-dev@blender.org</a><br>
<a href="https://lists.blender.org/mailman/listinfo/soc-2017-dev" rel="noreferrer" target="_blank">https://lists.blender.org/<wbr>mailman/listinfo/soc-2017-dev</a><br>
</blockquote></div><br></div>