i keep *trying* to move from portupgrade to portmaster

Doug Barton dougb at FreeBSD.org
Fri Aug 6 21:26:26 UTC 2010

On 08/06/2010 04:34, jhell wrote:

> Doug,
> One fallback that I cannot seem to get over is the creation of a backup
> package failed do you want to ignore [i] message prompt & the package
> messages that are displayed with $PAGER at the end of the upgrades.  I
> do not recall the packages that his had happened on, it does not happen
> often but when it did happen it was just before a nice long compile of
> OpenOffice :( while I was gone.
> The pkg-message problem has been stumping me since it inhibits my use of
> pwait(1) on another terminal. For instance I started a portmaster -a on
> one terminal and issued pwait(1) on another so I could build a new
> kernel and world right after a ports(7) upgrade. Since the pkg-message
> is displayed with PAGER obviously the initial portmaster process never
> terminates and post processes are revolving so they would/could exit to
> soon.

To deal with this you can use PAGER=cat, either on the command line, or
you can put it in a portmaster rc file.

> Do not prompt for a backup package creation failure

I need to add an option for this, but it will likely be an "expert"
option that you can set in the rc file. The theory is that package
creation failure should be a rare thing, and since portmaster has no way
to know what packages are really critical to any given system it treats
inability to safely recover from an upgrade failure as a critical error.
However, having the ability to disable this is an oft-requested feature,
I just haven't gotten to it yet.

I actually took a look at the code in this area last night with an eye
towards creating this option, I'll see if I can get it done for the next

> and force creation of whatever you have on the system already?

Not sure what this means, can you explain it in more detail?

> Configuration option to email the output of upgraded packages and their
> pkg-message or a similar option to just log to a file?

The ability to log actions to a file is already in the dev version in
svn. You have to specify PM_LOG in your rc file. I want to see how that
goes first before I consider adding a command line option for it. I
don't anticipate adding e-mail functionality to portmaster, that sounds
like something that should be done in a wrapper script, along with
PM_LOG. (Although, there was a meme from the early days that no Unix app
is complete until it grows the ability to do e-mail, so you never know ...)

> Also I still see a need for installing a
> /usr/local/etc/portmaster.rc.sample file for whatever version is
> installed and seperating that from the man page. This would make it much
> easier on the end user to configure portmaster for options they see fit.

Yeah, I think you're probably right that it's time to do this. The
current system actually makes it easier for me to keep the docs up to
date when I add new options, but maybe if I remove that bit the man page
won't seem so scary. :)



	Improve the effectiveness of your Internet presence with
	a domain name makeover!    http://SupersetSolutions.com/

	Computers are useless. They can only give you answers.
			-- Pablo Picasso

More information about the freebsd-ports mailing list