On Thursday 26 of December 2019 22:39:00 E. Liddell wrote: > I'm trying to fix some Gentoo packaging stuff, since Fat-Zer hasn't > touched his overlay in nearly a year and only ever provided live ebuilds > (= packages that install directly from git main branch, not from > released versions). There are a bunch of details in the packaging > apparatus that haven't been changed in a long time, and I'm pretty sure > that some of those details are incorrect. > I am very glad that you are interested in Gentoo builds! Some time ago, Chris and I on IRC have been addressing that Fat-Zer's overlay is not very well maintained, and that it would be good to set up an official one. For this reason, a new tde-packaging-gentoo repository was created, which contains a copy of the current Fat-Zer's repository. https://mirror.git.trinitydesktop.org/gitea/TDE/tde-packaging-gentoo The repository currently contains only the master branch, the r14.0.x branch has not been created yet. I don't know how Gentoo overlay works - whether it's possible to use branches. I don't even know if your plans are directed only to the latest master branch or whether you want to maintain a stable releases - currently r14.0.x branch. It's up to you. Chris has some plans, you have some plans, it would be good if you can work together to make sure there is a well maintained official Trinity Gentoo overlay. That would be great. > Specific questions: > > Permitted licenses for tqt are still listed in the ebuild as "QPL-1.0 > GPL-2 GPL-3", unchanged from qt3. Am I correct in remembering that QPL > (Trolltech's proprietary license) is no longer valid for tqt? > That is a good question. I also think that only GPL remains valid for TQt. > What is the actual version number of tqt? Of tqtinterface? > Historically, these followed a different version scheme from the main > desktop, but that seems to have changed. Currently, I'm dealing with the > version numbers, certain directory and file names, and a Gentoo SLOT > (mechanism for tracking multiple versions of the same package installed > in parallel) inconsistently, and I would like to clean things up. > Here are two numbers - the git repository versions and packages follow the TDE version numbering as a whole. However, the internal version number of the library is now 3.5.0. For deb packages, the package version is now 14.0.7, where the so library version inside the package is 3.5.0. > What, exactly, are msg2qm and qembed? The ebuild I inherited for tqt > builds them separately, with comments reading "# Make the > msg2qm[/qembed] utility (not made by default)", and furthermore the > build mechanism is currently broken. I need to know whether or not > fixing it is worth the effort. Are these utilities used for building > and/or running anything? > msg2tqm (tqembed) is a tool for converting data, such as images, into C++ code that can be embedded as part of a binary. Unfortunately, I do not remember whether / where this tool is actually used. However, for deb packages it is also built as part of TQt. > More to come as I work my way through the tree, if I don't just give up > and crawl away into a corner somewhere the way I did the last two times > I tried this. > It will be great if you can join your efforts with Chris and possibly other contributors. TGW is a great tool where you can discuss planned patches using issues and pull-requests. It could help you not give up and don't want to hide in a corner :) > E. Liddell > Cheers -- Slávek
Attachment:
signature.asc
Description: This is a digitally signed message part.
