11 Jan
2008
11 Jan
'08
4:44 p.m.
Dan McGee wrote:
Step back for a second and look at it this way. With any package, we normally install our own conf file if the out-of-box one is not usable or does not have sane defaults for Arch Linux. Pacman should be no different.
Having a pacman.conf in CVS is absolutely fine, and this wouldn't require a whole new release of pacman just to satisfy the addition or removal of repositories. There should be *no* Arch Linux specifics in the code that are not reasonable defaults for everyone.
Ok, I don't know why, I didn't understand what putting it in CVS meant in the beginning. I get it now, and it looks fine to me.