Re: Package configuration philosophy
On Wed, 26 Feb 1997, Jason Gunthorpe wrote:
> On Wed, 26 Feb 1997, Scott Stanley wrote:
>
> > On Wed, 26 Feb 1997, Jason Gunthorpe wrote:
> >
> > > On Thu, 27 Feb 1997, Craig Sanders wrote:
> > >
> > > I wonder if it would be possible to make a package that included a good
> > > degree of the typical customizations? I have setup 3 debian machines right
> > > from the ftp server in the past month and there are things I change right
> > > off the bat, the prompt is one, the .inputrc (to include home/end keys)
> > > some of the aliases, enable color ls etc
> >
> > The problem with this is that the defaults the package developer likes are
> > unlikely to conform to the particular taste of every user. This sounds
> > like a good option for an individual to create for their particular
> > needs. Might be a neat idea... It would certainly speed the process up
> > when doing installations on multiple machines.
>
> This is true, but the installation of the package is up to the Debian
> user, it's not forced, there could even be multiple conflicting packages
> with conflicting UI styles :> Encourage a 'learn by example' type of
> approach.
Several conflicting packages might work... But it is easy to install a
package and still not learn anything about how these defaults are actually
set up (or what files were even added to the system for that matter.)
This would significantly speed up setting up a system, but will only
promote learning if the changes are brought to the installers attention.
If an explanation of how the defaults were set was placed in /usr/doc as
part of the package, this might be work (I am sure there is a good way to
find out what files are included in a package without this documentation,
but that brings another variable into the learning curve....)
Scott
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-user-REQUEST@lists.debian.org . Trouble? e-mail to Bruce@Pixar.com
Reply to: