<div dir="ltr"><div><div><div><div><div><div>Hello Ellwood,<br><br></div>I also like the idea of checking for existence in the file system instead of trying to track some other record. Blender currently offers two ways to install addons that I know of:<br><br></div> * Copy the files to a user 2.x/scripts/addons directory (e.g., ~/.config/blender/2.x/scripts/addons in Linux)<br></div> * Use the "Install Addon" button, which just copies the files for you<br><br></div>I see these repositories as another way to copy files to this addons directory (in addition to getting automatic updates).<br><br></div>As for multiple root folders, I do not think this is really possible unless the "addon" is actually a collection of addons. Each addon should be a single module or package. However, maybe others know about some exceptions to this.<br><br></div>--Mitchell<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jul 18, 2017 at 2:41 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">Today I started adding an uninstall function.<br>
<br>
I started with the idea that a list of installed packages would be<br>
stored in a local "repository" (just like a remote repository) at<br>
install time. However, after following that idea for a bit, I felt it<br>
might be better for the definition of "installed" to be based on the<br>
presence (or absence) of the package on the filesystem. This kind of<br>
comes down to whether or not the package manager should be THE only way<br>
to install things, or if copying files into place manually should also work.<br>
<br>
I think I like the latter approach more; it works by definition, rather<br>
than by design. It's also how Atom works.<br>
<br>
A tangential question:<br>
Can a package contain multiple "root" files? (e.g. a zip with multiple<br>
directories at the top level)<br>
It would simplify things to disallow this, but perhaps some existing<br>
addons do this already? If so, is it worth maintaining compatibility<br>
with them?<br>
<br>
Plan for tomorrow: Add file list to repo generation script, finish and<br>
expose uninstall function, start on version grouping.<br>
<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>