David Wolfskill <david_at_catwhisker.org> wrote on
Date: Tue, 24 Dec 2024 14:46:46 UTC :
> As an experiment, I set up my newest laptop to update only via
> freebsd-update and installed only pre-built packages. (I am far more
> accustomed to building FreeBSD from source, as well as updating ports
> either via portmaster or by buidling my own packages, so there's a
> fairly high probability that I've rather lost the plot, here.)
>
> Now, the laptop is set up to run xdm at start-up; it's very much an
> "X11" setup.
>
> And for reference, it's running:
>
> FreeBSD g1-96.catwhisker.org 14.2-RELEASE FreeBSD 14.2-RELEASE
> releng/14.2-n269506-c8918d6c7412 GENERIC amd64
>
> And I run "pkg upgrade" on it every morning, to keep the packages
> up-to-date.
>
> A while back, I had decided that I wanted to use gimp, so I installed
> that. (via "pkg install ...") without fuss.
>
> This morning, I tried a script that I had cobbled up a while back (and
> used on an older laptop) which makes use of ImageMagik's "convert"
> utility -- and found that it wasn't installed on the newer laptop.
>
> So:
>
> | g1-96(14.2-R)[16] pkg install graphics/ImageMagick7
> . . .
Using this as an example for identifying the type of Makefile
notation involved to help predict from that . . .
# grep -E "(FLAVOR|PKG)" /usr/ports/graphics/ImageMagick7/Makefile
PKGNAMESUFFIX= 7
FLAVORS= x11 nox11
FLAVOR?= ${FLAVORS:[1]}
FLAVORS_SUB= yes
nox11_PKGNAMESUFFIX= 7-nox11
. . .
That "FLAVOR?= ${FLAVORS:[1]}" picks out the nox11 as the default.
More explicit but still in origin notation might be (presuming
it is accepted for install):
# pkg install graphics/ImageMagick7@x11
Seeing if there is a FLAVORS list and what its content is can be
helpful for knowing what to type.
The "nox11_PKGNAMESUFFIX= 7-nox11" is what made the package name
have -nox11 as part of its suffix. Nothing was set up to have a
-x11 in the package naming for the other case.
In package notation:
# pkg install ImageMagick7
will happen to pick out the x11 FLAVOR instead of the
ImageMagick7-nox11 FLAVOR.
It can be harder to identify the package notation for a
FLAVOR than to identify the origin @FLAVOR suffix to use.
This port's an example of that. Some ports always have
a suffix (or prefix) notation for each FLAVOR.
===
Mark Millard
marklmi at yahoo.com
