Policy or best practice on mentioning dependency issues

[Arch Willingham]

In my case, I guess I am "crying" (?) for two reasons:
 

1.	With yumex you have to start it, wait for it to come up, pick select, tell it it ok, wait for it to finish, tell it to close.....lost of hand holding. On the other hand, with a yum command line (shell script), you click one command and walk away.
2.	Sometimes, you can't tell which one is the problem with yumex. It bombs out and says there is a problem with x dependency in y package. When you review he list, none of the updatable packages contain anything obvious to clue you in to which package to exclude. I had one happen that way the other night. I had to end up opening yumex, selecting five packages, telling it to apply them. If they ran...great...if not figure out which of those five were causing the problem.

Arch
 

-----Original Message-----
From: fedora-test-list-bounces at redhat.com [mailto:fedora-test-list-bounces at redhat.com]On Behalf Of Dan Carruthers
Sent: Thursday, October 18, 2007 7:11 PM
To: For testers of Fedora Core development releases
Subject: Re: Policy or best practice on mentioning dependency issues


seth vidal wrote: 

On Thu, 2007-10-18 at 17:29 +0300, cornel panceac wrote:

  

hmm, what if instead of exiting, yum would ask: "do you wanna continue

with the broken deps packages excluded?" or similar?

    





what would you want yum to do if you ran it with -y?



-sv











  

I see all these people crying about broken deps packages in yum, so why not run yumex than when you have a broken dep just uncheck that package and go ahead with the install.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/fedora-test-list/attachments/20071018/8d7dcc63/attachment.htm>