Please explain why custom installer and provide hints about how to go manual

[fidergo-stephane-gourichon]

An installer for an extension? Please provide reasons

It's the first time I see a Firefox extension that requires a specific installer. Nowhere I see an explanation about it. Pages in the wiki explain a few things without motivation, assuming knowledge from the reader about the "why".

A binary installer? Let's first see in source what it does

I have read the complete go source code for the dedicated installer. It's short, nice!
It (backups if needed then) generates user*.css files, a customization dir, including a file that associates UUIDs to a known set of webextensions (why?).
Then I compiled it and run it, and had a look at the changes in firefox profile.

Request to make things easier for future visitors

Explaining the installation process would be useful for those purposes at least:

• gain legitimacy among security-savvy users who currently frown upon the binary installer
• provide a blueprint for anyone wishing to make another installer -- for example, an installer in bash, python or Powershell (e.g. issue Suggestion: Powershell script for Windows installation/configuration #19 )

Minor remark below

Extracts from the text that appears in the "new issue" field:

For questions or issues regarding how to setup ShadowFox, read first: https://github.com/overdodactyl/ShadowFox/wiki/Getting-Started

That page does not exist. You probably mean https://github.com/overdodactyl/ShadowFox/wiki/Installation

Thanks!

Thank you for your attention.