On Thu, 24 May 2018 15:02:10 +0100 "Johannes Lundberg" <johal...@gmail.com> said
On Thu, May 24, 2018 at 2:57 PM Chris H <portmas...@bsdforge.com> wrote: > On Thu, 24 May 2018 10:03:47 +0100 "Johannes Lundberg" <johal...@gmail.com> > said > > > On Thu, May 24, 2018 at 9:27 AM Bob Eager <r...@tavi.co.uk> wrote: > > > > > On Thu, 24 May 2018 09:08:17 +0100 > > > Johannes Lundberg <johal...@gmail.com> wrote: > > > > > > > In addition to that it would be nice (if it's not already done) to > > > > store this information in a log file somewhere so that one can > > > > revisit and see what needs to be manually configured for each > > > > installed package. > > > > > > I have this in syslog.conf: > > > > > > !pkg,pkg-static > > > *.* /var/log/pkg.log > > > > > > > Thanks for the tip. I'll use this. > > However, someone who knows about this probably know how to manually > > configure their system already. > > > > I want to make sure first timers and newbies don't miss important > messages > > on how to configure the system. > > > > Often we get inquires about stuff that is clearly described in the pkg > > message and bug reports that are a consequence of wrong configuration. > > How can we make this more clear so that it is not missed? > ports-mgmt/portmaster used (probably still does) to concatenate the list > of (port emitted) messages, and dump them to the console/screen when the > build/install session completed. > Perhaps pkg(8) could incorporate this, as well? > It does. The problem is there's no paging so all information is scrolled away unless you're on standby with scroll-lock which many computers don't have today...
Have you tried less(1) or more(1) ? eg; $ cat ~/output-log | less or, more simply $ less < ./output-log HTH --Chris
_______________________________________________ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
