Does your provides database include every file provided by every
package?
so that if you encounter:
Requires: /some/path/to/a/file
it can resolve it?
if there is another package that has "/some/path/to/a/file" in it`s Provides i can resolve it. otherwise i can`t. (yet)
also how are you doing your versioned-dep calculation? Are you calling
out to rpm for the rpm version comparisons?
that`s not that hard at all.
i just have a table with the package id, package provides/requires and the version of the requires/provides though this can use some tweaking.
how are you checking to see if the package foo-1.3-1 provides that
dependency or not?
to put it simple:
SELECT * FROM PROVIDES WHERE provide_id = '##' AND provide_name = 'foo-1.3-1';
(simple sample.. it`s not the query that i actually use.. that`s alot longer :P)
2007/4/9, seth vidal <skvidal@xxxxxxxxxxxxxx
>:
On Mon, 2007-04-09 at 23:19 +0200, Mark wrote:
> i don`t really understand what you mean..
> i actually check only all the requires of a package to the provides of
> the packages that are in the database.
> but the files-as-dep.. i don`t understand that.
>
Does your provides database include every file provided by every
package?
so that if you encounter:
Requires: /some/path/to/a/file
it can resolve it?
also how are you doing your versioned-dep calculation? Are you calling
out to rpm for the rpm version comparisons?
so if a pkg requires:
foo > 1:1.2
how are you checking to see if the package foo-1.3-1 provides that
dependency or not?
-sv
--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list
-- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
