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 649054 - Allow a command line argument to disable the cache
Allow a command line argument to disable the cache
Status: RESOLVED FIXED
Product: gobject-introspection
Classification: Platform
Component: general
unspecified
Other Mac OS
: Normal normal
: ---
Assigned To: gobject-introspection Maintainer(s)
gobject-introspection Maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2011-05-01 00:14 UTC by Jeremy Huddleston
Modified: 2015-02-07 16:55 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Add GI_SCANNER_DISABLE_CACHE environment variable (1.41 KB, patch)
2011-05-02 16:26 UTC, Colin Walters 		committed Details | Review

Description Jeremy Huddleston 2011-05-01 00:14:55 UTC 
There does not seem to be an option to disable caching with g-ir-scanner.  Please provide such an option, so we can properly build gnome within MacPorts which disables writing to $HOME during the build process:

https://trac.macports.org/ticket/26783
Comment 1 Colin Walters 2011-05-02 16:20:05 UTC 
What would work best for you here?  You probably want an environment variable, since a commandline argument would have to be hacked into projects' makefiles, correct?
Comment 2 Colin Walters 2011-05-02 16:26:53 UTC 
Created attachment 187051 [details] [review]
Add GI_SCANNER_DISABLE_CACHE environment variable
Comment 3 Jeremy Huddleston 2011-05-02 17:50:40 UTC 
Yep, that would work great for us.  Thanks.
Comment 4 Colin Walters 2011-05-04 18:57:03 UTC 
Attachment 187051 [details] pushed as 2330248 - Add GI_SCANNER_DISABLE_CACHE environment variable
Comment 5 ulrik sverdrup 2011-05-08 23:05:14 UTC 
A build tool should not write files outside its working directory or at least outside the top source directory. Using a $HOME-based cache is the wrong default except maybe for the gobject-introspection hackers themselves. Distributions will surely not like this (clean/reproducible builds). Is it not possible to implement a cache in the working directory instead?

Compare for example with intltool-update (uses cache in working directory).
Comment 6 Leo Singer 2011-05-08 23:31:42 UTC 
Or the cache could even be disabled by default.
Comment 7 André Klapper 2015-02-07 16:55:40 UTC 
[Mass-moving gobject-introspection tickets to its own Bugzilla product - see bug 708029. Mass-filter your bugmail for this message: introspection20150207 ]