Hi Clemens, On Mon, May 28, 2007 at 18:46:15 +0200, Clemens Koller wrote:
Hi, Johannes!
Johannes Winkelmann schrieb:
On Mon, May 28, 2007 at 12:27:16 +0200, Clemens Koller wrote: [...]
Maybe it's worth a simple message from prt-get install and prt-get update which dependencies are not satisfied (yet). [...] I've always like the idea, however as mentioned that would have meant a major change in the user interface, which is something which I didn't want to do at that point in time.
I wouldn't care about the UI/look and feel/whatever, as long as it's optional. Well, that was kinda my point. The commands didn't have the same meaning as before, so it couldn't be made optional.
Since it's impossible for prt-get to tell whether a build error was really due to missing dependencies, a message of warning about omitted dependencies will probably be counter productive for educating folks, since it will a) keep them from thinking on their own, and b) leave them frustrated if the tools suggest a solution and the build keeps failing after following it, with the tool staying silent
I don't ask for tools to suggest anything which could be misleading. Well, if the build fails, and you print out that the user is missing dependencies, you are in a way suggesting that this may be the problem, and thus the user will expect that getting rid of this warning will make the problem go away. I'd call that misleading.
I just don't like tools which stay silent and don't tell what they do or don't do. That's the only thing I would welcome here - in prt-get. I don't fully understand you here. How does it not tell you what it does?
Regards, Johannes -- Johannes Winkelmann mailto:jw@smts.ch Zurich, Switzerland http://jw.smts.ch