[PATCH] regex/cn9k: remove rule compiler

[Stephen Hemminger]

On Mon, 26 Jun 2023 18:43:21 +0200
Thomas Monjalon <thomas at monjalon.net> wrote:

> 26/06/2023 18:22, Stephen Hemminger:
> > On Mon, 26 Jun 2023 09:16:32 +0200
> > Thomas Monjalon <thomas at monjalon.net> wrote:
> >   
> > > 25/06/2023 22:57, Stephen Hemminger:  
> > > > On Wed, 21 Jun 2023 21:03:00 +0530
> > > > Jerin Jacob <jerinjacobk at gmail.com> wrote:
> > > >     
> > > > > On Wed, Jun 21, 2023 at 7:36 PM Thomas Monjalon <thomas at monjalon.net> wrote:    
> > > > > >
> > > > > > Nobody knows how to build the feature.
> > > > > > When the dependency "rxp_compiler" is found,
> > > > > > the header file is not available:
> > > > > >
> > > > > > drivers/regex/cn9k/cn9k_regexdev_compiler.c:12:10: fatal error:
> > > > > >         rxp-compiler.h: No such file or directory
> > > > > >
> > > > > > It seems that it depends on a proprietay library.      
> > > > > 
> > > > > Yes. it depended on proprietary library owned by NVIDIA now. Not sure
> > > > > Marvell has rights to publish it "freely available".
> > > > > In order to avoid forking this library, better option to make this
> > > > > library as public. Also, it looks like the library itself won't have
> > > > > proper installation procedures that is the
> > > > > reason for conflict as documented here in
> > > > > https://bugs.dpdk.org/show_bug.cgi?id=1232.    
> > > > 
> > > > Interesting. Then what about the GPU support which currently requires
> > > > proprietary NVIDIA CUDA library    
> > > 
> > > CUDA can be downloaded.
> > > It is even packaged in many Linux distributions.  
> > 
> > Thanks for the clarification.
> > So the real issue is not that it needs a proprietary library but it is
> > that the library is not available without special license.  
> 
> No you don't get it.
> The problem is that the dependency must be downloadable on Internet.
> CUDA is downloadable.
> The dependency for Marvell regex is not available on Internet.
> 
> > CUDA does require accepting a free license which may be a problem for some people who have
> > lawyers who read the fine print.
> > 
> > The policy about dependencies should be made more explicit in the documentation.  
> 
> It could be detailed in the contributing guide.

The natural place would be under a subsection about new libraries.
This is where the Tech Board approval of new dependencies should go as well.