Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com From: "Gary R Van Sickle" To: "Cygwin Mailing List (E-mail)" Subject: Re: [ANNOUNCEMENT] Updated: mutt-1.2.5i-5 Date: Tue, 2 Oct 2001 11:34:46 -0500 Message-ID: <000b01c14b60$25ff3370$2101a8c0@nomad> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0) X-Mimeole: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal > There is provision for post-isntall scripts, but I suggest a simpler > approach of jsut installing /etc/muttrc.default. Then the users config > is never overwritten, and a clean config is awlays available for > reference. > > Rob The problem I see there is that first-time installers then wouldn't have an /etc/muttrc at all until they happened to stumble across the muttrc.default. I could probably pretty easily set things up so that an /etc/muttrc.default gets installed, and then have a post-install script copy it to /etc/muttrc if and ony if it doesn't already exist. How does the post-install script functionality work? Can you point me to some docs or other explanation? Gary R. Van Sickle Braemar Inc. 11481 Rupp Dr. Burnsville, MN 55337 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/