jasonwryan wrote:Jristz wrote:jasonwryan wrote:Never do pacman -Syuf - it will break your system...in this case, wath is the objective of having a funtions that is recommended never use, instead why no only the -Syu --force and not the -Syuf???is more easy to write unintentionally a -Suyf raten than a -Syu --forceYou use the -f (or --force) option with S; ie., on a single package.
Inkane wrote:Uhm, what's so random about our debug packgae naming for KDE applications (putting -debug after the package name)?Ok, it's not that random, but the different prefixes (kdeutils, kdeapps,...) makes it a little confusing.Inkane wrote:Also,pacman -Ss qt | grep debug would point you to the qt-debug package.I'm downloading this right know.
chamber wrote:man pacman wrote: -Q, --query Query the package database. This operation allows you to view installed packages and their files, as well as meta-information about individual packages (dependencies, conflicts, install date, build date, size).
I'm using Crunchbang Linux on my laptop.
I noticed a strange behavior of the package manager: when installing a package from the official repo (libdirectfb-extra in my case) apt told me that a bunch of packages were no more needed (including xflux, obconf, obmenu and other applications that I use frequently).
tomk wrote:So you really think a bug report entitled "Just to let you know...." is OK?The purpose of the report is to convince the Arch devs to release 1.10.4 to extra before 1.11 moves over from testing.
dlin wrote:tomk wrote:Of course, you can suggest anything. Write the PKGBUILDs youself the way you think it should be done, and submit them in a feature request in the bugtracker.So, there is no standard way to build these packages from base + base-devel?I'm wonder how to make sure every package work well?