Opened 16 years ago

Closed 16 years ago

#18482 closed defect (fixed)

port info: curly braces around description when referenced inside long_description

Reported by: ryandesign (Ryan Carsten Schmidt) Owned by: macports-tickets@…
Priority: Normal Milestone: MacPorts 1.8.0
Component: base Version: 1.8.0
Keywords: Cc:
Port:

Description

Regression from 1.7.0: when you look at "port info" for a port whose long_description references ${description}, on trunk the description is surrounded by curly braces; this was not the case with 1.7.0.

MacPorts 1.7.0:

$ port info pure-ffi
pure-ffi @0.4 (devel)
Variants:    darwin

pure-ffi provides an interface to libffi which enables you to call C functions from Pure and vice versa. It goes beyond Pure's built-in C interface in that it also handles C structs and makes Pure functions callable from C. Moreover, depending on the libffi implementation, it may also be possible to call foreign languages other than C.
Homepage:    http://pure-lang.googlecode.com/

Library Dependencies: pure, libffi
Platforms:            darwin
Maintainers:          ryandesign@macports.org

MacPorts trunk @46785:

$ port info pure-ffi
pure-ffi @0.4 (devel)
Variants:             darwin

Description:          pure-ffi provides {an interface to libffi which enables you to call C functions
                      from Pure and vice versa.} It goes beyond Pure's built-in
                      C interface in that it also handles C structs and makes
                      Pure functions callable from C. Moreover, depending on the
                      libffi implementation, it may also be possible to call
                      foreign languages other than C.
Homepage:             http://pure-lang.googlecode.com/

Library Dependencies: pure, libffi
Platforms:            darwin
Maintainers:          ryandesign@macports.org

Attachments (1)

Picture 5.png (85.6 KB) - added by illogic-al@… 16 years ago.
example of {} encompassing description

Download all attachments as: .zip

Change History (4)

comment:1 Changed 16 years ago by illogic-al@…

a) i think this is actually the case in 1.7.0. I've noticed this and am not running trunk. b) i think your braces got eaten in the second example.

comment:2 Changed 16 years ago by illogic-al@…

Aha! it wasn't actually 'port info' where i noticed this, but rather 'port pkg'

If I run the package that was created from a port that ${description} for long_description then I can see what you're referring to. So a) above is incorrect.

Changed 16 years ago by illogic-al@…

Attachment: Picture 5.png added

example of {} encompassing description

comment:3 Changed 16 years ago by lperry (Perry Lee)

Resolution: fixed
Status: newclosed

Fixed in r46800.

Note: See TracTickets for help on using tickets.