Sorry, one more followup. I see now that I misread at the beginning and you were working with the Extensions policy which should have supported native paths.
That's a bug and I'll look into it. I've added the comment about ExtensionSettings to the policy doc. Mike On Thu, Feb 4, 2021 at 11:40 AM Mike Kaply <[email protected]> wrote: > Good call, I didn't even think about that. > > What's even more confusing is that Extensions did support local paths > originally, so we kept it for legacy purposes. > > ExtensionSettings doesn't. > > Mike > > On Thu, Feb 4, 2021 at 11:38 AM Andrew J. Buehler <[email protected]> > wrote: > >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA512 >> >> On 2021-02-04 at 12:17, Mike Kaply wrote: >> >> > So file URL was mentioned in the install_url, but it was kind of >> > buried. I made it more prominent and added a link to how file URLs >> > work. >> >> To be honest, this would not have helped me. I was looking at the >> "Extensions" policy, not the "ExtensionSettings" policy; I would not >> have expected the latter to be relevant, and indeed I may not even have >> noticed that it was present. Now that I've looked at it I can see how >> it's probably possible to use ExtensionSettings to specify installation >> of an extension, but at first glance based on the name I'd have expected >> it to be about configuring extensions, not about installing them. >> >> If it's recommendable to use ExtensionSettings rather than Extensions >> for installing such things, it might be worth noting that on the >> documentation for the Extensions policy, perhaps even by marking that >> policy as deprecated. >> >> - -- >> Andrew J. Buehler >> -----BEGIN PGP SIGNATURE----- >> >> iQJJBAEBCgAzFiEEJCOqsZEc2qVC44pUBKk1jTQoMmsFAmAcMQQVHHdhbmRlcmVy >> QGZhc3RtYWlsLmZtAAoJEASpNY00KDJryoMQAJCdfL60SrCDOxdwUQmU0jlF19qY >> hxRc9LE/7HgBznDs0FPq2141IHGNfYTVVtLa6adh8PKqUfzkqiMhN+i0XcxCbfut >> xvtmolmcRH6LBsQSA+1ZWDOS601aldAKY6XEf2jFZx8eFd1uiRUOxVJjG1pnw+bL >> DzWfsIz7GcAnVEmOsFgj1Dao+P7s0zIe1YJcgk78y8+2bf465FgnuhIpsRyCETCX >> O0hrNJ1EKZySE2rlTleOtc/KxqM/Rw84CyVQhEMhisj1OtwI2u2TJ7c122jAn/wi >> fDDa6YwYSiS9AwcKUnHR/W+TWcxyYvMLkwzzaBMeqJ6VoiLZ8yAbsdA7isuBBuWu >> FfDp4kn5VbxZK/tr/OdlfJMPE5PGefTmdYJ/X1jieyz0iB8+p1CxdgpAlZhjUv9L >> q1y1LyHkvjpqpKFbzLZNBXGP5/g0Wz+JheOjfQ6sXCoQsko2zx97F3BtJiAi+VKP >> f5X6AN7/y6QoMvqWCB6DdBUbpkerf69Wb4AR1As8jZDKxDVJrKilAy7NJskOzys3 >> CqcWajgMw3tYhWkNor1knRIYmyebxfHsZeZpC7wePN0YXqrhcuYpjiH79fm4fUEl >> r4YAU/RzofG3gTqB8fl5QlHDR8vvrxbf3hiOO/2c+22uQXbgfWbXqoXcPUndsMlj >> mmUgNAF4ETiRUEZG >> =iNl8 >> -----END PGP SIGNATURE----- >> _______________________________________________ >> Enterprise mailing list >> [email protected] >> https://mail.mozilla.org/listinfo/enterprise >> >> To unsubscribe from this list, please visit >> https://mail.mozilla.org/listinfo/enterprise or send an email to >> [email protected] with a subject of "unsubscribe" >> >
_______________________________________________ Enterprise mailing list [email protected] https://mail.mozilla.org/listinfo/enterprise To unsubscribe from this list, please visit https://mail.mozilla.org/listinfo/enterprise or send an email to [email protected] with a subject of "unsubscribe"
