<html><head></head><body bgcolor="#ffffff" text="#2e3436" link="#2a76c6" vlink="#2e3436"><div>Hi Paul, Hi Johannes,</div><div><br></div><div>On Wed, 2016-07-20 at 20:58 +0200, Paul Gevers wrote:</div><blockquote type="cite"><pre>Hi Josch,
On 20-07-16 20:46, Johannes Schauer wrote:
<blockquote type="cite">
could it be that my problem is just a variant of this bug:
<a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823706">https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823706</a>
</blockquote>
I think so.
<blockquote type="cite">
If yes, shall I still file a separate bug?
</blockquote>
That won't be needed than. I am not sure if Abou contacted upstream
about this.</pre></blockquote><div>I've contacted upstream and they don't seem to care about Debian packaging these components, they prefer they get compiled by user when needed. Anyway many compilers/interpreters are going in that direction with their own package manager like (pip, npm, ...). More and more packages will be provided using fppkg (see fppkg -h) and we should be able to handle them.</div><div><br></div><div>Now our issue is with packages that are provided in Lazarus sources, not using fppkg. So these are in half way. Sources are there but not compilation. This makes the use much more complex for us, but users have a very user friendly wizard to do it.</div><div><br></div><div>Unfortunately I don't have enough time to do the complete analysis of what needs to be done and how. So for now I can only propose to add some of these packages manually to the build target using a patch agains the make files or the rules file.</div><div><div><span><pre><pre>--
</pre>Cheers,
Abou Al Montacir</pre></span></div></div></body></html>