You are not logged in.
I wanted to postpone the recent kernel upgrade for a little while so I put in /etc/pacman.conf
'IgnorePkg = kernel26 kernel26-firmware '. Yet a 'pacman -Syu' happily tries to install the new kernel. Any idea why this is?
update:
My bash alias didn't call pacman, but 'clyde', and clyde has it's own 'ignorePkg' in /etc/clyde.conf .
Last edited by rwd (2010-11-28 23:10:21)
Offline
Whitespace? The wiki example uses:
IgnorePkg=kernel26Offline
I downgraded the kernel and changing the line to
IgnorePkg=kernel26 kernel26-firmware kernel26-headersBut pacman still tries to upgrade kernel26. Also the default pacman.conf in the pacman package uses the 'x = y' format for all settings, so it would seem odd that one specific setting shouldn't be used with whitespace.
Last edited by rwd (2010-11-28 21:38:05)
Offline
Thats strange. Whitespace works fine for me.
flack 2.0.6: menu-driven BASH script to easily tag FLAC files (AUR)
knock-once 1.2: BASH script to easily create/send one-time sequences for knockd (forum/AUR)
Offline
Did you remember to remove the # from the line?
Offline
Did you remember to remove the # from the line?
I had indeed removed it already.
Last edited by rwd (2010-11-28 22:23:41)
Offline
Ah found it. I my bash alias didn't call pacman, but 'clyde', and clyde has it's own 'ignorePkg' in /etc/clyde.conf . It would seem better design to me if clyde used pacman.conf as defaults since it is a front-end for pacman, but alas.
Last edited by rwd (2010-11-28 22:30:51)
Offline
Ah found it. I my bash alias didn't call pacman, but 'clyde', and clyde has it's own 'ignorePkg' in /etc/clyde.conf . It would seem better design to me if clyde used pacman.conf as defaults since it is a front-end for pacman, but alas.
The dev made that decision, you'll find it in the clyde thread along with reasonings for it. FWIW I agree with you, but I'm not the dev ![]()
Allan-Volunteer on the (topic being discussed) mailn lists. You never get the people who matters attention on the forums.
jasonwryan-Installing Arch is a measure of your literacy. Maintaining Arch is a measure of your diligence. Contributing to Arch is a measure of your competence.
Griemak-Bleeding edge, not bleeding flat. Edge denotes falls will occur from time to time. Bring your own parachute.
Offline
Ah found it. I my bash alias didn't call pacman, but 'clyde', and clyde has it's own 'ignorePkg' in /etc/clyde.conf . It would seem better design to me if clyde used pacman.conf as defaults since it is a front-end for pacman, but alas.
Clyde is not a frontend for pacman, it's a frontend for libalpm. Do you consider it better design if one program needs to be configured from another program's .conf file?
ᶘ ᵒᴥᵒᶅ
Offline
rwd wrote:Ah found it. I my bash alias didn't call pacman, but 'clyde', and clyde has it's own 'ignorePkg' in /etc/clyde.conf . It would seem better design to me if clyde used pacman.conf as defaults since it is a front-end for pacman, but alas.
Clyde is not a frontend for pacman, it's a frontend for libalpm. Do you consider it better design if one program needs to be configured from another program's .conf file?
Well from the user's point of view it is a front-end for pacman. So most sensible thing to me would be for clyde to use pacman.conf as default, with the ability to override them in clyde,conf, similar to Bauerbill, and also like the way mplayer front-ends deal with mplayer's settings. But let's not get into that. It's the dev's choice, and fortunately we have a lot of other apps to choose from.
Last edited by rwd (2010-11-29 09:16:24)
Offline
Well from the user's point of view it is a front-end for pacman. So most sensible thing to me would be for clyde to use pacman.conf as default, with the ability to override them in clyde,conf, similar to Bauerbill,
Why, The user is wrong. It is a libalpm frontend jsut like it says in its pkgdesc... "Next-generation libalpm/makepkg wrapper."
Bauerbill on the other hand states it is an extension of powerbill which states it is a wrapper for pacman...
Offline