Comments for WebPack
Re: -f doesn't work on 0.6 beta
> The -f option is supposed to "Force
> overwrite of existing files", but
> if you use it you get:
> "ERROR - source and destination are
> the same directory"
Webpack was never intended to operate in-place, it is designed to create a compressed copy of your website, and this compressed version is the one you upload. What you saw is an intentional safety check to stop you compressing (and possibly corrupting) your "source" website.
The -f option forces overwriting of existing files in the destination directory.
-f doesn't work on 0.6 beta
The -f option is supposed to "Force overwrite of existing files", but if you use it you get:
"ERROR - source and destination are the same directory"
Obviously they're the same if you're going to overwrite existing files!
Re: Is webpack dead?
Not quite, just having issues with webhosting - mail to ezza@kludgesoft.net will work (have updated freshmeat settings).
> The email address in the README bounces,
> so the product may be dead:
%
Is webpack dead?
The email address in the README bounces, so the product may be dead:
----- Transcript of session follows -----
... while talking to mail.kludgesoft.com.:
>>> DATA
<<< 553 sorry, that domain isn't in my list of allowed rcpthosts (#5.7.1)
550 5.1.1 <contact@kludgesoft.com>... User unknown
<<< 503 RCPT first (#5.5.1)
Re: -f doesn't work on 0.6 beta
Maybe that's what you meant it to say, but that isn't what it implies.
The way the wording is written of the "usage" message, is that the -f option will force to ignore that. The message is open to misinterpretation, which is never a good idea for help messages ;-)