Waldemar Brodkorb dixit:
>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.
The situation is similarily crazy with busybox modules, e.g.
busybox ash vs mksh vs bash, busybox ed vs ed, busybox vi vs vim.
So even if we have some kind of flavour ending (say, like
busybox-1.x-1 vs busybox-1.x-1-no_ash) we need proper dependency
tracking (maybe something like Provides: /bin/sh, which would
then be added to busybox-1.x-1 and mksh-200xxxxx-1-as_binsh,
although in _this_ case we could make a symlink after extracting
as well). We could split busybox into smaller modules, so that
we won't have a big executable /bin/busybox, but a smaller
/bin/busybox, a libbusybox.so.x.y, and things like ash, vi, ed,
ping6, in short, everything that would be split off because it
can be a choice, are small executables linked against libbusy-
box.so, if that's possible. But this would make maintaining it
a very hard job. And what do we do for other packages?
>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.
It's very complicated. When adding flavour extensions to pak-
kages, we'd basically need dependency tracking within WIB, or
rather, embed it statically into the database. (This would mean
that not only options like FWRT_PACKAGE_MKSH but also flavour
options like FWRT_PACKAGE_MKSH_AS_BINSH would have to be within
the info.nfo files.)
I admit I don't see a feasible solution _yet_.
//mirabile
--
"Using Lynx is like wearing a really good pair of shades: cuts out
the glare and harmful UV (ultra-vanity), and you feel so-o-o COOL."
-- Henry Nelson, March 1999
_______________________________________________
freewrt-developers mailing list
[email protected]
https://www.freewrt.org/lists/listinfo/freewrt-developers
