The problem of "Requires.private", for C/C++ libraries, it (might)
contain two different things: Libraries used for static linking *and*
Cflags to preprocess the header files.
If the position of Debian is that each reference in "Requires.private"
translates into a required dependency in
Many projects out there support not just a single crypto library like OpenSSL
but others like GnuTLS and NSS as well. While building the project, a switch
must be enabled or changed. Some projects even default not to OpenSSL. I saw
Curl, which supports all three via six different packages,
Recently, I stumbled over a change in Doxygen [1][2][3] which broke the online
documentation of a project, I had to use. The fix is easy. However, realizing
the issue is not easy (no error, warning, just subtle glitches in the docs).
Long story short, I grepped all -dev packages and their
Thank you so much. Both helped. For another project, I am going for the -dev
package content. For this issue here, the source turned out to be much easier.
The result is a bit astonishing. I have not checked for false positives yet.
But the initial search gave 650 affected source packages. I
> upstream .. issue
Paolo, thanks for watching. Doxygen works as expected.
In the past, it accepted group commands without being in a "special comment
section". Since version 1.8.16, Doxygen requires a "special
comment section". Again, as designed, Doxygen does not see those group
commands
> mass-bug-filing against the ones that FTBFS
Thanks for the idea. Fails To Build From Source. Although not tested, I
guess, not one (-doc) package will fail to build. Doxygen simply ignores
group commands in standard comments by now. Doxygen requires everything
to be in a Special Comment
> you will not get rid of either crypto stack
Thanks for everyone's comments. Sorry for the confusion introduced. I
like one package each with a different crypto-library backend. Then, it
is about user's choice rather than getting rid of something.
My (observed) problem: Many projects
Linux distributions, which have separate packages for developers, like
Debian, are not really supported [1] by the developer tool pkg-config
[2]. The problems are C/C++ libraries which depend on other libraries at
runtime. Let us pick one, a security library for utilizing DNSSEC:
$ sudo apt
> If foo.pc in libfoo-dev references bar.pc [...]
That is the problem: If 'bar.pc' is referenced just because for static
libraries, why does it create a dependency for me as a user, who is
a) not using pkg-config at all
and/or
b) linking dynamically?
Let us assume 'bar.pc' creates a
9 matches
Mail list logo
