multi-packages and portslogger
While looking at some output from portslogger I noticed that some ports are splitting the logging beteween $DISTNAME.log and $PKGNAME.log (with and without the p version suffix. The problem seems to only occur on ports with multi-packages. Example from a build with an empty log dir: [EMAIL PROTECTED]:~$ ls -1 /usr/ports/logs/*dnet* /usr/ports/logs/libdnet-1.10.log /usr/ports/logs/libdnet-1.10p2.log /usr/ports/logs/py-libdnet-1.10p1.log On a normal port it looks like this: === Checking files for x2vnc-1.6.1p0 === Extracting for x2vnc-1.6.1p0 === Patching for x2vnc-1.6.1p0 === Configuring for x2vnc-1.6.1p0 === Building for x2vnc-1.6.1p0 === Faking installation for x2vnc-1.6.1p0 === Building package for x2vnc-1.6.1p0 === Cleaning for x2vnc-1.6.1p0 On a multipackages port the p suffix is left off on some of the output steps: === Checking files for libdnet-1.10 === Extracting for libdnet-1.10 === Patching for libdnet-1.10 === Configuring for libdnet-1.10 === Building for libdnet-1.10 === Faking installation for libdnet-1.10 === Building package for libdnet-1.10p2 === Cleaning for libdnet-1.10p2 David
Re: multi-packages and portslogger
On Thu, Dec 28, 2006 at 12:02:13PM -0600, David Krause wrote: While looking at some output from portslogger I noticed that some ports are splitting the logging beteween $DISTNAME.log and $PKGNAME.log (with and without the p version suffix. The problem seems to only occur on ports with multi-packages. Example from a build with an empty log dir: Yes, it's a feature... not a bug.