And the day before that about the need for a "portable" email client:
Well, I was up to 3am working on it, but the sylpheed_portable PET has arrived (1MB):
To make it completely self-sufficient, requiring no dependencies, it has Cryptofs and Bogofilter inside it. The only deps are 'fuse' and 'sqlite3', that all puppies have. I haven't tested Bogofilter.
When you install this PET, it installs to /usr/local/sylpheed_portable, but doesn't actually run from there. When you run it, it asks to be copied to a partition, from whence it can be run into the future. Any partition, USB Flash drives also.
The reason that it installs first into /usr/local/sylpheed_portable is so that Woof-built-puppies can have it in their package list. It will be there, looking like any normal Sylpheed, runnable via the menu or the 'email' desktop icon, but the first time you run it, it gets relocated wherever you want it.
When it is finally installed in a mounted partition, it is just a RoxApp that you click to run. All configuration files and downloaded email are encrypted, and when you run Sylpheed you are asked for a password. Everything gets decrypted for the duration that you are using Sylpheed, then locked up again when you quit Sylpheed.
I'm using it with all the emails that I downloaded from Gmail, all 6,500 of them. Strangely, it seems faster accessing them via cryptofs than before.
Can we give the same "portable" treatment to Thunderbird/SeaMonkey-Mail? I don't know, will have to experiment -- sometime, don't know when.
Today will take some time off for family stuff -- someone's birthday, plus the old folks like to be visited.
Posted on 6 Mar 2012, 8:18 - Category: Wary - Comments - href="?edit=02735">Edit - Delete
Well, so are all the emails. I was thinking, what if someone stole my laptop? This got me thinking that I could implement an encrypted filesystem inside the Sylpheed installation.
Toward that end, I have compiled Cryptofs, which can encrypt an entire directory.
Here is the PET (230KB):
The only dependency is libfuse, which is in all puppies. Cryptofs does require libgpg-error and libgcrypt, however I linked those statically into the 'cryptofs' executable.
Posted on 5 Mar 2012, 18:37 - Category: Wary - Comments - href="?edit=02734">Edit - Delete
glew-1.7.0 OpenGL Extension Wrangler Library
llvm-2.8 Low Level Virtual Machine
clang-2.8 C/C++ compiler
libxml++-2.35.1 C++ interface to XML files
xulrunner-10.0.2 Embed Mozilla technologies into apps
Wary has all the dependencies, except libxml++ needs glibmm.
Now that might seem like a strange combination of PETs to create! I was compiling the dependencies for Lightspark, an open source Flash player. Then I found that Lightspark needs gcc 4.4+, whereas Wary has 4.3.4 -- so I compiled 4.4.6. However, Lightspark still needs Boost -- I installed libboost DEBs from Debian Lenny, but Lightspark compile failed, doesn't seem to like that version of Boost.
Posted on 28 Feb 2012, 8:28 - Category: Wary - Comments - href="?edit=02723">Edit - Delete
188.8.131.52 is recommended for language translators. It has some important bug fixes and enhancements for better and more complete translation.
Run MoManager and review translations, also you might find more to do in the 'doc_strings' category.
Get 184.108.40.206 from here:
We have three guys who I would like to acknowledge, who have completed or almost completed, "langpacks":
I am expecting that when Wary/Racy beta3 arrives at least two of these PETs will be available and ready for use. I intend to do some work on making it particularly easy to install these.
Posted on 26 Feb 2012, 14:44 - Category: Wary - Comments - href="?edit=02720">Edit - Delete
Right now I am uploading the SFS to ibiblio.org:
This is where Billtoo posted to the Forum:
Posted on 26 Feb 2012, 8:59 - Category: Wary - Comments - href="?edit=02718">Edit - Delete
The Wary build is here:
The Racy build is here:
If you are not familiar with what has been going on, that is, what has changed since earlier pup releases (Slacko, Wary, Racy), please browse down through my blog.
You will notice that the Wary ISO is very big. This is due to all of the analog modem drivers -- in Wary 5.2.2 I left out the Intel 53x modem drivers due to their enormous size, this time left them in. So, this time it really is the "kitchen sink" included, more SCSI drivers too.
Here is the Woof commit, dated 2012-02-21:
...note the change in how 'xwin' is executed. Karl Godt raised this issue in the Puppy Forum and I took another look at it. Here is a relevant earlier blog post:
Regarding the problem of how to launch 'xwin', this is a very ancient problem right from the early days of Puppy, and I think exposes a fundamental problem with Busybox and it's lack of support for runlevels in /etc/inittab. Unfortunately, the Busybox developers never provided an alternative to the runlevels. That is, there is no way to run 'xwin' after /etc/profile and /root/.profile (or .bashrc) have run (they are only supposed to set environment variables, not run executables).
Posted on 21 Feb 2012, 15:56 - Category: Wary - Comments - href="?edit=02705">Edit - Delete
Fortunately, Forum member 'npierce' has tracked down the cause of the problem:
I have put the patched 'fr' keyboard file into 'x_xorg76_mega_pkg-7.6-4-w5c.pet' and it is uploading right now.
Posted on 16 Feb 2012, 17:58 - Category: Wary - Comments - href="?edit=02690">Edit - Delete
Asunder 2.1 (audio CD ripper)
Homebank 4.4 (personal finances, supports OFX)
Isomaster 1.3.9 (edit ISO files)
These are included in Wary and Racy builds.
Asunder PET (46KB):
Homebank PET (208KB):
Isomaster PET (76KB):
Posted on 29 Jan 2012, 18:15 - Category: Wary - Comments - href="?edit=02664">Edit - Delete
Wjaguar's latest version, 3.40 download:
I have compiled version 3.40 in Wary and uploaded the PET (311KB, 360KB):
Posted on 28 Jan 2012, 8:54 - Category: Wary - Comments - href="?edit=02660">Edit - Delete
Sqlite (368KB, 427KB):
Seamonkey (16.4MB, 4.4MB):
Posted on 27 Jan 2012, 18:37 - Category: Wary - Comments - href="?edit=02656">Edit - Delete