Differences

This shows you the differences between two versions of the page.

--- faq [2008-11-06 08:27] – livecd links grizz
+++ faq [2012-10-31 10:55] (current) – avoid smart fromatting for double slashes glen
@@ Line 16: / Line 16: @@
 ==== What does the acronym "PLD" stand for? ====
 PLD is a recursive acronym (which are quite popular in the Open Source world) for PLD Linux Distribution. Do note, that it used to be Polish(ed) Linux Distribution, but that has changed many years ago and is no longer valid.
-==== Why were there two different PLD projects? ====
-Up until May 2003 all crucial decisions concerning PLD were made by its (now former) leader, Tomasz Kłoczko. Many developers didn't agree with his way of handling things and, after finding repeated attempts to change the situation a failure, decided to stop using the parts of infrastructure controlled by Tomasz (including the most critical part - the CVS repository) and, by doing so, render him unable to force any decisions upon anyone. Tomasz was offered a position as a developer within the new structures (of course without the power he previously had) but decided, together with one other developer that refused to switch, to keep developing his own version of PLD under the original domain name (pld.org.pl). Apparently after a while he lost interest in it, with the domain finally expiring after a few years. Currently (since mid 2007) *.pld.org.pl mirrors the content of *.pld-linux.org.
@@ Line 32: / Line 27: @@
 :34:19 < evilabram> rescue is for install ;-)
 </file>
-i suggest you to use rescuecd, as it's with more recent kernel and tools.
   * [[http://rescuecd.pld-linux.org/download/current/|RescueCD]]
@@ Line 43: / Line 36: @@
 ==== How to install PLD Th ? ====
-Use [[http://cri.pld-linux.org/|ChRoot Installer]] for PLD/Linux Th installation.
+  * Use [[http://cri.pld-linux.org/|ChRoot Installer]] for PLD/Linux Th installation.
+  * Graphical installation using Anaconda from [[http://livecd.pld-linux.org/|LiveCD]]
+  * [[:Docs:man:Installing_PLD_Linux_based_on_Rescue_CD| 'Classic' chroot installation]]
@@ Line 53: / Line 48: @@
 ==== How to check from which .spec file was package X built? ====
-First of all, one should check whether there exists a spec file named just like the package. If not, the name of the spec file can be found in the output of one of these commands:
-<file>rpm -q --changelog package package2 | grep '$Log'
-# for already installed packages
-rpm -q --changelog -p package.rpm package2.rpm | grep '$Log'
-# for packages available as files
-</file>
-One can also use a more sophisticated command (just like before, adding a "''-p''" switch after the "''--changelog''" command and giving full file names allows one to query packages from disk):
-<file>rpm -q --changelog package package2 | awk '/^\$Log:/ {spec=$2;gsub(",v$","",spec);print spec}'
-</file>
+''rpm -qi package'' command  will show various information about the package, including the source RPM name. You can check the
+source RPM name also with ''%%rpm -q --queryformat '%{sourcerpm}\n' package%%''. The base name of the source RPM (with version and the '.src.rpm' suffix stipped) is also the name for the GIT repository and the spec file.
 ==== How to check which package contains a particular file? ====