Re: pkg/44400: (print/ghostscript) The necessity of --disable-compile-inits parameter

[Makoto Fujiwara <makoto%ki.nu@localhost>]

The following reply was made to PR pkg/44400; it has been noted by GNATS.

From: Makoto Fujiwara <makoto%ki.nu@localhost>
To: Matthias Drochner <M.Drochner%fz-juelich.de@localhost>
Cc: gnats-bugs%NetBSD.org@localhost
Subject: Re: pkg/44400: (print/ghostscript) The necessity of  
--disable-compile-inits parameter
Date: Mon, 17 Jan 2011 21:39:36 +0900

 | To: pkg-manager%NetBSD.org@localhost, gnats-admin%NetBSD.org@localhost,
  pkgsrc-bugs%NetBSD.org@localhost, makoto%ki.nu@localhost
 | From: Matthias Drochner <M.Drochner%fz-juelich.de@localhost>
 | Subject: Re: pkg/44400: (print/ghostscript) The necessity of  
--disable-compile-inits parameter
 | Date: Mon, 17 Jan 2011 11:45:03 +0000 (UTC)
 | Message-ID: <20110117114503.1255F63B883%www.NetBSD.org@localhost>
  
 Matthias>  Can't you just set the GS_LIB environment variable, using
 Matthias>  a wrapper or your .profile, to have your initialization files
 Matthias>  found before the %rom% version?
 
   Thank you for the response. Sorry not to mention the GS_LIB
 variable setting. Yes I did try the similar thing. But I did
 not feel it was enough for comfortable setup for pkgsrc machine.
 
   Honestly speaking, this is my first step for ghostscript with
 CJK environment. I am planning to have another package to add
 CJK setup, providing TTF font(s) installation and cidfmap setting.
 To have (some kind of) fixed cidfmap location may be important.
 
  Also, giving an option to ghostscript does not add any burden
 to package (except a few lines of coding in options.mk) and even
 get smaller binaries with --disable-compile-inits.
 
 Thank a lot,
 ---
 Makoto Fujiwara