I've included a patch to clean up pacman.conf a bit and move the instructions it provides at the top to a more applicable position in the file.
I removed most of the NoUpgrade lines in the file because all of these files are already protected by their respective packages (at least in Arch, and I would assume in Frugal as well).
I also moved the comment about reordering the mirrors to right above where the server lists are specified. I removed the reference to sortmirrors for two reasons- it isn't in the current pacman CVS, and I am working on a script that may do the job slightly better and not delete mirrors as the current script does (Flyspray #2952). It is based off the script noted in the bug report that was posted in the forums.
Dan
--- pacman-lib.orig/etc/pacman.conf.in 2006-11-15 15:22:46.000000000 -0500 +++ pacman-lib/etc/pacman.conf.in 2006-12-05 18:06:23.000000000 -0500 @@ -1,16 +1,6 @@ # # /etc/pacman.conf # -# NOTE: If you find a mirror that is geographically close to you, please -# move it to the top of the server list, so pacman will choose it -# first. -# -# To re-sort your mirror lists by ping/traceroute results, use the -# /usr/bin/sortmirrors.pl script. It requires the "netselect" package. -# -# # sortmirrors.pl </etc/pacman.conf >pacman.conf.new -# - # See the pacman manpage for option directives
# @@ -18,42 +8,40 @@ # [options] LogFile = /var/log/pacman.log -NoUpgrade = etc/passwd etc/group etc/shadow etc/sudoers -NoUpgrade = etc/fstab etc/raidtab etc/mdadm.conf etc/ld.so.conf -NoUpgrade = etc/inittab etc/rc.conf etc/rc.local -NoUpgrade = etc/modprobe.conf etc/modules.conf -NoUpgrade = etc/lilo.conf boot/grub/menu.lst etc/mkinitrd.conf HoldPkg = pacman glibc #XferCommand = /usr/bin/wget --passive-ftp -c -O %o %u
# # REPOSITORIES # - can be defined here or included from another file -# - pacman will search repositories in the order defined here. +# - pacman will search repositories in the order defined here # - local/custom mirrors can be added here or in separate files -# +# - to add a preferred server, place it before an Include directive or first +# in the included file +# +# NOTE: If you find a mirror that is geographically close to you, please move +# it to the top of the server list, so pacman will choose it first. By default +# mirror lists are located in /etc/pacman.d/ +# +
#[testing] #Server = ftp://ftp.archlinux.org/testing/os/i686
[current] -# Add your preferred servers here, they will be used first Include = /etc/pacman.d/current
[extra] -# Add your preferred servers here, they will be used first Include = /etc/pacman.d/extra
-#[unstable] -# Add your preferred servers here, they will be used first -#Include = /etc/pacman.d/unstable - [community] -# Add your preferred servers here, they will be used first Include = /etc/pacman.d/community
-# An example of a custom package repository. See the pacman manpage for -# tips on creating your own repositories. +#[unstable] +#Include = /etc/pacman.d/unstable + +# See the pacman manpage for tips on creating your own repositories. #[custom] #Server = file:///home/custompkgs
On Tue, Dec 05, 2006 at 08:42:42PM -0500, Dan McGee dpmcgee@gmail.com wrote:
I removed most of the NoUpgrade lines in the file because all of these files are already protected by their respective packages (at least in Arch, and I would assume in Frugal as well).
yes, we removed them since ages :)
udv / greetings, VMiklos
On 12/5/06, Dan McGee dpmcgee@gmail.com wrote:
I've included a patch to clean up pacman.conf a bit and move the instructions it provides at the top to a more applicable position in the file.
Thanks! I've included most of this in cvs.
2006/12/8, Aaron Griffin aaronmgriffin@gmail.com:
On 12/5/06, Dan McGee dpmcgee@gmail.com wrote:
I've included a patch to clean up pacman.conf a bit and move the instructions it provides at the top to a more applicable position in the file.
Thanks! I've included most of this in cvs.
Shouldn't [unstable] be before community, current and extra by default? ;-/
On 12/8/06, Roman Kyrylych roman.kyrylych@gmail.com wrote:
2006/12/8, Aaron Griffin aaronmgriffin@gmail.com:
On 12/5/06, Dan McGee dpmcgee@gmail.com wrote:
I've included a patch to clean up pacman.conf a bit and move the instructions it provides at the top to a more applicable position in the file.
Thanks! I've included most of this in cvs.
Shouldn't [unstable] be before community, current and extra by default? ;-/
People might get a bit too eager and uncomment the repo and run a pacman -Syu, only to be on the forums five minutes later asking why something doesn't work right. If you leave it below, they will have to either purposely install something from unstable (e.g. by a 'pacman -S unstable/nvidia') or read up enough to realize that if they prefer packages from unstable, they will need to move the repo up in the list. I personally have testing and unstable uncommented but below current and extra, so I can pick what packages I want to install from these repositories and not be left with an unusable machine.
Dan
2006/12/9, Dan McGee dpmcgee@gmail.com:
Shouldn't [unstable] be before community, current and extra by default? ;-/
People might get a bit too eager and uncomment the repo and run a pacman -Syu, only to be on the forums five minutes later asking why something doesn't work right. If you leave it below, they will have to either purposely install something from unstable (e.g. by a 'pacman -S unstable/nvidia') or read up enough to realize that if they prefer packages from unstable, they will need to move the repo up in the list. I personally have testing and unstable uncommented but below current and extra, so I can pick what packages I want to install from these repositories and not be left with an unusable machine.
Ah, I've forgot about these issues. You are right.
On 12/8/06, Dan McGee dpmcgee@gmail.com wrote:
On 12/8/06, Roman Kyrylych roman.kyrylych@gmail.com wrote:
Shouldn't [unstable] be before community, current and extra by default? ;-/
People might get a bit too eager and uncomment the repo and run a pacman -Syu
Yes, this is the impression I got too, and I agree with it. [unstable] is exactly that. [community], on the other hand, is generally stable yet less popular packages. If you go by logical, hierarchal ordering, "before" sometimes implies "better". If I didn't know better, and saw community below unstable, I would automatically think "community is _worse_ than unstable", but it is, in actuality the other way around. I'd put my money on a community package before an unstable one (no offense to Shadowhand) because most of those are development versions, and unstable by their very nature.
pacman-dev@lists.archlinux.org