On Fri, Jul 27, 2012 at 03:18:44AM +0200, Luka Perkov wrote:
I'll fix it.
Fixed in r32897. As suggested on IRC I changed package name.
Luka
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
To whoever reworked my ISC-DHCP package into regular old DHCP:
You left in the CONFIG_DHCP4_ENABLE_IPV6 checks without actually putting it as
an option in the menu, so right now, all builds will have IPv6 support
disabled.
Please either add the option back to menuconfig for enabling/disabling
On 26/07/12 15:14, Oliver wrote:
To whoever reworked my ISC-DHCP package into regular old DHCP:
You left in the CONFIG_DHCP4_ENABLE_IPV6 checks without actually putting it
as
an option in the menu, so right now, all builds will have IPv6 support
disabled.
Please either add the option
On 26/07/12 15:53, Oliver wrote:
On Thursday 26 July 2012 15:32:22 John Crispin wrote:
Hi Oliver,
i think making a build_variant for ip4 and ip6 is a better solution than
creating a menuconfig option.
Really, I think it's sufficient to just check CONFIG_IPV6 - separating the
two
builds
On Thursday 26 July 2012 15:57:14 John Crispin wrote:
Really, I think it's insufficient to just check CONFIG_IPV6. i want a
build without and one with ipv6 version with the latter being depended
on CONFIG_IPV6. Doing what you propose means a ipkg is generated that
can have 1 of 2 binaries
On 26/07/12 16:04, Oliver wrote:
On Thursday 26 July 2012 15:57:14 John Crispin wrote:
Really, I think it's insufficient to just check CONFIG_IPV6. i want a
build without and one with ipv6 version with the latter being depended
on CONFIG_IPV6. Doing what you propose means a ipkg is generated
On Thursday 26 July 2012 16:07:15 John Crispin wrote:
i am talking about a version with and without ipv6. Or to make it easy
to understand, IPV4 and dual stack.
Which is exactly how I originally had it - it sat in its own section as
dhcp4 and there was a checkable option to enable IPv6
The point is: We want to tell, from the package name, what's inside an
ipkg archive.
This is not possible with so-called 'conditional dependencies', which
influence the
build, taking other config options into account.
Vice versa that means: We want to avoid having one and the same package
(as in
On Thursday 26 July 2012 16:54:57 Mirko Vogt wrote:
The point is: We want to tell, from the package name, what's inside an
ipkg archive.
This is not possible with so-called 'conditional dependencies', which
influence the
build, taking other config options into account.
Vice versa that means:
On Friday 27 July 2012 01:09:43 Mirko Vogt wrote:
On 07/27/2012 12:24 AM, Oliver wrote:
As it stands, it is *impossible* to build any of the dhcp tools with IPv6
support due to this bug, so something should be done in the interim.
You might have a valid point, however your attitude to
On Fri, Jul 27, 2012 at 02:59:41AM +0200, Oliver wrote:
On Friday 27 July 2012 01:09:43 Mirko Vogt wrote:
On 07/27/2012 12:24 AM, Oliver wrote:
As it stands, it is *impossible* to build any of the dhcp tools with IPv6
support due to this bug, so something should be done in the interim.
On Friday 27 July 2012 03:18:44 Luka Perkov wrote:
You were not in MAINTAINER macro.
That is true; to be a real maintainer I would argue that it's necessary to
have commit access - I have inquired about it in the past but nothing was
forthcoming, if I had the ability to commit to the repo, I
12 matches
Mail list logo
