Re: why so hard to decline recommend packages dselect/apt

2000-08-21 Thread John L. Fjellstad
On Mon, Aug 21, 2000 at 02:12:17AM +0200, Florian Friesdorf wrote: There are programs, like mutt, that depend on a smtp-mailer-daemon. You installed exim to satisfy this dependency. Now if you prefer using qmail instead of exim, just install qmail, and afaik exim will be automatically

Re: why so hard to decline recommend packages dselect/apt

2000-08-21 Thread Florian Friesdorf
On Mon, Aug 21, 2000 at 02:01:21AM -0700, John L. Fjellstad wrote: Well, the problem was that I wanted to install qmail from the author's pristine sources, so it couldn't really be under dpkg management. Basically, I needed equivs to satisfy the dependencies. What was weird is, you can

Re: why so hard to decline recommend packages dselect/apt

2000-08-20 Thread Eric Gillespie, Jr.
On Sat, Aug 19, 2000 at 04:26:26PM -0800, Ethan Benson [EMAIL PROTECTED] wrote: personally i just use apt-get as much as possible and dselect as little as possible. I agree, but sometimes it's nice to have that full-screen interface. That's why i *love* console-apt. It's so nice i use it for

Re: why so hard to decline recommend packages dselect/apt

2000-08-20 Thread John L. Fjellstad
On Sat, Aug 19, 2000 at 04:26:26PM -0800, Ethan Benson wrote: personally i just use apt-get as much as possible and dselect as little as possible. So, how do you avoid dependencies in apt-get? Or doesn't apt-get install recommended packages? If that's the case, how do you make it install

Re: why so hard to decline recommend packages dselect/apt

2000-08-20 Thread Mark Brown
On Sun, Aug 20, 2000 at 11:07:24AM -0700, John L. Fjellstad wrote: So, how do you avoid dependencies in apt-get? Or doesn't apt-get You don't want to avoid something that is an actual dependancy. install recommended packages? If that's the case, how do you make it install recommended and

Re: why so hard to decline recommend packages dselect/apt

2000-08-20 Thread John L. Fjellstad
On Sun, Aug 20, 2000 at 07:48:10PM +0100, Mark Brown wrote: You don't want to avoid something that is an actual dependancy. Well, take this 'problem' I recently had. I just upgraded from RedHat to Debian. My /home directory was kept, and the rest blown away. Anyways, I ran into a problem with

Re: why so hard to decline recommend packages dselect/apt

2000-08-20 Thread Florian Friesdorf
On Sun, Aug 20, 2000 at 03:40:09PM -0700, John L. Fjellstad wrote: Well, take this 'problem' I recently had. I just upgraded from RedHat to Debian. My /home directory was kept, and the rest blown away. Anyways, I ran into a problem with during the configuration (after installation), and

Re: why so hard to decline recommend packages dselect/apt

2000-08-20 Thread Ethan Benson
On Mon, Aug 21, 2000 at 02:12:17AM +0200, Florian Friesdorf wrote: There are programs, like mutt, that depend on a smtp-mailer-daemon. You installed exim to satisfy this dependency. Now if you prefer using qmail instead of exim, just install qmail, and afaik exim will be automatically

why so hard to decline recommend packages dselect/apt

2000-08-19 Thread Daniel Barclay
Why is it so hard to decline a recommends dependency? In dselect (using the apt method), if I select a package A that recommends a package B, dselect switches to the dependency- resolution screen with package B selected. If I simply deselect B and exit normally (with Return), dselect

Re: why so hard to decline recommend packages dselect/apt

2000-08-19 Thread Ethan Benson
On Sat, Aug 19, 2000 at 02:02:16PM -0400, Daniel Barclay wrote: Why is it so hard to decline a recommends dependency? [snip dselect experience we have all had] AGH! I have declined the recommendation. WHY WON'T DESELECT JUST SHUT THE FUCK UP! Reccommends == Depends as far as dselect is