[packagekit] Semantic issues with GetDeps (and other interface functions)

[Patryk Zawadzki]

On 8/31/07, Tom Parker <palfrey at tevp.net> wrote:
> Summary: Giving a simple package_id-specified list of dependencies is
> non-trivial (plus other interface semantic issues)
>
> Got a problem while thinking about how to build GetDeps. For .deb's, we
> can have many "dependancies". Some are "Depends", but then we've got

Same for rpm:

> * "Pre-Depends" - like Depends, but IIRC is more of a hint to the setup
> bits to do the *whole* process for Pre-Depends packages before starting
> to install this package.

"Requires(pre)"

> * "Suggests" - "You probably want this package"

"Suggests"

> * "Recommends" - "Adding this package will help"

"Enhances"

> * "Conflicts" - "Won't work with that package"

"Conflicts"

> * "Replaces" - "Both can be installed at the same time, but only if you
> do this one this second and it'll override some stuff that the other one
> would normally do"

"Obsoletes"

> (Some of that might be a bit off, need to re-read the Debian Packaging
> Policy document, but you get the idea)

...and "Provides" "Requires" etc.

-- 
Patryk Zawadzki
Generated Content