because of missing depends. Keep in mind that build_path_list has
to be extensive to avoid LISTING errors...
So, if we meet a stub there, we should do our best to avoid it.
Some of these checks are probably slightly overkill.
problem noticed by landry@
RUN_DEPENDS =
...
RUN_DEPENDS =
This won't catch such problems if they are spread in different files, but
should be helpful anyway now: idea from my recent typo in x11/kde4/runtime.
problems, and make some other automated checks ineffective. And we
try to have are ports more declarative than imperative, anyway.
The idea was supported by espie@ a while ago.
the checks and pkgpath detection ourself in portimport(1).
Sitting on this diff since september, reminded by kirby@.
Tested in the wild by importing many ports, mostly KDE4-related.
Input and okay sthen@
(now committing the right file instead of ports/bin/portcheck)
the checks and pkgpath detection ourself in portimport(1).
Sitting on this diff since september, reminded by kirby@.
Tested in the wild by importing many ports, mostly KDE4-related.
Input and okay sthen@
for dependencies and for running tests.
fix PortInfo to know whether tests are required.
Amend PortBuilder to be able to launch tests.
(there are pieces missing in the engine, like a secondary queue with forced
affinity to run actual tests, and the portbuilder code is very incomplete
and needs love)
following the bsd.port.arch.mk change. Suddenly, some paths make their way
into the build where they should not !
This actually comes from setting up wantbuild/wantinfo straight when building
path lists.
So reorganize stuff:
- don't ask for more scans during straight dump-vars reading.
- perform the "BUILD_PACKAGES may vanish from MULTI_PACKAGES" early in
merge_depends.
- do add appropriate wantbuild/wantinfo during actual dependency registration
there, which ensures depends that got ignored will be built.
This should restore proper behavior and fix long-standing semi-random
behavior.
lang/icon/interp): needs more information than just "we're solving deps"
to know whether to clean things or not.
-> similar problems as locking oneself, similar solution, replace
_SOLVING_DEP with _DEPENDENCY_STACK that tracks the dependencies.
okay mbalmer^Waja
