Comment #10 on issue 20669 by craig.schlenter: Implement extension packing on linux http://code.google.com/p/chromium/issues/detail?id=20669
Re comment #9, it's not quite done yet. It needs something approximately like http://codereview.chromium.org/246085 to respond to the command-line flag. Also windows seems to have a dialog hooked into chrome://extensions for packing but maybe that's not part of this bug. When I apply the above patch and pack the hello world extension, the resulting crx seems to be broken: (note the missing first character in the filenames) [cr...@csinspiron src(packext)]$ unzip -t ./myext.crx Archive: ./myext.crx warning [./myext.crx]: 306 extra bytes at beginning or within zipfile (attempting to process anyway) testing: anifest.json OK testing: y_toolstrip.html OK No errors detected in compressed data of ./myext.crx. For comparison, here is something that is "good". [cr...@csinspiron src(packext)]$ unzip -t ./chrome/test/data/extensions/good.crx Archive: ./chrome/test/data/extensions/good.crx warning [./chrome/test/data/extensions/good.crx]: 306 extra bytes at beginning or within zipfile (attempting to process anyway) testing: manifest.json OK testing: script1.js OK testing: script2.js OK No errors detected in compressed data of ./chrome/test/data/extensions/good.crx. Please note that I know absolutely nothing about extensions so consider the source of this information when reviewing the above :) -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
