[prev in list] [next in list] [prev in thread] [next in thread] 

List:       crux
Subject:    Re: Package Problems
From:       Robert McMeekin <rrm3 () rrm3 ! org>
Date:       2004-01-18 12:48:00
Message-ID: 200401181248.i0ICm05U002254 () reveal ! local
[Download RAW message or body]

On Sun, 18 Jan 2004 at 00:08:46 -0500,
johnlowell[at]ameritech.net (John Lowell) wrote:

> I guess I ought to find out now what the proceedure is for reporting
> something like this; should I be making some kind of log file for
> builds so the output is available for the package mantainer if a
> problem develops? I've had problems in the past with properly
> capturing output to a build directory using something like pkgmk -d -i
> | tee build.lst because the output gets cut-off in its final steps or
> otherwise doesn't conform to screen output. What is the preferred
> method for dealing with build output at Crux so that both maintainer
> and users can get the most from a solution to a problem of this kind?

pkgmk -f 2>&1 | tee $LOG_FILE

// Rob
-- 
"He's a globe-trotting voodoo senator trapped in a world he never
 made. She's a sharp-shooting insomniac barmaid on the trail of a
 serial killer. They fight crime!"
 
[prev in list] [next in list] [prev in thread] [next in thread]