On Tuesday 05 February 2019 07:23:51 pm Stefan Krusche wrote:

Am Dienstag, 5. Februar 2019 schrieb Michael:

...

Okay, I should go try to look this up, but, is there a meta package(s) or something that will install every TDE application that exists?

On my Debian based Devuan system there's a meta package tde-trinity which seems to install everything.

Hi Stefan,

That (well on Ubuntu) seems to be a meta for the base desktop and language pack? Nor will it install. :( (info pasted below)

I can do a 'apt search tde' to find out what's installed and not installed, but that includes all the development files and debugging symbols (and slave?) packages. (But not reliably, as it's not showing that I have Kate, kate-trinity, already installed.)

Hmm, after looking at the whole apt search list, probably this isn't such an 'interesting idea' anyway, as yeah having thinks like klaptopdaemon-trinity mass installed is definitely not desired on a desktop.

And after looking at all the apps on https://www.trinitydesktop.org/applications.php , the concept gets even more shot in the foot. :( Having KLatin, even if I never use it installed, is no big deal, but some of those kinda seem like deamons that might get auto-run?

Change my question....

Anyone know of a simple way to see a list of all the TDE 'high' level

apps/packages? * And the output can be then be used to install from?

I rarely use Synaptic, but I guessing(hoping) this can be done in Synaptic? (Cause yeah, I don't want to manually filter though the 300-600 TDE packages)

* I'd say from the Applications page, but after looking at apt search, that list looks very incomplete? I see screensaver and artwork packages in apt show, but neither on the Applications page.

*shrug* Maybe again I'm asking for something that doesn't exist, which reminds me I'll pre-post the Zim stuff I've got in a few minutes.

Best, Michael

root@local [~]# apt install tde-trinity Reading package lists... Done Building dependency tree Reading state information... Done Package tde-trinity is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source

E: Package 'tde-trinity' has no installation candidate

michael@local [~]# apt-cache showpkg tde-trinity Package: tde-trinity Versions:

Reverse Depends: tde-i18n-zhtw-trinity,tde-trinity tde-i18n-zhcn-trinity,tde-trinity tde-i18n-wa-trinity,tde-trinity tde-i18n-vi-trinity,tde-trinity tde-i18n-uzcyrillic-trinity,tde-trinity tde-i18n-uz-trinity,tde-trinity tde-i18n-uk-trinity,tde-trinity tde-i18n-tr-trinity,tde-trinity tde-i18n-th-trinity,tde-trinity tde-i18n-tg-trinity,tde-trinity tde-i18n-te-trinity,tde-trinity tde-i18n-ta-trinity,tde-trinity tde-i18n-sv-trinity,tde-trinity tde-i18n-srlatin-trinity,tde-trinity tde-i18n-ss-trinity,tde-trinity tde-i18n-sr-trinity,tde-trinity tde-i18n-sl-trinity,tde-trinity tde-i18n-sk-trinity,tde-trinity tde-i18n-se-trinity,tde-trinity tde-i18n-rw-trinity,tde-trinity tde-i18n-ru-trinity,tde-trinity tde-i18n-ro-trinity,tde-trinity tde-i18n-ptbr-trinity,tde-trinity tde-i18n-pt-trinity,tde-trinity tde-i18n-pl-trinity,tde-trinity tde-i18n-pa-trinity,tde-trinity tde-i18n-nn-trinity,tde-trinity tde-i18n-nl-trinity,tde-trinity tde-i18n-nds-trinity,tde-trinity tde-i18n-nb-trinity,tde-trinity tde-i18n-ms-trinity,tde-trinity tde-i18n-mn-trinity,tde-trinity tde-i18n-mk-trinity,tde-trinity tde-i18n-lv-trinity,tde-trinity tde-i18n-lt-trinity,tde-trinity tde-i18n-ko-trinity,tde-trinity tde-i18n-km-trinity,tde-trinity tde-i18n-kk-trinity,tde-trinity tde-i18n-ja-trinity,tde-trinity tde-i18n-it-trinity,tde-trinity tde-i18n-is-trinity,tde-trinity tde-i18n-hu-trinity,tde-trinity tde-i18n-hr-trinity,tde-trinity tde-i18n-hi-trinity,tde-trinity tde-i18n-he-trinity,tde-trinity tde-i18n-gl-trinity,tde-trinity tde-i18n-ga-trinity,tde-trinity tde-i18n-fy-trinity,tde-trinity tde-i18n-fr-trinity,tde-trinity tde-i18n-fi-trinity,tde-trinity tde-i18n-fa-trinity,tde-trinity tde-i18n-eu-trinity,tde-trinity tde-i18n-et-trinity,tde-trinity tde-i18n-es-trinity,tde-trinity tde-i18n-eo-trinity,tde-trinity tde-i18n-engb-trinity,tde-trinity tde-i18n-el-trinity,tde-trinity tde-i18n-de-trinity,tde-trinity tde-i18n-da-trinity,tde-trinity tde-i18n-cy-trinity,tde-trinity tde-i18n-csb-trinity,tde-trinity tde-i18n-cs-trinity,tde-trinity tde-i18n-ca-trinity,tde-trinity tde-i18n-bs-trinity,tde-trinity tde-i18n-br-trinity,tde-trinity tde-i18n-bn-trinity,tde-trinity tde-i18n-bg-trinity,tde-trinity tde-i18n-be-trinity,tde-trinity tde-i18n-az-trinity,tde-trinity tde-i18n-ar-trinity,tde-trinity tde-i18n-af-trinity,tde-trinity desktop-base-trinity,tde-trinity Dependencies: Provides: Reverse Provides:

On 02/06/2019 08:36 AM, Michael wrote:

E: Package 'tde-trinity' has no installation candidate

In Debian, tde-trinity installs not quite everything, but way more than most people will ever use. tdebase-trinity is probably a better starting point for most users.

But if I recall correctly, Ubuntu is different. If you search for 'trinity metapackage' you'll find your options. It may be best to search using Synaptic so you can easily see the complete descriptions.

On Wednesday 06 February 2019 07:17:22 pm Michele Calgaro via trinity-users wrote:

On 2019/02/07 01:36 AM, Michael wrote:

...

And after looking at all the apps on https://www.trinitydesktop.org/applications.php , the concept gets even more shot in the foot. :( Having KLatin, even if I never use it installed, is no big deal, but some of those kinda seem like deamons that might get auto-run?

That page may need to be updated, but at least here (https://git.trinitydesktop.org/cgit/) you will be able to have a quick list of the modules currently in TDE sources.

Thank you Michele!,

As John said, specific packages names are going to change per distribution, but that's the full agnostic list. And even in a format that's easily yank'ed, hack'ed, and slash'ed.

I'll dig through it myself, but is it safe to say all the 'user' type apps/packages live in the two sections "[--- tde ---]" and "applications?" I do see stuff like kshutdown in applications, so modifying the above with, "after filtering out system type apps?"

Thanks again! Michael

PS: The Search on the main page doesn't work well? Or, most likely, I just don't know how to use it. I was trying to find KLatin and then the specific file that contains the "Description:" text from "apt show tdeedu-trinity."

All of these return 'No repositories found' KLatin klatin educational apps from the official Trinity release

I don't really care about latin, but is there an easy pattern to find the Description texts?

Dan Youngquist wrote:

On 02/07/2019 08:24 AM, Michael wrote:

...

I don't really care about latin, but is there an easy pattern to find the Description texts?

apt-cache show <pkgname> will show the long description.

Ah great, I see now it shows also the package

Filename: pool/main/t/tdeedu-trinity/klatin-trinity_14.1.0-0debian9.0.5+3eko_amd64.deb

But I am not sure why it is so. is the debian package repository manager creating pool/main/t/tdeedu-trinity/

I was actually expecting to see it in pool/main/k/klatin-trinity_14.1.0-0debian9.0.5+3eko_amd64.deb

Cool, I wish I knew how the package manager knows to put it in tdeedu-trinity

regards

Michael wrote:

Hi I hope no one is offended, because I try to answer.

I'll dig through it myself, but is it safe to say all the 'user' type apps/packages live in the two sections "[--- tde ---]" and "applications?"  I do see stuff like kshutdown in applications, so modifying the above with, "after filtering out system type apps?"

I think it is safe to make this assumption, however look below with klatin - there is explanation

Thanks again! Michael

PS:  The Search on the main page doesn't work well?  Or, most likely, I just don't know how to use it.  I was trying to find KLatin and then the specific file that contains the "Description:" text from "apt show tdeedu-trinity."

All of these return 'No repositories found' KLatin klatin educational apps from the official Trinity release

The thing is that many applications are provided by the repositories in tde - for example klatin is in tdeedu and kmail, knotes etc. is in tdepim. I think the search is finding only names of repositories and not what apps those repositories provide (or packages).

So yes the apps are in tde and applications, but those in tde are not explicit. There is one repository to provide many apps/packages.

This was hard to understand in the beginning, but it makes sense. I now have a copy of tde-packaging and do something like

$ grep klatin-trinity -r ../tde-packaging/debian/stretch/ | grep Package ../tde-packaging/debian/stretch/tdeedu/debian/control:Package: klatin-trinity

and there you have it

regards

On Wednesday 06 February 2019 07:17:22 pm Michele Calgaro via trinity-users wrote:

On 2019/02/07 01:36 AM, Michael wrote:

...

And after looking at all the apps on https://www.trinitydesktop.org/applications.php

That page may need to be updated, but at least here (https://git.trinitydesktop.org/cgit/) you will be able to have a quick list of the modules currently in TDE sources.

tl;dr > I have the app names. Where do I get the descriptions off the git website? (And apt/yum/etc. package names if available.)

Okay, a bit of background is in order I guess. I’ve just built a new box, lots of ram, lots of disk, so initially I just wanted to install all of the TDE user apps just to try them out.

After Michele pointed out a way to see the names of all the apps, I remembered a conversation from several months back that it was suggested someone [could/should] add a wiki page so the updating of TDE app information could be off-loaded from the devs.

Since I now had all the app names, if I could also get the descriptions from git.trinitydesktop.org/cgit , or similar, then I could write a script that would build that wiki page. If there is also a programmatic way to get the apt/yum/etc. package names I can also add that to the script so that information is also available for new users.

Hence the request for the the specific file (or file pattern) within git.trinitydesktop.org/cgit that contains the "Description:" text that is displayed by, for example, "apt show tdeedu-trinity".

Apologies for the confusion my original rambling caused.

Thanks, Michael

On Monday 18 February 2019 10:23:08 am gregory guy wrote:

Michael wrote:

...

On Wednesday 06 February 2019 07:17:22 pm Michele Calgaro via trinity-users

wrote:

...

On 2019/02/07 01:36 AM, Michael wrote:

...

And after looking at all the apps on https://www.trinitydesktop.org/applications.php

That page may need to be updated, but at least here (https://git.trinitydesktop.org/cgit/) you will be able to have a quick list of the modules currently in TDE sources.

tl;dr > I have the app names. Where do I get the descriptions off the git website? (And apt/yum/etc. package names if available.)

Okay, a bit of background is in order I guess. I’ve just built a new box, lots of ram, lots of disk, so initially I just wanted to install all of the TDE user apps just to try them out.

After Michele pointed out a way to see the names of all the apps, I remembered a conversation from several months back that it was suggested someone [could/should] add a wiki page so the updating of TDE app information could be off-loaded from the devs.

Since I now had all the app names, if I could also get the descriptions from git.trinitydesktop.org/cgit , or similar, then I could write a script that would build that wiki page. If there is also a programmatic way to get the apt/yum/etc. package names I can also add that to the script so that information is also available for new users.

Hence the request for the the specific file (or file pattern) within git.trinitydesktop.org/cgit that contains the "Description:" text that is displayed by, for example, "apt show tdeedu-trinity".

Apologies for the confusion my original rambling caused.

Thanks, 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

I don't use Debian/Ubuntu but I believe that the description of the package is written in the "control" file and there's also a description field in the "spec" file for RPM packages.

Have you had a look on the packaging repository in git?

https://mirror.git.trinitydesktop.org/gitea/TDE/tde-packaging

Hi gregory,

Yeah!!! No, I was looking in the wrong place :(

Yup the Debian "control" file has everything needed, including the Debian package name.

I looked at the Red Hat .spec file and all I’d want from it would be the package name. I’m not sure what language it’s in, but am I parsing it right to get the RH package name? Using abakus for example, from these 2 lines in the .spec file (Link for example*):

%define tde_pkg abakus Name: trinity-%{tde_pkg}

Package name is "trinity-abakus"

and,

yum install trinity-abakus

would be the correct command to install the abakus package?

# # #

Last questions (hopefully ;)

- Do all the Debian derivatives (stretch, jessie, ...) use the same package names? - Do all the Ubuntu(s) have the same package names as Debian? - Are there any builds besides Debian and Red Hat that package names should be listed for?

I don’t mind pulling anything that is useful, but I’d rather not have to dig through all the builds (arch, ark, ..., ubuntus) if I don’t need to.

Thanks again, Michael

*Link for example: https://mirror.git.trinitydesktop.org/gitea/TDE/tde-packaging/src/branch/mas...

%define tde_pkg abakus Name: trinity-%{tde_pkg}

Package name is "trinity-abakus"

and,

yum install trinity-abakus

would be the correct command to install the abakus package?

Yes, both are correct. FYI, it is possible to define macros(*) in terms of other macros, something like this:

%define tde_a a %define tde_pkg %{a}b%{a}kus Name: trinity-%tde_pkg

Still giving package name "trinity-abakus"

So, ideally, resolving definitions should be recursive.

The curly braces are only necessary if there's other text immediately following (similar to the rules for $name vs ${name} in bash shell scripting).

This is the most compact link I could find for RPM syntax: https://rpm-packaging-guide.github.io/#what-is-a-spec-file

_____ (*) In proper RPM terminology, what we humans would think of as a "variable" is considered a really simple "macro" definition. Any substitutable thing is called a "macro", even a simple string substitution like the two defined in the example.

Douglas