17 Dec
2020
17 Dec
'20
1:12 a.m.
On Friday 02 of October 2020 17:37:02 Michael via tde-users wrote:
On Thursday 01 October 2020 06:37:00 pm Slávek Banko
via tde-users wrote:
Hi Michael,
I seem to have a fairly successful procedure. During the preparation of the
PHP routing script for creating new issues in TGW, I needed to get a table
that would contain all the binaries (including games and KCM modules) and
information about the git repository to which it belongs.
I have used Contents files that are accessible in the apt repository to
find all the files that are of interest. From this I found information
about the corresponding deb package name. And by searching in
the "control" files in the git repository tde-packaging, I found the
corresponding git repository for each binary (each application).
It seems to me that this table, or more precisely the procedure for
obtaining it, could be useful for automating the retrieval of information
and creating the initial look of wiki pages for applications. In that
procedure, finding descriptions from the corresponding deb package could
be added, which could serve as a basis for descriptions on the wiki pages.
At the same time, information about the git repository will be useful for
users to search for and create issues for applications.
What do you think about that?
Note: Thank you Leslie for your suggestion.
Cheers
--
Slávek
It can be seen that using package information as
a basis for
application wiki pages could help improve this information :)
However, it is important to think not only about how different the
granularity of packages can be in individual distributions, but also
that not every program has a separate package. For example, kwrite is
included in package kate-trinity (deb packaging).
Well crap.
Is there any automated way to get a list of all the programs?
# # #
Just installing everything and looking in /opt/trinity/bin/ doesn't seem
to work either? I see a bunch of slaves, launchers, helpers and such...
____________________________________________________