[Lazarus] Online Package Manager errors ?

[Michael Van Canneyt]

On Tue, 14 Apr 2020, Sven Barth via lazarus wrote:

> Balázs Székely via lazarus <lazarus at lists.lazarus-ide.org> schrieb am Mo.,
> 13. Apr. 2020, 20:08:
>
>>
>> I have a naive suggestion for OPM. Some components depends on external
>>> libraries/binaries (libffi, openssl, libsagui etc.), so it would be nice
>>> any field like "Libraries", or "Dependencies", or even "External files"
>>> inside the "Package info", providing previous information that the package
>>> needs external libraries/files to work properly. (sorry if it is already
>>> implemented, I'm using Lazarus 2.0.6)
>>>
>> Thanks for the suggestion. In my opinion the external libraries should be
>> shipped with the package(if possible). Adding a new entry in the package
>> tree it's not a problem, it can be done in 15-20 minutes, however the list
>> already has a "Christmas tree" feeling to it. Any extra info should be
>> added to the "package description"  or "community description" entries,
>> which can be opened in a separate form.
>>
>
> I don't agree. Especially on Linux (and the BSDs probably as well) that is
> part of the OS' package manager, even for macOS there is an open source one
> that one can install to handle such things. So a list of required
> dependencies would be enough.
>
> This list would also be useful for deployment of the final application
> however so that one can either set up an installer / package correctly or
> report to the user in a Readme or so what libraries are required.

+1.

Don't distribute binaries, only sources. The binary may not work on all
distributions, you'd need to provide one for all platforms (which you may
not have yourself). It may be outdated, no security fixed applied etc..

Michael.