After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 627126 - gsettings schema files don't get installed on FreeBSD
gsettings schema files don't get installed on FreeBSD
Status: RESOLVED FIXED
Product: glib
Classification: Platform
Component: gsettings
2.25.x
Other FreeBSD
: Normal normal
: ---
Assigned To: Allison Karlitskaya (desrt)
gtkdev
Depends on:
Blocks:
 
 
Reported: 2010-08-17 10:33 UTC by Koop Mast (kwm)
Modified: 2010-10-04 07:07 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
tweak sed expression to work with our non gnu sed. (578 bytes, patch)
2010-08-17 10:34 UTC, Koop Mast (kwm) 		none Details | Review

Description Koop Mast (kwm) 2010-08-17 10:33:17 UTC 
On freebsd the gsetting schema files don't get installed because our sed doesn't get the sed expression in gsettings__base_list.
Comment 1 Koop Mast (kwm) 2010-08-17 10:34:06 UTC 
Created attachment 168044 [details] [review]
tweak sed expression to work with our non gnu sed.
Comment 2 Antoine Jacoutot 2010-09-28 09:20:41 UTC 
We see the same issue on OpenBSD and I confirm this patch allows installing gsetting schema files.
Comment 3 Allison Karlitskaya (desrt) 2010-10-04 05:53:55 UTC 
I just did this commit:

commit 136e705e8383ff8848e425ac01278102d7badc52
Author: Ryan Lortie <desrt@desrt.ca>
Date:   Mon Oct 4 01:51:11 2010 -0400

    Bug 627126 - gsettings schemas on FreeBSD
    
    Rewrite the install rule for GSettings schemas to not depend on an
    obscure chunk of non-portable sed that nobody understands the purpose
    of.
    
    Instead, use make's VPATH feature to resolve the paths of the files that
    need to be installed.  No need to depend on the .valid targets here
    since automake already ensures that 'make all' is complete before 'make
    install' is permitted to run.



Can you guys verify that it worked out on BSD and reopen this bug if it didn't?
Comment 4 Antoine Jacoutot 2010-10-04 06:13:07 UTC 
(In reply to comment #3)
> Can you guys verify that it worked out on BSD and reopen this bug if it didn't?

I does the job for me on OpenBSD, thanks.
Comment 5 Koop Mast (kwm) 2010-10-04 07:07:19 UTC 
Also works for me on FreeBSD, thanks.