On 30.06.2014 23:23, pulkomandy wrote:
We should fix the problem in haikuporter and make it use the packages available in the running system even if newer versions are available in haikuporter, unless told otherwise. If this is not possible, then we should make --no-dependencies the default behavior.
Using the packages with a matching version from the recipe repository is done intentionally. It ensures that the built package is compatible with the packages from the repository.
The problem is not this default, but the state of the recipe repository. When building a package for release it should be done from the testing or stable branch which provide a consistent set of packages.