Referencing older entries in ports/UPDATING may be bad practice

Ighighi ighighi at gmail.com
Thu Mar 27 05:09:16 PDT 2008


Referencing old entries in ports/UPDATING that contain the commands,
options, etc. isn't completely safe because those options may change.

In the case of portupgrade(1), at the following options changed between
pkgtools-2.0.1 and pkgtools-2.4.3:

2.0.1:
      -c
      --clean          Do ``make clean'' before each build.  This is the
                       default behavior.  See the -w option below.

      -C
      --cleanup        Do ``make clean'' after each installation.  This
                       is the default behavior.  See the -W option below.

      -q
      --noconfig       Do not read the configuration file -
                       $PREFIX/etc/pkgtools.conf.



2.4.3:
      -c
      --config         Run ``make config-conditional'' before everything
                       for all tasks.  -w option below.

      -C
      --force-config   Run ``make config'' before everything for all
                       tasks.

      -q
      --quiet          Do not display a message when -N specified and
                       there is already installed package.

It doesn't bite to make each entry a little bit more "self-contained"
at least when it comes to the sequence of commands to be run. Though
I haven't yet found a single issue with current practice, it's better
to feel safe than to worry at the possibility, excuse me if it's just
me ;)  Safe for users and developers alike.


More information about the freebsd-ports mailing list