Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com From: "John Morrison" To: Cc: "Cygwin" Subject: RE: Skel files Date: Tue, 30 Jul 2002 14:56:02 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal In-Reply-To: <3D468616.EB96C019@yahoo.com> > From: Earnie Boyd [mailto:earnie_boyd@yahoo.com] Thanks Earnie, response is welcome :) > John Morrison wrote: > > > > Some of the files I have on my system which I believe could > > have defaults... > > > > .xinit Yes - But should be copied only by the > X11 package or perhaps RXVT. By copied I take it you mean packaged as part of a tar? I agree, personally, I'd choose X11. > > .xserverrc Yes - But should be copied only by the > X11 package needing it Agreed. > > .pinerc Yes - But should be copied only by the > PINE package Agreed. > > .vimrc Yes - But should be copied only by the > VIM package Agreed. I'm attempting (with this mail) to raise the profile (if you'll forgive the pun) of the skel capabilities. I _definitely_ want them to be part of the appropriate package! :) > > .bashrc No > > .bash_profile No > > .inputrc No > > .login No > > .logout No Why no? Not even comments and example usage? I (as a *nix newbie) didn't know these files existed, uses of or anything for ages. I found them out either by accident or by viewing somebody elses system. Even just a place holder with a comment as to what the file is for I would have considered useful. J. PS, what do you think about packaging up profile (removing that functionality from the setup app)? What about doing the same with the group/passwd script? Should that be another package? -- 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/