[Pkg-pascal-devel] Lazarus packaging model

[Paul Gevers]

On 06-05-14 21:12, Abou Al Montacir wrote:
>> As Promised a few weeks ago, I've drawn this graph as a starting point
>> to some documentation work about LCL SW model architecture and its
>> inherent packaging.

Sorry for not responding to your drawing earlier. I must confess that
although it seems to make the upstream architecture clear, if fails for
me to explain what this means for packaging purposes.

> Please note that is could be worth to note that lcl-units are kind of
> libraries while Lazarus is kind of program. Theoretically, one should be
> able to use different LCL versions with the latest Lazarus IDE. It could
> be compared gcc and libc orf fpc and its RTL.
> 
> In this logic, the lcl-${widget set} are just pascal bindings over c
> bindings

I was wondering, does the current upstream way of working scale? I mean,
should these libraries have a "soname bump" every time the compiler
changes? I.e. the units depend on the version of fpc, that is something
that is not true in the c world. This makes it very hard to distribute
multiple source packages with units (like we see now with
castle-game-engine). It means that ALL unit packages must migrate
together from unstable to testing, making this a pain if more unit
packages are packaged. In the c world only the API of the library itself
matters.

Paul (who is neither a c expert nor a library expert)


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 551 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-pascal-devel/attachments/20140506/a0f15ed9/attachment.sig>