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
X-Authentication-Warning: slinky.cs.nyu.edu: pechtcha owned process doing -bs
Date: Tue, 30 Jul 2002 14:10:17 -0400 (EDT)
From: Igor Pechtchanski <pechtcha AT cs DOT nyu DOT edu>
Reply-To: cygwin-apps AT cygwin DOT com
To: cygwin-apps AT cygwin DOT com
cc: cygwin AT cygwin DOT com
Subject: Re: Skel files
In-Reply-To: <3D46B5AE.469F6634@yahoo.com>
Message-ID: <Pine.GSO.4.44.0207301357130.8745-100000@slinky.cs.nyu.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Tue, 30 Jul 2002, Earnie Boyd wrote:

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

This would mean overwriting the file, so a comment inside to that regard
may be in order.

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

How about a comment in /etc/profile about using .bashrc to change
individual settings?

> 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

An example .inputrc outside of the home directory would actually be
useful.

Another approach would be to leave all commands in the shell config files
commented out, with notes describing them and saying to uncomment them to
enable that particular functionality.
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha AT cs DOT nyu DOT edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor AT watson DOT ibm DOT com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

It took the computational power of three Commodore 64s to fly to the moon.
It takes a 486 to run Windows 95.  Something is wrong here. -- SC sig file


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