dbus-python34, dbus-python35: fails to parse if corresponding python port is not installed

[ryandesign (Ryan Carsten Schmidt)]

The dbus-python34 and dbus-python35 subports fail to parse if corresponding python port is not installed:

sent 64 bytes  received 117 bytes  120.67 bytes/sec
total size is 512  speedup is 2.83
Creating port index in /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports
Warning: failed to open old entry for devel/dbus-python, making a new one
Adding port devel/dbus-python
Adding subport dbus-python27
Adding subport dbus-python34
Failed to parse file devel/dbus-python/Portfile with subport 'dbus-python35': couldn't execute "/opt/local/bin/python3.5-config": no such file or directory
Adding subport dbus-python24
Adding subport dbus-python25
Adding subport dbus-python26
Adding subport dbus-python31
Adding subport dbus-python32
Adding subport dbus-python33

Total number of ports parsed:	10 
Ports successfully parsed:	9 
Ports failed:			1 
Up-to-date ports skipped:	24823

This may be what is killing the portindex (#49179).

[MarcusCalhoun-Lopez (Marcus Calhoun-Lopez)]

The change was introduced in r140992.
Hopefully, r141026 fixes the problem.

[jmroot (Joshua Root)]

Why not find out the abiflags and append to configure.args in a pre-configure block?

[jmroot (Joshua Root)]

The parse failure is fixed in any case.

[michaelld (Michael Dickens)]

Replying to jmr@…:

Why not find out the abiflags and append to configure.args in a pre-configure block?

That's what I ended up doing, in r141038. Took a little effort because the variables defined outside the "subport" scope are no longer valid inside the "pre-configure" scope. Had to define them in the "subport" scope & then use in the "pre-configure" scope. Gotta love TCL!

[michaelld (Michael Dickens)]

Cc Me!