Hey Marco,
Worse, there are already native options like fppkg, online package manager etc, I myself don't even see a role for it as temporary stopgap till native solutions are developed.
Well, in all honesty this was a tool that was developed with Delphi in mind, since they don't have ANY package manager to boot. Hence the
anything is better than nothing approach makes some sense.
So I guess that Lazarus was an afterthought and kind of an attempt to be inclusive, I guess?! Maybe? I dunno, I'm still a bit stuck on the fact that they decided to use another language to make a tool.
For me it still feels like the carpenter decided to make a tool out of bread because he talked to a baker and he found it would be a good idea. Or some other analogy that makes sense in this situation.
I'm not against using another language for anything, because I'm a firm believer of
the right tool for the job. But what does a package manager need that the basic building blocks of Delphi and/or FPC/Lazarus don't have?! And does Go fit the requirement for
the right tool for the job in the context of a package manager?! And does Delphi fundamentally hinder such a package manager!? And in the long run, the tool has to be maintained by someone that knows the language, so why go outside the wheelhouse?!
But hey, let's not go into flamewar territory
And BTW, has anyone even tried to use
fppkg and/or
OPM on the Delphi side?
I've never used
fppkg, so I'm not really sure how it works, so I'm not gonna opine.
But I've been using
OPM a lot and I think the way it works, to use it on the Delphi side, we could only use the archives from the site since the tool itself is tied to the Lazarus IDE API. We could maybe have a have a version of
OPM that is done with the Delphi IDE API.
Hummmm, after I get my head out of the slump I've been on and we finish the new
OPM site, maybe I'll poke GetMem to maybe investigate how hard would it be to port
OPM to the Dark Side?
Cheers,
Gus