Re: port activate error: can't read "revision": no such variable

2007-05-10 Thread Paulo Moura
On 2007/05/10, at 15:10, Daniel J. Luke wrote: On May 10, 2007, at 5:36 AM, Paulo Moura wrote: there is not whitespace preceding the last "+". Therefore, it should not confuse MacPorts. Making "+" an illegal character is just the wrong way of fixing what seems to be a parsing bug in MacPo

Re: port activate error: can't read "revision": no such variable

2007-05-10 Thread James Berry
On May 10, 2007, at 2:36 AM, Paulo Moura wrote: I'm in favor of getting the + out of your version number. The "3.0.1+" version number is not something I control as is used by the third-party software. This software install on a directory named after this version number. Using a different

Re: port activate error: can't read "revision": no such variable

2007-05-10 Thread Daniel J. Luke
On May 10, 2007, at 5:36 AM, Paulo Moura wrote: there is not whitespace preceding the last "+". Therefore, it should not confuse MacPorts. Making "+" an illegal character is just the wrong way of fixing what seems to be a parsing bug in MacPorts. The only illegal characters should be the one

Re: port activate error: can't read "revision": no such variable

2007-05-10 Thread Paulo Moura
On 2007/05/10, at 10:02, Ryan Schmidt wrote: James Berry has committed some changes recently that removes '+' from the list of acceptable characters in port names (see top of the current ChangeLog [1]). If that's not it, I'm out of ideas :-) That change seems (from an outsider) quite arbi

Re: port activate error: can't read "revision": no such variable

2007-05-10 Thread Ryan Schmidt
On May 9, 2007, at 14:29, paul beard wrote: There is no "revision" variable in the portfile. Any ideas? Thanks, This man page seems to contradict itself, but perhaps it's not optional, as mentioned below. [snip] revision Local revision number of Portfile. Increment for port

Re: port activate error: can't read "revision": no such variable

2007-05-10 Thread Ryan Schmidt
On May 10, 2007, at 01:28, Paulo Moura wrote: On 2007/05/10, at 05:58, Boey Maun Suang wrote: You wouldn't happen to be running MacPorts from ToT (a.k.a. trunk), rather than a release version? Nope, I'm running the latest stable one (1.440). James Berry has committed some changes recently

Re: port activate error: can't read "revision": no such variable

2007-05-09 Thread Paulo Moura
On 2007/05/10, at 05:58, Boey Maun Suang wrote: You wouldn't happen to be running MacPorts from ToT (a.k.a. trunk), rather than a release version? Nope, I'm running the latest stable one (1.440). James Berry has committed some changes recently that removes '+' from the list of acceptable

Re: port activate error: can't read "revision": no such variable

2007-05-09 Thread Boey Maun Suang
Hi, On 10/05/2007, at 08:22, Paulo Moura wrote: The problem seems to be that MacPorts is not properly escaping version strings. The "3.0.1+" version comes from the software that the Portfile gets from CVS. This leads me to use the same version name on the portfile, otherwise the symbolic l

Re: port activate error: can't read "revision": no such variable

2007-05-09 Thread Paulo Moura
On 2007/05/09, at 22:57, James Berry wrote: Actually, try doing this: sudo port -p uninstall xsb @3.0.1+_0/ (add a slash to the end of the version number). This disambiguates the version from any variants for the port. I'm not sure it'll work, since I'm still not sure I know where

Re: port activate error: can't read "revision": no such variable

2007-05-09 Thread James Berry
On May 9, 2007, at 1:13 PM, Daniel J. Luke wrote: On May 9, 2007, at 4:08 PM, Paulo Moura wrote: pmmbp:~/Documents/Prolog/xsbcvs pmoura$ sudo port -f install ---> Fetching xsb ---> Verifying checksum(s) for xsb ---> Extracting xsb ---> Configuring xsb ---> Building xsb with target all ---

Re: port activate error: can't read "revision": no such variable

2007-05-09 Thread Paulo Moura
On 2007/05/09, at 21:13, Daniel J. Luke wrote: The + in the versions is likely confusing port. If that is really the case, then I would say that I tripped on a MacPorts bug (I'm using the latest version, ). You could try escaping it with a \ Tried it without success: pmmbp:~/Documents

Re: port activate error: can't read "revision": no such variable

2007-05-09 Thread Daniel J. Luke
On May 9, 2007, at 4:08 PM, Paulo Moura wrote: pmmbp:~/Documents/Prolog/xsbcvs pmoura$ sudo port -f install ---> Fetching xsb ---> Verifying checksum(s) for xsb ---> Extracting xsb ---> Configuring xsb ---> Building xsb with target all ---> Staging xsb into destroot ---> Packaging tgz arch

Re: port activate error: can't read "revision": no such variable

2007-05-09 Thread Paulo Moura
On 2007/05/09, at 20:29, paul beard wrote: On May 9, 2007, at 12:02 PM, Paulo Moura wrote: There is no "revision" variable in the portfile. Any ideas? Thanks, This man page seems to contradict itself, but perhaps it's not optional, as mentioned below. ... revision Local rev

Re: port activate error: can't read "revision": no such variable

2007-05-09 Thread paul beard
On May 9, 2007, at 12:02 PM, Paulo Moura wrote: There is no "revision" variable in the portfile. Any ideas? Thanks, This man page seems to contradict itself, but perhaps it's not optional, as mentioned below. MAIN VARIABLES All ports are required to set certain variables. name

port activate error: can't read "revision": no such variable

2007-05-09 Thread Paulo Moura
Hi! I'm writing a portfile for XSB, a logic programming language. When doing a port activate, I get the following error: DEBUG: Executing com.apple.activate (xsb) ---> Activating xsb 3.0.1+_0 Error: Target com.apple.activate returned: can't read "revision": no such variable Warning: the f