Am Montag, 9. August 2010, 19:17:24 schrieb Andrew: > 09.08.2010 19:40, KP Kirchdoerfer пишет: > > SOHO applications and routers don't bother me. > > A possible solution is to enhance ipv6 where possible (we do it today > > with ipv6 enabled packages like dnsmasq) and where itwon't raise pb's if > > no ipv6 is available: For example a merged shorewall package with > > shorewall and shorewall6 is no pb without having ipv6 , cause you can > > disable shorewall6 in shorewall6.config (which is the default setting > > anyway). Similar moddb and moddb6 can be merged, its just about having > > the modules in one lrp, one can decide about modules to load in > > modules.conf - a usual task. > > I guess ip6tables will not cause harm on ipv4-only system, at least it > > was installed on my desktop without asking me if I do have ipv6 :) > > > > Looking through the package directory in buildenv, these are the three > > packages I have in mind. > > > > kp > > For therse packages, that will not cause any troubles when IPv6 is > disabled, it's possible to include IPv6 functionality into base > packages. But IMHO it'll be good to make global IPv6 flag somewhere in > config files - this will make future IPv4/IPv6 package merging easier > for end users.
Sorry; I don't the idea, where a global flag can be useful. Maybe you can explain it more? I'm afraid that such a flag raises the users expectation that WE take care of enabling ipv6 whereever possible like module loading, enabling shorewall6, or other strange ideas.... kp ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
