The signtool is used to create "SmartUpdate" installs (Communicator 4.x)
rather than XPInstall packages (Mozilla/N6). The SmartUpdate script syntax
is similar but incompatible with XPInstall, but if you script is really an
XPInstall script and you name it "install.js" (SmartUpdate allowed arbitrary
install names) the signtool command given will work. XPInstall will
currently completely ignore the signature information.
"zip -rP myfoo.xpi install.js foo\*" would work, too.
-Dan Veditz
Mark B Baldwin wrote:
>
> We use signtool with the output being a .jar file. This signs and
> compresses all in one step. Netscape correctly uncompresses this format as
> long as the internal format of the jar file has an executable and an
> installation script called install.js.
>
> Our command line looks like this:
>
> signtool -k TestCert -Z testout.jar -d "c:\application
> data\mozilla\users50\default\n7rr8y9i.slt" -i install.js
> "e:\dev\webhelpinstall\install6"
>
> where:
> -k is the name of the certificate
> -Z is the name of the output
> -i is the name of the install script (must be install.js)
> the last parameter is the directory where the files to be signed and
> compressed are located.
>
> Groove on,
>
> Mark
> "rvj" <[EMAIL PROTECTED]> wrote in message
> news:8pqosn$[EMAIL PROTECTED]...> e.g what does a typical zip
> utility
> > > command line look like?
> > >
> > >
> >
> > OK have found 'How to install a new xpcom object...' post which implies
> any
> > zip utility is valid.
> >
> > Does this mean that
> >
> > a) the zip format used for packaging is 'irrelevant' ?
> > b) all zip utilities use the same format?
> > c) or that the appropriate unzip utility is downloaded or bundled in
> > xpinstall?
> >
> >
