Daily Ports+ #3: Ways to Specify Packages2008年01月18日 13時50分51秒

# ports+ test
# upgrade git- to git-
# upgrade eclipse-3.2.2 to eclipse-3.2.2_1
# upgrade cups-base-1.3.5_1 to cups-base-1.3.5_2

The number of ports I need to upgrade is rather small today.

Because the list is so small, I would like to list all of packages. Therefore, I use "-make-config-recursive" but not "-make-config."

# ports+ -make-config-recursive -j3 /usr/ports/devel/git \
java/eclipse /var/db/pkg/cups-base-1.3.5_1

There three forms to specify packages are most convenient ones. One with <category>/<portname> style. One include /usr/ports. One with /var/db/pkg.

When package is specified with fullpath, you can use wildcard like /var/db/pkg/p5-* to upgrade all perl modules /var/db/pkg/rubygem-* to upgrade all rubygem packages. This is most convenient way for upgrading. It is important to note that this format specifies with existing versions. That will trigger upgrades to newer versions. You don't have to find version numbers of new packages.

<category>/<portname> is less convenient for upgrading. You will often use this form when installing new ones.

When using shell auto-completion, you need to delete the ending slash. GNU make does not treat /usr/ports/java/eclipse/ as /usr/ports/java/eclipse. Ports+ will fails to find a way to install java/eclipse if you add tailing slash like /usr/ports/java/eclipse/.

Previous. Next.