Re: [LEDE-DEV] Layerscape package depending on libxml2

2018-05-10 Thread Y.b. Lu
Hi Micheal,

> -Original Message-
> From: Michael Heimpold [mailto:m...@heimpold.de]
> Sent: Wednesday, May 9, 2018 6:29 PM
> To: Y.b. Lu <yangbo...@nxp.com>
> Cc: lede-dev@lists.infradead.org; Xiaobo Xie <xiaobo@nxp.com>;
> openwrt-de...@lists.openwrt.org; Hauke Mehrtens <ha...@hauke-m.de>;
> John Crispin <j...@phrozen.org>
> Subject: Re: [LEDE-DEV] Layerscape package depending on libxml2
> 
> 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?

[Y.b. Lu] It's just an user space tool. It isn’t required for booting up.

> 
> 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.

[Y.b. Lu] Understand. Either Core openwrt or feed is ok for me as long as there 
is a place to put it 

> 
> Don't get me wrong, I'm not a core developer and this are just a few
> thoughts...

[Y.b. Lu] Thank you all the same for your help.

> 
> 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


Re: [LEDE-DEV] Layerscape package depending on libxml2

2018-05-09 Thread Michael Heimpold

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


Re: [LEDE-DEV] Layerscape package depending on libxml2

2018-05-09 Thread Y.b. Lu
Hi Michael,

> -Original Message-
> From: Michael Heimpold [mailto:m...@heimpold.de]
> Sent: Wednesday, May 9, 2018 2:41 AM
> To: lede-dev@lists.infradead.org; Xiaobo Xie <xiaobo@nxp.com>
> Cc: Y.b. Lu <yangbo...@nxp.com>; openwrt-de...@lists.openwrt.org; Hauke
> Mehrtens <ha...@hauke-m.de>; John Crispin <j...@phrozen.org>
> Subject: Re: [LEDE-DEV] Layerscape package depending on libxml2
> 
> 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.
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.

> 
> Just a few thoughts of mine,
> Michael
> 
> Am Dienstag, 8. Mai 2018, 08:44:27 CEST schrieb Y.b. Lu:
> > Hi John and Hauke,
> >
> > May I have your suggestion about an old problem? The pull request was
> merged leaving out fmc package.
> > https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit
> >
> hub.com%2Fopenwrt%2Fopenwrt%2Fpull%2F724=02%7C01%7Cyangbo
> .lu%40nx
> >
> p.com%7C5af09f423eb34c8479c508d5b5133b9d%7C686ea1d3bc2b4c6fa92c
> d99c5c3
> >
> 01635%7C0%7C1%7C636614016566713359=N2jlxMw2erh3uIjx1T%2F
> nWfvWZBe
> > Zjsz7ioGMDsbNP%2BE%3D=0
> >
> > I'd like to add this package fmc (frame manager configuration) for
> layerscape.
> > However it depends on libxml2 package which is not in the base feed. Must
> install feeds to enable and build it.
> > So I think I need some suggestion to find out a proper way to add this
> package.
> >
> > Thanks a lot.
> >
> > Best regards,
> > Yangbo Lu
> >
> > ___
> > Lede-dev mailing list
> > Lede-dev@lists.infradead.org
> > https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flist
> >
> s.infradead.org%2Fmailman%2Flistinfo%2Flede-dev=02%7C01%7Cyangb
> o.
> >
> lu%40nxp.com%7C5af09f423eb34c8479c508d5b5133b9d%7C686ea1d3bc2b
> 4c6fa92cd99c5c301635%7C0%7C1%7C636614016566713359=BDODn
> CrzqggSQgIx7%2B3y6zIFRb23T01nVATTSyKI3HU%3D=0
> >
> 


___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev


Re: [LEDE-DEV] Layerscape package depending on libxml2

2018-05-08 Thread Michael Heimpold
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?

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?

Just a few thoughts of mine,
Michael

Am Dienstag, 8. Mai 2018, 08:44:27 CEST schrieb Y.b. Lu:
> Hi John and Hauke,
> 
> May I have your suggestion about an old problem? The pull request was merged 
> leaving out fmc package.
> https://github.com/openwrt/openwrt/pull/724
> 
> I'd like to add this package fmc (frame manager configuration) for 
> layerscape. 
> However it depends on libxml2 package which is not in the base feed. Must 
> install feeds to enable and build it.
> So I think I need some suggestion to find out a proper way to add this 
> package.
> 
> Thanks a lot.
> 
> Best regards,
> Yangbo Lu
> 
> ___
> Lede-dev mailing list
> Lede-dev@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/lede-dev
> 



___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev


[LEDE-DEV] Layerscape package depending on libxml2

2018-05-08 Thread Y.b. Lu
Hi John and Hauke,

May I have your suggestion about an old problem? The pull request was merged 
leaving out fmc package.
https://github.com/openwrt/openwrt/pull/724

I'd like to add this package fmc (frame manager configuration) for layerscape. 
However it depends on libxml2 package which is not in the base feed. Must 
install feeds to enable and build it.
So I think I need some suggestion to find out a proper way to add this package.

Thanks a lot.

Best regards,
Yangbo Lu

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev