Opened 13 years ago
Closed 13 years ago
#34343 closed defect (fixed)
dbus: uses startupitem.install, which fails on MacPorts < 2.1
| Reported by: | ryandesign (Ryan Carsten Schmidt) | Owned by: | pixilla (Bradley Giesbrecht) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.0.4 |
| Keywords: | Cc: | MarcusCalhoun-Lopez (Marcus Calhoun-Lopez), mkae (Marko Käning), kk1987@…, jeff.culat@…, machsna (J. ‘mach’ Wust), shawn@…, blair (Blair Zajac), an0nym@…, jean-philippe.humbert@… | |
| Port: | dbus |
Description
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]}
Change History (21)
comment:1 Changed 13 years ago by mkae (Marko Käning)
| Cc: | mk@… added |
|---|
comment:6 Changed 13 years ago by nerdling (Jeremy Lavergne)
| Priority: | High → Normal |
|---|
Commented out in r92741.
comment:7 Changed 13 years ago by 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?
comment:8 Changed 13 years ago by 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.)
comment:11 follow-up: 12 Changed 13 years ago by 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 {
comment:12 Changed 13 years ago by 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 {
comment:14 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)
comment:16 follow-up: 20 Changed 13 years ago by pixilla (Bradley Giesbrecht)
See r92760.
I installed MacPorts 2.0.4 and dbus installed with several variant combinations.
Please report success or failure. Thanks.
comment:20 Changed 13 years ago by pixilla (Bradley Giesbrecht)
comment:21 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
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.
Cc Me!