Forum: Cfengine Help
Subject: FreeBSD package naming (un)conventions
Author: mikec
Link to topic: https://cfengine.com/forum/read.php?3,17970,17970#msg-17970
Hello all,
I'm trying to use cfengine to manage packages on FreeBSD boxen, and am
wondering if anybody has already solved the problem of how to manage
packages which are "renamed" on installation by the FreeBSD ports system.
As a simple example, the Reportlab (py-reportlab) port is renamed at
installation,
based on which version of Python it's installed/compiled against. So, assuming
that
Python 2.6 is installed, then Reportlab is installed as something like
py26-reportlab-1.2.3
rather than
py-reportlab-1.2.3
This makes it interesting to determine whether a port is installed.
There are also other variations on this (i.e. inconsistency):
mod_python3 => ap22-mod_python-3.3.1_3 when installed against Apache 2.2
apr => apr-ipv6-devrandom-gdbm-db47-1.4.2.1.3.9_1 showing which options
APR was built with
Please note that I'm *not* using pkg_add with pre-built packages here.
One of the requirements is to be able to compile and install the latest
version of a port automatically, and having to maintain multiple variants
of a package, each dealing with a different combination of
features/relationships
isn't feasible for this particular task.
Any suggestions? I'd rather not have to write my own package interface and
trawl through /var/db/pkg/*
Cheers
Mike
_______________________________________________
Help-cfengine mailing list
Help-cfengine@cfengine.org
https://cfengine.org/mailman/listinfo/help-cfengine
