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

[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 ones that  
> result in invalid file names (as this would lead to problems when  
> creating archives at the file system level).

I'm sure we'd be happy to accept a patch which improved the parsing :)

>> 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 version number  
> in the portfile results in a broken installation.

Does it just extract to a folder with a + in it? If so, you could  
specify worksrcdir in your Portfile.

> Moreover, what is important here is to fix the MacPorts parsing bug  
> uncovered by my portfile, not finding a workaround for some  
> specific portfile that only a few people care about.

The bug may be just that we didn't specify that + is not allowed in  
version.

--
Daniel J. Luke
+========================================================+
| *---------------- dluke at geeklair.net ----------------* |
| *-------------- http://www.geeklair.net -------------* |
+========================================================+
|   Opinions expressed are mine and do not necessarily   |
|          reflect the opinions of my employer.          |
+========================================================+


-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 186 bytes
Desc: This is a digitally signed message part
Url : http://lists.macosforge.org/pipermail/macports-users/attachments/20070510/2de236d3/PGP.bin