Hi,
the mentioned PR included a few new packages. I don't know the layerscape
platform, so I just want to understand it: these packages are all
necessary to
boot a "reasonable"
system? And this is true for fmc, too?
[Y.b. Lu] fmc is an important userspace tool for layerscape which is
frequently used and required by our key customers.
my point is more whether it is absolutely not possible to boot up
a layerscape system without these tools/packages?
Or to bring a somewhat constructed use-case: PHP7 is frequently used
and required by most of my customers - however, this does not justify
to move PHP7 to core openwrt.
Don't get me wrong, I'm not a core developer and this are just
a few thoughts...
Michael
Fmc build and usage depends on several packages. They are tclap,
fmlib, and eth-config which I added in the PR. Both fmlib and
eth-config are only for layerscape.
Then one option would be to move libxml2 to "core openwrt".
If not, it would be an alternative approach to move the not really important
packages to packages feed, and add the fmc package in the packages feed as
well. This way, the dependency to libxml2 is solved automatically and the
"core openwrt" stays as small as reasonable.
Or should we avoid packages in the package feed which have a strong
platform dependency?
[Y.b. Lu] Thanks a lot for your good suggestion. Actually I tend to
move libxml2 to core openwrt.
_______________________________________________
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
