Hi Helmut, On 02.01.20 20:14, Helmut Grohne wrote: > Yes. I often opt for moving all components to the multiarch libdir. > However in the case of cln, the comment in debian/rules line 70 made me > not go that route: > > # This installs into libdir, but we must not set libdir because it affects > the .la file: > > Maybe I didn't properly understand the comment, but it seemed as if we > shouldn't pass --libdir. If that actually works, it should be preferred. > It might even allow marking some packages Multi-Arch: same.
I, too, was wondering about this comment. Well, since .la files aren't shipped let's ignore this. I think it's safe to Multi-Arch: same libcln6, now. The -dev package, I don't think so: Some headers are configure-generated and arch-dependent. I'ld have to learn how to handle this, first. > This bug is only concerned with the location of the .pc file though. It > can be solved by only moving it or by moving all files. Whatever suits > you best. I chose the minimally invasive route, because I feared > introducing a regression, but as you figured it adds complexity on its > own. Thanks. I'm going to dupload a thoroughly modernized CLN package now. If you could have a look at it, this would be appreciated. -richy. -- Richard B. Kreckel <https://in.terlu.de/~kreckel/>
