Re: chromaprint: fpcalc missing

2018-04-03 Thread Pierre Neidhardt
Ludovic Courtès writes: > The best way to know that is by sending a patch. ;-) > > A common criterion in deciding whether or not to enable an optional > feature is how widely used it is vs. how much it adds to the size of the > package closure. If you can provide that kind of info in your patc

Re: chromaprint: fpcalc missing

2018-04-03 Thread Ludovic Courtès
Hello, Pierre Neidhardt skribis: > Catonano writes: > >> which package are you talking about ? >> >> Anyway, you can submit a patch ☺ > > The chromaprint package. > > I'll submit a patch but I wanted to ask, maybe the original author of > the recipe has an opinion about it. The best way to kno

Re: chromaprint: fpcalc missing

2018-04-03 Thread Pierre Neidhardt
Catonano writes: > which package are you talking about ? > > Anyway, you can submit a patch ☺ The chromaprint package. I'll submit a patch but I wanted to ask, maybe the original author of the recipe has an opinion about it. -- Pierre Neidhardt signature.asc Description: PGP signature

Re: chromaprint: fpcalc missing

2018-04-03 Thread Catonano
2018-04-03 8:24 GMT+02:00 Pierre Neidhardt : > > The chromaprint commandline tool "fpcalc" to compute fingerprints is > missing. > > I believe passing the CMAKE argument > > -DBUILD_TOOLS=ON > > would be enough. > > I guess it would be a nice fit for a separate output. > > -- > Pierre Neid

chromaprint: fpcalc missing

2018-04-02 Thread Pierre Neidhardt
The chromaprint commandline tool "fpcalc" to compute fingerprints is missing. I believe passing the CMAKE argument -DBUILD_TOOLS=ON would be enough. I guess it would be a nice fit for a separate output. -- Pierre Neidhardt signature.asc Description: PGP signature