| 1 |
On Fri, 26 Oct 2001 18:55:44 +0200 (CEST) |
| 2 |
"Tom von Schwerdtner" <tvon@×××××.org> wrote: |
| 3 |
|
| 4 |
> Not if you take Debian conflicts seriously, but you really shouldnt. |
| 5 |
> Debian packages control /etc to a large extent, and it is very hard to |
| 6 |
> have scripts that properly setup /etc files (esp on Debian where you |
| 7 |
> have |
| 8 |
> the 'alternatives' setup) when a system can potentially have multiple |
| 9 |
> apps/servers that do the same abstract job |
| 10 |
> (MTA/DBMS/HTTPD/SSHD...etc..), |
| 11 |
> so Debian takes care of this by saying "OK, you can only have 1 httpd, 1 |
| 12 |
> DBMS, 1 MTA and 1 sshd". This way, the scipts just have to deal with |
| 13 |
> whatever package they are contained in and dont have to deal with the |
| 14 |
> situation where there is already a package installed that does the same |
| 15 |
> abstract job. |
| 16 |
|
| 17 |
I'm sorry, but it's clear you aren't very familiar with Debian. |
| 18 |
Nowhere does it say, either in Policy or in Conflicts, etc... that you |
| 19 |
can't have multiple httpds installed. I currently have boa, thttpd, |
| 20 |
and apache installed an I'm running Debian 'frozen'. It was as simple |
| 21 |
as 'apt-get install boa thttpd apache' |
| 22 |
|
| 23 |
I'm also very confused by what you mean by "scripts" when you say |
| 24 |
"the scripts just have to deal with whatever package they are |
| 25 |
contained in and..." Do you mean init scripts?? Debian's Apache |
| 26 |
properly (IMHO) ships /etc/init.d/apache, not /etc/init.d/httpd. |
| 27 |
Boa ships /etc/init.d/boa and so on. |
| 28 |
Apache, Boa,and others do not conflict, although most "provide" |
| 29 |
httpd. httpd is a "virtual" (meta) package for other packages that |
| 30 |
want to depend on one but don't care specifically which. |
| 31 |
|
| 32 |
> Gentoo leaves /etc to the admin, which is good, so there is no reason |
| 33 |
> why |
| 34 |
> Gentoo should have the same "conflicts" that Debian has. |
| 35 |
|
| 36 |
Again, I think you misunderstand what 'conflicts' are in Debian. |
| 37 |
I have no idea what conflicts has to do with /etc, specifically. |
| 38 |
|
| 39 |
> BTW: I am not some seasoned Debian developer, these views come from |
| 40 |
> using |
| 41 |
> Debian for a while and having to work around the various Debian |
| 42 |
> conflicts |
| 43 |
> that I ran into......yes, Debian conflicts irritate the hell out of me |
| 44 |
> :) |
| 45 |
|
| 46 |
I've been a Debian developer and user for many years now, and |
| 47 |
Debian "conflicts" are, IMHO, extraordinarily useful -- they |
| 48 |
prevent me from accidentally killing other programs when I install. |
| 49 |
|
| 50 |
Perhaps a quick read of: |
| 51 |
http://www.debian.org/doc/debian-policy/ch-relationships.html |
| 52 |
will forestall any more "I heard this so it must be true.". |
| 53 |
|
| 54 |
|
| 55 |
|
| 56 |
|
| 57 |
-- |
| 58 |
Jon Nelson |
| 59 |
jnelson@×××××××.net |
| 60 |
C and Python Programmer |
| 61 |
Motorcycle Enthusiast |
Archives