[pacman-dev] Conf file mis-configuration by users

Travis Willard travis at archlinux.org
Fri Jan 11 15:23:23 EST 2008


On Jan 11, 2008 1:55 PM, Dan McGee <dpmcgee at gmail.com> wrote:
> On Jan 11, 2008 12:28 PM, Eric Belanger <belanger at astro.umontreal.ca> wrote:
> > On Fri, 11 Jan 2008, Xavier wrote:
> >
> > > Dan McGee wrote:
> > >>
> > >> We are not using a crazy config file. It is basically ini format,
> > >> which is quite standard, and I don't know a better way to go. All I
> > >> can say is adding a comment saying "# don't be a bonehead and
> > >> UNCOMMENT the [repo] headers!" or something.
> > >>
> > >
> > > Right, maybe a little comment would be enough.
> >
> > Maybe also having the comment before the [repo] line instead of after it
> > would help users noticing the [repo] header better.
> >
> >
> > >
> > >>
> > >> Comment is not a bad idea, although I just shake my head every time I
> > >> see these threads. Editors do have syntax highlighting too, which
> > >> makes this more obvious. I guess firing up the Gnome text editor as
> > >> root probably doesn't though. :)
> > >>
> > >
> > > Oh I see, that explains everything. I didn't notice previously, but
> > > syntax highlighting indeed helps a lot here. Probably that helped me
> > > never doing that mistake, and which is why I find it stupid.
> > > So besides the comment, we should also educate the users to use syntax
> > > highlighting, not using gnome text editor, and using sudo. Now there are
> > > probably many people that would object to these 3 advices, but well :D
>
> Travis- with this body of thoughts in mind, want to put together a
> patch for the current pacman.conf that may help improve things?

Yeah, sure, I'll jiggle it around a bit and see what falls out.
Thanks for the input guys.




More information about the pacman-dev mailing list