Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] Native dependencies in CDT ecosystem

Hi Roland,

Answers embedded.

On 11/17/2014 11:32 AM, Roland Grunberg wrote:
I just added to p2 a mechanism that allows IUs to express dependencies
on native packages. This information is used during the installation to
present the user with a dialog indicating which native packages are
required (see attached screenshot) -- p2 does not trigger the
installation automatically.
I think this is some interesting work!

I'm just wondering what your thoughts would be in using something like
PackageKit in querying/installing native dependencies. The advantage
would be that it's present on many Linux distros, and that calling it
would bring up the native authentication dialogs for performing the
actual install.
I had not considered PackageKit simply because I only had as a goal to support ubuntu 12 and 14 LTS and I knew how to deal with that easily. That said, I'm not opposed to see a contribution that uses PackageKit as long as we can get the DBus java library approved through IP and the license is compatible with Eclipse. As for prompting the user, we had decided that this could be too invasive / confusing for the user. Again this is something that could be considered.

One case I've seen is of having some project and upon building, getting
errors about missing system headers/libaries, but not being sure what
package provides those things. In Fedora we tried addressing this with a
plugin to scrape relevant info from logs/console and query the system
with PackageKit (through DBus) for possible solutions.

It would be interesting if there was a way to do this through p2
touchpoints  but it seems like keeping the user profile in sync with
system state would be tricky.
There were discussions similar to those in bug


Back to the top