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@
you cite in email, but noone stops you to !fmt the text. This removes the
corresponding parameter from check_long_lines() because it's not needed
anymore.
inspired in chat by bcallah@, idea okayed by sthen@, espie@ and naddy@
usually added by corresponding MODULE, which, of course, does his work
right. So catch common "kdeui" and "kio" libraries, too. Already run into
this a few times.
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@
- Make sure there is @unexec-delete rm -f %D/share/icons/foo/icon-theme.cache
for every icon theme index file; e.g., remove caches altogether with the
theme itself. Also, make sure that such line preceeds all of the icon theme
files there.
- Stop checking if the @exec/@unexec-delete line for theme is already listed:
we already take number of them into account, and those checks involve
calling the fgrep(1).
- choose size/nosize in Config.
- use affinity or affinitystub
- move locker creation to State, so we can init cores right away.
- as core init has run, we can call DPB::Core->reap (event loop) while
processing size and build stats, so that the startup script may start
slightly earlier.
- setup more options in Config for Reporter to use.
- scaffolding in SubEngine/Build to be able to use affinity info right away
