Closed Pawe1 closed 7 years ago
TBH starter edition support was more or less spontaneous. I did it because it worked(limited, but worked). I won't put too much work on that to deal with certain special cases(for now). Same goes for dependencies on editions(for now). And IDE 10.1/10.2 is already possible(implicitly) since you specify CompilerVersions which goes in hand with the IDE.
BTW at work we usually evaporate the builtin Indy and use the most recent or a custom modified one. Try to control/identify that in a packagemanager oO
Ok, maybe it was not so good example with Indy :stuck_out_tongue: For me DUnit/DUnitX is a problem because if (Delphinus) package installer contains step with building tests it will probably fail in Delphi Starter because DUnit/DUnitX is not shipped with IDE. But on the other side it's pointless to install DUnit in Delphi Professional+ There are other stuff like DB components...
Dependencies => I understand
So maybe Delphinus should add some environment variable for Starter or something?...
TBH tests should not build in a DelphinusPackage
I also sent to Vincent Parrett idea about Delphinus support because of Starter edition sucks and I think people should have easy way to install it. And also some libraries depend on it (for example Delphi Mocks; similar situation is with DUnit & other libraries)
I think that there should be allowed some kind of "virtual" dependencies. I mean dependencies to stuff installed "out of the box" like DUnit / DUnitX / Indy / .... I think that also it should be possible to add IDE version as a dependency (like Starter / Professional or 10.1 / 10.2 / etc.) because the mechanism is similar. I have no idea about implementation - this is only thing to consider.
Why? Because for example Starter edition lacks DUnit Or some ADO stuff / etc