Re: Packages should not Conflict on the basis of duplicate funct

1999-09-29 Thread Sean 'Shaleh' Perry
> > e) Let update-inetd handle this. This might not be enough for standalone > servers like apache and roxen but it would work with a pop3 server - > update-inetd -add should notice that there is already a valid entry enable > with that service and add the new entry with a hash mark. > Not enoug

Re: Packages should not Conflict on the basis of duplicate funct

1999-09-29 Thread Torsten Landschoff
On Tue, Sep 28, 1999 at 02:29:55PM -0400, Clint Adams wrote: > > Ok, let's bring this back to implementation. How would you propose we > > handle > > this? Currently daemons install, set themselves up, and begin running. > > > > a) we can prompt. > > b) we leave everything off and let the admin

Re: Packages should not Conflict on the basis of duplicate funct

1999-09-29 Thread John Lines
> > Ok, let's bring this back to implementation. How would you propose we > > handle > > this? Currently daemons install, set themselves up, and begin running. > d) have something that keeps track of installed services, perhaps with >priorities akin to alternatives. If there weren't an iss

Re: Packages should not Conflict on the basis of duplicate funct

1999-09-29 Thread Joey Hess
Seth R Arnold wrote: > The install program will scan the list of installed programs, and for each > package that Provides: service, it will offer a choice of which to configure > by default. FWIW, debconf will soon be able to do this, though it cannot yet. -- see shy jo

Re: Packages should not Conflict on the basis of duplicate funct

1999-09-28 Thread Seth R Arnold
On Tue, Sep 28, 1999 at 11:13:53AM -0700, Sean 'Shaleh' Perry wrote: > Ok, let's bring this back to implementation. How would you propose we handle > this? Currently daemons install, set themselves up, and begin running. > > a) we can prompt. > b) we leave everything off and let the admin turn i

Re: Packages should not Conflict on the basis of duplicate funct

1999-09-28 Thread Bjoern Brill
On Tue, 28 Sep 1999, Clint Adams wrote: > > Ok, let's bring this back to implementation. How would you propose we > > handle > > this? Currently daemons install, set themselves up, and begin running. > > > > a) we can prompt. > > b) we leave everything off and let the admin turn it on (not an

Re: Packages should not Conflict on the basis of duplicate funct

1999-09-28 Thread Clint Adams
> Ok, let's bring this back to implementation. How would you propose we handle > this? Currently daemons install, set themselves up, and begin running. > > a) we can prompt. > b) we leave everything off and let the admin turn it on (not an option for > obvious reasons) > c) first come first serv

Re: Packages should not Conflict on the basis of duplicate funct

1999-09-28 Thread Sean 'Shaleh' Perry
Ok, let's bring this back to implementation. How would you propose we handle this? Currently daemons install, set themselves up, and begin running. a) we can prompt. b) we leave everything off and let the admin turn it on (not an option for obvious reasons) c) first come first serve -- first dae

Re: Packages should not Conflict on the basis of duplicate funct

1999-09-28 Thread Clint Adams
> Because as everyone knows the last 10% takes 90% of the work and often ends up > hurting the other 90%. Then it's being done wrong. > The point is Debian needs to work for as many people as possible. We are > doing Yes, that's exactly the point. > apt-get source qpopper [...] > dpkg -i qpop

Re: Packages should not Conflict on the basis of duplicate funct

1999-09-28 Thread Sean 'Shaleh' Perry
On 27-Sep-99 Clint Adams wrote: >> a) I would not test a new daemon on a working machine, I would use a >> separate > > So? > >> b) if you know what you are doing, compile the packages by hand, fix their >> install scripts, and remove the conflicts. You are trying to circumvent the >> norm. >

Re: Packages should not Conflict on the basis of duplicate funct

1999-09-28 Thread Chris Rutter
On Mon, 27 Sep 1999, Sean 'Shaleh' Perry wrote: > b) if you know what you are doing, compile the packages by hand, fix their > install scripts, and remove the conflicts. You are trying to circumvent the > norm. But I think, to be fair, that what he's proposing *isn't* necessarily `not the norm'

Re: Packages should not Conflict on the basis of duplicate funct

1999-09-27 Thread Franklin Belew
On Mon, Sep 27, 1999 at 04:44:10PM -0400, Clint Adams wrote: > > a) I would not test a new daemon on a working machine, I would use a > > separate > > So? > > > b) if you know what you are doing, compile the packages by hand, fix their > > install scripts, and remove the conflicts. You are tryi

Re: Packages should not Conflict on the basis of duplicate funct

1999-09-27 Thread Clint Adams
> a) I would not test a new daemon on a working machine, I would use a separate So? > b) if you know what you are doing, compile the packages by hand, fix their > install scripts, and remove the conflicts. You are trying to circumvent the > norm. If I wanted to compile them by hand, why would I

Re: Packages should not Conflict on the basis of duplicate funct

1999-09-27 Thread Sean 'Shaleh' Perry
> > So what you're telling me is that anyone with a "complex" setup > shouldn't bother using Debian? > a) I would not test a new daemon on a working machine, I would use a separate one. In the case of gnu pop3, it will spin off and consume 99% of your cpu due to poor child management. We (I am