On Thu, Aug 07, 2003 at 05:23:05AM +0200, Axel Thimm wrote:
> What is yum's behaviour ("upgrade") in this case? Would it toggle the
> packages at each yum upgrade? Can such obsolete-loops be detected and
> the installed package preferred?
On Fri, Aug 08, 2003 at 11:37:26AM -0400, seth vidal wrote:
> > The policy I outlined above is to prefer whichever package is already
> > installed.
> >
> > Maybe yum could remove obsoleted packages in its upgrade computation?
> > That way if neither foo nor bar are installed, they won't get in with
> > a yum upgrade, and if on is installed, it will not start toggling.
>
>
> Think where that takes you.
>
> For example: a few years back openssh-server obsoleted sshd.
>
> By your description openssh-server wouldn't get in.
Only if sshd would have also obsoleted openssh-server. The case we are
talking about is more like zebra vs gated.
The idea is that whenever you have multiple possible solutions
(obsolete loops, conflicts and virtual packages provided by many
rpms), a way to prefer one solution would be to see, what the user has
installed. In the case of sshd vs openssh-servers you never have to
make the choice, because the ("upgrade") solution is unique.
--
Axel.Thimm@xxxxxxxxxxxxxxxxxxx
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.dulug.duke.edu/pipermail/yum/attachments/20030808/8c5f9743/attachment.bin
