On Wed, Feb 20, 2002, Michael Schloh wrote:

>     Please review, I think we need to download using ASCII mode because the source
>     file is uuencoded and might otherwise be unencoded wrongly.
> 
>   Summary:
>     Revision    Changes     Path
>     1.21        +1  -0      openpkg-doc/quickref/openpkg.txt
>   ____________________________________________________________________________
> 
>   Index: openpkg-doc/quickref/openpkg.txt
>   ============================================================
>   $ cvs diff -u -r1.20 -r1.21 openpkg.txt
>   --- openpkg-doc/quickref/openpkg.txt        17 Dec 2001 15:33:25 -0000      1.20
>   +++ openpkg-doc/quickref/openpkg.txt        20 Feb 2002 10:49:30 -0000      1.21
>   @@ -37,6 +37,7 @@
>        $ ftp ftp.openpkg.org
>        ftp> cd release/<V>/SRC
>        ftp> ls openpkg-*.src.sh
>   +    ftp> ascii
>        ftp> get openpkg-<V>-<R>.src.sh
>        ftp> bye
>        $ sh openpkg-<V>-<R>.src.sh --prefix=$opkg_root --user=$opkg_ugid 
>--group=$opkg_ugid

No, why? "ascii" is the default in all old clients and even if the
default is "binary" it would be even better. I would expect that you
use an explicit "binary" here to make sure old clients to not break the
thing. But we certainly do not need an explicit "ascii".

                                       Ralf S. Engelschall
                                       [EMAIL PROTECTED]
                                       www.engelschall.com
______________________________________________________________________
The OpenPKG Project                                    www.openpkg.org
Developer Communication List                   [EMAIL PROTECTED]

Reply via email to