[kde-windows] [Bug 363467] New: Portage fails to construct runtime dependencies for packages under kde/applications

[Jasem Mutlaq via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=363467

            Bug ID: 363467
           Summary: Portage fails to construct runtime dependencies for
                    packages under kde/applications
           Product: kde-windows
           Version: unspecified
          Platform: MS Windows
                OS: MS Windows
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: buildsystem
          Assignee: kde-windows at kde.org
          Reporter: mutlaqja at ikarustech.com

While trying to use 'emerge --package kstars', the emerge process never finds
the required runtime dependencies for KStars and install them as needed to the
archive directory.

After a bit of investigation, the problem turns out to be getDependencies(
category, package, runtimeOnly = False ): function in portage.py.

For applications that fall under portage/kde/applications/*, the function
returns the subpackage as "applications" but that fails when it tries to call 
_getSubinfo("kde", "applications) as it cannot find the applications.py file
since it doesn't exist.

Attached is a small patch that fixes this problem. However, a bigger issue is
that tree layout itself. There are many applications (kdevelop, ktorrent, k3b)
that fall under portage's "extragear" while others fall under
"kde/applications". What's the reason for this? It seems inconsistent.

Reproducible: Always

Steps to Reproduce:
1. emerge --package kstars
2. 
3.

Actual Results:  
no runtime dependencies installed

Expected Results:  
runtime dependencies installed

-- 
You are receiving this mail because:
You are the assignee for the bug.