Bug 401965 - Missing subdirectories of kde-dev-scripts-18.04.3-1.fc29
Summary: Missing subdirectories of kde-dev-scripts-18.04.3-1.fc29
Status: RESOLVED INTENTIONAL
Alias: None
Product: kdesdk-scripts
Classification: Developer tools
Component: Miscellaneous (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Michael Pyne
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-12-10 15:53 UTC by Matt Fagnani
Modified: 2023-01-19 06:35 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Matt Fagnani 2018-12-10 15:53:59 UTC
SUMMARY

kde-dev-scripts-18.04.3-1.fc29 on Fedora 29 appears to be missing various subdirectories with programs such as gdb, kf5, frameworks, kde-emacs, qt4 which are in the kde-dev-scripts-18.04.3 git tree at 
https://cgit.kde.org/kde-dev-scripts.git/tree/?h=Applications%2F18.04

Those subdirectories aren't shown by sudo dnf repoquery -l kde-dev-scripts 
or at https://koji.fedoraproject.org/koji/rpminfo?rpmID=14654888


STEPS TO REPRODUCE
1. sudo dnf repoquery -l kde-dev-scripts
2. check https://koji.fedoraproject.org/koji/rpminfo?rpmID=14654888
3. check subdirectories in git tree at https://cgit.kde.org/kde-dev-scripts.git/tree/?h=Applications%2F18.04

OBSERVED RESULT

kde-dev-scripts-18.04.3-1.fc29 is missing various subdirectories with programs.

EXPECTED RESULT

kde-dev-scripts-18.04.3-1.fc29 contains the subdirectories above

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora 29
(available in About System)
KDE Plasma Version: 5.14.4
KDE Frameworks Version: 5.52.0
Qt Version: 5.11.1

ADDITIONAL INFORMATION

Rex Dieter wrote the following at the entry I made for Fedora at https://bugzilla.redhat.com/show_bug.cgi?id=1657575

"Good question for upstream.  As you can see from,
https://cgit.kde.org/kde-dev-scripts.git/tree/CMakeLists.txt?h=Applications/18.04

Those extra items you mention are indeed not installed by default (I assume that is on purpose)"

The question is if the directories above were intentionally omitted from the CMakeLists.txt install parts or not. I assigned this to kdesdk-scripts because it was the closest component I could find to kde-dev-scripts.
Comment 1 Michael Pyne 2018-12-11 04:22:14 UTC
This is indeed at least partially intentional. I won't promise that there's not been oversights from developers adding scripts to forget to also update the CMakeLists.txt so that it gets installed.

But for things like gdb/, there's special added work that needs to be done each time and the result varies by Qt's .so version so it's not appropriate for install. qt4/ is old, kde-emacs/ doesn't hold scripts appropriate for bin/, and frameworks/ was more of the one-time work to assemble KF5 than useful things to install.

kf5/ looks like it has a lot of goodness in there which could be installed though, and probably replace the ancient cvs and svn support scripts that we *do* install.

Are there specific scripts you're wanting to be installed? I'm not sure it makes sense to just dump the full git repo contents into a given install dir, except maybe for adding kf5/*.
Comment 2 Matt Fagnani 2018-12-11 05:00:56 UTC
(In reply to Michael Pyne from comment #1)
> This is indeed at least partially intentional. I won't promise that there's
> not been oversights from developers adding scripts to forget to also update
> the CMakeLists.txt so that it gets installed.
> 
> But for things like gdb/, there's special added work that needs to be done
> each time and the result varies by Qt's .so version so it's not appropriate
> for install. qt4/ is old, kde-emacs/ doesn't hold scripts appropriate for
> bin/, and frameworks/ was more of the one-time work to assemble KF5 than
> useful things to install.
> 
> kf5/ looks like it has a lot of goodness in there which could be installed
> though, and probably replace the ancient cvs and svn support scripts that we
> *do* install.
> 
> Are there specific scripts you're wanting to be installed? I'm not sure it
> makes sense to just dump the full git repo contents into a given install
> dir, except maybe for adding kf5/*.

I was looking to use the scripts in the gdb directory to print out the values of Qt objects like QStrings in gdb. I've been troubleshooting ksysguard crashes when it's been shutting down due to segmentation faults which I found were resulting from use-after-free errors as I described in bug 400499  

I ran git clone https://anongit.kde.org/kde-dev-scripts.git 
In gdb, I ran source /programs/kde-dev-scripts/gdb/load-qt5printers.py
The values of QString variables were printed correctly after that.
That workaround did what I was looking to do. 

Some of the directories might be added to packages but not others I take it then. Perhaps Rex or the other maintainers could add the kf5 and possibly other directories if they wish. I just found the kde-dev-scripts package yesterday and installed it, so I wasn't sure what was normally in the package or not. Thanks for your explanation which clarified what the various directories and programs contain and how up to date they are for me.
Comment 3 Justin Zobel 2023-01-19 00:19:09 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 4 Matt Fagnani 2023-01-19 06:35:20 UTC
(In reply to Justin Zobel from comment #3)
> Thank you for reporting this issue in KDE software. As it has been a while
> since this issue was reported, can we please ask you to see if you can
> reproduce the issue with a recent software version?
> 
> If you can reproduce the issue, please change the status to "REPORTED" when
> replying. Thank you!

kde-dev-scripts-22.12.1-1.fc37.noarch doesn't appear to contain the programs in directories such as gdb, kf5, frameworks, kde-emacs at https://invent.kde.org/sdk/kde-dev-scripts/-/tree/master/kde-emacs That seemed to be intentional at least in part given Michael's comment 1, so I'm setting the status to resolved - intentional.