Bug 489667
| Summary: | Too much dependencies to install. | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | alex <m_dorset> |
| Component: | gstreamer-plugins-good | Assignee: | Adam Jackson <ajax> |
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | rawhide | CC: | ajax, rdieter, vmayatsk |
| Target Milestone: | --- | Keywords: | FutureFeature |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Enhancement | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2009-05-08 17:57:23 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
alex
2009-03-11 10:00:21 UTC
One way to avoid PolicyKit-kde (and associated kde dependencies) is to pre-install PolicyKit-gnome, and try installing gstreamer-* again. Which features would you like removed from the gstreamer plugins to reduce their dependency list? I don't very familiar with gstreamer. Let's assume, I use some light-weight window manager, I have no gnome/kde. Should I really install gnome/kde dependencies? Is where any way to avoid it? By the way. It's no only my opinion, but packages in Fedora is going more and more complex way with increasing deps :-( As second example (It's no about gstreamer), which I remember right now - rpm -qR gettext-devel | grep gcj libgcj_bc.so.1()(64bit) see comment #1. Some apps in fedora are starting to include Requires: PolicyKit-authentication-agent The item in this transaction triggering that was gnome-mount. 2 packages currently Provides: PolicyKit-authentication-agent they are: PolicyKit-gnome PolicyKit-kde If you don't have either currently installed, yum tries to pick one for you (to your benefit or dismay). I try to make some analogy probably not the best. Let's make a little overview of dovecot package from fedora: [root@fedora-dev /]# yum search dovecot | grep '^d' | cut -d: -f1 dovecot.i386 dovecot-devel.i386 dovecot-gssapi.i386 dovecot-ldap.i386 dovecot-managesieve.i386 dovecot-mysql.i386 dovecot-pgsql.i386 dovecot-sieve.i386 dovecot-sqlite.i386 I don't have to install all these packages: mysql/pgsql/sqlite/ldap. If I need some of them, it would be installed as deps for appropriate dovecot-* package. Where is no way doing something like that in this case? I think we're talking past each other. that's ok, I'll try to make it clearer. You're mostly concerned about the kde-related dependencies getting pulled in? Yes or no? If so, yum install PolicyKit-gnome yum install gstreamer-plugins-good will get you what you want. If you want each item in gstreamer-plugins-good that contains new/extra dependencies to be split into separate packaging, that's something altogether different. I can agree with reporter. I'm using Fedora day to day starting from Core 2 and dependencies problem gets worse and worse. We have too much complex all-in-one packages. Nowadays its impossible to have simple Fedora installation without half of gnome, kde and java stuff. For example, Fedora 9 and 10 (I'm not sure about rawhide) requires tomcat server for OpenOffice due to weird dependency in some package, which does not relate to OO.org directly. It's madness to require tomcat for usual desktop installation! Try to do `rpm -qa | less' and to see how many packages you don't really need. Ever need. I think packages complexity reduction can be a major feature for next Fedora releases. No only about kde. I have understood trick with yum, thank you. Should I install at least 'kde or gnome deps'? Can I avoid all of them? Thanks also to Vitaly Mayatskikh for his comment. Yeah, I want to see less complex system. Less complex? Three's a tradeoff you know. You're tradeing deps for more packages is all. Instead of a single gstreamer-plugins-good, now you'll have umpteen gstreamer-plugin-foo* subpkgs. Vitaly, you're welcome to help implement the idea... otherwise, it's simply more work for the existing already overworked pkg maintainers. My english not strong to understand meaning of 'Three's a tradeoff'. But I certainly understand whole point, what bug reports in "the best of" should contain some proposed patch. In the next time reporting I will try to make some appropriate spec(s) or so on. It's all about free time, yes. From what I gather, I'll mark this as a wishlist item requesting more extensive pkg splits (FutureFeature keyword), and leave it to the maintainer(s) in question to decide what to do with it. As for me, I'd like to see tens of thousands of separate packages instead of one fedora-blob.rpm ;) And it will be my pleasure to help with solving of dependencies complexity problem. However, it will require not only splitting one big package to several of smaller size, but also introduce a new policy of packages installation, like it does, for example, in Debian. They have 3 possibilities of deps solving: "minimal", "base", "recommended" (I don't remember exactly). And the system installed with minimal deps is really minimal, only 200-300 megs on disk. Thanks for understanding, Rex! We currently have no plans to split gstreamer-plugins-good apart. The PolicyKit integration does require a PK auth agent, and yum happens to pick the KDE one for whatever reason, but that's not gstreamer's fault. |