On 10/04/2024 06:44 PM, David Christensen wrote:
On 10/4/24 04:47, Richard Owlett wrote:
On 10/03/2024 06:34 PM, David Christensen wrote:
On 10/3/24 05:51, Richard Owlett wrote:
Is there standard/recommended location for an executable to be used
by only a one user?
In my case it should be under /home/richard/ .
But where?
It would help if you told us about the executable and the context for
its use -- e.g. self-contain binary for shell usage, one of several
programs included in a large graphical user interface application
suite that requires a specific desktop environment, etc.
<chuckle> If life were only that simple.
This started out with planning to update my PRIMARY system from
32 bit Debian 9 with SeaMonkey 2.49.4
to
64 bit Debian 12 with SeaMonkey 2.53.19
The 32 bit system resembles Topsy. It "just grew".
My goal for the 64 bit system is that it more closely conform to the
expectations of Debian.
For some indeterminate time BOTH versions of SeaMonkey *MUST* run on
both the 32 and 64 bit systems.
From a SeaMonkey list I've gotten the needed information to have two
incompatible versions coexist. It's a known problem.
So my question in a way becomes "Where do I _not put_ SeaMonkey
executable to avoid future clashes?"
Michael Kjörling referred me to specific sections of
https://specifications.freedesktop.org/basedir-spec/latest/index.html
and
https://www.freedesktop.org/software/systemd/man/latest/file-hierarchy.html
.
I needed the introductory material in both.
I will be carefully re-reading both.
I suspect it will be valuable to browse www.freedesktop.org generally.
[ I'll likely learn what questions I should be asking. ]
SeaMonkey does not appear to be available as a Debian package:
https://packages.debian.org/search?keywords=seamonkey&searchon=names&suite=all§ion=all
As far as I know it never has been.
I have been using it or its predecessors since the days of Netscape
Navigator.
STFW I see downloadable packages for SeaMonkey:
https://www.seamonkey-project.org/releases/
Rather than trying to do an in-place upgrade of your primary system, I
suggest implementing regular backups on your current primary system,
building a new primary system with 64 bit Debian 12 with SeaMonkey
2.53.19, restoring your data onto the new primary system, and
implementing regular backups of your new primary system.
*ROFL* That is the correct standard advice.
[ also a demo of why I ask SeaMonkey questions on SeaMonkey fora ]
I also take your suggestion one level deeper by doing it all on a
physically separate scratch test hardware when some would say doing it
in VM environment is enough isolation.
On a previous SeaMonkey update I demonstrated why one has backups ;/
