Opened 10 years ago
Closed 10 years ago
#44897 closed defect (fixed)
tao @ 6.2.6 Problem installing pre-built binary
Reported by: | lockhart (Thomas Lockhart) | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.3.1 |
Keywords: | haspatch maintainer | Cc: | |
Port: | tao |
Description
It is great to see pre-built binaries for the tao port. However, the .plist file for starting the daemon is not found since it apparently is looking for it in the build directory. The workaround is to install from source using "port install -s tao". Details below. I'll work on a patch for this but marked this as "haspatch" since a patch is coming and I can't change that field later.
---> Fetching archive for tao ---> Attempting to fetch tao-6.2.6_0+server.darwin_13.x86_64.tbz2 from http://packages.macports.org/tao ---> Attempting to fetch tao-6.2.6_0+server.darwin_13.x86_64.tbz2.rmd160 from http://packages.macports.org/tao ---> Installing tao @6.2.6_0+server Error: org.macports.install for port tao returned: error copying "/opt/local/var/macports/build/_opt_local_var_macports_sources_svn.macports.org_trunk_dports_devel_tao/tao/work/ACE_wrappers/org.macports.tao_cosnaming.plist": no such file or directory Please see the log file for port tao for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_svn.macports.org_trunk_dports_devel_tao/tao/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port tao failed
Attachments (1)
Change History (5)
comment:1 follow-up: 2 Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)
comment:2 follow-up: 3 Changed 10 years ago by lockhart (Thomas Lockhart)
Replying to ryandesign@…:
Replying to tlockhart1976@…:
I'll work on a patch for this but marked this as "haspatch" since a patch is coming and I can't change that field later.
Have you had a chance to work on this patch?
Looking at it now. It seems to be simple, but it is not clear from other Portfile examples where the preferred location of the .plist file is. I see /Library/LaunchDaemons/, /opt/local/etc/LaunchDaemons/, /opt/local/Library/LaunchDaemons/, and /System/Library/LaunchDaemons/ in various portfiles. So which is it??
comment:3 Changed 10 years ago by lockhart (Thomas Lockhart)
Replying to tlockhart1976@…:
Replying to ryandesign@…:
Replying to tlockhart1976@…:
I'll work on a patch for this but marked this as "haspatch" since a patch is coming and I can't change that field later.
Have you had a chance to work on this patch?
Looking at it now. It seems to be simple, but it is not clear from other Portfile examples where the preferred location of the .plist file is. I see /Library/LaunchDaemons/, /opt/local/etc/LaunchDaemons/, /opt/local/Library/LaunchDaemons/, and /System/Library/LaunchDaemons/ in various portfiles. So which is it??
I'm going with /opt/local/etc/LaunchDaemons/ for now since that was used in the original Portfile. If the path is changed then the Portfile will need some special-case checks for the other location. Let me know if this path is not preferred.
Changed 10 years ago by lockhart (Thomas Lockhart)
Attachment: | Portfile.diff added |
---|
Install server startup script from port contents rather than from worksrcpath. This should fix the problem with installing from a pre-built binary.
comment:4 Changed 10 years ago by pixilla (Bradley Giesbrecht)
Resolution: | → fixed |
---|---|
Status: | new → closed |
See r128303
Replying to tlockhart1976@…:
Have you had a chance to work on this patch?