En Mon, 11 Mar 2019 07:01:33 -0600, Michael Van Canneyt via lazarus
<lazarus@lists.lazarus-ide.org> escribió:
On Mon, 11 Mar 2019, Kostas Michalopoulos via lazarus wrote:
On Fri, Mar 8, 2019 at 12:55 PM Juha Manninen via lazarus
<lazarus@lists.lazarus-ide.org> wrote:
Everybody wants to include their custom components in LCL. Why?
Most likely because it is much easier to have a single "batteries
included" installer that provides everything you need out of the box
now and much more likely to be there and working in the future (since
it is part of the codebase that the Lazarus devs are compiling against
after every modification), than chase after packages provided by
others who may or may not keep them available and up to date (keeping
your own copies can solve the "available" part, but then you take
unofficial ownership of the package for the "up to date" part).
Exactly.
Relying on packages somewhere in the cloud can lead to nasty surprises.
I've been bitten by npm ("packaging on steroids") more than once when
developing browser-based apps, and I am very reluctant to use such
mechanisms.
You're constantly chasing version numbers for no good reason.
BTW Is not fppkg something like npm?
and BTW although not for MVC but, can fppkg-lazarus integration be removed
until it just works? I would like not to see the config lazarus IDE dialog
to open on every launch just because fppkg is not setup right (Error: the
Fppkg configuration is corrupt. et al), and there is no way the user can
fix it (when you are not using 'by default' the default fpc install).
Jesus Reyes A.
--
_______________________________________________
lazarus mailing list
lazarus@lists.lazarus-ide.org
https://lists.lazarus-ide.org/listinfo/lazarus
