Bug 69184 - Make aptcc backend's GSteamer support optional
Summary: Make aptcc backend's GSteamer support optional
Status: RESOLVED NOTABUG
Alias: None
Product: PackageKit
Classification: Unclassified
Component: backend-apt (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Richard Hughes
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-09-10 16:05 UTC by Loïc Minier
Modified: 2018-08-21 15:52 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
Make aptcc backend's GStreamer support optional (5.40 KB, text/plain)
2013-09-10 16:05 UTC, Loïc Minier
Details

Description Loïc Minier 2013-09-10 16:05:06 UTC
Created attachment 85575 [details]
Make aptcc backend's GStreamer support optional

Hi,

Ubuntu currently includes the aptcc PackageKit backend to install APT packages over PackageKit's DBus interface, but Ubuntu doesn't make use of the functionality to resolve GStreamer packages over PackageKit (Ubuntu uses the sessioninstaller GStreamer plugin instead).

So I'd like to avoid the GStreamer dependency of the aptcc PK backend (notably because we're transitioning from GStreamer 0.10 to 1.0).

Attaching a patch to this effect.

Thanks for considering!

NB: tested new configure flag with:
- force disabled, with gstreamer deps available (result: disabled)
- force enabled, with gstreamer deps available (result: enabled)
- force enabled, with gstreamer deps unavailable (result: fails configure)
- default (autodetection), with gstreamer deps available (result: enabled)
- default (autodetection), with gstreamer deps available (result: disabled)
Comment 1 Richard Hughes 2018-08-21 15:52:39 UTC
We moved the upstream bugtracker to GitHub a long time ago. If this issue still affects you please re-create the issue here: https://github.com/hughsie/PackageKit/issues
 
Sorry for the impersonal message, and fingers crossed your issue no longer happens. Thanks.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.