Re: Packaging pjproject

[Marius Bakke]

Jan <address@hidden> writes:

> Hello,
> I have hard time trying to fix the pjproject package - something is
> broken in our version of pjproject, which makes Jami crash.
> pjproject-jami works, because we disable some unused dependencies, but
> pjproject alone never actually worked.
> The problem is there are dependencies packed in third_party folder and
> the build system wants to have them there. I tried removing the
> "make dep" phase, modifying Makefiles, etc, but no matter what I do,
> the build system still complains about not having dependencies, for
> example speex, even though it is present in the propagated inputs field.
> How do we deal with problems like this?

Unfortunately there is no single approach for dealing with these kinds
of problems, as they are typically highly package-specific.

I must admit that I'm a little confused between pjproject and
pjproject-jami.  Is it correct to assume that the latter exists only
because the former fails to build?  Why are you trying to switch?

Would it make sense to get rid of pjproject entirely (nothing depends on
it) in favor of pjproject-jami?

signature.asc
Description: PGP signature