dbus: uses startupitem.install, which fails on MacPorts < 2.1

[ryandesign (Ryan Carsten Schmidt)]

As of r92726 the dbus port already uses the startupitem.install keyword, which does not exist before MacPorts 2.1, therefore, as ​reported on the mailing list, users of MacPorts < 2.1 encounter an error when trying to use this port, for example:

$ port info dbus
Error: Unable to open port: can't read "startupitem.install": no such variable

If you want to use startupitem.install in the port already, you need to preface any usage of that variable with something like the following so that MacPorts 2.0.x won't fail:

if {[info exists startupitem.install]}

[mkae (Marko Käning)]

Cc Me!

[kk1987@…]

Cc Me!

[jeff.culat@…]

Cc Me!

[machsna (J. ‘mach’ Wust)]

Cc Me!

[shawn@…]

Cc Me!

[nerdling (Jeremy Lavergne)]

Commented out in r92741.

[shawn@…]

So a fix has been committed, how long does it take before it propagates out to users? Is there a way we can force it? Is there a downside to applying the fix manually?

[mkae (Marko Käning)]

Try for now simply this:

sudo port upgrade dbus +no_startupitem

This might solve the issue for now without any patches... (Depending on your installation, of course.)

[jeff.culat@…]

It works for me. Thanks

[shawn@…]

That workaround also resolves it for me. Thanks!

[pixilla (Bradley Giesbrecht)]

Ryan: Would a test/set before the first use of startupitem.install be a good solution?

+# The startupitem.install keyword does not exist in MacPorts < 2.1.
+if {![info exists ${startupitem.install}]} {
+    set startupitem.install yes
+}
pre-configure {

[pixilla (Bradley Giesbrecht)]

Correction

+# The startupitem.install keyword does not exist in MacPorts < 2.1.
+if {![info exists startupitem.install]} {
+    set startupitem.install yes
+}
pre-configure {

[pixilla (Bradley Giesbrecht)]

Has duplicate #34349

[ryandesign (Ryan Carsten Schmidt)]

Replying to pixilla@…:

Has duplicate #34349

Really? That looks like a different error message.

#34348 is a duplicate, though.

Yes, setting startupitem.install to a default value would be fine.

[blair (Blair Zajac)]

Cc Me!

[pixilla (Bradley Giesbrecht)]

See r92760.

I installed MacPorts 2.0.4 and dbus installed with several variant combinations.

Please report success or failure. Thanks.

[an0nym@…]

Cc Me!

[jean-philippe.humbert@…]

Cc Me!

[ryandesign (Ryan Carsten Schmidt)]

Has duplicate #34360.

[pixilla (Bradley Giesbrecht)]

Replying to pixilla@…:

See r92760.

I installed MacPorts 2.0.4 and dbus installed with several variant combinations.

Please report success or failure. Thanks.

Any feedback? r92760 should fix this.

[ryandesign (Ryan Carsten Schmidt)]

dbus no longer uses startupitem.install when it's not defined, which is what I filed this ticket about. I verified the port builds fine with MacPorts 2.0.4 and 2.1 beta 1, so I'm calling it resolved.

There is a remaining issue for users using the binary; see #34349.