On Monday, 15 October 2007, at 18:58:45 (-0400),
Jeff Johnson wrote:

>  All depends on the relation between the build <-> install machines.
>  If the build system has content that is sufficiently close to the
>  install system, then the computation of the package that provides a
>  dependency is just a lookup.

Indeed.

>  The lookup is clean, completely dynamic, done automatically, and
>  completely obscure. Will work fine for building in chroot's like
>  PLD, but will have the usual problems of lack of precision using
>  the open-ended versionless
>      Requires: foo

Ick.  This will completely break the moment a major shared library
version changes.  So this really solves nothing at all...it just
shifts the problem from one spot to another spot, and in fact makes
the end result a lot worse.

>  The private reason for adding (with default disabled) is to hand
>  zealots a completely implemented package-only mechanism, rather
>  than discussing the relative worth of soname, file, name space,
>  interpreter, parentdir, linkto etc etc animules in the rpm
>  dependency menagerie.
> 
>  I believe in lobotomies as a cure for stoopidity ;-)

"Here, have some rope.  What's the big loop at the end?  Oh,
nothing really...."

Michael

-- 
Michael Jennings (a.k.a. KainX)  http://www.kainx.org/  <mej@kainx.org>
Linux Server/Cluster Admin, LBL.gov       Author, Eterm (www.eterm.org)
-----------------------------------------------------------------------
 "There are two ways to slide easily through life:  to believe
  everything, or to doubt everything; both ways save us from
  thinking."                       -- Polish Linguist Alfred Korzybski