Skip to content
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

Add file extension option to web-ext build #393

Open
kumar303 opened this issue Jul 26, 2016 · 7 comments
Open

Add file extension option to web-ext build #393

kumar303 opened this issue Jul 26, 2016 · 7 comments

Comments

@kumar303
Copy link
Contributor

kumar303 commented Jul 26, 2016

Add an option to build a package file with something other than the .xpi extension

@Croydon
Copy link

Croydon commented Jul 27, 2016

What about an manifest value which allows to save this setting persistent and also allows to save the build multiple times with different file extensions? Could be a step for Firefox&Chrome packaging at once?

I'm not sure if the often discussed mozilla.json file is already a reality, but I guess there could be a place for something like this.

@kumar303
Copy link
Contributor Author

kumar303 commented Jul 28, 2016

Could be a step for Firefox&Chrome packaging at once?

Could you explain this further? Can't you just use a .zip for both Firefox and Chrome? That was our intention when prioritizing support for .zip.

What about an manifest value which allows to save this setting persistent

I think a good solution here would be to implement support for a web-ext config file that you could commit to your repo to set defaults: #176

@andymckay
Copy link
Contributor

Also, there isn't a mozilla.json file that I know about.

@Croydon
Copy link

Croydon commented Aug 17, 2016

@kumar303:

Could you explain this further? Can't you just use a .zip for both Firefox and Chrome? That was our intention when prioritizing support for .zip.

When I didn't get it wrong it is not possible to install a .zip bundled add-on permanently in a (non-stable) Firefox build, is it? I'm doing this for longer testings of my (.xpi) add-ons.

I think a good solution here would be to implement support for a web-ext config file that you could commit to your repo to set defaults: #176

That sounds very good :)

@kumar303
Copy link
Contributor Author

When I didn't get it wrong it is not possible to install a .zip bundled add-on permanently in a (non-stable) Firefox build, is it? I'm doing this for longer testings of my (.xpi) add-ons.

You can install a .zip permanently in any build of Firefox (stable or non-stable). In about:addons you select 'Install add-on from file' in the gears menu. In the file picker change 'Format' from 'Add-ons' to 'All files' and select the zip.

@Croydon
Copy link

Croydon commented Aug 17, 2016

You can install a .zip permanently in any build of Firefox (stable or non-stable).

I'm sorry. I forgot the most important information. Is it also possible to install a .zip addon permanently when it's not signed?

I might remembering reading something like .zip are good for temporary testing or something. Unfortunately, my GitHub feed is spamming a huge information flow, so that I mostly just skim the issues, prs..

@kumar303
Copy link
Contributor Author

I'm sorry. I forgot the most important information. Is it also possible to install a .zip addon permanently when it's not signed?

I think so. Just like with XPIs, you would need to either use a pre-production or unbranded build with signing disabled.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants