libunity-webapps0 Depends on unity-webapps-service instead of Recommends - move gsettings schemas to a unity-webapps-common

Bug #1265628 reported by dobey on 2014-01-02
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
WebApps: Applications Data
Undecided
Unassigned
WebApps: libunity-webapps
Medium
Alexandre Abreu
libunity-webapps (Ubuntu)
Undecided
Unassigned
webapps-applications (Ubuntu)
Undecided
Unassigned

Bug Description

The libunity-webapps0 package is declaring a hard Depends on unity-webapps-service, though the latter is not actually required by the library. For someone who does not need or want any webapps, it is feasible that they would want to uninstall this service, and not have it waste CPU and memory.

A reasonable solution would be to move the necessary pieces of that package (the crashdb conf file for apport, and the gsettings schemas) to a unity-webapps-common package which the library can hard Depends on, and have unity-webapps-service be a Recommends instead.

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in libunity-webapps (Ubuntu):
status: New → Confirmed
Mantas Kriaučiūnas (mantas) wrote :

unity-webapps-common package is from different source - webapps-applications, so, I've markeed webapps-applications project as affected by this bug.

Btw, currently unity-webapps-common depends on unity-webapps-service, I think there also should be Recommends instead (when gsettings schema files will be moved to a unity-webapps-common package).
Should I report another bug about this?

Rodney Dawes wrote on 2014-01-02:
> A reasonable solution would be to move the necessary pieces of that package
> (the crashdb conf file for apport, and the gsettings schemas) to a unity-webapps-common package

summary: libunity-webapps0 Depends on unity-webapps-service instead of Recommends
+ - move gsettings schemas to a unity-webapps-common

unity-webapps-service & libunity-webapps0 are not really used as of now so they should be removed and refactored in the case of libunity-webapps along with the associated dependencies.

The libunity-webapps code that might still be somewhat relevant (for some kind of backward compatiblity) is the gsettings related one.

Changed in webapps-applications (Ubuntu):
status: New → Confirmed
Changed in libunity-webapps:
status: New → Confirmed
assignee: nobody → Alexandre Abreu (abreu-alexandre)
importance: Undecided → Medium

One thing that should be done regarding libunity-webapps is to assess if even the gsettings part is required (being used by unity-chromium-extension),

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers