cvs commit: ports/x11-wm/fvwm2-devel Makefile pkg-plist ports/x11-wm/fvwm2-devel/files patch-configure

[Peter Jeremy]

On Thu, 2005-Sep-15 17:03:30 +0200, Stijn Hoop wrote:
>On Thu, Sep 15, 2005 at 07:46:34AM -0700, David O'Brien wrote:
>> Or stick them in /etc/make.conf and still have them available for every
>> build.  I'm more than able to use 'vi' and edit /etc/make.conf.
>> And I don't get surprises later when I start some 'make install' of a
>> package with dependencies and walk away - only to find it stopped wanting
>> to know if I want to select some mostly useless options.

I think OPTIONS does have some benefits:
1) It forces the port maintainer to make some effort at listing all the
   configuration options and documenting what they do.
2) It means you get a chance to set configuration options on all the port's
   dependencies without having to track them down in advance.

OTOH, I agree that it's a nuisance to run "make install" or "portupgrade"
and come back several hours later to discover that some obscure dependency
is waiting for you to define its configuration.

>Or do 'make config-recursive' before 'make install'.

Note that this option doesn't exist with portupgrade.

-- 
Peter Jeremy