libgsf-1.14.22 and configure option --disable-schemas-install

[ballapete (Peter "Pete" Dyballa)]

When building this package on PPC Mac OS X 10.5.8 I see:

--->  Extracting libgsf
--->  Extracting libgsf-1.14.22.tar.xz
--->  Configuring libgsf
configure: WARNING: unrecognized options: --disable-schemas-install

In the end a zillion of schema files is installed!

[ryandesign (Ryan Carsten Schmidt)]

There appear to be two separate issues that you're talking about.

Replying to Peter_Dyballa@…:

When building this package on PPC Mac OS X 10.5.8 I see:

--->  Extracting libgsf
--->  Extracting libgsf-1.14.22.tar.xz
--->  Configuring libgsf
configure: WARNING: unrecognized options: --disable-schemas-install

This is the first issue: the port uses the configure option --disable-schemas-install which is unknown and therefore has no effect. We could therefore remove this option. (I checked ./configure --help and did not see any similar option. It probably used to exist and was removed by the developers at some point and we didn't notice.)

In the end a zillion of schema files is installed!

This is the second issue: the port has a post-activate block which uses gconftool-2 to install and register the schema files:

post-activate {
    if {![variant_isset no_gnome]} {
        system "\
            export GCONF_CONFIG_SOURCE=`gconftool-2 --get-default-source` && \
            gconftool-2 --makefile-install-rule \
            ${prefix}/etc/gconf/schemas/*.schemas"
    }
}

I don't know what these schema files are for, but the fact that there's a block of code in the portfile doing this suggests it's deliberate. On further examination, I see the block was added almost 4 years ago in r41441 for #14729. If you're suggesting we remove that block of code, then I'd want to understand what the schemas are and why it would be ok to not have them or not register them in the way that #14729 says they should be registered.

[ballapete (Peter "Pete" Dyballa)]

I can't suggest removing them because I don't know what they're good for. I mentioned this behaviour from the failing configure option "--disable-schemas-install" from which I concluded that they were not installed (and necessary?) on Mac OS X.

[ryandesign (Ryan Carsten Schmidt)]

I removed the --disable-schemas-install configure arg in r97632.