On 05/24/2015 03:11 PM, robert.devanna@nospammail.net wrote:
If you are not going to accept any answer anyway, why ask? I would trust experience of people who have been using openSUSE for a long time.
Seriously what are you talking about?
Sloppy is sloppy. Doesn't matter to me one bit 'who' someone is.
I'm perfectly open to accepting thoughtful, verifiable answers that are self-consistent. That's why I'm asking.
As for looking at code, that's exactly what I'm doing. Because I apparently have to to get an answer that's pulled out of someone's hat.
I agree with you about "sloppy" but looking at the Ruby code won't help you. The issue is the parameters that code works with which are in the packages. The only way you're going to deal with this is, as I said earlier, forget about yast altogether. Its a constraint that expects things to work in a set way and part of that set way is a dependency tree that it expects is met. Now that's going to be fine for setting up dhcp services as I outlined, but if you want to install Shorewall you're going to have to over-ride yast's expectation about "2". The other approach, which I'm more inclined to take, is to ignore yast altogether. There are many applications I have (I put iem in /opt, which I have as a separate file system so it can survive upgrades) that I install without using yast/zypper. The advantage of have repository reference for an application and the reference in the RPM database is that you can do a 'zypper up' to update it. If you can live without that, or if the application itself notifies you or has a service that notifies you when an update is available then that's good. Perhaps you're happy with the revision you have; perhaps you track bugs/updates by some other method. I can understand yast for newbies, though some seem to expect it to do things without their RTFM or without their willingness to explore its options, especially as an installer and especially when it comes to disk space provisioning, but that's another matter. Yes, like most guis, is a crutch, often a very useful crutch that's easier than doing things 'manually'. But all GUIs embody the GUI designer's concept of what you ought to do, channel what you can do to his model. I can't recall, for example, the last time (except for installation) that I used yast to set up a repository or install a package. The closets was using the web to find the repository (well, ok, in FTP mode) and paste the URL into a zypper command line in a sudo in a kterminal. OK, so in the 85% case yast is doing the same as zypper, but in that extra 15% I want the control I get with zypper or with 'rpm' that I can't do with yast or which would be tedious and awkward with yast. For example, I can extract things from the database using ' rpm', format, filter, produce a list and run a shell loop feeding them to zypper. Yes, i have, Yes it's a "one liner". You might try using zypper or yast to black-list Susefirewall2 and see what happens. Hmm. Its one of the things I have black-listed, along with many language packages, sendmail, exim, kde3 and a variety of 32-bit packages. :-) -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org