#16990 closed submission (fixed)
new port: libpqxx26
Reported by: | dweber@… | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 1.6.0 |
Keywords: | libpqxx postgresql83 | Cc: | |
Port: | libpqxx26 |
Description
This is a version specific replacement for port:libpqxx. Since libpqxx was first submitted, there is a new version (3.0) in testing. To allow for multiple version installations, these ports for libpqxx will follow a similar naming convention to the postgresql ports that append the major and minor version numbers into the port name. Hence, we will soon have libpqxx26 and libpqxx30.
I now have commit rights for macports, but I have no information on how to exercise those rights. Can you point me to an introduction on how to svn my ports into the trunk? Or, would you prefer to have them submitted as tickets?
Thanks, Darren
PS, Can we remove the port:libpqxx? Or, can we make it an alias for the latest version of libpqxx (say libpqxx = libpqxx30)?
Attachments (2)
Change History (8)
Changed 16 years ago by dweber@…
comment:1 Changed 16 years ago by mf2k (Frank Schima)
You just need to checkout the svn tree. See this link and this one too. Then you modify your local copy and commit changes with svn.
Replying to dweber@…:
PS, Can we remove the port:libpqxx? Or, can we make it an alias for the latest version of libpqxx (say libpqxx = libpqxx30)?
I think libpqxx should always be the latest release version and create the older versions (e.g. libpqxx26) as needed for port dependencies. No need for libpqxx30 right now. I'm sure other opinions may vary.
comment:2 Changed 16 years ago by blb@…
Are 2.6 and 3.0 incompatible enough that both are needed? If so, is 2.6 only needed for older apps? Fortunately libpqxx doesn't appear to be a dependency for anything, so that part is easy. Renaming ports otherwise can be a bit of a mess due to what happens when people try things like upgrading it.
comment:3 Changed 16 years ago by dweber@…
There's a few changes to the Porfile, please use Portfile.2 attached.
The minor versions are compatible (ie, 2.6.? compatible, 3.0.? compatible), otherwise not.
I will adopt the strategy suggested (blb), so libpqxx will be updated to 3.0.0 and we can ignore the port:libpqxx30 for now (until something > 3.0.? is released). I created a ticket for libpqxx30, which could be dropped or used as you like. I will create another ticket to update libpqxx ASAP.
comment:4 Changed 16 years ago by jmroot (Joshua Root)
Resolution: | → fixed |
---|---|
Status: | new → closed |
This was added in r46122.
comment:5 Changed 16 years ago by jmroot (Joshua Root)
Type: | enhancement → submission |
---|
comment:6 Changed 16 years ago by (none)
Milestone: | Port Submissions |
---|
Milestone Port Submissions deleted
libpqxx26 Portfile