[MacPorts] #16619: certain characters in long description cause corrupt receipt to be installed

[MacPorts]

#16619: certain characters in long description cause corrupt receipt to be
installed
-------------------------------------------+--------------------------------
  Reporter:  darren.weber.lists at gmail.com  |       Owner:  macports-tickets at lists.macosforge.org
      Type:  defect                        |      Status:  new                                  
  Priority:  Normal                        |   Milestone:  MacPorts base bugs                   
 Component:  base                          |     Version:  1.6.0                                
Resolution:                                |    Keywords:  receipt port syntax                  
      Port:                                |  
-------------------------------------------+--------------------------------

Comment(by darren.weber.lists at gmail.com):

 Replying to [comment:4 jmr@…]:
 > I think you could work around this by wrapping your long_description
 body in braces.

 Yes, that could be the fix.  In that case, all the special backslash
 characters (symbols) would not get parsed.  I've found a discussion of tcl
 parsing online at:
 http://www.beedub.com/book/2nd/tclintro.doc.html.  Also, the Ousterhout
 book "Tcl and the Tk Toolkit" also explains this syntax issue with some
 useful examples.

 I wonder then if macports "should" parse the long_description for any
 special backslash characters, like \n, \t, etc. and then wrap them in {}
 before creating the receipt?  In any case, it might help to have some
 examples of using {} in the MACPORTS GUIDE.  Perhaps a general policy
 statement about the formatting of long_description would help.

-- 
Ticket URL: <http://trac.macports.org/ticket/16619#comment:5>
MacPorts <http://www.macports.org/>
Ports system for Mac OS