[MacPorts] #39616: Submission chemical-mime-data

MacPorts noreply at macports.org
Tue Jul 2 18:24:03 PDT 2013


#39616: Submission chemical-mime-data
---------------------------------+--------------------------
  Reporter:  c.herbig@…          |      Owner:  ryandesign@…
      Type:  submission          |     Status:  assigned
  Priority:  Normal              |  Milestone:
 Component:  ports               |    Version:  2.1.3
Resolution:                      |   Keywords:
      Port:  chemical-mime-data  |
---------------------------------+--------------------------

Comment (by c.herbig@…):

 Replying to [comment:3 ryandesign@…]:
 > I'm attaching a revised Portfile to fix the homepage, master_sites,
 adjust the formatting, and add "supported_archs noarch" because it does
 not install any architecture-specific files.
 >
 > Because the port is noarch, it does not link with any libraries, so it
 should not have any library dependencies. Are the listed library
 dependencies needed at build time, runtime or both?
 >
 > Activation fails:
 >
 > {{{
 > Error: org.macports.activate for port chemical-mime-data returned: Image
 error: /opt/local/share/mime/XMLnamespaces already exists and does not
 belong to a registered port.  Unable to activate port chemical-mime-data.
 Use 'port -f activate chemical-mime-data' to force the activation.
 > }}}
 >
 > In fact there are a dozen files it installs that are already on my
 system as a result of other installations. I added a post-destroot block
 to delete them but perhaps a post-activate step is required to update
 those files somehow.

 I'm looking through the configure script to see if I can figure this out
 again.  I'm still getting the following error:

 {{{
 :info:configure
 :info:configure checking for convert... no
 :info:configure checking for rsvg... no
 :info:configure configure: error: Cannot find rsvg (librsvg binary) or
 convert $
 :info:configure Command failed:  cd
 "/opt/local/var/macports/build/_opt_sly_mac$
 :info:configure Exit code: 1
 }}}

 ... and now I remember I fixed it by just caving and installing
 imagemagick.  There is another option:

 {{{
 --with-gnome-mime[=PATH]
                           enable, disable or override the installation
                           directory of the old GNOME 2.4 MIME support
 files
                           [default=$datadir/mime-info]
 }}}

 ... that might be key to it.  I'll try it.

-- 
Ticket URL: <https://trac.macports.org/ticket/39616#comment:4>
MacPorts <http://www.macports.org/>
Ports system for OS X


More information about the macports-tickets mailing list