X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com Date: Mon, 27 Mar 2023 20:57:31 +0200 (CEST) From: Roland Lutz To: "Girvin Herr (gherrl2 AT fastmail DOT com) [via geda-user AT delorie DOT com]" Subject: Re: [geda-user] Changing gschem backup file permissions In-Reply-To: <4772851a-fca0-4370-d6bb-ef854127e604@fastmail.com> Message-ID: References: <4772851a-fca0-4370-d6bb-ef854127e604 AT fastmail DOT com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="8323329-142004255-1679943451=:1858" Reply-To: geda-user AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: geda-user AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --8323329-142004255-1679943451=:1858 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8BIT Hi Girvin, On Mon, 27 Mar 2023, Girvin Herr (gherrl2 AT fastmail DOT com) [via geda-user AT delorie DOT com] wrote: > Is there a way to change the gschem backup file permissions within > gschem to at least read/write for the owner (0644)? changing the backup file permissions is hard-coded in libgeda. You can disable this behavior by commenting out lines 413–416 in libgeda/src/f_basic.c and re-building gEDA/gaf: > if (chmod(backup_filename, mask) != 0) { > s_log_message (_("Could NOT set backup file [%s] readonly\n"), > backup_filename); > } Roland --8323329-142004255-1679943451=:1858--