Re: repo agnostic package resolvers (was: Latest apt broken?)

--===============6391564627813149301==
Content-Disposition: inline
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="uZ3hkaAS1mZxFaxD"


--uZ3hkaAS1mZxFaxD
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, Jan 20, 2005 at 08:43:43AM +0800, Jeff Pitman wrote:
> On Thursday 20 January 2005 01:52, seth vidal wrote:
> > And yet it makes the pkg mgmt a nightmare b/c now, instead of being
> > able to key on file name I have to go find the packages the provide
> > that file (or worse yet, if wildcards are involved) then figure out
> > the arch for those involved and match.
>=20
> How do you do "Requires: /usr/sbin/alternatives" ?  I didn't think=20
> wildcards were involved .. can't see an immediate use for that. =20
> Explicit is better than implicit on this one.

I believe Seth is talking about implementing this behaviour in yum
(e.g. how a package resolver is going to traverse all packages to see
which ones provided this file to kick out).

It is in principle similar to the Requires seek, only that there a
package resolver can stop at the first match, which in the case of
Obsoletes/Conflicts it has to check everything.

Also wildcards make little sense for requires, but can be used for
Obsoletes/Conflicts (e.g. kde.spec could contain Obsoletes:
/usr/bin/gnome-* and vice versa ;).

=46rom a packager's POV the more expressive power rpm gets the better :)
--=20
Axel.Thimm at ATrpms.net

--uZ3hkaAS1mZxFaxD
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)

iD8DBQFB7wJTQBVS1GOamfERAvxMAKCHsBQERYv/w+uZoHdpcE9w6/rclwCfcdGM
nKkSspVJdOmaQBlotn3sVT8=
=Hei5
-----END PGP SIGNATURE-----

--uZ3hkaAS1mZxFaxD--


--===============6391564627813149301==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
repo-coord mailing list
[email protected]
http://lists.atrpms.net/mailman/listinfo/repo-coord

--===============6391564627813149301==--