Wary 1.0.2 (102) feedback

[Shep]

Most puppies have mimencode for base64 encoding. Wary gets around a missing mimencode by allowing uuencode to take the -m option to handle base64 encoding. Fair enough.

But how to decode base64 in Wary? Busybox's uudecode does not know about a -m option.

Code: Select all

# uudecode --help
BusyBox v1.17.2 (2010-09-28 21:52:28 GMT-8) multi-call binary.

Usage: uudecode [-o OUTFILE] [INFILE]

Uudecode a file
Finds outfile name in uuencoded source unless -o is given

[npierce]

But how to decode base64 in Wary? Busybox's uudecode does not know about a -m option.

If the file was encoded by uuencode -m, uudecode will recognize that it is base64, because uuencode indicates that it is base64 in the first line of the encoded file.

If the file was encoded by mimencode, things are not as simple, since mimencode doesn't indicate the type of encoding in the file.

If you have such a file, you can supply that information by using the following one-line command (although it might get wrapped to two lines in your browser window) to give uudecode something that it recognizes:

Code: Select all

echo -e "begin-base64 644 decoded_file\n`cat encoded_file`\n====" | uudecode

The above command decodes a file named "encoded_file" to a file named "decoded_file", and gives it permissions 644.

If you do this a lot, you may want to write a short script -- something like this:

Code: Select all

#!/bin/bash

if [ -f "$1" ] && [ -r "$1" ] && [ -n "$2" ] ; then

echo -e "begin-base64 `stat --printf %a "$1"` $2\n`cat "$1"`\n====" | uudecode

elif [ -e "$1" ] && [ -r "$1" ] && [ -n "$2" ] ; then

echo "$1: not a regular file"

elif [ -e "$1" ] && [ -n "$2" ] ; then

echo "$1: Read permission denied"

elif [ -n "$2" ] ; then

echo "$1: file not found"

else

echo -e "Usage:\n\t$0 <encoded_file> <decoded_file>"

fi

I've double-spaced to make clear the individual lines, despite how they might wrap in your browser window.

The script decodes the file named in the first argument to the file named in the second argument, and gives the decoded file the same read, write, and execute permissions as the encoded file.

Of course it might be easier to install mimencode, and would be easier still if it was included with the distro.

[Shep]

But how to decode base64 in Wary? Busybox's uudecode does not know about a -m option.

If the file was encoded by uuencode -m, uudecode will recognize that it is base64, because uuencode indicates that it is base64 in the first line of the encoded file.

Thank you for the trouble you went to in answering my question. A week after posting I remembered I should just copy the binary from another puppy (TXZ) and it runs just fine in Wary. I now store it outside the save file so I can call it from whatever puppy is lacking that binary.

The most logical solution would be for uudecode to accept the -m argument. Or couldn't it simply interpret the differing line lengths as indicative of UU or base64?

Most often I copy the block of base64 stuff out of an email, without headers, and need to decode it.

Again, thanks.

[npierce]

Shep,

You're welcome.

I'm glad to hear that you now have a mimencode binary that your Puppies can share -- a good solution.

I would think that the need to decode base64 e-mail attachments would be common enough to justify the little 9 kB footprint that mimencode would require in Wary. Although I enjoyed looking into finding a way to do it with uudecode, many users won't want to go to that length.

Of course, if uudecode had an option for this, as you suggested, that would be a space-saving alternative.

[ttuuxxx]

Hi Barry I also spent 2 days on trying to get the wxgtk email client going and well its a no go, lol
So I went on a hunt for another email, client for your repo.
Well I found one its a Gnome email client called Balsa, I made just about all the deps static, lol only esmtp needed to be shared, It needed Gconf,Orbit, Dbus, etc. I manually removed Dbus from Gconf, what a pain that was, I'll post the sources for Gconf-No-Dbus later. I managed to get them to compile statically. Anyways here's a package its not 100% complete yet, I need to workout which gnome icons it needs, But it would be good to get it tested by users. Spellcheck works, I statically compiled gtkspell, Pop3 works for Gmail, I need to figure out what's being called when you click a url in a message, because It doesn't find the handler, probably yelp or ghelp.
I'll keep working on it.
ttuuxxx

[yosi666]

Hi Barry
I tried to download Wary 1.0.2 from your blog but the download is unavailable. Is there anywhere else from where I can download it to try this new version?
Thank you very much for ur job

[James C]

Hi Barry
I tried to download Wary 1.0.2 from your blog but the download is unavailable. Is there anywhere else from where I can download it to try this new version?
Thank you very much for ur job

This is an old test release.For the latest, Wary 5.0 see here
http://bkhome.org/blog/?viewDetailed=02057

[yosi666]

Yep, realized after I posted
Thanks for the reply
Liked the Wary 5.0 very much. Recognised my zte mf 110 usb modem in a minute after installing the zzz_scripts_simple pet in Barry's blog
Nice work!

[abushcrafter]

But how to decode base64 in Wary? Busybox's uudecode does not know about a -m option.

If the file was encoded by uuencode -m, uudecode will recognize that it is base64, because uuencode indicates that it is base64 in the first line of the encoded file.

If the file was encoded by mimencode, things are not as simple, since mimencode doesn't indicate the type of encoding in the file.

If you have such a file, you can supply that information by using the following one-line command (although it might get wrapped to two lines in your browser window) to give uudecode something that it recognizes:

Code: Select all

echo -e "begin-base64 644 decoded_file\n`cat encoded_file`\n====" | uudecode

The above command decodes a file named "encoded_file" to a file named "decoded_file", and gives it permissions 644.

If you do this a lot, you may want to write a short script -- something like this:

Code: Select all

#!/bin/bash

if [ -f "$1" ] && [ -r "$1" ] && [ -n "$2" ] ; then

echo -e "begin-base64 `stat --printf %a "$1"` $2\n`cat "$1"`\n====" | uudecode

elif [ -e "$1" ] && [ -r "$1" ] && [ -n "$2" ] ; then

echo "$1: not a regular file"

elif [ -e "$1" ] && [ -n "$2" ] ; then

echo "$1: Read permission denied"

elif [ -n "$2" ] ; then

echo "$1: file not found"

else

echo -e "Usage:\n\t$0 <encoded_file> <decoded_file>"

fi

I've double-spaced to make clear the individual lines, despite how they might wrap in your browser window.

The script decodes the file named in the first argument to the file named in the second argument, and gives the decoded file the same read, write, and execute permissions as the encoded file.

Of course it might be easier to install mimencode, and would be easier still if it was included with the distro.

Hmm, could you have a look at my Improving The Wrappers From Xarchive thread at test out the "uu-wrap.sh" wrapper please?