Hey all,
I’ve reached out to the MX Linux group and asked:
How to add a DE to the MX Package Installer? https://forum.mxlinux.org/viewtopic.php?f=93&t=59309
The response is pretty positive and I think it’s at the point of needing a TDE developer to contact their lead developer to work out what/which options are available and what would be the next step.
Copy/Pasting current replies:
########### by Michael-IDA » Sat Jul 18, 2020 8:14 pm [me] I'm not a dev, but there has been interest by the TDE (Trinity Desktop Environment) folks to get added into the 'official' MX build. What, or who, can I point the TDE devs to?
by Jerry3904 » Sat Jul 18, 2020 8:28 pm [Administrator] The Lead Dev: Dolphin Oracle.
by andyprough » Sat Jul 18, 2020 9:16 pm [User] By the way, TDE is extremely easy to add to MX - just add the repos and the gpg signing key from the Debian installation page (https://wiki.trinitydesktop.org/Debian_Trinity_Repository_Installation_Instr...), and then apt update, and apt install tde-trinity. Works very well on MX.
by Stevo » Sat Jul 18, 2020 10:49 pm [Developer] That makes it simple to add to MX PI scripts, but are they looking for real "official" approval from MX, or just being added to the installer?
Maybe they could work with us to set up an official MX-TDE edition, if they're interested, though of course the XFCE-specific MX tools will again have to modified for TDE right after dolphin_oracle has adapted them for the upcoming KDE release. It would probably need both a 32 and a 64-bit release. ###########
For whatever I’m capable, I’ll help.
Best, Michael
Ref: profile - dolphin_oracle https://forum.mxlinux.org/memberlist.php?mode=viewprofile&u=5333&sid...
--------------------------------------------------------------------- To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
On Sunday 19 July 2020 07:58:58 Michael wrote:
Hey all,
I’ve reached out to the MX Linux group and asked:
How to add a DE to the MX Package Installer? https://forum.mxlinux.org/viewtopic.php?f=93&t=59309
The response is pretty positive and I think it’s at the point of needing a TDE developer to contact their lead developer to work out what/which options are available and what would be the next step.
Copy/Pasting current replies:
########### by Michael-IDA » Sat Jul 18, 2020 8:14 pm [me] I'm not a dev, but there has been interest by the TDE (Trinity Desktop Environment) folks to get added into the 'official' MX build. What, or who, can I point the TDE devs to?
by Jerry3904 » Sat Jul 18, 2020 8:28 pm [Administrator] The Lead Dev: Dolphin Oracle.
by andyprough » Sat Jul 18, 2020 9:16 pm [User] By the way, TDE is extremely easy to add to MX - just add the repos and the gpg signing key from the Debian installation page (https://wiki.trinitydesktop.org/Debian_Trinity_Repository_Installation_Ins tructions), and then apt update, and apt install tde-trinity. Works very well on MX.
by Stevo » Sat Jul 18, 2020 10:49 pm [Developer] That makes it simple to add to MX PI scripts, but are they looking for real "official" approval from MX, or just being added to the installer?
Maybe they could work with us to set up an official MX-TDE edition, if they're interested, though of course the XFCE-specific MX tools will again have to modified for TDE right after dolphin_oracle has adapted them for the upcoming KDE release. It would probably need both a 32 and a 64-bit release. ###########
For whatever I’m capable, I’ll help.
Best, Michael
super COOL !
Now if only we can get TDE into other distros ... all in good time.
Bill
--------------------------------------------------------------------- To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Anno domini 2020 Sun, 19 Jul 09:58:58 -0500 Michael scripsit:
Hey all,
I’ve reached out to the MX Linux group and asked:
How to add a DE to the MX Package Installer? https://forum.mxlinux.org/viewtopic.php?f=93&t=59309
The response is pretty positive and I think it’s at the point of needing a TDE developer to contact their lead developer to work out what/which options are available and what would be the next step.
Copy/Pasting current replies:
########### by Michael-IDA » Sat Jul 18, 2020 8:14 pm [me] I'm not a dev, but there has been interest by the TDE (Trinity Desktop Environment) folks to get added into the 'official' MX build. What, or who, can I point the TDE devs to?
by Jerry3904 » Sat Jul 18, 2020 8:28 pm [Administrator] The Lead Dev: Dolphin Oracle.
by andyprough » Sat Jul 18, 2020 9:16 pm [User] By the way, TDE is extremely easy to add to MX - just add the repos and the gpg signing key from the Debian installation page (https://wiki.trinitydesktop.org/Debian_Trinity_Repository_Installation_Instr...), and then apt update, and apt install tde-trinity. Works very well on MX.
by Stevo » Sat Jul 18, 2020 10:49 pm [Developer] That makes it simple to add to MX PI scripts, but are they looking for real "official" approval from MX, or just being added to the installer?
Maybe they could work with us to set up an official MX-TDE edition, if they're interested, though of course the XFCE-specific MX tools will again have to modified for TDE right after dolphin_oracle has adapted them for the upcoming KDE release. It would probably need both a 32 and a 64-bit release. ###########
For whatever I’m capable, I’ll help.
That's quite pleasent news :)
Nik
Best, Michael
Ref: profile - dolphin_oracle https://forum.mxlinux.org/memberlist.php?mode=viewprofile&u=5333&sid...
To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
On Sunday 19 July 2020 09:58:58 am Michael wrote:
Hey all,
I’ve reached out to the MX Linux group and asked:
How to add a DE to the MX Package Installer? https://forum.mxlinux.org/viewtopic.php?f=93&t=59309
The response is pretty positive and I think it’s at the point of needing a TDE developer to contact their lead developer to work out what/which options are available and what would be the next step.
Copy/Pasting current replies:
########### by Michael-IDA » Sat Jul 18, 2020 8:14 pm [me] I'm not a dev, but there has been interest by the TDE (Trinity Desktop Environment) folks to get added into the 'official' MX build. What, or who, can I point the TDE devs to?
by Jerry3904 » Sat Jul 18, 2020 8:28 pm [Administrator] The Lead Dev: Dolphin Oracle.
by andyprough » Sat Jul 18, 2020 9:16 pm [User] By the way, TDE is extremely easy to add to MX - just add the repos and the gpg signing key from the Debian installation page (https://wiki.trinitydesktop.org/Debian_Trinity_Repository_Installation_Ins tructions), and then apt update, and apt install tde-trinity. Works very well on MX.
by Stevo » Sat Jul 18, 2020 10:49 pm [Developer] That makes it simple to add to MX PI scripts, but are they looking for real "official" approval from MX, or just being added to the installer?
Maybe they could work with us to set up an official MX-TDE edition, if they're interested, though of course the XFCE-specific MX tools will again have to modified for TDE right after dolphin_oracle has adapted them for the upcoming KDE release. It would probably need both a 32 and a 64-bit release. ###########
For whatever I’m capable, I’ll help.
This seems too easy.
########### by dolphin_oracle » Sun Jul 19, 2020 12:05 pm the files that we use to define what's in mx-packageinstaller->popular apps are XML files. there are even places for screenshots, pre and post install scripts if extra steps are needed, like adding repos.
https://github.com/MX-Linux/mx-packageinstaller-pkglist ###########
I found 4 examples with external repositories
https://github.com/MX-Linux/mx-packageinstaller-pkglist/search?q=repository&...
To me ‘spotify_64.pm’ seems the closest match to what I believe we’d want. ‘airvpn.pm’ is the most complex, probably good for example/reference. In any event I copy/pasted/edited what I could (attached as tde_64.pm). Which probably needs to go into the TDE git somewhere.
Things that definitely need checking:
- <installable> architecture(s) (I picked 64, not completely sure that’s correct). - method/place for # Import GPG signing key. (needs review by MX dev). - when to use sudo and when it’s not needed (got no real clue why some commands use it). - <description> needs an official English description and then as many translations as we can do.
We also need a TDE developer to interface with dolphin_oracle directly for the ‘official’ request to add it to their system.
Anything else I can help with let me know, Michael
--------------------------------------------------------------------- To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
On Sunday 19 July 2020 07:21:09 pm Michael wrote:
This seems too easy.
########### by dolphin_oracle » Sun Jul 19, 2020 12:05 pm the files that we use to define what's in mx-packageinstaller->popular apps are XML files. there are even places for screenshots, pre and post install scripts if extra steps are needed, like adding repos.
https://github.com/MX-Linux/mx-packageinstaller-pkglist ###########
I found 4 examples with external repositories
https://github.com/MX-Linux/mx-packageinstaller-pkglist/search?q=repository &unscoped_q=repository
To me ‘spotify_64.pm’ seems the closest match to what I believe we’d want. ‘airvpn.pm’ is the most complex, probably good for example/reference. In any event I copy/pasted/edited what I could (attached as tde_64.pm). Which probably needs to go into the TDE git somewhere.
Things that definitely need checking:
- <installable> architecture(s) (I picked 64, not completely sure that’s
correct).
- method/place for # Import GPG signing key. (needs review by MX dev).
- when to use sudo and when it’s not needed (got no real clue why some
commands use it).
- <description> needs an official English description and then as many
translations as we can do.
We also need a TDE developer to interface with dolphin_oracle directly for the ‘official’ request to add it to their system.
Anything else I can help with let me know, Michael
- Updated .pm per dolphin_oracle comments.
- Could use newer screenshot(s) posted to: - - https://www.trinitydesktop.org/screenshots.php - - All those are from 2014. - - If at all possible do one similar to https://www.trinitydesktop.org/media/screenshots/large/tde1.png so that it includes the full, visible, "The Trinity Desktop is a full software desktop..." paragraph. (but possibly I don’t understand the use of that screenshot, so maybe not?)
- .pm should be renamed to tde.pm if TDE is all architecture.
https://forum.mxlinux.org/viewtopic.php?f=93&t=59309
###########
by dolphin_oracle » Sun Jul 19, 2020 8:13 pm you don't need sudo anywhere. the script runs elevated already.
if your packages are 64bit only, the 64 is appropriate. If you also have 32 bit packages, then "all" is appropriate.
you will want to run an apt-get update in the post-uninstall area since you are removing a list. typically I don't remove list files unless there is a chance of some conflict, in which case they should not be left enabled at all. (deb-multimedia is an example here, good packages, but leaving the repo enabled is bad for mx).
for the key, download into /tmp instead of /root. remove the temporary downloaded deb after install.
we prefer the deb-src entries to be commented out by default. our debian.list file is a good example.
###########
--------------------------------------------------------------------- To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Anno domini 2020 Mon, 20 Jul 11:31:17 -0500 Michael scripsit:
On Sunday 19 July 2020 07:21:09 pm Michael wrote:
This seems too easy.
########### by dolphin_oracle » Sun Jul 19, 2020 12:05 pm the files that we use to define what's in mx-packageinstaller->popular apps are XML files. there are even places for screenshots, pre and post install scripts if extra steps are needed, like adding repos.
https://github.com/MX-Linux/mx-packageinstaller-pkglist ###########
I found 4 examples with external repositories
https://github.com/MX-Linux/mx-packageinstaller-pkglist/search?q=repository &unscoped_q=repository
To me ‘spotify_64.pm’ seems the closest match to what I believe we’d want. ‘airvpn.pm’ is the most complex, probably good for example/reference. In any event I copy/pasted/edited what I could (attached as tde_64.pm). Which probably needs to go into the TDE git somewhere.
Things that definitely need checking:
- <installable> architecture(s) (I picked 64, not completely sure that’s
correct).
- method/place for # Import GPG signing key. (needs review by MX dev).
- when to use sudo and when it’s not needed (got no real clue why some
commands use it).
- <description> needs an official English description and then as many
translations as we can do.
We also need a TDE developer to interface with dolphin_oracle directly for the ‘official’ request to add it to their system.
Anything else I can help with let me know, Michael
Updated .pm per dolphin_oracle comments.
Could use newer screenshot(s) posted to:
- All those are from 2014.
- If at all possible do one similar to
https://www.trinitydesktop.org/media/screenshots/large/tde1.png so that it includes the full, visible, "The Trinity Desktop is a full software desktop..." paragraph. (but possibly I don’t understand the use of that screenshot, so maybe not?)
- .pm should be renamed to tde.pm if TDE is all architecture.
https://forum.mxlinux.org/viewtopic.php?f=93&t=59309
###########
by dolphin_oracle » Sun Jul 19, 2020 8:13 pm you don't need sudo anywhere. the script runs elevated already.
if your packages are 64bit only, the 64 is appropriate. If you also have 32 bit packages, then "all" is appropriate.
you will want to run an apt-get update in the post-uninstall area since you are removing a list. typically I don't remove list files unless there is a chance of some conflict, in which case they should not be left enabled at all. (deb-multimedia is an example here, good packages, but leaving the repo enabled is bad for mx).
for the key, download into /tmp instead of /root. remove the temporary downloaded deb after install.
we prefer the deb-src entries to be commented out by default. our debian.list file is a good example.
###########
@ screenshots: there where a number of newer ones on the site, too. I remember that some of my FreeBSD box where there, too, as TDE does quite nicely on FreeBSD these days. Don't know when they vanished, where and why.
Nik
On Monday 20 July 2020 12:28:48 pm Dr. Nikolaus Klepp wrote:
Anno domini 2020 Mon, 20 Jul 11:31:17 -0500
Michael scripsit:
On Sunday 19 July 2020 07:21:09 pm Michael wrote:
This seems too easy.
########### by dolphin_oracle » Sun Jul 19, 2020 12:05 pm the files that we use to define what's in mx-packageinstaller->popular apps are XML files. there are even places for screenshots, pre and post install scripts if extra steps are needed, like adding repos.
https://github.com/MX-Linux/mx-packageinstaller-pkglist ###########
I found 4 examples with external repositories
https://github.com/MX-Linux/mx-packageinstaller-pkglist/search?q=reposi tory &unscoped_q=repository
To me ‘spotify_64.pm’ seems the closest match to what I believe we’d want. ‘airvpn.pm’ is the most complex, probably good for example/reference. In any event I copy/pasted/edited what I could (attached as tde_64.pm). Which probably needs to go into the TDE git somewhere.
Things that definitely need checking:
- <installable> architecture(s) (I picked 64, not completely sure
that’s correct).
- method/place for # Import GPG signing key. (needs review by MX dev).
- when to use sudo and when it’s not needed (got no real clue why some
commands use it).
- <description> needs an official English description and then as many
translations as we can do.
We also need a TDE developer to interface with dolphin_oracle directly for the ‘official’ request to add it to their system.
Anything else I can help with let me know, Michael
Updated .pm per dolphin_oracle comments.
Could use newer screenshot(s) posted to:
- All those are from 2014.
- If at all possible do one similar to
https://www.trinitydesktop.org/media/screenshots/large/tde1.png so that it includes the full, visible, "The Trinity Desktop is a full software desktop..." paragraph. (but possibly I don’t understand the use of that screenshot, so maybe not?)
- .pm should be renamed to tde.pm if TDE is all architecture.
https://forum.mxlinux.org/viewtopic.php?f=93&t=59309
###########
by dolphin_oracle » Sun Jul 19, 2020 8:13 pm you don't need sudo anywhere. the script runs elevated already.
if your packages are 64bit only, the 64 is appropriate. If you also have 32 bit packages, then "all" is appropriate.
you will want to run an apt-get update in the post-uninstall area since you are removing a list. typically I don't remove list files unless there is a chance of some conflict, in which case they should not be left enabled at all. (deb-multimedia is an example here, good packages, but leaving the repo enabled is bad for mx).
for the key, download into /tmp instead of /root. remove the temporary downloaded deb after install.
we prefer the deb-src entries to be commented out by default. our debian.list file is a good example.
###########
@ screenshots: there where a number of newer ones on the site, too. I remember that some of my FreeBSD box where there, too, as TDE does quite nicely on FreeBSD these days. Don't know when they vanished, where and why.
Hopefully last edit of the .pm by me...
I'm scheduled to test it next weekend, I'll update to the list next then (these minor edits are getting spammy, so see the MX formum post till then)
best all, michael..
--------------------------------------------------------------------- To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Anno domini 2020 Mon, 20 Jul 13:23:27 -0500 Michael scripsit:
On Monday 20 July 2020 12:28:48 pm Dr. Nikolaus Klepp wrote:
Anno domini 2020 Mon, 20 Jul 11:31:17 -0500
Michael scripsit:
On Sunday 19 July 2020 07:21:09 pm Michael wrote:
This seems too easy.
########### by dolphin_oracle » Sun Jul 19, 2020 12:05 pm the files that we use to define what's in mx-packageinstaller->popular apps are XML files. there are even places for screenshots, pre and post install scripts if extra steps are needed, like adding repos.
https://github.com/MX-Linux/mx-packageinstaller-pkglist ###########
I found 4 examples with external repositories
https://github.com/MX-Linux/mx-packageinstaller-pkglist/search?q=reposi tory &unscoped_q=repository
To me ‘spotify_64.pm’ seems the closest match to what I believe we’d want. ‘airvpn.pm’ is the most complex, probably good for example/reference. In any event I copy/pasted/edited what I could (attached as tde_64.pm). Which probably needs to go into the TDE git somewhere.
Things that definitely need checking:
- <installable> architecture(s) (I picked 64, not completely sure
that’s correct).
- method/place for # Import GPG signing key. (needs review by MX dev).
- when to use sudo and when it’s not needed (got no real clue why some
commands use it).
- <description> needs an official English description and then as many
translations as we can do.
We also need a TDE developer to interface with dolphin_oracle directly for the ‘official’ request to add it to their system.
Anything else I can help with let me know, Michael
Updated .pm per dolphin_oracle comments.
Could use newer screenshot(s) posted to:
- All those are from 2014.
- If at all possible do one similar to
https://www.trinitydesktop.org/media/screenshots/large/tde1.png so that it includes the full, visible, "The Trinity Desktop is a full software desktop..." paragraph. (but possibly I don’t understand the use of that screenshot, so maybe not?)
- .pm should be renamed to tde.pm if TDE is all architecture.
https://forum.mxlinux.org/viewtopic.php?f=93&t=59309
###########
by dolphin_oracle » Sun Jul 19, 2020 8:13 pm you don't need sudo anywhere. the script runs elevated already.
if your packages are 64bit only, the 64 is appropriate. If you also have 32 bit packages, then "all" is appropriate.
you will want to run an apt-get update in the post-uninstall area since you are removing a list. typically I don't remove list files unless there is a chance of some conflict, in which case they should not be left enabled at all. (deb-multimedia is an example here, good packages, but leaving the repo enabled is bad for mx).
for the key, download into /tmp instead of /root. remove the temporary downloaded deb after install.
we prefer the deb-src entries to be commented out by default. our debian.list file is a good example.
###########
@ screenshots: there where a number of newer ones on the site, too. I remember that some of my FreeBSD box where there, too, as TDE does quite nicely on FreeBSD these days. Don't know when they vanished, where and why.
Hopefully last edit of the .pm by me...
I'm scheduled to test it next weekend, I'll update to the list next then (these minor edits are getting spammy, so see the MX formum post till then)
best all, michael..
Hi Michael,
When I have MX installed, whet do I do with that tde.pm ?
Nik
On Thursday 23 July 2020 06:07:25 am Dr. Nikolaus Klepp wrote:
Anno domini 2020 Mon, 20 Jul 13:23:27 -0500
Michael scripsit:
On Monday 20 July 2020 12:28:48 pm Dr. Nikolaus Klepp wrote:
Anno domini 2020 Mon, 20 Jul 11:31:17 -0500
Michael scripsit:
On Sunday 19 July 2020 07:21:09 pm Michael wrote:
This seems too easy.
########### by dolphin_oracle » Sun Jul 19, 2020 12:05 pm the files that we use to define what's in mx-packageinstaller->popular apps are XML files. there are even places for screenshots, pre and post install scripts if extra steps are needed, like adding repos.
https://github.com/MX-Linux/mx-packageinstaller-pkglist ###########
I found 4 examples with external repositories
https://github.com/MX-Linux/mx-packageinstaller-pkglist/search?q=re posi tory &unscoped_q=repository
To me ‘spotify_64.pm’ seems the closest match to what I believe we’d want. ‘airvpn.pm’ is the most complex, probably good for example/reference. In any event I copy/pasted/edited what I could (attached as tde_64.pm). Which probably needs to go into the TDE git somewhere.
Things that definitely need checking:
- <installable> architecture(s) (I picked 64, not completely sure
that’s correct).
- method/place for # Import GPG signing key. (needs review by MX
dev). - when to use sudo and when it’s not needed (got no real clue why some commands use it).
- <description> needs an official English description and then as
many translations as we can do.
We also need a TDE developer to interface with dolphin_oracle directly for the ‘official’ request to add it to their system.
Anything else I can help with let me know, Michael
Updated .pm per dolphin_oracle comments.
Could use newer screenshot(s) posted to:
- All those are from 2014.
- If at all possible do one similar to
https://www.trinitydesktop.org/media/screenshots/large/tde1.png so that it includes the full, visible, "The Trinity Desktop is a full software desktop..." paragraph. (but possibly I don’t understand the use of that screenshot, so maybe not?)
- .pm should be renamed to tde.pm if TDE is all architecture.
https://forum.mxlinux.org/viewtopic.php?f=93&t=59309
###########
by dolphin_oracle » Sun Jul 19, 2020 8:13 pm you don't need sudo anywhere. the script runs elevated already.
if your packages are 64bit only, the 64 is appropriate. If you also have 32 bit packages, then "all" is appropriate.
you will want to run an apt-get update in the post-uninstall area since you are removing a list. typically I don't remove list files unless there is a chance of some conflict, in which case they should not be left enabled at all. (deb-multimedia is an example here, good packages, but leaving the repo enabled is bad for mx).
for the key, download into /tmp instead of /root. remove the temporary downloaded deb after install.
we prefer the deb-src entries to be commented out by default. our debian.list file is a good example.
###########
@ screenshots: there where a number of newer ones on the site, too. I remember that some of my FreeBSD box where there, too, as TDE does quite nicely on FreeBSD these days. Don't know when they vanished, where and why.
Hopefully last edit of the .pm by me...
I'm scheduled to test it next weekend, I'll update to the list next then (these minor edits are getting spammy, so see the MX formum post till then)
best all, michael..
Hi Michael,
When I have MX installed, whet do I do with that tde.pm ?
Hi Nik,
Notes: 1) This has not been tested! Do scan for typo’s before use. (wget line was tested) 2) I’ve set the attached .pm for 64 bit architectures. (change as needed) 3) AFAIK this only works if you’ve installed the full MX. (so you’ll already have Xfce4 installed)
After the MX install, drop it in:
/usr/share/mx-packageinstaller-pkglist -rw-r--r-- root root
Then from Xfce4
Menu >> MX Tools >> MX Package Installer {Tab} Popular Applications {Expand} Desktop Environments {Check} Trinity Desktop Environment {Click} Install
Logout of Xfce4 Login TDE {set default window manager, etc.}
I think that’s it. Let me know how it goes :)
Best, Michael
Notes continued: 4) Still needs translations of the description. 5) Has several extra, extraneous comments.
Ref: https://forum.mxlinux.org/viewtopic.php?p=587347#p587347
--------------------------------------------------------------------- To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
On Thursday 23 of July 2020 16:46:21 Michael wrote:
On Thursday 23 July 2020 06:07:25 am Dr. Nikolaus Klepp wrote:
Anno domini 2020 Mon, 20 Jul 13:23:27 -0500
Michael scripsit:
On Monday 20 July 2020 12:28:48 pm Dr. Nikolaus Klepp wrote:
Anno domini 2020 Mon, 20 Jul 11:31:17 -0500
Michael scripsit:
On Sunday 19 July 2020 07:21:09 pm Michael wrote:
This seems too easy.
########### by dolphin_oracle » Sun Jul 19, 2020 12:05 pm the files that we use to define what's in mx-packageinstaller->popular apps are XML files. there are even places for screenshots, pre and post install scripts if extra steps are needed, like adding repos.
https://github.com/MX-Linux/mx-packageinstaller-pkglist ###########
I found 4 examples with external repositories
https://github.com/MX-Linux/mx-packageinstaller-pkglist/search ?q=re posi tory &unscoped_q=repository
To me ‘spotify_64.pm’ seems the closest match to what I believe we’d want. ‘airvpn.pm’ is the most complex, probably good for example/reference. In any event I copy/pasted/edited what I could (attached as tde_64.pm). Which probably needs to go into the TDE git somewhere.
Things that definitely need checking:
- <installable> architecture(s) (I picked 64, not completely
sure that’s correct).
- method/place for # Import GPG signing key. (needs review by
MX dev). - when to use sudo and when it’s not needed (got no real clue why some commands use it).
- <description> needs an official English description and then
as many translations as we can do.
We also need a TDE developer to interface with dolphin_oracle directly for the ‘official’ request to add it to their system.
Anything else I can help with let me know, Michael
Updated .pm per dolphin_oracle comments.
Could use newer screenshot(s) posted to:
- All those are from 2014.
- If at all possible do one similar to
https://www.trinitydesktop.org/media/screenshots/large/tde1.png so that it includes the full, visible, "The Trinity Desktop is a full software desktop..." paragraph. (but possibly I don’t understand the use of that screenshot, so maybe not?)
- .pm should be renamed to tde.pm if TDE is all architecture.
https://forum.mxlinux.org/viewtopic.php?f=93&t=59309
###########
by dolphin_oracle » Sun Jul 19, 2020 8:13 pm you don't need sudo anywhere. the script runs elevated already.
if your packages are 64bit only, the 64 is appropriate. If you also have 32 bit packages, then "all" is appropriate.
you will want to run an apt-get update in the post-uninstall area since you are removing a list. typically I don't remove list files unless there is a chance of some conflict, in which case they should not be left enabled at all. (deb-multimedia is an example here, good packages, but leaving the repo enabled is bad for mx).
for the key, download into /tmp instead of /root. remove the temporary downloaded deb after install.
we prefer the deb-src entries to be commented out by default. our debian.list file is a good example.
###########
@ screenshots: there where a number of newer ones on the site, too. I remember that some of my FreeBSD box where there, too, as TDE does quite nicely on FreeBSD these days. Don't know when they vanished, where and why.
Hopefully last edit of the .pm by me...
I'm scheduled to test it next weekend, I'll update to the list next then (these minor edits are getting spammy, so see the MX formum post till then)
best all, michael..
Hi Michael,
When I have MX installed, whet do I do with that tde.pm ?
Hi Nik,
Notes:
- This has not been tested! Do scan for typo’s before use. (wget line
was tested) 2) I’ve set the attached .pm for 64 bit architectures. (change as needed) 3) AFAIK this only works if you’ve installed the full MX. (so you’ll already have Xfce4 installed)
After the MX install, drop it in:
/usr/share/mx-packageinstaller-pkglist -rw-r--r-- root root
Then from Xfce4
Menu >> MX Tools >> MX Package Installer {Tab} Popular Applications {Expand} Desktop Environments {Check} Trinity Desktop Environment {Click} Install
Logout of Xfce4 Login TDE {set default window manager, etc.}
I think that’s it. Let me know how it goes :)
Best, Michael
Notes continued: 4) Still needs translations of the description. 5) Has several extra, extraneous comments.
Ref: https://forum.mxlinux.org/viewtopic.php?p=587347#p587347
Is it necessary to have files for each architecture? Is it possible for one file to provide that information for all architectures?
I haven't looked at what architectures are supported in MX, but I assume we provide packages for all the needed architectures. Because the repository URL is the same for all architectures, and therefore the same GPG key, it seems unnecessary to create multiple files that will contain the same data, only with a difference for the architecture.
Cheers
On Thursday 23 July 2020 09:55:38 am Slávek Banko wrote:
On Thursday 23 of July 2020 16:46:21 Michael wrote:
On Thursday 23 July 2020 06:07:25 am Dr. Nikolaus Klepp wrote:
Anno domini 2020 Mon, 20 Jul 13:23:27 -0500
Michael scripsit:
On Monday 20 July 2020 12:28:48 pm Dr. Nikolaus Klepp wrote:
Anno domini 2020 Mon, 20 Jul 11:31:17 -0500
Michael scripsit:
On Sunday 19 July 2020 07:21:09 pm Michael wrote: > This seems too easy. > > ########### > by dolphin_oracle » Sun Jul 19, 2020 12:05 pm > the files that we use to define what's in > mx-packageinstaller->popular apps are XML files. there are > even places for screenshots, pre and post install scripts if > extra steps are needed, like adding repos. > > https://github.com/MX-Linux/mx-packageinstaller-pkglist > ########### > > I found 4 examples with external repositories > > https://github.com/MX-Linux/mx-packageinstaller-pkglist/search >?q=re posi tory &unscoped_q=repository > > To me ‘spotify_64.pm’ seems the closest match to what I > believe we’d want. ‘airvpn.pm’ is the most complex, probably > good for example/reference. In any event I copy/pasted/edited > what I could (attached as tde_64.pm). Which probably needs to > go into the TDE git somewhere. > > Things that definitely need checking: > > - <installable> architecture(s) (I picked 64, not completely > sure that’s correct). > - method/place for # Import GPG signing key. (needs review by > MX dev). - when to use sudo and when it’s not needed (got no > real clue why some commands use it). > - <description> needs an official English description and then > as many translations as we can do. > > We also need a TDE developer to interface with dolphin_oracle > directly for the ‘official’ request to add it to their system. > > Anything else I can help with let me know, > Michael
Updated .pm per dolphin_oracle comments.
Could use newer screenshot(s) posted to:
- All those are from 2014.
- If at all possible do one similar to
https://www.trinitydesktop.org/media/screenshots/large/tde1.png so that it includes the full, visible, "The Trinity Desktop is a full software desktop..." paragraph. (but possibly I don’t understand the use of that screenshot, so maybe not?)
- .pm should be renamed to tde.pm if TDE is all architecture.
https://forum.mxlinux.org/viewtopic.php?f=93&t=59309
> ###########
by dolphin_oracle » Sun Jul 19, 2020 8:13 pm you don't need sudo anywhere. the script runs elevated already.
if your packages are 64bit only, the 64 is appropriate. If you also have 32 bit packages, then "all" is appropriate.
you will want to run an apt-get update in the post-uninstall area since you are removing a list. typically I don't remove list files unless there is a chance of some conflict, in which case they should not be left enabled at all. (deb-multimedia is an example here, good packages, but leaving the repo enabled is bad for mx).
for the key, download into /tmp instead of /root. remove the temporary downloaded deb after install.
we prefer the deb-src entries to be commented out by default. our debian.list file is a good example.
> ###########
@ screenshots: there where a number of newer ones on the site, too. I remember that some of my FreeBSD box where there, too, as TDE does quite nicely on FreeBSD these days. Don't know when they vanished, where and why.
Hopefully last edit of the .pm by me...
I'm scheduled to test it next weekend, I'll update to the list next then (these minor edits are getting spammy, so see the MX formum post till then)
best all, michael..
Hi Michael,
When I have MX installed, whet do I do with that tde.pm ?
Hi Nik,
Notes:
- This has not been tested! Do scan for typo’s before use. (wget line
was tested) 2) I’ve set the attached .pm for 64 bit architectures. (change as needed) 3) AFAIK this only works if you’ve installed the full MX. (so you’ll already have Xfce4 installed)
After the MX install, drop it in:
/usr/share/mx-packageinstaller-pkglist -rw-r--r-- root root
Then from Xfce4
Menu >> MX Tools >> MX Package Installer {Tab} Popular Applications {Expand} Desktop Environments {Check} Trinity Desktop Environment {Click} Install
Logout of Xfce4 Login TDE {set default window manager, etc.}
I think that’s it. Let me know how it goes :)
Best, Michael
Notes continued: 4) Still needs translations of the description. 5) Has several extra, extraneous comments.
Ref: https://forum.mxlinux.org/viewtopic.php?p=587347#p587347
Is it necessary to have files for each architecture? Is it possible for one file to provide that information for all architectures?
I haven't looked at what architectures are supported in MX, but I assume we provide packages for all the needed architectures. Because the repository URL is the same for all architectures, and therefore the same GPG key, it seems unnecessary to create multiple files that will contain the same data, only with a difference for the architecture.
Hi Slávek,
That was one of my questions earlier in this thread, "What architecture is TDE?" Based on above, I'm changing it to 'all.'
--------------------------------------------------------------------- To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
On Thursday 23 of July 2020 19:32:56 Michael wrote:
On Thursday 23 July 2020 09:55:38 am Slávek Banko wrote:
On Thursday 23 of July 2020 16:46:21 Michael wrote:
On Thursday 23 July 2020 06:07:25 am Dr. Nikolaus Klepp wrote:
Anno domini 2020 Mon, 20 Jul 13:23:27 -0500
Michael scripsit:
On Monday 20 July 2020 12:28:48 pm Dr. Nikolaus Klepp wrote:
Anno domini 2020 Mon, 20 Jul 11:31:17 -0500
Michael scripsit: > On Sunday 19 July 2020 07:21:09 pm Michael wrote: > > This seems too easy. > > > > ########### > > by dolphin_oracle » Sun Jul 19, 2020 12:05 pm > > the files that we use to define what's in > > mx-packageinstaller->popular apps are XML files. there are > > even places for screenshots, pre and post install scripts > > if extra steps are needed, like adding repos. > > > > https://github.com/MX-Linux/mx-packageinstaller-pkglist > > ########### > > > > I found 4 examples with external repositories > > > > https://github.com/MX-Linux/mx-packageinstaller-pkglist/se > >arch ?q=re posi tory &unscoped_q=repository > > > > To me ‘spotify_64.pm’ seems the closest match to what I > > believe we’d want. ‘airvpn.pm’ is the most complex, > > probably good for example/reference. In any event I > > copy/pasted/edited what I could (attached as tde_64.pm). > > Which probably needs to go into the TDE git somewhere. > > > > Things that definitely need checking: > > > > - <installable> architecture(s) (I picked 64, not > > completely sure that’s correct). > > - method/place for # Import GPG signing key. (needs > > review by MX dev). - when to use sudo and when it’s not > > needed (got no real clue why some commands use it). > > - <description> needs an official English description and > > then as many translations as we can do. > > > > We also need a TDE developer to interface with > > dolphin_oracle directly for the ‘official’ request to add > > it to their system. > > > > Anything else I can help with let me know, > > Michael > > - Updated .pm per dolphin_oracle comments. > > - Could use newer screenshot(s) posted to: > - - https://www.trinitydesktop.org/screenshots.php > - - All those are from 2014. > - - If at all possible do one similar to > https://www.trinitydesktop.org/media/screenshots/large/tde1. >png so that it includes the full, visible, "The Trinity > Desktop is a full software desktop..." paragraph. (but > possibly I don’t understand the use of that screenshot, so > maybe not?) > > - .pm should be renamed to tde.pm if TDE is all > architecture. > > > https://forum.mxlinux.org/viewtopic.php?f=93&t=59309 > > > ########### > > by dolphin_oracle » Sun Jul 19, 2020 8:13 pm > you don't need sudo anywhere. the script runs elevated > already. > > if your packages are 64bit only, the 64 is appropriate. If > you also have 32 bit packages, then "all" is appropriate. > > you will want to run an apt-get update in the post-uninstall > area since you are removing a list. typically I don't remove > list files unless there is a chance of some conflict, in > which case they should not be left enabled at all. > (deb-multimedia is an example here, good packages, but > leaving the repo enabled is bad for mx). > > for the key, download into /tmp instead of /root. remove the > temporary downloaded deb after install. > > we prefer the deb-src entries to be commented out by > default. our debian.list file is a good example. > > > ###########
@ screenshots: there where a number of newer ones on the site, too. I remember that some of my FreeBSD box where there, too, as TDE does quite nicely on FreeBSD these days. Don't know when they vanished, where and why.
Hopefully last edit of the .pm by me...
I'm scheduled to test it next weekend, I'll update to the list next then (these minor edits are getting spammy, so see the MX formum post till then)
best all, michael..
Hi Michael,
When I have MX installed, whet do I do with that tde.pm ?
Hi Nik,
Notes:
- This has not been tested! Do scan for typo’s before use. (wget
line was tested) 2) I’ve set the attached .pm for 64 bit architectures. (change as needed) 3) AFAIK this only works if you’ve installed the full MX. (so you’ll already have Xfce4 installed)
After the MX install, drop it in:
/usr/share/mx-packageinstaller-pkglist -rw-r--r-- root root
Then from Xfce4
Menu >> MX Tools >> MX Package Installer {Tab} Popular Applications {Expand} Desktop Environments {Check} Trinity Desktop Environment {Click} Install
Logout of Xfce4 Login TDE {set default window manager, etc.}
I think that’s it. Let me know how it goes :)
Best, Michael
Notes continued: 4) Still needs translations of the description. 5) Has several extra, extraneous comments.
Ref: https://forum.mxlinux.org/viewtopic.php?p=587347#p587347
Is it necessary to have files for each architecture? Is it possible for one file to provide that information for all architectures?
I haven't looked at what architectures are supported in MX, but I assume we provide packages for all the needed architectures. Because the repository URL is the same for all architectures, and therefore the same GPG key, it seems unnecessary to create multiple files that will contain the same data, only with a difference for the architecture.
Hi Slávek,
That was one of my questions earlier in this thread, "What architecture is TDE?" Based on above, I'm changing it to 'all.'
You can see the list of architectures on the wiki: https://wiki.trinitydesktop.org/Debian_Trinity_Repository_Installation_Instr...
For Ubuntu, the list of available architectures is smaller: https://wiki.trinitydesktop.org/Ubuntu_Trinity_Repository_Installation_Instr...
Cheers
On Thursday 23 July 2020 12:42:37 pm Slávek Banko wrote:
On Thursday 23 of July 2020 19:32:56 Michael wrote:
On Thursday 23 July 2020 09:55:38 am Slávek Banko wrote:
On Thursday 23 of July 2020 16:46:21 Michael wrote:
On Thursday 23 July 2020 06:07:25 am Dr. Nikolaus Klepp wrote:
Anno domini 2020 Mon, 20 Jul 13:23:27 -0500
Michael scripsit:
On Monday 20 July 2020 12:28:48 pm Dr. Nikolaus Klepp wrote: > Anno domini 2020 Mon, 20 Jul 11:31:17 -0500 > > Michael scripsit: > > On Sunday 19 July 2020 07:21:09 pm Michael wrote: > > > This seems too easy. > > > > > > ########### > > > by dolphin_oracle » Sun Jul 19, 2020 12:05 pm > > > the files that we use to define what's in > > > mx-packageinstaller->popular apps are XML files. there are > > > even places for screenshots, pre and post install scripts > > > if extra steps are needed, like adding repos. > > > > > > https://github.com/MX-Linux/mx-packageinstaller-pkglist > > > ########### > > > > > > I found 4 examples with external repositories > > > > > > https://github.com/MX-Linux/mx-packageinstaller-pkglist/se > > >arch ?q=re posi tory &unscoped_q=repository > > > > > > To me ‘spotify_64.pm’ seems the closest match to what I > > > believe we’d want. ‘airvpn.pm’ is the most complex, > > > probably good for example/reference. In any event I > > > copy/pasted/edited what I could (attached as tde_64.pm). > > > Which probably needs to go into the TDE git somewhere. > > > > > > Things that definitely need checking: > > > > > > - <installable> architecture(s) (I picked 64, not > > > completely sure that’s correct). > > > - method/place for # Import GPG signing key. (needs > > > review by MX dev). - when to use sudo and when it’s not > > > needed (got no real clue why some commands use it). > > > - <description> needs an official English description and > > > then as many translations as we can do. > > > > > > We also need a TDE developer to interface with > > > dolphin_oracle directly for the ‘official’ request to add > > > it to their system. > > > > > > Anything else I can help with let me know, > > > Michael > > > > - Updated .pm per dolphin_oracle comments. > > > > - Could use newer screenshot(s) posted to: > > - - https://www.trinitydesktop.org/screenshots.php > > - - All those are from 2014. > > - - If at all possible do one similar to > > https://www.trinitydesktop.org/media/screenshots/large/tde1. > >png so that it includes the full, visible, "The Trinity > > Desktop is a full software desktop..." paragraph. (but > > possibly I don’t understand the use of that screenshot, so > > maybe not?) > > > > - .pm should be renamed to tde.pm if TDE is all > > architecture. > > > > > > https://forum.mxlinux.org/viewtopic.php?f=93&t=59309 > > > > > ########### > > > > by dolphin_oracle » Sun Jul 19, 2020 8:13 pm > > you don't need sudo anywhere. the script runs elevated > > already. > > > > if your packages are 64bit only, the 64 is appropriate. If > > you also have 32 bit packages, then "all" is appropriate. > > > > you will want to run an apt-get update in the post-uninstall > > area since you are removing a list. typically I don't remove > > list files unless there is a chance of some conflict, in > > which case they should not be left enabled at all. > > (deb-multimedia is an example here, good packages, but > > leaving the repo enabled is bad for mx). > > > > for the key, download into /tmp instead of /root. remove the > > temporary downloaded deb after install. > > > > we prefer the deb-src entries to be commented out by > > default. our debian.list file is a good example. > > > > > ########### > > @ screenshots: there where a number of newer ones on the site, > too. I remember that some of my FreeBSD box where there, too, > as TDE does quite nicely on FreeBSD these days. Don't know > when they vanished, where and why.
Hopefully last edit of the .pm by me...
I'm scheduled to test it next weekend, I'll update to the list next then (these minor edits are getting spammy, so see the MX formum post till then)
best all, michael..
Hi Michael,
When I have MX installed, whet do I do with that tde.pm ?
Hi Nik,
Notes:
- This has not been tested! Do scan for typo’s before use. (wget
line was tested) 2) I’ve set the attached .pm for 64 bit architectures. (change as needed) 3) AFAIK this only works if you’ve installed the full MX. (so you’ll already have Xfce4 installed)
After the MX install, drop it in:
/usr/share/mx-packageinstaller-pkglist -rw-r--r-- root root
Then from Xfce4
Menu >> MX Tools >> MX Package Installer {Tab} Popular Applications {Expand} Desktop Environments {Check} Trinity Desktop Environment {Click} Install
Logout of Xfce4 Login TDE {set default window manager, etc.}
I think that’s it. Let me know how it goes :)
Best, Michael
Notes continued: 4) Still needs translations of the description. 5) Has several extra, extraneous comments.
Ref: https://forum.mxlinux.org/viewtopic.php?p=587347#p587347
Is it necessary to have files for each architecture? Is it possible for one file to provide that information for all architectures?
I haven't looked at what architectures are supported in MX, but I assume we provide packages for all the needed architectures. Because the repository URL is the same for all architectures, and therefore the same GPG key, it seems unnecessary to create multiple files that will contain the same data, only with a difference for the architecture.
Hi Slávek,
That was one of my questions earlier in this thread, "What architecture is TDE?" Based on above, I'm changing it to 'all.'
You can see the list of architectures on the wiki: https://wiki.trinitydesktop.org/Debian_Trinity_Repository_Installation_Inst ructions
For Ubuntu, the list of available architectures is smaller: https://wiki.trinitydesktop.org/Ubuntu_Trinity_Repository_Installation_Inst ructions
Cheers
Yes I know that page is there, that's what I wrote the .pm from...
10.x - buster : amd64, i386, armel, armhf, arm64, ppc64el
"amd64, i386, armel, armhf, arm64, ppc64el" means nothing to 99% of computer users, myself included.
I, and pretty much everyone I've ever known, who's not basically a kernel developer goes:
"It said '10.x - buster' that must be what I need." - or - "I have an AMD 64 bit processor, it said so on the box, so lets pick 'amd64' and try."
No offense but that page might as well have random letters after ‘buster’ to the normal user.
Best, Michael
--------------------------------------------------------------------- To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Anno domini 2020 Thu, 23 Jul 09:46:21 -0500 Michael scripsit:
On Thursday 23 July 2020 06:07:25 am Dr. Nikolaus Klepp wrote:
Anno domini 2020 Mon, 20 Jul 13:23:27 -0500
Michael scripsit:
On Monday 20 July 2020 12:28:48 pm Dr. Nikolaus Klepp wrote:
Anno domini 2020 Mon, 20 Jul 11:31:17 -0500
Michael scripsit:
On Sunday 19 July 2020 07:21:09 pm Michael wrote:
This seems too easy.
########### by dolphin_oracle » Sun Jul 19, 2020 12:05 pm the files that we use to define what's in mx-packageinstaller->popular apps are XML files. there are even places for screenshots, pre and post install scripts if extra steps are needed, like adding repos.
https://github.com/MX-Linux/mx-packageinstaller-pkglist ###########
I found 4 examples with external repositories
https://github.com/MX-Linux/mx-packageinstaller-pkglist/search?q=re posi tory &unscoped_q=repository
To me ‘spotify_64.pm’ seems the closest match to what I believe we’d want. ‘airvpn.pm’ is the most complex, probably good for example/reference. In any event I copy/pasted/edited what I could (attached as tde_64.pm). Which probably needs to go into the TDE git somewhere.
Things that definitely need checking:
- <installable> architecture(s) (I picked 64, not completely sure
that’s correct).
- method/place for # Import GPG signing key. (needs review by MX
dev). - when to use sudo and when it’s not needed (got no real clue why some commands use it).
- <description> needs an official English description and then as
many translations as we can do.
We also need a TDE developer to interface with dolphin_oracle directly for the ‘official’ request to add it to their system.
Anything else I can help with let me know, Michael
Updated .pm per dolphin_oracle comments.
Could use newer screenshot(s) posted to:
- All those are from 2014.
- If at all possible do one similar to
https://www.trinitydesktop.org/media/screenshots/large/tde1.png so that it includes the full, visible, "The Trinity Desktop is a full software desktop..." paragraph. (but possibly I don’t understand the use of that screenshot, so maybe not?)
- .pm should be renamed to tde.pm if TDE is all architecture.
https://forum.mxlinux.org/viewtopic.php?f=93&t=59309
###########
by dolphin_oracle » Sun Jul 19, 2020 8:13 pm you don't need sudo anywhere. the script runs elevated already.
if your packages are 64bit only, the 64 is appropriate. If you also have 32 bit packages, then "all" is appropriate.
you will want to run an apt-get update in the post-uninstall area since you are removing a list. typically I don't remove list files unless there is a chance of some conflict, in which case they should not be left enabled at all. (deb-multimedia is an example here, good packages, but leaving the repo enabled is bad for mx).
for the key, download into /tmp instead of /root. remove the temporary downloaded deb after install.
we prefer the deb-src entries to be commented out by default. our debian.list file is a good example.
###########
@ screenshots: there where a number of newer ones on the site, too. I remember that some of my FreeBSD box where there, too, as TDE does quite nicely on FreeBSD these days. Don't know when they vanished, where and why.
Hopefully last edit of the .pm by me...
I'm scheduled to test it next weekend, I'll update to the list next then (these minor edits are getting spammy, so see the MX formum post till then)
best all, michael..
Hi Michael,
When I have MX installed, whet do I do with that tde.pm ?
Hi Nik,
Notes:
- This has not been tested! Do scan for typo’s before use. (wget line was
tested) 2) I’ve set the attached .pm for 64 bit architectures. (change as needed) 3) AFAIK this only works if you’ve installed the full MX. (so you’ll already have Xfce4 installed)
After the MX install, drop it in:
/usr/share/mx-packageinstaller-pkglist -rw-r--r-- root root
Then from Xfce4
Menu >> MX Tools >> MX Package Installer {Tab} Popular Applications {Expand} Desktop Environments {Check} Trinity Desktop Environment {Click} Install
Logout of Xfce4 Login TDE {set default window manager, etc.}
I think that’s it. Let me know how it goes :)
Best, Michael
Notes continued: 4) Still needs translations of the description. 5) Has several extra, extraneous comments.
Ref: https://forum.mxlinux.org/viewtopic.php?p=587347#p587347
Playing dumb user (aka click and hope for the best) actually works - looks like it's downloading and installing TDE :)
Login will need to wayt till I have physical access to the testmachine - I'm now running over ssh.
Nik
Anno domini 2020 Thu, 23 Jul 09:46:21 -0500 Michael scripsit:
On Thursday 23 July 2020 06:07:25 am Dr. Nikolaus Klepp wrote:
Anno domini 2020 Mon, 20 Jul 13:23:27 -0500
Michael scripsit:
On Monday 20 July 2020 12:28:48 pm Dr. Nikolaus Klepp wrote:
Anno domini 2020 Mon, 20 Jul 11:31:17 -0500
Michael scripsit:
On Sunday 19 July 2020 07:21:09 pm Michael wrote:
This seems too easy.
########### by dolphin_oracle » Sun Jul 19, 2020 12:05 pm the files that we use to define what's in mx-packageinstaller->popular apps are XML files. there are even places for screenshots, pre and post install scripts if extra steps are needed, like adding repos.
https://github.com/MX-Linux/mx-packageinstaller-pkglist ###########
I found 4 examples with external repositories
https://github.com/MX-Linux/mx-packageinstaller-pkglist/search?q=re posi tory &unscoped_q=repository
To me ‘spotify_64.pm’ seems the closest match to what I believe we’d want. ‘airvpn.pm’ is the most complex, probably good for example/reference. In any event I copy/pasted/edited what I could (attached as tde_64.pm). Which probably needs to go into the TDE git somewhere.
Things that definitely need checking:
- <installable> architecture(s) (I picked 64, not completely sure
that’s correct).
- method/place for # Import GPG signing key. (needs review by MX
dev). - when to use sudo and when it’s not needed (got no real clue why some commands use it).
- <description> needs an official English description and then as
many translations as we can do.
We also need a TDE developer to interface with dolphin_oracle directly for the ‘official’ request to add it to their system.
Anything else I can help with let me know, Michael
Updated .pm per dolphin_oracle comments.
Could use newer screenshot(s) posted to:
- All those are from 2014.
- If at all possible do one similar to
https://www.trinitydesktop.org/media/screenshots/large/tde1.png so that it includes the full, visible, "The Trinity Desktop is a full software desktop..." paragraph. (but possibly I don’t understand the use of that screenshot, so maybe not?)
- .pm should be renamed to tde.pm if TDE is all architecture.
https://forum.mxlinux.org/viewtopic.php?f=93&t=59309
###########
by dolphin_oracle » Sun Jul 19, 2020 8:13 pm you don't need sudo anywhere. the script runs elevated already.
if your packages are 64bit only, the 64 is appropriate. If you also have 32 bit packages, then "all" is appropriate.
you will want to run an apt-get update in the post-uninstall area since you are removing a list. typically I don't remove list files unless there is a chance of some conflict, in which case they should not be left enabled at all. (deb-multimedia is an example here, good packages, but leaving the repo enabled is bad for mx).
for the key, download into /tmp instead of /root. remove the temporary downloaded deb after install.
we prefer the deb-src entries to be commented out by default. our debian.list file is a good example.
###########
@ screenshots: there where a number of newer ones on the site, too. I remember that some of my FreeBSD box where there, too, as TDE does quite nicely on FreeBSD these days. Don't know when they vanished, where and why.
Hopefully last edit of the .pm by me...
I'm scheduled to test it next weekend, I'll update to the list next then (these minor edits are getting spammy, so see the MX formum post till then)
best all, michael..
Hi Michael,
When I have MX installed, whet do I do with that tde.pm ?
Hi Nik,
Notes:
- This has not been tested! Do scan for typo’s before use. (wget line was
tested) 2) I’ve set the attached .pm for 64 bit architectures. (change as needed) 3) AFAIK this only works if you’ve installed the full MX. (so you’ll already have Xfce4 installed)
After the MX install, drop it in:
/usr/share/mx-packageinstaller-pkglist -rw-r--r-- root root
Then from Xfce4
Menu >> MX Tools >> MX Package Installer {Tab} Popular Applications {Expand} Desktop Environments {Check} Trinity Desktop Environment {Click} Install
Logout of Xfce4 Login TDE {set default window manager, etc.}
I think that’s it. Let me know how it goes :)
Best, Michael
Notes continued: 4) Still needs translations of the description. 5) Has several extra, extraneous comments.
Ref: https://forum.mxlinux.org/viewtopic.php?p=587347#p587347
Ok, almost everything went smooth:
After download completed and the first packages got installed, the console got confused by escapecodes. Not nice to look at, but just cosmetic.
At the end I got this error:
"Fehler traten auf beim Bearbeiten von:\n htdig\n khelpcenter-trinity\n tdebase-trinity\n tde-core-trinity\n tde-trinity\n tex-common" "E: Sub-process /usr/bin/dpkg returned an error code (1)" +++ void MainWindow::refreshPopularApps() +++ +++ QStringList MainWindow::listInstalled() +++ dpkg --get-selections | grep -v deinstall | cut -f1 +++ void MainWindow::displayPopularApps() const +++
a manual "apt-get install --fix-missing" just configured these packages: htdig khelpcenter-trinity tde-core-trinity tde-trinity tdebase-trinity tex-common
TDE login works as expected. Languagepack is missing (can that be selected by the user in the GUI?)
On TDE mx-updater is kind of broken: it shows the number of available updates, but it cannot install the updates.
Handbook and some other desktop ikons have a generic "empty page" icon, but work.
So basicly an easy way to add TDE to MX - well done :)
Nik
On Thursday 23 July 2020 10:53:22 am Dr. Nikolaus Klepp wrote:
Ref: https://forum.mxlinux.org/viewtopic.php?p=587347#p587347
Ok, almost everything went smooth:
After download completed and the first packages got installed, the console got confused by escapecodes. Not nice to look at, but just cosmetic.
At the end I got this error:
"Fehler traten auf beim Bearbeiten von:\n htdig\n khelpcenter-trinity\n tdebase-trinity\n tde-core-trinity\n tde-trinity\n tex-common" "E: Sub-process /usr/bin/dpkg returned an error code (1)" +++ void MainWindow::refreshPopularApps() +++ +++ QStringList MainWindow::listInstalled() +++ dpkg --get-selections | grep -v deinstall | cut -f1 +++ void MainWindow::displayPopularApps() const +++
a manual "apt-get install --fix-missing" just configured these packages: htdig khelpcenter-trinity tde-core-trinity tde-trinity tdebase-trinity tex-common
TDE login works as expected. Languagepack is missing (can that be selected by the user in the GUI?)
On TDE mx-updater is kind of broken: it shows the number of available updates, but it cannot install the updates.
Handbook and some other desktop ikons have a generic "empty page" icon, but work.
So basicly an easy way to add TDE to MX - well done :)
For blind code that went better than I expected. Re-posted to the MX forum and I’ll have time this weekend to try it myself and make any fixes then.
Best, Michael
--------------------------------------------------------------------- To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting