Last night Vincent gave us a presentation on his DPM, Delphi Package
Manager. (Hopefully the video will be available soonish)
It is rather good.
Note: In the discussion below, Packages below mostly refer to DPM packages.
You can add a package via DPM to your program (group) and it is only
there for that program (group). If the library has Delphi design time
packages, they are there for that program, but aren’t there when you
load and build some other program.
It also allows you to move your program to a newer (older?) version of
Delphi the project files gets fixed to work on the newer version of
Delphi, and the package files for the newer version are used. (Likely
assumes the package(s) in DPM have suitable entries for the newer
version of Delphi.)
DPM Packages have information indicating the Delphi Versions they
support, and the versions of the Package source available. You can load
an older version of the package if needed and available. DPM will
remember the version you want and restore that version next time you
load the program (group). It also gives you an easy way to upgrade to
the latest version of the package, and back down again.
When you load a package for the first time it is built by DPM. So you
are usually building against DCU files, so fast. In this mode it is a
bit fiddly to look at the actual package source files. There is an
option to use source, so each build will build from the source files.
I often seem to wind up hacking some of the files in packages I use.
Either to get them to compile, or to alter/add some behaviour. I am
assuming I can do this by putting my modified files into a higher
priority folder. (Likely need source mode mentioned above enabled for
the modified package)
There is a DPM package creation program.
It also seems good.
You can have local/private packages on your computer, or on a share that
DPM can access for in house/private use. (eg. commercial packages)
It’s a pretty impressive tool.
Thanks Vincent.