Which distro provides a full, complete TDE R14.1.2 install? Every single TDE package. Something that can be downloaded, installed to a VM, and install some kind of TDE meta package.
Thanks.
On Mon May 20 2024 21:04:38 Darrell Anderson via tde-users wrote:
Which distro provides a full, complete TDE R14.1.2 install? Every single TDE package. Something that can be downloaded, installed to a VM, and install some kind of TDE meta package.
You're probably going to want to follow the instructions from this page to add the Trinity repository to one of the popular distros. It's just a few lines of text to be added to a config file.
Darrell Anderson composed on 2024-05-21 00:04 (UTC-0400):
Which distro provides a full, complete TDE R14.1.2 install? Every single TDE package. Something that can be downloaded, installed to a VM, and install some kind of TDE meta package.
How to install TDE pages for each distro are all about the same. e.g. https://wiki.trinitydesktop.org/Debian_Trinity_Repository_Installation_Instructions includes this language:
sudo aptitude install tde-trinity
Just above it in highlight is the following:
[quote]Warning! tde-trinity package is a comprehensive meta-package. To install a minimalist environment, replace tde-trinity with tdebase-trinity in the instructions below.[/quote]
IOW, if you *don't* want a full, complete installation of TDE (on Debian), *don't* install tde-trinity.
It's similar on non-Debian distros, e.g. openSUSE: https://wiki.trinitydesktop.org/OpenSUSE_Trinity_Repository_Installation_Instructions [quote] # zypper install trinity-desktop
The trinity-desktop package is a comprehensive meta-package. To install minimalist, substitute trinity-tdebase for trinity-desktop, and append trinity-tdm if you wish to use TDM as your display manager.[/quote]
Darrell Anderson composed on 2024-05-20 23:04 (UTC-0500):
Which distro provides a full, complete TDE R14.1.2 install? Every single TDE package. Something that can be downloaded, installed to a VM, and install some kind of TDE meta package.
How to install TDE pages for each distro are all about the same. e.g. https://wiki.trinitydesktop.org/Debian_Trinity_Repository_Installation_Instructions includes this language:
sudo aptitude install tde-trinity
Just above it in highlight is the following:
[quote]Warning! tde-trinity package is a comprehensive meta-package. To install a minimalist environment, replace tde-trinity with tdebase-trinity in the instructions below.[/quote]
IOW, if you *don't* want a full, complete installation of TDE (on Debian), *don't* install tde-trinity.
It's similar on non-Debian distros, e.g. openSUSE: https://wiki.trinitydesktop.org/OpenSUSE_Trinity_Repository_Installation_Instructions [quote] # zypper install trinity-desktop
The trinity-desktop package is a comprehensive meta-package. To install minimalist, substitute trinity-tdebase for trinity-desktop, and append trinity-tdm if you wish to use TDM as your display manager.[/quote]
On 5/21/24 2:06 AM, Felix Miata via tde-users wrote:
How to install TDE pages for each distro are all about the same. e.g. https://wiki.trinitydesktop.org/Debian_Trinity_Repository_Installation_Instructions includes this language:
sudo aptitude install tde-trinity
Just above it in highlight is the following:
[quote]Warning! tde-trinity package is a comprehensive meta-package. To install a minimalist environment, replace tde-trinity with tdebase-trinity in the instructions below.[/quote]
Sounds good enough. I have no plans to use Debian. All I want is a complete TDE install. Slackware is notably absent from the list of distros offering anything close to a full TDE install. I hope to work toward resolving that, but I need a full install to start comparing.
Second, I am interested in how much a full TDE conflicts with a full KDE. Slackware comes with a full KDE install.
For the curious, along with the recent discussions about TDE keeping KDE3 on "life support," one of my guesses that keeps TDE restrained from wider adoption is living in /opt purgatory. I have posted my share of questions regarding this dilemma. TDE is not well designed to coexist with other DEs and this can be seen in the complexity of starttde, incomplete *.desktop files, etc. I filed bug reports about this well back into the first days of TDE.
I suspect many TDE users do not experience conflicts with other DEs because they only use TDE. That's fine and not a point of contention. Those who use multiple DEs or have computers with multiple users run into snags trying to massage TDE with the DEs.
I am not a coder, but one way or another I suspect the only way to move forward is somebody collecting notes to help move TDE back to /usr land. Hence the request for a full TDE install environment. :)
Darrell Anderson composed on 2024-05-21 12:28 (UTC-0500):
Felix Miata via tde-users wrote:
How to install TDE pages for each distro are all about the same. e.g. https://wiki.trinitydesktop.org/Debian_Trinity_Repository_Installation_Instructions includes this language:
sudo aptitude install tde-trinity
Just above it in highlight is the following:
[quote]Warning! tde-trinity package is a comprehensive meta-package. To install a minimalist environment, replace tde-trinity with tdebase-trinity in the instructions below.[/quote]
Sounds good enough. I have no plans to use Debian. All I want is a complete TDE install. Slackware is notably absent from the list of distros offering anything close to a full TDE install. I hope to work toward resolving that, but I need a full install to start comparing.
http://mirror.ppa.trinitydesktop.org/trinity/rpm/ Debian, Devuan, Ubuntu, RedHat EL, Fedora, Mageia, openSUSE, PCLinuxOS
Second, I am interested in how much a full TDE conflicts with a full KDE. Slackware comes with a full KDE install.
Outside the menuing systems, zero. That's why KDE3 was, and TDE still remains, installed to /opt/, necessary for KDE3 and KDE4 to both be installed on the same system when KDE4 was originally provided in distro releases offering both, e.g. openSUSE, where KDE3 is still available in optional repos for both Leap and TW. The menu starter used may need customizing for availability if desired of both Konsoles, both Konqs, both Kates, etc. regardless which DE is currently active.
I have no understanding /why/ there's any objection to TDE placement in /opt/.
Felix Miata composed on 2024-05-21 13:56 (UTC-0400):
Darrell Anderson composed on 2024-05-21 12:28 (UTC-0500):
I have no plans to use Debian. All I want is a complete TDE install. Slackware is notably absent from the list of distros offering anything close to a full TDE install. I hope to work toward resolving that, but I need a full install to start comparing.
http://mirror.ppa.trinitydesktop.org/trinity/rpm/ Debian, Devuan, Ubuntu, RedHat EL, Fedora, Mageia, openSUSE, PCLinuxOS
I forgot this page exists (I thought my list was short): https://wiki.trinitydesktop.org/Category:Installation It adds Archlinux, FreeBSD, MX Linux, Raspbian and *Slackware*. https://wiki.trinitydesktop.org/Slackware_Trinity_Installation_Instructions
said Thierry de Coulon via tde-users:
| On Tuesday 21 May 2024 19.56:37 Felix Miata via tde-users wrote: | > I have no understanding /why/ there's any objection to TDE placement | > in /opt/. | | So do I. Clear, clean, convenient.
This weird argument goes back 25 years, when some of us were recompiling KDE daily. Then, you'd add "prefix=/opt/kde" because, as those who wanted it splattered all over the place discovered to their anguish, if the build blew up you could easily delete everything from /opt/kde -- not so easy if you've distributed it all through the filesystem.
I'd argue that more rather than fewer things ought to be nicely segregated in /opt.
On 5/21/24 12:56 PM, Felix Miata via tde-users wrote:
I have no understanding/why/ there's any objection to TDE placement in/opt/.
Perhaps I am an outlier. That would be nothing new in my life. :)
There is no strict technical requirement against installing to /opt, but doing so renders TDE a second class player. No other DE is installed this way.
A bug report was filed long ago:
https://bugs.trinitydesktop.org/show_bug.cgi?id=1934
Installing to /opt was understandable in the early days of forking TDE. KDE was and still is the 800 pound canary that is more popular than TDE -- both by users and politically in the free/libre world. There is no way TDE developers and users would win a spitting contest about which DE should be installed to /usr and /opt. The result is TDE users are told to "know their place" and sit in the back of the bus.
From Paul Sheer's Rute User's Tutorial and Exposition:
"/opt is reserved for the installation of add-on application software packages."
While not a technical issue, I don't think installing TDE to /opt suggests an add-on application. LibreOffice perhaps, but DEs are primary applications and should be installed to /usr.
Except that 800 pound canary still exists.
Installing to /opt requires work-arounds and tap dancing with environment variables, such as $PATH. This is noticeable in starttde. Even the current starttde is not robust with configuring $PATH.
Although declared compliant on the TDE web site, TDE is not really XDG compliant. There are related bug reports.
Related, discussed some weeks back is getting non KDE Qt5 software to blend with TDE. There are no such issues with non KDE Qt5 software in KDE or other DEs. The root cause usually is the Qt5 software developers never heard of TDE or don't think TDE is relevant.
Another example is /usr/bin/xdg-open. Notice TDE is not listed as a DE option.
In the end TDE tends to receive a poor grade by tech savvy users.
The MATE developers resolved the dilemma early in their forking from GNOME 2 by renaming potentially conflicting binaries with a 'mate-' prefix. TDE could be developed the same with a 'tde-' prefix. Since most people today are mouse point-clicky users, most would notice no difference with respect to the TDE menu and respective *.desktop files. Users comfortable with the Alt+F2 Run dialog would notice the change (typing 'tde-konsole' rather than konsole), but MATE users have grown accustomed to this many years ago, probably because GNOME binaries use a gnome- prefix. So too would TDE users adapt.
Since my return to TDE I have run into several of these issues. I have submitted bug reports and feature requests, but most of any such effort would be more readily resolved if TDE was installed in /usr conflict-free.
I use both KDE 5 and TDE and for some years also used MATE and Xfce. There always have been conflicts and work-around hoops to jump through because TDE is not respected as a regular DE in /usr.
I stopped using MATE and Xfce when the developers adopted GTK3, but I use KDE 5 and harbor no ill feelings about KDE like I once did during the early days of KDE 4 (and I remember the spitting contests we had with KDE developers in the mail lists). Both KDE 5 and TDE work for me, except they do not work well together without sweat equity.
Users who primarily only use TDE are unlikely to run into any of these issues.
My desire is not to create community conflict or launch a coup. I have been around computers for more than 40 years. I was involved in the early days of TDE. I believe returning TDE to /usr, along with related adjustments, would render TDE more palatable to distro maintainers and raise TDE popularity. There are people who believe TDE is cute, quaint, nostalgic, or nice, but they also believe TDE is obsolete and irrelevant to modern users. As recent discussions indicate by the yet unread LWN article, at least one editor or author probably thinks this way. I don't believe any of that. Conversely, returning TDE to /usr and improving XDG compliance improves credibility. No more sitting at the back of the bus.
Anyway, nothing is going to happen until the lead TDE developers give the word. :)
On Tue May 21 2024 13:22:33 Darrell Anderson via tde-users wrote:
There is no strict technical requirement against installing to /opt, but doing so renders TDE a second class player. No other DE is installed this way.
<long argument snipped>
TDE works fine in /opt, as does Google Earth and Unity Hub game development environment.
Thank you TDE devs for maintaining and improving an excellent and reliable software product without forcing unnecessary changes on us.
--Mike
Mike Bird composed on 2024-05-21 13:43 (UTC-0700):
Darrell Anderson wrote on 2024-05-21 15:22 (UTC-0500)::
"/opt is reserved for the installation of add-on application software packages."
While not a technical issue, I don't think installing TDE to /opt suggests an add-on application.
Add-on as in sourced from elsewhere than the distribution being installed to, like brother print drivers, not add-on as in dealer-prep, rust-proofing, tape-stripes and cupholders. The former nicely defines /opt/.
There is no strict technical requirement against installing to /opt, but doing so renders TDE a second class player. No other DE is installed this way.
<long argument snipped>
TDE works fine in /opt, as does Google Earth and Unity Hub game development environment.
Thank you TDE devs for maintaining and improving an excellent and reliable software product without forcing unnecessary changes on us.
And for not wasting time moving it from /opt/ to /usr/. What ain't broke don't need fixin.
Felix Miata via tde-users wrote:
And for not wasting time moving it from /opt/ to /usr/. What ain't broke don't need fixin.
It is on the roadmap, but AFAIK too many things need to be adjusted regarding the naming of the applications. I trust Slavek and Michele to lead us there. In the past few years few excellent developers joined and I see a lot of progress compared to 10y ago. I keep my fingers crossed.
On 2024-05-21 18:14:36 deloptes via tde-users wrote:
Felix Miata via tde-users wrote:
And for not wasting time moving it from /opt/ to /usr/. What ain't broke don't need fixin.
It is on the roadmap, but AFAIK too many things need to be adjusted regarding the naming of the applications. I trust Slavek and Michele to lead us there. In the past few years few excellent developers joined and I see a lot of progress compared to 10y ago. I keep my fingers crossed.
Unless it's a requirement for TDE to be accepted as a "mainstream" desktop environment, I think that would be a waste of time and resources. TDE works just fine in /opt/.
Leslie -- Platform: Linux Distribution: openSUSE Leap 15.5 - x86_64 Desktop Environment: Trinity Qt: 3.5.0 TDE: R14.1.2 tde-config: 1.0
J Leslie Turriff via tde-users wrote:
Unless it's a requirement for TDE to be accepted as a "mainstream" desktop environment, I think that would be a waste of time and resources. TDE works just fine in /opt/.
I think it falls under "nice to have". The other aspect is that it will be not mistaken with KDE (I mean the applications)
On Tuesday 21 May 2024 22.22:33 Darrell Anderson via tde-users wrote:
There is no strict technical requirement against installing to /opt, but doing so renders TDE a second class player. No other DE is installed this way.
In my /opt live:
- Trinity - Vivaldi - Firefox - Simplify3D - MasterPDF -Editor - LibreOffice - Google Chrome and Earth - AfterShot Pro - and even M$ Edge (yep, for their Teams Prgressive Web App that no long can connect to their new Teams...)
So /opt is quite used. Judging of a DE from where it is installed is... well.. let's say surprising. A little as if I said a car is good not because I use it because where I bought it.
Thierry
On 5/21/24 3:59 PM, Thierry de Coulon via tde-users wrote:
On Tuesday 21 May 2024 22.22:33 Darrell Anderson via tde-users wrote:
There is no strict technical requirement against installing to /opt, but doing so renders TDE a second class player. No other DE is installed this way.
In my /opt live:
- Trinity
- Vivaldi
- Firefox
- Simplify3D
- MasterPDF -Editor
- LibreOffice
- Google Chrome and Earth
- AfterShot Pro
- and even M$ Edge (yep, for their Teams Prgressive Web App that no long can
connect to their new Teams...)
So /opt is quite used. Judging of a DE from where it is installed is... well.. let's say surprising. A little as if I said a car is good not because I use it because where I bought it.
Fair enough. My guess is every one of those apps create sym links in /usr/bin because seldom is /opt/trinity/$anything in the search path $PATH.
On 2024-05-21 16:22:19 Darrell Anderson via tde-users wrote:
On 5/21/24 3:59 PM, Thierry de Coulon via tde-users wrote:
On Tuesday 21 May 2024 22.22:33 Darrell Anderson via tde-users wrote:
There is no strict technical requirement against installing to /opt, but doing so renders TDE a second class player. No other DE is installed this way.
In my /opt live:
- Trinity
- Vivaldi
- Firefox
- Simplify3D
- MasterPDF -Editor
- LibreOffice
- Google Chrome and Earth
- AfterShot Pro
- and even M$ Edge (yep, for their Teams Prgressive Web App that no long
can connect to their new Teams...)
So /opt is quite used. Judging of a DE from where it is installed is... well.. let's say surprising. A little as if I said a car is good not because I use it because where I bought it.
Fair enough. My guess is every one of those apps create sym links in /usr/bin because seldom is /opt/trinity/$anything in the search path $PATH.
In fact, if you look in /opt/trinity/bin/starttde below line 208, it dynamically adds /opt/trinity directories to the path.
Leslie -- Platform: Linux Distribution: openSUSE Leap 15.5 - x86_64 Desktop Environment: Trinity Qt: 3.5.0 TDE: R14.1.2 tde-config: 1.0
On 5/21/24 6:14 PM, J Leslie Turriff via tde-users wrote:
In fact, if you look in /opt/trinity/bin/starttde below line 208, it dynamically adds /opt/trinity directories to the path.
Yes, but /opt/trinity/bin does not get into $PATH if the user does not launch starttde. Some users might want to use TDE software from within a different DE. I modified starttde and some /etc/profile.d scripts to accommodate either use case.
On 2024-05-21 18:46:49 Darrell Anderson via tde-users wrote:
On 5/21/24 6:14 PM, J Leslie Turriff via tde-users wrote:
In fact, if you look in /opt/trinity/bin/starttde below line 208, it dynamically adds /opt/trinity directories to the path.
Yes, but /opt/trinity/bin does not get into $PATH if the user does not launch starttde. Some users might want to use TDE software from within a different DE. I modified starttde and some /etc/profile.d scripts to accommodate either use case.
Easy enough to add /opt/trinity/bin to PATH in .bashrc.
Leslie -- Platform: Linux Distribution: openSUSE Leap 15.5 - x86_64 Desktop Environment: Trinity Qt: 3.5.0 TDE: R14.1.2 tde-config: 1.0
Darrell Anderson via tde-users composed on 2024-05-21 19:59 (UTC-0500):
On 5/21/24 7:51 PM, J Leslie Turriff via tde-users wrote:
Easy enough to add /opt/trinity/bin to PATH in .bashrc.
And for people who do not use bash? ;)
Besides maybe Arch, Gentoo, LFS and/or Slackware, what doesn't have /etc/skel/.bashrc?
On 2024-05-21 22:04:59 Felix Miata via tde-users wrote:
Darrell Anderson via tde-users composed on 2024-05-21 19:59 (UTC-0500):
On 5/21/24 7:51 PM, J Leslie Turriff via tde-users wrote:
Easy enough to add /opt/trinity/bin to PATH in .bashrc.
And for people who do not use bash? ;)
Besides maybe Arch, Gentoo, LFS and/or Slackware, what doesn't have /etc/skel/.bashrc?
I think he means people who don't know what .bashrc does.
Leslie -- Platform: Linux Distribution: openSUSE Leap 15.5 - x86_64 Desktop Environment: Trinity Qt: 3.5.0 TDE: R14.1.2 tde-config: 1.0
On 5/21/24 10:04 PM, Felix Miata via tde-users wrote:
And for people who do not use bash? ;)
Besides maybe Arch, Gentoo, LFS and/or Slackware, what doesn't have /etc/skel/.bashrc?
Doesn't matter if bash is included in the distro. Users are not required to use bash as their default shell.
Bash is not the default shell with the BSDs.
Slackware does not install a default /etc/skel. That is an exercise for the user. That is a big reason I continue using Slackware -- Patrick does not presume how anybody should use their computers. He provides a base operating system and let's everybody decide what they want to do.
Darrell Anderson composed on 2024-05-21 22:40 (UTC-0500):
Felix Miata wrote:
And for people who do not use bash? ;)
Besides maybe Arch, Gentoo, LFS and/or Slackware, what doesn't have /etc/skel/.bashrc?
Doesn't matter if bash is included in the distro. Users are not required to use bash as their default shell.
Bash is not the default shell with the BSDs.
Slackware does not install a default /etc/skel. That is an exercise for the user. That is a big reason I continue using Slackware -- Patrick does not presume how anybody should use their computers. He provides a base operating system and let's everybody decide what they want to do.
My point was *most* users on *most* distros have a ~/.bashrc file, whether they know it or not, and whether they consciously or not do anything that may be affected by anything in it. Some environments get pretty big:
set | wc -lm
1608 57565
set | grep opt/
MANPATH=/usr/local/man:/usr/share/man:/opt/kde3/share/man PATH=/opt/kde3/bin:/home/redact/bin:/usr/local/bin:/usr/bin:/bin:/home/redact/bin WINDOWMANAGER=/opt/kde3/bin/startkde XDG_DATA_DIRS=/usr/local/share:/usr/share:/etc/opt/kde3/share:/opt/kde3/share
On 5/21/24 11:14 PM, Felix Miata via tde-users wrote:
My point was *most* users on *most* distros have a ~/.bashrc file, whether they know it or not, and whether they consciously or not do anything that may be affected by anything in it.
When a user does not use bash as the default shell, then anything inside .bashrc or any of the other bash startup scripts are irrelevant because the files do not get sourced. Adding /opt/trinity/bin to the user's $PATH in .bashrc is not going to do anything.
Suppose though a user discovers that TDE software can't be used within a different DE and finds a way to massage $PATH to place /opt/trinity/bin after /usr/bin. Some people are willing to invest that kind of sweat equity. Most won't, simply muttering WTF. This is part of the point about installing TDE in /usr. Doing that means there are not going to be any environment variable issues.
In that use case, placing /opt/trinity/bin after /usr/bin is important. Otherwise all binaries in /opt/trinity/bin prevail over those in /usr/bin. If that person is using KDE and wants to use an occasional TDE tool then I'll guess the user will get frustrated and mad.
I was there when starttde was first massaged into a complex script. I contributed my share of the code. Everybody involved worked hard to anticipate various usage scenarios. Unfortunately the script, and TDE in general, is designed more or less as a sole DE. There is nothing wrong with this approach, until a person wants to use multiple DEs or the computer is used by multiple people where global environment variables cause havoc.
Like I shared earlier, I am not trying to start a coup. There are some issues with TDE that need attention, that's all. That TDE works great for you in /opt is nice, but we live in a big world with many different use cases. None of the other DEs installed in /usr face these issues. And if or when the devs agree to pursue this issue, everything will be tested in a git branch, not in production.
said Darrell Anderson via tde-users: | On 5/21/24 7:51 PM, J Leslie Turriff via tde-users wrote: | > Easy enough to add /opt/trinity/bin to PATH in .bashrc. | | And for people who do not use bash? ;)
They can compile it themselves and put it wherever they want.
Anno domini 2024 Wed, 22 May 18:38:36 +0000 dep via tde-users scripsit:
said Darrell Anderson via tde-users: | On 5/21/24 7:51 PM, J Leslie Turriff via tde-users wrote: | > Easy enough to add /opt/trinity/bin to PATH in .bashrc. | | And for people who do not use bash? ;)
They can compile it themselves and put it wherever they want.
.. even if the sun does not shine there ... (sorry, it's late and somehow walking down memory lane awakes strange ghosts of days long gone https://www.youtube.com/watch?v=qTf3NsLiG58 )
-- Please do not email me anything that you are not comfortable also sharing with the NSA, CIA ...
On Tuesday 21 May 2024 13:22:33 Darrell Anderson via tde-users wrote:
On 5/21/24 12:56 PM, Felix Miata via tde-users wrote:
I have no understanding/why/ there's any objection to TDE placement in/opt/.
Perhaps I am an outlier. That would be nothing new in my life. :)
There is no strict technical requirement against installing to /opt, but doing so renders TDE a second class player. No other DE is installed this way.
I used to share your opinion, and that was more or less my complaint: that a desktop installed to /opt/ makes TDE appear second-class, that we must sit at the back of the bus, that we don't get included as one of the default choices of desktop by the major distros.
Now, however, I don't mind so much. (Been running TDE for about 12 years, KDE3 for another 8 years or so before that.) For one thing, there are some basic technical problems -- if I may call it that -- having to do with the simple problem of naming. Many legacy KDE3 applications retain their KDE names, prefixes, suffixes, as well as the same extensions (for file type, deb, rpm, etc.), so that the newer KDE4/5/6 packages would create apparent conflicts.
To attempt to rename *all* the TDE packages that have old KDE3 names would be difficult, because it could not be done easily by some kind of find-and-replace too. Any half-hearted measures would be a waste of time, and at the moment, I believe, only a fool's errand.
If we do that, then any renaming scheme must be thorough, comprehensive, rename every single package, so that it is uniform. Also this would obscure our historical connection with KDE.
A bug report was filed long ago:
{SNIP}
In the end TDE tends to receive a poor grade by tech savvy users.
And yet TDE is still used by users who are even *more* tech savvy than those savants who would judge us.
;-)
In the end, I think that it's more important to keep TDE free-libre, compliant with GNU/Linux standards, and not go chasing after acceptance by the big guys. Look at what happens to all those other desktops: they all become, sooner or later, to more or less degree, owned by corporations, and then those desktops get changed, streamlined, options removed, our little private, individual worlds are ruined, and we end up with a dilemma -- either conform, and use some desktop that we don't like, that doesn't allow us to configure our machines as it suits us, or just to stop using these machines altogether. (The same, by the way, goes for other applications, programs, distros, etc.; once they are controlleld by some corporation, or by some "inner circle" of developers who have no connection to users.) Things get changed. Look at what happened to the 'Buntus; some would say that they same thing happened to Debian, which is why some rebel developers forked Devuan.
Besides which ... I am sure that there are many other technical issues, much harder than just the renaming of packages, that must be resolved before any great changes can happen, before we get out of the /opt/ folder.
It would be nice to have a Devuan installation disc with TDE already available for installation; I mean, just a plain vanilla Devuan, not somebody's snapshot of their system. (Nik, among others, has released snapshots, which are nice to play around with, nice to see what others are doing; but Nik configures his system as it suits him, so those snapshots don't work for me.)
In the meanwhile, though, I have adapted to the present situation, and I am just glad that TDE exists, as I lose patience with other desktops, and practically have a meltdown whenever I have to use another person's machine, or when I must use public computers.
For this, I have taken to portable apps for Windoze, and for those situations where it is possible to use it, I have created a mini-version of my system on a 256 gb flash drive -- COMPLEAT with root, home, swap partitions, and a UEFI boot partition -- so that, with permission, I can use somebody else's hardware, reboot into my own system. Then when I am reunited with my laptop or desktop, I can insert that flash drive, and transfer files over to my main machine.
Ultimately, I value my freedom more than I do convenience, and don't mind being the outsider. It used to hurt my feelings when I didn't belong to the group of cool kids at school, but 50-60 years later I find that I actually belong with the misfits, that the misfits are always the ones who are the true insiders, the ones who make interesting work, whose lives are more adventurous and exciting.
Whatever minor inconveniences remain in TDE, they are nothing compared to the inconveniences of using some other desktop.
Bill
On 2024-05-21 12:56:37 Felix Miata via tde-users wrote:
I have no understanding /why/ there's any objection to TDE placement in /opt/.
Felix Miata
There seems to be no rationale for putting Everything in /usr/*. I suspect that a lot of developers don't read or understand the Filesystem Heirarchy Standard. Today everything is poured into the same bucket, which pushes developers to come up with some awkward naming conventions as a side-effect. See https://www.pathname.com/fhs/pub/fhs-2.3.html#OPTADDONAPPLICATIONSOFTWAREPAC....
Leslie -- Platform: Linux Distribution: openSUSE Leap 15.5 - x86_64 Desktop Environment: Trinity Qt: 3.5.0 TDE: R14.1.2 tde-config: 1.0
said Felix Miata via tde-users:
| sudo aptitude install tde-trinity
Strangely, I recently discovered that aptitude is no longer on at least one distribution -- the Raspberry Pi 5 version of Debian -- though apt and its variants still are. I wonder if aptitude is falling out of favor. (I discovered it while executing the very command above, which worked with apt and, I suppose, apt-get.)
dep via tde-users composed on 2024-05-22 18:28 (UTC):
said Felix Miata:
| sudo aptitude install tde-trinity
Strangely, I recently discovered that aptitude is no longer on at least one distribution -- the Raspberry Pi 5 version of Debian -- though apt and its variants still are. I wonder if aptitude is falling out of favor. (I discovered it while executing the very command above, which worked with apt and, I suppose, apt-get.)
Is this about availability from the distro, or whether installed by default? I've often found it necessary to apt install it when I wish to use it.
-
Darrell Anderson -
deloptes -
dep -
Dr. Nikolaus Klepp -
Felix Miata -
J Leslie Turriff -
Mike Bird -
Thierry de Coulon -
William Morder