From: Alan Grimes <alonzotg@verizon.net>
To: Gentoo User <gentoo-user@lists.gentoo.org>
Subject: [gentoo-user] Zombie seamonkey build...
Date: Wed, 14 Aug 2024 18:24:46 -0400 [thread overview]
Message-ID: <81690408-5115-c236-12f5-1e6713c46026@verizon.net> (raw)
In-Reply-To: 81690408-5115-c236-12f5-1e6713c46026.ref@verizon.net
I'm still using seamonkey as my e-mail as I have been doing with it and
its predecessors since 1998....
I am using the symlink trick to exploit the magic of dynamic linking to
get the stale build of seamonkey to run against the updated library. I
would like it to be able to build again at some point.
Furthermore any replacement of seamonkey must do the following two things:
1. not cause me a headache. (reeeealy hard.)
2. Come with a perpetual warranty, if I am reincarnated 500 years from
now, I'm going to be pissed if I'm going to have to learn a new email
client.
--
You can't out-crazy a Democrat.
#EggCrisis #BlackWinter
White is the new Kulak.
Powers are not rights.
next parent reply other threads:[~2024-08-14 22:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <81690408-5115-c236-12f5-1e6713c46026.ref@verizon.net>
2024-08-14 22:24 ` Alan Grimes [this message]
2024-08-14 23:38 ` [gentoo-user] Zombie seamonkey build mad.scientist.at.large
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=81690408-5115-c236-12f5-1e6713c46026@verizon.net \
--to=alonzotg@verizon.net \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox