#22298 closed update (fixed)
Updated logtalk portfile for version 2.37.5
Reported by: | pmoura (Paulo Moura) | Owned by: | ryandesign (Ryan Carsten Schmidt) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | |
Keywords: | haspatch maintainer | Cc: | |
Port: | logtalk |
Description
Updated logtalk portfile for version 2.37.5
Attachments (1)
Change History (10)
comment:1 Changed 15 years ago by jmroot (Joshua Root)
Keywords: | haspatch maintainer added |
---|---|
Port: | logtalk added |
Version: | 1.8.1 |
comment:2 Changed 15 years ago by ryandesign (Ryan Carsten Schmidt)
Owner: | changed from macports-tickets@… to ryandesign@… |
---|---|
Status: | new → assigned |
comment:3 follow-up: 4 Changed 15 years ago by pmoura (Paulo Moura)
True, there is a dependency on the "shared-mime-info" port should be declared. I will upload an updated patch for the portfile shortly. However, there is also an issue in your testing machine as the error message says that "/opt/local/share/mime/aliases already exists and does not belong to a registered port." Installing the "shared-mime-info" port using MacPorts should clear the error. Logtalk is only touching the "/opt/local/share/mime" because is calling the "update-mime-database" command.
comment:4 Changed 15 years ago by ryandesign (Ryan Carsten Schmidt)
Replying to pmoura@…:
However, there is also an issue in your testing machine as the error message says that "/opt/local/share/mime/aliases already exists and does not belong to a registered port." Installing the "shared-mime-info" port using MacPorts should clear the error.
Well, no, shared-mime-info is already installed, and reinstalling it changes nothing. The stuff in /opt/local/share/mime is installed by but not registered to the shared-mime-info port. I filed this as a bug, but Anthony (who changed the port to behave that way in r33238) said the behavior is intentional.
Logtalk is only touching the "/opt/local/share/mime" because is calling the "update-mime-database" command.
Ok. I'm not familiar with how the MIME database is supposed to function, how updates to that are meant to work. If you can figure it out, great; if not, try asking Anthony or another committer who updated shared-mime-info in the past.
comment:5 Changed 15 years ago by pmoura (Paulo Moura)
I use the "update-mime-database" command as advised by the freedesktop.org developers. Thus, now that the dependency is declared in the Logtalk portfile, all should be fine (famous last words ;-). Thanks for your support. Please let me know if any other issue arises when testing the portfile.
comment:6 Changed 15 years ago by pmoura (Paulo Moura)
The error "/opt/local/share/mime/aliases already exists and does not belong to a registered port." still occurs with the latest patch I uploaded. Still looking for a solution.
Changed 15 years ago by pmoura (Paulo Moura)
Attachment: | Portfile-logtalk.diff added |
---|
comment:7 Changed 15 years ago by pmoura (Paulo Moura)
Just uploaded a new patch that eliminates the error.
comment:8 Changed 15 years ago by ryandesign (Ryan Carsten Schmidt)
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
logtalk @2.37.3_0 installs fine, but @2.37.5_0 has this complaint:
logtalk @2.37.3_0 seems not to have tried to install anything in /opt/local/share/mime, but @2.37.5_0 does. That directory is already provided by the shared-mime-info port (though for reasons explained (?) in #21093 the files are not registered to the port).
So, the logtalk port should now either inform the logtalk build process not to install ${destroot}${prefix}/share/mime, or if there is no way to tell it not to do that, should delete ${destroot}${prefix}/share/mime in the post-destroot phase. If logtalk really requires those files, then a dependency on the shared-mime-info port should be declared.