Hi,
Στις 14/4/2020 6:23 π.μ., ο Michael Van Canneyt via lazarus έγραψε:
On Tue, 14 Apr 2020, Sven Barth via lazarus wrote:
Balázs Székely via lazarus <[email protected]> schrieb am
Mo.,
13. Apr. 2020, 20:08:
< snip >
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.
Hmm, how about archive and/or object files for static linking ? An
approach that I saw in mormot ( I don't know if it is the same in OPK I
didn't check the package there ... )
In my case I'm writing a package that it'll use a specific version of
libusb, and I was thinking to use static linking to solve this .
regads,
--
Dimitrios Chr. Ioannidis
--
_______________________________________________
lazarus mailing list
[email protected]
https://lists.lazarus-ide.org/listinfo/lazarus
