DelphiPackageManager
Package or Library or ... ?
Delphi Already uses the term 'Package' for runtime and design time packages (bpl's). So should our package manager really be called a 'Library Manager'?
In most other development environments I have looked at, the term 'Package Manager' is used. Thoughts?
My personal preference is also "Library", perhaps I have a bias against the term "Package" in this context. To be precise: a Package in Delphi is part of a Library.
The current Delphi docs have this definition:
A library is a collection of implementations of subroutines, classes, etc. that you can reuse to develop software.
Although "Library" is also used as synonym for a DLL. There is even a keyword for that.
On the other hand there is also a Library page in the Delphi Options where you specify the "Library path". As the latter is a declared target of this project, I think "Library Manager" should be the preferred term.
Dependency? And dependency manager.
Doesn't roll of the tongue too well.. but worth considering.
@Anders' bundle sounds good. Not already in use in Delphi, but known in other package managing contexts.
The more I think of it, the better it sounds.
Well, other communities have pick a fancy word and go:
- Ruby has "gem" for this concept
- Python has "egg"
So maybe we can be a bit more creative. For my DelphiVM I was considering "brick" and "stone": in the end Delphi was a temple, so a building :D. ... I know it is a bad joke
@jcangas I'd loved to come up with some unique and clever name, ask any vendor, product naming is hard! Ruby & Gem fit together well, it's easy to create some sort of logo etc. I've got nothing though!
There is cucumber, guacamole and whole tomato....let's call it...Tortilla :-)
