Bug 1281465 - RFE: better name for xfce-polkit
Summary: RFE: better name for xfce-polkit
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: xfce-polkit
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Raphael Groner
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-11-12 15:17 UTC by Ali Akcaagac
Modified: 2015-11-12 16:24 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-11-12 16:24:58 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Ali Akcaagac 2015-11-12 15:17:52 UTC
I would like to make a suggestion.

-bash-4.3$ rpm -qa | grep -i "polkit"
xfce-polkit-0.2-2.fc22.i686
polkit-0.113-4.fc22.i686
polkit-pkla-compat-0.1-5.fc22.i686
polkit-gnome-0.105-7.fc22.i686
polkit-libs-0.113-4.fc22.i686

That is the current output of the packages installed on my system (yes polkit-gnome got removed just after that output).

As you see there seem to be some sort of naming convention (as I would describe it) for postfix'ing all packages with polkit-*

It would be nice to have xfce-polkit renamed to polkit-xfce to fit better into this convention.

This is a backported package build from SRPM for Fedora 22... in case you wonder why there is such a package.

Comment 1 Raphael Groner 2015-11-12 15:24:47 UTC
Sorry, xfce-polkit is the original upstream name. Besides it's another separate upstream and *not* a part of that official polkit upstream. Therefore I do not want to change.
https://fedoraproject.org/wiki/Packaging:NamingGuidelines#General_Naming

Kevin, what do you think about this?

Comment 2 Kevin Fenzi 2015-11-12 16:06:44 UTC
I don't see any need to change the name. 

If you can convince upstream to change we could follow suit, but it seems like a lot of makework. ;)

Comment 3 Raphael Groner 2015-11-12 16:24:58 UTC
Sorry again, but a name change does not make any sense to me.


Note You need to log in before you can comment on or make changes to this bug.