Hi,
On Sun, 11 Feb 2007 at 1:52 +0100, Dirk Nehring wrote:
> On Sat, Feb 10, 2007 at 12:50:44AM +0100, Waldemar Brodkorb wrote:
> > Hi,
> > On Thu, 08 Feb 2007 at 18:46 +0100, Christian Gmeiner wrote:
> > > >Why?
> > > >* why no check à la
> > > > ifeq (${FWRT_PACKAGE_KMOD_IPV6},)
> > > > so that 'y' _and_ 'm' work
> > > Okay, will change it
> > >
> > > >* why disable this at all, userland works fine with it?
> > > Maybe the package will be bigger with ipv6 support?
> > >
> > > >
> > > >We probably really need some FWRT_CONFIG_IPV6 option.
> > > >Should I add that to menuconfig?
> > >
> > > Maybe this is a good idea, but the opinion of wbx is important.
> >
> > I like to have build flavours. It is just very important to always
> > have the ability to make bulk snapshot and release build with all
> > packages and flavours included. So if you add something like
> > FWRT_CONFIG_IPV6, be sure it can be automatically build.
>
> Hi Waldemar,
>
> what do you mean with "automatically build"? I thought of the following
> idea: if anyone disabled "FWRT_CONFIG_IPV6", all configure calls gets
> and additional "--disable-ipv6" option to it. These packages will not
> work in an IPV6 enviroment if there is special IPV6 code in it (to save
> space). Will this concept break webbuilder?
Yes. Because then we cannot distinguish between ipv6 enabled and
disabled packages. If you --enable-ipv6 option you also need to
create a package with foobar_ipv6 .. but then we still need to
automatically build all packages twice one time with ipv6 enabled,
and one time without.
For 1.1 I need a clean solution for creating a release. Just one
script should do the work without any kind of interaction. Right now
I have three ugly scripts and the need some kind of interaction,
that is bad.
So if we add any kind of flavour to packages, we need a solution
which works for release builds and for WIB.
I am open for ideas and patches how to solve our problems.
have fun
Waldemar
--
don't open your wrt, free it
http://www.freewrt.org
_______________________________________________
freewrt-developers mailing list
[email protected]
https://www.freewrt.org/lists/listinfo/freewrt-developers
