| Summary: | kio has a runtime dependency on kinit (circular dependency) | ||
|---|---|---|---|
| Product: | [Unmaintained] kio | Reporter: | G360 <kde-bugs.9ek5t> |
| Component: | general | Assignee: | David Faure <faure> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | normal | CC: | nate |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
G360
2016-07-14 01:19:59 UTC
Since it's a *runtime* dependency and not a compile time dependency, it's not a problem. It's typical of any runtime dependency, we had that with kde-runtime for all of the KDE4 time frame, for instance. kde-runtime had a compile-time dependency on kdelibs4, and kdelibs4 had a runtime dependency on kde-runtime (which provided a number of executables used by kdelibs4). So you need kio to compile kinit, and then you install both, and then it all works. I'm not sure what this means in terms of packaging though. Installing either one should install the other as well. I suppose one could say we should merge them then, but having them separated makes it possible to *one day* remove some dependencies. Sounds like this isn't really a problem. |