-
Notifications
You must be signed in to change notification settings - Fork 89
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move XPIs to release section #116
Comments
I will move them to release section later on ;) |
IMHO XPIs should be installed from the files provided by their authors, not the ones stored separately. Extensions are separate products, let's not mix them with the browser. They can be installed by default, but they should be installed not from bundled xpis, but from the ones supplied by their authors. In other words, when a browser creates a new profile, it should ask its user if a user needs the default adddons to be installed, and if the user approves, then the browser should download and install them. Or it may show not a |
Those xpi versions are reviewed, it's why i made a copy there (a reviewed version, |
It is good they are reviewed, but you can store only their locations and hashes. |
1 You will need to rewrite history (there is an app for that), otherwise the wasted space won't be reclaimed.
2 It is not a good idea to store xpis in the repo at all.
The text was updated successfully, but these errors were encountered: