Open vincentparrett opened 5 years ago
Source code is of course preferred but binary form should be also allowed for commercial vendors. The form can be specified with the dependency itself and only the requested part is downloaded.
Both would be preferred to accommodate commercial vendors and trial packages.
Well - the elephant in the room as far as I'm concerned here is "packages" which simply patch or enhance existing functionality - possibly provided by a defunct third party or simply to fix EMBT libraries that EMBT stubbornly and unaccountably refuses to remedy.
For instance, RSP-19551 which requires a 2-line change - all of 10 minutes' work to add the the list of bugs fixed and reported problems solved. Of course, the library in question is covered by a copyright notice - and I don't want to have to fight an international copyright-violation action.
Should a package file contain
Binaries only or source only would simplify dependency resolution. When both are included, the dependency resolution would need to keep track of whether source or binaries are used, for example a binary package could not take a dependency on a source code package, as it would likely result in the dreaded "F2051: Unit %s was compiled with a different version of %s.%s" error.