[pacman-dev] config handling

Роман Кирилич roman.kyrylych at gmail.com
Fri May 26 19:24:01 EDT 2006


I just found your first post. How could I miss it?
Thank you for patch. It does exactly what I meant.

2006/5/27, Роман Кирилич <roman.kyrylych at gmail.com>:
> Current behaviour seems fine to me too. All I said is just for
> clarification of how it should be so no changes in this behaviour
> should be made
> (e.g. NoUpgrade functionality should not be removed, and other files
> (not config files) shouldn't be added to backup array).
>
> 2006/5/27, Xavier Chantry <x.chantry at wanadoo.fr>:
> > On Sat, May 27, 2006 at 12:40:02AM +0300, ????? ??????? wrote:
> > > When file is in NoUpgrade list Pacman should do it's XYZ logic with
> > > one important change - it should NEVER overwrite any file listed in
> > > NoUpgrade.
> >
> > That's what I did.
> >
> > > By default there should be NO NoUpgrade list in pacman.conf.
> > > There is no point to include any _config_ file in NoUpgrade, _only
> > > modified system shell scripts_ should be included there (for some rare
> > > cases when user modifies them).
> >
> > I agree.
> >
> > > When package that owns file listed in NoUpgrade is removed - this file
> > > should be saved as .pacsave.
> >
> > Yep, but I was asking about the current pacman behavior,
> > since I couldn't try it.
> > Having a second look at the code, it finally seems it's already
> > what happens, so it's fine.
> >
> >
> > _______________________________________________
> > pacman-dev mailing list
> > pacman-dev at archlinux.org
> > http://www.archlinux.org/mailman/listinfo/pacman-dev
> >
>


More information about the pacman-dev mailing list