Re: Bug#154142: etherconf only depends on dhcp-client
On Wed, Jul 24, 2002 at 09:01:26AM -0400, Simon Law wrote: Package: etherconf Version: 1.12 Severity: Normal etherconf depends on only dhcp-client, which conflicts with dhcp3-client. This is sad, because only dhcp3-client will work on my system. I suggest the following: Depends: debconf, ifupdown (= 0.6.4), dhcp-client | dhcp3-client, libconfhelper-perl Is this acceptable, or is there some deep down dependency on dhcp-client 2.x? IMO dhcp-client should be a virtual package Provided by dhcp3-client, udhcpc, and pump. -- Branden Robinson | GPG signed/encrypted mail welcome [EMAIL PROTECTED] | 1024D/9C0BCBFB Consultant| D5F6 D4C9 E25B 3D37 068C Progeny Linux Systems | 72E8 0F42 191A 9C0B CBFB -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#154142: etherconf only depends on dhcp-client
On Wed, Jul 24, 2002 at 10:06:34AM -0500, Branden Robinson wrote: On Wed, Jul 24, 2002 at 09:01:26AM -0400, Simon Law wrote: Package: etherconf Version: 1.12 Severity: Normal etherconf depends on only dhcp-client, which conflicts with dhcp3-client. This is sad, because only dhcp3-client will work on my system. I suggest the following: Depends: debconf, ifupdown (= 0.6.4), dhcp-client | dhcp3-client, libconfhelper-perl Is this acceptable, or is there some deep down dependency on dhcp-client 2.x? IMO dhcp-client should be a virtual package Provided by dhcp3-client, udhcpc, and pump. I also concur. Does that mean that dhcp-client becomes dhcp2-client? Does this not have far reaching effects? Perhaps Progeny can kludge the etherconf package while I talk to DHCP maintainers? Is this an acceptable compromise? Simon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#154142: etherconf only depends on dhcp-client
On Wed, Jul 24, 2002 at 11:36:58AM -0400, Simon Law wrote: On Wed, Jul 24, 2002 at 10:06:34AM -0500, Branden Robinson wrote: IMO dhcp-client should be a virtual package Provided by dhcp3-client, udhcpc, and pump. I also concur. Does that mean that dhcp-client becomes dhcp2-client? No. It just means that it would become a mixed virtual package instead of a pure virtual package, in APT's terminology. Does this not have far reaching effects? It would, if it were necessary. Perhaps Progeny can kludge the etherconf package while I talk to DHCP maintainers? Is this an acceptable compromise? Well, let's see first if there is any disagreement. Adding Provides: to 3 packages should not, in theory, be controversial. -- Branden Robinson | GPG signed/encrypted mail welcome [EMAIL PROTECTED] | 1024D/9C0BCBFB Consultant| D5F6 D4C9 E25B 3D37 068C Progeny Linux Systems | 72E8 0F42 191A 9C0B CBFB -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
