[packagekit] Exposing apt/yum's build-dep feature in packagekit?
Dan Kegel
dank at kegel.com
Thu Apr 9 10:59:28 PDT 2009
On Thu, Apr 9, 2009 at 10:56 AM, Sebastian Heinlein <glatzor at ubuntu.com> wrote:
>> Hey, it's Richard's use case, and he thought it was important
>> enough to introduce a whole new feature, package catalogs.
>> Think he should remove that feature?
>
> In the case of catalogs the build deps would be stored in the catalog
> file and not in the repository data AFAIK. That is a big difference.
Why? In either case, the developer is getting the build deps
needed to start hacking on the app, isn't she?
>> Perhaps he simply has developers more firmly in mind as users than you do?
>
> You are talking about package maintainers or developer of upstream projects?
>
> The native get build-dep feature is perhaps mostly used by package maintainers
> and as a starting point for people who want to compile something not yet
> available - but would have to install additional dependencies.
build-dep is also used by plain old developers who just want to
start hacking. That's the way a lot of wine developers get the
needed dependencies.
- Dan
More information about the PackageKit
mailing list