From yar@bsd.chem.msu.ru  Sat Jan 26 12:40:53 2008
Return-Path: <yar@bsd.chem.msu.ru>
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 7876516A475;
	Sat, 26 Jan 2008 12:40:53 +0000 (UTC)
	(envelope-from yar@bsd.chem.msu.ru)
Received: from bsd.chem.msu.ru (bsd.chem.msu.ru [195.208.208.23])
	by mx1.freebsd.org (Postfix) with ESMTP id 0559413C459;
	Sat, 26 Jan 2008 12:40:52 +0000 (UTC)
	(envelope-from yar@bsd.chem.msu.ru)
Received: from bsd.chem.msu.ru (localhost [127.0.0.1])
	by bsd.chem.msu.ru (8.13.8/8.13.8) with ESMTP id m0QCXxJj007471;
	Sat, 26 Jan 2008 15:33:59 +0300 (MSK)
	(envelope-from yar@bsd.chem.msu.ru)
Received: (from yar@localhost)
	by bsd.chem.msu.ru (8.13.8/8.13.8/Submit) id m0QCXxnH007470;
	Sat, 26 Jan 2008 15:33:59 +0300 (MSK)
	(envelope-from yar)
Message-Id: <200801261233.m0QCXxnH007470@bsd.chem.msu.ru>
Date: Sat, 26 Jan 2008 15:33:59 +0300 (MSK)
From: Yar Tikhiy <yar@comp.chem.msu.su>
To: FreeBSD-gnats-submit@freebsd.org
Cc: dougb@freebsd.org
Subject: portmaster still issues prompts in unattended mode
X-Send-Pr-Version: 3.113
X-GNATS-Notify:

>Number:         120001
>Category:       ports
>Synopsis:       portmaster still issues prompts in unattended mode
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    dougb
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat Jan 26 12:50:02 UTC 2008
>Closed-Date:    Tue Feb 12 20:11:46 UTC 2008
>Last-Modified:  Tue Feb 12 20:11:46 UTC 2008
>Originator:     Yar Tikhiy
>Release:        FreeBSD 6.2-RELEASE i386
>Organization:
none
>Environment:

	portmaster 2.0

>Description:
	
	If given a -u option (unattended mode) and a list of ports
	to work on, portmaster still will ask if it shall update
	each port.

>How-To-Repeat:

	# portmaster -u portmaster
	===>>> Gathering distinfo list for installed ports
	===>>> Update portmaster-2.0? [n]
	
	# portmaster -f -u portmaster
	===>>> Gathering distinfo list for installed ports
	===>>> Update portmaster-2.0? [n]

>Fix:

	At least in combination with -f, -u should inhibit all prompts.
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: dougb 
State-Changed-When: Sat Jan 26 16:13:22 UTC 2008 
State-Changed-Why:  



Responsible-Changed-From-To: freebsd-ports-bugs->dougb 
Responsible-Changed-By: dougb 
Responsible-Changed-When: Sat Jan 26 16:13:22 UTC 2008 
Responsible-Changed-Why:  


http://www.freebsd.org/cgi/query-pr.cgi?pr=120001 
State-Changed-From-To: closed->analyzed 
State-Changed-By: dougb 
State-Changed-When: Sat Jan 26 16:13:51 UTC 2008 
State-Changed-Why:  

Oops, gnats did what I told it, instead of what I wanted it to do. 

The behavior you're seeing is a feature, since if a user specifies 
a glob pattern for something in /var/db/pkg we want to be absolutely 
sure that we're updating the port they actually intended to update. 

I will make an effort to clarify the man page in this regard. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=120001 

From: Yar Tikhiy <yar@comp.chem.msu.su>
To: dougb@FreeBSD.org
Cc: bug-followup@FreeBSD.org
Subject: Re: ports/120001: portmaster still issues prompts in unattended mode
Date: Sun, 27 Jan 2008 07:43:51 +0300

 On Sat, Jan 26, 2008 at 04:15:53PM +0000, dougb@FreeBSD.org wrote:
 > 
 > The behavior you're seeing is a feature, since if a user specifies
 > a glob pattern for something in /var/db/pkg we want to be absolutely
 > sure that we're updating the port they actually intended to update.
 > 
 > I will make an effort to clarify the man page in this regard.
 
 Perhaps it's worth also noting in the manpage that to get truly
 unattended mode for portupgrade -a, one needs to specify more
 options.  In particular, "make config" should be suppressed.
 Here's the command that works for me:
 
 	portmaster -a -u -G -m BATCH=YES
 
 Today, when hundreds to thousands of ports are installed in an
 average desktop system, using default build options just saves one's
 time while the benefits from customizing individual ports aren't
 worth the effort spent.  E.g., the installation of X and a desktop
 environment can finish in a night if run unattended, but it will
 turn into a many-day nuisance if one chooses to respond to all the
 "make config" dialogs.
 
 But, if all the dialogs were ignored at the install time via -DBATCH,
 they'll need to be ignored explicitly at the portupgrade time, too,
 because no config files exist in /var/db/ports.
 
 -- 
 Yar

From: Doug Barton <dougb@FreeBSD.org>
To: Yar Tikhiy <yar@comp.chem.msu.su>
Cc: bug-followup@FreeBSD.org
Subject: Re: ports/120001: portmaster still issues prompts in unattended mode
Date: Sat, 26 Jan 2008 20:52:08 -0800

 Yar Tikhiy wrote:
 > On Sat, Jan 26, 2008 at 04:15:53PM +0000, dougb@FreeBSD.org wrote:
 >> The behavior you're seeing is a feature, since if a user specifies
 >> a glob pattern for something in /var/db/pkg we want to be absolutely
 >> sure that we're updating the port they actually intended to update.
 >>
 >> I will make an effort to clarify the man page in this regard.
 > 
 > Perhaps it's worth also noting in the manpage that to get truly
 > unattended mode for portupgrade -a, one needs to specify more
 > options.  In particular, "make config" should be suppressed.
 
 You mean like what it says now? :)
 -u  unattended mode -- accept defaults for all but 'make config'
 
 > Today, when hundreds to thousands of ports are installed in an
 > average desktop system, using default build options just saves one's
 > time while the benefits from customizing individual ports aren't
 > worth the effort spent. 
 
 That is your opinion, and you're entitled to it. That's also why I put
 -G mode in there to satisfy people who have your perspective.
 
 > E.g., the installation of X and a desktop
 > environment can finish in a night if run unattended, but it will
 > turn into a many-day nuisance if one chooses to respond to all the
 > "make config" dialogs.
 
 I'm not sure what you mean by this. You only have to answer the
 questions once, and you answer them all before anything starts
 building. If you have to run portmaster again for the same port, you
 won't be prompted with the OPTIONS again unless they've changed (or
 you use --force-config).
 
 In any case, a user found an actual bug today when using a combination
 of options that had never occurred to me, so I will be updating both
 the script and the man page "soonish."
 
 Doug
 
 
 -- 
 
     This .signature sanitized for your protection
 

From: Doug Barton <dougb@FreeBSD.org>
To: Yar Tikhiy <yar@comp.chem.msu.su>
Cc: bug-followup@FreeBSD.org
Subject: Re: ports/120001: portmaster still issues prompts in unattended mode
Date: Sat, 26 Jan 2008 20:52:20 -0800

 Yar Tikhiy wrote:
 > On Sat, Jan 26, 2008 at 04:15:53PM +0000, dougb@FreeBSD.org wrote:
 >> The behavior you're seeing is a feature, since if a user specifies
 >> a glob pattern for something in /var/db/pkg we want to be absolutely
 >> sure that we're updating the port they actually intended to update.
 >>
 >> I will make an effort to clarify the man page in this regard.
 > 
 > Perhaps it's worth also noting in the manpage that to get truly
 > unattended mode for portupgrade -a, one needs to specify more
 > options.  In particular, "make config" should be suppressed.
 
 You mean like what it says now? :)
 -u  unattended mode -- accept defaults for all but 'make config'
 
 > Today, when hundreds to thousands of ports are installed in an
 > average desktop system, using default build options just saves one's
 > time while the benefits from customizing individual ports aren't
 > worth the effort spent. 
 
 That is your opinion, and you're entitled to it. That's also why I put
 -G mode in there to satisfy people who have your perspective.
 
 > E.g., the installation of X and a desktop
 > environment can finish in a night if run unattended, but it will
 > turn into a many-day nuisance if one chooses to respond to all the
 > "make config" dialogs.
 
 I'm not sure what you mean by this. You only have to answer the
 questions once, and you answer them all before anything starts
 building. If you have to run portmaster again for the same port, you
 won't be prompted with the OPTIONS again unless they've changed (or
 you use --force-config).
 
 In any case, a user found an actual bug today when using a combination
 of options that had never occurred to me, so I will be updating both
 the script and the man page "soonish."
 
 Doug
 
 
 -- 
 
     This .signature sanitized for your protection
 

From: Yar Tikhiy <yar@comp.chem.msu.su>
To: Doug Barton <dougb@FreeBSD.org>
Cc: bug-followup@FreeBSD.org
Subject: Re: ports/120001: portmaster still issues prompts in unattended mode
Date: Sun, 27 Jan 2008 08:17:11 +0300

 On Sat, Jan 26, 2008 at 08:52:20PM -0800, Doug Barton wrote:
 > Yar Tikhiy wrote:
 > > On Sat, Jan 26, 2008 at 04:15:53PM +0000, dougb@FreeBSD.org wrote:
 > >> The behavior you're seeing is a feature, since if a user specifies
 > >> a glob pattern for something in /var/db/pkg we want to be absolutely
 > >> sure that we're updating the port they actually intended to update.
 > >>
 > >> I will make an effort to clarify the man page in this regard.
 > > 
 > > Perhaps it's worth also noting in the manpage that to get truly
 > > unattended mode for portupgrade -a, one needs to specify more
 > > options.  In particular, "make config" should be suppressed.
 > 
 > You mean like what it says now? :)
 > -u  unattended mode -- accept defaults for all but 'make config'
 
 An example in EXAMPLES can show how to suppress prompts and dialogs
 totally via a combination of options.
 
 > > Today, when hundreds to thousands of ports are installed in an
 > > average desktop system, using default build options just saves one's
 > > time while the benefits from customizing individual ports aren't
 > > worth the effort spent. 
 > 
 > That is your opinion, and you're entitled to it. That's also why I put
 > -G mode in there to satisfy people who have your perspective.
 
 Nevertheless, it may deserve a line in EXAMPLES. :-)
 
 > > E.g., the installation of X and a desktop
 > > environment can finish in a night if run unattended, but it will
 > > turn into a many-day nuisance if one chooses to respond to all the
 > > "make config" dialogs.
 > 
 > I'm not sure what you mean by this. You only have to answer the
 > questions once, and you answer them all before anything starts
 > building. If you have to run portmaster again for the same port, you
 > won't be prompted with the OPTIONS again unless they've changed (or
 > you use --force-config).
 
 My point is as follows.  Assume I don't have time or will to answer
 to the bunch of cryptic questions when initially installing such
 big things as X+Gnome, so I set BATCH and I'm happy with the default
 installation.  Later I'd like to update my ports, but I still have
 no time or will to go through the dialogs.  Fortunately, there is
 a combination of options to portupgrade allowing me to skip all the
 dialogs again.  Isn't it worth mentioning in EXAMPLES? :-)
 
 > In any case, a user found an actual bug today when using a combination
 > of options that had never occurred to me, so I will be updating both
 > the script and the man page "soonish."
 
 Thanks!
 
 -- 
 Yar
State-Changed-From-To: analyzed->closed 
State-Changed-By: dougb 
State-Changed-When: Tue Feb 12 20:09:47 UTC 2008 
State-Changed-Why:  

Originator reports that he is satisfied with the new version, 
and version 2.1 of the man page contains the updates I mentioned. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=120001 
>Unformatted:
