Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <3D46B5AE.469F6634@yahoo.com>
Date: Tue, 30 Jul 2002 11:50:06 -0400
From: Earnie Boyd <earnie_boyd AT yahoo DOT com>
Reply-To: cygwin-apps AT cygwin DOT com
X-Accept-Language: en
MIME-Version: 1.0
To: John Morrison <john DOT r DOT morrison AT ntlworld DOT com>
CC: cygwin-apps AT cygwin DOT com, Cygwin <cygwin AT cygwin DOT com>
Subject: Re: Skel files
References: <NCEBJJFMCAOKNNABBFIMMEHICEAA DOT john DOT r DOT morrison AT ntlworld DOT com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

John Morrison wrote:
> 
> > From: Earnie Boyd [mailto:earnie_boyd AT yahoo DOT 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.
> 

Maybe both.

> > > .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! :)
> 

You can create the /profile/skel for these and the package could copy if
they exist or provide it's own default.

> > > .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.
> 

Examples are fine.  Forcing the user to have them would be a pain, IMO. 
It complicates the install process beyond what is needed.  These files
are for the user to modify there environment to their specific need, not
what someone else dreams up as a standard user environment.  The
standard environment should only be controlled by the /etc/profile, etc.
files.

Yes, you could argue that about the other files as well.  However, the
other files aren't as common and are more tool specific rather than
environment specific.

Earnie

--
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/