Opened 7 years ago

Closed 7 years ago

Last modified 7 years ago

#43200 closed enhancement (fixed)

LibreCAD 2.0.3

Reported by: librecad@… Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version:
Keywords: haspatch maintainer Cc: dongxuli2011@…
Port: LibreCAD

Description

Attached diff for port file to build LibreCAD 2.0.3

This patch also removes the dependency on muparser that is included in LibreCAD The reason for doing this is because of bug in muparser that doesn't process locales correctly. The included version of muparser is this fix attached. We will be removing muparser from LibreCAD once this patch has been applied by the muparser folks.

I believe it's related to this : https://code.google.com/p/muparser/issues/detail?id=1

Attachments (1)

Portfile-LibreCAD.diff (1.7 KB) - added by librecad@… 7 years ago.
new patch against 2.0.2

Download all attachments as: .zip

Change History (6)

comment:1 Changed 7 years ago by mf2k (Frank Schima)

Cc: dongxuli2011@… added
Keywords: haspatch maintainer added
Milestone: MacPorts 2.3.0
Port: LibreCAD added
Version: 2.2.1

In the future, please fill in the Port field. The Milestone field is for Macports team members' use only, please do not set it.

comment:2 Changed 7 years ago by mf2k (Frank Schima)

Resolution: fixed
Status: newclosed

Thanks. r118673.

Note the following for the next time.

$ port lint --nitpick LibreCAD
--->  Verifying Portfile for LibreCAD
Error: Line 75 hardcodes /opt/local, use ${prefix} instead
Error: Line 77 hardcodes /opt/local, use ${prefix} instead

Changed 7 years ago by librecad@…

Attachment: Portfile-LibreCAD.diff added

new patch against 2.0.2

comment:3 Changed 7 years ago by librecad@…

I attached a new patch against 2.0.2 that fixes a error we received from the build bot. It also uses ${prefix} instead of the hard coded path

comment:4 Changed 7 years ago by mf2k (Frank Schima)

Please attach a new patch against the current version of the Portfile in svn - which is version 2.0.3. Also, in the future, please open a new ticket rather than attaching a patch to a closed ticket.

comment:5 Changed 7 years ago by mf2k (Frank Schima)

You are referring to #43276.

Note: See TracTickets for help on using tickets.