Looks like PolicyKit-kde bits are in kdebase-workspace now.
Any thoughts or opinions on whether to roll this into kdebase-workspace proper (with Obsoletes/Provides), or to continue to make it as a separate (sub)package?
I did the former as a first try in kdebase-workspace-4.2.85-1 packaging.
-- Rex
On Sunday 17 May 2009 16:52:46 Rex Dieter wrote:
Looks like PolicyKit-kde bits are in kdebase-workspace now.
Any thoughts or opinions on whether to roll this into kdebase-workspace proper (with Obsoletes/Provides), or to continue to make it as a separate (sub)package?
I did the former as a first try in kdebase-workspace-4.2.85-1 packaging.
Maybe if you can outline the advantages and disadvantages as you see them.
Eli
Eli Wapniarski wrote:
On Sunday 17 May 2009 16:52:46 Rex Dieter wrote:
Looks like PolicyKit-kde bits are in kdebase-workspace now.
Any thoughts or opinions on whether to roll this into kdebase-workspace proper (with Obsoletes/Provides), or to continue to make it as a separate (sub)package?
I did the former as a first try in kdebase-workspace-4.2.85-1 packaging.
Maybe if you can outline the advantages and disadvantages as you see them.
Off the top of my head:
1. included in kdebase-workspace Simpler (all in one place) Only relevant for a kde desktop anyway Avoids the potential confusion of PolicyKit-kde vs PolicyKit-gnome
2. PolKit-kde subpkg Less pkg rename churn more modular packaging (though it would remain Require'd by kdebase-workspace at least)
-- Rex
- included in kdebase-workspace
Simpler (all in one place) Only relevant for a kde desktop anyway Avoids the potential confusion of PolicyKit-kde vs PolicyKit-gnome
- ... (though it would remain Require'd by
kdebase-workspace at least)
Which is required by KDE for a working Desktop? So....
Make your life simple... huh?
One package to rule them all (place evil laugh here) :)
Eli