FreeBSD has a package system to manage installations and dependencies, and so does perl.\u00a0 Perl on FreeBSD, therefore, causes these to intersect in interesting, and sometimes suboptimal ways.<\/p>\n
CPAN can be used to install perl packages that aren’t in the ports tree, and FreeBSD handles this with relative grace by including them in its package database with the prefix “bsdpan,” and be excluded from updates.\u00a0 An identical package installed from the ports tree will be prefixed with “p5” instead, and be treated as any other port, with dependencies and upgrades handled as part of the ports system.<\/p>\n
After trying out a few CPAN modules (which in turn installed their own dependencies) I found myself with a great many “bsdpan” packages, which I’d prefer to tuck neatly into the bsd ports tree rather than continue to manage with CPAN, therefore, I whanged together a shell script to do it:<\/p>\n
#!\/bin\/sh\r\npkg_info | grep ^bsdpan | awk '{print $1}' > \/tmp\/bsdpan-to-p5.tmp\r\n> \/tmp\/bsdpan-to-p5-2.tmp\r\ncd \/usr\/ports\r\nwhile read bsdname; do\r\n\u00a0 name=$(echo $bsdname | cut -c 8- )\r\n\u00a0 portpath=$(make search name=p5-$name | grep ^Path | awk '{print $2}' | sed -r 's\/\\\/usr\\\/ports\\\/\/\/')\r\n\u00a0 shortname=$(echo $name | sed -r 's\/(.*)-.*\/\\1\/');\r\n\u00a0 if [ \"$portpath\" ]; then\r\n\u00a0\u00a0\u00a0\u00a0 echo -n p5-$name is in ports,\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 echo \" adding to list\"\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 echo portupgrade -o $portpath -f bsdpan-$shortname >> \/tmp\/bsdpan-to-p5-2.tmp\r\n\u00a0 else\r\n\u00a0\u00a0\u00a0\u00a0 echo p5-$name not in ports\r\n\u00a0\u00a0\u00a0\u00a0 portpath=$(make search name=p5-$shortname- | grep ^Path | awk '{print $2}' | sed -r 's\/\\\/usr\\\/ports\\\/\/\/')\r\n\u00a0\u00a0\u00a0\u00a0 if [ \"$portpath\" ]; then\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 paths=$(echo $portpath | wc -w)\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 if [ \"$paths\" -eq \"1\" ]; then\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 p5name=$(make search name=p5-$shortname- | grep Port | awk '{print $2}')\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 echo \" ... $p5name found, using that\"\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 echo portupgrade -o $portpath -f bsdpan-$shortname >> \/tmp\/bsdpan-to-p5-2.tmp\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 fi\r\n\u00a0\u00a0\u00a0\u00a0 fi\r\n\u00a0 fi\r\ndone < \/tmp\/bsdpan-to-p5.tmp\r\nrm \/tmp\/bsdpan-to-p5.tmp\r\necho\r\necho \"Starting conversion ...\"\r\necho\r\nsh \/tmp\/bsdpan-to-p5-2.tmp\r\nrm \/tmp\/bsdpan-to-p5-2.tmp<\/pre>\nThe script tries to automate a manual process of finding the corresponding “p5” port for each “bsdpan” port, and builds a script that replaces each one using the portupgrade tool.<\/p>\n
It doesn’t make any attempt to resolve dependencies, so it may take a few passes.\u00a0 It also can’t help where a search for the port name returns more than one possibility (usually part of a longer name) or when the “p5” name happens to be nothing like the “bsdpan” name, but in practice, there are only a handful of exceptions.<\/p>\n","protected":false},"excerpt":{"rendered":"
FreeBSD has a package system to manage installations and dependencies, and so does perl.\u00a0 Perl on FreeBSD, therefore, causes these to intersect in interesting, and sometimes suboptimal ways. CPAN can be used to install perl packages that aren’t in the ports tree, and FreeBSD handles this with relative grace by \u2026 Continue reading