From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,7624df5e57d09688 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2002-06-10 05:36:01 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!headwall.stanford.edu!newsfeed-west.nntpserver.com!hub1.meganetnews.com!nntpserver.com!news-xfer.siscom.net!nntp2.aus1.giganews.com!nntp.giganews.com!nntp3.aus1.giganews.com!bin6.nnrp.aus1.giganews.com.POSTED!not-for-mail Sender: Stephe@TAKVER Newsgroups: comp.lang.ada Subject: Re: config files proposal References: <3CFA8E42.B7844253@san.rr.com> <3CFAEEB5.CE3041C2@san.rr.com> <3D03DE18.9031B0F5@san.rr.com> From: Stephen Leake Message-ID: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-GC-Trace: gv1-XEtzqAcdzvZSw9Tgj+uxQfqlk9ZdqEjIFpedGc= NNTP-Posting-Date: Mon, 10 Jun 2002 07:35:45 CDT Organization: Giganews.Com - Premium News Outsourcing X-Trace: sv3-fQ6uRtX/fy4dYd8nbySliqEiJi0RiJGFBI6Gwf8lS+VA5U7CBN2O6U6E8ZV41HR0ObyMue9KY8mtkUe!txgjVdX5m7zAxTQhVUG6on6MlBPFBvICvhN+8cyg8zYZE1iTBeV7ndU= X-Complaints-To: abuse@comcast.com X-DMCA-Complaints-To: dmca@comcast.net X-Abuse-Info: Please be sure to forward a copy of ALL headers X-Abuse-Info: Otherwise we will be unable to process your complaint properly Date: Mon, 10 Jun 2002 12:35:45 GMT Xref: archiver1.google.com comp.lang.ada:25663 Date: 2002-06-10T12:35:45+00:00 List-Id: Darren New writes: > Stephen Leake wrote: > > Good point. I guess I can check the write privs on the found file. > > Naw. Hmm. What if I find a "system" config file, that I _don't_ have write priviledge for? > > Or provide two search paths; one read-only and one writeable. > > Or just require the full path to the config to be saved, and perhaps default > it to where it was loaded from. I think if you try to "guess" which config > file to clobber, you're going to guess wrong too often. With clear rules about it, there's no "guessing". Here's my proposed rule: --- There are two search paths; one for files that are read only, one for files that are writeable. If the first config file is found on a read only path, the "flush" operation creates a new file in the first directory of the writeable path. --- That gives total control to the client of the Config_Files package. -- -- Stephe