New issue
Advanced search Search tips

Issue 619532 link

Starred by 1 user

Issue metadata

Status: Archived
Owner: ----
Closed: Jun 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Feature



Sign in to add a comment

Meaningful name for .crx file when packing an extension

Reported by jayhe...@gmail.com, Jun 13 2016

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.84 Safari/537.36

Steps to reproduce the problem:
1. Pack an extension in chrome://extensions/ with Developer Mode turned on
2. Look at the name of the .crx file

What is the expected behavior?
Ideally the .crx file name would be constructed from name and version number information in the manifest. For example, MyExtension_1.0.5.crx and MyExtension.pem.

What went wrong?
I have lots of "src.crx" and "src.pem" files.

Did this work before? N/A 

Chrome version: 51.0.2704.84  Channel: stable
OS Version: Ubuntu 15.10
Flash Version: Shockwave Flash 21.0 r0

It may be useful to be able to override this in the command line packager. That's not working at all at the moment ( issue 514308 ) so there's no need to worry about breaking users' deployment scripts if you make this change.
 
Components: Platform>Extensions
Status: Untriaged (was: Unconfirmed)
As the issue is of Type feature marking it as Untriaged to get more inputs from dev team.

thanks,
Labels: -OS-Linux -Pri-2 Pri-3
Status: Available (was: Untriaged)
I don't think anyone on the chrome team will have time to work on this in the near future, but I think we'd be happy to review patches if someone wanted to try and contribute an implementation of this feature. 

Comment 3 Deleted

Comment 4 by jayhe...@gmail.com, Jun 27 2016

It turns out I was running the command line packager wrongly - I had omitted the "=" between the "--pack-extension-key" switch and the pathname.

With that and jq (https://stedolan.github.io/jq/) I am able to get what I wanted.

To read the version number with jq:
cat manifest.json | jq -r '[.version] | @csv'
Project Member

Comment 5 by sheriffbot@chromium.org, Jun 28 2017

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Status: Archived (was: Untriaged)
Based on #4, I'm going to archive this one.

Sign in to add a comment