On Mon, Dec 07, 2009 at 05:12:03PM -0500, Greg Larkin wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Kevin Golding wrote: > > In article <4b1d617a.6020...@freebsd.org>, Greg Larkin > > <glar...@freebsd.org> writes > >> This might get you further: > >> > >> fbsd70# make -V \ > >> PYDISTUTILS_PKGVERSION:C/\(\[\[:digit:\]\]\.\[\[:digit:\]\]\)\./\\1_/g > >> 0.1_0 > >> fbsd70# > > > > Well that does indeed work in that context, but I have no idea why it > > appears to do nothing in the Makefile. It seems completely unchanged: > > > > pkg_delete: unexec command for '/usr/local/bin/easy_install-2.6 -q -m -S > > /usr/local/lib/python2.6/site-packages django-signals-ahoy==0.1.0' > > failed > > > > I actually had to double check I did indeed update the correct file. A > > bit strange anyway. > > > > Kevin > > Hi Kevin, > > There's a lot more backslash escaping required in the :C suffix above > when running the make command directly in the shell. If you remove some > of the backslashes in the equivalent line in the Makefile, should be all > set. Then you can check to make it's working by running "make -V > PYEASYINSTALL_UNINSTALLARGS".
A bit off-topic, and a bit late, but you can avoid the need for those additional backslashes by simply placing the string in apostrophes (single quotes). It's the shell that tries to interpret the string before passing it to "make" itself, and the single quotes tell the shell to not even try to interpret the string. So, just do: make -V 'PYDISTUTILS_PKGVERSION:C/([[:digit:]]\.[[:digit:]])\./\1_/g' ...and you'll see what make(1) thinks of the quoted string, just as if you'd put it in the Makefile. G'luck, Peter -- Peter Pentchev r...@ringlet.net r...@space.bg r...@freebsd.org PGP key: http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint 2EE7 A7A5 17FC 124C F115 C354 651E EFB0 2527 DF13 .siht ekil ti gnidaer eb d'uoy ,werbeH ni erew ecnetnes siht fI
pgpXa9EbTWuFM.pgp
Description: PGP signature
