Opened 14 years ago

Closed 14 years ago

#27762 closed update (fixed)

tinyproxy @1.8.2 update

Reported by: tmurase@… Owned by: ryandesign (Ryan Carsten Schmidt)
Priority: Normal Milestone:
Component: ports Version: 1.9.2
Keywords: Cc:
Port: tinyproxy

Description

Built on OS X 10.6.5, gcc 4.2, Xcode 3.2.2, Component versions: DevToolsCore-1648.0; DevToolsSupport-1631.0, BuildVersion: 10M2148 Attaching a patch that kills an LDFLAGS line in the configure file which is linux specific.

Attachments (2)

patch-configure.diff (239 bytes) - added by tmurase@… 14 years ago.
Patch for configure file
Portfile-tinyproxy.diff (2.2 KB) - added by tmurase@… 14 years ago.
Update to fix the livecheck, startupitem and add a dir for the pid file

Download all attachments as: .zip

Change History (4)

Changed 14 years ago by tmurase@…

Attachment: patch-configure.diff added

Patch for configure file

Changed 14 years ago by tmurase@…

Attachment: Portfile-tinyproxy.diff added

Update to fix the livecheck, startupitem and add a dir for the pid file

comment:1 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)

Owner: changed from macports-tickets@… to ryandesign@…
Status: newassigned

Thanks.

comment:2 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)

Resolution: fixed
Status: assignedclosed

Committed in r75438 with some changes:

  • reformatted
  • install conf file as tinyproxy.conf.default so as not to overwrite the user's configuration when they upgrade the port; more logic should still be added to alert the user they must copy this default file (and/or the port should do so itself); see some other ports for ideas
  • don't install INSTALL file since it just tells the user how to install, which, by the time a user reads this, is something MacPorts has already done

I committed your addition of "-undefined error" to the LDFLAGS and "--disable-regexcheck" to the configure arguments, but I did not understand why these were added; the port seems to compile fine without these lines. Was the addition of these lines solving a specific problem you had?

Note: See TracTickets for help on using tickets.