Bug#308725: ITP: dhcpv6 -- a stateful address autoconfiguration protocol for IPv6
On Wed, May 11, 2005 at 11:37:58PM -0500, Adam M wrote:
On 5/11/05, Hamish Moffatt [EMAIL PROTECTED] wrote:
Err. I guess you are packaging an implementation rather than a protocol
(I'm not sure how you would package a protocol). I think you may need to
improve your description with that in mind.
s/protocol/server/ for example.
Right. Although the package will contain the server, the client and
possibly a relay. Well, probably 2 or 3 binary packages from one
source. But yes, s/protocol/{server,client,relay}/ in the one line
description. This long description should probably only be used for
the server and the client/relay have more terse long descriptions of
what they do, not a description of what DHCPv6 protocol is.
That sounds good. Thanks.
Hamish
--
Hamish Moffatt VK3SB [EMAIL PROTECTED] [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#308725: ITP: dhcpv6 -- a stateful address autoconfiguration protocol for IPv6
[Adam M.] Description : a stateful address autoconfiguration protocol for IPv6 DHCPv6 is a stateful address autoconfiguration protocol for IPv6, a counterpart to IPv6 stateless address autoconfiguration protocol. Please specify whether your package provides a client, a server, or both. If it's only a client, or only a server, you should probably rename the package accordingly (see the DHCPv4-related packages). It wouldn't hurt to mention that the stateless server is the Debian package 'radvd' and doesn't require specific client software other than iproute or whatever. It can either be used independently or it can coexist with its counterpart protocol. This protocol uses client/server mode of operation but can also provide support through a Relay Agent. Is the Relay Agent provided by this package as well, or by a separate Debian package, or does Debian not have one at all? signature.asc Description: Digital signature
Bug#308725: ITP: dhcpv6 -- a stateful address autoconfiguration protocol for IPv6
On Wed, May 11, 2005 at 08:03:34PM -0500, Adam M. wrote: [...] Current upstream does not appear to be very active. I'm not yet certain whether I will make this a Debian package or Upstrea/Debian patch. So maybe it would be good idea to package some more active project named dibbler? Its author wants to package his software for Debian. [...] regards fEnIo -- ,''`. Bartosz Fenski | mailto:[EMAIL PROTECTED] | pgp:0x13fefc40 | irc:fEnIo : :' : 32-050 Skawina - Glowackiego 3/15 - w. malopolskie - Poland `. `' phone:+48602383548 | proud Debian maintainer and user `- http://skawina.eu.org | jid:[EMAIL PROTECTED] | rlu:172001 signature.asc Description: Digital signature
Bug#308725: ITP: dhcpv6 -- a stateful address autoconfiguration protocol for IPv6
On 5/12/05, Peter Samuelson [EMAIL PROTECTED] wrote: [Adam M.] Description : a stateful address autoconfiguration protocol for IPv6 DHCPv6 is a stateful address autoconfiguration protocol for IPv6, a counterpart to IPv6 stateless address autoconfiguration protocol. Please specify whether your package provides a client, a server, or both. If it's only a client, or only a server, you should probably rename the package accordingly (see the DHCPv4-related packages). This was meant as a ITP: source package here One binary will include the client, and another the server It wouldn't hurt to mention that the stateless server is the Debian package 'radvd' and doesn't require specific client software other than iproute or whatever. Yes, radvd is the stateless server and the kernel has the client for auto-self-configuration. It can either be used independently or it can coexist with its counterpart protocol. This protocol uses client/server mode of operation but can also provide support through a Relay Agent. Is the Relay Agent provided by this package as well, or by a separate Debian package, or does Debian not have one at all? I don't think there is one. The sources do have a dhcp6relay.c, but that is not compiled. The relay agent is in the TODO list. I guess the Relay Agent should have been lowercase! - Adam
Bug#308725: ITP: dhcpv6 -- a stateful address autoconfiguration protocol for IPv6
On 5/12/05, Bartosz Fenski aka fEnIo [EMAIL PROTECTED] wrote: On Wed, May 11, 2005 at 08:03:34PM -0500, Adam M. wrote: [...] Current upstream does not appear to be very active. I'm not yet certain whether I will make this a Debian package or Upstrea/Debian patch. So maybe it would be good idea to package some more active project named dibbler? Its author wants to package his software for Debian. Well, I just DL dibbler. The source code is C++, while dhcpv6 is C only. The source code for dibbler is much, much larger than dhcpv6. Dibbler also seems it wants to be a stateless server, like radvd in addition to DHCPv6 server. The last revision of dibbler seems to be in December 2004. The last revision of dhcpv6 is about a year ago. From the sources, Dibbler seems to have a linux, windows 2k and xp ports. dhcpv6 is more for the BSD environment only. I don't know. I really think that maybe it would be best of dibbler AND dhcpv6 were packaged separately. It seems these two packages are complimentary, like Apache and webfs. Also, I do not think dibbler's client could ever be part of base due to its size. The upstream tarball contains the dibbler-client at about 1 meg. - Adam
Bug#308725: ITP: dhcpv6 -- a stateful address autoconfiguration protocol for IPv6
Package: wnpp Severity: wishlist Owner: Adam M. [EMAIL PROTECTED] * Package name: dhcpv6 Version : 0.10 Upstream Author : ?? Not a single one - many... * URL : http://dhcpv6.sourceforge.net/ * License : Mostly BSD, some LGPL and MIT/X Description : a stateful address autoconfiguration protocol for IPv6 DHCPv6 is a stateful address autoconfiguration protocol for IPv6, a counterpart to IPv6 stateless address autoconfiguration protocol. It can either be used independently or it can coexist with its counterpart protocol. This protocol uses client/server mode of operation but can also provide support through a Relay Agent. Current upstream does not appear to be very active. I'm not yet certain whether I will make this a Debian package or Upstrea/Debian patch. This depends on how much of the code can be replaced by current libc functionality. I should get this package done within a month (so by mid-June) since I will be doing some code reviewing and not just packaging. - Adam -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.11-1-k7 Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#308725: ITP: dhcpv6 -- a stateful address autoconfiguration protocol for IPv6
On 5/11/05, Hamish Moffatt [EMAIL PROTECTED] wrote:
On Wed, May 11, 2005 at 08:03:34PM -0500, Adam M. wrote:
* Package name: dhcpv6
Version : 0.10
Upstream Author : ?? Not a single one - many...
* URL : http://dhcpv6.sourceforge.net/
* License : Mostly BSD, some LGPL and MIT/X
Description : a stateful address autoconfiguration protocol for IPv6
DHCPv6 is a stateful address autoconfiguration protocol for IPv6, a
counterpart to IPv6 stateless address autoconfiguration protocol. It
can either be used independently or it can coexist with its
counterpart protocol. This protocol uses client/server mode of
operation but can also provide support through a Relay Agent.
Err. I guess you are packaging an implementation rather than a protocol
(I'm not sure how you would package a protocol). I think you may need to
improve your description with that in mind.
s/protocol/server/ for example.
Right. Although the package will contain the server, the client and
possibly a relay. Well, probably 2 or 3 binary packages from one
source. But yes, s/protocol/{server,client,relay}/ in the one line
description. This long description should probably only be used for
the server and the client/relay have more terse long descriptions of
what they do, not a description of what DHCPv6 protocol is.
- Adam
