Am 10.12.17 um 21:20 schrieb Kurt Jaeger: > Hi! > >> Shouldn't the FLAVOR be part of the package origin? >> >> $ pkg info -o '*setuptools*' >> py27-setuptools-36.5.0 devel/py-setuptools >> py36-setuptools-36.5.0 devel/py-setuptools > > Yes, but it seems this works: > > $ pkg info -o '*setuptools*' > py27-setuptools-36.5.0 devel/py27-setuptools > py34-setuptools-36.5.0 devel/py34-setuptools > py35-setuptools-36.5.0 devel/py35-setuptools > py36-setuptools-36.5.0 devel/py36-setuptools > > with pkg 1.10.99.5
But that output is wrong for a system with ports built after FLAVOR support has been activated. I have already asked portmgr, whether it might be possible, to consider the flavor as a required part of the origin. That should lead to the following output for the first command example: $ pkg info -o '*setuptools*' py27-setuptools-36.5.0 devel/py-setuptools@py27 py36-setuptools-36.5.0 devel/py-setuptools@py36 I'd also like to have a make target "list-pkgname-flavors", which should provide somewhat similar output when run in a port directory: $ cd /usr/ports/devel/py-setuptools $ make list-pkgname-flavors py27-setuptools-36.5.0 py27 py36-setuptools-36.5.0 py36 The purpose is to easily identify the FLAVOR to be passed when building some package with a known name and is the counterpart to querying the FLAVOR of a package from the pkg DB. Regards, STefan _______________________________________________ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"