Daily Ports+ #6: PORTS+_IGNORE or +IGNOREME2008年01月22日 07時25分07秒

Sometime, one needs to avoid upgrading some packages. I have had setup ports+ to ignore clisp due to build failure. I also have others that I don't want to upgrade due to some library reasons, incompatibility reasons, or others.

Ports+ has configuration file. Its default path is /usr/local/etc/ports+.conf. You can add entries to PORTS+_IGNORE.


# grep clisp /usr/local/etc/ports+.conf
PORTS+_IGNORE += clisp.* # build fails

Because the implementation of ports+ is in GNU awk, you specify in the regular expression. That is slightly different from shell wild-card expansions. If any entries in PORTS+_IGNORE matches in either package name or <category>/<portname>, they are ignored from upgrading.

Once I comment it out with #, ports+ test shows that it will upgrade when you say so.


# grep clisp /usr/local/etc/ports+.conf
# PORTS+_IGNORE += clisp.* # build fails
# ports+ test
# upgrade clisp-2.41a to clisp-2.43

It still fails on build so that I want ignore clisp. You can create an _IGNOREME file in the package database directory. Ports+ ignores all packages that +IGNOREME is on. This time I use +IGNOREME so that it is compatible with portugprade and portmaster.

# touch /var/db/pkg/clisp-2.41a/+IGNOREME
# ports+ test

This time, ports+ test does not show any upgrade candidates.

+IGNOREME is the preferred way for most cases as they are compatible with other port upgrading tools. One of these exceptional cases are probably when you need to exclude a set of packages like rubygem.*, .*linux.*, and so on.

Previous. Next.

コメント

コメントをどうぞ

※メールアドレスとURLの入力は必須ではありません。 入力されたメールアドレスは記事に反映されず、ブログの管理者のみが参照できます。

※なお、送られたコメントはブログの管理者が確認するまで公開されません。

名前:
メールアドレス:
URL:
コメント:

トラックバック

このエントリのトラックバックURL: http://uyota.asablo.jp/blog/2008/01/22/2572683/tb

※なお、送られたトラックバックはブログの管理者が確認するまで公開されません。