Re: IPFire Building Packages

[Ghislain Hachey <ghachey.lists@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 1190 bytes --]

On 7/6/14, 16:57, Michael Tremer wrote:
> That's what we call bundled packages (very often libraries) and which
> are extremely discouraged. The problem that comes with that is that when
> a component gets updated to resolve a certain issue this problem is
> still in the twenty other copies of the same software. Imagine that for
> things like Heartbleed. It also consumes space, increases the build time
> and so on.
>
> You should use the provided versions of those tools and libraries or
> modify them if that is required. All other components that are missing
> should be created as individual packages.

Yeah, I understand that. My only fear is that the software in question 
is including those third party libs as deps because they are needed in a 
very particular shape (specific versions, some source changes, etc.) to 
make it all work properly as a whole. I will check with the developers 
upstream regarding this and if not I will see if I can not modify the 
build process to include those deps as individual packages in IPFire.

Regarding IPFire version 3, If there are specific things I can do to 
help, sure. I'll go through information in the links to get started.

-- 
GH