<br><br><div class="gmail_quote">On Fri, Jun 3, 2011 at 7:01 PM, Michael Wiktowy <span dir="ltr"><<a href="mailto:michael.wiktowy@gmail.com" target="_blank">michael.wiktowy@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>On Fri, Jun 3, 2011 at 12:35 PM, Colin Walters <<a href="mailto:walters@verbum.org" target="_blank">walters@verbum.org</a>> wrote:<br>
>> If this is under way, could extension makers be pointed towards it to<br>
>> future-proof their extensions.<br>
><br>
> I'm not sure what you mean by this.<br>
<br>
</div>Searching around now, it looks like Looking Glass (alt+f2 "lg")<br>
already registers the extensions so maybe not much else needs to be<br>
done in the extensions to take advantage of future enhancements to<br>
extension management.<br>
<br>
Also, wrt. yum as the existing manager for now, is there some policy<br>
on one extension per package, package naming, configuration formats,<br>
etc.? Right now, a lot of extensions are only available via<br>
instructions to just git clone development trees right into your<br>
extension directories which is bypassing a lot of review, auditing,<br>
and sanity processes. Is there anyone shepherding these into sane and<br>
consistent rpm packages?<br>
<br>
/Mike<br>
<div><div></div><div>--<br>
devel mailing list<br>
<a href="mailto:devel@lists.fedoraproject.org" target="_blank">devel@lists.fedoraproject.org</a><br>
<a href="https://admin.fedoraproject.org/mailman/listinfo/devel" target="_blank">https://admin.fedoraproject.org/mailman/listinfo/devel</a></div></div></blockquote><div><br></div><div>The latest version of gnome-tweak-tool can enable/disable installed extentions</div>
<div><br></div><div><a href="http://timlau.fedorapeople.org/files/pics/tweek-tool.png">http://timlau.fedorapeople.org/files/pics/tweek-tool.png</a></div><div><br></div><div>Tim</div>
</div><br>