Why is yum not liked by some?

[lesmikesell at gmail.com (Les Mikesell)]

On Thu, 2005-09-08 at 11:09, William Hooper wrote:
> [snip]
> > I think that might be a reasonable starting point. But it doesn't solve
> > the problem of attempting updates as a repository is being modified. You
> > have to work around that even if you do your own snapshot copies.
> 
> If you run the repo, you can control it so machines aren't trying to
> update during the (very short time) that you are running createrepo.
> 
> If you don't run your own repo, then all bets are off.  Of course, if you
> don't run your own repo, how are you going to be sure the older version of
> any give package is there when you want to install it?

Does anyone delete released packages from repositories?  Regardless,
they have to come from somewhere.  How do you know that the 'somewhere'
that you use isn't inconsistent at the time you take your copy of
the contents?  Is there a test to make sure that all possible
dependencies can be resolved within a repository - and is that enough
to know that the snapshot you took is actually what the OS developers
intended to be used together?  I'm looking for something like a
tag that can be applied to a CVS repository that would be applied by
someone who knows the state is consistent and can be used by anyone
else to retrieve exactly that state regardless of ongoing changes.

-- 
  Les Mikesell
    lesmikesell@xxxxxxxxx