On 11/03/2019 14:01, Michael Van Canneyt via lazarus wrote:
IMO Lazarus should provide a decent selection that allows someone to
do most
common tasks without needing to install something extra.
(what this "decent selection" is, is up for debate, of course)
Well, that and where does the manpower originate from (aka "who does it?")
Adding more and more to the main product, means more resources needed to
maintain it.
The Idea that none included packages can break (be broken by changes in
the main product) or become outdated, already says it: There may be no
one to maintain it.
Once added to the core product, the core team will maintain it ("must"
maintain it), and therefore reduce efforts on other works.
Besides packages that come with Lazarus, but are not bigide have been
broken before too. (afaik)
----
My understanding is (not using it myself, only from hearsay), that at
current the OPM repository is maintained. So if there is a version that
works, then opm should know, and you need not search for it yourself.
Sure that may break sometimes, but as I said, so do packages that are in
core.
A good idea, would be to have CI. If someone would invest the time, in
setting it up, and contributing the test cases needed (start with "does
it compile") then that would be a solution.
Provided the OPM registry is part of it.
If a change to trunk, would break an opm package, the team, and the
package maintainer would know.
If the maintainer no longer exists, then the team can choose: Fix it, or
remove it from opm.
In the past, afaik, packages have been moved from core to ccr (maybe due
to similar reasons?)
----
Looking at the bugtracker, shows that core is already too big. And that
therefore it does not guarantee, that all issues will be fixed - or will
be fixed quicker than in an opm package.
--
_______________________________________________
lazarus mailing list
[email protected]
https://lists.lazarus-ide.org/listinfo/lazarus
