Johannes Winkelmann [2008-06-18 10:24]:
On Wed, Jun 18, 2008 at 09:07:27 +0200, Victor Martinez wrote:
On Wed, 18 Jun 2008 08:15:37 +0200 Johannes Winkelmann <jw@smts.ch> wrote:
[snip]
2. Dependency handling ---------------------- [...] In this way, you remove the diy though by default. I mean, you make things automated instead of let the user keep track of ports/packages. Yes, the default behaviour is changing. I'm not sure how many users resolve dependencies by hand, that's one reason for this RFC.
I typically use 'install' myself, but I have to admit I don't know why. And if I don't want t dependency, I typically use --ignore= along with depinst. In this case, I could just as well use 'lock' to make it clear.
I'd really like to hear how others handle this. Do you normally use install and track dependencies by hand? Do you often ignore dependencies as specified by the maintainer? Should "depinst/install -D" be optional, for example for large transaction like gnome?
I paid attention to how I am using prt-get over the last few days. I seem to often use deptree on a package I'm about to install, to check that it doesn't pull in weird stuff that I don't like (yes, I'm silly). Afterwards I run prt-get install or prt-get depinst. I like what I've read here so far, though, and I think defaulting to depinst behaviour should be okay; I would just have to remember locking packages that I don't want :) Regards, Tilman -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail?