Opened 12 years ago

Closed 12 years ago

Last modified 12 years ago

#15411 closed enhancement (fixed)

Python bsddb/subversion-python25bindings module updates

Reported by: danielluke (Daniel J. Luke) Owned by: danielluke (Daniel J. Luke)
Priority: Normal Milestone:
Component: ports Version: 1.6.0
Keywords: Cc: mww@…, blair (Blair Zajac)
Port:

Description

I would like to get apr-util/subversion (along with the subversion-bindings ports) updated to use db46 instead of db44.

The python bsddb modules should probably also be updated at the same time.

I've tested the py25-bsddb version but not the others.

I would like to coordinate the commit of this as much as possible.

If it's OK with you, I'll commit the update along with the apr-util/subversion/subversion-bindings ports.

Attachments (2)

subversion-python25bindings.diff (1.5 KB) - added by danielluke (Daniel J. Luke) 12 years ago.
updates for the subversion-python24bindings port
python-bsddb-updates.diff (2.4 KB) - added by danielluke (Daniel J. Luke) 12 years ago.

Download all attachments as: .zip

Change History (9)

Changed 12 years ago by danielluke (Daniel J. Luke)

updates for the subversion-python24bindings port

comment:1 Changed 12 years ago by danielluke (Daniel J. Luke)

Summary: Python bsddb module updatesPython bsddb/subversion-python25bindings module updates

comment:2 Changed 12 years ago by danielluke (Daniel J. Luke)

Status: newassigned

Changed 12 years ago by danielluke (Daniel J. Luke)

Attachment: python-bsddb-updates.diff added

comment:3 Changed 12 years ago by danielluke (Daniel J. Luke)

The bsddb ports would need incremented revision, of course... I've added that to the attached diff.

comment:4 Changed 12 years ago by blair (Blair Zajac)

I would like to see all these ports use variants, +db44, +db45 and +db46.

You never know when some other program that has some dependency on a particular BDB version and wants to use APR and we're on 4.6.

Say foopackage comes out with dependencies on 4.7 for some new feature and we need to recompile. Also, foopackage also links against apr. With the no-variant approach, you'd have to edit all your files to get this to work and the next sync would destroy those.

Maybe putting a bdb version in etc/macports somewhere as a the default would be nice.

comment:5 Changed 12 years ago by danielluke (Daniel J. Luke)

Since ports can't depend on variants on other ports (and may never be able to), I don't know that that's a workable end-state.

We'll probably need a 'default' bdb version (which would be 4.6 now and maybe 4.7 if someone makes a port for it).

It might make sense to add variants that change things to depend on the older bdb versions, but I wouldn't bother adding (and testing) them unless there actually ends up being demand for it.

I don't think a global macports conf setting for the version of a single project is a good idea. Of course, if the variants are named consistently, someone could set up default variants to get the behavior you want.

So, in summary, I would like to make the change I've proposed here (which just updates the current state of things to use a newer bdb) and if you'd like to write variants for the other bdb versions, I wouldn't be opposed to adding them.

comment:6 Changed 12 years ago by danielluke (Daniel J. Luke)

Resolution: fixed
Status: assignedclosed

committed in r37636 and r37637

comment:7 Changed 12 years ago by (none)

Milestone: Port Enhancements

Milestone Port Enhancements deleted

Note: See TracTickets for help on using tickets.