portupgrade question

Nikola Lecic nlecic at EUnet.yu
Wed Aug 15 01:10:32 PDT 2007

On Wed, 15 Aug 2007 08:36:53 +0400 (GST)
Rakhesh Sasidharan <rakhesh at rakhesh.com> wrote:

> Nikola Lecic wrote:
> > Yes, options are not saved that way and Vim's default is with X11.
> > Please make sure that the following lines exist in
> > your /usr/local/etc/pkgtools.conf:
> >
> >  MAKE_ARGS = {
> >  	'editors/vim' => 'NO_GUI=yes',
> >  	[... options for other ports ...]
> >  }
> >
> > Next time portupgrade will honour it (without -P/-PP options, of
> > course).
> As far as I know, portupgrade won't honour this setting vim is
> upgraded as a dependency of some other port. (Please correct me if
> I'm wrong. I haven't tried this; its just something I read).

At least with portupgrade-devel, that doesn't seem true. I read it
too, and the source was an unofficial blog. For example, I have:

      'print/apsfilter'           => 'PAPERSIZE=a4',
      'print/ghostscript-gpl'     => 'A4=yes',

ghostscript-gpl is a dependency of apsfilter. Now, ghostscript-gpl
needed update. I removed apsfilter for this testing purpose and:

  # portupgrade -NR apsfilter
  --->  Installing 'apsfilter-7.2.8_3' from a port (print/apsfilter)
  --->  Building '/usr/ports/print/apsfilter' with make flags: PAPERSIZE=a4
  --->  Upgrading 'ghostscript-gpl-8.57' to 'ghostscript-gpl-8.57_1'
  --->  Building '/usr/ports/print/ghostscript-gpl' with make flags: A4=yes A4=yes

> So the /etc/make.conf option is better.

It is definitively the most universal and IMHO it should appear in the

I just like to keep all ports/packages upgrading options at the same

BTW, as far as I can recollect, as a global-honouring tool for ports
configuration, the most frequently quoted one along these lists was

Nikola Lečić

More information about the freebsd-questions mailing list