Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

This is my default approach to writing installers for the Unices. The program is compressed and added to the end of the script, and the script does the unpacking and any needed setup/configuration for the specific platform it's getting installed on.

I don't append it in binary form, though. I uuencode it. That way, there is no danger in using text editors.



Why uuencode? Base64 is the defacto standard these days.


Sorry, I did mean base64. I have a bad habit of calling all "binary as text" encodings "uuencode". I usually catch myself before I put it in writing, though.


I've used both, but only briefly. I think I used uuencode when using uucp. And Base64 in one of my Python programs.

What are their pros and cons, in your opinion?


Base 64 is slightly more space efficient. Other than that it's just more popular and better supported.


Got it, thanks.

Yes, uuencode / uudecode are probably older too.

They are from the uucp dialup comms era of networking.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: