X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=0.1 required=5.0 tests=AWL,BAYES_50,FROM_LOCAL_NOVOWEL,HK_RANDOM_FROM,RP_MATCHES_RCVD,SPF_HELO_PASS X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: "Sebastien Vauban" Subject: Re: Portable shell code between Cygwin and Linux Date: Mon, 01 Aug 2011 08:40:52 +0200 Lines: 19 Message-ID: <80mxftljm3.fsf@somewhere.org> References: <80hb65b3ue DOT fsf AT somewhere DOT org> <4E330E40 DOT 6080606 AT cs DOT umass DOT edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Url: Under construction... X-Archive: encrypt User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1.50 (windows-nt) X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Hi Eliot, Eliot Moss wrote: > Another way to be portable is to have per-system files to set up some > environment variables and then uniform portable files that use them. You can > do that same thing *within* a file by writing conditionals or a case on the > result of uname. It's probably best to segregate per-system stuff in a > well-contained file or section of a file in this way ... Thanks for your answer. But the whole idea is to write something in a way that it must not be rewritten for the other system. Maybe it's just a dream. Best regards, Seb -- Sebastien Vauban -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple