Description of problem:
PK cannot be fully uninstalled due to dependency
PK cannot be disabled easily
So PK is not modular enough and not user friendly enough
Version-Release number of selected component (if applicable):
# rpm -e PackageKit-0.7.5-1.fc17.x86_64 PackageKit-glib-0.7.5-1.fc17.x86_64 PackageKit-yum-0.7.5-1.fc17.x86_64
error: Failed dependencies:
libpackagekit-glib2.so.14()(64bit) is needed by (installed) gnome-settings-daemon-3.4.2-4.fc17.x86_64
Fedora components/packages should be modular: easy to install and uninstall without unnecessary dependencies
Fedora components/packages should have an ON/OFF switch
(In reply to comment #0)
> Description of problem:
> PK cannot be fully uninstalled due to dependency
You can't uninstall upower, colord, systemd, etc.
> PK cannot be disabled easily
Why do you want to do that?
> So PK is not modular enough and not user friendly enough
I don't share your working for those conclusions, sorry.
PK is not in the upower, colord, systemd.
upower is optional and should be separate. Your CPU migth not even be suported!
systemd is obvious, despite the bugs, most of the biggest have been fixed, it was not yet ripe for release. Hard to circumvent though.
colord I do not even use and it balks about two identical webcams. Not good, needs to go.
PK I do not need as I know how to run yum manually from time to time.
I am the user.
I am not asking something impossible.
Just a tiny feature:
PK needs a CLEAR ON/OFF switch.
PK needs to be uninstallable.
Those are very basic functionalities which should be in every package/component.
I even want to pay for this basic stuff. (!!)
You can get 90% of disabling PK, by simply configuring your gui client, gpk-prefs or apper (kde), to never check for updates.
Or uninstall said gui frontend (gnome-packagekit and/or apper), and you'll never be bothered by it either.
The maintainers of this component have carefully considered your request to make PK fully removable, and deemed it not practical to implement.
It's fine if you disagree, but re-opening this bug again is not a constructive way forward. If you wish to pursue further discussion, I'd recommend other avenues,
probably the fedora devel mailing list would be most appropriate.
90% is not 100%.
'Not practical to implement' so...
The set of features is totally reasonable and even practical towards the user.
Who designed stuff this way so that it was not practical to implement such a carefully decided upon basic set of features?
Do they disagree on my carefully decided basic set of features?
Or do they agree but do they uphold the opinion that it is to much work in this specific case?
Who are 'they'?
I do not disagree. My case here is the goal that all packages should strive for.
That is the truth. You'll have a hard time explaining otherwise.
The project is not flexible enough for my wishes so if a developer does not understand or even has the nerve to say he thinks so then it is his issue unleashed upon the users.
See the housekeeping process which shows numerous bugs that are not solved or even not responded to within the time of two Fedora releases.
Please FIX the issues.
(In reply to comment #4)
> Who designed stuff this way so that it was not practical to implement such a
> carefully decided upon basic set of features?
> Do they disagree on my carefully decided basic set of features?
> Or do they agree but do they uphold the opinion that it is to much work in
> this specific case?
> Who are 'they'?
> I do not disagree. My case here is the goal that all packages should strive
> That is the truth. You'll have a hard time explaining otherwise.
Sure, the truth is that you can't remove systemd, colord, PackageKit or upower from a general purpose operating system. Sorry, that's just the reality we live in.
> The project is not flexible enough for my wishes so if a developer does not
> understand or even has the nerve to say he thinks so then it is his issue
> unleashed upon the users.
Sure, it's my issue.
> See the housekeeping process which shows numerous bugs that are not solved
> or even not responded to within the time of two Fedora releases.
Right, I do a lot of the PackageKit in my own time. I have limited free time as I have a new baby. Any help writing code and fixing bugs is very welcome.
PLEASE rethink what you are doing and who you are doing that for.
Please consider THEIR perspective.
PLEASE FIX the stuff I mentioned.
The 'reality' that we cannot remove certain stuff cannot be used as an argument, it merely explains how BAD the situation is w.r.t. modularity.
PLEASE FIX the stuff I mentioned.
See comment #3 if you want further dialog.
bugzilla is *not* the place for a discussion like this.
I am not discussing. You are not understanding well enough.
You don't even say 'I see your point, but I cannot do that right now..' or similar.
I did say we "have carefully considered your request" in comment #3 . Please do consider that as "I see your point..." as well.
Then I misunderstood that part.
Still, the 'CANTFIX' does not offer any perspective that the two basic issues I mentioned will ever be fixed.
So no future date, or some conditional explanation or whatever.
WONTFIX/CANTFIX means to the feature you requested as-is, will (most likely) not ever get implemented. Developers in feature requests (and bugzilla) have no responsibility to justify their judgements to your satisfaction. They know the code and implementations fairly well, hopefully, and deserve some level of trust to know what they are talking about.
That said, I have now suggested on 3 separate occasions that if you don't accept that resolution, you can take up further discussion in other more appropriate venues (like fedora -devel list).
This will likely be my last comment here on this bug, unless any new information (that hasn't already been mentioned) comes to light.
(In reply to comment #10)
> Then I misunderstood that part.
> Still, the 'CANTFIX' does not offer any perspective that the two basic
> issues I mentioned will ever be fixed.
> So no future date, or some conditional explanation or whatever.
You can remove PackageKit in F-18+ without issue, you can do the same in F-19 too.