[MacPorts] #16621: libpqxx

MacPorts noreply at macports.org
Mon Sep 22 21:37:54 PDT 2008


#16621: libpqxx
-------------------------------------------+--------------------------------
  Reporter:  darren.weber.lists at gmail.com  |       Owner:  ryandesign at macports.org
      Type:  enhancement                   |      Status:  closed                 
  Priority:  Normal                        |   Milestone:  Port Submissions       
 Component:  ports                         |     Version:  1.6.0                  
Resolution:  fixed                         |    Keywords:                         
      Port:  libpqxx                       |  
-------------------------------------------+--------------------------------

Comment(by ryandesign at macports.org):

 Replying to [comment:5 darren.weber.lists@…]:
 > the new Portfile [...] has lost the line with {{{distfiles
 ${distname}.tar.gz}}}; so I assume you removed that intentionally (along
 with the distfile name from the checksums)

 Yes, as Rainer said the default for `distfiles` is
 `${distname}$[extract.suffix}` so that wasn't necessary. Also it's not
 necessary to list the distfile name in the `checksums` statement unless
 you have more than one distfile.


 Replying to [comment:4 darren.weber.lists@…]:
 > How should I continue to work on the port?
 >
 > a) sync and then modify the Portfile within my own local repository, or
 > b) port edit libpqxx
 >
 > Should I use tickets to update the port with modifications?

 When you get commit access you can just commit your changes without filing
 tickets, but until then, you should file tickets for your modifications
 and attach diffs. How you generate those diffs is up to you.

 The docs will say to set up a local ports tree. Presumably the reason is
 so that if you make changes they won't get wiped out by the next "port
 sync", because the ports tree is usually synced via rsync which will wipe
 out local changes. However, I switched my ports tree to be a Subversion
 working copy. To update this, `port sync` just calls `svn update` which
 does not throw away local changes. This also makes it easy to get your
 differences to submit: instead of having to remember to make a copy of the
 Portfile before your changes (`cp -p Portfile Portfile.orig`) and then run
 a difference between them later (`diff -u Portfile.orig Portfile`), all
 you have to do is tell Subversion to give you the difference (`svn diff`).

 For more help, you should send a message to macports-dev; that's better
 than having the discussion in this ticket.

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


More information about the macports-tickets mailing list