What decides where GetIt places the stuff it installs?
It seems that the files are placed under current user, even if Delphi is installed for “all users”. How do you get around that for a build server where the build process is running under a system account? This is kinda ridiculous.
Quote from Vincent Parrett: “Umm.. don’t use getit.. its a toy not a real package manager. Seriously why tf would it place libraries under the user profile.”
I have to agree. GetIt appears like a really trivial download/installer, than an actual package installer.
I guess it would be better to install the libs locally, then copy them to VCS managed folders, and check out those on the build server.
Originally shared by Lars Fosdal
GetIt, FinalBuilder and Continua Build Server
We are having some issues with the OmniThreadLibrary not being found when FinalBuilder is invoked from Continua.
GetIt places OTL under
and when I am logged on to the server, the FB projects build fine. When the Continua service user executes, it is a different user than my UI login – so naturally, the installation is not there.
What is the recommended way to get around this?
8 thoughts on “What decides where GetIt places the stuff it installs?”
There is an environment variable you can use, BDSCatalogRepository. I have it set to C:ComponentsEmbarcaderoStudio18.0CatalogRepository for Berlin.
Don’t use GetIt, it’s not appropriate for anything other than toy use.
I’ll repeat: use git submodules. They are in version control, but in separate repositories. This also makes it way easier to do proper versioning as you can select which commit/version the submodule refers to. In addition it is way better for open source stuff, as GetIt is always behind on them.
Conceptual con: it would lack an additional quality check that GetIt could provide if it were maintained as frequently as for instance https://github.com/Homebrew/homebrew-core/commits/master
Now if GetIt was based on a DVCS, that might slightly change things.
I want a package manager that handles library paths properly, deals with dependencies, is easy to publish to etc, you know, something like nuget or npm or ruby gems etc.
Agree with most of the statements made above but to look a little positive on GetIt, at least they put something together. Hopefully they build on it and make it better in future releases.
GetIt is a glorified installer but that is about it, it needs a lot more polishing.
Reading how the Delphinus package manager is based on github, I’d wonder why GetIt doesn’t use a similar construct (or supports them): https://github.com/Memnarch/Delphinus/wiki/Publishing-your-Project-for-Delphinus
Jeroen Wiert Pluimers Perhaps because they want to be able to maintain the full supply chain, e.g. refuse projects as they don’t want to have customers using GetIt adding to Delphi Professional capabilities that are in the “Enterprise” space – see https://synopse.info/forum/viewtopic.php?pid=17453#p17453
Richard Baroniunas you want to give them credit for producing something that is a bit crap? Classic low expectations of the Delphi user.
You must log in to post a comment.