aware of everything going on on the same host. In particular, group together
other ports waiting for lock on the same host, and run one single pkg_add.
since they are now in order, this helps quite a bit.
that handles held locks, and starts build.
Specialize it for normal builds to remove all build_path_list elements
at once, and choose the smallest one.
in all, this means that the logs will show less variety in what they
build, thus giving better statistics earlier.
from removing them (so that we do less delete/re-add cycles, the more
cores you have the more relevant this becomes).
again, found on Yandex machines, thx to 12 cores or more.
at the end of fake
- sort available cores so that if all hosts fire at the same time, the
load will be fair (found out on yandex machines)
- new iamroot property: for chroot distant hosts, it's simpler to connect
as root, then you can directly chroot -u user and not need the extra sudo
stage.
- more specific "walk_same_host_jobs" to use to signal jobs, for instance.
stylistically, I tend to prefer ``, but since we use a lot of fragments,
the parenthetical nature of $() is better.
- give a more complete name to portstree-/inst- depends lists, so that several
"make package" can run in the same cache.
- create temp dependency files atomically by using mktemp/chmod/mv
(global cache)
(to be referenced by documentation, to stop confusing crypto signatures
with other signatures).
(old name kept over release, to be scraped completely afterwards, user-visible
change only)
okay sthen@
user improvement:
with an extra -d, also scan the directories for "current" pkgnames,
and display a ! in pkgnames that are current while reporting conflicts.
ports. Given that you import port once but update it a few times, make
the update mode (-CU) default for portcheck, and provide a "new port"
switch (-N) instead.
This commit updates portcheck(1) and portimport(1): code, documentation and
tests. The WWW stuff will be updated separately.
Note: regression suite fails now as it detected an actual misconsistence
in portcheck's output. This will be handled ASAP, too.
Initial prodding by naddy@
