[web] Publish ro translation of the RPM Guide
Petr Kovář
pmkovar at fedoraproject.org
Mon Aug 22 23:10:54 UTC 2011
commit d7b5c36875b8c2bac5a419d766dd4245a6665f16
Author: Petr Kovar <pkovar at redhat.com>
Date: Tue Aug 23 01:09:49 2011 +0200
Publish ro translation of the RPM Guide
fedoradocs.db | Bin 539648 -> 541696 bytes
public_html/Sitemap | 42 +-
public_html/as-IN/Site_Statistics.html | 13 +-
public_html/as-IN/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 6 +-
public_html/as-IN/opds-Fedora_Core.xml | 2 +-
.../as-IN/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/as-IN/opds.xml | 10 +-
public_html/as-IN/toc.html | 11 +-
public_html/bg-BG/Site_Statistics.html | 13 +-
public_html/bg-BG/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 6 +-
public_html/bg-BG/opds-Fedora_Core.xml | 2 +-
.../bg-BG/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/bg-BG/opds.xml | 10 +-
public_html/bg-BG/toc.html | 11 +-
public_html/bn-IN/Site_Statistics.html | 13 +-
public_html/bn-IN/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 6 +-
public_html/bn-IN/opds-Fedora_Core.xml | 2 +-
.../bn-IN/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/bn-IN/opds.xml | 10 +-
public_html/bn-IN/toc.html | 11 +-
public_html/bs-BA/Site_Statistics.html | 13 +-
public_html/bs-BA/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 6 +-
public_html/bs-BA/opds-Fedora_Core.xml | 2 +-
.../bs-BA/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/bs-BA/opds.xml | 10 +-
public_html/bs-BA/toc.html | 11 +-
public_html/ca-ES/Site_Statistics.html | 13 +-
public_html/ca-ES/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 6 +-
public_html/ca-ES/opds-Fedora_Core.xml | 2 +-
.../ca-ES/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/ca-ES/opds.xml | 10 +-
public_html/ca-ES/toc.html | 11 +-
public_html/cs-CZ/Site_Statistics.html | 13 +-
public_html/cs-CZ/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 6 +-
public_html/cs-CZ/opds-Fedora_Core.xml | 2 +-
.../cs-CZ/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/cs-CZ/opds.xml | 10 +-
public_html/cs-CZ/toc.html | 11 +-
public_html/da-DK/Site_Statistics.html | 13 +-
public_html/da-DK/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 6 +-
public_html/da-DK/opds-Fedora_Core.xml | 2 +-
.../da-DK/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/da-DK/opds.xml | 10 +-
public_html/da-DK/toc.html | 11 +-
public_html/de-DE/Site_Statistics.html | 13 +-
public_html/de-DE/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 6 +-
public_html/de-DE/opds-Fedora_Core.xml | 2 +-
.../de-DE/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/de-DE/opds.xml | 10 +-
public_html/de-DE/toc.html | 13 +-
public_html/el-GR/Site_Statistics.html | 13 +-
public_html/el-GR/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 6 +-
public_html/el-GR/opds-Fedora_Core.xml | 2 +-
.../el-GR/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/el-GR/opds.xml | 10 +-
public_html/el-GR/toc.html | 9 +-
public_html/en-US/Site_Statistics.html | 13 +-
public_html/en-US/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 6 +-
public_html/en-US/opds-Fedora_Core.xml | 2 +-
.../en-US/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/en-US/opds.xml | 10 +-
public_html/en-US/toc.html | 11 +-
public_html/es-ES/Site_Statistics.html | 13 +-
public_html/es-ES/opds-Fedora.xml | 2 +-
public_html/es-ES/opds-Fedora_15.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 6 +-
public_html/es-ES/opds-Fedora_Core.xml | 2 +-
.../es-ES/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/es-ES/opds.xml | 12 +-
public_html/es-ES/toc.html | 9 +-
public_html/fa-IR/Site_Statistics.html | 13 +-
public_html/fa-IR/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 6 +-
public_html/fa-IR/opds-Fedora_Core.xml | 2 +-
.../fa-IR/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/fa-IR/opds.xml | 10 +-
public_html/fa-IR/toc.html | 11 +-
public_html/fi-FI/Site_Statistics.html | 13 +-
public_html/fi-FI/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 6 +-
public_html/fi-FI/opds-Fedora_Core.xml | 2 +-
.../fi-FI/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/fi-FI/opds.xml | 10 +-
public_html/fi-FI/toc.html | 11 +-
public_html/fr-FR/Site_Statistics.html | 13 +-
public_html/fr-FR/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 6 +-
public_html/fr-FR/opds-Fedora_Core.xml | 2 +-
.../fr-FR/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/fr-FR/opds.xml | 10 +-
public_html/fr-FR/toc.html | 11 +-
public_html/gu-IN/Site_Statistics.html | 13 +-
public_html/gu-IN/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 6 +-
public_html/gu-IN/opds-Fedora_Core.xml | 2 +-
.../gu-IN/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/gu-IN/opds.xml | 10 +-
public_html/gu-IN/toc.html | 11 +-
public_html/he-IL/Site_Statistics.html | 13 +-
public_html/he-IL/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 6 +-
public_html/he-IL/opds-Fedora_Core.xml | 2 +-
.../he-IL/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/he-IL/opds.xml | 10 +-
public_html/he-IL/toc.html | 11 +-
public_html/hi-IN/Site_Statistics.html | 13 +-
public_html/hi-IN/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 6 +-
public_html/hi-IN/opds-Fedora_Core.xml | 2 +-
.../hi-IN/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/hi-IN/opds.xml | 10 +-
public_html/hi-IN/toc.html | 11 +-
public_html/hu-HU/Site_Statistics.html | 13 +-
public_html/hu-HU/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 6 +-
public_html/hu-HU/opds-Fedora_Core.xml | 2 +-
.../hu-HU/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/hu-HU/opds.xml | 10 +-
public_html/hu-HU/toc.html | 11 +-
public_html/id-ID/Site_Statistics.html | 13 +-
public_html/id-ID/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 6 +-
public_html/id-ID/opds-Fedora_Core.xml | 2 +-
.../id-ID/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/id-ID/opds.xml | 10 +-
public_html/id-ID/toc.html | 11 +-
public_html/index.html | 2 +-
public_html/it-IT/Site_Statistics.html | 13 +-
public_html/it-IT/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 6 +-
public_html/it-IT/opds-Fedora_Core.xml | 2 +-
.../it-IT/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/it-IT/opds.xml | 10 +-
public_html/it-IT/toc.html | 13 +-
public_html/ja-JP/Site_Statistics.html | 13 +-
public_html/ja-JP/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 6 +-
public_html/ja-JP/opds-Fedora_Core.xml | 2 +-
.../ja-JP/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/ja-JP/opds.xml | 10 +-
public_html/ja-JP/toc.html | 11 +-
public_html/kn-IN/Site_Statistics.html | 13 +-
public_html/kn-IN/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 6 +-
public_html/kn-IN/opds-Fedora_Core.xml | 2 +-
.../kn-IN/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/kn-IN/opds.xml | 10 +-
public_html/kn-IN/toc.html | 11 +-
public_html/ko-KR/Site_Statistics.html | 13 +-
public_html/ko-KR/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 6 +-
public_html/ko-KR/opds-Fedora_Core.xml | 2 +-
.../ko-KR/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/ko-KR/opds.xml | 10 +-
public_html/ko-KR/toc.html | 11 +-
public_html/ml-IN/Site_Statistics.html | 13 +-
public_html/ml-IN/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 6 +-
public_html/ml-IN/opds-Fedora_Core.xml | 2 +-
.../ml-IN/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/ml-IN/opds.xml | 10 +-
public_html/ml-IN/toc.html | 11 +-
public_html/mr-IN/Site_Statistics.html | 13 +-
public_html/mr-IN/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 6 +-
public_html/mr-IN/opds-Fedora_Core.xml | 2 +-
.../mr-IN/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/mr-IN/opds.xml | 10 +-
public_html/mr-IN/toc.html | 11 +-
public_html/nb-NO/Site_Statistics.html | 13 +-
public_html/nb-NO/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 6 +-
public_html/nb-NO/opds-Fedora_Core.xml | 2 +-
.../nb-NO/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/nb-NO/opds.xml | 10 +-
public_html/nb-NO/toc.html | 11 +-
public_html/nl-NL/Site_Statistics.html | 13 +-
public_html/nl-NL/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 6 +-
public_html/nl-NL/opds-Fedora_Core.xml | 2 +-
.../nl-NL/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/nl-NL/opds.xml | 10 +-
public_html/nl-NL/toc.html | 7 +-
public_html/opds.xml | 94 +-
public_html/or-IN/Site_Statistics.html | 13 +-
public_html/or-IN/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 6 +-
public_html/or-IN/opds-Fedora_Core.xml | 2 +-
.../or-IN/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/or-IN/opds.xml | 10 +-
public_html/or-IN/toc.html | 11 +-
public_html/pa-IN/Site_Statistics.html | 13 +-
public_html/pa-IN/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 6 +-
public_html/pa-IN/opds-Fedora_Core.xml | 2 +-
.../pa-IN/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/pa-IN/opds.xml | 10 +-
public_html/pa-IN/toc.html | 11 +-
public_html/pl-PL/Site_Statistics.html | 13 +-
public_html/pl-PL/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 6 +-
public_html/pl-PL/opds-Fedora_Core.xml | 2 +-
.../pl-PL/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/pl-PL/opds.xml | 10 +-
public_html/pl-PL/toc.html | 11 +-
public_html/pt-BR/Site_Statistics.html | 13 +-
public_html/pt-BR/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 6 +-
public_html/pt-BR/opds-Fedora_Core.xml | 2 +-
.../pt-BR/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/pt-BR/opds.xml | 10 +-
public_html/pt-BR/toc.html | 9 +-
public_html/pt-PT/Site_Statistics.html | 13 +-
public_html/pt-PT/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 6 +-
public_html/pt-PT/opds-Fedora_Core.xml | 2 +-
.../pt-PT/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/pt-PT/opds.xml | 10 +-
public_html/pt-PT/toc.html | 7 +-
...edora_Draft_Documentation-0.1-RPM_Guide-ro.epub | Bin 0 -> 585317 bytes
.../RPM_Guide/Common_Content/css/common.css | 1495 ++
.../RPM_Guide/Common_Content/css/default.css | 3 +
.../RPM_Guide/Common_Content/css/lang.css | 2 +
.../RPM_Guide/Common_Content/css/overrides.css | 51 +
.../RPM_Guide/Common_Content/css/print.css | 16 +
.../RPM_Guide/Common_Content/images/1.png | Bin 0 -> 710 bytes
.../RPM_Guide/Common_Content/images/1.svg | 27 +
.../RPM_Guide/Common_Content/images/10.png | Bin 0 -> 985 bytes
.../RPM_Guide/Common_Content/images/10.svg | 31 +
.../RPM_Guide/Common_Content/images/11.png | Bin 0 -> 810 bytes
.../RPM_Guide/Common_Content/images/11.svg | 31 +
.../RPM_Guide/Common_Content/images/12.png | Bin 0 -> 1012 bytes
.../RPM_Guide/Common_Content/images/12.svg | 31 +
.../RPM_Guide/Common_Content/images/13.png | Bin 0 -> 1048 bytes
.../RPM_Guide/Common_Content/images/13.svg | 31 +
.../RPM_Guide/Common_Content/images/14.png | Bin 0 -> 914 bytes
.../RPM_Guide/Common_Content/images/14.svg | 31 +
.../RPM_Guide/Common_Content/images/15.png | Bin 0 -> 989 bytes
.../RPM_Guide/Common_Content/images/15.svg | 31 +
.../RPM_Guide/Common_Content/images/16.png | Bin 0 -> 1047 bytes
.../RPM_Guide/Common_Content/images/16.svg | 31 +
.../RPM_Guide/Common_Content/images/17.png | Bin 0 -> 888 bytes
.../RPM_Guide/Common_Content/images/17.svg | 31 +
.../RPM_Guide/Common_Content/images/18.png | Bin 0 -> 1075 bytes
.../RPM_Guide/Common_Content/images/18.svg | 31 +
.../RPM_Guide/Common_Content/images/19.png | Bin 0 -> 1049 bytes
.../RPM_Guide/Common_Content/images/19.svg | 31 +
.../RPM_Guide/Common_Content/images/2.png | Bin 0 -> 896 bytes
.../RPM_Guide/Common_Content/images/2.svg | 27 +
.../RPM_Guide/Common_Content/images/20.png | Bin 0 -> 1151 bytes
.../RPM_Guide/Common_Content/images/20.svg | 31 +
.../RPM_Guide/Common_Content/images/21.png | Bin 0 -> 994 bytes
.../RPM_Guide/Common_Content/images/21.svg | 31 +
.../RPM_Guide/Common_Content/images/22.png | Bin 0 -> 1162 bytes
.../RPM_Guide/Common_Content/images/22.svg | 31 +
.../RPM_Guide/Common_Content/images/23.png | Bin 0 -> 1207 bytes
.../RPM_Guide/Common_Content/images/23.svg | 31 +
.../RPM_Guide/Common_Content/images/24.png | Bin 0 -> 1081 bytes
.../RPM_Guide/Common_Content/images/24.svg | 31 +
.../RPM_Guide/Common_Content/images/25.png | Bin 0 -> 1173 bytes
.../RPM_Guide/Common_Content/images/25.svg | 31 +
.../RPM_Guide/Common_Content/images/26.png | Bin 0 -> 1208 bytes
.../RPM_Guide/Common_Content/images/26.svg | 31 +
.../RPM_Guide/Common_Content/images/27.png | Bin 0 -> 1080 bytes
.../RPM_Guide/Common_Content/images/27.svg | 31 +
.../RPM_Guide/Common_Content/images/28.png | Bin 0 -> 1225 bytes
.../RPM_Guide/Common_Content/images/28.svg | 31 +
.../RPM_Guide/Common_Content/images/29.png | Bin 0 -> 1196 bytes
.../RPM_Guide/Common_Content/images/29.svg | 31 +
.../RPM_Guide/Common_Content/images/3.png | Bin 0 -> 958 bytes
.../RPM_Guide/Common_Content/images/3.svg | 27 +
.../RPM_Guide/Common_Content/images/30.png | Bin 0 -> 1250 bytes
.../RPM_Guide/Common_Content/images/30.svg | 31 +
.../RPM_Guide/Common_Content/images/31.png | Bin 0 -> 1078 bytes
.../RPM_Guide/Common_Content/images/31.svg | 31 +
.../RPM_Guide/Common_Content/images/32.png | Bin 0 -> 1241 bytes
.../RPM_Guide/Common_Content/images/32.svg | 31 +
.../RPM_Guide/Common_Content/images/33.png | Bin 0 -> 1268 bytes
.../RPM_Guide/Common_Content/images/33.svg | 31 +
.../RPM_Guide/Common_Content/images/34.png | Bin 0 -> 1175 bytes
.../RPM_Guide/Common_Content/images/34.svg | 31 +
.../RPM_Guide/Common_Content/images/35.png | Bin 0 -> 1224 bytes
.../RPM_Guide/Common_Content/images/35.svg | 31 +
.../RPM_Guide/Common_Content/images/36.png | Bin 0 -> 1281 bytes
.../RPM_Guide/Common_Content/images/36.svg | 31 +
.../RPM_Guide/Common_Content/images/37.png | Bin 0 -> 1140 bytes
.../RPM_Guide/Common_Content/images/37.svg | 31 +
.../RPM_Guide/Common_Content/images/38.png | Bin 0 -> 1300 bytes
.../RPM_Guide/Common_Content/images/38.svg | 31 +
.../RPM_Guide/Common_Content/images/39.png | Bin 0 -> 1294 bytes
.../RPM_Guide/Common_Content/images/39.svg | 31 +
.../RPM_Guide/Common_Content/images/4.png | Bin 0 -> 849 bytes
.../RPM_Guide/Common_Content/images/4.svg | 27 +
.../RPM_Guide/Common_Content/images/40.png | Bin 0 -> 1130 bytes
.../RPM_Guide/Common_Content/images/40.svg | 31 +
.../RPM_Guide/Common_Content/images/5.png | Bin 0 -> 900 bytes
.../RPM_Guide/Common_Content/images/5.svg | 27 +
.../RPM_Guide/Common_Content/images/6.png | Bin 0 -> 929 bytes
.../RPM_Guide/Common_Content/images/6.svg | 27 +
.../RPM_Guide/Common_Content/images/7.png | Bin 0 -> 807 bytes
.../RPM_Guide/Common_Content/images/7.svg | 27 +
.../RPM_Guide/Common_Content/images/8.png | Bin 0 -> 962 bytes
.../RPM_Guide/Common_Content/images/8.svg | 27 +
.../RPM_Guide/Common_Content/images/9.png | Bin 0 -> 936 bytes
.../RPM_Guide/Common_Content/images/9.svg | 27 +
.../Common_Content/images/bkgrnd_greydots.png | Bin 0 -> 157 bytes
.../Common_Content/images/bullet_arrowblue.png | Bin 0 -> 177 bytes
.../Common_Content/images/documentation.png | Bin 0 -> 623 bytes
.../RPM_Guide/Common_Content/images/dot.png | Bin 0 -> 98 bytes
.../RPM_Guide/Common_Content/images/dot2.png | Bin 0 -> 98 bytes
.../RPM_Guide/Common_Content/images/green.png | Bin 0 -> 176 bytes
.../RPM_Guide/Common_Content/images/h1-bg.png | Bin 0 -> 565 bytes
.../RPM_Guide/Common_Content/images/image_left.png | Bin 0 -> 1114 bytes
.../Common_Content/images/image_right.png | Bin 0 -> 2260 bytes
.../RPM_Guide/Common_Content/images/important.png | Bin 0 -> 2080 bytes
.../RPM_Guide/Common_Content/images/important.svg | 106 +
.../RPM_Guide/Common_Content/images/logo.png | Bin 0 -> 1114 bytes
.../RPM_Guide/Common_Content/images/note.png | Bin 0 -> 1241 bytes
.../RPM_Guide/Common_Content/images/note.svg | 111 +
.../RPM_Guide/Common_Content/images/red.png | Bin 0 -> 163 bytes
.../RPM_Guide/Common_Content/images/shade.png | Bin 0 -> 101 bytes
.../RPM_Guide/Common_Content/images/shine.png | Bin 0 -> 146 bytes
.../Common_Content/images/stock-go-back.png | Bin 0 -> 828 bytes
.../Common_Content/images/stock-go-forward.png | Bin 0 -> 828 bytes
.../Common_Content/images/stock-go-up.png | Bin 0 -> 760 bytes
.../RPM_Guide/Common_Content/images/stock-home.png | Bin 0 -> 808 bytes
.../RPM_Guide/Common_Content/images/title_logo.png | Bin 0 -> 13399 bytes
.../RPM_Guide/Common_Content/images/title_logo.svg | 61 +
.../RPM_Guide/Common_Content/images/warning.png | Bin 0 -> 1340 bytes
.../RPM_Guide/Common_Content/images/warning.svg | 89 +
.../Common_Content/images/watermark-draft.png | Bin 0 -> 25365 bytes
.../RPM_Guide/Common_Content/images/yellow.png | Bin 0 -> 175 bytes
.../0.1/html-single/RPM_Guide/index.html |23203 ++++++++++++++++++++
.../html/RPM_Guide/Common_Content/css/common.css | 1495 ++
.../html/RPM_Guide/Common_Content/css/default.css | 3 +
.../0.1/html/RPM_Guide/Common_Content/css/lang.css | 2 +
.../RPM_Guide/Common_Content/css/overrides.css | 51 +
.../html/RPM_Guide/Common_Content/css/print.css | 16 +
.../0.1/html/RPM_Guide/Common_Content/images/1.png | Bin 0 -> 710 bytes
.../0.1/html/RPM_Guide/Common_Content/images/1.svg | 27 +
.../html/RPM_Guide/Common_Content/images/10.png | Bin 0 -> 985 bytes
.../html/RPM_Guide/Common_Content/images/10.svg | 31 +
.../html/RPM_Guide/Common_Content/images/11.png | Bin 0 -> 810 bytes
.../html/RPM_Guide/Common_Content/images/11.svg | 31 +
.../html/RPM_Guide/Common_Content/images/12.png | Bin 0 -> 1012 bytes
.../html/RPM_Guide/Common_Content/images/12.svg | 31 +
.../html/RPM_Guide/Common_Content/images/13.png | Bin 0 -> 1048 bytes
.../html/RPM_Guide/Common_Content/images/13.svg | 31 +
.../html/RPM_Guide/Common_Content/images/14.png | Bin 0 -> 914 bytes
.../html/RPM_Guide/Common_Content/images/14.svg | 31 +
.../html/RPM_Guide/Common_Content/images/15.png | Bin 0 -> 989 bytes
.../html/RPM_Guide/Common_Content/images/15.svg | 31 +
.../html/RPM_Guide/Common_Content/images/16.png | Bin 0 -> 1047 bytes
.../html/RPM_Guide/Common_Content/images/16.svg | 31 +
.../html/RPM_Guide/Common_Content/images/17.png | Bin 0 -> 888 bytes
.../html/RPM_Guide/Common_Content/images/17.svg | 31 +
.../html/RPM_Guide/Common_Content/images/18.png | Bin 0 -> 1075 bytes
.../html/RPM_Guide/Common_Content/images/18.svg | 31 +
.../html/RPM_Guide/Common_Content/images/19.png | Bin 0 -> 1049 bytes
.../html/RPM_Guide/Common_Content/images/19.svg | 31 +
.../0.1/html/RPM_Guide/Common_Content/images/2.png | Bin 0 -> 896 bytes
.../0.1/html/RPM_Guide/Common_Content/images/2.svg | 27 +
.../html/RPM_Guide/Common_Content/images/20.png | Bin 0 -> 1151 bytes
.../html/RPM_Guide/Common_Content/images/20.svg | 31 +
.../html/RPM_Guide/Common_Content/images/21.png | Bin 0 -> 994 bytes
.../html/RPM_Guide/Common_Content/images/21.svg | 31 +
.../html/RPM_Guide/Common_Content/images/22.png | Bin 0 -> 1162 bytes
.../html/RPM_Guide/Common_Content/images/22.svg | 31 +
.../html/RPM_Guide/Common_Content/images/23.png | Bin 0 -> 1207 bytes
.../html/RPM_Guide/Common_Content/images/23.svg | 31 +
.../html/RPM_Guide/Common_Content/images/24.png | Bin 0 -> 1081 bytes
.../html/RPM_Guide/Common_Content/images/24.svg | 31 +
.../html/RPM_Guide/Common_Content/images/25.png | Bin 0 -> 1173 bytes
.../html/RPM_Guide/Common_Content/images/25.svg | 31 +
.../html/RPM_Guide/Common_Content/images/26.png | Bin 0 -> 1208 bytes
.../html/RPM_Guide/Common_Content/images/26.svg | 31 +
.../html/RPM_Guide/Common_Content/images/27.png | Bin 0 -> 1080 bytes
.../html/RPM_Guide/Common_Content/images/27.svg | 31 +
.../html/RPM_Guide/Common_Content/images/28.png | Bin 0 -> 1225 bytes
.../html/RPM_Guide/Common_Content/images/28.svg | 31 +
.../html/RPM_Guide/Common_Content/images/29.png | Bin 0 -> 1196 bytes
.../html/RPM_Guide/Common_Content/images/29.svg | 31 +
.../0.1/html/RPM_Guide/Common_Content/images/3.png | Bin 0 -> 958 bytes
.../0.1/html/RPM_Guide/Common_Content/images/3.svg | 27 +
.../html/RPM_Guide/Common_Content/images/30.png | Bin 0 -> 1250 bytes
.../html/RPM_Guide/Common_Content/images/30.svg | 31 +
.../html/RPM_Guide/Common_Content/images/31.png | Bin 0 -> 1078 bytes
.../html/RPM_Guide/Common_Content/images/31.svg | 31 +
.../html/RPM_Guide/Common_Content/images/32.png | Bin 0 -> 1241 bytes
.../html/RPM_Guide/Common_Content/images/32.svg | 31 +
.../html/RPM_Guide/Common_Content/images/33.png | Bin 0 -> 1268 bytes
.../html/RPM_Guide/Common_Content/images/33.svg | 31 +
.../html/RPM_Guide/Common_Content/images/34.png | Bin 0 -> 1175 bytes
.../html/RPM_Guide/Common_Content/images/34.svg | 31 +
.../html/RPM_Guide/Common_Content/images/35.png | Bin 0 -> 1224 bytes
.../html/RPM_Guide/Common_Content/images/35.svg | 31 +
.../html/RPM_Guide/Common_Content/images/36.png | Bin 0 -> 1281 bytes
.../html/RPM_Guide/Common_Content/images/36.svg | 31 +
.../html/RPM_Guide/Common_Content/images/37.png | Bin 0 -> 1140 bytes
.../html/RPM_Guide/Common_Content/images/37.svg | 31 +
.../html/RPM_Guide/Common_Content/images/38.png | Bin 0 -> 1300 bytes
.../html/RPM_Guide/Common_Content/images/38.svg | 31 +
.../html/RPM_Guide/Common_Content/images/39.png | Bin 0 -> 1294 bytes
.../html/RPM_Guide/Common_Content/images/39.svg | 31 +
.../0.1/html/RPM_Guide/Common_Content/images/4.png | Bin 0 -> 849 bytes
.../0.1/html/RPM_Guide/Common_Content/images/4.svg | 27 +
.../html/RPM_Guide/Common_Content/images/40.png | Bin 0 -> 1130 bytes
.../html/RPM_Guide/Common_Content/images/40.svg | 31 +
.../0.1/html/RPM_Guide/Common_Content/images/5.png | Bin 0 -> 900 bytes
.../0.1/html/RPM_Guide/Common_Content/images/5.svg | 27 +
.../0.1/html/RPM_Guide/Common_Content/images/6.png | Bin 0 -> 929 bytes
.../0.1/html/RPM_Guide/Common_Content/images/6.svg | 27 +
.../0.1/html/RPM_Guide/Common_Content/images/7.png | Bin 0 -> 807 bytes
.../0.1/html/RPM_Guide/Common_Content/images/7.svg | 27 +
.../0.1/html/RPM_Guide/Common_Content/images/8.png | Bin 0 -> 962 bytes
.../0.1/html/RPM_Guide/Common_Content/images/8.svg | 27 +
.../0.1/html/RPM_Guide/Common_Content/images/9.png | Bin 0 -> 936 bytes
.../0.1/html/RPM_Guide/Common_Content/images/9.svg | 27 +
.../Common_Content/images/bkgrnd_greydots.png | Bin 0 -> 157 bytes
.../Common_Content/images/bullet_arrowblue.png | Bin 0 -> 177 bytes
.../Common_Content/images/documentation.png | Bin 0 -> 623 bytes
.../html/RPM_Guide/Common_Content/images/dot.png | Bin 0 -> 98 bytes
.../html/RPM_Guide/Common_Content/images/dot2.png | Bin 0 -> 98 bytes
.../html/RPM_Guide/Common_Content/images/green.png | Bin 0 -> 176 bytes
.../html/RPM_Guide/Common_Content/images/h1-bg.png | Bin 0 -> 565 bytes
.../RPM_Guide/Common_Content/images/image_left.png | Bin 0 -> 1114 bytes
.../Common_Content/images/image_right.png | Bin 0 -> 2260 bytes
.../RPM_Guide/Common_Content/images/important.png | Bin 0 -> 2080 bytes
.../RPM_Guide/Common_Content/images/important.svg | 106 +
.../html/RPM_Guide/Common_Content/images/logo.png | Bin 0 -> 1114 bytes
.../html/RPM_Guide/Common_Content/images/note.png | Bin 0 -> 1241 bytes
.../html/RPM_Guide/Common_Content/images/note.svg | 111 +
.../html/RPM_Guide/Common_Content/images/red.png | Bin 0 -> 163 bytes
.../html/RPM_Guide/Common_Content/images/shade.png | Bin 0 -> 101 bytes
.../html/RPM_Guide/Common_Content/images/shine.png | Bin 0 -> 146 bytes
.../Common_Content/images/stock-go-back.png | Bin 0 -> 828 bytes
.../Common_Content/images/stock-go-forward.png | Bin 0 -> 828 bytes
.../Common_Content/images/stock-go-up.png | Bin 0 -> 760 bytes
.../RPM_Guide/Common_Content/images/stock-home.png | Bin 0 -> 808 bytes
.../RPM_Guide/Common_Content/images/title_logo.png | Bin 0 -> 13399 bytes
.../RPM_Guide/Common_Content/images/title_logo.svg | 61 +
.../RPM_Guide/Common_Content/images/warning.png | Bin 0 -> 1340 bytes
.../RPM_Guide/Common_Content/images/warning.svg | 89 +
.../Common_Content/images/watermark-draft.png | Bin 0 -> 25365 bytes
.../RPM_Guide/Common_Content/images/yellow.png | Bin 0 -> 175 bytes
.../RPM-Guide-Using_RPM-DB-verifying_packages.html | 141 +
...ide-Using_RPM_DB-Querying_file_information.html | 230 +
...RPM_GUide-Using_RPM_DB-working_with_RPM_db.html | 44 +
...PM_DB-Combining_queries-Recently_installed.html | 29 +
...DB-Combining_queries-State_of_config_files.html | 20 +
.../RPM_Guide-Using_RPM_DB-Combining_queries.html | 49 +
.../RPM_Guide-Using_RPM_DB-Cusomt_queries.html | 56 +
.../RPM_Guide-Using_RPM_DB-Formatting_arrays.html | 46 +
...PM_DB-Getting_information_on_package_files.html | 96 +
.../RPM_Guide-Using_RPM_DB-Listing_changed.html | 59 +
...Guide-Using_RPM_DB-Other_Query_Format_Tags.html | 128 +
.../RPM_Guide-Using_RPM_DB-Query_format_tags.html | 31 +
...ng_RPM_DB-Querying_for_package_information.html | 236 +
.../RPM_Guide-Using_RPM_DB-Special_formatting.html | 42 +
...uide-Using_RPM_DB-controlling_verification.html | 188 +
.../RPM_Guide-Using_RPM_DB-file_state.html | 91 +
...RPM_Guide-Using_RPM_DB-getting_information.html | 45 +
.../RPM_Guide-Using_RPM_DB-listing_conf_files.html | 58 +
.../RPM_Guide-Using_RPM_DB-listing_scripts.html | 89 +
.../RPM_Guide/RPM_Guide-Using_RPM_DB-new_db.html | 29 +
.../RPM_Guide-Using_RPM_DB-package_groups.html | 24 +
...Using_RPM_DB-querying_pacakge_dependencies.html | 190 +
.../RPM_Guide-Using_RPM_DB-rebuilding_RPM-db.html | 20 +
.../RPM_Guide/RPM_Guide-Using_RPM_DB-summary.html | 16 +
.../RPM_Guide/appe-Publican-Revision_History.html | 16 +
.../0.1/html/RPM_Guide/ch-advanced-packaging.html | 210 +
.../0.1/html/RPM_Guide/ch-command-reference.html | 1324 ++
.../0.1/html/RPM_Guide/ch-creating-rpms.html | 232 +
.../0.1/html/RPM_Guide/ch-customizing-rpm.html | 204 +
.../0.1/html/RPM_Guide/ch-dependencies.html | 121 +
.../0.1/html/RPM_Guide/ch-development-tools.html | 36 +
.../html/RPM_Guide/ch-extra-packaging-tools.html | 667 +
.../0.1/html/RPM_Guide/ch-intro-packaging.html | 44 +
.../0.1/html/RPM_Guide/ch-intro-rpm.html | 48 +
.../0.1/html/RPM_Guide/ch-licensing.html | 155 +
.../0.1/html/RPM_Guide/ch-management-software.html | 346 +
.../0.1/html/RPM_Guide/ch-online-resources.html | 412 +
.../0.1/html/RPM_Guide/ch-other-linuxes.html | 107 +
.../0.1/html/RPM_Guide/ch-other-os.html | 284 +
.../0.1/html/RPM_Guide/ch-package-structure.html | 2053 ++
.../html/RPM_Guide/ch-packaging-guidelines.html | 110 +
.../0.1/html/RPM_Guide/ch-programming-c.html | 561 +
.../0.1/html/RPM_Guide/ch-programming-perl.html | 50 +
.../0.1/html/RPM_Guide/ch-rpm-evolution.html | 76 +
.../0.1/html/RPM_Guide/ch-rpm-overview.html | 72 +
.../html/RPM_Guide/ch-rpm-programming-python.html | 54 +
.../0.1/html/RPM_Guide/ch-rpmbuild.html | 290 +
.../0.1/html/RPM_Guide/ch-scripting.html | 36 +
.../0.1/html/RPM_Guide/ch-specfile-syntax.html | 164 +
.../0.1/html/RPM_Guide/ch-specfiles.html | 42 +
.../0.1/html/RPM_Guide/ch-transactions.html | 46 +
.../0.1/html/RPM_Guide/ch-using-rpm-db.html | 320 +
.../0.1/html/RPM_Guide/ch-using-rpm.html | 22 +
.../0.1/html/RPM_Guide/ch01s02.html | 48 +
.../0.1/html/RPM_Guide/ch01s02s02.html | 14 +
.../0.1/html/RPM_Guide/ch01s02s03.html | 14 +
.../0.1/html/RPM_Guide/ch01s02s04.html | 18 +
.../0.1/html/RPM_Guide/ch01s02s05.html | 12 +
.../0.1/html/RPM_Guide/ch01s02s06.html | 12 +
.../0.1/html/RPM_Guide/ch01s02s07.html | 18 +
.../0.1/html/RPM_Guide/ch01s02s08.html | 14 +
.../0.1/html/RPM_Guide/ch01s03.html | 200 +
.../0.1/html/RPM_Guide/ch01s04.html | 28 +
.../0.1/html/RPM_Guide/ch02s02.html | 60 +
.../0.1/html/RPM_Guide/ch02s03.html | 105 +
.../0.1/html/RPM_Guide/ch02s03s02.html | 30 +
.../0.1/html/RPM_Guide/ch02s04.html | 14 +
.../0.1/html/RPM_Guide/ch03s02.html | 399 +
.../0.1/html/RPM_Guide/ch03s02s02.html | 31 +
.../0.1/html/RPM_Guide/ch03s02s02s02.html | 27 +
.../0.1/html/RPM_Guide/ch03s02s03.html | 17 +
.../0.1/html/RPM_Guide/ch03s02s04.html | 21 +
.../0.1/html/RPM_Guide/ch03s02s05.html | 41 +
.../0.1/html/RPM_Guide/ch03s02s05s02.html | 13 +
.../0.1/html/RPM_Guide/ch03s02s06.html | 32 +
.../0.1/html/RPM_Guide/ch03s03.html | 48 +
.../0.1/html/RPM_Guide/ch03s03s02.html | 15 +
.../0.1/html/RPM_Guide/ch03s03s03.html | 26 +
.../0.1/html/RPM_Guide/ch03s04.html | 55 +
.../0.1/html/RPM_Guide/ch03s05.html | 72 +
.../0.1/html/RPM_Guide/ch04s02s03.html | 101 +
.../0.1/html/RPM_Guide/ch04s02s05.html | 35 +
.../0.1/html/RPM_Guide/ch04s03.html | 96 +
.../0.1/html/RPM_Guide/ch05s02.html | 148 +
.../0.1/html/RPM_Guide/ch05s02s02.html | 112 +
.../0.1/html/RPM_Guide/ch05s02s03.html | 26 +
.../0.1/html/RPM_Guide/ch05s02s04.html | 224 +
.../0.1/html/RPM_Guide/ch05s02s05.html | 42 +
.../0.1/html/RPM_Guide/ch05s03.html | 222 +
.../0.1/html/RPM_Guide/ch05s04.html | 20 +
.../0.1/html/RPM_Guide/ch06s02.html | 184 +
.../0.1/html/RPM_Guide/ch06s02s02.html | 27 +
.../0.1/html/RPM_Guide/ch06s03.html | 69 +
.../0.1/html/RPM_Guide/ch06s04.html | 19 +
.../0.1/html/RPM_Guide/ch07s02.html | 38 +
.../0.1/html/RPM_Guide/ch07s02s02.html | 54 +
.../0.1/html/RPM_Guide/ch07s02s03.html | 32 +
.../0.1/html/RPM_Guide/ch07s02s04.html | 32 +
.../0.1/html/RPM_Guide/ch07s03.html | 184 +
.../0.1/html/RPM_Guide/ch07s03s02.html | 90 +
.../0.1/html/RPM_Guide/ch07s03s03.html | 210 +
.../0.1/html/RPM_Guide/ch07s03s04.html | 14 +
.../0.1/html/RPM_Guide/ch07s03s05.html | 18 +
.../0.1/html/RPM_Guide/ch07s03s06.html | 46 +
.../0.1/html/RPM_Guide/ch07s03s07.html | 18 +
.../0.1/html/RPM_Guide/ch07s04.html | 24 +
.../0.1/html/RPM_Guide/ch08s02.html | 146 +
.../0.1/html/RPM_Guide/ch08s02s02.html | 20 +
.../0.1/html/RPM_Guide/ch08s02s03.html | 67 +
.../0.1/html/RPM_Guide/ch08s02s03s02.html | 22 +
.../0.1/html/RPM_Guide/ch08s02s03s03.html | 22 +
.../0.1/html/RPM_Guide/ch08s02s03s04.html | 20 +
.../0.1/html/RPM_Guide/ch08s02s03s05.html | 18 +
.../0.1/html/RPM_Guide/ch08s02s03s06.html | 58 +
.../0.1/html/RPM_Guide/ch08s02s04.html | 260 +
.../0.1/html/RPM_Guide/ch08s03.html | 59 +
.../0.1/html/RPM_Guide/ch08s04.html | 18 +
.../0.1/html/RPM_Guide/ch09s02.html | 52 +
.../0.1/html/RPM_Guide/ch09s02s02.html | 82 +
.../0.1/html/RPM_Guide/ch09s03.html | 142 +
.../0.1/html/RPM_Guide/ch09s03s02.html | 33 +
.../0.1/html/RPM_Guide/ch09s03s03.html | 48 +
.../0.1/html/RPM_Guide/ch09s03s04.html | 42 +
.../0.1/html/RPM_Guide/ch09s04.html | 162 +
.../0.1/html/RPM_Guide/ch09s04s02.html | 81 +
.../0.1/html/RPM_Guide/ch09s04s03.html | 73 +
.../0.1/html/RPM_Guide/ch09s04s04.html | 16 +
.../0.1/html/RPM_Guide/ch09s04s05.html | 100 +
.../0.1/html/RPM_Guide/ch09s05.html | 32 +
.../0.1/html/RPM_Guide/ch09s05s02.html | 34 +
.../0.1/html/RPM_Guide/ch09s05s03.html | 72 +
.../0.1/html/RPM_Guide/ch09s05s04.html | 85 +
.../0.1/html/RPM_Guide/ch09s05s05.html | 130 +
.../0.1/html/RPM_Guide/ch09s05s06.html | 28 +
.../0.1/html/RPM_Guide/ch09s05s07.html | 28 +
.../0.1/html/RPM_Guide/ch09s06.html | 23 +
.../0.1/html/RPM_Guide/ch09s07.html | 61 +
.../0.1/html/RPM_Guide/ch09s07s02.html | 148 +
.../0.1/html/RPM_Guide/ch09s07s03.html | 30 +
.../0.1/html/RPM_Guide/ch09s07s04.html | 140 +
.../0.1/html/RPM_Guide/ch09s08.html | 132 +
.../0.1/html/RPM_Guide/ch09s09.html | 24 +
.../0.1/html/RPM_Guide/ch10s02.html | 259 +
.../0.1/html/RPM_Guide/ch10s03.html | 28 +
.../0.1/html/RPM_Guide/ch10s04.html | 110 +
.../0.1/html/RPM_Guide/ch10s04s02.html | 46 +
.../0.1/html/RPM_Guide/ch10s04s03.html | 22 +
.../0.1/html/RPM_Guide/ch10s05.html | 34 +
.../0.1/html/RPM_Guide/ch10s05s02.html | 38 +
.../0.1/html/RPM_Guide/ch10s05s03.html | 20 +
.../0.1/html/RPM_Guide/ch10s06.html | 44 +
.../0.1/html/RPM_Guide/ch10s06s02.html | 60 +
.../0.1/html/RPM_Guide/ch10s06s03.html | 91 +
.../0.1/html/RPM_Guide/ch10s07.html | 26 +
.../0.1/html/RPM_Guide/ch11s02.html | 106 +
.../0.1/html/RPM_Guide/ch11s02s02.html | 30 +
.../0.1/html/RPM_Guide/ch11s03.html | 206 +
.../0.1/html/RPM_Guide/ch11s03s02.html | 24 +
.../0.1/html/RPM_Guide/ch11s03s03.html | 14 +
.../0.1/html/RPM_Guide/ch11s04.html | 30 +
.../0.1/html/RPM_Guide/ch11s04s02.html | 146 +
.../0.1/html/RPM_Guide/ch11s04s03.html | 20 +
.../0.1/html/RPM_Guide/ch11s04s04.html | 18 +
.../0.1/html/RPM_Guide/ch11s04s05.html | 102 +
.../0.1/html/RPM_Guide/ch11s04s06.html | 96 +
.../0.1/html/RPM_Guide/ch11s04s07.html | 22 +
.../0.1/html/RPM_Guide/ch11s05.html | 19 +
.../0.1/html/RPM_Guide/ch12s02.html | 22 +
.../0.1/html/RPM_Guide/ch13s02.html | 68 +
.../0.1/html/RPM_Guide/ch13s02s02.html | 32 +
.../0.1/html/RPM_Guide/ch13s02s02s02.html | 16 +
.../0.1/html/RPM_Guide/ch13s02s02s03.html | 18 +
.../0.1/html/RPM_Guide/ch13s02s02s04.html | 14 +
.../0.1/html/RPM_Guide/ch13s02s02s05.html | 22 +
.../0.1/html/RPM_Guide/ch13s02s02s06.html | 14 +
.../0.1/html/RPM_Guide/ch13s02s02s07.html | 14 +
.../0.1/html/RPM_Guide/ch13s03.html | 22 +
.../0.1/html/RPM_Guide/ch14s02.html | 50 +
.../0.1/html/RPM_Guide/ch14s03.html | 30 +
.../0.1/html/RPM_Guide/ch14s04.html | 26 +
.../0.1/html/RPM_Guide/ch14s04s02.html | 58 +
.../0.1/html/RPM_Guide/ch14s04s03.html | 16 +
.../0.1/html/RPM_Guide/ch14s04s04.html | 126 +
.../0.1/html/RPM_Guide/ch14s04s05.html | 197 +
.../0.1/html/RPM_Guide/ch14s05.html | 94 +
.../0.1/html/RPM_Guide/ch14s06.html | 40 +
.../0.1/html/RPM_Guide/ch14s06s02.html | 35 +
.../0.1/html/RPM_Guide/ch14s07.html | 18 +
.../0.1/html/RPM_Guide/ch14s08.html | 16 +
.../0.1/html/RPM_Guide/ch15s02.html | 34 +
.../0.1/html/RPM_Guide/ch15s02s02.html | 297 +
.../0.1/html/RPM_Guide/ch15s02s02s02.html | 38 +
.../0.1/html/RPM_Guide/ch15s02s02s03.html | 26 +
.../0.1/html/RPM_Guide/ch15s02s02s04.html | 32 +
.../0.1/html/RPM_Guide/ch15s02s02s05.html | 98 +
.../0.1/html/RPM_Guide/ch15s02s02s06.html | 44 +
.../0.1/html/RPM_Guide/ch15s02s03.html | 40 +
.../0.1/html/RPM_Guide/ch15s02s04.html | 231 +
.../0.1/html/RPM_Guide/ch15s02s05.html | 50 +
.../0.1/html/RPM_Guide/ch15s03.html | 28 +
.../0.1/html/RPM_Guide/ch15s03s02.html | 90 +
.../0.1/html/RPM_Guide/ch15s03s03.html | 145 +
.../0.1/html/RPM_Guide/ch15s03s04.html | 28 +
.../0.1/html/RPM_Guide/ch15s03s05.html | 20 +
.../0.1/html/RPM_Guide/ch15s04.html | 136 +
.../0.1/html/RPM_Guide/ch15s04s02.html | 64 +
.../0.1/html/RPM_Guide/ch15s05.html | 541 +
.../0.1/html/RPM_Guide/ch15s06.html | 18 +
.../0.1/html/RPM_Guide/ch15s07.html | 20 +
.../0.1/html/RPM_Guide/ch16s02.html | 100 +
.../0.1/html/RPM_Guide/ch16s03.html | 80 +
.../0.1/html/RPM_Guide/ch16s03s02.html | 130 +
.../0.1/html/RPM_Guide/ch16s03s03.html | 60 +
.../0.1/html/RPM_Guide/ch16s03s03s02.html | 34 +
.../0.1/html/RPM_Guide/ch16s03s04.html | 59 +
.../0.1/html/RPM_Guide/ch16s03s05.html | 180 +
.../0.1/html/RPM_Guide/ch16s03s06.html | 157 +
.../0.1/html/RPM_Guide/ch16s04.html | 87 +
.../0.1/html/RPM_Guide/ch16s04s02.html | 130 +
.../0.1/html/RPM_Guide/ch16s05.html | 92 +
.../0.1/html/RPM_Guide/ch16s06.html | 39 +
.../0.1/html/RPM_Guide/ch16s06s02.html | 203 +
.../0.1/html/RPM_Guide/ch16s06s03.html | 42 +
.../0.1/html/RPM_Guide/ch16s06s03s02.html | 64 +
.../0.1/html/RPM_Guide/ch16s06s03s03.html | 16 +
.../0.1/html/RPM_Guide/ch16s06s04.html | 210 +
.../0.1/html/RPM_Guide/ch16s06s04s02.html | 40 +
.../0.1/html/RPM_Guide/ch16s06s04s03.html | 236 +
.../0.1/html/RPM_Guide/ch16s07.html | 22 +
.../0.1/html/RPM_Guide/ch16s08.html | 20 +
.../0.1/html/RPM_Guide/ch17s02.html | 24 +
.../0.1/html/RPM_Guide/ch17s02s02.html | 61 +
.../0.1/html/RPM_Guide/ch17s02s03.html | 14 +
.../0.1/html/RPM_Guide/ch17s02s04.html | 24 +
.../0.1/html/RPM_Guide/ch17s02s05.html | 49 +
.../0.1/html/RPM_Guide/ch17s03.html | 28 +
.../0.1/html/RPM_Guide/ch17s03s02.html | 14 +
.../0.1/html/RPM_Guide/ch17s03s03.html | 68 +
.../0.1/html/RPM_Guide/ch17s03s04.html | 231 +
.../0.1/html/RPM_Guide/ch17s03s05.html | 167 +
.../0.1/html/RPM_Guide/ch17s03s05s02.html | 77 +
.../0.1/html/RPM_Guide/ch17s03s05s03.html | 103 +
.../0.1/html/RPM_Guide/ch17s03s06.html | 102 +
.../0.1/html/RPM_Guide/ch17s03s07.html | 16 +
.../0.1/html/RPM_Guide/ch17s04.html | 28 +
.../0.1/html/RPM_Guide/ch17s05.html | 18 +
.../0.1/html/RPM_Guide/ch18s02.html | 56 +
.../0.1/html/RPM_Guide/ch18s02s02.html | 30 +
.../0.1/html/RPM_Guide/ch18s02s03.html | 16 +
.../0.1/html/RPM_Guide/ch18s02s04.html | 24 +
.../0.1/html/RPM_Guide/ch18s02s05.html | 44 +
.../0.1/html/RPM_Guide/ch18s02s05s02.html | 83 +
.../0.1/html/RPM_Guide/ch18s02s05s03.html | 32 +
.../0.1/html/RPM_Guide/ch18s02s05s04.html | 13 +
.../0.1/html/RPM_Guide/ch18s03.html | 18 +
.../0.1/html/RPM_Guide/ch18s04.html | 22 +
.../0.1/html/RPM_Guide/ch18s04s02.html | 16 +
.../0.1/html/RPM_Guide/ch18s05.html | 20 +
.../0.1/html/RPM_Guide/ch19s02.html | 22 +
.../0.1/html/RPM_Guide/ch19s02s02.html | 26 +
.../0.1/html/RPM_Guide/ch19s02s03.html | 16 +
.../0.1/html/RPM_Guide/ch19s02s04.html | 96 +
.../0.1/html/RPM_Guide/ch19s02s05.html | 70 +
.../0.1/html/RPM_Guide/ch19s02s06.html | 40 +
.../0.1/html/RPM_Guide/ch19s02s07.html | 30 +
.../0.1/html/RPM_Guide/ch19s03.html | 178 +
.../0.1/html/RPM_Guide/ch19s03s02.html | 53 +
.../0.1/html/RPM_Guide/ch19s04.html | 40 +
.../0.1/html/RPM_Guide/ch19s04s02.html | 64 +
.../0.1/html/RPM_Guide/ch19s05.html | 24 +
.../0.1/html/RPM_Guide/ch20s02.html | 49 +
.../0.1/html/RPM_Guide/ch20s02s02.html | 82 +
.../0.1/html/RPM_Guide/ch20s02s03.html | 36 +
.../0.1/html/RPM_Guide/ch20s02s03s02.html | 88 +
.../0.1/html/RPM_Guide/ch20s03.html | 92 +
.../0.1/html/RPM_Guide/ch20s03s02.html | 36 +
.../0.1/html/RPM_Guide/ch20s04.html | 14 +
.../0.1/html/RPM_Guide/ch21s02.html | 98 +
.../0.1/html/RPM_Guide/ch21s02s02.html | 96 +
.../0.1/html/RPM_Guide/ch21s02s03.html | 46 +
.../0.1/html/RPM_Guide/ch21s02s04.html | 235 +
.../0.1/html/RPM_Guide/ch22s02.html | 166 +
.../0.1/html/RPM_Guide/ch22s02s02.html | 66 +
.../0.1/html/RPM_Guide/ch22s02s03.html | 40 +
.../0.1/html/RPM_Guide/ch22s03.html | 18 +
.../0.1/html/RPM_Guide/ch22s03s02.html | 18 +
.../0.1/html/RPM_Guide/ch22s03s03.html | 18 +
.../0.1/html/RPM_Guide/ch22s03s04.html | 16 +
.../0.1/html/RPM_Guide/ch22s03s05.html | 40 +
.../0.1/html/RPM_Guide/ch22s04.html | 50 +
.../0.1/html/RPM_Guide/ch22s05.html | 23 +
.../0.1/html/RPM_Guide/ch25s02.html | 16 +
.../0.1/html/RPM_Guide/ch26s02.html | 18 +
.../0.1/html/RPM_Guide/ch26s03.html | 24 +
.../0.1/html/RPM_Guide/ch26s04.html | 32 +
.../0.1/html/RPM_Guide/index.html | 35 +
.../0.1/html/RPM_Guide/ix01.html | 10 +
.../0.1/html/RPM_Guide/pr01s02.html | 20 +
.../0.1/html/RPM_Guide/pr01s02s02.html | 24 +
.../0.1/html/RPM_Guide/pr01s03.html | 50 +
.../0.1/html/RPM_Guide/pr01s04.html | 14 +
...Fedora_Draft_Documentation-0.1-RPM_Guide-ro.pdf | Bin 0 -> 1735396 bytes
public_html/ro/Site_Statistics.html | 419 +
public_html/ro/opds-Fedora.xml | 1257 ++
.../ro/opds-Fedora_Contributor_Documentation.xml | 73 +
public_html/ro/opds-Fedora_Core.xml | 195 +
public_html/ro/opds-Fedora_Draft_Documentation.xml | 110 +
public_html/ro/opds.xml | 47 +
public_html/ro/toc.html | 1179 +
public_html/ru-RU/Site_Statistics.html | 13 +-
public_html/ru-RU/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 6 +-
public_html/ru-RU/opds-Fedora_Core.xml | 2 +-
.../ru-RU/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/ru-RU/opds.xml | 10 +-
public_html/ru-RU/toc.html | 11 +-
public_html/sk-SK/Site_Statistics.html | 13 +-
public_html/sk-SK/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 6 +-
public_html/sk-SK/opds-Fedora_Core.xml | 2 +-
.../sk-SK/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/sk-SK/opds.xml | 10 +-
public_html/sk-SK/toc.html | 11 +-
public_html/sr-Latn-RS/Site_Statistics.html | 13 +-
public_html/sr-Latn-RS/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 6 +-
public_html/sr-Latn-RS/opds-Fedora_Core.xml | 2 +-
.../sr-Latn-RS/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/sr-Latn-RS/opds.xml | 10 +-
public_html/sr-Latn-RS/toc.html | 9 +-
public_html/sr-RS/Site_Statistics.html | 13 +-
public_html/sr-RS/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 6 +-
public_html/sr-RS/opds-Fedora_Core.xml | 2 +-
.../sr-RS/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/sr-RS/opds.xml | 10 +-
public_html/sr-RS/toc.html | 9 +-
public_html/sv-SE/Site_Statistics.html | 13 +-
public_html/sv-SE/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 6 +-
public_html/sv-SE/opds-Fedora_Core.xml | 2 +-
.../sv-SE/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/sv-SE/opds.xml | 10 +-
public_html/sv-SE/toc.html | 13 +-
public_html/ta-IN/Site_Statistics.html | 13 +-
public_html/ta-IN/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 6 +-
public_html/ta-IN/opds-Fedora_Core.xml | 2 +-
.../ta-IN/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/ta-IN/opds.xml | 10 +-
public_html/ta-IN/toc.html | 11 +-
public_html/te-IN/Site_Statistics.html | 13 +-
public_html/te-IN/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 6 +-
public_html/te-IN/opds-Fedora_Core.xml | 2 +-
.../te-IN/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/te-IN/opds.xml | 10 +-
public_html/te-IN/toc.html | 11 +-
public_html/toc.html | 49 +-
public_html/uk-UA/Site_Statistics.html | 13 +-
public_html/uk-UA/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 6 +-
public_html/uk-UA/opds-Fedora_Core.xml | 2 +-
.../uk-UA/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/uk-UA/opds.xml | 10 +-
public_html/uk-UA/toc.html | 9 +-
public_html/zh-CN/Site_Statistics.html | 13 +-
public_html/zh-CN/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 6 +-
public_html/zh-CN/opds-Fedora_Core.xml | 2 +-
.../zh-CN/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/zh-CN/opds.xml | 10 +-
public_html/zh-CN/toc.html | 11 +-
public_html/zh-TW/Site_Statistics.html | 13 +-
public_html/zh-TW/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 6 +-
public_html/zh-TW/opds-Fedora_Core.xml | 2 +-
.../zh-TW/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/zh-TW/opds.xml | 10 +-
public_html/zh-TW/toc.html | 11 +-
835 files changed, 60258 insertions(+), 813 deletions(-)
---
diff --git a/fedoradocs.db b/fedoradocs.db
index d72390d..b9432a2 100644
Binary files a/fedoradocs.db and b/fedoradocs.db differ
diff --git a/public_html/Sitemap b/public_html/Sitemap
index 148ee62..a46a04e 100644
--- a/public_html/Sitemap
+++ b/public_html/Sitemap
@@ -1963,7 +1963,7 @@
<priority>0.8</priority>
</url>
<url>
- <loc>http://docs.fedoraproject.org/en-US/Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-en-US.pdf</loc>
+ <loc>http://docs.fedoraproject.org/en-US/Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.pdf</loc>
<lastmod>2010-07-23</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
@@ -2755,7 +2755,7 @@
<priority>0.8</priority>
</url>
<url>
- <loc>http://docs.fedoraproject.org/en-US/Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf</loc>
+ <loc>http://docs.fedoraproject.org/en-US/Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf</loc>
<lastmod>2009-11-17</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
@@ -3019,7 +3019,7 @@
<priority>0.8</priority>
</url>
<url>
- <loc>http://docs.fedoraproject.org/en-US/Fedora/8/pdf/Installation_Guide/Fedora-9-Installation_Guide-en-US.pdf</loc>
+ <loc>http://docs.fedoraproject.org/en-US/Fedora/8/pdf/Installation_Guide/Fedora-8-Installation_Guide-en-US.pdf</loc>
<lastmod>2008-05-13</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
@@ -3193,7 +3193,7 @@
<priority>0.8</priority>
</url>
<url>
- <loc>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub</loc>
+ <loc>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub</loc>
<lastmod>2010-11-23</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
@@ -3259,7 +3259,7 @@
<priority>0.8</priority>
</url>
<url>
- <loc>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf</loc>
+ <loc>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf</loc>
<lastmod>2010-07-07</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
@@ -3973,7 +3973,7 @@
<priority>0.8</priority>
</url>
<url>
- <loc>http://docs.fedoraproject.org/es-ES/Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-es-ES.pdf</loc>
+ <loc>http://docs.fedoraproject.org/es-ES/Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-es-ES.pdf</loc>
<lastmod>2010-05-22</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
@@ -4645,7 +4645,7 @@
<priority>0.8</priority>
</url>
<url>
- <loc>http://docs.fedoraproject.org/es-ES/Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-es-ES.pdf</loc>
+ <loc>http://docs.fedoraproject.org/es-ES/Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-es-ES.pdf</loc>
<lastmod>2010-06-13</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
@@ -8635,7 +8635,7 @@
<priority>0.8</priority>
</url>
<url>
- <loc>http://docs.fedoraproject.org/nl-NL/Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-nl-NL.pdf</loc>
+ <loc>http://docs.fedoraproject.org/nl-NL/Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-nl-NL.pdf</loc>
<lastmod>2010-05-22</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
@@ -11905,6 +11905,30 @@
<priority>0.8</priority>
</url>
<url>
+ <loc>http://docs.fedoraproject.org/ro/Fedora_Draft_Documentation/0.1/epub/RPM_Guide/Fedora_Draft_Documentation-0.1-RPM_Guide-ro.epub</loc>
+ <lastmod>2011-08-22</lastmod>
+ <changefreq>monthly</changefreq>
+ <priority>0.8</priority>
+</url>
+<url>
+ <loc>http://docs.fedoraproject.org/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html</loc>
+ <lastmod>2011-08-22</lastmod>
+ <changefreq>monthly</changefreq>
+ <priority>0.8</priority>
+</url>
+<url>
+ <loc>http://docs.fedoraproject.org/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/index.html</loc>
+ <lastmod>2011-08-22</lastmod>
+ <changefreq>monthly</changefreq>
+ <priority>0.8</priority>
+</url>
+<url>
+ <loc>http://docs.fedoraproject.org/ro/Fedora_Draft_Documentation/0.1/pdf/RPM_Guide/Fedora_Draft_Documentation-0.1-RPM_Guide-ro.pdf</loc>
+ <lastmod>2011-08-22</lastmod>
+ <changefreq>monthly</changefreq>
+ <priority>0.8</priority>
+</url>
+<url>
<loc>http://docs.fedoraproject.org/ru-RU/Fedora/15/html/Fedora_Live_Images/index.html</loc>
<lastmod>2011-08-16</lastmod>
<changefreq>monthly</changefreq>
@@ -11983,7 +12007,7 @@
<priority>0.8</priority>
</url>
<url>
- <loc>http://docs.fedoraproject.org/ru-RU/Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-ru-RU.pdf</loc>
+ <loc>http://docs.fedoraproject.org/ru-RU/Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-ru-RU.pdf</loc>
<lastmod>2010-05-22</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
diff --git a/public_html/as-IN/Site_Statistics.html b/public_html/as-IN/Site_Statistics.html
index e17799c..5501668 100644
--- a/public_html/as-IN/Site_Statistics.html
+++ b/public_html/as-IN/Site_Statistics.html
@@ -392,6 +392,15 @@
</tr>
<tr>
+ <td>Romanian</td>
+ <td>ro</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ </tr>
+
+ <tr>
<td>Tamil</td>
<td>ta-IN</td>
<td>1</td>
@@ -402,8 +411,8 @@
</table>
<div class="totals">
- <b>Total Languages: </b>42<br />
- <b>Total Packages: </b>673
+ <b>Total Languages: </b>43<br />
+ <b>Total Packages: </b>674
</div>
</body>
</html>
diff --git a/public_html/as-IN/opds-Fedora.xml b/public_html/as-IN/opds-Fedora.xml
index 6029084..ce7a1b0 100644
--- a/public_html/as-IN/opds-Fedora.xml
+++ b/public_html/as-IN/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/as-IN/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2011-08-17T11:44:21</updated>
+ <updated>2011-08-22T23:04:43</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/as-IN/opds-Fedora_Contributor_Documentation.xml b/public_html/as-IN/opds-Fedora_Contributor_Documentation.xml
index feaf3ea..77ed36d 100644
--- a/public_html/as-IN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/as-IN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/as-IN/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2011-08-17T11:44:21</updated>
+ <updated>2011-08-22T23:04:43</updated>
<!--author>
<name></name>
<uri></uri>
@@ -14,7 +14,7 @@
<entry>
<title>Fedora Elections Guide</title>
- <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub</id>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub</id>
<!--author>
<name></name>
<uri></uri>
@@ -26,7 +26,7 @@
<summary>Fedora Elections Guide
</summary>
<content type="text">This book covers procedural information for the use the Fedora Elections software</content>
- <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub">
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub">
<dc:format>application/epub+zip</dc:format>
</link>
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
diff --git a/public_html/as-IN/opds-Fedora_Core.xml b/public_html/as-IN/opds-Fedora_Core.xml
index 63a5fca..478802f 100644
--- a/public_html/as-IN/opds-Fedora_Core.xml
+++ b/public_html/as-IN/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/as-IN/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2011-08-17T11:44:21</updated>
+ <updated>2011-08-22T23:04:43</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/as-IN/opds-Fedora_Draft_Documentation.xml b/public_html/as-IN/opds-Fedora_Draft_Documentation.xml
index b2f68d0..e2f974d 100644
--- a/public_html/as-IN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/as-IN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/as-IN/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2011-08-17T11:44:21</updated>
+ <updated>2011-08-22T23:04:43</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/as-IN/opds.xml b/public_html/as-IN/opds.xml
index fb817bc..2a42247 100644
--- a/public_html/as-IN/opds.xml
+++ b/public_html/as-IN/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/as-IN/opds.xml</id>
<title>Product List</title>
- <updated>2011-08-17T11:44:21</updated>
+ <updated>2011-08-22T23:04:43</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/as-IN/Fedora/opds-Fedora.xml</id>
- <updated>2011-08-17T11:44:21</updated>
+ <updated>2011-08-22T23:04:43</updated>
<dc:language>as-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/as-IN/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2011-08-17T11:44:21</updated>
+ <updated>2011-08-22T23:04:43</updated>
<dc:language>as-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/as-IN/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2011-08-17T11:44:21</updated>
+ <updated>2011-08-22T23:04:43</updated>
<dc:language>as-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/as-IN/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2011-08-17T11:44:21</updated>
+ <updated>2011-08-22T23:04:43</updated>
<dc:language>as-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/as-IN/toc.html b/public_html/as-IN/toc.html
index 9edba22..ae1bdaf 100644
--- a/public_html/as-IN/toc.html
+++ b/public_html/as-IN/toc.html
@@ -58,6 +58,7 @@
<option value="pl-PL">Polski</option>
<option value="pt-BR">Português Brasileiro</option>
<option value="pt-PT">Português</option>
+ <option value="ro">Romanian</option>
<option value="ru-RU">РуÑÑкий</option>
<option value="sk-SK">SlovenÅ¡Äina</option>
<option value="sr-Latn-RS">Srpski (latinica)</option>
@@ -292,7 +293,7 @@
<a class="type" href="../en-US/./Fedora/13/epub/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/13/html/Accessibility_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/13/html/Accessibility_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/13/html-single/Accessibility_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/13/html-single/Accessibility_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.13.Burning_ISO_images_to_disc' class="book collapsed" onclick="toggle(event, 'Fedora.13.Burning_ISO_images_to_disc.types');">
@@ -609,7 +610,7 @@
<a class="type" href="../en-US/./Fedora/11/epub/Security_Guide/Fedora-11-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/11/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/11/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.11.User_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.11.User_Guide.types');">
@@ -738,7 +739,7 @@
<a class="type" href="../en-US/./Fedora/8/epub/Installation_Guide/Fedora-8-Installation_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/8/html/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/8/html/Installation_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/8/html-single/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/8/html-single/Installation_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-9-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-9-Installation_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-8-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-8-Installation_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.8.Making_Fedora_Discs' class="book collapsed" onclick="toggle(event, 'Fedora.8.Making_Fedora_Discs.types');">
@@ -838,7 +839,7 @@
<div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Fedora_Elections_Guide.types');">
<a class="type" href="../en-US/Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html'"><span class="book">Fedora Elections Guide</span></a>
<div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide.types' class="types hidden" onclick="work=0;">
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
@@ -859,7 +860,7 @@
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/bg-BG/Site_Statistics.html b/public_html/bg-BG/Site_Statistics.html
index e17799c..5501668 100644
--- a/public_html/bg-BG/Site_Statistics.html
+++ b/public_html/bg-BG/Site_Statistics.html
@@ -392,6 +392,15 @@
</tr>
<tr>
+ <td>Romanian</td>
+ <td>ro</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ </tr>
+
+ <tr>
<td>Tamil</td>
<td>ta-IN</td>
<td>1</td>
@@ -402,8 +411,8 @@
</table>
<div class="totals">
- <b>Total Languages: </b>42<br />
- <b>Total Packages: </b>673
+ <b>Total Languages: </b>43<br />
+ <b>Total Packages: </b>674
</div>
</body>
</html>
diff --git a/public_html/bg-BG/opds-Fedora.xml b/public_html/bg-BG/opds-Fedora.xml
index ff42800..b6f58aa 100644
--- a/public_html/bg-BG/opds-Fedora.xml
+++ b/public_html/bg-BG/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bg-BG/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2011-08-17T11:44:21</updated>
+ <updated>2011-08-22T23:04:44</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bg-BG/opds-Fedora_Contributor_Documentation.xml b/public_html/bg-BG/opds-Fedora_Contributor_Documentation.xml
index 8d10f92..0b52416 100644
--- a/public_html/bg-BG/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/bg-BG/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bg-BG/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2011-08-17T11:44:21</updated>
+ <updated>2011-08-22T23:04:44</updated>
<!--author>
<name></name>
<uri></uri>
@@ -14,7 +14,7 @@
<entry>
<title>Fedora Elections Guide</title>
- <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub</id>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub</id>
<!--author>
<name></name>
<uri></uri>
@@ -26,7 +26,7 @@
<summary>Fedora Elections Guide
</summary>
<content type="text">This book covers procedural information for the use the Fedora Elections software</content>
- <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub">
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub">
<dc:format>application/epub+zip</dc:format>
</link>
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
diff --git a/public_html/bg-BG/opds-Fedora_Core.xml b/public_html/bg-BG/opds-Fedora_Core.xml
index 2f09c4a..7d91750 100644
--- a/public_html/bg-BG/opds-Fedora_Core.xml
+++ b/public_html/bg-BG/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bg-BG/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2011-08-17T11:44:21</updated>
+ <updated>2011-08-22T23:04:44</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bg-BG/opds-Fedora_Draft_Documentation.xml b/public_html/bg-BG/opds-Fedora_Draft_Documentation.xml
index c8b0c50..8f03b5c 100644
--- a/public_html/bg-BG/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/bg-BG/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bg-BG/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2011-08-17T11:44:21</updated>
+ <updated>2011-08-22T23:04:44</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bg-BG/opds.xml b/public_html/bg-BG/opds.xml
index 1d3ecca..99e2c3c 100644
--- a/public_html/bg-BG/opds.xml
+++ b/public_html/bg-BG/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/bg-BG/opds.xml</id>
<title>Product List</title>
- <updated>2011-08-17T11:44:21</updated>
+ <updated>2011-08-22T23:04:44</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/bg-BG/Fedora/opds-Fedora.xml</id>
- <updated>2011-08-17T11:44:21</updated>
+ <updated>2011-08-22T23:04:44</updated>
<dc:language>bg-BG</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/bg-BG/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2011-08-17T11:44:21</updated>
+ <updated>2011-08-22T23:04:44</updated>
<dc:language>bg-BG</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/bg-BG/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2011-08-17T11:44:21</updated>
+ <updated>2011-08-22T23:04:44</updated>
<dc:language>bg-BG</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/bg-BG/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2011-08-17T11:44:21</updated>
+ <updated>2011-08-22T23:04:44</updated>
<dc:language>bg-BG</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/bg-BG/toc.html b/public_html/bg-BG/toc.html
index a848344..89dff1b 100644
--- a/public_html/bg-BG/toc.html
+++ b/public_html/bg-BG/toc.html
@@ -58,6 +58,7 @@
<option value="pl-PL">Polski</option>
<option value="pt-BR">Português Brasileiro</option>
<option value="pt-PT">Português</option>
+ <option value="ro">Romanian</option>
<option value="ru-RU">РуÑÑкий</option>
<option value="sk-SK">SlovenÅ¡Äina</option>
<option value="sr-Latn-RS">Srpski (latinica)</option>
@@ -289,7 +290,7 @@
<a class="type" href="../en-US/./Fedora/13/epub/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/13/html/Accessibility_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/13/html/Accessibility_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/13/html-single/Accessibility_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/13/html-single/Accessibility_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.13.Burning_ISO_images_to_disc' class="book collapsed" onclick="toggle(event, 'Fedora.13.Burning_ISO_images_to_disc.types');">
@@ -606,7 +607,7 @@
<a class="type" href="../en-US/./Fedora/11/epub/Security_Guide/Fedora-11-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/11/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/11/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.11.User_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.11.User_Guide.types');">
@@ -735,7 +736,7 @@
<a class="type" href="../en-US/./Fedora/8/epub/Installation_Guide/Fedora-8-Installation_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/8/html/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/8/html/Installation_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/8/html-single/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/8/html-single/Installation_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-9-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-9-Installation_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-8-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-8-Installation_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.8.Making_Fedora_Discs' class="book collapsed" onclick="toggle(event, 'Fedora.8.Making_Fedora_Discs.types');">
@@ -835,7 +836,7 @@
<div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Fedora_Elections_Guide.types');">
<a class="type" href="../en-US/Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html'"><span class="book">Fedora Elections Guide</span></a>
<div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide.types' class="types hidden" onclick="work=0;">
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
@@ -856,7 +857,7 @@
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/bn-IN/Site_Statistics.html b/public_html/bn-IN/Site_Statistics.html
index e17799c..5501668 100644
--- a/public_html/bn-IN/Site_Statistics.html
+++ b/public_html/bn-IN/Site_Statistics.html
@@ -392,6 +392,15 @@
</tr>
<tr>
+ <td>Romanian</td>
+ <td>ro</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ </tr>
+
+ <tr>
<td>Tamil</td>
<td>ta-IN</td>
<td>1</td>
@@ -402,8 +411,8 @@
</table>
<div class="totals">
- <b>Total Languages: </b>42<br />
- <b>Total Packages: </b>673
+ <b>Total Languages: </b>43<br />
+ <b>Total Packages: </b>674
</div>
</body>
</html>
diff --git a/public_html/bn-IN/opds-Fedora.xml b/public_html/bn-IN/opds-Fedora.xml
index 4787ebf..4cf77e5 100644
--- a/public_html/bn-IN/opds-Fedora.xml
+++ b/public_html/bn-IN/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bn-IN/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2011-08-17T11:44:21</updated>
+ <updated>2011-08-22T23:04:44</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bn-IN/opds-Fedora_Contributor_Documentation.xml b/public_html/bn-IN/opds-Fedora_Contributor_Documentation.xml
index 2714998..b8bdbd1 100644
--- a/public_html/bn-IN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/bn-IN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bn-IN/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2011-08-17T11:44:21</updated>
+ <updated>2011-08-22T23:04:44</updated>
<!--author>
<name></name>
<uri></uri>
@@ -14,7 +14,7 @@
<entry>
<title>Fedora Elections Guide</title>
- <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub</id>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub</id>
<!--author>
<name></name>
<uri></uri>
@@ -26,7 +26,7 @@
<summary>Fedora Elections Guide
</summary>
<content type="text">This book covers procedural information for the use the Fedora Elections software</content>
- <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub">
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub">
<dc:format>application/epub+zip</dc:format>
</link>
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
diff --git a/public_html/bn-IN/opds-Fedora_Core.xml b/public_html/bn-IN/opds-Fedora_Core.xml
index b4aa1fb..19af2fd 100644
--- a/public_html/bn-IN/opds-Fedora_Core.xml
+++ b/public_html/bn-IN/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bn-IN/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2011-08-17T11:44:21</updated>
+ <updated>2011-08-22T23:04:44</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bn-IN/opds-Fedora_Draft_Documentation.xml b/public_html/bn-IN/opds-Fedora_Draft_Documentation.xml
index 22c0e37..edb9b4d 100644
--- a/public_html/bn-IN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/bn-IN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bn-IN/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2011-08-17T11:44:21</updated>
+ <updated>2011-08-22T23:04:44</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bn-IN/opds.xml b/public_html/bn-IN/opds.xml
index b082575..d186ab0 100644
--- a/public_html/bn-IN/opds.xml
+++ b/public_html/bn-IN/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/bn-IN/opds.xml</id>
<title>Product List</title>
- <updated>2011-08-17T11:44:21</updated>
+ <updated>2011-08-22T23:04:44</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/bn-IN/Fedora/opds-Fedora.xml</id>
- <updated>2011-08-17T11:44:21</updated>
+ <updated>2011-08-22T23:04:44</updated>
<dc:language>bn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/bn-IN/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2011-08-17T11:44:21</updated>
+ <updated>2011-08-22T23:04:44</updated>
<dc:language>bn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/bn-IN/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2011-08-17T11:44:21</updated>
+ <updated>2011-08-22T23:04:44</updated>
<dc:language>bn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/bn-IN/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2011-08-17T11:44:21</updated>
+ <updated>2011-08-22T23:04:44</updated>
<dc:language>bn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/bn-IN/toc.html b/public_html/bn-IN/toc.html
index 6a49bc9..876cc3c 100644
--- a/public_html/bn-IN/toc.html
+++ b/public_html/bn-IN/toc.html
@@ -58,6 +58,7 @@
<option value="pl-PL">Polski</option>
<option value="pt-BR">Português Brasileiro</option>
<option value="pt-PT">Português</option>
+ <option value="ro">Romanian</option>
<option value="ru-RU">РуÑÑкий</option>
<option value="sk-SK">SlovenÅ¡Äina</option>
<option value="sr-Latn-RS">Srpski (latinica)</option>
@@ -292,7 +293,7 @@
<a class="type" href="../en-US/./Fedora/13/epub/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/13/html/Accessibility_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/13/html/Accessibility_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/13/html-single/Accessibility_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/13/html-single/Accessibility_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.13.Burning_ISO_images_to_disc' class="book collapsed" onclick="toggle(event, 'Fedora.13.Burning_ISO_images_to_disc.types');">
@@ -609,7 +610,7 @@
<a class="type" href="../en-US/./Fedora/11/epub/Security_Guide/Fedora-11-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/11/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/11/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.11.User_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.11.User_Guide.types');">
@@ -738,7 +739,7 @@
<a class="type" href="../en-US/./Fedora/8/epub/Installation_Guide/Fedora-8-Installation_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/8/html/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/8/html/Installation_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/8/html-single/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/8/html-single/Installation_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-9-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-9-Installation_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-8-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-8-Installation_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.8.Making_Fedora_Discs' class="book collapsed" onclick="toggle(event, 'Fedora.8.Making_Fedora_Discs.types');">
@@ -838,7 +839,7 @@
<div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Fedora_Elections_Guide.types');">
<a class="type" href="../en-US/Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html'"><span class="book">Fedora Elections Guide</span></a>
<div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide.types' class="types hidden" onclick="work=0;">
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
@@ -859,7 +860,7 @@
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/bs-BA/Site_Statistics.html b/public_html/bs-BA/Site_Statistics.html
index e17799c..5501668 100644
--- a/public_html/bs-BA/Site_Statistics.html
+++ b/public_html/bs-BA/Site_Statistics.html
@@ -392,6 +392,15 @@
</tr>
<tr>
+ <td>Romanian</td>
+ <td>ro</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ </tr>
+
+ <tr>
<td>Tamil</td>
<td>ta-IN</td>
<td>1</td>
@@ -402,8 +411,8 @@
</table>
<div class="totals">
- <b>Total Languages: </b>42<br />
- <b>Total Packages: </b>673
+ <b>Total Languages: </b>43<br />
+ <b>Total Packages: </b>674
</div>
</body>
</html>
diff --git a/public_html/bs-BA/opds-Fedora.xml b/public_html/bs-BA/opds-Fedora.xml
index f9d9ee0..63d4246 100644
--- a/public_html/bs-BA/opds-Fedora.xml
+++ b/public_html/bs-BA/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bs-BA/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2011-08-17T11:44:21</updated>
+ <updated>2011-08-22T23:04:44</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bs-BA/opds-Fedora_Contributor_Documentation.xml b/public_html/bs-BA/opds-Fedora_Contributor_Documentation.xml
index 907d902..7e6f169 100644
--- a/public_html/bs-BA/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/bs-BA/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bs-BA/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2011-08-17T11:44:21</updated>
+ <updated>2011-08-22T23:04:44</updated>
<!--author>
<name></name>
<uri></uri>
@@ -14,7 +14,7 @@
<entry>
<title>Fedora Elections Guide</title>
- <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub</id>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub</id>
<!--author>
<name></name>
<uri></uri>
@@ -26,7 +26,7 @@
<summary>Fedora Elections Guide
</summary>
<content type="text">This book covers procedural information for the use the Fedora Elections software</content>
- <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub">
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub">
<dc:format>application/epub+zip</dc:format>
</link>
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
diff --git a/public_html/bs-BA/opds-Fedora_Core.xml b/public_html/bs-BA/opds-Fedora_Core.xml
index 7940ce7..5e3315a 100644
--- a/public_html/bs-BA/opds-Fedora_Core.xml
+++ b/public_html/bs-BA/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bs-BA/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2011-08-17T11:44:21</updated>
+ <updated>2011-08-22T23:04:44</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bs-BA/opds-Fedora_Draft_Documentation.xml b/public_html/bs-BA/opds-Fedora_Draft_Documentation.xml
index 3f7f867..eb8b5ac 100644
--- a/public_html/bs-BA/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/bs-BA/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bs-BA/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2011-08-17T11:44:21</updated>
+ <updated>2011-08-22T23:04:44</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bs-BA/opds.xml b/public_html/bs-BA/opds.xml
index aeb5da3..d3de3ab 100644
--- a/public_html/bs-BA/opds.xml
+++ b/public_html/bs-BA/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/bs-BA/opds.xml</id>
<title>Product List</title>
- <updated>2011-08-17T11:44:21</updated>
+ <updated>2011-08-22T23:04:44</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/bs-BA/Fedora/opds-Fedora.xml</id>
- <updated>2011-08-17T11:44:21</updated>
+ <updated>2011-08-22T23:04:44</updated>
<dc:language>bs-BA</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/bs-BA/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2011-08-17T11:44:21</updated>
+ <updated>2011-08-22T23:04:44</updated>
<dc:language>bs-BA</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/bs-BA/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2011-08-17T11:44:21</updated>
+ <updated>2011-08-22T23:04:44</updated>
<dc:language>bs-BA</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/bs-BA/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2011-08-17T11:44:21</updated>
+ <updated>2011-08-22T23:04:44</updated>
<dc:language>bs-BA</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/bs-BA/toc.html b/public_html/bs-BA/toc.html
index 8e9c784..f8a5b6d 100644
--- a/public_html/bs-BA/toc.html
+++ b/public_html/bs-BA/toc.html
@@ -58,6 +58,7 @@
<option value="pl-PL">Polski</option>
<option value="pt-BR">Português Brasileiro</option>
<option value="pt-PT">Português</option>
+ <option value="ro">Romanian</option>
<option value="ru-RU">РуÑÑкий</option>
<option value="sk-SK">SlovenÅ¡Äina</option>
<option value="sr-Latn-RS">Srpski (latinica)</option>
@@ -292,7 +293,7 @@
<a class="type" href="../en-US/./Fedora/13/epub/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/13/html/Accessibility_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/13/html/Accessibility_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/13/html-single/Accessibility_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/13/html-single/Accessibility_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.13.Burning_ISO_images_to_disc' class="book collapsed" onclick="toggle(event, 'Fedora.13.Burning_ISO_images_to_disc.types');">
@@ -618,7 +619,7 @@
<a class="type" href="../en-US/./Fedora/11/epub/Security_Guide/Fedora-11-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/11/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/11/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
@@ -738,7 +739,7 @@
<a class="type" href="../en-US/./Fedora/8/epub/Installation_Guide/Fedora-8-Installation_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/8/html/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/8/html/Installation_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/8/html-single/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/8/html-single/Installation_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-9-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-9-Installation_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-8-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-8-Installation_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.8.Making_Fedora_Discs' class="book collapsed" onclick="toggle(event, 'Fedora.8.Making_Fedora_Discs.types');">
@@ -838,7 +839,7 @@
<div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Fedora_Elections_Guide.types');">
<a class="type" href="../en-US/Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html'"><span class="book">Fedora Elections Guide</span></a>
<div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide.types' class="types hidden" onclick="work=0;">
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
@@ -859,7 +860,7 @@
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/ca-ES/Site_Statistics.html b/public_html/ca-ES/Site_Statistics.html
index e17799c..5501668 100644
--- a/public_html/ca-ES/Site_Statistics.html
+++ b/public_html/ca-ES/Site_Statistics.html
@@ -392,6 +392,15 @@
</tr>
<tr>
+ <td>Romanian</td>
+ <td>ro</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ </tr>
+
+ <tr>
<td>Tamil</td>
<td>ta-IN</td>
<td>1</td>
@@ -402,8 +411,8 @@
</table>
<div class="totals">
- <b>Total Languages: </b>42<br />
- <b>Total Packages: </b>673
+ <b>Total Languages: </b>43<br />
+ <b>Total Packages: </b>674
</div>
</body>
</html>
diff --git a/public_html/ca-ES/opds-Fedora.xml b/public_html/ca-ES/opds-Fedora.xml
index 9bae372..d91e8ce 100644
--- a/public_html/ca-ES/opds-Fedora.xml
+++ b/public_html/ca-ES/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ca-ES/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2011-08-17T11:44:21</updated>
+ <updated>2011-08-22T23:04:44</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ca-ES/opds-Fedora_Contributor_Documentation.xml b/public_html/ca-ES/opds-Fedora_Contributor_Documentation.xml
index ac19543..a0b8e98 100644
--- a/public_html/ca-ES/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/ca-ES/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ca-ES/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2011-08-17T11:44:22</updated>
+ <updated>2011-08-22T23:04:44</updated>
<!--author>
<name></name>
<uri></uri>
@@ -14,7 +14,7 @@
<entry>
<title>Fedora Elections Guide</title>
- <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub</id>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub</id>
<!--author>
<name></name>
<uri></uri>
@@ -26,7 +26,7 @@
<summary>Fedora Elections Guide
</summary>
<content type="text">This book covers procedural information for the use the Fedora Elections software</content>
- <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub">
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub">
<dc:format>application/epub+zip</dc:format>
</link>
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
diff --git a/public_html/ca-ES/opds-Fedora_Core.xml b/public_html/ca-ES/opds-Fedora_Core.xml
index 30f6b43..07b014f 100644
--- a/public_html/ca-ES/opds-Fedora_Core.xml
+++ b/public_html/ca-ES/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ca-ES/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2011-08-17T11:44:22</updated>
+ <updated>2011-08-22T23:04:44</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ca-ES/opds-Fedora_Draft_Documentation.xml b/public_html/ca-ES/opds-Fedora_Draft_Documentation.xml
index 9d62bd1..2cda0ea 100644
--- a/public_html/ca-ES/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/ca-ES/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ca-ES/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2011-08-17T11:44:22</updated>
+ <updated>2011-08-22T23:04:44</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ca-ES/opds.xml b/public_html/ca-ES/opds.xml
index e9a9f8f..617d460 100644
--- a/public_html/ca-ES/opds.xml
+++ b/public_html/ca-ES/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/ca-ES/opds.xml</id>
<title>Product List</title>
- <updated>2011-08-17T11:44:22</updated>
+ <updated>2011-08-22T23:04:44</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/ca-ES/Fedora/opds-Fedora.xml</id>
- <updated>2011-08-17T11:44:22</updated>
+ <updated>2011-08-22T23:04:44</updated>
<dc:language>ca-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/ca-ES/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2011-08-17T11:44:22</updated>
+ <updated>2011-08-22T23:04:44</updated>
<dc:language>ca-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/ca-ES/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2011-08-17T11:44:22</updated>
+ <updated>2011-08-22T23:04:44</updated>
<dc:language>ca-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/ca-ES/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2011-08-17T11:44:22</updated>
+ <updated>2011-08-22T23:04:44</updated>
<dc:language>ca-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/ca-ES/toc.html b/public_html/ca-ES/toc.html
index dc43627..34241da 100644
--- a/public_html/ca-ES/toc.html
+++ b/public_html/ca-ES/toc.html
@@ -58,6 +58,7 @@
<option value="pl-PL">Polski</option>
<option value="pt-BR">Português Brasileiro</option>
<option value="pt-PT">Português</option>
+ <option value="ro">Romanian</option>
<option value="ru-RU">РуÑÑкий</option>
<option value="sk-SK">SlovenÅ¡Äina</option>
<option value="sr-Latn-RS">Srpski (latinica)</option>
@@ -291,7 +292,7 @@
<a class="type" href="../en-US/./Fedora/13/epub/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/13/html/Accessibility_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/13/html/Accessibility_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/13/html-single/Accessibility_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/13/html-single/Accessibility_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.13.Burning_ISO_images_to_disc' class="book collapsed" onclick="toggle(event, 'Fedora.13.Burning_ISO_images_to_disc.types');">
@@ -608,7 +609,7 @@
<a class="type" href="../en-US/./Fedora/11/epub/Security_Guide/Fedora-11-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/11/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/11/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.11.User_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.11.User_Guide.types');">
@@ -737,7 +738,7 @@
<a class="type" href="../en-US/./Fedora/8/epub/Installation_Guide/Fedora-8-Installation_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/8/html/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/8/html/Installation_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/8/html-single/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/8/html-single/Installation_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-9-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-9-Installation_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-8-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-8-Installation_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.8.Making_Fedora_Discs' class="book collapsed" onclick="toggle(event, 'Fedora.8.Making_Fedora_Discs.types');">
@@ -837,7 +838,7 @@
<div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Fedora_Elections_Guide.types');">
<a class="type" href="../en-US/Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html'"><span class="book">Fedora Elections Guide</span></a>
<div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide.types' class="types hidden" onclick="work=0;">
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
@@ -858,7 +859,7 @@
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/cs-CZ/Site_Statistics.html b/public_html/cs-CZ/Site_Statistics.html
index e17799c..5501668 100644
--- a/public_html/cs-CZ/Site_Statistics.html
+++ b/public_html/cs-CZ/Site_Statistics.html
@@ -392,6 +392,15 @@
</tr>
<tr>
+ <td>Romanian</td>
+ <td>ro</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ </tr>
+
+ <tr>
<td>Tamil</td>
<td>ta-IN</td>
<td>1</td>
@@ -402,8 +411,8 @@
</table>
<div class="totals">
- <b>Total Languages: </b>42<br />
- <b>Total Packages: </b>673
+ <b>Total Languages: </b>43<br />
+ <b>Total Packages: </b>674
</div>
</body>
</html>
diff --git a/public_html/cs-CZ/opds-Fedora.xml b/public_html/cs-CZ/opds-Fedora.xml
index 6d47574..780bdad 100644
--- a/public_html/cs-CZ/opds-Fedora.xml
+++ b/public_html/cs-CZ/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/cs-CZ/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2011-08-17T11:44:22</updated>
+ <updated>2011-08-22T23:04:44</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/cs-CZ/opds-Fedora_Contributor_Documentation.xml b/public_html/cs-CZ/opds-Fedora_Contributor_Documentation.xml
index 73259fb..977fafb 100644
--- a/public_html/cs-CZ/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/cs-CZ/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/cs-CZ/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2011-08-17T11:44:22</updated>
+ <updated>2011-08-22T23:04:44</updated>
<!--author>
<name></name>
<uri></uri>
@@ -14,7 +14,7 @@
<entry>
<title>Fedora Elections Guide</title>
- <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub</id>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub</id>
<!--author>
<name></name>
<uri></uri>
@@ -26,7 +26,7 @@
<summary>Fedora Elections Guide
</summary>
<content type="text">This book covers procedural information for the use the Fedora Elections software</content>
- <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub">
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub">
<dc:format>application/epub+zip</dc:format>
</link>
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
diff --git a/public_html/cs-CZ/opds-Fedora_Core.xml b/public_html/cs-CZ/opds-Fedora_Core.xml
index c20ff5b..947c460 100644
--- a/public_html/cs-CZ/opds-Fedora_Core.xml
+++ b/public_html/cs-CZ/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/cs-CZ/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2011-08-17T11:44:22</updated>
+ <updated>2011-08-22T23:04:44</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/cs-CZ/opds-Fedora_Draft_Documentation.xml b/public_html/cs-CZ/opds-Fedora_Draft_Documentation.xml
index a05252e..2337688 100644
--- a/public_html/cs-CZ/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/cs-CZ/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/cs-CZ/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2011-08-17T11:44:22</updated>
+ <updated>2011-08-22T23:04:44</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/cs-CZ/opds.xml b/public_html/cs-CZ/opds.xml
index 52edb67..a861a63 100644
--- a/public_html/cs-CZ/opds.xml
+++ b/public_html/cs-CZ/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/cs-CZ/opds.xml</id>
<title>Product List</title>
- <updated>2011-08-17T11:44:22</updated>
+ <updated>2011-08-22T23:04:44</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/cs-CZ/Fedora/opds-Fedora.xml</id>
- <updated>2011-08-17T11:44:22</updated>
+ <updated>2011-08-22T23:04:44</updated>
<dc:language>cs-CZ</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/cs-CZ/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2011-08-17T11:44:22</updated>
+ <updated>2011-08-22T23:04:44</updated>
<dc:language>cs-CZ</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/cs-CZ/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2011-08-17T11:44:22</updated>
+ <updated>2011-08-22T23:04:44</updated>
<dc:language>cs-CZ</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/cs-CZ/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2011-08-17T11:44:22</updated>
+ <updated>2011-08-22T23:04:44</updated>
<dc:language>cs-CZ</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/cs-CZ/toc.html b/public_html/cs-CZ/toc.html
index ce60b32..e42baeb 100644
--- a/public_html/cs-CZ/toc.html
+++ b/public_html/cs-CZ/toc.html
@@ -58,6 +58,7 @@
<option value="pl-PL">Polski</option>
<option value="pt-BR">Português Brasileiro</option>
<option value="pt-PT">Português</option>
+ <option value="ro">Romanian</option>
<option value="ru-RU">РуÑÑкий</option>
<option value="sk-SK">SlovenÅ¡Äina</option>
<option value="sr-Latn-RS">Srpski (latinica)</option>
@@ -318,7 +319,7 @@
<a class="type" href="../en-US/./Fedora/13/epub/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/13/html/Accessibility_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/13/html/Accessibility_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/13/html-single/Accessibility_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/13/html-single/Accessibility_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.13.Fedora_Live_Images' class="book collapsed" onclick="toggle(event, 'Fedora.13.Fedora_Live_Images.types');">
@@ -608,7 +609,7 @@
<a class="type" href="../en-US/./Fedora/11/epub/Security_Guide/Fedora-11-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/11/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/11/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.11.User_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.11.User_Guide.types');">
@@ -737,7 +738,7 @@
<a class="type" href="../en-US/./Fedora/8/epub/Installation_Guide/Fedora-8-Installation_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/8/html/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/8/html/Installation_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/8/html-single/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/8/html-single/Installation_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-9-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-9-Installation_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-8-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-8-Installation_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.8.Making_Fedora_Discs' class="book collapsed" onclick="toggle(event, 'Fedora.8.Making_Fedora_Discs.types');">
@@ -837,7 +838,7 @@
<div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Fedora_Elections_Guide.types');">
<a class="type" href="../en-US/Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html'"><span class="book">Fedora Elections Guide</span></a>
<div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide.types' class="types hidden" onclick="work=0;">
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
@@ -858,7 +859,7 @@
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/da-DK/Site_Statistics.html b/public_html/da-DK/Site_Statistics.html
index e17799c..5501668 100644
--- a/public_html/da-DK/Site_Statistics.html
+++ b/public_html/da-DK/Site_Statistics.html
@@ -392,6 +392,15 @@
</tr>
<tr>
+ <td>Romanian</td>
+ <td>ro</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ </tr>
+
+ <tr>
<td>Tamil</td>
<td>ta-IN</td>
<td>1</td>
@@ -402,8 +411,8 @@
</table>
<div class="totals">
- <b>Total Languages: </b>42<br />
- <b>Total Packages: </b>673
+ <b>Total Languages: </b>43<br />
+ <b>Total Packages: </b>674
</div>
</body>
</html>
diff --git a/public_html/da-DK/opds-Fedora.xml b/public_html/da-DK/opds-Fedora.xml
index d610055..21ab251 100644
--- a/public_html/da-DK/opds-Fedora.xml
+++ b/public_html/da-DK/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/da-DK/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2011-08-17T11:44:22</updated>
+ <updated>2011-08-22T23:04:45</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/da-DK/opds-Fedora_Contributor_Documentation.xml b/public_html/da-DK/opds-Fedora_Contributor_Documentation.xml
index c3535a8..0b6bf09 100644
--- a/public_html/da-DK/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/da-DK/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/da-DK/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2011-08-17T11:44:22</updated>
+ <updated>2011-08-22T23:04:45</updated>
<!--author>
<name></name>
<uri></uri>
@@ -14,7 +14,7 @@
<entry>
<title>Fedora Elections Guide</title>
- <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub</id>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub</id>
<!--author>
<name></name>
<uri></uri>
@@ -26,7 +26,7 @@
<summary>Fedora Elections Guide
</summary>
<content type="text">This book covers procedural information for the use the Fedora Elections software</content>
- <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub">
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub">
<dc:format>application/epub+zip</dc:format>
</link>
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
diff --git a/public_html/da-DK/opds-Fedora_Core.xml b/public_html/da-DK/opds-Fedora_Core.xml
index 47e8d1a..6a2a2de 100644
--- a/public_html/da-DK/opds-Fedora_Core.xml
+++ b/public_html/da-DK/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/da-DK/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2011-08-17T11:44:22</updated>
+ <updated>2011-08-22T23:04:45</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/da-DK/opds-Fedora_Draft_Documentation.xml b/public_html/da-DK/opds-Fedora_Draft_Documentation.xml
index 84225cb..7a3f20e 100644
--- a/public_html/da-DK/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/da-DK/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/da-DK/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2011-08-17T11:44:22</updated>
+ <updated>2011-08-22T23:04:45</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/da-DK/opds.xml b/public_html/da-DK/opds.xml
index 23908a6..2784aca 100644
--- a/public_html/da-DK/opds.xml
+++ b/public_html/da-DK/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/da-DK/opds.xml</id>
<title>Product List</title>
- <updated>2011-08-17T11:44:22</updated>
+ <updated>2011-08-22T23:04:45</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/da-DK/Fedora/opds-Fedora.xml</id>
- <updated>2011-08-17T11:44:22</updated>
+ <updated>2011-08-22T23:04:45</updated>
<dc:language>da-DK</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/da-DK/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2011-08-17T11:44:22</updated>
+ <updated>2011-08-22T23:04:45</updated>
<dc:language>da-DK</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/da-DK/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2011-08-17T11:44:22</updated>
+ <updated>2011-08-22T23:04:45</updated>
<dc:language>da-DK</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/da-DK/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2011-08-17T11:44:22</updated>
+ <updated>2011-08-22T23:04:45</updated>
<dc:language>da-DK</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/da-DK/toc.html b/public_html/da-DK/toc.html
index 7b533fd..e7ddce8 100644
--- a/public_html/da-DK/toc.html
+++ b/public_html/da-DK/toc.html
@@ -58,6 +58,7 @@
<option value="pl-PL">Polski</option>
<option value="pt-BR">Português Brasileiro</option>
<option value="pt-PT">Português</option>
+ <option value="ro">Romanian</option>
<option value="ru-RU">РуÑÑкий</option>
<option value="sk-SK">SlovenÅ¡Äina</option>
<option value="sr-Latn-RS">Srpski (latinica)</option>
@@ -292,7 +293,7 @@
<a class="type" href="../en-US/./Fedora/13/epub/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/13/html/Accessibility_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/13/html/Accessibility_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/13/html-single/Accessibility_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/13/html-single/Accessibility_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.13.Burning_ISO_images_to_disc' class="book collapsed" onclick="toggle(event, 'Fedora.13.Burning_ISO_images_to_disc.types');">
@@ -609,7 +610,7 @@
<a class="type" href="../en-US/./Fedora/11/epub/Security_Guide/Fedora-11-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/11/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/11/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.11.User_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.11.User_Guide.types');">
@@ -738,7 +739,7 @@
<a class="type" href="../en-US/./Fedora/8/epub/Installation_Guide/Fedora-8-Installation_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/8/html/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/8/html/Installation_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/8/html-single/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/8/html-single/Installation_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-9-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-9-Installation_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-8-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-8-Installation_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.8.Making_Fedora_Discs' class="book collapsed" onclick="toggle(event, 'Fedora.8.Making_Fedora_Discs.types');">
@@ -838,7 +839,7 @@
<div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Fedora_Elections_Guide.types');">
<a class="type" href="../en-US/Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html'"><span class="book">Fedora Elections Guide</span></a>
<div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide.types' class="types hidden" onclick="work=0;">
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
@@ -859,7 +860,7 @@
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/de-DE/Site_Statistics.html b/public_html/de-DE/Site_Statistics.html
index c5ccec6..df03c19 100644
--- a/public_html/de-DE/Site_Statistics.html
+++ b/public_html/de-DE/Site_Statistics.html
@@ -392,6 +392,15 @@
</tr>
<tr>
+ <td>Romanian</td>
+ <td>ro</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ </tr>
+
+ <tr>
<td>Tamil</td>
<td>ta-IN</td>
<td>1</td>
@@ -402,8 +411,8 @@
</table>
<div class="totals">
- <b>Sprachen gesamt: </b>42<br />
- <b>Pakete gesamt: </b>673
+ <b>Sprachen gesamt: </b>43<br />
+ <b>Pakete gesamt: </b>674
</div>
</body>
</html>
diff --git a/public_html/de-DE/opds-Fedora.xml b/public_html/de-DE/opds-Fedora.xml
index 56c59b6..cb60982 100644
--- a/public_html/de-DE/opds-Fedora.xml
+++ b/public_html/de-DE/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/de-DE/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2011-08-17T11:44:22</updated>
+ <updated>2011-08-22T23:04:45</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/de-DE/opds-Fedora_Contributor_Documentation.xml b/public_html/de-DE/opds-Fedora_Contributor_Documentation.xml
index 4e84eb6..494eb80 100644
--- a/public_html/de-DE/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/de-DE/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/de-DE/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2011-08-17T11:44:22</updated>
+ <updated>2011-08-22T23:04:45</updated>
<!--author>
<name></name>
<uri></uri>
@@ -14,7 +14,7 @@
<entry>
<title>Fedora Elections Guide</title>
- <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub</id>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub</id>
<!--author>
<name></name>
<uri></uri>
@@ -26,7 +26,7 @@
<summary>Fedora Elections Guide
</summary>
<content type="text">This book covers procedural information for the use the Fedora Elections software</content>
- <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub">
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub">
<dc:format>application/epub+zip</dc:format>
</link>
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
diff --git a/public_html/de-DE/opds-Fedora_Core.xml b/public_html/de-DE/opds-Fedora_Core.xml
index 2e84e9e..807ccae 100644
--- a/public_html/de-DE/opds-Fedora_Core.xml
+++ b/public_html/de-DE/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/de-DE/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2011-08-17T11:44:22</updated>
+ <updated>2011-08-22T23:04:45</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/de-DE/opds-Fedora_Draft_Documentation.xml b/public_html/de-DE/opds-Fedora_Draft_Documentation.xml
index 1dd4336..83ab4ac 100644
--- a/public_html/de-DE/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/de-DE/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/de-DE/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2011-08-17T11:44:22</updated>
+ <updated>2011-08-22T23:04:45</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/de-DE/opds.xml b/public_html/de-DE/opds.xml
index bbb04e2..a4ebc00 100644
--- a/public_html/de-DE/opds.xml
+++ b/public_html/de-DE/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/de-DE/opds.xml</id>
<title>Product List</title>
- <updated>2011-08-17T11:44:22</updated>
+ <updated>2011-08-22T23:04:45</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/de-DE/Fedora/opds-Fedora.xml</id>
- <updated>2011-08-17T11:44:22</updated>
+ <updated>2011-08-22T23:04:45</updated>
<dc:language>de-DE</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/de-DE/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2011-08-17T11:44:22</updated>
+ <updated>2011-08-22T23:04:45</updated>
<dc:language>de-DE</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/de-DE/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2011-08-17T11:44:22</updated>
+ <updated>2011-08-22T23:04:45</updated>
<dc:language>de-DE</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/de-DE/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2011-08-17T11:44:22</updated>
+ <updated>2011-08-22T23:04:45</updated>
<dc:language>de-DE</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/de-DE/toc.html b/public_html/de-DE/toc.html
index 1e11098..a2ac481 100644
--- a/public_html/de-DE/toc.html
+++ b/public_html/de-DE/toc.html
@@ -58,6 +58,7 @@
<option value="pl-PL">Polski</option>
<option value="pt-BR">Português Brasileiro</option>
<option value="pt-PT">Português</option>
+ <option value="ro">Romanian</option>
<option value="ru-RU">РуÑÑкий</option>
<option value="sk-SK">SlovenÅ¡Äina</option>
<option value="sr-Latn-RS">Srpski (latinica)</option>
@@ -309,7 +310,7 @@
<a class="type" href="../en-US/./Fedora/13/epub/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/13/html/Accessibility_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/13/html/Accessibility_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/13/html-single/Accessibility_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/13/html-single/Accessibility_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.13.Installation_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.13.Installation_Guide.types');">
@@ -608,7 +609,7 @@
<a class="type" href="../en-US/./Fedora/11/epub/Security_Guide/Fedora-11-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/11/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/11/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.11.User_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.11.User_Guide.types');">
@@ -708,7 +709,7 @@
<a class="type" href="../en-US/./Fedora/10/epub/Security_Guide/Fedora-11-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/10/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/10/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/10/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/10/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/10/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/10/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/10/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/10/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.10.User_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.10.User_Guide.types');">
@@ -809,7 +810,7 @@
<a class="type" href="../en-US/./Fedora/8/epub/Installation_Guide/Fedora-8-Installation_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/8/html/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/8/html/Installation_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/8/html-single/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/8/html-single/Installation_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-9-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-9-Installation_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-8-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-8-Installation_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.8.SELinux_FAQ' class="book collapsed" onclick="toggle(event, 'Fedora.8.SELinux_FAQ.types');">
@@ -891,7 +892,7 @@
<div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Fedora_Elections_Guide.types');">
<a class="type" href="../en-US/Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html'"><span class="book">Fedora Elections Guide</span></a>
<div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide.types' class="types hidden" onclick="work=0;">
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
@@ -912,7 +913,7 @@
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/el-GR/Site_Statistics.html b/public_html/el-GR/Site_Statistics.html
index e17799c..5501668 100644
--- a/public_html/el-GR/Site_Statistics.html
+++ b/public_html/el-GR/Site_Statistics.html
@@ -392,6 +392,15 @@
</tr>
<tr>
+ <td>Romanian</td>
+ <td>ro</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ </tr>
+
+ <tr>
<td>Tamil</td>
<td>ta-IN</td>
<td>1</td>
@@ -402,8 +411,8 @@
</table>
<div class="totals">
- <b>Total Languages: </b>42<br />
- <b>Total Packages: </b>673
+ <b>Total Languages: </b>43<br />
+ <b>Total Packages: </b>674
</div>
</body>
</html>
diff --git a/public_html/el-GR/opds-Fedora.xml b/public_html/el-GR/opds-Fedora.xml
index f211e5c..921a8c0 100644
--- a/public_html/el-GR/opds-Fedora.xml
+++ b/public_html/el-GR/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/el-GR/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2011-08-17T11:44:22</updated>
+ <updated>2011-08-22T23:04:45</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/el-GR/opds-Fedora_Contributor_Documentation.xml b/public_html/el-GR/opds-Fedora_Contributor_Documentation.xml
index 1751568..041d083 100644
--- a/public_html/el-GR/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/el-GR/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/el-GR/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2011-08-17T11:44:22</updated>
+ <updated>2011-08-22T23:04:45</updated>
<!--author>
<name></name>
<uri></uri>
@@ -14,7 +14,7 @@
<entry>
<title>Fedora Elections Guide</title>
- <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub</id>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub</id>
<!--author>
<name></name>
<uri></uri>
@@ -26,7 +26,7 @@
<summary>Fedora Elections Guide
</summary>
<content type="text">This book covers procedural information for the use the Fedora Elections software</content>
- <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub">
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub">
<dc:format>application/epub+zip</dc:format>
</link>
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
diff --git a/public_html/el-GR/opds-Fedora_Core.xml b/public_html/el-GR/opds-Fedora_Core.xml
index 25f3753..f9c7545 100644
--- a/public_html/el-GR/opds-Fedora_Core.xml
+++ b/public_html/el-GR/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/el-GR/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2011-08-17T11:44:22</updated>
+ <updated>2011-08-22T23:04:45</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/el-GR/opds-Fedora_Draft_Documentation.xml b/public_html/el-GR/opds-Fedora_Draft_Documentation.xml
index c002469..56b6ae7 100644
--- a/public_html/el-GR/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/el-GR/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/el-GR/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2011-08-17T11:44:22</updated>
+ <updated>2011-08-22T23:04:45</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/el-GR/opds.xml b/public_html/el-GR/opds.xml
index 8c2633b..12541d4 100644
--- a/public_html/el-GR/opds.xml
+++ b/public_html/el-GR/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/el-GR/opds.xml</id>
<title>Product List</title>
- <updated>2011-08-17T11:44:23</updated>
+ <updated>2011-08-22T23:04:45</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/el-GR/Fedora/opds-Fedora.xml</id>
- <updated>2011-08-17T11:44:22</updated>
+ <updated>2011-08-22T23:04:45</updated>
<dc:language>el-GR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/el-GR/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2011-08-17T11:44:22</updated>
+ <updated>2011-08-22T23:04:45</updated>
<dc:language>el-GR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/el-GR/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2011-08-17T11:44:22</updated>
+ <updated>2011-08-22T23:04:45</updated>
<dc:language>el-GR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/el-GR/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2011-08-17T11:44:22</updated>
+ <updated>2011-08-22T23:04:45</updated>
<dc:language>el-GR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/el-GR/toc.html b/public_html/el-GR/toc.html
index eae3e08..f0353fe 100644
--- a/public_html/el-GR/toc.html
+++ b/public_html/el-GR/toc.html
@@ -58,6 +58,7 @@
<option value="pl-PL">Polski</option>
<option value="pt-BR">Português Brasileiro</option>
<option value="pt-PT">Português</option>
+ <option value="ro">Romanian</option>
<option value="ru-RU">РуÑÑкий</option>
<option value="sk-SK">SlovenÅ¡Äina</option>
<option value="sr-Latn-RS">Srpski (latinica)</option>
@@ -292,7 +293,7 @@
<a class="type" href="../en-US/./Fedora/13/epub/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/13/html/Accessibility_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/13/html/Accessibility_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/13/html-single/Accessibility_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/13/html-single/Accessibility_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.13.Burning_ISO_images_to_disc' class="book collapsed" onclick="toggle(event, 'Fedora.13.Burning_ISO_images_to_disc.types');">
@@ -609,7 +610,7 @@
<a class="type" href="../en-US/./Fedora/11/epub/Security_Guide/Fedora-11-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/11/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/11/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.11.User_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.11.User_Guide.types');">
@@ -838,7 +839,7 @@
<div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Fedora_Elections_Guide.types');">
<a class="type" href="../en-US/Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html'"><span class="book">Fedora Elections Guide</span></a>
<div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide.types' class="types hidden" onclick="work=0;">
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
@@ -859,7 +860,7 @@
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/en-US/Site_Statistics.html b/public_html/en-US/Site_Statistics.html
index e17799c..5501668 100644
--- a/public_html/en-US/Site_Statistics.html
+++ b/public_html/en-US/Site_Statistics.html
@@ -392,6 +392,15 @@
</tr>
<tr>
+ <td>Romanian</td>
+ <td>ro</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ </tr>
+
+ <tr>
<td>Tamil</td>
<td>ta-IN</td>
<td>1</td>
@@ -402,8 +411,8 @@
</table>
<div class="totals">
- <b>Total Languages: </b>42<br />
- <b>Total Packages: </b>673
+ <b>Total Languages: </b>43<br />
+ <b>Total Packages: </b>674
</div>
</body>
</html>
diff --git a/public_html/en-US/opds-Fedora.xml b/public_html/en-US/opds-Fedora.xml
index 51d7a3d..17450f9 100644
--- a/public_html/en-US/opds-Fedora.xml
+++ b/public_html/en-US/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/en-US/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2011-08-17T11:44:23</updated>
+ <updated>2011-08-22T23:04:45</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/en-US/opds-Fedora_Contributor_Documentation.xml b/public_html/en-US/opds-Fedora_Contributor_Documentation.xml
index 78bb4a4..669e24b 100644
--- a/public_html/en-US/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/en-US/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/en-US/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2011-08-17T11:44:23</updated>
+ <updated>2011-08-22T23:04:45</updated>
<!--author>
<name></name>
<uri></uri>
@@ -14,7 +14,7 @@
<entry>
<title>Fedora Elections Guide</title>
- <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub</id>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub</id>
<!--author>
<name></name>
<uri></uri>
@@ -26,7 +26,7 @@
<summary>Fedora Elections Guide
</summary>
<content type="text">This book covers procedural information for the use the Fedora Elections software</content>
- <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub">
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub">
<dc:format>application/epub+zip</dc:format>
</link>
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
diff --git a/public_html/en-US/opds-Fedora_Core.xml b/public_html/en-US/opds-Fedora_Core.xml
index ed8668a..64b6116 100644
--- a/public_html/en-US/opds-Fedora_Core.xml
+++ b/public_html/en-US/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/en-US/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2011-08-17T11:44:23</updated>
+ <updated>2011-08-22T23:04:45</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/en-US/opds-Fedora_Draft_Documentation.xml b/public_html/en-US/opds-Fedora_Draft_Documentation.xml
index 958fb94..f178ff7 100644
--- a/public_html/en-US/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/en-US/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/en-US/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2011-08-17T11:44:23</updated>
+ <updated>2011-08-22T23:04:45</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/en-US/opds.xml b/public_html/en-US/opds.xml
index ad6c953..4edd24b 100644
--- a/public_html/en-US/opds.xml
+++ b/public_html/en-US/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/en-US/opds.xml</id>
<title>Product List</title>
- <updated>2011-08-17T11:44:23</updated>
+ <updated>2011-08-22T23:04:45</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/en-US/Fedora/opds-Fedora.xml</id>
- <updated>2011-08-17T11:44:23</updated>
+ <updated>2011-08-22T23:04:45</updated>
<dc:language>en-US</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2011-08-17T11:44:23</updated>
+ <updated>2011-08-22T23:04:45</updated>
<dc:language>en-US</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/en-US/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2011-08-17T11:44:23</updated>
+ <updated>2011-08-22T23:04:45</updated>
<dc:language>en-US</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2011-08-17T11:44:23</updated>
+ <updated>2011-08-22T23:04:45</updated>
<dc:language>en-US</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/en-US/toc.html b/public_html/en-US/toc.html
index 832bd43..d6abe01 100644
--- a/public_html/en-US/toc.html
+++ b/public_html/en-US/toc.html
@@ -58,6 +58,7 @@
<option value="pl-PL">Polski</option>
<option value="pt-BR">Português Brasileiro</option>
<option value="pt-PT">Português</option>
+ <option value="ro">Romanian</option>
<option value="ru-RU">РуÑÑкий</option>
<option value="sk-SK">SlovenÅ¡Äina</option>
<option value="sr-Latn-RS">Srpski (latinica)</option>
@@ -279,7 +280,7 @@
<a class="type" href="./Fedora/13/epub/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.epub" >epub</a>
<a class="type" href="./Fedora/13/html/Accessibility_Guide/index.html" onclick="window.top.location='./Fedora/13/html/Accessibility_Guide/index.html';return false;">html</a>
<a class="type" href="./Fedora/13/html-single/Accessibility_Guide/index.html" onclick="window.top.location='./Fedora/13/html-single/Accessibility_Guide/index.html';return false;">html-single</a>
- <a class="type" href="./Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-en-US.pdf" onclick="window.top.location='./Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.pdf" onclick="window.top.location='./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.13.Burning_ISO_images_to_disc' class="book collapsed">
@@ -586,7 +587,7 @@
<a class="type" href="./Fedora/11/epub/Security_Guide/Fedora-11-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="./Fedora/11/html/Security_Guide/index.html" onclick="window.top.location='./Fedora/11/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="./Fedora/11/html-single/Security_Guide/index.html" onclick="window.top.location='./Fedora/11/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.11.User_Guide' class="book collapsed">
@@ -700,7 +701,7 @@
<a class="type" href="./Fedora/8/epub/Installation_Guide/Fedora-8-Installation_Guide-en-US.epub" >epub</a>
<a class="type" href="./Fedora/8/html/Installation_Guide/index.html" onclick="window.top.location='./Fedora/8/html/Installation_Guide/index.html';return false;">html</a>
<a class="type" href="./Fedora/8/html-single/Installation_Guide/index.html" onclick="window.top.location='./Fedora/8/html-single/Installation_Guide/index.html';return false;">html-single</a>
- <a class="type" href="./Fedora/8/pdf/Installation_Guide/Fedora-9-Installation_Guide-en-US.pdf" onclick="window.top.location='./Fedora/8/pdf/Installation_Guide/Fedora-9-Installation_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="./Fedora/8/pdf/Installation_Guide/Fedora-8-Installation_Guide-en-US.pdf" onclick="window.top.location='./Fedora/8/pdf/Installation_Guide/Fedora-8-Installation_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.8.Making_Fedora_Discs' class="book collapsed">
@@ -785,7 +786,7 @@
<div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide' class="book collapsed">
<a class="type" href="Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html'"><span class="book">Fedora Elections Guide</span></a>
<div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide.types' class="types" onclick="work=0;">
- <a class="type" href="./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub" >epub</a>
+ <a class="type" href="./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub" >epub</a>
<a class="type" href="./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
<a class="type" href="./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
<a class="type" href="./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
@@ -806,7 +807,7 @@
<a class="type" href="./Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub" >epub</a>
<a class="type" href="./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html" onclick="window.top.location='./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html';return false;">html</a>
<a class="type" href="./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html" onclick="window.top.location='./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html';return false;">html-single</a>
- <a class="type" href="./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf" onclick="window.top.location='./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf" onclick="window.top.location='./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/es-ES/Site_Statistics.html b/public_html/es-ES/Site_Statistics.html
index 5fdc5e4..94e3d2e 100644
--- a/public_html/es-ES/Site_Statistics.html
+++ b/public_html/es-ES/Site_Statistics.html
@@ -392,6 +392,15 @@
</tr>
<tr>
+ <td>Romanian</td>
+ <td>ro</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ </tr>
+
+ <tr>
<td>Tamil</td>
<td>ta-IN</td>
<td>1</td>
@@ -402,8 +411,8 @@
</table>
<div class="totals">
- <b>Idiomas totales: </b>42<br />
- <b>Paquetes totales: </b>673
+ <b>Idiomas totales: </b>43<br />
+ <b>Paquetes totales: </b>674
</div>
</body>
</html>
diff --git a/public_html/es-ES/opds-Fedora.xml b/public_html/es-ES/opds-Fedora.xml
index cd76160..713cd82 100644
--- a/public_html/es-ES/opds-Fedora.xml
+++ b/public_html/es-ES/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/es-ES/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2011-08-17T11:44:23</updated>
+ <updated>2011-08-22T23:04:46</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/es-ES/opds-Fedora_15.xml b/public_html/es-ES/opds-Fedora_15.xml
index 42b983c..b2d0b1c 100644
--- a/public_html/es-ES/opds-Fedora_15.xml
+++ b/public_html/es-ES/opds-Fedora_15.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/es-ES/opds-Fedora_15.xml</id>
<title>Fedora 15</title>
<subtitle>Fedora 15</subtitle>
- <updated>2011-08-17T11:44:23</updated>
+ <updated>2011-08-22T23:04:46</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/es-ES/opds-Fedora_Contributor_Documentation.xml b/public_html/es-ES/opds-Fedora_Contributor_Documentation.xml
index 6d3ceb1..0569a7c 100644
--- a/public_html/es-ES/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/es-ES/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/es-ES/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2011-08-17T11:44:23</updated>
+ <updated>2011-08-22T23:04:46</updated>
<!--author>
<name></name>
<uri></uri>
@@ -14,7 +14,7 @@
<entry>
<title>Fedora Elections Guide</title>
- <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub</id>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub</id>
<!--author>
<name></name>
<uri></uri>
@@ -26,7 +26,7 @@
<summary>Fedora Elections Guide
</summary>
<content type="text">This book covers procedural information for the use the Fedora Elections software</content>
- <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub">
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub">
<dc:format>application/epub+zip</dc:format>
</link>
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
diff --git a/public_html/es-ES/opds-Fedora_Core.xml b/public_html/es-ES/opds-Fedora_Core.xml
index 6121d1b..9995a81 100644
--- a/public_html/es-ES/opds-Fedora_Core.xml
+++ b/public_html/es-ES/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/es-ES/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2011-08-17T11:44:23</updated>
+ <updated>2011-08-22T23:04:46</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/es-ES/opds-Fedora_Draft_Documentation.xml b/public_html/es-ES/opds-Fedora_Draft_Documentation.xml
index 88ed29d..1e16e16 100644
--- a/public_html/es-ES/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/es-ES/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/es-ES/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2011-08-17T11:44:23</updated>
+ <updated>2011-08-22T23:04:46</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/es-ES/opds.xml b/public_html/es-ES/opds.xml
index 22eb8fb..09b173b 100644
--- a/public_html/es-ES/opds.xml
+++ b/public_html/es-ES/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/es-ES/opds.xml</id>
<title>Product List</title>
- <updated>2011-08-17T11:44:23</updated>
+ <updated>2011-08-22T23:04:46</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/es-ES/Fedora/opds-Fedora.xml</id>
- <updated>2011-08-17T11:44:23</updated>
+ <updated>2011-08-22T23:04:46</updated>
<dc:language>es-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora 15</title>
<id>http://docs.fedoraproject.org/es-ES/Fedora_15/opds-Fedora_15.xml</id>
- <updated>2011-08-17T11:44:23</updated>
+ <updated>2011-08-22T23:04:46</updated>
<dc:language>es-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_15.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/es-ES/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2011-08-17T11:44:23</updated>
+ <updated>2011-08-22T23:04:46</updated>
<dc:language>es-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/es-ES/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2011-08-17T11:44:23</updated>
+ <updated>2011-08-22T23:04:46</updated>
<dc:language>es-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/es-ES/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2011-08-17T11:44:23</updated>
+ <updated>2011-08-22T23:04:46</updated>
<dc:language>es-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/es-ES/toc.html b/public_html/es-ES/toc.html
index 2fff090..6e9f76a 100644
--- a/public_html/es-ES/toc.html
+++ b/public_html/es-ES/toc.html
@@ -58,6 +58,7 @@
<option value="pl-PL">Polski</option>
<option value="pt-BR">Português Brasileiro</option>
<option value="pt-PT">Português</option>
+ <option value="ro">Romanian</option>
<option value="ru-RU">РуÑÑкий</option>
<option value="sk-SK">SlovenÅ¡Äina</option>
<option value="sr-Latn-RS">Srpski (latinica)</option>
@@ -286,7 +287,7 @@
<a class="type" href="./Fedora/13/epub/Accessibility_Guide/Fedora-13-Accessibility_Guide-es-ES.epub" >epub</a>
<a class="type" href="./Fedora/13/html/Accessibility_Guide/index.html" onclick="window.top.location='./Fedora/13/html/Accessibility_Guide/index.html';return false;">html</a>
<a class="type" href="./Fedora/13/html-single/Accessibility_Guide/index.html" onclick="window.top.location='./Fedora/13/html-single/Accessibility_Guide/index.html';return false;">html-single</a>
- <a class="type" href="./Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-es-ES.pdf" onclick="window.top.location='./Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-es-ES.pdf';return false;">pdf</a>
+ <a class="type" href="./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-es-ES.pdf" onclick="window.top.location='./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-es-ES.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.13.Burning_ISO_images_to_disc' class="book collapsed">
@@ -648,7 +649,7 @@
<a class="type" href="./Fedora/11/epub/Security_Guide/Fedora-11-Security_Guide-es-ES.epub" >epub</a>
<a class="type" href="./Fedora/11/html/Security_Guide/index.html" onclick="window.top.location='./Fedora/11/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="./Fedora/11/html-single/Security_Guide/index.html" onclick="window.top.location='./Fedora/11/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-es-ES.pdf" onclick="window.top.location='./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-es-ES.pdf';return false;">pdf</a>
+ <a class="type" href="./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-es-ES.pdf" onclick="window.top.location='./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-es-ES.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.11.User_Guide' class="book collapsed">
@@ -996,7 +997,7 @@
<div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Fedora_Elections_Guide.types');">
<a class="type" href="../en-US/Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html'"><span class="book">Fedora Elections Guide</span></a>
<div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide.types' class="types hidden" onclick="work=0;">
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
@@ -1017,7 +1018,7 @@
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/fa-IR/Site_Statistics.html b/public_html/fa-IR/Site_Statistics.html
index e17799c..5501668 100644
--- a/public_html/fa-IR/Site_Statistics.html
+++ b/public_html/fa-IR/Site_Statistics.html
@@ -392,6 +392,15 @@
</tr>
<tr>
+ <td>Romanian</td>
+ <td>ro</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ </tr>
+
+ <tr>
<td>Tamil</td>
<td>ta-IN</td>
<td>1</td>
@@ -402,8 +411,8 @@
</table>
<div class="totals">
- <b>Total Languages: </b>42<br />
- <b>Total Packages: </b>673
+ <b>Total Languages: </b>43<br />
+ <b>Total Packages: </b>674
</div>
</body>
</html>
diff --git a/public_html/fa-IR/opds-Fedora.xml b/public_html/fa-IR/opds-Fedora.xml
index 2b8c818..1580641 100644
--- a/public_html/fa-IR/opds-Fedora.xml
+++ b/public_html/fa-IR/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/fa-IR/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2011-08-17T11:44:23</updated>
+ <updated>2011-08-22T23:04:46</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fa-IR/opds-Fedora_Contributor_Documentation.xml b/public_html/fa-IR/opds-Fedora_Contributor_Documentation.xml
index a1c5e7e..452aeaf 100644
--- a/public_html/fa-IR/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/fa-IR/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/fa-IR/opds-Fedora_Contributor_Documentation.xml</id>
<title>مستندات مشارکت کننده Ùدورا</title>
<subtitle>مستندات مشارکت کننده Ùدورا</subtitle>
- <updated>2011-08-17T11:44:23</updated>
+ <updated>2011-08-22T23:04:46</updated>
<!--author>
<name></name>
<uri></uri>
@@ -14,7 +14,7 @@
<entry>
<title>Fedora Elections Guide</title>
- <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub</id>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub</id>
<!--author>
<name></name>
<uri></uri>
@@ -26,7 +26,7 @@
<summary>Fedora Elections Guide
</summary>
<content type="text">This book covers procedural information for the use the Fedora Elections software</content>
- <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub">
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub">
<dc:format>application/epub+zip</dc:format>
</link>
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
diff --git a/public_html/fa-IR/opds-Fedora_Core.xml b/public_html/fa-IR/opds-Fedora_Core.xml
index 30e6d68..11bc209 100644
--- a/public_html/fa-IR/opds-Fedora_Core.xml
+++ b/public_html/fa-IR/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/fa-IR/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2011-08-17T11:44:23</updated>
+ <updated>2011-08-22T23:04:46</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fa-IR/opds-Fedora_Draft_Documentation.xml b/public_html/fa-IR/opds-Fedora_Draft_Documentation.xml
index d229b55..ed0f3eb 100644
--- a/public_html/fa-IR/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/fa-IR/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/fa-IR/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2011-08-17T11:44:23</updated>
+ <updated>2011-08-22T23:04:46</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fa-IR/opds.xml b/public_html/fa-IR/opds.xml
index a2f2d8d..ac079df 100644
--- a/public_html/fa-IR/opds.xml
+++ b/public_html/fa-IR/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/fa-IR/opds.xml</id>
<title>Product List</title>
- <updated>2011-08-17T11:44:23</updated>
+ <updated>2011-08-22T23:04:46</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/fa-IR/Fedora/opds-Fedora.xml</id>
- <updated>2011-08-17T11:44:23</updated>
+ <updated>2011-08-22T23:04:46</updated>
<dc:language>fa-IR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>مستندات مشارکت کننده Ùدورا</title>
<id>http://docs.fedoraproject.org/fa-IR/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2011-08-17T11:44:23</updated>
+ <updated>2011-08-22T23:04:46</updated>
<dc:language>fa-IR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/fa-IR/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2011-08-17T11:44:23</updated>
+ <updated>2011-08-22T23:04:46</updated>
<dc:language>fa-IR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/fa-IR/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2011-08-17T11:44:23</updated>
+ <updated>2011-08-22T23:04:46</updated>
<dc:language>fa-IR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/fa-IR/toc.html b/public_html/fa-IR/toc.html
index 02d8bcc..ab4357a 100644
--- a/public_html/fa-IR/toc.html
+++ b/public_html/fa-IR/toc.html
@@ -58,6 +58,7 @@
<option value="pl-PL">Polski</option>
<option value="pt-BR">Português Brasileiro</option>
<option value="pt-PT">Português</option>
+ <option value="ro">Romanian</option>
<option value="ru-RU">РуÑÑкий</option>
<option value="sk-SK">SlovenÅ¡Äina</option>
<option value="sr-Latn-RS">Srpski (latinica)</option>
@@ -300,7 +301,7 @@
<a class="type" href="../en-US/./Fedora/13/epub/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/13/html/Accessibility_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/13/html/Accessibility_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/13/html-single/Accessibility_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/13/html-single/Accessibility_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.13.Burning_ISO_images_to_disc' class="book collapsed" onclick="toggle(event, 'Fedora.13.Burning_ISO_images_to_disc.types');">
@@ -608,7 +609,7 @@
<a class="type" href="../en-US/./Fedora/11/epub/Security_Guide/Fedora-11-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/11/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/11/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.11.User_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.11.User_Guide.types');">
@@ -737,7 +738,7 @@
<a class="type" href="../en-US/./Fedora/8/epub/Installation_Guide/Fedora-8-Installation_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/8/html/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/8/html/Installation_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/8/html-single/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/8/html-single/Installation_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-9-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-9-Installation_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-8-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-8-Installation_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.8.Making_Fedora_Discs' class="book collapsed" onclick="toggle(event, 'Fedora.8.Making_Fedora_Discs.types');">
@@ -845,7 +846,7 @@
<div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Fedora_Elections_Guide.types');">
<a class="type" href="../en-US/Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html'"><span class="book">Fedora Elections Guide</span></a>
<div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide.types' class="types hidden" onclick="work=0;">
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
@@ -857,7 +858,7 @@
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/fi-FI/Site_Statistics.html b/public_html/fi-FI/Site_Statistics.html
index e17799c..5501668 100644
--- a/public_html/fi-FI/Site_Statistics.html
+++ b/public_html/fi-FI/Site_Statistics.html
@@ -392,6 +392,15 @@
</tr>
<tr>
+ <td>Romanian</td>
+ <td>ro</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ </tr>
+
+ <tr>
<td>Tamil</td>
<td>ta-IN</td>
<td>1</td>
@@ -402,8 +411,8 @@
</table>
<div class="totals">
- <b>Total Languages: </b>42<br />
- <b>Total Packages: </b>673
+ <b>Total Languages: </b>43<br />
+ <b>Total Packages: </b>674
</div>
</body>
</html>
diff --git a/public_html/fi-FI/opds-Fedora.xml b/public_html/fi-FI/opds-Fedora.xml
index 072ca49..d5cb67c 100644
--- a/public_html/fi-FI/opds-Fedora.xml
+++ b/public_html/fi-FI/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/fi-FI/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2011-08-17T11:44:23</updated>
+ <updated>2011-08-22T23:04:46</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fi-FI/opds-Fedora_Contributor_Documentation.xml b/public_html/fi-FI/opds-Fedora_Contributor_Documentation.xml
index c8dcee7..d26af63 100644
--- a/public_html/fi-FI/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/fi-FI/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/fi-FI/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2011-08-17T11:44:23</updated>
+ <updated>2011-08-22T23:04:46</updated>
<!--author>
<name></name>
<uri></uri>
@@ -14,7 +14,7 @@
<entry>
<title>Fedora Elections Guide</title>
- <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub</id>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub</id>
<!--author>
<name></name>
<uri></uri>
@@ -26,7 +26,7 @@
<summary>Fedora Elections Guide
</summary>
<content type="text">This book covers procedural information for the use the Fedora Elections software</content>
- <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub">
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub">
<dc:format>application/epub+zip</dc:format>
</link>
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
diff --git a/public_html/fi-FI/opds-Fedora_Core.xml b/public_html/fi-FI/opds-Fedora_Core.xml
index 61dae67..d552f30 100644
--- a/public_html/fi-FI/opds-Fedora_Core.xml
+++ b/public_html/fi-FI/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/fi-FI/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2011-08-17T11:44:23</updated>
+ <updated>2011-08-22T23:04:46</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fi-FI/opds-Fedora_Draft_Documentation.xml b/public_html/fi-FI/opds-Fedora_Draft_Documentation.xml
index c31a092..cf44a67 100644
--- a/public_html/fi-FI/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/fi-FI/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/fi-FI/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2011-08-17T11:44:23</updated>
+ <updated>2011-08-22T23:04:47</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fi-FI/opds.xml b/public_html/fi-FI/opds.xml
index 8e3fd45..fd2874f 100644
--- a/public_html/fi-FI/opds.xml
+++ b/public_html/fi-FI/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/fi-FI/opds.xml</id>
<title>Product List</title>
- <updated>2011-08-17T11:44:23</updated>
+ <updated>2011-08-22T23:04:47</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/fi-FI/Fedora/opds-Fedora.xml</id>
- <updated>2011-08-17T11:44:23</updated>
+ <updated>2011-08-22T23:04:46</updated>
<dc:language>fi-FI</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/fi-FI/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2011-08-17T11:44:23</updated>
+ <updated>2011-08-22T23:04:46</updated>
<dc:language>fi-FI</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/fi-FI/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2011-08-17T11:44:23</updated>
+ <updated>2011-08-22T23:04:47</updated>
<dc:language>fi-FI</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/fi-FI/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2011-08-17T11:44:23</updated>
+ <updated>2011-08-22T23:04:47</updated>
<dc:language>fi-FI</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/fi-FI/toc.html b/public_html/fi-FI/toc.html
index 3d15631..0f88eb2 100644
--- a/public_html/fi-FI/toc.html
+++ b/public_html/fi-FI/toc.html
@@ -58,6 +58,7 @@
<option value="pl-PL">Polski</option>
<option value="pt-BR">Português Brasileiro</option>
<option value="pt-PT">Português</option>
+ <option value="ro">Romanian</option>
<option value="ru-RU">РуÑÑкий</option>
<option value="sk-SK">SlovenÅ¡Äina</option>
<option value="sr-Latn-RS">Srpski (latinica)</option>
@@ -309,7 +310,7 @@
<a class="type" href="../en-US/./Fedora/13/epub/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/13/html/Accessibility_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/13/html/Accessibility_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/13/html-single/Accessibility_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/13/html-single/Accessibility_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.13.Installation_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.13.Installation_Guide.types');">
@@ -608,7 +609,7 @@
<a class="type" href="../en-US/./Fedora/11/epub/Security_Guide/Fedora-11-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/11/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/11/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.11.User_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.11.User_Guide.types');">
@@ -755,7 +756,7 @@
<a class="type" href="../en-US/./Fedora/8/epub/Installation_Guide/Fedora-8-Installation_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/8/html/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/8/html/Installation_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/8/html-single/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/8/html-single/Installation_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-9-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-9-Installation_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-8-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-8-Installation_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.8.SELinux_FAQ' class="book collapsed" onclick="toggle(event, 'Fedora.8.SELinux_FAQ.types');">
@@ -837,7 +838,7 @@
<div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Fedora_Elections_Guide.types');">
<a class="type" href="../en-US/Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html'"><span class="book">Fedora Elections Guide</span></a>
<div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide.types' class="types hidden" onclick="work=0;">
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
@@ -858,7 +859,7 @@
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/fr-FR/Site_Statistics.html b/public_html/fr-FR/Site_Statistics.html
index e17799c..5501668 100644
--- a/public_html/fr-FR/Site_Statistics.html
+++ b/public_html/fr-FR/Site_Statistics.html
@@ -392,6 +392,15 @@
</tr>
<tr>
+ <td>Romanian</td>
+ <td>ro</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ </tr>
+
+ <tr>
<td>Tamil</td>
<td>ta-IN</td>
<td>1</td>
@@ -402,8 +411,8 @@
</table>
<div class="totals">
- <b>Total Languages: </b>42<br />
- <b>Total Packages: </b>673
+ <b>Total Languages: </b>43<br />
+ <b>Total Packages: </b>674
</div>
</body>
</html>
diff --git a/public_html/fr-FR/opds-Fedora.xml b/public_html/fr-FR/opds-Fedora.xml
index 93b3d5a..4c3eb2d 100644
--- a/public_html/fr-FR/opds-Fedora.xml
+++ b/public_html/fr-FR/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/fr-FR/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2011-08-17T11:44:24</updated>
+ <updated>2011-08-22T23:04:47</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fr-FR/opds-Fedora_Contributor_Documentation.xml b/public_html/fr-FR/opds-Fedora_Contributor_Documentation.xml
index 0a6ffa6..2c172f7 100644
--- a/public_html/fr-FR/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/fr-FR/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/fr-FR/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2011-08-17T11:44:24</updated>
+ <updated>2011-08-22T23:04:47</updated>
<!--author>
<name></name>
<uri></uri>
@@ -14,7 +14,7 @@
<entry>
<title>Fedora Elections Guide</title>
- <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub</id>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub</id>
<!--author>
<name></name>
<uri></uri>
@@ -26,7 +26,7 @@
<summary>Fedora Elections Guide
</summary>
<content type="text">This book covers procedural information for the use the Fedora Elections software</content>
- <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub">
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub">
<dc:format>application/epub+zip</dc:format>
</link>
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
diff --git a/public_html/fr-FR/opds-Fedora_Core.xml b/public_html/fr-FR/opds-Fedora_Core.xml
index 01a0a95..0cf491b 100644
--- a/public_html/fr-FR/opds-Fedora_Core.xml
+++ b/public_html/fr-FR/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/fr-FR/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2011-08-17T11:44:24</updated>
+ <updated>2011-08-22T23:04:47</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fr-FR/opds-Fedora_Draft_Documentation.xml b/public_html/fr-FR/opds-Fedora_Draft_Documentation.xml
index 9e977e6..63c7bfa 100644
--- a/public_html/fr-FR/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/fr-FR/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/fr-FR/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2011-08-17T11:44:24</updated>
+ <updated>2011-08-22T23:04:47</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fr-FR/opds.xml b/public_html/fr-FR/opds.xml
index 19a892d..7c08431 100644
--- a/public_html/fr-FR/opds.xml
+++ b/public_html/fr-FR/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/fr-FR/opds.xml</id>
<title>Product List</title>
- <updated>2011-08-17T11:44:24</updated>
+ <updated>2011-08-22T23:04:47</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/fr-FR/Fedora/opds-Fedora.xml</id>
- <updated>2011-08-17T11:44:24</updated>
+ <updated>2011-08-22T23:04:47</updated>
<dc:language>fr-FR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/fr-FR/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2011-08-17T11:44:24</updated>
+ <updated>2011-08-22T23:04:47</updated>
<dc:language>fr-FR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/fr-FR/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2011-08-17T11:44:24</updated>
+ <updated>2011-08-22T23:04:47</updated>
<dc:language>fr-FR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/fr-FR/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2011-08-17T11:44:24</updated>
+ <updated>2011-08-22T23:04:47</updated>
<dc:language>fr-FR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/fr-FR/toc.html b/public_html/fr-FR/toc.html
index 53fec83..2b46e2d 100644
--- a/public_html/fr-FR/toc.html
+++ b/public_html/fr-FR/toc.html
@@ -58,6 +58,7 @@
<option value="pl-PL">Polski</option>
<option value="pt-BR">Português Brasileiro</option>
<option value="pt-PT">Português</option>
+ <option value="ro">Romanian</option>
<option value="ru-RU">РуÑÑкий</option>
<option value="sk-SK">SlovenÅ¡Äina</option>
<option value="sr-Latn-RS">Srpski (latinica)</option>
@@ -334,7 +335,7 @@
<a class="type" href="../en-US/./Fedora/13/epub/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/13/html/Accessibility_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/13/html/Accessibility_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/13/html-single/Accessibility_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/13/html-single/Accessibility_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.13.Installation_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.13.Installation_Guide.types');">
@@ -606,7 +607,7 @@
<a class="type" href="../en-US/./Fedora/11/epub/Security_Guide/Fedora-11-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/11/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/11/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.11.User_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.11.User_Guide.types');">
@@ -735,7 +736,7 @@
<a class="type" href="../en-US/./Fedora/8/epub/Installation_Guide/Fedora-8-Installation_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/8/html/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/8/html/Installation_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/8/html-single/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/8/html-single/Installation_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-9-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-9-Installation_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-8-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-8-Installation_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.8.Making_Fedora_Discs' class="book collapsed" onclick="toggle(event, 'Fedora.8.Making_Fedora_Discs.types');">
@@ -835,7 +836,7 @@
<div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Fedora_Elections_Guide.types');">
<a class="type" href="../en-US/Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html'"><span class="book">Fedora Elections Guide</span></a>
<div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide.types' class="types hidden" onclick="work=0;">
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
@@ -856,7 +857,7 @@
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/gu-IN/Site_Statistics.html b/public_html/gu-IN/Site_Statistics.html
index e17799c..5501668 100644
--- a/public_html/gu-IN/Site_Statistics.html
+++ b/public_html/gu-IN/Site_Statistics.html
@@ -392,6 +392,15 @@
</tr>
<tr>
+ <td>Romanian</td>
+ <td>ro</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ </tr>
+
+ <tr>
<td>Tamil</td>
<td>ta-IN</td>
<td>1</td>
@@ -402,8 +411,8 @@
</table>
<div class="totals">
- <b>Total Languages: </b>42<br />
- <b>Total Packages: </b>673
+ <b>Total Languages: </b>43<br />
+ <b>Total Packages: </b>674
</div>
</body>
</html>
diff --git a/public_html/gu-IN/opds-Fedora.xml b/public_html/gu-IN/opds-Fedora.xml
index 6e3c94b..c7ab4a2 100644
--- a/public_html/gu-IN/opds-Fedora.xml
+++ b/public_html/gu-IN/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/gu-IN/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2011-08-17T11:44:24</updated>
+ <updated>2011-08-22T23:04:47</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/gu-IN/opds-Fedora_Contributor_Documentation.xml b/public_html/gu-IN/opds-Fedora_Contributor_Documentation.xml
index d402734..aa634c9 100644
--- a/public_html/gu-IN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/gu-IN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/gu-IN/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2011-08-17T11:44:24</updated>
+ <updated>2011-08-22T23:04:47</updated>
<!--author>
<name></name>
<uri></uri>
@@ -14,7 +14,7 @@
<entry>
<title>Fedora Elections Guide</title>
- <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub</id>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub</id>
<!--author>
<name></name>
<uri></uri>
@@ -26,7 +26,7 @@
<summary>Fedora Elections Guide
</summary>
<content type="text">This book covers procedural information for the use the Fedora Elections software</content>
- <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub">
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub">
<dc:format>application/epub+zip</dc:format>
</link>
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
diff --git a/public_html/gu-IN/opds-Fedora_Core.xml b/public_html/gu-IN/opds-Fedora_Core.xml
index 3378714..addf07f 100644
--- a/public_html/gu-IN/opds-Fedora_Core.xml
+++ b/public_html/gu-IN/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/gu-IN/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2011-08-17T11:44:24</updated>
+ <updated>2011-08-22T23:04:47</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/gu-IN/opds-Fedora_Draft_Documentation.xml b/public_html/gu-IN/opds-Fedora_Draft_Documentation.xml
index 815efae..2fbe54f 100644
--- a/public_html/gu-IN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/gu-IN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/gu-IN/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2011-08-17T11:44:24</updated>
+ <updated>2011-08-22T23:04:47</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/gu-IN/opds.xml b/public_html/gu-IN/opds.xml
index 56b66dc..9f981cd 100644
--- a/public_html/gu-IN/opds.xml
+++ b/public_html/gu-IN/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/gu-IN/opds.xml</id>
<title>Product List</title>
- <updated>2011-08-17T11:44:24</updated>
+ <updated>2011-08-22T23:04:47</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/gu-IN/Fedora/opds-Fedora.xml</id>
- <updated>2011-08-17T11:44:24</updated>
+ <updated>2011-08-22T23:04:47</updated>
<dc:language>gu-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/gu-IN/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2011-08-17T11:44:24</updated>
+ <updated>2011-08-22T23:04:47</updated>
<dc:language>gu-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/gu-IN/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2011-08-17T11:44:24</updated>
+ <updated>2011-08-22T23:04:47</updated>
<dc:language>gu-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/gu-IN/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2011-08-17T11:44:24</updated>
+ <updated>2011-08-22T23:04:47</updated>
<dc:language>gu-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/gu-IN/toc.html b/public_html/gu-IN/toc.html
index 09f8f0a..2b3102a 100644
--- a/public_html/gu-IN/toc.html
+++ b/public_html/gu-IN/toc.html
@@ -58,6 +58,7 @@
<option value="pl-PL">Polski</option>
<option value="pt-BR">Português Brasileiro</option>
<option value="pt-PT">Português</option>
+ <option value="ro">Romanian</option>
<option value="ru-RU">РуÑÑкий</option>
<option value="sk-SK">SlovenÅ¡Äina</option>
<option value="sr-Latn-RS">Srpski (latinica)</option>
@@ -292,7 +293,7 @@
<a class="type" href="../en-US/./Fedora/13/epub/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/13/html/Accessibility_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/13/html/Accessibility_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/13/html-single/Accessibility_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/13/html-single/Accessibility_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.13.Burning_ISO_images_to_disc' class="book collapsed" onclick="toggle(event, 'Fedora.13.Burning_ISO_images_to_disc.types');">
@@ -609,7 +610,7 @@
<a class="type" href="../en-US/./Fedora/11/epub/Security_Guide/Fedora-11-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/11/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/11/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.11.User_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.11.User_Guide.types');">
@@ -738,7 +739,7 @@
<a class="type" href="../en-US/./Fedora/8/epub/Installation_Guide/Fedora-8-Installation_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/8/html/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/8/html/Installation_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/8/html-single/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/8/html-single/Installation_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-9-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-9-Installation_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-8-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-8-Installation_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.8.Making_Fedora_Discs' class="book collapsed" onclick="toggle(event, 'Fedora.8.Making_Fedora_Discs.types');">
@@ -838,7 +839,7 @@
<div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Fedora_Elections_Guide.types');">
<a class="type" href="../en-US/Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html'"><span class="book">Fedora Elections Guide</span></a>
<div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide.types' class="types hidden" onclick="work=0;">
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
@@ -859,7 +860,7 @@
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/he-IL/Site_Statistics.html b/public_html/he-IL/Site_Statistics.html
index e17799c..5501668 100644
--- a/public_html/he-IL/Site_Statistics.html
+++ b/public_html/he-IL/Site_Statistics.html
@@ -392,6 +392,15 @@
</tr>
<tr>
+ <td>Romanian</td>
+ <td>ro</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ </tr>
+
+ <tr>
<td>Tamil</td>
<td>ta-IN</td>
<td>1</td>
@@ -402,8 +411,8 @@
</table>
<div class="totals">
- <b>Total Languages: </b>42<br />
- <b>Total Packages: </b>673
+ <b>Total Languages: </b>43<br />
+ <b>Total Packages: </b>674
</div>
</body>
</html>
diff --git a/public_html/he-IL/opds-Fedora.xml b/public_html/he-IL/opds-Fedora.xml
index e03594e..aff1ed2 100644
--- a/public_html/he-IL/opds-Fedora.xml
+++ b/public_html/he-IL/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/he-IL/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2011-08-17T11:44:24</updated>
+ <updated>2011-08-22T23:04:47</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/he-IL/opds-Fedora_Contributor_Documentation.xml b/public_html/he-IL/opds-Fedora_Contributor_Documentation.xml
index 87517ff..8995fda 100644
--- a/public_html/he-IL/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/he-IL/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/he-IL/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2011-08-17T11:44:24</updated>
+ <updated>2011-08-22T23:04:47</updated>
<!--author>
<name></name>
<uri></uri>
@@ -14,7 +14,7 @@
<entry>
<title>Fedora Elections Guide</title>
- <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub</id>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub</id>
<!--author>
<name></name>
<uri></uri>
@@ -26,7 +26,7 @@
<summary>Fedora Elections Guide
</summary>
<content type="text">This book covers procedural information for the use the Fedora Elections software</content>
- <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub">
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub">
<dc:format>application/epub+zip</dc:format>
</link>
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
diff --git a/public_html/he-IL/opds-Fedora_Core.xml b/public_html/he-IL/opds-Fedora_Core.xml
index 9aadf84..b5f09d7 100644
--- a/public_html/he-IL/opds-Fedora_Core.xml
+++ b/public_html/he-IL/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/he-IL/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2011-08-17T11:44:24</updated>
+ <updated>2011-08-22T23:04:47</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/he-IL/opds-Fedora_Draft_Documentation.xml b/public_html/he-IL/opds-Fedora_Draft_Documentation.xml
index 62e2729..2fa4784 100644
--- a/public_html/he-IL/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/he-IL/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/he-IL/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2011-08-17T11:44:24</updated>
+ <updated>2011-08-22T23:04:47</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/he-IL/opds.xml b/public_html/he-IL/opds.xml
index 94f6ac4..995699d 100644
--- a/public_html/he-IL/opds.xml
+++ b/public_html/he-IL/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/he-IL/opds.xml</id>
<title>Product List</title>
- <updated>2011-08-17T11:44:24</updated>
+ <updated>2011-08-22T23:04:47</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/he-IL/Fedora/opds-Fedora.xml</id>
- <updated>2011-08-17T11:44:24</updated>
+ <updated>2011-08-22T23:04:47</updated>
<dc:language>he-IL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/he-IL/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2011-08-17T11:44:24</updated>
+ <updated>2011-08-22T23:04:47</updated>
<dc:language>he-IL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/he-IL/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2011-08-17T11:44:24</updated>
+ <updated>2011-08-22T23:04:47</updated>
<dc:language>he-IL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/he-IL/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2011-08-17T11:44:24</updated>
+ <updated>2011-08-22T23:04:47</updated>
<dc:language>he-IL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/he-IL/toc.html b/public_html/he-IL/toc.html
index 8552eec..3ec7fe6 100644
--- a/public_html/he-IL/toc.html
+++ b/public_html/he-IL/toc.html
@@ -58,6 +58,7 @@
<option value="pl-PL">Polski</option>
<option value="pt-BR">Português Brasileiro</option>
<option value="pt-PT">Português</option>
+ <option value="ro">Romanian</option>
<option value="ru-RU">РуÑÑкий</option>
<option value="sk-SK">SlovenÅ¡Äina</option>
<option value="sr-Latn-RS">Srpski (latinica)</option>
@@ -301,7 +302,7 @@
<a class="type" href="../en-US/./Fedora/13/epub/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/13/html/Accessibility_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/13/html/Accessibility_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/13/html-single/Accessibility_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/13/html-single/Accessibility_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.13.Burning_ISO_images_to_disc' class="book collapsed" onclick="toggle(event, 'Fedora.13.Burning_ISO_images_to_disc.types');">
@@ -609,7 +610,7 @@
<a class="type" href="../en-US/./Fedora/11/epub/Security_Guide/Fedora-11-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/11/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/11/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.11.User_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.11.User_Guide.types');">
@@ -738,7 +739,7 @@
<a class="type" href="../en-US/./Fedora/8/epub/Installation_Guide/Fedora-8-Installation_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/8/html/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/8/html/Installation_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/8/html-single/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/8/html-single/Installation_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-9-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-9-Installation_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-8-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-8-Installation_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.8.Making_Fedora_Discs' class="book collapsed" onclick="toggle(event, 'Fedora.8.Making_Fedora_Discs.types');">
@@ -838,7 +839,7 @@
<div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Fedora_Elections_Guide.types');">
<a class="type" href="../en-US/Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html'"><span class="book">Fedora Elections Guide</span></a>
<div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide.types' class="types hidden" onclick="work=0;">
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
@@ -859,7 +860,7 @@
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/hi-IN/Site_Statistics.html b/public_html/hi-IN/Site_Statistics.html
index e17799c..5501668 100644
--- a/public_html/hi-IN/Site_Statistics.html
+++ b/public_html/hi-IN/Site_Statistics.html
@@ -392,6 +392,15 @@
</tr>
<tr>
+ <td>Romanian</td>
+ <td>ro</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ </tr>
+
+ <tr>
<td>Tamil</td>
<td>ta-IN</td>
<td>1</td>
@@ -402,8 +411,8 @@
</table>
<div class="totals">
- <b>Total Languages: </b>42<br />
- <b>Total Packages: </b>673
+ <b>Total Languages: </b>43<br />
+ <b>Total Packages: </b>674
</div>
</body>
</html>
diff --git a/public_html/hi-IN/opds-Fedora.xml b/public_html/hi-IN/opds-Fedora.xml
index 666dd2d..5f714a8 100644
--- a/public_html/hi-IN/opds-Fedora.xml
+++ b/public_html/hi-IN/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/hi-IN/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2011-08-17T11:44:24</updated>
+ <updated>2011-08-22T23:04:47</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/hi-IN/opds-Fedora_Contributor_Documentation.xml b/public_html/hi-IN/opds-Fedora_Contributor_Documentation.xml
index 738e455..7d6a1a9 100644
--- a/public_html/hi-IN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/hi-IN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/hi-IN/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2011-08-17T11:44:24</updated>
+ <updated>2011-08-22T23:04:47</updated>
<!--author>
<name></name>
<uri></uri>
@@ -14,7 +14,7 @@
<entry>
<title>Fedora Elections Guide</title>
- <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub</id>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub</id>
<!--author>
<name></name>
<uri></uri>
@@ -26,7 +26,7 @@
<summary>Fedora Elections Guide
</summary>
<content type="text">This book covers procedural information for the use the Fedora Elections software</content>
- <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub">
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub">
<dc:format>application/epub+zip</dc:format>
</link>
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
diff --git a/public_html/hi-IN/opds-Fedora_Core.xml b/public_html/hi-IN/opds-Fedora_Core.xml
index e85d697..6ed0ae5 100644
--- a/public_html/hi-IN/opds-Fedora_Core.xml
+++ b/public_html/hi-IN/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/hi-IN/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2011-08-17T11:44:24</updated>
+ <updated>2011-08-22T23:04:47</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/hi-IN/opds-Fedora_Draft_Documentation.xml b/public_html/hi-IN/opds-Fedora_Draft_Documentation.xml
index 93919f1..bec2ccf 100644
--- a/public_html/hi-IN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/hi-IN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/hi-IN/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2011-08-17T11:44:24</updated>
+ <updated>2011-08-22T23:04:47</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/hi-IN/opds.xml b/public_html/hi-IN/opds.xml
index 492f3b9..b486c41 100644
--- a/public_html/hi-IN/opds.xml
+++ b/public_html/hi-IN/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/hi-IN/opds.xml</id>
<title>Product List</title>
- <updated>2011-08-17T11:44:24</updated>
+ <updated>2011-08-22T23:04:47</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/hi-IN/Fedora/opds-Fedora.xml</id>
- <updated>2011-08-17T11:44:24</updated>
+ <updated>2011-08-22T23:04:47</updated>
<dc:language>hi-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/hi-IN/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2011-08-17T11:44:24</updated>
+ <updated>2011-08-22T23:04:47</updated>
<dc:language>hi-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/hi-IN/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2011-08-17T11:44:24</updated>
+ <updated>2011-08-22T23:04:47</updated>
<dc:language>hi-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/hi-IN/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2011-08-17T11:44:24</updated>
+ <updated>2011-08-22T23:04:47</updated>
<dc:language>hi-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/hi-IN/toc.html b/public_html/hi-IN/toc.html
index 0e03bb5..13c3900 100644
--- a/public_html/hi-IN/toc.html
+++ b/public_html/hi-IN/toc.html
@@ -58,6 +58,7 @@
<option value="pl-PL">Polski</option>
<option value="pt-BR">Português Brasileiro</option>
<option value="pt-PT">Português</option>
+ <option value="ro">Romanian</option>
<option value="ru-RU">РуÑÑкий</option>
<option value="sk-SK">SlovenÅ¡Äina</option>
<option value="sr-Latn-RS">Srpski (latinica)</option>
@@ -292,7 +293,7 @@
<a class="type" href="../en-US/./Fedora/13/epub/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/13/html/Accessibility_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/13/html/Accessibility_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/13/html-single/Accessibility_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/13/html-single/Accessibility_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.13.Burning_ISO_images_to_disc' class="book collapsed" onclick="toggle(event, 'Fedora.13.Burning_ISO_images_to_disc.types');">
@@ -609,7 +610,7 @@
<a class="type" href="../en-US/./Fedora/11/epub/Security_Guide/Fedora-11-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/11/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/11/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.11.User_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.11.User_Guide.types');">
@@ -738,7 +739,7 @@
<a class="type" href="../en-US/./Fedora/8/epub/Installation_Guide/Fedora-8-Installation_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/8/html/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/8/html/Installation_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/8/html-single/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/8/html-single/Installation_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-9-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-9-Installation_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-8-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-8-Installation_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.8.Making_Fedora_Discs' class="book collapsed" onclick="toggle(event, 'Fedora.8.Making_Fedora_Discs.types');">
@@ -838,7 +839,7 @@
<div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Fedora_Elections_Guide.types');">
<a class="type" href="../en-US/Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html'"><span class="book">Fedora Elections Guide</span></a>
<div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide.types' class="types hidden" onclick="work=0;">
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
@@ -859,7 +860,7 @@
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/hu-HU/Site_Statistics.html b/public_html/hu-HU/Site_Statistics.html
index e17799c..5501668 100644
--- a/public_html/hu-HU/Site_Statistics.html
+++ b/public_html/hu-HU/Site_Statistics.html
@@ -392,6 +392,15 @@
</tr>
<tr>
+ <td>Romanian</td>
+ <td>ro</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ </tr>
+
+ <tr>
<td>Tamil</td>
<td>ta-IN</td>
<td>1</td>
@@ -402,8 +411,8 @@
</table>
<div class="totals">
- <b>Total Languages: </b>42<br />
- <b>Total Packages: </b>673
+ <b>Total Languages: </b>43<br />
+ <b>Total Packages: </b>674
</div>
</body>
</html>
diff --git a/public_html/hu-HU/opds-Fedora.xml b/public_html/hu-HU/opds-Fedora.xml
index 3008d2b..bcbc400 100644
--- a/public_html/hu-HU/opds-Fedora.xml
+++ b/public_html/hu-HU/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/hu-HU/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2011-08-17T11:44:24</updated>
+ <updated>2011-08-22T23:04:48</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/hu-HU/opds-Fedora_Contributor_Documentation.xml b/public_html/hu-HU/opds-Fedora_Contributor_Documentation.xml
index fb12ccf..2d3cf23 100644
--- a/public_html/hu-HU/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/hu-HU/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/hu-HU/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2011-08-17T11:44:25</updated>
+ <updated>2011-08-22T23:04:48</updated>
<!--author>
<name></name>
<uri></uri>
@@ -14,7 +14,7 @@
<entry>
<title>Fedora Elections Guide</title>
- <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub</id>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub</id>
<!--author>
<name></name>
<uri></uri>
@@ -26,7 +26,7 @@
<summary>Fedora Elections Guide
</summary>
<content type="text">This book covers procedural information for the use the Fedora Elections software</content>
- <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub">
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub">
<dc:format>application/epub+zip</dc:format>
</link>
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
diff --git a/public_html/hu-HU/opds-Fedora_Core.xml b/public_html/hu-HU/opds-Fedora_Core.xml
index 196d22a..10c0b74 100644
--- a/public_html/hu-HU/opds-Fedora_Core.xml
+++ b/public_html/hu-HU/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/hu-HU/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2011-08-17T11:44:25</updated>
+ <updated>2011-08-22T23:04:48</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/hu-HU/opds-Fedora_Draft_Documentation.xml b/public_html/hu-HU/opds-Fedora_Draft_Documentation.xml
index 3f2b887..9ff5d23 100644
--- a/public_html/hu-HU/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/hu-HU/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/hu-HU/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2011-08-17T11:44:25</updated>
+ <updated>2011-08-22T23:04:48</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/hu-HU/opds.xml b/public_html/hu-HU/opds.xml
index 2d25394..63a3a79 100644
--- a/public_html/hu-HU/opds.xml
+++ b/public_html/hu-HU/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/hu-HU/opds.xml</id>
<title>Product List</title>
- <updated>2011-08-17T11:44:25</updated>
+ <updated>2011-08-22T23:04:48</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/hu-HU/Fedora/opds-Fedora.xml</id>
- <updated>2011-08-17T11:44:25</updated>
+ <updated>2011-08-22T23:04:48</updated>
<dc:language>hu-HU</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/hu-HU/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2011-08-17T11:44:25</updated>
+ <updated>2011-08-22T23:04:48</updated>
<dc:language>hu-HU</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/hu-HU/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2011-08-17T11:44:25</updated>
+ <updated>2011-08-22T23:04:48</updated>
<dc:language>hu-HU</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/hu-HU/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2011-08-17T11:44:25</updated>
+ <updated>2011-08-22T23:04:48</updated>
<dc:language>hu-HU</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/hu-HU/toc.html b/public_html/hu-HU/toc.html
index df65b25..71fec1f 100644
--- a/public_html/hu-HU/toc.html
+++ b/public_html/hu-HU/toc.html
@@ -58,6 +58,7 @@
<option value="pl-PL">Polski</option>
<option value="pt-BR">Português Brasileiro</option>
<option value="pt-PT">Português</option>
+ <option value="ro">Romanian</option>
<option value="ru-RU">РуÑÑкий</option>
<option value="sk-SK">SlovenÅ¡Äina</option>
<option value="sr-Latn-RS">Srpski (latinica)</option>
@@ -292,7 +293,7 @@
<a class="type" href="../en-US/./Fedora/13/epub/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/13/html/Accessibility_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/13/html/Accessibility_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/13/html-single/Accessibility_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/13/html-single/Accessibility_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.13.Burning_ISO_images_to_disc' class="book collapsed" onclick="toggle(event, 'Fedora.13.Burning_ISO_images_to_disc.types');">
@@ -609,7 +610,7 @@
<a class="type" href="../en-US/./Fedora/11/epub/Security_Guide/Fedora-11-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/11/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/11/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.11.User_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.11.User_Guide.types');">
@@ -738,7 +739,7 @@
<a class="type" href="../en-US/./Fedora/8/epub/Installation_Guide/Fedora-8-Installation_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/8/html/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/8/html/Installation_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/8/html-single/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/8/html-single/Installation_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-9-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-9-Installation_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-8-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-8-Installation_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.8.Making_Fedora_Discs' class="book collapsed" onclick="toggle(event, 'Fedora.8.Making_Fedora_Discs.types');">
@@ -838,7 +839,7 @@
<div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Fedora_Elections_Guide.types');">
<a class="type" href="../en-US/Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html'"><span class="book">Fedora Elections Guide</span></a>
<div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide.types' class="types hidden" onclick="work=0;">
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
@@ -859,7 +860,7 @@
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/id-ID/Site_Statistics.html b/public_html/id-ID/Site_Statistics.html
index e17799c..5501668 100644
--- a/public_html/id-ID/Site_Statistics.html
+++ b/public_html/id-ID/Site_Statistics.html
@@ -392,6 +392,15 @@
</tr>
<tr>
+ <td>Romanian</td>
+ <td>ro</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ </tr>
+
+ <tr>
<td>Tamil</td>
<td>ta-IN</td>
<td>1</td>
@@ -402,8 +411,8 @@
</table>
<div class="totals">
- <b>Total Languages: </b>42<br />
- <b>Total Packages: </b>673
+ <b>Total Languages: </b>43<br />
+ <b>Total Packages: </b>674
</div>
</body>
</html>
diff --git a/public_html/id-ID/opds-Fedora.xml b/public_html/id-ID/opds-Fedora.xml
index f91677d..9c806cd 100644
--- a/public_html/id-ID/opds-Fedora.xml
+++ b/public_html/id-ID/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/id-ID/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2011-08-17T11:44:25</updated>
+ <updated>2011-08-22T23:04:48</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/id-ID/opds-Fedora_Contributor_Documentation.xml b/public_html/id-ID/opds-Fedora_Contributor_Documentation.xml
index c289a43..1f6cd5c 100644
--- a/public_html/id-ID/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/id-ID/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/id-ID/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2011-08-17T11:44:25</updated>
+ <updated>2011-08-22T23:04:48</updated>
<!--author>
<name></name>
<uri></uri>
@@ -14,7 +14,7 @@
<entry>
<title>Fedora Elections Guide</title>
- <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub</id>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub</id>
<!--author>
<name></name>
<uri></uri>
@@ -26,7 +26,7 @@
<summary>Fedora Elections Guide
</summary>
<content type="text">This book covers procedural information for the use the Fedora Elections software</content>
- <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub">
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub">
<dc:format>application/epub+zip</dc:format>
</link>
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
diff --git a/public_html/id-ID/opds-Fedora_Core.xml b/public_html/id-ID/opds-Fedora_Core.xml
index ff04806..c56feab 100644
--- a/public_html/id-ID/opds-Fedora_Core.xml
+++ b/public_html/id-ID/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/id-ID/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2011-08-17T11:44:25</updated>
+ <updated>2011-08-22T23:04:48</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/id-ID/opds-Fedora_Draft_Documentation.xml b/public_html/id-ID/opds-Fedora_Draft_Documentation.xml
index 95fb1ce..5b36bdb 100644
--- a/public_html/id-ID/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/id-ID/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/id-ID/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2011-08-17T11:44:25</updated>
+ <updated>2011-08-22T23:04:48</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/id-ID/opds.xml b/public_html/id-ID/opds.xml
index 4f2ed32..798024a 100644
--- a/public_html/id-ID/opds.xml
+++ b/public_html/id-ID/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/id-ID/opds.xml</id>
<title>Product List</title>
- <updated>2011-08-17T11:44:25</updated>
+ <updated>2011-08-22T23:04:48</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/id-ID/Fedora/opds-Fedora.xml</id>
- <updated>2011-08-17T11:44:25</updated>
+ <updated>2011-08-22T23:04:48</updated>
<dc:language>id-ID</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/id-ID/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2011-08-17T11:44:25</updated>
+ <updated>2011-08-22T23:04:48</updated>
<dc:language>id-ID</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/id-ID/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2011-08-17T11:44:25</updated>
+ <updated>2011-08-22T23:04:48</updated>
<dc:language>id-ID</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/id-ID/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2011-08-17T11:44:25</updated>
+ <updated>2011-08-22T23:04:48</updated>
<dc:language>id-ID</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/id-ID/toc.html b/public_html/id-ID/toc.html
index c72e16e..2ad768a 100644
--- a/public_html/id-ID/toc.html
+++ b/public_html/id-ID/toc.html
@@ -58,6 +58,7 @@
<option value="pl-PL">Polski</option>
<option value="pt-BR">Português Brasileiro</option>
<option value="pt-PT">Português</option>
+ <option value="ro">Romanian</option>
<option value="ru-RU">РуÑÑкий</option>
<option value="sk-SK">SlovenÅ¡Äina</option>
<option value="sr-Latn-RS">Srpski (latinica)</option>
@@ -301,7 +302,7 @@
<a class="type" href="../en-US/./Fedora/13/epub/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/13/html/Accessibility_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/13/html/Accessibility_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/13/html-single/Accessibility_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/13/html-single/Accessibility_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.13.Fedora_Live_Images' class="book collapsed" onclick="toggle(event, 'Fedora.13.Fedora_Live_Images.types');">
@@ -609,7 +610,7 @@
<a class="type" href="../en-US/./Fedora/11/epub/Security_Guide/Fedora-11-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/11/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/11/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.11.User_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.11.User_Guide.types');">
@@ -738,7 +739,7 @@
<a class="type" href="../en-US/./Fedora/8/epub/Installation_Guide/Fedora-8-Installation_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/8/html/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/8/html/Installation_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/8/html-single/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/8/html-single/Installation_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-9-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-9-Installation_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-8-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-8-Installation_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.8.Making_Fedora_Discs' class="book collapsed" onclick="toggle(event, 'Fedora.8.Making_Fedora_Discs.types');">
@@ -838,7 +839,7 @@
<div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Fedora_Elections_Guide.types');">
<a class="type" href="../en-US/Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html'"><span class="book">Fedora Elections Guide</span></a>
<div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide.types' class="types hidden" onclick="work=0;">
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
@@ -859,7 +860,7 @@
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/index.html b/public_html/index.html
index 4020ec2..ab4c0cd 100644
--- a/public_html/index.html
+++ b/public_html/index.html
@@ -16,7 +16,7 @@
lang = window.navigator.language;
var match = 0;
- var locales = ["as-IN","bg-BG","bn-IN","bs-BA","ca-ES","cs-CZ","da-DK","de-DE","el-GR","en-US","es-ES","fa-IR","fi-FI","fr-FR","gu-IN","he-IL","hi-IN","hu-HU","id-ID","it-IT","ja-JP","kn-IN","ko-KR","ml-IN","mr-IN","nb-NO","nl-NL","or-IN","pa-IN","pl-PL","pt-BR","pt-PT","ru-RU","sk-SK","sr-Latn-RS","sr-RS","sv-SE","ta-IN","te-IN","uk-UA","zh-CN","zh-TW"];
+ var locales = ["as-IN","bg-BG","bn-IN","bs-BA","ca-ES","cs-CZ","da-DK","de-DE","el-GR","en-US","es-ES","fa-IR","fi-FI","fr-FR","gu-IN","he-IL","hi-IN","hu-HU","id-ID","it-IT","ja-JP","kn-IN","ko-KR","ml-IN","mr-IN","nb-NO","nl-NL","or-IN","pa-IN","pl-PL","pt-BR","pt-PT","ro","ru-RU","sk-SK","sr-Latn-RS","sr-RS","sv-SE","ta-IN","te-IN","uk-UA","zh-CN","zh-TW"];
if(lang) {
// Try for full match of lang_LOC
diff --git a/public_html/it-IT/Site_Statistics.html b/public_html/it-IT/Site_Statistics.html
index e17799c..5501668 100644
--- a/public_html/it-IT/Site_Statistics.html
+++ b/public_html/it-IT/Site_Statistics.html
@@ -392,6 +392,15 @@
</tr>
<tr>
+ <td>Romanian</td>
+ <td>ro</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ </tr>
+
+ <tr>
<td>Tamil</td>
<td>ta-IN</td>
<td>1</td>
@@ -402,8 +411,8 @@
</table>
<div class="totals">
- <b>Total Languages: </b>42<br />
- <b>Total Packages: </b>673
+ <b>Total Languages: </b>43<br />
+ <b>Total Packages: </b>674
</div>
</body>
</html>
diff --git a/public_html/it-IT/opds-Fedora.xml b/public_html/it-IT/opds-Fedora.xml
index 2da972b..e7fdbcb 100644
--- a/public_html/it-IT/opds-Fedora.xml
+++ b/public_html/it-IT/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/it-IT/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2011-08-17T11:44:25</updated>
+ <updated>2011-08-22T23:04:48</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/it-IT/opds-Fedora_Contributor_Documentation.xml b/public_html/it-IT/opds-Fedora_Contributor_Documentation.xml
index 028c11a..831faf6 100644
--- a/public_html/it-IT/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/it-IT/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/it-IT/opds-Fedora_Contributor_Documentation.xml</id>
<title>Documentazione Collaboratori Fedora</title>
<subtitle>Documentazione Collaboratori Fedora</subtitle>
- <updated>2011-08-17T11:44:25</updated>
+ <updated>2011-08-22T23:04:48</updated>
<!--author>
<name></name>
<uri></uri>
@@ -14,7 +14,7 @@
<entry>
<title>Fedora Elections Guide</title>
- <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub</id>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub</id>
<!--author>
<name></name>
<uri></uri>
@@ -26,7 +26,7 @@
<summary>Fedora Elections Guide
</summary>
<content type="text">This book covers procedural information for the use the Fedora Elections software</content>
- <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub">
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub">
<dc:format>application/epub+zip</dc:format>
</link>
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
diff --git a/public_html/it-IT/opds-Fedora_Core.xml b/public_html/it-IT/opds-Fedora_Core.xml
index 4df8747..3711248 100644
--- a/public_html/it-IT/opds-Fedora_Core.xml
+++ b/public_html/it-IT/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/it-IT/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2011-08-17T11:44:25</updated>
+ <updated>2011-08-22T23:04:48</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/it-IT/opds-Fedora_Draft_Documentation.xml b/public_html/it-IT/opds-Fedora_Draft_Documentation.xml
index e7cab7a..18099c7 100644
--- a/public_html/it-IT/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/it-IT/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/it-IT/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2011-08-17T11:44:25</updated>
+ <updated>2011-08-22T23:04:48</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/it-IT/opds.xml b/public_html/it-IT/opds.xml
index d7bb689..a32845c 100644
--- a/public_html/it-IT/opds.xml
+++ b/public_html/it-IT/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/it-IT/opds.xml</id>
<title>Product List</title>
- <updated>2011-08-17T11:44:25</updated>
+ <updated>2011-08-22T23:04:48</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/it-IT/Fedora/opds-Fedora.xml</id>
- <updated>2011-08-17T11:44:25</updated>
+ <updated>2011-08-22T23:04:48</updated>
<dc:language>it-IT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Documentazione Collaboratori Fedora</title>
<id>http://docs.fedoraproject.org/it-IT/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2011-08-17T11:44:25</updated>
+ <updated>2011-08-22T23:04:48</updated>
<dc:language>it-IT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/it-IT/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2011-08-17T11:44:25</updated>
+ <updated>2011-08-22T23:04:48</updated>
<dc:language>it-IT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/it-IT/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2011-08-17T11:44:25</updated>
+ <updated>2011-08-22T23:04:48</updated>
<dc:language>it-IT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/it-IT/toc.html b/public_html/it-IT/toc.html
index ce1a4e6..2f72fda 100644
--- a/public_html/it-IT/toc.html
+++ b/public_html/it-IT/toc.html
@@ -58,6 +58,7 @@
<option value="pl-PL">Polski</option>
<option value="pt-BR">Português Brasileiro</option>
<option value="pt-PT">Português</option>
+ <option value="ro">Romanian</option>
<option value="ru-RU">РуÑÑкий</option>
<option value="sk-SK">SlovenÅ¡Äina</option>
<option value="sr-Latn-RS">Srpski (latinica)</option>
@@ -606,7 +607,7 @@
<a class="type" href="../en-US/./Fedora/11/epub/Security_Guide/Fedora-11-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/11/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/11/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.11.User_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.11.User_Guide.types');">
@@ -706,7 +707,7 @@
<a class="type" href="../en-US/./Fedora/10/epub/Security_Guide/Fedora-11-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/10/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/10/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/10/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/10/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/10/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/10/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/10/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/10/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.10.User_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.10.User_Guide.types');">
@@ -806,7 +807,7 @@
<a class="type" href="../en-US/./Fedora/9/epub/Security_Guide/Fedora-11-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/9/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/9/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/9/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/9/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/9/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/9/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/9/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/9/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.9.User_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.9.User_Guide.types');">
@@ -915,7 +916,7 @@
<a class="type" href="../en-US/./Fedora/8/epub/Security_Guide/Fedora-11-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/8/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/8/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/8/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/8/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/8/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/8/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/8/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/8/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.8.User_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.8.User_Guide.types');">
@@ -1006,7 +1007,7 @@
<div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Fedora_Elections_Guide.types');">
<a class="type" href="../en-US/Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html'"><span class="book">Fedora Elections Guide</span></a>
<div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide.types' class="types hidden" onclick="work=0;">
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
@@ -1018,7 +1019,7 @@
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/ja-JP/Site_Statistics.html b/public_html/ja-JP/Site_Statistics.html
index 2857d93..16bd081 100644
--- a/public_html/ja-JP/Site_Statistics.html
+++ b/public_html/ja-JP/Site_Statistics.html
@@ -392,6 +392,15 @@
</tr>
<tr>
+ <td>Romanian</td>
+ <td>ro</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ </tr>
+
+ <tr>
<td>Tamil</td>
<td>ta-IN</td>
<td>1</td>
@@ -402,8 +411,8 @@
</table>
<div class="totals">
- <b>言語数ã®åˆè¨ˆ: </b>42<br />
- <b>パッケージ数ã®åˆè¨ˆ: </b>673
+ <b>言語数ã®åˆè¨ˆ: </b>43<br />
+ <b>パッケージ数ã®åˆè¨ˆ: </b>674
</div>
</body>
</html>
diff --git a/public_html/ja-JP/opds-Fedora.xml b/public_html/ja-JP/opds-Fedora.xml
index a45ba10..700bdb5 100644
--- a/public_html/ja-JP/opds-Fedora.xml
+++ b/public_html/ja-JP/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ja-JP/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2011-08-17T11:44:25</updated>
+ <updated>2011-08-22T23:04:48</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ja-JP/opds-Fedora_Contributor_Documentation.xml b/public_html/ja-JP/opds-Fedora_Contributor_Documentation.xml
index 59991ff..015973f 100644
--- a/public_html/ja-JP/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/ja-JP/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ja-JP/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora コントリビュータ用ドã‚ュメント</title>
<subtitle>Fedora コントリビュータ用ドã‚ュメント</subtitle>
- <updated>2011-08-17T11:44:25</updated>
+ <updated>2011-08-22T23:04:49</updated>
<!--author>
<name></name>
<uri></uri>
@@ -14,7 +14,7 @@
<entry>
<title>Fedora Elections Guide</title>
- <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub</id>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub</id>
<!--author>
<name></name>
<uri></uri>
@@ -26,7 +26,7 @@
<summary>Fedora Elections Guide
</summary>
<content type="text">This book covers procedural information for the use the Fedora Elections software</content>
- <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub">
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub">
<dc:format>application/epub+zip</dc:format>
</link>
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
diff --git a/public_html/ja-JP/opds-Fedora_Core.xml b/public_html/ja-JP/opds-Fedora_Core.xml
index b1295e6..ed3c5f5 100644
--- a/public_html/ja-JP/opds-Fedora_Core.xml
+++ b/public_html/ja-JP/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ja-JP/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2011-08-17T11:44:25</updated>
+ <updated>2011-08-22T23:04:49</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ja-JP/opds-Fedora_Draft_Documentation.xml b/public_html/ja-JP/opds-Fedora_Draft_Documentation.xml
index a07beac..1c2f656 100644
--- a/public_html/ja-JP/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/ja-JP/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ja-JP/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora ドラフト文書</title>
<subtitle>Fedora ドラフト文書</subtitle>
- <updated>2011-08-17T11:44:25</updated>
+ <updated>2011-08-22T23:04:49</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ja-JP/opds.xml b/public_html/ja-JP/opds.xml
index 6f07891..4b7383b 100644
--- a/public_html/ja-JP/opds.xml
+++ b/public_html/ja-JP/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/ja-JP/opds.xml</id>
<title>Product List</title>
- <updated>2011-08-17T11:44:25</updated>
+ <updated>2011-08-22T23:04:49</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/ja-JP/Fedora/opds-Fedora.xml</id>
- <updated>2011-08-17T11:44:25</updated>
+ <updated>2011-08-22T23:04:48</updated>
<dc:language>ja-JP</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora コントリビュータ用ドã‚ュメント</title>
<id>http://docs.fedoraproject.org/ja-JP/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2011-08-17T11:44:25</updated>
+ <updated>2011-08-22T23:04:49</updated>
<dc:language>ja-JP</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/ja-JP/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2011-08-17T11:44:25</updated>
+ <updated>2011-08-22T23:04:49</updated>
<dc:language>ja-JP</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora ドラフト文書</title>
<id>http://docs.fedoraproject.org/ja-JP/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2011-08-17T11:44:25</updated>
+ <updated>2011-08-22T23:04:49</updated>
<dc:language>ja-JP</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/ja-JP/toc.html b/public_html/ja-JP/toc.html
index f8f0257..e5694dd 100644
--- a/public_html/ja-JP/toc.html
+++ b/public_html/ja-JP/toc.html
@@ -58,6 +58,7 @@
<option value="pl-PL">Polski</option>
<option value="pt-BR">Português Brasileiro</option>
<option value="pt-PT">Português</option>
+ <option value="ro">Romanian</option>
<option value="ru-RU">РуÑÑкий</option>
<option value="sk-SK">SlovenÅ¡Äina</option>
<option value="sr-Latn-RS">Srpski (latinica)</option>
@@ -301,7 +302,7 @@
<a class="type" href="../en-US/./Fedora/13/epub/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/13/html/Accessibility_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/13/html/Accessibility_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/13/html-single/Accessibility_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/13/html-single/Accessibility_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.13.Burning_ISO_images_to_disc' class="book collapsed" onclick="toggle(event, 'Fedora.13.Burning_ISO_images_to_disc.types');">
@@ -609,7 +610,7 @@
<a class="type" href="../en-US/./Fedora/11/epub/Security_Guide/Fedora-11-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/11/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/11/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.11.User_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.11.User_Guide.types');">
@@ -756,7 +757,7 @@
<a class="type" href="../en-US/./Fedora/8/epub/Installation_Guide/Fedora-8-Installation_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/8/html/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/8/html/Installation_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/8/html-single/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/8/html-single/Installation_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-9-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-9-Installation_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-8-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-8-Installation_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.8.SELinux_FAQ' class="book collapsed" onclick="toggle(event, 'Fedora.8.SELinux_FAQ.types');">
@@ -847,7 +848,7 @@
<div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Fedora_Elections_Guide.types');">
<a class="type" href="../en-US/Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html'"><span class="book">Fedora Elections Guide</span></a>
<div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide.types' class="types hidden" onclick="work=0;">
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
@@ -859,7 +860,7 @@
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/kn-IN/Site_Statistics.html b/public_html/kn-IN/Site_Statistics.html
index e17799c..5501668 100644
--- a/public_html/kn-IN/Site_Statistics.html
+++ b/public_html/kn-IN/Site_Statistics.html
@@ -392,6 +392,15 @@
</tr>
<tr>
+ <td>Romanian</td>
+ <td>ro</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ </tr>
+
+ <tr>
<td>Tamil</td>
<td>ta-IN</td>
<td>1</td>
@@ -402,8 +411,8 @@
</table>
<div class="totals">
- <b>Total Languages: </b>42<br />
- <b>Total Packages: </b>673
+ <b>Total Languages: </b>43<br />
+ <b>Total Packages: </b>674
</div>
</body>
</html>
diff --git a/public_html/kn-IN/opds-Fedora.xml b/public_html/kn-IN/opds-Fedora.xml
index d5b7995..46655fc 100644
--- a/public_html/kn-IN/opds-Fedora.xml
+++ b/public_html/kn-IN/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/kn-IN/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2011-08-17T11:44:25</updated>
+ <updated>2011-08-22T23:04:49</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/kn-IN/opds-Fedora_Contributor_Documentation.xml b/public_html/kn-IN/opds-Fedora_Contributor_Documentation.xml
index e5a7ce1..154b525 100644
--- a/public_html/kn-IN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/kn-IN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/kn-IN/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2011-08-17T11:44:25</updated>
+ <updated>2011-08-22T23:04:49</updated>
<!--author>
<name></name>
<uri></uri>
@@ -14,7 +14,7 @@
<entry>
<title>Fedora Elections Guide</title>
- <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub</id>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub</id>
<!--author>
<name></name>
<uri></uri>
@@ -26,7 +26,7 @@
<summary>Fedora Elections Guide
</summary>
<content type="text">This book covers procedural information for the use the Fedora Elections software</content>
- <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub">
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub">
<dc:format>application/epub+zip</dc:format>
</link>
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
diff --git a/public_html/kn-IN/opds-Fedora_Core.xml b/public_html/kn-IN/opds-Fedora_Core.xml
index 7cf94e9..9bbde27 100644
--- a/public_html/kn-IN/opds-Fedora_Core.xml
+++ b/public_html/kn-IN/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/kn-IN/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2011-08-17T11:44:25</updated>
+ <updated>2011-08-22T23:04:49</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/kn-IN/opds-Fedora_Draft_Documentation.xml b/public_html/kn-IN/opds-Fedora_Draft_Documentation.xml
index 3af6ea2..b52cf25 100644
--- a/public_html/kn-IN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/kn-IN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/kn-IN/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2011-08-17T11:44:25</updated>
+ <updated>2011-08-22T23:04:49</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/kn-IN/opds.xml b/public_html/kn-IN/opds.xml
index 735446c..3b53a03 100644
--- a/public_html/kn-IN/opds.xml
+++ b/public_html/kn-IN/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/kn-IN/opds.xml</id>
<title>Product List</title>
- <updated>2011-08-17T11:44:26</updated>
+ <updated>2011-08-22T23:04:49</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/kn-IN/Fedora/opds-Fedora.xml</id>
- <updated>2011-08-17T11:44:25</updated>
+ <updated>2011-08-22T23:04:49</updated>
<dc:language>kn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/kn-IN/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2011-08-17T11:44:25</updated>
+ <updated>2011-08-22T23:04:49</updated>
<dc:language>kn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/kn-IN/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2011-08-17T11:44:25</updated>
+ <updated>2011-08-22T23:04:49</updated>
<dc:language>kn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/kn-IN/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2011-08-17T11:44:25</updated>
+ <updated>2011-08-22T23:04:49</updated>
<dc:language>kn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/kn-IN/toc.html b/public_html/kn-IN/toc.html
index 24d79df..8d2d3b3 100644
--- a/public_html/kn-IN/toc.html
+++ b/public_html/kn-IN/toc.html
@@ -58,6 +58,7 @@
<option value="pl-PL">Polski</option>
<option value="pt-BR">Português Brasileiro</option>
<option value="pt-PT">Português</option>
+ <option value="ro">Romanian</option>
<option value="ru-RU">РуÑÑкий</option>
<option value="sk-SK">SlovenÅ¡Äina</option>
<option value="sr-Latn-RS">Srpski (latinica)</option>
@@ -292,7 +293,7 @@
<a class="type" href="../en-US/./Fedora/13/epub/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/13/html/Accessibility_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/13/html/Accessibility_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/13/html-single/Accessibility_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/13/html-single/Accessibility_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.13.Burning_ISO_images_to_disc' class="book collapsed" onclick="toggle(event, 'Fedora.13.Burning_ISO_images_to_disc.types');">
@@ -609,7 +610,7 @@
<a class="type" href="../en-US/./Fedora/11/epub/Security_Guide/Fedora-11-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/11/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/11/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.11.User_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.11.User_Guide.types');">
@@ -738,7 +739,7 @@
<a class="type" href="../en-US/./Fedora/8/epub/Installation_Guide/Fedora-8-Installation_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/8/html/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/8/html/Installation_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/8/html-single/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/8/html-single/Installation_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-9-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-9-Installation_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-8-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-8-Installation_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.8.Making_Fedora_Discs' class="book collapsed" onclick="toggle(event, 'Fedora.8.Making_Fedora_Discs.types');">
@@ -838,7 +839,7 @@
<div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Fedora_Elections_Guide.types');">
<a class="type" href="../en-US/Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html'"><span class="book">Fedora Elections Guide</span></a>
<div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide.types' class="types hidden" onclick="work=0;">
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
@@ -859,7 +860,7 @@
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/ko-KR/Site_Statistics.html b/public_html/ko-KR/Site_Statistics.html
index e17799c..5501668 100644
--- a/public_html/ko-KR/Site_Statistics.html
+++ b/public_html/ko-KR/Site_Statistics.html
@@ -392,6 +392,15 @@
</tr>
<tr>
+ <td>Romanian</td>
+ <td>ro</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ </tr>
+
+ <tr>
<td>Tamil</td>
<td>ta-IN</td>
<td>1</td>
@@ -402,8 +411,8 @@
</table>
<div class="totals">
- <b>Total Languages: </b>42<br />
- <b>Total Packages: </b>673
+ <b>Total Languages: </b>43<br />
+ <b>Total Packages: </b>674
</div>
</body>
</html>
diff --git a/public_html/ko-KR/opds-Fedora.xml b/public_html/ko-KR/opds-Fedora.xml
index fe0b547..f45da05 100644
--- a/public_html/ko-KR/opds-Fedora.xml
+++ b/public_html/ko-KR/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ko-KR/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2011-08-17T11:44:26</updated>
+ <updated>2011-08-22T23:04:49</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ko-KR/opds-Fedora_Contributor_Documentation.xml b/public_html/ko-KR/opds-Fedora_Contributor_Documentation.xml
index 03a365e..10dbfaa 100644
--- a/public_html/ko-KR/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/ko-KR/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ko-KR/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2011-08-17T11:44:26</updated>
+ <updated>2011-08-22T23:04:49</updated>
<!--author>
<name></name>
<uri></uri>
@@ -14,7 +14,7 @@
<entry>
<title>Fedora Elections Guide</title>
- <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub</id>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub</id>
<!--author>
<name></name>
<uri></uri>
@@ -26,7 +26,7 @@
<summary>Fedora Elections Guide
</summary>
<content type="text">This book covers procedural information for the use the Fedora Elections software</content>
- <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub">
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub">
<dc:format>application/epub+zip</dc:format>
</link>
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
diff --git a/public_html/ko-KR/opds-Fedora_Core.xml b/public_html/ko-KR/opds-Fedora_Core.xml
index e3ed2e0..f86d01b 100644
--- a/public_html/ko-KR/opds-Fedora_Core.xml
+++ b/public_html/ko-KR/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ko-KR/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2011-08-17T11:44:26</updated>
+ <updated>2011-08-22T23:04:49</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ko-KR/opds-Fedora_Draft_Documentation.xml b/public_html/ko-KR/opds-Fedora_Draft_Documentation.xml
index c481afd..a64f4c2 100644
--- a/public_html/ko-KR/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/ko-KR/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ko-KR/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2011-08-17T11:44:26</updated>
+ <updated>2011-08-22T23:04:49</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ko-KR/opds.xml b/public_html/ko-KR/opds.xml
index 90b6c5b..8ac739b 100644
--- a/public_html/ko-KR/opds.xml
+++ b/public_html/ko-KR/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/ko-KR/opds.xml</id>
<title>Product List</title>
- <updated>2011-08-17T11:44:26</updated>
+ <updated>2011-08-22T23:04:49</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/ko-KR/Fedora/opds-Fedora.xml</id>
- <updated>2011-08-17T11:44:26</updated>
+ <updated>2011-08-22T23:04:49</updated>
<dc:language>ko-KR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/ko-KR/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2011-08-17T11:44:26</updated>
+ <updated>2011-08-22T23:04:49</updated>
<dc:language>ko-KR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/ko-KR/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2011-08-17T11:44:26</updated>
+ <updated>2011-08-22T23:04:49</updated>
<dc:language>ko-KR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/ko-KR/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2011-08-17T11:44:26</updated>
+ <updated>2011-08-22T23:04:49</updated>
<dc:language>ko-KR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/ko-KR/toc.html b/public_html/ko-KR/toc.html
index 57a59e6..0343e99 100644
--- a/public_html/ko-KR/toc.html
+++ b/public_html/ko-KR/toc.html
@@ -58,6 +58,7 @@
<option value="pl-PL">Polski</option>
<option value="pt-BR">Português Brasileiro</option>
<option value="pt-PT">Português</option>
+ <option value="ro">Romanian</option>
<option value="ru-RU">РуÑÑкий</option>
<option value="sk-SK">SlovenÅ¡Äina</option>
<option value="sr-Latn-RS">Srpski (latinica)</option>
@@ -292,7 +293,7 @@
<a class="type" href="../en-US/./Fedora/13/epub/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/13/html/Accessibility_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/13/html/Accessibility_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/13/html-single/Accessibility_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/13/html-single/Accessibility_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.13.Burning_ISO_images_to_disc' class="book collapsed" onclick="toggle(event, 'Fedora.13.Burning_ISO_images_to_disc.types');">
@@ -609,7 +610,7 @@
<a class="type" href="../en-US/./Fedora/11/epub/Security_Guide/Fedora-11-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/11/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/11/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.11.User_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.11.User_Guide.types');">
@@ -738,7 +739,7 @@
<a class="type" href="../en-US/./Fedora/8/epub/Installation_Guide/Fedora-8-Installation_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/8/html/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/8/html/Installation_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/8/html-single/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/8/html-single/Installation_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-9-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-9-Installation_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-8-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-8-Installation_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.8.Making_Fedora_Discs' class="book collapsed" onclick="toggle(event, 'Fedora.8.Making_Fedora_Discs.types');">
@@ -838,7 +839,7 @@
<div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Fedora_Elections_Guide.types');">
<a class="type" href="../en-US/Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html'"><span class="book">Fedora Elections Guide</span></a>
<div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide.types' class="types hidden" onclick="work=0;">
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
@@ -859,7 +860,7 @@
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/ml-IN/Site_Statistics.html b/public_html/ml-IN/Site_Statistics.html
index e17799c..5501668 100644
--- a/public_html/ml-IN/Site_Statistics.html
+++ b/public_html/ml-IN/Site_Statistics.html
@@ -392,6 +392,15 @@
</tr>
<tr>
+ <td>Romanian</td>
+ <td>ro</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ </tr>
+
+ <tr>
<td>Tamil</td>
<td>ta-IN</td>
<td>1</td>
@@ -402,8 +411,8 @@
</table>
<div class="totals">
- <b>Total Languages: </b>42<br />
- <b>Total Packages: </b>673
+ <b>Total Languages: </b>43<br />
+ <b>Total Packages: </b>674
</div>
</body>
</html>
diff --git a/public_html/ml-IN/opds-Fedora.xml b/public_html/ml-IN/opds-Fedora.xml
index 594dd5a..126c100 100644
--- a/public_html/ml-IN/opds-Fedora.xml
+++ b/public_html/ml-IN/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ml-IN/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2011-08-17T11:44:26</updated>
+ <updated>2011-08-22T23:04:49</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ml-IN/opds-Fedora_Contributor_Documentation.xml b/public_html/ml-IN/opds-Fedora_Contributor_Documentation.xml
index 014784d..7e9ce15 100644
--- a/public_html/ml-IN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/ml-IN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ml-IN/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2011-08-17T11:44:26</updated>
+ <updated>2011-08-22T23:04:49</updated>
<!--author>
<name></name>
<uri></uri>
@@ -14,7 +14,7 @@
<entry>
<title>Fedora Elections Guide</title>
- <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub</id>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub</id>
<!--author>
<name></name>
<uri></uri>
@@ -26,7 +26,7 @@
<summary>Fedora Elections Guide
</summary>
<content type="text">This book covers procedural information for the use the Fedora Elections software</content>
- <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub">
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub">
<dc:format>application/epub+zip</dc:format>
</link>
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
diff --git a/public_html/ml-IN/opds-Fedora_Core.xml b/public_html/ml-IN/opds-Fedora_Core.xml
index 41c02b7..8d5e82c 100644
--- a/public_html/ml-IN/opds-Fedora_Core.xml
+++ b/public_html/ml-IN/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ml-IN/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2011-08-17T11:44:26</updated>
+ <updated>2011-08-22T23:04:49</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ml-IN/opds-Fedora_Draft_Documentation.xml b/public_html/ml-IN/opds-Fedora_Draft_Documentation.xml
index 6b34c5c..c3397bb 100644
--- a/public_html/ml-IN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/ml-IN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ml-IN/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2011-08-17T11:44:26</updated>
+ <updated>2011-08-22T23:04:49</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ml-IN/opds.xml b/public_html/ml-IN/opds.xml
index fe3e160..533fa1d 100644
--- a/public_html/ml-IN/opds.xml
+++ b/public_html/ml-IN/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/ml-IN/opds.xml</id>
<title>Product List</title>
- <updated>2011-08-17T11:44:26</updated>
+ <updated>2011-08-22T23:04:49</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/ml-IN/Fedora/opds-Fedora.xml</id>
- <updated>2011-08-17T11:44:26</updated>
+ <updated>2011-08-22T23:04:49</updated>
<dc:language>ml-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/ml-IN/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2011-08-17T11:44:26</updated>
+ <updated>2011-08-22T23:04:49</updated>
<dc:language>ml-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/ml-IN/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2011-08-17T11:44:26</updated>
+ <updated>2011-08-22T23:04:49</updated>
<dc:language>ml-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/ml-IN/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2011-08-17T11:44:26</updated>
+ <updated>2011-08-22T23:04:49</updated>
<dc:language>ml-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/ml-IN/toc.html b/public_html/ml-IN/toc.html
index 2bad8f3..4b7b331 100644
--- a/public_html/ml-IN/toc.html
+++ b/public_html/ml-IN/toc.html
@@ -58,6 +58,7 @@
<option value="pl-PL">Polski</option>
<option value="pt-BR">Português Brasileiro</option>
<option value="pt-PT">Português</option>
+ <option value="ro">Romanian</option>
<option value="ru-RU">РуÑÑкий</option>
<option value="sk-SK">SlovenÅ¡Äina</option>
<option value="sr-Latn-RS">Srpski (latinica)</option>
@@ -292,7 +293,7 @@
<a class="type" href="../en-US/./Fedora/13/epub/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/13/html/Accessibility_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/13/html/Accessibility_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/13/html-single/Accessibility_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/13/html-single/Accessibility_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.13.Burning_ISO_images_to_disc' class="book collapsed" onclick="toggle(event, 'Fedora.13.Burning_ISO_images_to_disc.types');">
@@ -609,7 +610,7 @@
<a class="type" href="../en-US/./Fedora/11/epub/Security_Guide/Fedora-11-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/11/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/11/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.11.User_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.11.User_Guide.types');">
@@ -738,7 +739,7 @@
<a class="type" href="../en-US/./Fedora/8/epub/Installation_Guide/Fedora-8-Installation_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/8/html/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/8/html/Installation_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/8/html-single/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/8/html-single/Installation_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-9-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-9-Installation_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-8-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-8-Installation_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.8.Making_Fedora_Discs' class="book collapsed" onclick="toggle(event, 'Fedora.8.Making_Fedora_Discs.types');">
@@ -838,7 +839,7 @@
<div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Fedora_Elections_Guide.types');">
<a class="type" href="../en-US/Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html'"><span class="book">Fedora Elections Guide</span></a>
<div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide.types' class="types hidden" onclick="work=0;">
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
@@ -859,7 +860,7 @@
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/mr-IN/Site_Statistics.html b/public_html/mr-IN/Site_Statistics.html
index e17799c..5501668 100644
--- a/public_html/mr-IN/Site_Statistics.html
+++ b/public_html/mr-IN/Site_Statistics.html
@@ -392,6 +392,15 @@
</tr>
<tr>
+ <td>Romanian</td>
+ <td>ro</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ </tr>
+
+ <tr>
<td>Tamil</td>
<td>ta-IN</td>
<td>1</td>
@@ -402,8 +411,8 @@
</table>
<div class="totals">
- <b>Total Languages: </b>42<br />
- <b>Total Packages: </b>673
+ <b>Total Languages: </b>43<br />
+ <b>Total Packages: </b>674
</div>
</body>
</html>
diff --git a/public_html/mr-IN/opds-Fedora.xml b/public_html/mr-IN/opds-Fedora.xml
index 4ea90e5..d85ff02 100644
--- a/public_html/mr-IN/opds-Fedora.xml
+++ b/public_html/mr-IN/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/mr-IN/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2011-08-17T11:44:26</updated>
+ <updated>2011-08-22T23:04:49</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/mr-IN/opds-Fedora_Contributor_Documentation.xml b/public_html/mr-IN/opds-Fedora_Contributor_Documentation.xml
index bada612..333eff7 100644
--- a/public_html/mr-IN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/mr-IN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/mr-IN/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2011-08-17T11:44:26</updated>
+ <updated>2011-08-22T23:04:49</updated>
<!--author>
<name></name>
<uri></uri>
@@ -14,7 +14,7 @@
<entry>
<title>Fedora Elections Guide</title>
- <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub</id>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub</id>
<!--author>
<name></name>
<uri></uri>
@@ -26,7 +26,7 @@
<summary>Fedora Elections Guide
</summary>
<content type="text">This book covers procedural information for the use the Fedora Elections software</content>
- <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub">
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub">
<dc:format>application/epub+zip</dc:format>
</link>
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
diff --git a/public_html/mr-IN/opds-Fedora_Core.xml b/public_html/mr-IN/opds-Fedora_Core.xml
index 21c808e..b359b48 100644
--- a/public_html/mr-IN/opds-Fedora_Core.xml
+++ b/public_html/mr-IN/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/mr-IN/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2011-08-17T11:44:26</updated>
+ <updated>2011-08-22T23:04:49</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/mr-IN/opds-Fedora_Draft_Documentation.xml b/public_html/mr-IN/opds-Fedora_Draft_Documentation.xml
index 003744d..fbab52b 100644
--- a/public_html/mr-IN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/mr-IN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/mr-IN/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2011-08-17T11:44:26</updated>
+ <updated>2011-08-22T23:04:49</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/mr-IN/opds.xml b/public_html/mr-IN/opds.xml
index 15f706c..e8cbc56 100644
--- a/public_html/mr-IN/opds.xml
+++ b/public_html/mr-IN/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/mr-IN/opds.xml</id>
<title>Product List</title>
- <updated>2011-08-17T11:44:26</updated>
+ <updated>2011-08-22T23:04:49</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/mr-IN/Fedora/opds-Fedora.xml</id>
- <updated>2011-08-17T11:44:26</updated>
+ <updated>2011-08-22T23:04:49</updated>
<dc:language>mr-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/mr-IN/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2011-08-17T11:44:26</updated>
+ <updated>2011-08-22T23:04:49</updated>
<dc:language>mr-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/mr-IN/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2011-08-17T11:44:26</updated>
+ <updated>2011-08-22T23:04:49</updated>
<dc:language>mr-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/mr-IN/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2011-08-17T11:44:26</updated>
+ <updated>2011-08-22T23:04:49</updated>
<dc:language>mr-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/mr-IN/toc.html b/public_html/mr-IN/toc.html
index 3cc05d5..4b3f9ba 100644
--- a/public_html/mr-IN/toc.html
+++ b/public_html/mr-IN/toc.html
@@ -58,6 +58,7 @@
<option value="pl-PL">Polski</option>
<option value="pt-BR">Português Brasileiro</option>
<option value="pt-PT">Português</option>
+ <option value="ro">Romanian</option>
<option value="ru-RU">РуÑÑкий</option>
<option value="sk-SK">SlovenÅ¡Äina</option>
<option value="sr-Latn-RS">Srpski (latinica)</option>
@@ -292,7 +293,7 @@
<a class="type" href="../en-US/./Fedora/13/epub/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/13/html/Accessibility_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/13/html/Accessibility_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/13/html-single/Accessibility_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/13/html-single/Accessibility_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.13.Burning_ISO_images_to_disc' class="book collapsed" onclick="toggle(event, 'Fedora.13.Burning_ISO_images_to_disc.types');">
@@ -609,7 +610,7 @@
<a class="type" href="../en-US/./Fedora/11/epub/Security_Guide/Fedora-11-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/11/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/11/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.11.User_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.11.User_Guide.types');">
@@ -738,7 +739,7 @@
<a class="type" href="../en-US/./Fedora/8/epub/Installation_Guide/Fedora-8-Installation_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/8/html/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/8/html/Installation_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/8/html-single/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/8/html-single/Installation_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-9-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-9-Installation_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-8-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-8-Installation_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.8.Making_Fedora_Discs' class="book collapsed" onclick="toggle(event, 'Fedora.8.Making_Fedora_Discs.types');">
@@ -838,7 +839,7 @@
<div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Fedora_Elections_Guide.types');">
<a class="type" href="../en-US/Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html'"><span class="book">Fedora Elections Guide</span></a>
<div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide.types' class="types hidden" onclick="work=0;">
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
@@ -859,7 +860,7 @@
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/nb-NO/Site_Statistics.html b/public_html/nb-NO/Site_Statistics.html
index e17799c..5501668 100644
--- a/public_html/nb-NO/Site_Statistics.html
+++ b/public_html/nb-NO/Site_Statistics.html
@@ -392,6 +392,15 @@
</tr>
<tr>
+ <td>Romanian</td>
+ <td>ro</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ </tr>
+
+ <tr>
<td>Tamil</td>
<td>ta-IN</td>
<td>1</td>
@@ -402,8 +411,8 @@
</table>
<div class="totals">
- <b>Total Languages: </b>42<br />
- <b>Total Packages: </b>673
+ <b>Total Languages: </b>43<br />
+ <b>Total Packages: </b>674
</div>
</body>
</html>
diff --git a/public_html/nb-NO/opds-Fedora.xml b/public_html/nb-NO/opds-Fedora.xml
index 95f853f..534b396 100644
--- a/public_html/nb-NO/opds-Fedora.xml
+++ b/public_html/nb-NO/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/nb-NO/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2011-08-17T11:44:26</updated>
+ <updated>2011-08-22T23:04:49</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/nb-NO/opds-Fedora_Contributor_Documentation.xml b/public_html/nb-NO/opds-Fedora_Contributor_Documentation.xml
index 8b62ee7..5a4f060 100644
--- a/public_html/nb-NO/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/nb-NO/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/nb-NO/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2011-08-17T11:44:26</updated>
+ <updated>2011-08-22T23:04:49</updated>
<!--author>
<name></name>
<uri></uri>
@@ -14,7 +14,7 @@
<entry>
<title>Fedora Elections Guide</title>
- <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub</id>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub</id>
<!--author>
<name></name>
<uri></uri>
@@ -26,7 +26,7 @@
<summary>Fedora Elections Guide
</summary>
<content type="text">This book covers procedural information for the use the Fedora Elections software</content>
- <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub">
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub">
<dc:format>application/epub+zip</dc:format>
</link>
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
diff --git a/public_html/nb-NO/opds-Fedora_Core.xml b/public_html/nb-NO/opds-Fedora_Core.xml
index b66d9fe..c1efeee 100644
--- a/public_html/nb-NO/opds-Fedora_Core.xml
+++ b/public_html/nb-NO/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/nb-NO/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2011-08-17T11:44:26</updated>
+ <updated>2011-08-22T23:04:49</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/nb-NO/opds-Fedora_Draft_Documentation.xml b/public_html/nb-NO/opds-Fedora_Draft_Documentation.xml
index 8b577fe..2182965 100644
--- a/public_html/nb-NO/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/nb-NO/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/nb-NO/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2011-08-17T11:44:26</updated>
+ <updated>2011-08-22T23:04:49</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/nb-NO/opds.xml b/public_html/nb-NO/opds.xml
index 71a3610..668e89e 100644
--- a/public_html/nb-NO/opds.xml
+++ b/public_html/nb-NO/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/nb-NO/opds.xml</id>
<title>Product List</title>
- <updated>2011-08-17T11:44:26</updated>
+ <updated>2011-08-22T23:04:49</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/nb-NO/Fedora/opds-Fedora.xml</id>
- <updated>2011-08-17T11:44:26</updated>
+ <updated>2011-08-22T23:04:49</updated>
<dc:language>nb-NO</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/nb-NO/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2011-08-17T11:44:26</updated>
+ <updated>2011-08-22T23:04:49</updated>
<dc:language>nb-NO</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/nb-NO/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2011-08-17T11:44:26</updated>
+ <updated>2011-08-22T23:04:49</updated>
<dc:language>nb-NO</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/nb-NO/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2011-08-17T11:44:26</updated>
+ <updated>2011-08-22T23:04:49</updated>
<dc:language>nb-NO</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/nb-NO/toc.html b/public_html/nb-NO/toc.html
index c24bcbd..792b3ce 100644
--- a/public_html/nb-NO/toc.html
+++ b/public_html/nb-NO/toc.html
@@ -58,6 +58,7 @@
<option value="pl-PL">Polski</option>
<option value="pt-BR">Português Brasileiro</option>
<option value="pt-PT">Português</option>
+ <option value="ro">Romanian</option>
<option value="ru-RU">РуÑÑкий</option>
<option value="sk-SK">SlovenÅ¡Äina</option>
<option value="sr-Latn-RS">Srpski (latinica)</option>
@@ -292,7 +293,7 @@
<a class="type" href="../en-US/./Fedora/13/epub/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/13/html/Accessibility_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/13/html/Accessibility_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/13/html-single/Accessibility_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/13/html-single/Accessibility_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.13.Burning_ISO_images_to_disc' class="book collapsed" onclick="toggle(event, 'Fedora.13.Burning_ISO_images_to_disc.types');">
@@ -609,7 +610,7 @@
<a class="type" href="../en-US/./Fedora/11/epub/Security_Guide/Fedora-11-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/11/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/11/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.11.User_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.11.User_Guide.types');">
@@ -747,7 +748,7 @@
<a class="type" href="../en-US/./Fedora/8/epub/Installation_Guide/Fedora-8-Installation_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/8/html/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/8/html/Installation_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/8/html-single/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/8/html-single/Installation_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-9-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-9-Installation_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-8-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-8-Installation_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.8.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.8.Release_Notes.types');">
@@ -838,7 +839,7 @@
<div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Fedora_Elections_Guide.types');">
<a class="type" href="../en-US/Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html'"><span class="book">Fedora Elections Guide</span></a>
<div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide.types' class="types hidden" onclick="work=0;">
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
@@ -859,7 +860,7 @@
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/nl-NL/Site_Statistics.html b/public_html/nl-NL/Site_Statistics.html
index 8fd84e4..6ff0929 100644
--- a/public_html/nl-NL/Site_Statistics.html
+++ b/public_html/nl-NL/Site_Statistics.html
@@ -392,6 +392,15 @@
</tr>
<tr>
+ <td>Romanian</td>
+ <td>ro</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ </tr>
+
+ <tr>
<td>Tamil</td>
<td>ta-IN</td>
<td>1</td>
@@ -402,8 +411,8 @@
</table>
<div class="totals">
- <b>Totaal talen: </b>42<br />
- <b>Totaal pakketten: </b>673
+ <b>Totaal talen: </b>43<br />
+ <b>Totaal pakketten: </b>674
</div>
</body>
</html>
diff --git a/public_html/nl-NL/opds-Fedora.xml b/public_html/nl-NL/opds-Fedora.xml
index dc43a42..60b2729 100644
--- a/public_html/nl-NL/opds-Fedora.xml
+++ b/public_html/nl-NL/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/nl-NL/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2011-08-17T11:44:27</updated>
+ <updated>2011-08-22T23:04:50</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/nl-NL/opds-Fedora_Contributor_Documentation.xml b/public_html/nl-NL/opds-Fedora_Contributor_Documentation.xml
index b63a846..0b5ea45 100644
--- a/public_html/nl-NL/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/nl-NL/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/nl-NL/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2011-08-17T11:44:27</updated>
+ <updated>2011-08-22T23:04:50</updated>
<!--author>
<name></name>
<uri></uri>
@@ -14,7 +14,7 @@
<entry>
<title>Fedora Elections Guide</title>
- <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub</id>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub</id>
<!--author>
<name></name>
<uri></uri>
@@ -26,7 +26,7 @@
<summary>Fedora Elections Guide
</summary>
<content type="text">This book covers procedural information for the use the Fedora Elections software</content>
- <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub">
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub">
<dc:format>application/epub+zip</dc:format>
</link>
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
diff --git a/public_html/nl-NL/opds-Fedora_Core.xml b/public_html/nl-NL/opds-Fedora_Core.xml
index 845385d..3ebd8a7 100644
--- a/public_html/nl-NL/opds-Fedora_Core.xml
+++ b/public_html/nl-NL/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/nl-NL/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2011-08-17T11:44:27</updated>
+ <updated>2011-08-22T23:04:50</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/nl-NL/opds-Fedora_Draft_Documentation.xml b/public_html/nl-NL/opds-Fedora_Draft_Documentation.xml
index b44f860..5047ead 100644
--- a/public_html/nl-NL/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/nl-NL/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/nl-NL/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2011-08-17T11:44:27</updated>
+ <updated>2011-08-22T23:04:50</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/nl-NL/opds.xml b/public_html/nl-NL/opds.xml
index b3a02b9..c516321 100644
--- a/public_html/nl-NL/opds.xml
+++ b/public_html/nl-NL/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/nl-NL/opds.xml</id>
<title>Product List</title>
- <updated>2011-08-17T11:44:27</updated>
+ <updated>2011-08-22T23:04:50</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/nl-NL/Fedora/opds-Fedora.xml</id>
- <updated>2011-08-17T11:44:27</updated>
+ <updated>2011-08-22T23:04:50</updated>
<dc:language>nl-NL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/nl-NL/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2011-08-17T11:44:27</updated>
+ <updated>2011-08-22T23:04:50</updated>
<dc:language>nl-NL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/nl-NL/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2011-08-17T11:44:27</updated>
+ <updated>2011-08-22T23:04:50</updated>
<dc:language>nl-NL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/nl-NL/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2011-08-17T11:44:27</updated>
+ <updated>2011-08-22T23:04:50</updated>
<dc:language>nl-NL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/nl-NL/toc.html b/public_html/nl-NL/toc.html
index 008111c..6393cb3 100644
--- a/public_html/nl-NL/toc.html
+++ b/public_html/nl-NL/toc.html
@@ -58,6 +58,7 @@
<option value="pl-PL">Polski</option>
<option value="pt-BR">Português Brasileiro</option>
<option value="pt-PT">Português</option>
+ <option value="ro">Romanian</option>
<option value="ru-RU">РуÑÑкий</option>
<option value="sk-SK">SlovenÅ¡Äina</option>
<option value="sr-Latn-RS">Srpski (latinica)</option>
@@ -286,7 +287,7 @@
<a class="type" href="./Fedora/13/epub/Accessibility_Guide/Fedora-13-Accessibility_Guide-nl-NL.epub" >epub</a>
<a class="type" href="./Fedora/13/html/Accessibility_Guide/index.html" onclick="window.top.location='./Fedora/13/html/Accessibility_Guide/index.html';return false;">html</a>
<a class="type" href="./Fedora/13/html-single/Accessibility_Guide/index.html" onclick="window.top.location='./Fedora/13/html-single/Accessibility_Guide/index.html';return false;">html-single</a>
- <a class="type" href="./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-nl-NL.pdf" onclick="window.top.location='./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-nl-NL.pdf';return false;">pdf</a>
+ <a class="type" href="./Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-nl-NL.pdf" onclick="window.top.location='./Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-nl-NL.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.13.Burning_ISO_images_to_disc' class="book collapsed">
@@ -1015,7 +1016,7 @@
<div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Fedora_Elections_Guide.types');">
<a class="type" href="../en-US/Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html'"><span class="book">Fedora Elections Guide</span></a>
<div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide.types' class="types hidden" onclick="work=0;">
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
@@ -1036,7 +1037,7 @@
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/opds.xml b/public_html/opds.xml
index 741c435..a644c58 100644
--- a/public_html/opds.xml
+++ b/public_html/opds.xml
@@ -7,7 +7,7 @@
<link rel="start" href="http://docs.fedoraproject.org/opds.xml" type="application/atom+xml;type=feed;profile=opds-catalog"/>
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<title>Fedora Documentation</title>
- <updated>2011-08-17T11:44:31</updated>
+ <updated>2011-08-22T23:04:55</updated>
<!--author>
<name></name>
<uri></uri>
@@ -16,7 +16,7 @@
<entry>
<title>অসমীয়া</title>
<id>as-IN/opds.xml</id>
- <updated>2011-08-17T11:44:21</updated>
+ <updated>2011-08-22T23:04:43</updated>
<dc:language>as-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="as-IN/opds.xml"/>
@@ -24,7 +24,7 @@
<entry>
<title>българÑки</title>
<id>bg-BG/opds.xml</id>
- <updated>2011-08-17T11:44:21</updated>
+ <updated>2011-08-22T23:04:44</updated>
<dc:language>bg-BG</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="bg-BG/opds.xml"/>
@@ -32,7 +32,7 @@
<entry>
<title>বাংলা</title>
<id>bn-IN/opds.xml</id>
- <updated>2011-08-17T11:44:21</updated>
+ <updated>2011-08-22T23:04:44</updated>
<dc:language>bn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="bn-IN/opds.xml"/>
@@ -40,7 +40,7 @@
<entry>
<title>Bosanski</title>
<id>bs-BA/opds.xml</id>
- <updated>2011-08-17T11:44:21</updated>
+ <updated>2011-08-22T23:04:44</updated>
<dc:language>bs-BA</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="bs-BA/opds.xml"/>
@@ -48,7 +48,7 @@
<entry>
<title>Català </title>
<id>ca-ES/opds.xml</id>
- <updated>2011-08-17T11:44:22</updated>
+ <updated>2011-08-22T23:04:44</updated>
<dc:language>ca-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="ca-ES/opds.xml"/>
@@ -56,7 +56,7 @@
<entry>
<title>Čeština</title>
<id>cs-CZ/opds.xml</id>
- <updated>2011-08-17T11:44:22</updated>
+ <updated>2011-08-22T23:04:44</updated>
<dc:language>cs-CZ</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="cs-CZ/opds.xml"/>
@@ -64,7 +64,7 @@
<entry>
<title>Dansk</title>
<id>da-DK/opds.xml</id>
- <updated>2011-08-17T11:44:22</updated>
+ <updated>2011-08-22T23:04:45</updated>
<dc:language>da-DK</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="da-DK/opds.xml"/>
@@ -72,7 +72,7 @@
<entry>
<title>Deutsch</title>
<id>de-DE/opds.xml</id>
- <updated>2011-08-17T11:44:22</updated>
+ <updated>2011-08-22T23:04:45</updated>
<dc:language>de-DE</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="de-DE/opds.xml"/>
@@ -80,7 +80,7 @@
<entry>
<title>Ελληνικά</title>
<id>el-GR/opds.xml</id>
- <updated>2011-08-17T11:44:23</updated>
+ <updated>2011-08-22T23:04:45</updated>
<dc:language>el-GR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="el-GR/opds.xml"/>
@@ -88,7 +88,7 @@
<entry>
<title>English</title>
<id>en-US/opds.xml</id>
- <updated>2011-08-17T11:44:23</updated>
+ <updated>2011-08-22T23:04:45</updated>
<dc:language>en-US</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="en-US/opds.xml"/>
@@ -96,7 +96,7 @@
<entry>
<title>Español</title>
<id>es-ES/opds.xml</id>
- <updated>2011-08-17T11:44:23</updated>
+ <updated>2011-08-22T23:04:46</updated>
<dc:language>es-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="es-ES/opds.xml"/>
@@ -104,7 +104,7 @@
<entry>
<title>Ùارسی</title>
<id>fa-IR/opds.xml</id>
- <updated>2011-08-17T11:44:23</updated>
+ <updated>2011-08-22T23:04:46</updated>
<dc:language>fa-IR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="fa-IR/opds.xml"/>
@@ -112,7 +112,7 @@
<entry>
<title>Suomi</title>
<id>fi-FI/opds.xml</id>
- <updated>2011-08-17T11:44:23</updated>
+ <updated>2011-08-22T23:04:47</updated>
<dc:language>fi-FI</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="fi-FI/opds.xml"/>
@@ -120,7 +120,7 @@
<entry>
<title>Français</title>
<id>fr-FR/opds.xml</id>
- <updated>2011-08-17T11:44:24</updated>
+ <updated>2011-08-22T23:04:47</updated>
<dc:language>fr-FR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="fr-FR/opds.xml"/>
@@ -128,7 +128,7 @@
<entry>
<title>ગà«àªœàª°àª¾àª¤à«€</title>
<id>gu-IN/opds.xml</id>
- <updated>2011-08-17T11:44:24</updated>
+ <updated>2011-08-22T23:04:47</updated>
<dc:language>gu-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="gu-IN/opds.xml"/>
@@ -136,7 +136,7 @@
<entry>
<title>עברית</title>
<id>he-IL/opds.xml</id>
- <updated>2011-08-17T11:44:24</updated>
+ <updated>2011-08-22T23:04:47</updated>
<dc:language>he-IL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="he-IL/opds.xml"/>
@@ -144,7 +144,7 @@
<entry>
<title>हिनà¥à¤¦à¥€</title>
<id>hi-IN/opds.xml</id>
- <updated>2011-08-17T11:44:24</updated>
+ <updated>2011-08-22T23:04:47</updated>
<dc:language>hi-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="hi-IN/opds.xml"/>
@@ -152,7 +152,7 @@
<entry>
<title>Magyar</title>
<id>hu-HU/opds.xml</id>
- <updated>2011-08-17T11:44:25</updated>
+ <updated>2011-08-22T23:04:48</updated>
<dc:language>hu-HU</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="hu-HU/opds.xml"/>
@@ -160,7 +160,7 @@
<entry>
<title>Indonesia</title>
<id>id-ID/opds.xml</id>
- <updated>2011-08-17T11:44:25</updated>
+ <updated>2011-08-22T23:04:48</updated>
<dc:language>id-ID</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="id-ID/opds.xml"/>
@@ -168,7 +168,7 @@
<entry>
<title>Italiano</title>
<id>it-IT/opds.xml</id>
- <updated>2011-08-17T11:44:25</updated>
+ <updated>2011-08-22T23:04:48</updated>
<dc:language>it-IT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="it-IT/opds.xml"/>
@@ -176,7 +176,7 @@
<entry>
<title>日本語</title>
<id>ja-JP/opds.xml</id>
- <updated>2011-08-17T11:44:25</updated>
+ <updated>2011-08-22T23:04:49</updated>
<dc:language>ja-JP</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="ja-JP/opds.xml"/>
@@ -184,7 +184,7 @@
<entry>
<title>ಕನà³à²¨à²¡</title>
<id>kn-IN/opds.xml</id>
- <updated>2011-08-17T11:44:26</updated>
+ <updated>2011-08-22T23:04:49</updated>
<dc:language>kn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="kn-IN/opds.xml"/>
@@ -192,7 +192,7 @@
<entry>
<title>í•œêµì–´</title>
<id>ko-KR/opds.xml</id>
- <updated>2011-08-17T11:44:26</updated>
+ <updated>2011-08-22T23:04:49</updated>
<dc:language>ko-KR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="ko-KR/opds.xml"/>
@@ -200,7 +200,7 @@
<entry>
<title>മലയാളം</title>
<id>ml-IN/opds.xml</id>
- <updated>2011-08-17T11:44:26</updated>
+ <updated>2011-08-22T23:04:49</updated>
<dc:language>ml-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="ml-IN/opds.xml"/>
@@ -208,7 +208,7 @@
<entry>
<title>मराठी</title>
<id>mr-IN/opds.xml</id>
- <updated>2011-08-17T11:44:26</updated>
+ <updated>2011-08-22T23:04:49</updated>
<dc:language>mr-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="mr-IN/opds.xml"/>
@@ -216,7 +216,7 @@
<entry>
<title>Norsk (bokmål)</title>
<id>nb-NO/opds.xml</id>
- <updated>2011-08-17T11:44:26</updated>
+ <updated>2011-08-22T23:04:49</updated>
<dc:language>nb-NO</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="nb-NO/opds.xml"/>
@@ -224,7 +224,7 @@
<entry>
<title>Nederlands</title>
<id>nl-NL/opds.xml</id>
- <updated>2011-08-17T11:44:27</updated>
+ <updated>2011-08-22T23:04:50</updated>
<dc:language>nl-NL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="nl-NL/opds.xml"/>
@@ -232,7 +232,7 @@
<entry>
<title>ଓଡ଼ିଆ</title>
<id>or-IN/opds.xml</id>
- <updated>2011-08-17T11:44:27</updated>
+ <updated>2011-08-22T23:04:50</updated>
<dc:language>or-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="or-IN/opds.xml"/>
@@ -240,7 +240,7 @@
<entry>
<title>ਪੰਜਾਬੀ</title>
<id>pa-IN/opds.xml</id>
- <updated>2011-08-17T11:44:27</updated>
+ <updated>2011-08-22T23:04:50</updated>
<dc:language>pa-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="pa-IN/opds.xml"/>
@@ -248,7 +248,7 @@
<entry>
<title>Polski</title>
<id>pl-PL/opds.xml</id>
- <updated>2011-08-17T11:44:27</updated>
+ <updated>2011-08-22T23:04:51</updated>
<dc:language>pl-PL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="pl-PL/opds.xml"/>
@@ -256,7 +256,7 @@
<entry>
<title>Português Brasileiro</title>
<id>pt-BR/opds.xml</id>
- <updated>2011-08-17T11:44:28</updated>
+ <updated>2011-08-22T23:04:51</updated>
<dc:language>pt-BR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="pt-BR/opds.xml"/>
@@ -264,15 +264,23 @@
<entry>
<title>Português</title>
<id>pt-PT/opds.xml</id>
- <updated>2011-08-17T11:44:28</updated>
+ <updated>2011-08-22T23:04:52</updated>
<dc:language>pt-PT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="pt-PT/opds.xml"/>
</entry>
<entry>
+ <title>Romanian</title>
+ <id>ro/opds.xml</id>
+ <updated>2011-08-22T23:04:52</updated>
+ <dc:language>ro</dc:language>
+ <content type="text"></content>
+ <link type="application/atom+xml" href="ro/opds.xml"/>
+ </entry>
+ <entry>
<title>РуÑÑкий</title>
<id>ru-RU/opds.xml</id>
- <updated>2011-08-17T11:44:28</updated>
+ <updated>2011-08-22T23:04:52</updated>
<dc:language>ru-RU</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="ru-RU/opds.xml"/>
@@ -280,7 +288,7 @@
<entry>
<title>SlovenÅ¡Äina</title>
<id>sk-SK/opds.xml</id>
- <updated>2011-08-17T11:44:28</updated>
+ <updated>2011-08-22T23:04:52</updated>
<dc:language>sk-SK</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="sk-SK/opds.xml"/>
@@ -288,7 +296,7 @@
<entry>
<title>Srpski (latinica)</title>
<id>sr-Latn-RS/opds.xml</id>
- <updated>2011-08-17T11:44:29</updated>
+ <updated>2011-08-22T23:04:53</updated>
<dc:language>sr-Latn-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="sr-Latn-RS/opds.xml"/>
@@ -296,7 +304,7 @@
<entry>
<title>СрпÑки</title>
<id>sr-RS/opds.xml</id>
- <updated>2011-08-17T11:44:29</updated>
+ <updated>2011-08-22T23:04:53</updated>
<dc:language>sr-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="sr-RS/opds.xml"/>
@@ -304,7 +312,7 @@
<entry>
<title>Svenska</title>
<id>sv-SE/opds.xml</id>
- <updated>2011-08-17T11:44:29</updated>
+ <updated>2011-08-22T23:04:53</updated>
<dc:language>sv-SE</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="sv-SE/opds.xml"/>
@@ -312,7 +320,7 @@
<entry>
<title>தமிழà¯</title>
<id>ta-IN/opds.xml</id>
- <updated>2011-08-17T11:44:29</updated>
+ <updated>2011-08-22T23:04:54</updated>
<dc:language>ta-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="ta-IN/opds.xml"/>
@@ -320,7 +328,7 @@
<entry>
<title>తెలà±à°—à±</title>
<id>te-IN/opds.xml</id>
- <updated>2011-08-17T11:44:29</updated>
+ <updated>2011-08-22T23:04:54</updated>
<dc:language>te-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="te-IN/opds.xml"/>
@@ -328,7 +336,7 @@
<entry>
<title>УкраїнÑька</title>
<id>uk-UA/opds.xml</id>
- <updated>2011-08-17T11:44:30</updated>
+ <updated>2011-08-22T23:04:54</updated>
<dc:language>uk-UA</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="uk-UA/opds.xml"/>
@@ -336,7 +344,7 @@
<entry>
<title>简体ä¸æ–‡</title>
<id>zh-CN/opds.xml</id>
- <updated>2011-08-17T11:44:30</updated>
+ <updated>2011-08-22T23:04:54</updated>
<dc:language>zh-CN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="zh-CN/opds.xml"/>
@@ -344,7 +352,7 @@
<entry>
<title>ç¹é«”ä¸æ–‡</title>
<id>zh-TW/opds.xml</id>
- <updated>2011-08-17T11:44:30</updated>
+ <updated>2011-08-22T23:04:54</updated>
<dc:language>zh-TW</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="zh-TW/opds.xml"/>
diff --git a/public_html/or-IN/Site_Statistics.html b/public_html/or-IN/Site_Statistics.html
index e17799c..5501668 100644
--- a/public_html/or-IN/Site_Statistics.html
+++ b/public_html/or-IN/Site_Statistics.html
@@ -392,6 +392,15 @@
</tr>
<tr>
+ <td>Romanian</td>
+ <td>ro</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ </tr>
+
+ <tr>
<td>Tamil</td>
<td>ta-IN</td>
<td>1</td>
@@ -402,8 +411,8 @@
</table>
<div class="totals">
- <b>Total Languages: </b>42<br />
- <b>Total Packages: </b>673
+ <b>Total Languages: </b>43<br />
+ <b>Total Packages: </b>674
</div>
</body>
</html>
diff --git a/public_html/or-IN/opds-Fedora.xml b/public_html/or-IN/opds-Fedora.xml
index 79baef5..88625f6 100644
--- a/public_html/or-IN/opds-Fedora.xml
+++ b/public_html/or-IN/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/or-IN/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2011-08-17T11:44:27</updated>
+ <updated>2011-08-22T23:04:50</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/or-IN/opds-Fedora_Contributor_Documentation.xml b/public_html/or-IN/opds-Fedora_Contributor_Documentation.xml
index 0ac6355..00f0158 100644
--- a/public_html/or-IN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/or-IN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/or-IN/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2011-08-17T11:44:27</updated>
+ <updated>2011-08-22T23:04:50</updated>
<!--author>
<name></name>
<uri></uri>
@@ -14,7 +14,7 @@
<entry>
<title>Fedora Elections Guide</title>
- <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub</id>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub</id>
<!--author>
<name></name>
<uri></uri>
@@ -26,7 +26,7 @@
<summary>Fedora Elections Guide
</summary>
<content type="text">This book covers procedural information for the use the Fedora Elections software</content>
- <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub">
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub">
<dc:format>application/epub+zip</dc:format>
</link>
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
diff --git a/public_html/or-IN/opds-Fedora_Core.xml b/public_html/or-IN/opds-Fedora_Core.xml
index 60b4b06..63fa4c7 100644
--- a/public_html/or-IN/opds-Fedora_Core.xml
+++ b/public_html/or-IN/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/or-IN/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2011-08-17T11:44:27</updated>
+ <updated>2011-08-22T23:04:50</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/or-IN/opds-Fedora_Draft_Documentation.xml b/public_html/or-IN/opds-Fedora_Draft_Documentation.xml
index 677b437..3322cac 100644
--- a/public_html/or-IN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/or-IN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/or-IN/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2011-08-17T11:44:27</updated>
+ <updated>2011-08-22T23:04:50</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/or-IN/opds.xml b/public_html/or-IN/opds.xml
index 3e35eb2..4ca2305 100644
--- a/public_html/or-IN/opds.xml
+++ b/public_html/or-IN/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/or-IN/opds.xml</id>
<title>Product List</title>
- <updated>2011-08-17T11:44:27</updated>
+ <updated>2011-08-22T23:04:50</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/or-IN/Fedora/opds-Fedora.xml</id>
- <updated>2011-08-17T11:44:27</updated>
+ <updated>2011-08-22T23:04:50</updated>
<dc:language>or-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/or-IN/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2011-08-17T11:44:27</updated>
+ <updated>2011-08-22T23:04:50</updated>
<dc:language>or-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/or-IN/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2011-08-17T11:44:27</updated>
+ <updated>2011-08-22T23:04:50</updated>
<dc:language>or-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/or-IN/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2011-08-17T11:44:27</updated>
+ <updated>2011-08-22T23:04:50</updated>
<dc:language>or-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/or-IN/toc.html b/public_html/or-IN/toc.html
index 81d10fa..daacb2e 100644
--- a/public_html/or-IN/toc.html
+++ b/public_html/or-IN/toc.html
@@ -58,6 +58,7 @@
<option value="pl-PL">Polski</option>
<option value="pt-BR">Português Brasileiro</option>
<option value="pt-PT">Português</option>
+ <option value="ro">Romanian</option>
<option value="ru-RU">РуÑÑкий</option>
<option value="sk-SK">SlovenÅ¡Äina</option>
<option value="sr-Latn-RS">Srpski (latinica)</option>
@@ -292,7 +293,7 @@
<a class="type" href="../en-US/./Fedora/13/epub/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/13/html/Accessibility_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/13/html/Accessibility_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/13/html-single/Accessibility_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/13/html-single/Accessibility_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.13.Burning_ISO_images_to_disc' class="book collapsed" onclick="toggle(event, 'Fedora.13.Burning_ISO_images_to_disc.types');">
@@ -609,7 +610,7 @@
<a class="type" href="../en-US/./Fedora/11/epub/Security_Guide/Fedora-11-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/11/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/11/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.11.User_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.11.User_Guide.types');">
@@ -738,7 +739,7 @@
<a class="type" href="../en-US/./Fedora/8/epub/Installation_Guide/Fedora-8-Installation_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/8/html/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/8/html/Installation_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/8/html-single/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/8/html-single/Installation_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-9-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-9-Installation_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-8-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-8-Installation_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.8.Making_Fedora_Discs' class="book collapsed" onclick="toggle(event, 'Fedora.8.Making_Fedora_Discs.types');">
@@ -838,7 +839,7 @@
<div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Fedora_Elections_Guide.types');">
<a class="type" href="../en-US/Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html'"><span class="book">Fedora Elections Guide</span></a>
<div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide.types' class="types hidden" onclick="work=0;">
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
@@ -859,7 +860,7 @@
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/pa-IN/Site_Statistics.html b/public_html/pa-IN/Site_Statistics.html
index e17799c..5501668 100644
--- a/public_html/pa-IN/Site_Statistics.html
+++ b/public_html/pa-IN/Site_Statistics.html
@@ -392,6 +392,15 @@
</tr>
<tr>
+ <td>Romanian</td>
+ <td>ro</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ </tr>
+
+ <tr>
<td>Tamil</td>
<td>ta-IN</td>
<td>1</td>
@@ -402,8 +411,8 @@
</table>
<div class="totals">
- <b>Total Languages: </b>42<br />
- <b>Total Packages: </b>673
+ <b>Total Languages: </b>43<br />
+ <b>Total Packages: </b>674
</div>
</body>
</html>
diff --git a/public_html/pa-IN/opds-Fedora.xml b/public_html/pa-IN/opds-Fedora.xml
index 9014db7..9c6c9f7 100644
--- a/public_html/pa-IN/opds-Fedora.xml
+++ b/public_html/pa-IN/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pa-IN/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2011-08-17T11:44:27</updated>
+ <updated>2011-08-22T23:04:50</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pa-IN/opds-Fedora_Contributor_Documentation.xml b/public_html/pa-IN/opds-Fedora_Contributor_Documentation.xml
index 3f8a0bd..95a3b02 100644
--- a/public_html/pa-IN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/pa-IN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pa-IN/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2011-08-17T11:44:27</updated>
+ <updated>2011-08-22T23:04:50</updated>
<!--author>
<name></name>
<uri></uri>
@@ -14,7 +14,7 @@
<entry>
<title>Fedora Elections Guide</title>
- <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub</id>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub</id>
<!--author>
<name></name>
<uri></uri>
@@ -26,7 +26,7 @@
<summary>Fedora Elections Guide
</summary>
<content type="text">This book covers procedural information for the use the Fedora Elections software</content>
- <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub">
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub">
<dc:format>application/epub+zip</dc:format>
</link>
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
diff --git a/public_html/pa-IN/opds-Fedora_Core.xml b/public_html/pa-IN/opds-Fedora_Core.xml
index fc2b4c6..d59509a 100644
--- a/public_html/pa-IN/opds-Fedora_Core.xml
+++ b/public_html/pa-IN/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pa-IN/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2011-08-17T11:44:27</updated>
+ <updated>2011-08-22T23:04:50</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pa-IN/opds-Fedora_Draft_Documentation.xml b/public_html/pa-IN/opds-Fedora_Draft_Documentation.xml
index 8df75d0..1397f7b 100644
--- a/public_html/pa-IN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/pa-IN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pa-IN/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2011-08-17T11:44:27</updated>
+ <updated>2011-08-22T23:04:50</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pa-IN/opds.xml b/public_html/pa-IN/opds.xml
index 4289adc..9b918d4 100644
--- a/public_html/pa-IN/opds.xml
+++ b/public_html/pa-IN/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/pa-IN/opds.xml</id>
<title>Product List</title>
- <updated>2011-08-17T11:44:27</updated>
+ <updated>2011-08-22T23:04:50</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/pa-IN/Fedora/opds-Fedora.xml</id>
- <updated>2011-08-17T11:44:27</updated>
+ <updated>2011-08-22T23:04:50</updated>
<dc:language>pa-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/pa-IN/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2011-08-17T11:44:27</updated>
+ <updated>2011-08-22T23:04:50</updated>
<dc:language>pa-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/pa-IN/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2011-08-17T11:44:27</updated>
+ <updated>2011-08-22T23:04:50</updated>
<dc:language>pa-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/pa-IN/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2011-08-17T11:44:27</updated>
+ <updated>2011-08-22T23:04:50</updated>
<dc:language>pa-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/pa-IN/toc.html b/public_html/pa-IN/toc.html
index dd0384b..f264d95 100644
--- a/public_html/pa-IN/toc.html
+++ b/public_html/pa-IN/toc.html
@@ -58,6 +58,7 @@
<option value="pl-PL">Polski</option>
<option value="pt-BR">Português Brasileiro</option>
<option value="pt-PT">Português</option>
+ <option value="ro">Romanian</option>
<option value="ru-RU">РуÑÑкий</option>
<option value="sk-SK">SlovenÅ¡Äina</option>
<option value="sr-Latn-RS">Srpski (latinica)</option>
@@ -292,7 +293,7 @@
<a class="type" href="../en-US/./Fedora/13/epub/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/13/html/Accessibility_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/13/html/Accessibility_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/13/html-single/Accessibility_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/13/html-single/Accessibility_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.13.Burning_ISO_images_to_disc' class="book collapsed" onclick="toggle(event, 'Fedora.13.Burning_ISO_images_to_disc.types');">
@@ -609,7 +610,7 @@
<a class="type" href="../en-US/./Fedora/11/epub/Security_Guide/Fedora-11-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/11/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/11/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.11.User_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.11.User_Guide.types');">
@@ -738,7 +739,7 @@
<a class="type" href="../en-US/./Fedora/8/epub/Installation_Guide/Fedora-8-Installation_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/8/html/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/8/html/Installation_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/8/html-single/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/8/html-single/Installation_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-9-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-9-Installation_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-8-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-8-Installation_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.8.Making_Fedora_Discs' class="book collapsed" onclick="toggle(event, 'Fedora.8.Making_Fedora_Discs.types');">
@@ -838,7 +839,7 @@
<div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Fedora_Elections_Guide.types');">
<a class="type" href="../en-US/Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html'"><span class="book">Fedora Elections Guide</span></a>
<div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide.types' class="types hidden" onclick="work=0;">
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
@@ -859,7 +860,7 @@
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/pl-PL/Site_Statistics.html b/public_html/pl-PL/Site_Statistics.html
index 66c67a2..fb822a6 100644
--- a/public_html/pl-PL/Site_Statistics.html
+++ b/public_html/pl-PL/Site_Statistics.html
@@ -392,6 +392,15 @@
</tr>
<tr>
+ <td>Romanian</td>
+ <td>ro</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ </tr>
+
+ <tr>
<td>Tamil</td>
<td>ta-IN</td>
<td>1</td>
@@ -402,8 +411,8 @@
</table>
<div class="totals">
- <b>Razem języków: </b>42<br />
- <b>Razem pakietów: </b>673
+ <b>Razem języków: </b>43<br />
+ <b>Razem pakietów: </b>674
</div>
</body>
</html>
diff --git a/public_html/pl-PL/opds-Fedora.xml b/public_html/pl-PL/opds-Fedora.xml
index 7ee25de..036a0ff 100644
--- a/public_html/pl-PL/opds-Fedora.xml
+++ b/public_html/pl-PL/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pl-PL/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2011-08-17T11:44:27</updated>
+ <updated>2011-08-22T23:04:51</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pl-PL/opds-Fedora_Contributor_Documentation.xml b/public_html/pl-PL/opds-Fedora_Contributor_Documentation.xml
index 02c7dd7..3eede59 100644
--- a/public_html/pl-PL/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/pl-PL/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pl-PL/opds-Fedora_Contributor_Documentation.xml</id>
<title>Dokumentacja dla współtwórców Fedory</title>
<subtitle>Dokumentacja dla współtwórców Fedory</subtitle>
- <updated>2011-08-17T11:44:27</updated>
+ <updated>2011-08-22T23:04:51</updated>
<!--author>
<name></name>
<uri></uri>
@@ -14,7 +14,7 @@
<entry>
<title>Fedora Elections Guide</title>
- <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub</id>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub</id>
<!--author>
<name></name>
<uri></uri>
@@ -26,7 +26,7 @@
<summary>Fedora Elections Guide
</summary>
<content type="text">This book covers procedural information for the use the Fedora Elections software</content>
- <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub">
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub">
<dc:format>application/epub+zip</dc:format>
</link>
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
diff --git a/public_html/pl-PL/opds-Fedora_Core.xml b/public_html/pl-PL/opds-Fedora_Core.xml
index 6d1e834..6838d40 100644
--- a/public_html/pl-PL/opds-Fedora_Core.xml
+++ b/public_html/pl-PL/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pl-PL/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2011-08-17T11:44:27</updated>
+ <updated>2011-08-22T23:04:51</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pl-PL/opds-Fedora_Draft_Documentation.xml b/public_html/pl-PL/opds-Fedora_Draft_Documentation.xml
index 491e259..c1f5744 100644
--- a/public_html/pl-PL/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/pl-PL/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pl-PL/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2011-08-17T11:44:27</updated>
+ <updated>2011-08-22T23:04:51</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pl-PL/opds.xml b/public_html/pl-PL/opds.xml
index f0093e5..84ab6b2 100644
--- a/public_html/pl-PL/opds.xml
+++ b/public_html/pl-PL/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/pl-PL/opds.xml</id>
<title>Product List</title>
- <updated>2011-08-17T11:44:27</updated>
+ <updated>2011-08-22T23:04:51</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/pl-PL/Fedora/opds-Fedora.xml</id>
- <updated>2011-08-17T11:44:27</updated>
+ <updated>2011-08-22T23:04:51</updated>
<dc:language>pl-PL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Dokumentacja dla współtwórców Fedory</title>
<id>http://docs.fedoraproject.org/pl-PL/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2011-08-17T11:44:27</updated>
+ <updated>2011-08-22T23:04:51</updated>
<dc:language>pl-PL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/pl-PL/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2011-08-17T11:44:27</updated>
+ <updated>2011-08-22T23:04:51</updated>
<dc:language>pl-PL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/pl-PL/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2011-08-17T11:44:27</updated>
+ <updated>2011-08-22T23:04:51</updated>
<dc:language>pl-PL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/pl-PL/toc.html b/public_html/pl-PL/toc.html
index 30a64e3..3bae479 100644
--- a/public_html/pl-PL/toc.html
+++ b/public_html/pl-PL/toc.html
@@ -58,6 +58,7 @@
<option selected="selected" value="pl-PL">Polski</option>
<option value="pt-BR">Português Brasileiro</option>
<option value="pt-PT">Português</option>
+ <option value="ro">Romanian</option>
<option value="ru-RU">РуÑÑкий</option>
<option value="sk-SK">SlovenÅ¡Äina</option>
<option value="sr-Latn-RS">Srpski (latinica)</option>
@@ -608,7 +609,7 @@
<a class="type" href="../en-US/./Fedora/11/epub/Security_Guide/Fedora-11-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/11/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/11/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.11.User_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.11.User_Guide.types');">
@@ -690,7 +691,7 @@
<a class="type" href="../en-US/./Fedora/10/epub/Security_Guide/Fedora-11-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/10/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/10/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/10/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/10/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/10/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/10/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/10/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/10/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.10.User_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.10.User_Guide.types');">
@@ -772,7 +773,7 @@
<a class="type" href="../en-US/./Fedora/9/epub/Security_Guide/Fedora-11-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/9/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/9/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/9/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/9/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/9/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/9/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/9/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/9/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.9.User_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.9.User_Guide.types');">
@@ -918,7 +919,7 @@
<div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Fedora_Elections_Guide.types');">
<a class="type" href="../en-US/Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html'"><span class="book">Fedora Elections Guide</span></a>
<div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide.types' class="types hidden" onclick="work=0;">
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
@@ -930,7 +931,7 @@
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/pt-BR/Site_Statistics.html b/public_html/pt-BR/Site_Statistics.html
index e17799c..5501668 100644
--- a/public_html/pt-BR/Site_Statistics.html
+++ b/public_html/pt-BR/Site_Statistics.html
@@ -392,6 +392,15 @@
</tr>
<tr>
+ <td>Romanian</td>
+ <td>ro</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ </tr>
+
+ <tr>
<td>Tamil</td>
<td>ta-IN</td>
<td>1</td>
@@ -402,8 +411,8 @@
</table>
<div class="totals">
- <b>Total Languages: </b>42<br />
- <b>Total Packages: </b>673
+ <b>Total Languages: </b>43<br />
+ <b>Total Packages: </b>674
</div>
</body>
</html>
diff --git a/public_html/pt-BR/opds-Fedora.xml b/public_html/pt-BR/opds-Fedora.xml
index 3d22bfd..64a640b 100644
--- a/public_html/pt-BR/opds-Fedora.xml
+++ b/public_html/pt-BR/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pt-BR/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2011-08-17T11:44:28</updated>
+ <updated>2011-08-22T23:04:51</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pt-BR/opds-Fedora_Contributor_Documentation.xml b/public_html/pt-BR/opds-Fedora_Contributor_Documentation.xml
index f4aa51d..73e4e35 100644
--- a/public_html/pt-BR/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/pt-BR/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pt-BR/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2011-08-17T11:44:28</updated>
+ <updated>2011-08-22T23:04:51</updated>
<!--author>
<name></name>
<uri></uri>
@@ -14,7 +14,7 @@
<entry>
<title>Fedora Elections Guide</title>
- <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub</id>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub</id>
<!--author>
<name></name>
<uri></uri>
@@ -26,7 +26,7 @@
<summary>Fedora Elections Guide
</summary>
<content type="text">This book covers procedural information for the use the Fedora Elections software</content>
- <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub">
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub">
<dc:format>application/epub+zip</dc:format>
</link>
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
diff --git a/public_html/pt-BR/opds-Fedora_Core.xml b/public_html/pt-BR/opds-Fedora_Core.xml
index 91c6782..4b0b9a6 100644
--- a/public_html/pt-BR/opds-Fedora_Core.xml
+++ b/public_html/pt-BR/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pt-BR/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2011-08-17T11:44:28</updated>
+ <updated>2011-08-22T23:04:51</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pt-BR/opds-Fedora_Draft_Documentation.xml b/public_html/pt-BR/opds-Fedora_Draft_Documentation.xml
index b97b7de..9e67613 100644
--- a/public_html/pt-BR/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/pt-BR/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pt-BR/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2011-08-17T11:44:28</updated>
+ <updated>2011-08-22T23:04:51</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pt-BR/opds.xml b/public_html/pt-BR/opds.xml
index 104f464..c1e0e96 100644
--- a/public_html/pt-BR/opds.xml
+++ b/public_html/pt-BR/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/pt-BR/opds.xml</id>
<title>Product List</title>
- <updated>2011-08-17T11:44:28</updated>
+ <updated>2011-08-22T23:04:51</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/pt-BR/Fedora/opds-Fedora.xml</id>
- <updated>2011-08-17T11:44:28</updated>
+ <updated>2011-08-22T23:04:51</updated>
<dc:language>pt-BR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/pt-BR/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2011-08-17T11:44:28</updated>
+ <updated>2011-08-22T23:04:51</updated>
<dc:language>pt-BR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/pt-BR/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2011-08-17T11:44:28</updated>
+ <updated>2011-08-22T23:04:51</updated>
<dc:language>pt-BR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/pt-BR/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2011-08-17T11:44:28</updated>
+ <updated>2011-08-22T23:04:51</updated>
<dc:language>pt-BR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/pt-BR/toc.html b/public_html/pt-BR/toc.html
index 8ed75e7..d91db0e 100644
--- a/public_html/pt-BR/toc.html
+++ b/public_html/pt-BR/toc.html
@@ -58,6 +58,7 @@
<option value="pl-PL">Polski</option>
<option selected="selected" value="pt-BR">Português Brasileiro</option>
<option value="pt-PT">Português</option>
+ <option value="ro">Romanian</option>
<option value="ru-RU">РуÑÑкий</option>
<option value="sk-SK">SlovenÅ¡Äina</option>
<option value="sr-Latn-RS">Srpski (latinica)</option>
@@ -292,7 +293,7 @@
<a class="type" href="../en-US/./Fedora/13/epub/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/13/html/Accessibility_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/13/html/Accessibility_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/13/html-single/Accessibility_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/13/html-single/Accessibility_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.13.Burning_ISO_images_to_disc' class="book collapsed" onclick="toggle(event, 'Fedora.13.Burning_ISO_images_to_disc.types');">
@@ -609,7 +610,7 @@
<a class="type" href="../en-US/./Fedora/11/epub/Security_Guide/Fedora-11-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/11/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/11/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.11.User_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.11.User_Guide.types');">
@@ -847,7 +848,7 @@
<div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Fedora_Elections_Guide.types');">
<a class="type" href="../en-US/Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html'"><span class="book">Fedora Elections Guide</span></a>
<div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide.types' class="types hidden" onclick="work=0;">
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
@@ -868,7 +869,7 @@
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/pt-PT/Site_Statistics.html b/public_html/pt-PT/Site_Statistics.html
index e17799c..5501668 100644
--- a/public_html/pt-PT/Site_Statistics.html
+++ b/public_html/pt-PT/Site_Statistics.html
@@ -392,6 +392,15 @@
</tr>
<tr>
+ <td>Romanian</td>
+ <td>ro</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ </tr>
+
+ <tr>
<td>Tamil</td>
<td>ta-IN</td>
<td>1</td>
@@ -402,8 +411,8 @@
</table>
<div class="totals">
- <b>Total Languages: </b>42<br />
- <b>Total Packages: </b>673
+ <b>Total Languages: </b>43<br />
+ <b>Total Packages: </b>674
</div>
</body>
</html>
diff --git a/public_html/pt-PT/opds-Fedora.xml b/public_html/pt-PT/opds-Fedora.xml
index 64add4e..ec69b77 100644
--- a/public_html/pt-PT/opds-Fedora.xml
+++ b/public_html/pt-PT/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pt-PT/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2011-08-17T11:44:28</updated>
+ <updated>2011-08-22T23:04:51</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pt-PT/opds-Fedora_Contributor_Documentation.xml b/public_html/pt-PT/opds-Fedora_Contributor_Documentation.xml
index 12f3490..f18dde0 100644
--- a/public_html/pt-PT/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/pt-PT/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pt-PT/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2011-08-17T11:44:28</updated>
+ <updated>2011-08-22T23:04:51</updated>
<!--author>
<name></name>
<uri></uri>
@@ -14,7 +14,7 @@
<entry>
<title>Fedora Elections Guide</title>
- <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub</id>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub</id>
<!--author>
<name></name>
<uri></uri>
@@ -26,7 +26,7 @@
<summary>Fedora Elections Guide
</summary>
<content type="text">This book covers procedural information for the use the Fedora Elections software</content>
- <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub">
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub">
<dc:format>application/epub+zip</dc:format>
</link>
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
diff --git a/public_html/pt-PT/opds-Fedora_Core.xml b/public_html/pt-PT/opds-Fedora_Core.xml
index 80300f3..c672fa5 100644
--- a/public_html/pt-PT/opds-Fedora_Core.xml
+++ b/public_html/pt-PT/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pt-PT/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2011-08-17T11:44:28</updated>
+ <updated>2011-08-22T23:04:52</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pt-PT/opds-Fedora_Draft_Documentation.xml b/public_html/pt-PT/opds-Fedora_Draft_Documentation.xml
index 58b2465..94a1f04 100644
--- a/public_html/pt-PT/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/pt-PT/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pt-PT/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2011-08-17T11:44:28</updated>
+ <updated>2011-08-22T23:04:52</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pt-PT/opds.xml b/public_html/pt-PT/opds.xml
index d792e3d..3d0b67f 100644
--- a/public_html/pt-PT/opds.xml
+++ b/public_html/pt-PT/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/pt-PT/opds.xml</id>
<title>Product List</title>
- <updated>2011-08-17T11:44:28</updated>
+ <updated>2011-08-22T23:04:52</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/pt-PT/Fedora/opds-Fedora.xml</id>
- <updated>2011-08-17T11:44:28</updated>
+ <updated>2011-08-22T23:04:51</updated>
<dc:language>pt-PT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/pt-PT/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2011-08-17T11:44:28</updated>
+ <updated>2011-08-22T23:04:51</updated>
<dc:language>pt-PT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/pt-PT/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2011-08-17T11:44:28</updated>
+ <updated>2011-08-22T23:04:52</updated>
<dc:language>pt-PT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/pt-PT/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2011-08-17T11:44:28</updated>
+ <updated>2011-08-22T23:04:52</updated>
<dc:language>pt-PT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/pt-PT/toc.html b/public_html/pt-PT/toc.html
index c57b96f..a930865 100644
--- a/public_html/pt-PT/toc.html
+++ b/public_html/pt-PT/toc.html
@@ -58,6 +58,7 @@
<option value="pl-PL">Polski</option>
<option value="pt-BR">Português Brasileiro</option>
<option selected="selected" value="pt-PT">Português</option>
+ <option value="ro">Romanian</option>
<option value="ru-RU">РуÑÑкий</option>
<option value="sk-SK">SlovenÅ¡Äina</option>
<option value="sr-Latn-RS">Srpski (latinica)</option>
@@ -608,7 +609,7 @@
<a class="type" href="../en-US/./Fedora/11/epub/Security_Guide/Fedora-11-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/11/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/11/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.11.User_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.11.User_Guide.types');">
@@ -846,7 +847,7 @@
<div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Fedora_Elections_Guide.types');">
<a class="type" href="../en-US/Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html'"><span class="book">Fedora Elections Guide</span></a>
<div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide.types' class="types hidden" onclick="work=0;">
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
@@ -867,7 +868,7 @@
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/epub/RPM_Guide/Fedora_Draft_Documentation-0.1-RPM_Guide-ro.epub b/public_html/ro/Fedora_Draft_Documentation/0.1/epub/RPM_Guide/Fedora_Draft_Documentation-0.1-RPM_Guide-ro.epub
new file mode 100644
index 0000000..54f27dc
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/epub/RPM_Guide/Fedora_Draft_Documentation-0.1-RPM_Guide-ro.epub differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/css/common.css b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/css/common.css
new file mode 100644
index 0000000..f9603b7
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/css/common.css
@@ -0,0 +1,1495 @@
+body, h1, h2, h3, h4, h5, h6, pre, li, div {
+ line-height: 1.29em;
+}
+
+body {
+ background-color: white;
+ margin:0 auto;
+ font-family: "liberation sans", "Myriad ", "Bitstream Vera Sans", "Lucida Grande", "Luxi Sans", "Trebuchet MS", helvetica, verdana, arial, sans-serif;
+ font-size:12px;
+ max-width:55em;
+ color:black;
+}
+
+body.toc_embeded {
+ /*for web hosting system only*/
+ margin-left: 300px;
+}
+
+object.toc, iframe.toc {
+ /*for web hosting system only*/
+ border-style:none;
+ position:fixed;
+ width:290px;
+ height:99.99%;
+ top:0;
+ left:0;
+ z-index: 100;
+ border-style:none;
+ border-right:1px solid #999;
+}
+
+/* Hide web menu */
+
+body.notoc {
+ margin-left: 3em;
+}
+
+iframe.notoc {
+ border-style:none;
+ border: none;
+ padding: 0em;
+ position:fixed;
+ width: 21px;
+ height: 29px;
+ top: 0px;
+ left:0;
+ overflow: hidden;
+ margin: 0em;
+ margin-left: -3px;
+}
+/* End hide web menu */
+
+/* desktop styles */
+body.desktop {
+ margin-left: 26em;
+}
+
+body.desktop .book > .toc {
+ display:block;
+ width:24em;
+ height:99%;
+ position:fixed;
+ overflow:auto;
+ top:0px;
+ left:0px;
+ padding-left:1em;
+ background-color:#EEEEEE;
+}
+
+.toc {
+ line-height:1.35em;
+}
+
+.toc .glossary,
+.toc .chapter, .toc .appendix {
+ margin-top:1em;
+}
+
+.toc .part {
+ margin-top:1em;
+ display:block;
+}
+
+span.glossary,
+span.appendix {
+ display:block;
+ margin-top:0.5em;
+}
+
+div {
+ padding-top:0px;
+}
+
+div.section {
+ padding-top:1em;
+}
+
+p, div.para, div.formalpara {
+ padding-top:0px;
+ margin-top:0.3em;
+ padding-bottom:0px;
+ margin-bottom:1em;
+}
+
+/*Links*/
+a {
+ outline: none;
+}
+
+a:link {
+ text-decoration:none;
+ border-bottom: 1px dotted ;
+ color:#3366cc;
+}
+
+a:visited {
+ text-decoration:none;
+ border-bottom: 1px dotted ;
+ color:#003366;
+}
+
+div.longdesc-link {
+ float:right;
+ color:#999;
+}
+
+.toc a, .qandaset a {
+ font-weight:normal;
+}
+
+/*headings*/
+h1, h2, h3, h4, h5, h6 {
+ color: #336699;
+ margin-top: 0em;
+ margin-bottom: 0em;
+ background-color: transparent;
+}
+
+h1 {
+ font-size:2.0em;
+}
+
+.titlepage h1.title {
+ font-size: 3.0em;
+ padding-top: 1em;
+ text-align:left;
+}
+
+.book > .titlepage h1.title {
+ text-align:center;
+}
+
+.article > .titlepage h1.title {
+ text-align:center;
+}
+
+.set .titlepage > div > div > h1.title {
+ text-align:center;
+}
+
+.producttitle {
+ margin-top: 0em;
+ margin-bottom: 0em;
+ font-size: 3.0em;
+ font-weight: bold;
+ background: #003d6e url(../images/h1-bg.png) top left repeat-x;
+ color: white;
+ text-align: center;
+ padding: 0.7em;
+}
+
+.titlepage .corpauthor {
+ margin-top: 1em;
+ text-align: center;
+}
+
+.section h1.title {
+ font-size: 1.6em;
+ padding: 0em;
+ color: #336699;
+ text-align: left;
+ background: white;
+}
+
+h2 {
+ font-size:1.6em;
+}
+
+
+h2.subtitle, h3.subtitle {
+ margin-top: 1em;
+ margin-bottom: 1em;
+ font-size: 1.4em;
+ text-align: center;
+}
+
+.preface > div > div > div > h2.title {
+ margin-top: 1em;
+ font-size: 2.0em;
+}
+
+.appendix h2 {
+ margin-top: 1em;
+ font-size: 2.0em;
+}
+
+
+
+h3 {
+ font-size:1.3em;
+ padding-top:0em;
+ padding-bottom:0em;
+}
+h4 {
+ font-size:1.1em;
+ padding-top:0em;
+ padding-bottom:0em;
+}
+
+h5 {
+ font-size:1em;
+}
+
+h6 {
+ font-size:1em;
+}
+
+h5.formalpara {
+ font-size:1em;
+ margin-top:2em;
+ margin-bottom:.8em;
+}
+
+.abstract h6 {
+ margin-top:1em;
+ margin-bottom:.5em;
+ font-size:2em;
+}
+
+/*element rules*/
+hr {
+ border-collapse: collapse;
+ border-style:none;
+ border-top: 1px dotted #ccc;
+ width:100%;
+ margin-top: 3em;
+}
+
+/* web site rules */
+ul.languages, .languages li {
+ display:inline;
+ padding:0em;
+}
+
+.languages li a {
+ padding:0em .5em;
+ text-decoration: none;
+}
+
+.languages li p, .languages li div.para {
+ display:inline;
+}
+
+.languages li a:link, .languages li a:visited {
+ color:#444;
+}
+
+.languages li a:hover, .languages li a:focus, .languages li a:active {
+ color:black;
+}
+
+ul.languages {
+ display:block;
+ background-color:#eee;
+ padding:.5em;
+}
+
+/*supporting stylesheets*/
+
+/*unique to the webpage only*/
+.books {
+ position:relative;
+}
+
+.versions li {
+ width:100%;
+ clear:both;
+ display:block;
+}
+
+a.version {
+ font-size:2em;
+ text-decoration:none;
+ width:100%;
+ display:block;
+ padding:1em 0em .2em 0em;
+ clear:both;
+}
+
+a.version:before {
+ content:"Version";
+ font-size:smaller;
+}
+
+a.version:visited, a.version:link {
+ color:#666;
+}
+
+a.version:focus, a.version:hover {
+ color:black;
+}
+
+.books {
+ display:block;
+ position:relative;
+ clear:both;
+ width:100%;
+}
+
+.books li {
+ display:block;
+ width:200px;
+ float:left;
+ position:relative;
+ clear: none ;
+}
+
+.books .html {
+ width:170px;
+ display:block;
+}
+
+.books .pdf {
+ position:absolute;
+ left:170px;
+ top:0px;
+ font-size:smaller;
+}
+
+.books .pdf:link, .books .pdf:visited {
+ color:#555;
+}
+
+.books .pdf:hover, .books .pdf:focus {
+ color:#000;
+}
+
+.books li a {
+ text-decoration:none;
+}
+
+.books li a:hover {
+ color:black;
+}
+
+/*products*/
+.products li {
+ display: block;
+ width:300px;
+ float:left;
+}
+
+.products li a {
+ width:300px;
+ padding:.5em 0em;
+}
+
+.products ul {
+ clear:both;
+}
+
+/*revision history*/
+.revhistory {
+ display:block;
+}
+
+.revhistory table {
+ background-color:transparent;
+ border-color:#fff;
+ padding:0em;
+ margin: 0;
+ border-collapse:collapse;
+ border-style:none;
+}
+
+.revhistory td {
+ text-align :left;
+ padding:0em;
+ border: none;
+ border-top: 1px solid #fff;
+ font-weight: bold;
+}
+
+.revhistory .simplelist td {
+ font-weight: normal;
+}
+
+.revhistory .simplelist {
+ margin-bottom: 1.5em;
+ margin-left: 1em;
+}
+
+.revhistory table th {
+ display: none;
+}
+
+
+/*credits*/
+.authorgroup div {
+ clear:both;
+ text-align: center;
+}
+
+h3.author {
+ margin: 0em;
+ padding: 0em;
+ padding-top: 1em;
+}
+
+.authorgroup h4 {
+ padding: 0em;
+ margin: 0em;
+ padding-top: 1em;
+ margin-top: 1em;
+}
+
+.author,
+.editor,
+.translator,
+.othercredit,
+.contrib {
+ display: block;
+}
+
+.revhistory .author {
+ display: inline;
+}
+
+.othercredit h3 {
+ padding-top: 1em;
+}
+
+
+.othercredit {
+ margin:0em;
+ padding:0em;
+}
+
+.releaseinfo {
+ clear: both;
+}
+
+.copyright {
+ margin-top: 1em;
+}
+
+/* qanda sets */
+.answer {
+ margin-bottom:1em;
+ border-bottom:1px dotted #ccc;
+}
+
+.qandaset .toc {
+ border-bottom:1px dotted #ccc;
+}
+
+.question {
+ font-weight:bold;
+}
+
+.answer .data, .question .data {
+ padding-left: 2.6em;
+}
+
+.answer label, .question label {
+ float:left;
+ font-weight:bold;
+}
+
+/* inline syntax highlighting */
+.perl_Alert {
+ color: #0000ff;
+}
+
+.perl_BaseN {
+ color: #007f00;
+}
+
+.perl_BString {
+ color: #5C3566;
+}
+
+.perl_Char {
+ color: #ff00ff;
+}
+
+.perl_Comment {
+ color: #FF00FF;
+}
+
+
+.perl_DataType {
+ color: #0000ff;
+}
+
+
+.perl_DecVal {
+ color: #00007f;
+}
+
+
+.perl_Error {
+ color: #ff0000;
+}
+
+
+.perl_Float {
+ color: #00007f;
+}
+
+
+.perl_Function {
+ color: #007f00;
+}
+
+
+.perl_IString {
+ color: #5C3566;
+}
+
+
+.perl_Keyword {
+ color: #002F5D;
+}
+
+
+.perl_Operator {
+ color: #ffa500;
+}
+
+
+.perl_Others {
+ color: #b03060;
+}
+
+
+.perl_RegionMarker {
+ color: #96b9ff;
+}
+
+
+.perl_Reserved {
+ color: #9b30ff;
+}
+
+
+.perl_String {
+ color: #5C3566;
+}
+
+
+.perl_Variable {
+ color: #0000ff;
+}
+
+
+.perl_Warning {
+ color: #0000ff;
+}
+
+/*Lists*/
+ul {
+ padding-left:1.6em;
+ list-style-image:url(../images/dot.png);
+ list-style-type: circle;
+}
+
+ul ul {
+ list-style-image:url(../images/dot2.png);
+ list-style-type: circle;
+}
+
+ol {
+ list-style-image:none;
+ list-style-type: decimal;
+}
+
+ol ol {
+ list-style-type: lower-alpha;
+}
+
+ol.arabic {
+ list-style-type: decimal;
+}
+
+ol.loweralpha {
+ list-style-type: lower-alpha;
+}
+
+ol.lowerroman {
+ list-style-type: lower-roman;
+}
+
+ol.upperalpha {
+ list-style-type: upper-alpha;
+}
+
+ol.upperroman {
+ list-style-type: upper-roman;
+}
+
+dt {
+ font-weight:bold;
+ margin-bottom:0em;
+ padding-bottom:0em;
+}
+
+dd {
+ margin:0em;
+ margin-left:2em;
+ padding-top:0em;
+ padding-bottom: 1em;
+}
+
+li {
+ padding-top:0px;
+ margin-top:0em;
+ padding-bottom:0px;
+ margin-bottom:0.4em;
+}
+
+li p, li div.para {
+ padding-top:0px;
+ margin-top:0em;
+ padding-bottom:0px;
+ margin-bottom:0.3em;
+}
+
+/*images*/
+img {
+ display:block;
+ margin: 2em 0;
+}
+
+.inlinemediaobject, .inlinemediaobject img {
+ display:inline;
+ margin:0em;
+}
+
+.figure img {
+ display:block;
+ margin:0;
+}
+
+.figure .title {
+ margin:0em;
+ margin-bottom:2em;
+ padding:0px;
+}
+
+/*document modes*/
+.confidential {
+ background-color:#900;
+ color:White;
+ padding:.5em .5em;
+ text-transform:uppercase;
+ text-align:center;
+}
+
+.longdesc-link {
+ display:none;
+}
+
+.longdesc {
+ display:none;
+}
+
+.prompt {
+ padding:0em .3em;
+}
+
+/*user interface styles*/
+.screen .replaceable {
+}
+
+.guibutton, .guilabel {
+ font-family: "liberation mono", "bitstream vera mono", "dejavu mono", monospace;
+ font-weight: bold;
+ white-space: nowrap;
+}
+
+.example {
+ background-color: #ffffff;
+ border-left: 3px solid #aaaaaa;
+ padding-top: 1em;
+ padding-bottom: 0.1em;
+}
+
+.example h6 {
+ padding-left: 10px;
+}
+
+.example-contents {
+ padding-left: 10px;
+ background-color: #ffffff;
+}
+
+.example-contents .para {
+/* padding: 10px;*/
+}
+
+/*terminal/console text*/
+.computeroutput,
+.option {
+ font-family:"liberation mono", "bitstream vera mono", "dejavu mono", monospace;
+ font-weight:bold;
+}
+
+.replaceable {
+ font-family:"liberation mono", "bitstream vera mono", "dejavu mono", monospace;
+ font-style: italic;
+}
+
+.command, .filename, .keycap, .classname, .literal {
+ font-family:"liberation mono", "bitstream vera mono", "dejavu mono", monospace;
+ font-weight:bold;
+}
+
+/* no bold in toc */
+.toc * {
+ font-weight: inherit;
+}
+
+pre {
+ font-family:"liberation mono", "bitstream vera mono", "dejavu mono", monospace;
+ display:block;
+ background-color: #f5f5f5;
+ color: #000000;
+ border: 1px solid #aaaaaa;
+ margin-bottom: 0.3em;
+ padding:.5em 1em;
+ white-space: pre-wrap; /* css-3 */
+ white-space: -moz-pre-wrap !important; /* Mozilla, since 1999 */
+ white-space: -pre-wrap; /* Opera 4-6 */
+ white-space: -o-pre-wrap; /* Opera 7 */
+ word-wrap: break-word; /* Internet Explorer 5.5+ */
+ font-size: 0.9em;
+}
+
+pre .replaceable,
+pre .keycap {
+}
+
+code {
+ font-family:"liberation mono", "bitstream vera mono", "dejavu mono", monospace;
+ white-space: nowrap;
+ font-weight:bold;
+}
+
+.parameter code {
+ display: inline;
+ white-space: pre-wrap; /* css-3 */
+ white-space: -moz-pre-wrap !important; /* Mozilla, since 1999 */
+ white-space: -pre-wrap; /* Opera 4-6 */
+ white-space: -o-pre-wrap; /* Opera 7 */
+ word-wrap: break-word; /* Internet Explorer 5.5+ */
+}
+
+/*Notifications*/
+div.warning:before {
+ content:url(../images/warning.png);
+ padding-left: 5px;
+}
+
+div.note:before {
+ content:url(../images/note.png);
+ padding-left: 5px;
+}
+
+div.important:before {
+ content:url(../images/important.png);
+ padding-left: 5px;
+}
+
+div.warning, div.note, div.important {
+ color: black;
+ margin: 0em;
+ padding: 0em;
+ background: none;
+ background-color: white;
+ margin-bottom: 1em;
+ border-bottom: 1px solid #aaaaaa;
+}
+
+div.warning h2, div.note h2,div.important h2 {
+ margin: 0em;
+ padding: 0em;
+ color: #eeeeec;
+ padding-top: 0px;
+ padding-bottom: 0px;
+ height: 1.4em;
+ line-height: 1.4em;
+ font-size: 1.4em;
+ display:inline;
+}
+
+div.admonition_header {
+ clear: both;
+ margin: 0em;
+ padding: 0em;
+ margin-top: -3.3em;
+ padding-left: 58px;
+ line-height: 1.0em;
+ font-size: 1.0em;
+}
+
+div.warning div.admonition_header {
+ background: url(../images/red.png) top left repeat-x;
+ background-color: #590000;
+}
+
+div.note div.admonition_header {
+ background: url(../images/green.png) top right repeat-x;
+ background-color: #597800;
+}
+
+div.important div.admonition_header {
+ background: url(../images/yellow.png) top right repeat-x;
+ background-color: #a6710f;
+}
+
+div.warning p, div.warning div.para,
+div.note p, div.note div.para,
+div.important p, div.important div.para {
+ padding: 0em;
+ margin: 0em;
+}
+
+div.admonition {
+ border: none;
+ border-left: 1px solid #aaaaaa;
+ border-right: 1px solid #aaaaaa;
+ padding:0em;
+ margin:0em;
+ padding-top: 1.5em;
+ padding-bottom: 1em;
+ padding-left: 2em;
+ padding-right: 1em;
+ background-color: #eeeeec;
+ -moz-border-radius: 0px;
+ -webkit-border-radius: 0px;
+ border-radius: 0px;
+}
+
+/*Page Title*/
+#title {
+ display:block;
+ height:45px;
+ padding-bottom:1em;
+ margin:0em;
+}
+
+#title a.left{
+ display:inline;
+ border:none;
+}
+
+#title a.left img{
+ border:none;
+ float:left;
+ margin:0em;
+ margin-top:.7em;
+}
+
+#title a.right {
+ padding-bottom:1em;
+}
+
+#title a.right img {
+ border:none;
+ float:right;
+ margin:0em;
+ margin-top:.7em;
+}
+
+/*Table*/
+table {
+ border:1px solid #6c614b;
+ width:100%;
+ border-collapse:collapse;
+}
+
+table.simplelist, .calloutlist table {
+ border-style: none;
+}
+
+table th {
+ text-align:left;
+ background-color:#6699cc;
+ padding:.3em .5em;
+ color:white;
+}
+
+table td {
+ padding:.15em .5em;
+}
+
+table tr.even td {
+ background-color:#f5f5f5;
+}
+
+table th p:first-child, table td p:first-child, table li p:first-child,
+table th div.para:first-child, table td div.para:first-child, table li div.para:first-child {
+ margin-top:0em;
+ padding-top:0em;
+ display:inline;
+}
+
+th, td {
+ border-style:none;
+ vertical-align: top;
+ border: 1px solid #000;
+}
+
+.simplelist th, .simplelist td {
+ border: none;
+}
+
+table table td {
+ border-bottom:1px dotted #aaa;
+ background-color:white;
+ padding:.6em 0em;
+}
+
+table table {
+ border:1px solid white;
+}
+
+td.remarkval {
+ color:#444;
+}
+
+td.fieldval {
+ font-weight:bold;
+}
+
+.lbname, .lbtype, .lbdescr, .lbdriver, .lbhost {
+ color:white;
+ font-weight:bold;
+ background-color:#999;
+ width:120px;
+}
+
+td.remarkval {
+ width:230px;
+}
+
+td.tname {
+ font-weight:bold;
+}
+
+th.dbfield {
+ width:120px;
+}
+
+th.dbtype {
+ width:70px;
+}
+
+th.dbdefault {
+ width:70px;
+}
+
+th.dbnul {
+ width:70px;
+}
+
+th.dbkey {
+ width:70px;
+}
+
+span.book {
+ margin-top:4em;
+ display:block;
+}
+
+span.chapter {
+ display:block;
+ margin-top:0.5em;
+}
+
+table.simplelist td, .calloutlist table td {
+ border-style: none;
+}
+
+/*Breadcrumbs*/
+#breadcrumbs ul li.first:before {
+ content:" ";
+}
+
+#breadcrumbs {
+ color:#900;
+ padding:3px;
+ margin-bottom:25px;
+}
+
+#breadcrumbs ul {
+ margin-left:0;
+ padding-left:0;
+ display:inline;
+ border:none;
+}
+
+#breadcrumbs ul li {
+ margin-left:0;
+ padding-left:2px;
+ border:none;
+ list-style:none;
+ display:inline;
+}
+
+#breadcrumbs ul li:before {
+ content:"\0020 \0020 \0020 \00BB \0020";
+ color:#333;
+}
+
+/*index*/
+.glossary h3,
+.index h3 {
+ font-size: 2em;
+ color:#aaa;
+ margin:0em;
+}
+
+.indexdiv {
+ margin-bottom:1em;
+}
+
+.glossary dt,
+.index dt {
+ color:#444;
+ padding-top:.5em;
+}
+
+.glossary dl dl dt,
+.index dl dl dt {
+ color:#777;
+ font-weight:normal;
+ padding-top:0em;
+}
+
+.index dl dl dt:before {
+ content:"- ";
+ color:#ccc;
+}
+
+/*changes*/
+.footnote {
+ font-size: .7em;
+ margin:0em;
+ color:#222;
+}
+
+table .footnote {
+}
+
+sup {
+ color:#999;
+ margin:0em;
+ padding:0em;
+ line-height: .4em;
+ font-size: 1em;
+ padding-left:0em;
+}
+
+.footnote {
+ position:relative;
+}
+
+.footnote sup {
+ color:#e3dcc0;
+ position:absolute;
+ left: .4em;
+}
+
+.footnote sup a:link,
+.footnote sup a:visited {
+ color:#92917d;
+ text-decoration:none;
+}
+
+.footnote:hover sup a {
+ text-decoration:none;
+}
+
+.footnote p,.footnote div.para {
+ padding-left:2em;
+}
+
+.footnote a:link,
+.footnote a:visited {
+ color:#00537c;
+}
+
+.footnote a:hover {
+}
+
+/**/
+div.chapter {
+ margin-top:3em;
+}
+
+div.section {
+ margin-top:1em;
+}
+
+div.note .replaceable,
+div.important .replaceable,
+div.warning .replaceable,
+div.note .keycap,
+div.important .keycap,
+div.warning .keycap
+{
+}
+
+ul li p:last-child, ul li div.para:last-child {
+ margin-bottom:0em;
+ padding-bottom:0em;
+}
+
+/*document navigation*/
+.docnav a, .docnav strong {
+ border:none;
+ text-decoration:none;
+ font-weight:normal;
+}
+
+.docnav {
+ list-style:none;
+ margin:0em;
+ padding:0em;
+ position:relative;
+ width:100%;
+ padding-bottom:2em;
+ padding-top:1em;
+ border-top:1px dotted #ccc;
+}
+
+.docnav li {
+ list-style:none;
+ margin:0em;
+ padding:0em;
+ display:inline;
+ font-size:.8em;
+}
+
+.docnav li:before {
+ content:" ";
+}
+
+.docnav li.previous, .docnav li.next {
+ position:absolute;
+ top:1em;
+}
+
+.docnav li.up, .docnav li.home {
+ margin:0em 1.5em;
+}
+
+.docnav li.previous {
+ left:0px;
+ text-align:left;
+}
+
+.docnav li.next {
+ right:0px;
+ text-align:right;
+}
+
+.docnav li.previous strong, .docnav li.next strong {
+ height:22px;
+ display:block;
+}
+
+.docnav {
+ margin:0 auto;
+ text-align:center;
+}
+
+.docnav li.next a strong {
+ background: url(../images/stock-go-forward.png) top right no-repeat;
+ padding-top:3px;
+ padding-bottom:4px;
+ padding-right:28px;
+ font-size:1.2em;
+}
+
+.docnav li.previous a strong {
+ background: url(../images/stock-go-back.png) top left no-repeat;
+ padding-top:3px;
+ padding-bottom:4px;
+ padding-left:28px;
+ padding-right:0.5em;
+ font-size:1.2em;
+}
+
+.docnav li.home a strong {
+ background: url(../images/stock-home.png) top left no-repeat;
+ padding:5px;
+ padding-left:28px;
+ font-size:1.2em;
+}
+
+.docnav li.up a strong {
+ background: url(../images/stock-go-up.png) top left no-repeat;
+ padding:5px;
+ padding-left:28px;
+ font-size:1.2em;
+}
+
+.docnav a:link, .docnav a:visited {
+ color:#666;
+}
+
+.docnav a:hover, .docnav a:focus, .docnav a:active {
+ color:black;
+}
+
+.docnav a {
+ max-width: 10em;
+ overflow:hidden;
+}
+
+.docnav a:link strong {
+ text-decoration:none;
+}
+
+.docnav {
+ margin:0 auto;
+ text-align:center;
+}
+
+ul.docnav {
+ margin-bottom: 1em;
+}
+/* Reports */
+.reports ul {
+ list-style:none;
+ margin:0em;
+ padding:0em;
+}
+
+.reports li{
+ margin:0em;
+ padding:0em;
+}
+
+.reports li.odd {
+ background-color: #eeeeee;
+ margin:0em;
+ padding:0em;
+}
+
+.reports dl {
+ display:inline;
+ margin:0em;
+ padding:0em;
+ float:right;
+ margin-right: 17em;
+ margin-top:-1.3em;
+}
+
+.reports dt {
+ display:inline;
+ margin:0em;
+ padding:0em;
+}
+
+.reports dd {
+ display:inline;
+ margin:0em;
+ padding:0em;
+ padding-right:.5em;
+}
+
+.reports h2, .reports h3{
+ display:inline;
+ padding-right:.5em;
+ font-size:10pt;
+ font-weight:normal;
+}
+
+.reports div.progress {
+ display:inline;
+ float:right;
+ width:16em;
+ background:#c00 url(../images/shine.png) top left repeat-x;
+ margin:0em;
+ margin-top:-1.3em;
+ padding:0em;
+ border:none;
+}
+
+/*uniform*/
+body.results, body.reports {
+ max-width:57em ;
+ padding:0em;
+}
+
+/*Progress Bar*/
+div.progress {
+ display:block;
+ float:left;
+ width:16em;
+ background:#c00 url(../images/shine.png) top left repeat-x;
+ height:1em;
+}
+
+div.progress span {
+ height:1em;
+ float:left;
+}
+
+div.progress span.translated {
+ background:#6c3 url(../images/shine.png) top left repeat-x;
+}
+
+div.progress span.fuzzy {
+ background:#ff9f00 url(../images/shine.png) top left repeat-x;
+}
+
+
+/*Results*/
+
+.results ul {
+ list-style:none;
+ margin:0em;
+ padding:0em;
+}
+
+.results li{
+ margin:0em;
+ padding:0em;
+}
+
+.results li.odd {
+ background-color: #eeeeee;
+ margin:0em;
+ padding:0em;
+}
+
+.results dl {
+ display:inline;
+ margin:0em;
+ padding:0em;
+ float:right;
+ margin-right: 17em;
+ margin-top:-1.3em;
+}
+
+.results dt {
+ display:inline;
+ margin:0em;
+ padding:0em;
+}
+
+.results dd {
+ display:inline;
+ margin:0em;
+ padding:0em;
+ padding-right:.5em;
+}
+
+.results h2, .results h3 {
+ display:inline;
+ padding-right:.5em;
+ font-size:10pt;
+ font-weight:normal;
+}
+
+.results div.progress {
+ display:inline;
+ float:right;
+ width:16em;
+ background:#c00 url(../images/shine.png) top left repeat-x;
+ margin:0em;
+ margin-top:-1.3em;
+ padding:0em;
+ border:none;
+}
+
+/* Dirty EVIL Mozilla hack for round corners */
+pre {
+ -moz-border-radius:11px;
+ -webkit-border-radius:11px;
+ border-radius: 11px;
+}
+
+.example {
+ -moz-border-radius:0px;
+ -webkit-border-radius:0px;
+ border-radius: 0px;
+}
+
+.package, .citetitle {
+ font-style: italic;
+}
+
+.titlepage .edition {
+ color: #336699;
+ background-color: transparent;
+ margin-top: 1em;
+ margin-bottom: 1em;
+ font-size: 1.4em;
+ font-weight: bold;
+ text-align: center;
+}
+
+span.remark {
+ background-color: #ff00ff;
+}
+
+.draft {
+ background-image: url(../images/watermark-draft.png);
+ background-repeat: repeat-y;
+ background-position: center;
+}
+
+.foreignphrase {
+ font-style: inherit;
+}
+
+dt {
+ clear:both;
+}
+
+dt img {
+ border-style: none;
+ max-width: 112px;
+}
+
+dt object {
+ max-width: 112px;
+}
+
+dt .inlinemediaobject, dt object {
+ display: inline;
+ float: left;
+ margin-bottom: 1em;
+ padding-right: 1em;
+ width: 112px;
+}
+
+dl:after {
+ display: block;
+ clear: both;
+ content: "";
+}
+
+.toc dd {
+ padding-bottom: 0em;
+ margin-bottom: 1em;
+ padding-left: 1.3em;
+ margin-left: 0em;
+}
+
+div.toc > dl > dt {
+ padding-bottom: 0em;
+ margin-bottom: 0em;
+ margin-top: 1em;
+}
+
+
+.strikethrough {
+ text-decoration: line-through;
+}
+
+.underline {
+ text-decoration: underline;
+}
+
+.calloutlist img, .callout {
+ padding: 0em;
+ margin: 0em;
+ width: 12pt;
+ display: inline;
+ vertical-align: middle;
+}
+
+.stepalternatives {
+ list-style-image: none;
+ list-style-type: none;
+}
+
+
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/css/default.css b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/css/default.css
new file mode 100644
index 0000000..bf38ebb
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/css/default.css
@@ -0,0 +1,3 @@
+ at import url("common.css");
+ at import url("overrides.css");
+ at import url("lang.css");
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/css/lang.css b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/css/lang.css
new file mode 100644
index 0000000..81c3115
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/css/lang.css
@@ -0,0 +1,2 @@
+/* place holder */
+
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/css/overrides.css b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/css/overrides.css
new file mode 100644
index 0000000..057be29
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/css/overrides.css
@@ -0,0 +1,51 @@
+a:link {
+ color:#0066cc;
+}
+
+a:hover, a:active {
+ color:#003366;
+}
+
+a:visited {
+ color:#6699cc;
+}
+
+
+h1 {
+ color:#3c6eb4
+}
+
+.producttitle {
+ background: #3c6eb4 url(../images/h1-bg.png) top left repeat;
+}
+
+.section h1.title {
+ color:#3c6eb4;
+}
+
+
+h2,h3,h4,h5,h6 {
+ color:#3c6eb4;
+}
+
+table {
+ border:1px solid #3c6eb4;
+}
+
+table th {
+ background-color:#3c6eb4;
+}
+
+
+table tr.even td {
+ background-color:#f5f5f5;
+}
+
+.revhistory table th {
+ color:#3c6eb4;
+}
+
+.titlepage .edition {
+ color: #3c6eb4;
+}
+
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/css/print.css b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/css/print.css
new file mode 100644
index 0000000..773d8ae
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/css/print.css
@@ -0,0 +1,16 @@
+ at import url("common.css");
+ at import url("overrides.css");
+ at import url("lang.css");
+
+#tocframe {
+ display: none;
+}
+
+body.toc_embeded {
+ margin-left: 30px;
+}
+
+.producttitle {
+ color: #336699;
+}
+
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/1.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/1.png
new file mode 100644
index 0000000..c21d7a3
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/1.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/1.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/1.svg
new file mode 100644
index 0000000..a2b3903
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/1.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;fill:#000000;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 17.853468,22.008438 -2.564941,0 0,-7.022461 c -5e-6,-0.143873 -5e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224122,0.224121 -0.08301,0.07748 -0.168786,0.157724 -0.257324,0.240723 -0.08854,0.08302 -0.17432,0.157723 -0.257324,0.224121 l -1.394531,1.120605 -1.245117,-1.543945 3.909668,-3.1127931 2.108398,0 0,12.1357421"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/10.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/10.png
new file mode 100644
index 0000000..15b81da
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/10.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/10.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/10.svg
new file mode 100644
index 0000000..af015ab
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/10.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724 -0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L 8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0 0,12.1357421"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.6378,15.940567 c -9e-6,0.979497 -0.07748,1.853845 -0.232422,2.623047 -0.149422,0.769208 -0.392912,1.422202 -0.730468,1.958984 -0.332039,0.536785 -0.763679,0.94629 -1.294922,1.228516 -0.525722,0.282226 -1.162115,0.42334 -1.90918,0.42334 -0.702803,0 -1.314294,-0.141114 -1.834473,-0.42334 -0.520184,-0.282226 -0.951824,-0.691731 -1.294922,-1.228516 -0.3431,-0.536782 -0.600424,-1.189776 -0.771972,-1.958984 -0.166016,-0.769202 -0.249024,-1.64355 -0.249024,-2.623047 0,-0.979485 0.07471,-1.8566 0.224121,-2.631348 0.154948,-0.77473 0.398437,-1.430491 0.730469,-1.967285 0.33203,-0.536772 0.760903,-0.946277 1.286621,-1.228515 0.525713,-0.2877487 1.162106,-0.4316287 1.90918,-0.431641 0.69726,1.23e-5 1.305984,0.1411254 1.826172,0.42334 0.520175,0.282238 0.954582,0.691743 1.303223,1.228515 0.348624,0.536794 0.608715,1.192555 0.780273,1.967286 0.171541,0.774747 0.257315,1.654629 0.257324,2.639648 m -5.760742,0 c -3e-6,1.383468 0.118975,2.423832 0.356934,3.121094 0.237952,0.6
97268 0.650223,1.0459 1.236816,1.045898 0.575516,2e-6 0.987787,-0.345863 1.236816,-1.037597 0.254552,-0.691729 0.38183,-1.734859 0.381836,-3.129395 -6e-6,-1.38899 -0.127284,-2.43212 -0.381836,-3.129395 -0.249029,-0.702789 -0.6613,-1.054188 -1.236816,-1.054199 -0.293299,1.1e-5 -0.542322,0.08855 -0.74707,0.265625 -0.199223,0.177093 -0.362471,0.439951 -0.489746,0.788574 -0.127282,0.348642 -0.218591,0.785816 -0.273926,1.311524 -0.05534,0.52019 -0.08301,1.126146 -0.08301,1.817871"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/11.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/11.png
new file mode 100644
index 0000000..2fcc2dd
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/11.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/11.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/11.svg
new file mode 100644
index 0000000..cb82b70
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/11.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724 -0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L 8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0 0,12.1357421"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 22.579206,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141117,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168786,0.157724 -0.257324,0.240723 -0.08855,0.08302 -0.17432,0.157723 -0.257325,0.224121 l -1.394531,1.120605 -1.245117,-1.543945 3.909668,-3.1127931 2.108398,0 0,12.1357421"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/12.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/12.png
new file mode 100644
index 0000000..edebe20
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/12.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/12.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/12.svg
new file mode 100644
index 0000000..3b6d822
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/12.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724 -0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L 8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0 0,12.1357421"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.621199,22.008438 -8.143067,0 0,-1.784668 2.855469,-3.07959 c 0.359697,-0.387364 0.686194,-0.744297 0.979492,-1.0708 0.29329,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373535,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437179,10e-6 -0.857751,0.10792 -1.261719,0.323731 -0.403974,0.215829 -0.827314,0.522958 -1.27002,0.921386 l -1.394531,-1.651855 c 0.249023,-0.226877 0.509114,-0.442698 0.780274,-0.647461 0.271157,-0.210275 0.569985,-0.395659 0.896484,-0.556152 0.326495,-0.16047 0.686195,-0.2877488 1.079101,-0.3818364 0.3929,-0.099597 0.832841,-0.1494018 1.319825,-0.1494141 0.581049,1.23e-5 1.101231,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860507,0.3901488 1.187011,0.6889648 0.32649,0.293305 0.575513,0.650239 0.747071,1.070801 0.177075,0.420583 0.265616,0.893727 0.265625,1.419
433 -9e-6,0.47592 -0.08302,0.932463 -0.249024,1.369629 -0.166024,0.431648 -0.392911,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622565,0.830083 -1.004394,1.245117 -0.376309,0.40951 -0.78028,0.827315 -1.211914,1.253418 l -1.460938,1.469238 0,0.116211 4.947266,0 0,2.158203"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/13.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/13.png
new file mode 100644
index 0000000..ec48cef
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/13.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/13.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/13.svg
new file mode 100644
index 0000000..226e461
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/13.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724 -0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L 8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0 0,12.1357421"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.148054,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.207519,1.137207 -0.132821,0.33204 -0.318205,0.625334 -0.556153,0.879883 -0.232429,0.249031 -0.509121,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979486,0.121751 1.721021,0.420579 2.22461,0.896485 0.503572,0.470382 0.755362,1.106775 0.755371,1.909179 -9e-6,0.531253 -0.09685,1.023766 -0.290528,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879882,1.170411 -0.392911,0.332031 -0.890958,0.592122 -1.494141,0.780273 -0.597662,0.182617 -1.303227,0.273926 -2.116699,0.273926 -0.652998,0 -1.267256,-0.05534 -1.842774,-0.166016 -0.575522,-0.105143 -1.112305,-0.268392 -1.610351,-0.489746 l 0,-2.183105 c 0.249022,0.132815 0.51188,0.249025 0.788574,0.348632 0.276691,0.09961 0.553384,0.185387 0.830078,0.257325 0.27669,0.06641 0.547849,0.116212 0.813477,0.149414 0.271155,0.0332 0.525712,0.04981 0.763671,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132812 0.315425,
-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188146,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124512,-0.73877 -7e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.20474 -0.265631,-0.376289 -0.498047,-0.51464 -0.226893,-0.143876 -0.525721,-0.254553 -0.896485,-0.332032 -0.370772,-0.07747 -0.827315,-0.116205 -1.369628,-0.116211 l -0.863282,0 0,-1.801269 0.84668,0 c 0.509111,7e-6 0.93245,-0.04426 1.270019,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124512,-0.672363 -6e-6,-0.431632 -0.135585,-0.769197 -0.406739,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,1e-5 -0.514652,0.02768 -0.747071,0.08301 -0.226891,0.04981 -0.439944,0.116221 -0.63916,0.199218 -0.193687,0.07748 -0.373537,0.166026 -0.53955,0.265625 -0.160484,0.09409 -0.307131,0.188161 -0.439942,0.282227 l -1.294922,-1.7
09961 c 0.232421,-0.171538 0.484212,-0.329253 0.755371,-0.473145 0.276692,-0.143868 0.575519,-0.26838 0.896485,-0.373535 0.320961,-0.1106647 0.666826,-0.1964393 1.037597,-0.2573239 0.370765,-0.06086 0.766435,-0.091296 1.187012,-0.091309 0.597651,1.23e-5 1.139969,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/14.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/14.png
new file mode 100644
index 0000000..33d5637
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/14.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/14.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/14.svg
new file mode 100644
index 0000000..5aaa3a3
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/14.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724 -0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L 8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0 0,12.1357421"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.803816,19.493301 -1.460938,0 0,2.515137 -2.498535,0 0,-2.515137 -5.013672,0 0,-1.784668 5.154785,-7.8359371 2.357422,0 0,7.6284181 1.460938,0 0,1.992187 m -3.959473,-1.992187 0,-2.058594 c -5e-6,-0.07193 -5e-6,-0.17431 0,-0.307129 0.0055,-0.138339 0.01106,-0.293287 0.0166,-0.464844 0.0055,-0.171541 0.01106,-0.348625 0.0166,-0.53125 0.01106,-0.182609 0.01936,-0.356925 0.0249,-0.522949 0.01106,-0.166007 0.01936,-0.309887 0.0249,-0.43164 0.01106,-0.12727 0.01936,-0.218579 0.0249,-0.273926 l -0.07471,0 c -0.09961,0.232431 -0.213058,0.478687 -0.340332,0.738769 -0.121749,0.2601 -0.262862,0.520191 -0.42334,0.780274 l -2.02539,3.071289 2.755859,0"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/15.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/15.png
new file mode 100644
index 0000000..f1a4eb2
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/15.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/15.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/15.svg
new file mode 100644
index 0000000..f51dd96
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/15.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724 -0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L 8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0 0,12.1357421"
+ id="path2839"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 20.761335,14.255508 c 0.520177,8e-6 1.004389,0.08025 1.452637,0.240723 0.448235,0.160489 0.838372,0.395678 1.17041,0.705566 0.332024,0.309903 0.592114,0.697272 0.780274,1.16211 0.188142,0.459315 0.282218,0.987797 0.282226,1.585449 -8e-6,0.658532 -0.102385,1.250654 -0.307129,1.776367 -0.20476,0.520184 -0.506355,0.962892 -0.904785,1.328125 -0.398444,0.359701 -0.893724,0.636394 -1.48584,0.830078 -0.586594,0.193685 -1.261723,0.290528 -2.02539,0.290528 -0.304366,0 -0.605961,-0.01384 -0.904785,-0.0415 -0.298831,-0.02767 -0.586591,-0.06917 -0.863282,-0.124512 -0.27116,-0.04981 -0.531251,-0.116211 -0.780273,-0.199219 -0.243491,-0.08301 -0.464845,-0.17985 -0.664063,-0.290527 l 0,-2.216309 c 0.193684,0.11068 0.417805,0.215823 0.672364,0.31543 0.254555,0.09408 0.517413,0.177086 0.788574,0.249024 0.27669,0.06641 0.553383,0.121746 0.830078,0.166015 0.276689,0.03874 0.539547,0.05811 0.788574,0.05811 0.741532,2e-6 1.305985,-0.152179 1.69336,-0.456543 0.387364,-0.309893 0.581048
,-0.799639 0.581054,-1.469239 -6e-6,-0.597651 -0.190924,-1.051427 -0.572754,-1.361328 -0.376307,-0.315424 -0.960128,-0.473139 -1.751464,-0.473144 -0.143884,5e-6 -0.298832,0.0083 -0.464844,0.0249 -0.160485,0.01661 -0.320967,0.03874 -0.481446,0.06641 -0.15495,0.02768 -0.304364,0.05811 -0.448242,0.09131 -0.143882,0.02767 -0.268394,0.05811 -0.373535,0.09131 l -1.020996,-0.547852 0.456543,-6.1840821 6.408203,0 0,2.1748051 -4.183594,0 -0.199218,2.382324 c 0.177079,-0.03873 0.381832,-0.07747 0.614257,-0.116211 0.237952,-0.03873 0.542314,-0.0581 0.913086,-0.05811"
+ id="path2841"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/16.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/16.png
new file mode 100644
index 0000000..d38a155
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/16.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/16.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/16.svg
new file mode 100644
index 0000000..cb7e2f5
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/16.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724 -0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L 8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0 0,12.1357421"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 16.428328,16.853653 c -1e-6,-0.581049 0.03044,-1.159336 0.09131,-1.734863 0.06641,-0.575514 0.17985,-1.126132 0.340332,-1.651856 0.166015,-0.531241 0.387369,-1.023753 0.664063,-1.477539 0.282224,-0.453765 0.636391,-0.846669 1.0625,-1.178711 0.431637,-0.337553 0.946285,-0.600411 1.543945,-0.788574 0.603185,-0.1936727 1.305984,-0.2905151 2.108398,-0.2905274 0.116205,1.23e-5 0.243483,0.00278 0.381836,0.0083 0.13834,0.00555 0.276686,0.013847 0.415039,0.024902 0.143873,0.00555 0.282219,0.016614 0.415039,0.033203 0.132805,0.016614 0.251783,0.035982 0.356934,0.058105 l 0,2.0502924 c -0.210294,-0.04979 -0.434415,-0.08853 -0.672363,-0.116211 -0.232429,-0.03319 -0.467618,-0.04979 -0.705567,-0.0498 -0.747076,1e-5 -1.361333,0.09408 -1.842773,0.282226 -0.48145,0.182627 -0.863285,0.439951 -1.145508,0.771973 -0.28223,0.33204 -0.484215,0.730477 -0.605957,1.195312 -0.116214,0.464852 -0.188154,0.9795 -0.21582,1.543946 l 0.09961,0 c 0.110674,-0.199212 0.243487,-0.384596 0.398438,-0
.556153 0.160478,-0.177076 0.345862,-0.32649 0.556152,-0.448242 0.210282,-0.127271 0.445471,-0.22688 0.705566,-0.298828 0.265621,-0.07193 0.561681,-0.107902 0.888184,-0.10791 0.52571,8e-6 0.998854,0.08578 1.419434,0.257324 0.420565,0.171557 0.774732,0.42058 1.0625,0.74707 0.293286,0.326504 0.517407,0.727708 0.672363,1.203614 0.154939,0.475916 0.232413,1.021 0.232422,1.635254 -9e-6,0.658532 -0.09408,1.247887 -0.282227,1.768066 -0.182625,0.520184 -0.445483,0.962892 -0.788574,1.328125 -0.343106,0.359701 -0.758145,0.636394 -1.245117,0.830078 -0.486985,0.188151 -1.034836,0.282227 -1.643555,0.282227 -0.59766,0 -1.156579,-0.105144 -1.676758,-0.31543 -0.520185,-0.21582 -0.97396,-0.542317 -1.361328,-0.979492 -0.381837,-0.437173 -0.683432,-0.987791 -0.904785,-1.651856 -0.215821,-0.669593 -0.323731,-1.460933 -0.32373,-2.374023 m 4.216796,3.270508 c 0.226883,2e-6 0.431636,-0.0415 0.614258,-0.124512 0.188146,-0.08854 0.348627,-0.218585 0.481446,-0.390137 0.13834,-0.17708 0.243483,-0.3984
34 0.315429,-0.664062 0.07747,-0.265622 0.116205,-0.581051 0.116211,-0.946289 -6e-6,-0.592118 -0.124518,-1.056961 -0.373535,-1.394531 -0.243495,-0.343094 -0.61703,-0.514643 -1.120605,-0.514649 -0.254562,6e-6 -0.486984,0.04981 -0.697266,0.149414 -0.21029,0.09962 -0.390141,0.229661 -0.539551,0.390137 -0.149417,0.160487 -0.265628,0.340337 -0.348633,0.539551 -0.07748,0.199223 -0.116214,0.401209 -0.116211,0.605957 -3e-6,0.28223 0.0332,0.564456 0.09961,0.846679 0.07194,0.276696 0.17708,0.528486 0.315429,0.755371 0.143877,0.221357 0.318193,0.401207 0.52295,0.539551 0.210282,0.138349 0.453771,0.207522 0.730468,0.20752"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/17.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/17.png
new file mode 100644
index 0000000..d83e898
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/17.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/17.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/17.svg
new file mode 100644
index 0000000..5d6f0ad
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/17.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724 -0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L 8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0 0,12.1357421"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 17.51573,22.008438 4.316406,-9.960937 -5.578125,0 0,-2.1582035 8.367188,0 0,1.6103515 -4.424317,10.508789 -2.681152,0"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/18.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/18.png
new file mode 100644
index 0000000..9e39de4
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/18.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/18.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/18.svg
new file mode 100644
index 0000000..9ea672c
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/18.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724 -0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L 8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0 0,12.1357421"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 20.48741,9.7149811 c 0.503575,1.23e-5 0.979486,0.060885 1.427734,0.1826172 0.448236,0.1217567 0.841139,0.3043737 1.178711,0.5478517 0.337557,0.243501 0.605949,0.547862 0.805176,0.913086 0.19921,0.365244 0.298819,0.794118 0.298828,1.286621 -9e-6,0.365243 -0.05535,0.697274 -0.166016,0.996094 -0.110685,0.293302 -0.262866,0.561694 -0.456543,0.805175 -0.193692,0.237963 -0.423347,0.451017 -0.688965,0.639161 -0.265631,0.188157 -0.553392,0.359707 -0.863281,0.514648 0.320957,0.171556 0.63362,0.362473 0.937988,0.572754 0.309889,0.210292 0.583814,0.448247 0.821778,0.713867 0.237947,0.260096 0.428865,0.55339 0.572754,0.879883 0.143871,0.326501 0.215811,0.691735 0.21582,1.095703 -9e-6,0.503583 -0.09962,0.960126 -0.298828,1.369629 -0.199227,0.409506 -0.478687,0.758139 -0.838379,1.045898 -0.359708,0.287761 -0.791348,0.509115 -1.294922,0.664063 -0.498053,0.154948 -1.048671,0.232422 -1.651855,0.232422 -0.652999,0 -1.234053,-0.07471 -1.743164,-0.224121 -0.509117,-0.149414 -0.93799
1,-0.362467 -1.286622,-0.639161 -0.348634,-0.276691 -0.614258,-0.617023 -0.796875,-1.020996 -0.177084,-0.403969 -0.265625,-0.857744 -0.265625,-1.361328 0,-0.415035 0.06087,-0.78857 0.182618,-1.120605 0.121744,-0.332027 0.287759,-0.630855 0.498046,-0.896485 0.210285,-0.265619 0.456542,-0.500808 0.73877,-0.705566 0.282224,-0.204747 0.583819,-0.384597 0.904785,-0.539551 -0.271161,-0.171543 -0.525718,-0.356927 -0.763672,-0.556152 -0.237957,-0.204746 -0.445477,-0.428866 -0.622558,-0.672363 -0.171551,-0.249016 -0.309897,-0.522942 -0.415039,-0.821778 -0.09961,-0.298819 -0.149415,-0.628083 -0.149414,-0.987793 -1e-6,-0.481435 0.09961,-0.902008 0.298828,-1.261718 0.204751,-0.365224 0.478676,-0.669585 0.821777,-0.913086 0.343097,-0.249012 0.738767,-0.434396 1.187012,-0.5561527 0.448238,-0.1217326 0.918615,-0.1826049 1.411133,-0.1826172 m -1.718262,9.0644529 c -3e-6,0.221357 0.03597,0.42611 0.10791,0.614258 0.07194,0.18262 0.17708,0.340334 0.31543,0.473145 0.143876,0.132814 0.32096,0.23
7957 0.53125,0.315429 0.210282,0.07194 0.453771,0.107912 0.730468,0.10791 0.58105,2e-6 1.015457,-0.135577 1.303223,-0.406738 0.287754,-0.27669 0.431634,-0.639157 0.431641,-1.087402 -7e-6,-0.232419 -0.04981,-0.439938 -0.149414,-0.622559 -0.09408,-0.188147 -0.218594,-0.359696 -0.373535,-0.514648 -0.14942,-0.160478 -0.32097,-0.307125 -0.514649,-0.439942 -0.19369,-0.132807 -0.387375,-0.260086 -0.581055,-0.381836 L 20.3878,16.72084 c -0.243494,0.12175 -0.464848,0.254563 -0.664062,0.398438 -0.199223,0.138351 -0.370772,0.293299 -0.514649,0.464844 -0.138349,0.16602 -0.246259,0.348637 -0.32373,0.547851 -0.07748,0.199223 -0.116214,0.415043 -0.116211,0.647461 m 1.70166,-7.188476 c -0.182622,10e-6 -0.354171,0.02768 -0.514648,0.08301 -0.154952,0.05535 -0.290532,0.13559 -0.406739,0.240723 -0.11068,0.105153 -0.199222,0.235199 -0.265625,0.390137 -0.06641,0.154957 -0.09961,0.329274 -0.09961,0.522949 -3e-6,0.232431 0.0332,0.434416 0.09961,0.605957 0.07194,0.166024 0.166012,0.315438 0.282227,0
.448242 0.121741,0.127287 0.260087,0.243498 0.415039,0.348633 0.160477,0.09962 0.32926,0.199226 0.506348,0.298828 0.171544,-0.08853 0.334793,-0.185376 0.489746,-0.290527 0.154942,-0.105135 0.290522,-0.224113 0.406738,-0.356934 0.121739,-0.138338 0.218581,-0.293286 0.290527,-0.464843 0.07193,-0.171541 0.107904,-0.367993 0.10791,-0.589356 -6e-6,-0.193675 -0.03321,-0.367992 -0.09961,-0.522949 -0.06641,-0.154938 -0.15772,-0.284984 -0.273926,-0.390137 -0.116216,-0.105133 -0.254562,-0.185374 -0.415039,-0.240723 -0.160487,-0.05533 -0.334803,-0.083 -0.522949,-0.08301"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/19.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/19.png
new file mode 100644
index 0000000..9eeedfb
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/19.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/19.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/19.svg
new file mode 100644
index 0000000..80d1d09
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/19.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724 -0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L 8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0 0,12.1357421"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.554792,15.052383 c -8e-6,0.581061 -0.03321,1.162116 -0.09961,1.743164 -0.06088,0.575526 -0.174325,1.126144 -0.340332,1.651856 -0.16049,0.525719 -0.381844,1.018232 -0.664063,1.477539 -0.2767,0.453778 -0.630866,0.846681 -1.0625,1.178711 -0.426112,0.332032 -0.94076,0.59489 -1.543945,0.788574 -0.597661,0.188151 -1.300459,0.282227 -2.108398,0.282227 -0.116214,0 -0.243493,-0.0028 -0.381836,-0.0083 -0.138349,-0.0055 -0.279462,-0.01384 -0.42334,-0.0249 -0.138348,-0.0055 -0.273928,-0.0166 -0.406738,-0.0332 -0.132814,-0.01107 -0.249025,-0.02767 -0.348633,-0.0498 l 0,-2.058594 c 0.204751,0.05534 0.423338,0.09961 0.655762,0.132813 0.237953,0.02767 0.478675,0.04151 0.722168,0.0415 0.747066,2e-6 1.361324,-0.09131 1.842773,-0.273925 0.48144,-0.188149 0.863276,-0.44824 1.145508,-0.780274 0.28222,-0.337562 0.481439,-0.738766 0.597656,-1.203613 0.121738,-0.464839 0.196445,-0.97672 0.224121,-1.535645 l -0.10791,0 c -0.110683,0.199225 -0.243496,0.384609 -0.398438,0.556153 -0.1549
53,0.171554 -0.33757,0.320968 -0.547851,0.448242 -0.210292,0.127283 -0.448247,0.226892 -0.713867,0.298828 -0.26563,0.07194 -0.561691,0.107914 -0.888184,0.10791 -0.525719,4e-6 -0.998863,-0.08577 -1.419433,-0.257324 -0.420575,-0.171545 -0.777509,-0.420568 -1.070801,-0.74707 -0.287762,-0.326492 -0.509116,-0.727696 -0.664063,-1.203614 -0.154948,-0.475904 -0.232422,-1.020988 -0.232422,-1.635253 0,-0.65852 0.09131,-1.247875 0.273926,-1.768067 0.18815,-0.520172 0.453775,-0.960113 0.796875,-1.319824 0.343097,-0.365223 0.758136,-0.644682 1.245117,-0.838379 0.49251,-0.1936727 1.043128,-0.2905151 1.651856,-0.2905274 0.597651,1.23e-5 1.15657,0.1079224 1.676758,0.3237304 0.520175,0.210298 0.971184,0.534028 1.353027,0.971192 0.381828,0.437185 0.683423,0.990569 0.904785,1.660156 0.221346,0.669605 0.332023,1.458178 0.332031,2.365722 m -4.216796,-3.262207 c -0.226893,1.1e-5 -0.434412,0.04151 -0.622559,0.124512 -0.188155,0.08302 -0.351403,0.213063 -0.489746,0.390137 -0.132816,0.171559 -0.2379
59,0.392913 -0.31543,0.664062 -0.07194,0.265634 -0.107913,0.581063 -0.10791,0.946289 -3e-6,0.586596 0.124509,1.05144 0.373535,1.394532 0.24902,0.343105 0.625322,0.514654 1.128906,0.514648 0.254553,6e-6 0.486975,-0.0498 0.697266,-0.149414 0.210281,-0.0996 0.390131,-0.229648 0.539551,-0.390137 0.149408,-0.160475 0.262852,-0.340325 0.340332,-0.53955 0.083,-0.199212 0.124505,-0.401197 0.124512,-0.605958 -7e-6,-0.282218 -0.03598,-0.561677 -0.107911,-0.838378 -0.06641,-0.282218 -0.171555,-0.534008 -0.315429,-0.755372 -0.138352,-0.226878 -0.312669,-0.409495 -0.52295,-0.547851 -0.204757,-0.138336 -0.44548,-0.207509 -0.722167,-0.20752"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/2.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/2.png
new file mode 100644
index 0000000..ff9cc57
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/2.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/2.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/2.svg
new file mode 100644
index 0000000..8e94260
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/2.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 19.89546,22.008438 -8.143066,0 0,-1.784668 2.855468,-3.07959 c 0.359697,-0.387364 0.686194,-0.744297 0.979493,-1.0708 0.293289,-0.326492 0.545079,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.373529,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.17431,-0.666821 0.174316,-1.037598 -6e-6,-0.409496 -0.124517,-0.727692 -0.373535,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.261719,0.323731 -0.403974,0.215829 -0.827313,0.522958 -1.270019,0.921386 l -1.394531,-1.651855 c 0.249022,-0.226877 0.509113,-0.442698 0.780273,-0.647461 0.271157,-0.210275 0.569985,-0.395659 0.896484,-0.556152 0.326495,-0.16047 0.686195,-0.2877488 1.079102,-0.3818364 0.3929,-0.099597 0.832841,-0.1494018 1.319824,-0.1494141 0.58105,1.23e-5 1.101231,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860507,0.3901488 1.187012,0.6889648 0.326489,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.893727 0.265625,1.41
9433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/20.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/20.png
new file mode 100644
index 0000000..b28b4aa
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/20.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/20.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/20.svg
new file mode 100644
index 0000000..409ac6e
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/20.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.6378,15.940567 c -9e-6,0.979497 -0.07748,1.853845 -0.232422,2.623047 -0.149422,0.769208 -0.392912,1.422202 -0.730468,1.958984 -0.332039,0.536785 -0.763679,0.94629 -1.294922,1.228516 -0.525722,0.282226 -1.162115,0.42334 -1.90918,0.42334 -0.702803,0 -1.314294,-0.141114 -1.834473,-0.42334 -0.520184,-0.282226 -0.951824,-0.691731 -1.294922,-1.228516 -0.3431,-0.536782 -0.600424,-1.189776 -0.771972,-1.958984 -0.166016,-0.769202 -0.249024,-1.64355 -0.249024,-2.623047 0,-0.979485 0.07471,-1.8566 0.224121,-2.631348 0.154948,-0.77473 0.398437,-1.430491 0.730469,-1.967285 0.33203,-0.536772 0.760903,-0.946277 1.286621,-1.228515 0.525713,-0.2877487 1.162106,-0.4316287 1.90918,-0.431641 0.69726,1.23e-5 1.305984,0.1411254 1.826172,0.42334 0.520175,0.282238 0.954582,0.691743 1.303223,1.228515 0.348624,0.536794 0.608715,1.192555 0.780273,1.967286 0.171541,0.774747 0.257315,1.654629 0.257324,2.639648 m -5.760742,0 c -3e-6,1.383468 0.118975,2.423832 0.356934,3.121094 0.237952,0.6
97268 0.650223,1.0459 1.236816,1.045898 0.575516,2e-6 0.987787,-0.345863 1.236816,-1.037597 0.254552,-0.691729 0.38183,-1.734859 0.381836,-3.129395 -6e-6,-1.38899 -0.127284,-2.43212 -0.381836,-3.129395 -0.249029,-0.702789 -0.6613,-1.054188 -1.236816,-1.054199 -0.293299,1.1e-5 -0.542322,0.08855 -0.74707,0.265625 -0.199223,0.177093 -0.362471,0.439951 -0.489746,0.788574 -0.127282,0.348642 -0.218591,0.785816 -0.273926,1.311524 -0.05534,0.52019 -0.08301,1.126146 -0.08301,1.817871"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/21.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/21.png
new file mode 100644
index 0000000..eda952c
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/21.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/21.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/21.svg
new file mode 100644
index 0000000..7bc03af
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/21.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 22.579206,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141117,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168786,0.157724 -0.257324,0.240723 -0.08855,0.08302 -0.17432,0.157723 -0.257325,0.224121 l -1.394531,1.120605 -1.245117,-1.543945 3.909668,-3.1127931 2.108398,0 0,12.1357421"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/22.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/22.png
new file mode 100644
index 0000000..90b14b0
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/22.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/22.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/22.svg
new file mode 100644
index 0000000..fe086f6
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/22.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.621199,22.008438 -8.143067,0 0,-1.784668 2.855469,-3.07959 c 0.359697,-0.387364 0.686194,-0.744297 0.979492,-1.0708 0.29329,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373535,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437179,10e-6 -0.857751,0.10792 -1.261719,0.323731 -0.403974,0.215829 -0.827314,0.522958 -1.27002,0.921386 l -1.394531,-1.651855 c 0.249023,-0.226877 0.509114,-0.442698 0.780274,-0.647461 0.271157,-0.210275 0.569985,-0.395659 0.896484,-0.556152 0.326495,-0.16047 0.686195,-0.2877488 1.079101,-0.3818364 0.3929,-0.099597 0.832841,-0.1494018 1.319825,-0.1494141 0.581049,1.23e-5 1.101231,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860507,0.3901488 1.187011,0.6889648 0.32649,0.293305 0.575513,0.650239 0.747071,1.070801 0.177075,0.420583 0.265616,0.893727 0.265625,1.419
433 -9e-6,0.47592 -0.08302,0.932463 -0.249024,1.369629 -0.166024,0.431648 -0.392911,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622565,0.830083 -1.004394,1.245117 -0.376309,0.40951 -0.78028,0.827315 -1.211914,1.253418 l -1.460938,1.469238 0,0.116211 4.947266,0 0,2.158203"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/23.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/23.png
new file mode 100644
index 0000000..8b35a74
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/23.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/23.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/23.svg
new file mode 100644
index 0000000..f17ec29
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/23.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.148054,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.207519,1.137207 -0.132821,0.33204 -0.318205,0.625334 -0.556153,0.879883 -0.232429,0.249031 -0.509121,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979486,0.121751 1.721021,0.420579 2.22461,0.896485 0.503572,0.470382 0.755362,1.106775 0.755371,1.909179 -9e-6,0.531253 -0.09685,1.023766 -0.290528,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879882,1.170411 -0.392911,0.332031 -0.890958,0.592122 -1.494141,0.780273 -0.597662,0.182617 -1.303227,0.273926 -2.116699,0.273926 -0.652998,0 -1.267256,-0.05534 -1.842774,-0.166016 -0.575522,-0.105143 -1.112305,-0.268392 -1.610351,-0.489746 l 0,-2.183105 c 0.249022,0.132815 0.51188,0.249025 0.788574,0.348632 0.276691,0.09961 0.553384,0.185387 0.830078,0.257325 0.27669,0.06641 0.547849,0.116212 0.813477,0.149414 0.271155,0.0332 0.525712,0.04981 0.763671,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132812 0.315425,
-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188146,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124512,-0.73877 -7e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.20474 -0.265631,-0.376289 -0.498047,-0.51464 -0.226893,-0.143876 -0.525721,-0.254553 -0.896485,-0.332032 -0.370772,-0.07747 -0.827315,-0.116205 -1.369628,-0.116211 l -0.863282,0 0,-1.801269 0.84668,0 c 0.509111,7e-6 0.93245,-0.04426 1.270019,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124512,-0.672363 -6e-6,-0.431632 -0.135585,-0.769197 -0.406739,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,1e-5 -0.514652,0.02768 -0.747071,0.08301 -0.226891,0.04981 -0.439944,0.116221 -0.63916,0.199218 -0.193687,0.07748 -0.373537,0.166026 -0.53955,0.265625 -0.160484,0.09409 -0.307131,0.188161 -0.439942,0.282227 l -1.294922,-1.7
09961 c 0.232421,-0.171538 0.484212,-0.329253 0.755371,-0.473145 0.276692,-0.143868 0.575519,-0.26838 0.896485,-0.373535 0.320961,-0.1106647 0.666826,-0.1964393 1.037597,-0.2573239 0.370765,-0.06086 0.766435,-0.091296 1.187012,-0.091309 0.597651,1.23e-5 1.139969,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/24.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/24.png
new file mode 100644
index 0000000..6041b02
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/24.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/24.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/24.svg
new file mode 100644
index 0000000..42a5333
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/24.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.803816,19.493301 -1.460938,0 0,2.515137 -2.498535,0 0,-2.515137 -5.013672,0 0,-1.784668 5.154785,-7.8359371 2.357422,0 0,7.6284181 1.460938,0 0,1.992187 m -3.959473,-1.992187 0,-2.058594 c -5e-6,-0.07193 -5e-6,-0.17431 0,-0.307129 0.0055,-0.138339 0.01106,-0.293287 0.0166,-0.464844 0.0055,-0.171541 0.01106,-0.348625 0.0166,-0.53125 0.01106,-0.182609 0.01936,-0.356925 0.0249,-0.522949 0.01106,-0.166007 0.01936,-0.309887 0.0249,-0.43164 0.01106,-0.12727 0.01936,-0.218579 0.0249,-0.273926 l -0.07471,0 c -0.09961,0.232431 -0.213058,0.478687 -0.340332,0.738769 -0.121749,0.2601 -0.262862,0.520191 -0.42334,0.780274 l -2.02539,3.071289 2.755859,0"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/25.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/25.png
new file mode 100644
index 0000000..ecb15e6
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/25.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/25.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/25.svg
new file mode 100644
index 0000000..a8d4672
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/25.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 20.761335,14.255508 c 0.520177,8e-6 1.004389,0.08025 1.452637,0.240723 0.448235,0.160489 0.838372,0.395678 1.17041,0.705566 0.332024,0.309903 0.592114,0.697272 0.780274,1.16211 0.188142,0.459315 0.282218,0.987797 0.282226,1.585449 -8e-6,0.658532 -0.102385,1.250654 -0.307129,1.776367 -0.20476,0.520184 -0.506355,0.962892 -0.904785,1.328125 -0.398444,0.359701 -0.893724,0.636394 -1.48584,0.830078 -0.586594,0.193685 -1.261723,0.290528 -2.02539,0.290528 -0.304366,0 -0.605961,-0.01384 -0.904785,-0.0415 -0.298831,-0.02767 -0.586591,-0.06917 -0.863282,-0.124512 -0.27116,-0.04981 -0.531251,-0.116211 -0.780273,-0.199219 -0.243491,-0.08301 -0.464845,-0.17985 -0.664063,-0.290527 l 0,-2.216309 c 0.193684,0.11068 0.417805,0.215823 0.672364,0.31543 0.254555,0.09408 0.517413,0.177086 0.788574,0.249024 0.27669,0.06641 0.553383,0.121746 0.830078,0.166015 0.276689,0.03874 0.539547,0.05811 0.788574,0.05811 0.741532,2e-6 1.305985,-0.152179 1.69336,-0.456543 0.387364,-0.309893 0.581048
,-0.799639 0.581054,-1.469239 -6e-6,-0.597651 -0.190924,-1.051427 -0.572754,-1.361328 -0.376307,-0.315424 -0.960128,-0.473139 -1.751464,-0.473144 -0.143884,5e-6 -0.298832,0.0083 -0.464844,0.0249 -0.160485,0.01661 -0.320967,0.03874 -0.481446,0.06641 -0.15495,0.02768 -0.304364,0.05811 -0.448242,0.09131 -0.143882,0.02767 -0.268394,0.05811 -0.373535,0.09131 l -1.020996,-0.547852 0.456543,-6.1840821 6.408203,0 0,2.1748051 -4.183594,0 -0.199218,2.382324 c 0.177079,-0.03873 0.381832,-0.07747 0.614257,-0.116211 0.237952,-0.03873 0.542314,-0.0581 0.913086,-0.05811"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/26.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/26.png
new file mode 100644
index 0000000..4b2f560
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/26.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/26.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/26.svg
new file mode 100644
index 0000000..3cf00ec
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/26.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 16.428328,16.853653 c -1e-6,-0.581049 0.03044,-1.159336 0.09131,-1.734863 0.06641,-0.575514 0.17985,-1.126132 0.340332,-1.651856 0.166015,-0.531241 0.387369,-1.023753 0.664063,-1.477539 0.282224,-0.453765 0.636391,-0.846669 1.0625,-1.178711 0.431637,-0.337553 0.946285,-0.600411 1.543945,-0.788574 0.603185,-0.1936727 1.305984,-0.2905151 2.108398,-0.2905274 0.116205,1.23e-5 0.243483,0.00278 0.381836,0.0083 0.13834,0.00555 0.276686,0.013847 0.415039,0.024902 0.143873,0.00555 0.282219,0.016614 0.415039,0.033203 0.132805,0.016614 0.251783,0.035982 0.356934,0.058105 l 0,2.0502924 c -0.210294,-0.04979 -0.434415,-0.08853 -0.672363,-0.116211 -0.232429,-0.03319 -0.467618,-0.04979 -0.705567,-0.0498 -0.747076,1e-5 -1.361333,0.09408 -1.842773,0.282226 -0.48145,0.182627 -0.863285,0.439951 -1.145508,0.771973 -0.28223,0.33204 -0.484215,0.730477 -0.605957,1.195312 -0.116214,0.464852 -0.188154,0.9795 -0.21582,1.543946 l 0.09961,0 c 0.110674,-0.199212 0.243487,-0.384596 0.398438,-0
.556153 0.160478,-0.177076 0.345862,-0.32649 0.556152,-0.448242 0.210282,-0.127271 0.445471,-0.22688 0.705566,-0.298828 0.265621,-0.07193 0.561681,-0.107902 0.888184,-0.10791 0.52571,8e-6 0.998854,0.08578 1.419434,0.257324 0.420565,0.171557 0.774732,0.42058 1.0625,0.74707 0.293286,0.326504 0.517407,0.727708 0.672363,1.203614 0.154939,0.475916 0.232413,1.021 0.232422,1.635254 -9e-6,0.658532 -0.09408,1.247887 -0.282227,1.768066 -0.182625,0.520184 -0.445483,0.962892 -0.788574,1.328125 -0.343106,0.359701 -0.758145,0.636394 -1.245117,0.830078 -0.486985,0.188151 -1.034836,0.282227 -1.643555,0.282227 -0.59766,0 -1.156579,-0.105144 -1.676758,-0.31543 -0.520185,-0.21582 -0.97396,-0.542317 -1.361328,-0.979492 -0.381837,-0.437173 -0.683432,-0.987791 -0.904785,-1.651856 -0.215821,-0.669593 -0.323731,-1.460933 -0.32373,-2.374023 m 4.216796,3.270508 c 0.226883,2e-6 0.431636,-0.0415 0.614258,-0.124512 0.188146,-0.08854 0.348627,-0.218585 0.481446,-0.390137 0.13834,-0.17708 0.243483,-0.3984
34 0.315429,-0.664062 0.07747,-0.265622 0.116205,-0.581051 0.116211,-0.946289 -6e-6,-0.592118 -0.124518,-1.056961 -0.373535,-1.394531 -0.243495,-0.343094 -0.61703,-0.514643 -1.120605,-0.514649 -0.254562,6e-6 -0.486984,0.04981 -0.697266,0.149414 -0.21029,0.09962 -0.390141,0.229661 -0.539551,0.390137 -0.149417,0.160487 -0.265628,0.340337 -0.348633,0.539551 -0.07748,0.199223 -0.116214,0.401209 -0.116211,0.605957 -3e-6,0.28223 0.0332,0.564456 0.09961,0.846679 0.07194,0.276696 0.17708,0.528486 0.315429,0.755371 0.143877,0.221357 0.318193,0.401207 0.52295,0.539551 0.210282,0.138349 0.453771,0.207522 0.730468,0.20752"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/27.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/27.png
new file mode 100644
index 0000000..ecf058e
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/27.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/27.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/27.svg
new file mode 100644
index 0000000..c8d6440
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/27.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 17.51573,22.008438 4.316406,-9.960937 -5.578125,0 0,-2.1582035 8.367188,0 0,1.6103515 -4.424317,10.508789 -2.681152,0"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/28.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/28.png
new file mode 100644
index 0000000..e64efb2
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/28.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/28.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/28.svg
new file mode 100644
index 0000000..5acce93
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/28.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 20.48741,9.7149811 c 0.503575,1.23e-5 0.979486,0.060885 1.427734,0.1826172 0.448236,0.1217567 0.841139,0.3043737 1.178711,0.5478517 0.337557,0.243501 0.605949,0.547862 0.805176,0.913086 0.19921,0.365244 0.298819,0.794118 0.298828,1.286621 -9e-6,0.365243 -0.05535,0.697274 -0.166016,0.996094 -0.110685,0.293302 -0.262866,0.561694 -0.456543,0.805175 -0.193692,0.237963 -0.423347,0.451017 -0.688965,0.639161 -0.265631,0.188157 -0.553392,0.359707 -0.863281,0.514648 0.320957,0.171556 0.63362,0.362473 0.937988,0.572754 0.309889,0.210292 0.583814,0.448247 0.821778,0.713867 0.237947,0.260096 0.428865,0.55339 0.572754,0.879883 0.143871,0.326501 0.215811,0.691735 0.21582,1.095703 -9e-6,0.503583 -0.09962,0.960126 -0.298828,1.369629 -0.199227,0.409506 -0.478687,0.758139 -0.838379,1.045898 -0.359708,0.287761 -0.791348,0.509115 -1.294922,0.664063 -0.498053,0.154948 -1.048671,0.232422 -1.651855,0.232422 -0.652999,0 -1.234053,-0.07471 -1.743164,-0.224121 -0.509117,-0.149414 -0.93799
1,-0.362467 -1.286622,-0.639161 -0.348634,-0.276691 -0.614258,-0.617023 -0.796875,-1.020996 -0.177084,-0.403969 -0.265625,-0.857744 -0.265625,-1.361328 0,-0.415035 0.06087,-0.78857 0.182618,-1.120605 0.121744,-0.332027 0.287759,-0.630855 0.498046,-0.896485 0.210285,-0.265619 0.456542,-0.500808 0.73877,-0.705566 0.282224,-0.204747 0.583819,-0.384597 0.904785,-0.539551 -0.271161,-0.171543 -0.525718,-0.356927 -0.763672,-0.556152 -0.237957,-0.204746 -0.445477,-0.428866 -0.622558,-0.672363 -0.171551,-0.249016 -0.309897,-0.522942 -0.415039,-0.821778 -0.09961,-0.298819 -0.149415,-0.628083 -0.149414,-0.987793 -1e-6,-0.481435 0.09961,-0.902008 0.298828,-1.261718 0.204751,-0.365224 0.478676,-0.669585 0.821777,-0.913086 0.343097,-0.249012 0.738767,-0.434396 1.187012,-0.5561527 0.448238,-0.1217326 0.918615,-0.1826049 1.411133,-0.1826172 m -1.718262,9.0644529 c -3e-6,0.221357 0.03597,0.42611 0.10791,0.614258 0.07194,0.18262 0.17708,0.340334 0.31543,0.473145 0.143876,0.132814 0.32096,0.23
7957 0.53125,0.315429 0.210282,0.07194 0.453771,0.107912 0.730468,0.10791 0.58105,2e-6 1.015457,-0.135577 1.303223,-0.406738 0.287754,-0.27669 0.431634,-0.639157 0.431641,-1.087402 -7e-6,-0.232419 -0.04981,-0.439938 -0.149414,-0.622559 -0.09408,-0.188147 -0.218594,-0.359696 -0.373535,-0.514648 -0.14942,-0.160478 -0.32097,-0.307125 -0.514649,-0.439942 -0.19369,-0.132807 -0.387375,-0.260086 -0.581055,-0.381836 L 20.3878,16.72084 c -0.243494,0.12175 -0.464848,0.254563 -0.664062,0.398438 -0.199223,0.138351 -0.370772,0.293299 -0.514649,0.464844 -0.138349,0.16602 -0.246259,0.348637 -0.32373,0.547851 -0.07748,0.199223 -0.116214,0.415043 -0.116211,0.647461 m 1.70166,-7.188476 c -0.182622,10e-6 -0.354171,0.02768 -0.514648,0.08301 -0.154952,0.05535 -0.290532,0.13559 -0.406739,0.240723 -0.11068,0.105153 -0.199222,0.235199 -0.265625,0.390137 -0.06641,0.154957 -0.09961,0.329274 -0.09961,0.522949 -3e-6,0.232431 0.0332,0.434416 0.09961,0.605957 0.07194,0.166024 0.166012,0.315438 0.282227,0
.448242 0.121741,0.127287 0.260087,0.243498 0.415039,0.348633 0.160477,0.09962 0.32926,0.199226 0.506348,0.298828 0.171544,-0.08853 0.334793,-0.185376 0.489746,-0.290527 0.154942,-0.105135 0.290522,-0.224113 0.406738,-0.356934 0.121739,-0.138338 0.218581,-0.293286 0.290527,-0.464843 0.07193,-0.171541 0.107904,-0.367993 0.10791,-0.589356 -6e-6,-0.193675 -0.03321,-0.367992 -0.09961,-0.522949 -0.06641,-0.154938 -0.15772,-0.284984 -0.273926,-0.390137 -0.116216,-0.105133 -0.254562,-0.185374 -0.415039,-0.240723 -0.160487,-0.05533 -0.334803,-0.083 -0.522949,-0.08301"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/29.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/29.png
new file mode 100644
index 0000000..dbbca1b
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/29.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/29.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/29.svg
new file mode 100644
index 0000000..507dd44
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/29.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.554792,15.052383 c -8e-6,0.581061 -0.03321,1.162116 -0.09961,1.743164 -0.06088,0.575526 -0.174325,1.126144 -0.340332,1.651856 -0.16049,0.525719 -0.381844,1.018232 -0.664063,1.477539 -0.2767,0.453778 -0.630866,0.846681 -1.0625,1.178711 -0.426112,0.332032 -0.94076,0.59489 -1.543945,0.788574 -0.597661,0.188151 -1.300459,0.282227 -2.108398,0.282227 -0.116214,0 -0.243493,-0.0028 -0.381836,-0.0083 -0.138349,-0.0055 -0.279462,-0.01384 -0.42334,-0.0249 -0.138348,-0.0055 -0.273928,-0.0166 -0.406738,-0.0332 -0.132814,-0.01107 -0.249025,-0.02767 -0.348633,-0.0498 l 0,-2.058594 c 0.204751,0.05534 0.423338,0.09961 0.655762,0.132813 0.237953,0.02767 0.478675,0.04151 0.722168,0.0415 0.747066,2e-6 1.361324,-0.09131 1.842773,-0.273925 0.48144,-0.188149 0.863276,-0.44824 1.145508,-0.780274 0.28222,-0.337562 0.481439,-0.738766 0.597656,-1.203613 0.121738,-0.464839 0.196445,-0.97672 0.224121,-1.535645 l -0.10791,0 c -0.110683,0.199225 -0.243496,0.384609 -0.398438,0.556153 -0.1549
53,0.171554 -0.33757,0.320968 -0.547851,0.448242 -0.210292,0.127283 -0.448247,0.226892 -0.713867,0.298828 -0.26563,0.07194 -0.561691,0.107914 -0.888184,0.10791 -0.525719,4e-6 -0.998863,-0.08577 -1.419433,-0.257324 -0.420575,-0.171545 -0.777509,-0.420568 -1.070801,-0.74707 -0.287762,-0.326492 -0.509116,-0.727696 -0.664063,-1.203614 -0.154948,-0.475904 -0.232422,-1.020988 -0.232422,-1.635253 0,-0.65852 0.09131,-1.247875 0.273926,-1.768067 0.18815,-0.520172 0.453775,-0.960113 0.796875,-1.319824 0.343097,-0.365223 0.758136,-0.644682 1.245117,-0.838379 0.49251,-0.1936727 1.043128,-0.2905151 1.651856,-0.2905274 0.597651,1.23e-5 1.15657,0.1079224 1.676758,0.3237304 0.520175,0.210298 0.971184,0.534028 1.353027,0.971192 0.381828,0.437185 0.683423,0.990569 0.904785,1.660156 0.221346,0.669605 0.332023,1.458178 0.332031,2.365722 m -4.216796,-3.262207 c -0.226893,1.1e-5 -0.434412,0.04151 -0.622559,0.124512 -0.188155,0.08302 -0.351403,0.213063 -0.489746,0.390137 -0.132816,0.171559 -0.2379
59,0.392913 -0.31543,0.664062 -0.07194,0.265634 -0.107913,0.581063 -0.10791,0.946289 -3e-6,0.586596 0.124509,1.05144 0.373535,1.394532 0.24902,0.343105 0.625322,0.514654 1.128906,0.514648 0.254553,6e-6 0.486975,-0.0498 0.697266,-0.149414 0.210281,-0.0996 0.390131,-0.229648 0.539551,-0.390137 0.149408,-0.160475 0.262852,-0.340325 0.340332,-0.53955 0.083,-0.199212 0.124505,-0.401197 0.124512,-0.605958 -7e-6,-0.282218 -0.03598,-0.561677 -0.107911,-0.838378 -0.06641,-0.282218 -0.171555,-0.534008 -0.315429,-0.755372 -0.138352,-0.226878 -0.312669,-0.409495 -0.52295,-0.547851 -0.204757,-0.138336 -0.44548,-0.207509 -0.722167,-0.20752"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/3.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/3.png
new file mode 100644
index 0000000..4febe43
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/3.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/3.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/3.svg
new file mode 100644
index 0000000..5e87e1f
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/3.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;text-anchor:start;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 19.422316,12.587051 c -9e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.23243,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315437,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503572,0.470382 0.755362,1.106775 0.755371,1.909179 -9e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.392911,0.332031 -0.890957,0.592122 -1.494141,0.780273 -0.597661,0.182617 -1.303227,0.273926 -2.116699,0.273926 -0.652998,0 -1.267255,-0.05534 -1.842773,-0.166016 -0.575523,-0.105143 -1.112306,-0.268392 -1.610352,-0.489746 l 0,-2.183105 c 0.249023,0.132815 0.511881,0.249025 0.788574,0.348632 0.276692,0.09961 0.553384,0.185387 0.830079,0.257325 0.27669,0.06641 0.547848,0.116212 0.813476,0.149414 0.271156,0.0332 0.525713,0.04981 0.763672,0.0498 0.475907,2e-6 0.871577,-0.04427 1.187012,-0.132812 0.315424,-
0.08854 0.567214,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320957,-0.351397 0.398437,-0.572754 0.083,-0.226885 0.124506,-0.473141 0.124512,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.265631,-0.376297 -0.498047,-0.514648 -0.226893,-0.143876 -0.525721,-0.254553 -0.896484,-0.332032 -0.370773,-0.07747 -0.827315,-0.116205 -1.369629,-0.116211 l -0.863281,0 0,-1.801269 0.846679,0 c 0.509111,7e-6 0.932451,-0.04426 1.27002,-0.132813 0.33756,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.43164,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124512,-0.672363 -6e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.68897,-0.365224 -1.27002,-0.365234 -0.265629,10e-6 -0.514652,0.02768 -0.74707,0.08301 -0.226891,0.04981 -0.439944,0.116221 -0.63916,0.199218 -0.193688,0.07748 -0.373538,0.166026 -0.539551,0.265625 -0.160484,0.09409 -0.307131,0.188161 -0.439941,0.282227 l -1.294922,-1.70
9961 c 0.232421,-0.171538 0.484211,-0.329253 0.755371,-0.473145 0.276691,-0.143868 0.575519,-0.26838 0.896484,-0.373535 0.320961,-0.1106647 0.666827,-0.1964393 1.037598,-0.2573239 0.370765,-0.06086 0.766435,-0.091296 1.187012,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492506,0.1272911 0.913079,0.3154421 1.261718,0.5644531 0.348626,0.243501 0.617017,0.545096 0.805176,0.904786 0.193677,0.354177 0.290519,0.760914 0.290528,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/30.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/30.png
new file mode 100644
index 0000000..f4ffb14
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/30.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/30.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/30.svg
new file mode 100644
index 0000000..434e663
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/30.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.6378,15.940567 c -9e-6,0.979497 -0.07748,1.853845 -0.232422,2.623047 -0.149422,0.769208 -0.392912,1.422202 -0.730468,1.958984 -0.332039,0.536785 -0.763679,0.94629 -1.294922,1.228516 -0.525722,0.282226 -1.162115,0.42334 -1.90918,0.42334 -0.702803,0 -1.314294,-0.141114 -1.834473,-0.42334 -0.520184,-0.282226 -0.951824,-0.691731 -1.294922,-1.228516 -0.3431,-0.536782 -0.600424,-1.189776 -0.771972,-1.958984 -0.166016,-0.769202 -0.249024,-1.64355 -0.249024,-2.623047 0,-0.979485 0.07471,-1.8566 0.224121,-2.631348 0.154948,-0.77473 0.398437,-1.430491 0.730469,-1.967285 0.33203,-0.536772 0.760903,-0.946277 1.286621,-1.228515 0.525713,-0.2877487 1.162106,-0.4316287 1.90918,-0.431641 0.69726,1.23e-5 1.305984,0.1411254 1.826172,0.42334 0.520175,0.282238 0.954582,0.691743 1.303223,1.228515 0.348624,0.536794 0.608715,1.192555 0.780273,1.967286 0.171541,0.774747 0.257315,1.654629 0.257324,2.639648 m -5.760742,0 c -3e-6,1.383468 0.118975,2.423832 0.356934,3.121094 0.237952,0.6
97268 0.650223,1.0459 1.236816,1.045898 0.575516,2e-6 0.987787,-0.345863 1.236816,-1.037597 0.254552,-0.691729 0.38183,-1.734859 0.381836,-3.129395 -6e-6,-1.38899 -0.127284,-2.43212 -0.381836,-3.129395 -0.249029,-0.702789 -0.6613,-1.054188 -1.236816,-1.054199 -0.293299,1.1e-5 -0.542322,0.08855 -0.74707,0.265625 -0.199223,0.177093 -0.362471,0.439951 -0.489746,0.788574 -0.127282,0.348642 -0.218591,0.785816 -0.273926,1.311524 -0.05534,0.52019 -0.08301,1.126146 -0.08301,1.817871"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/31.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/31.png
new file mode 100644
index 0000000..0b29e87
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/31.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/31.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/31.svg
new file mode 100644
index 0000000..08c3f2d
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/31.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 22.579206,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141117,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168786,0.157724 -0.257324,0.240723 -0.08855,0.08302 -0.17432,0.157723 -0.257325,0.224121 l -1.394531,1.120605 -1.245117,-1.543945 3.909668,-3.1127931 2.108398,0 0,12.1357421"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/32.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/32.png
new file mode 100644
index 0000000..a4740a3
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/32.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/32.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/32.svg
new file mode 100644
index 0000000..aa099c3
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/32.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.621199,22.008438 -8.143067,0 0,-1.784668 2.855469,-3.07959 c 0.359697,-0.387364 0.686194,-0.744297 0.979492,-1.0708 0.29329,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373535,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437179,10e-6 -0.857751,0.10792 -1.261719,0.323731 -0.403974,0.215829 -0.827314,0.522958 -1.27002,0.921386 l -1.394531,-1.651855 c 0.249023,-0.226877 0.509114,-0.442698 0.780274,-0.647461 0.271157,-0.210275 0.569985,-0.395659 0.896484,-0.556152 0.326495,-0.16047 0.686195,-0.2877488 1.079101,-0.3818364 0.3929,-0.099597 0.832841,-0.1494018 1.319825,-0.1494141 0.581049,1.23e-5 1.101231,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860507,0.3901488 1.187011,0.6889648 0.32649,0.293305 0.575513,0.650239 0.747071,1.070801 0.177075,0.420583 0.265616,0.893727 0.265625,1.419
433 -9e-6,0.47592 -0.08302,0.932463 -0.249024,1.369629 -0.166024,0.431648 -0.392911,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622565,0.830083 -1.004394,1.245117 -0.376309,0.40951 -0.78028,0.827315 -1.211914,1.253418 l -1.460938,1.469238 0,0.116211 4.947266,0 0,2.158203"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/33.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/33.png
new file mode 100644
index 0000000..f23ccea
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/33.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/33.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/33.svg
new file mode 100644
index 0000000..fce979c
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/33.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.148054,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.207519,1.137207 -0.132821,0.33204 -0.318205,0.625334 -0.556153,0.879883 -0.232429,0.249031 -0.509121,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979486,0.121751 1.721021,0.420579 2.22461,0.896485 0.503572,0.470382 0.755362,1.106775 0.755371,1.909179 -9e-6,0.531253 -0.09685,1.023766 -0.290528,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879882,1.170411 -0.392911,0.332031 -0.890958,0.592122 -1.494141,0.780273 -0.597662,0.182617 -1.303227,0.273926 -2.116699,0.273926 -0.652998,0 -1.267256,-0.05534 -1.842774,-0.166016 -0.575522,-0.105143 -1.112305,-0.268392 -1.610351,-0.489746 l 0,-2.183105 c 0.249022,0.132815 0.51188,0.249025 0.788574,0.348632 0.276691,0.09961 0.553384,0.185387 0.830078,0.257325 0.27669,0.06641 0.547849,0.116212 0.813477,0.149414 0.271155,0.0332 0.525712,0.04981 0.763671,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132812 0.315425,
-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188146,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124512,-0.73877 -7e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.20474 -0.265631,-0.376289 -0.498047,-0.51464 -0.226893,-0.143876 -0.525721,-0.254553 -0.896485,-0.332032 -0.370772,-0.07747 -0.827315,-0.116205 -1.369628,-0.116211 l -0.863282,0 0,-1.801269 0.84668,0 c 0.509111,7e-6 0.93245,-0.04426 1.270019,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124512,-0.672363 -6e-6,-0.431632 -0.135585,-0.769197 -0.406739,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,1e-5 -0.514652,0.02768 -0.747071,0.08301 -0.226891,0.04981 -0.439944,0.116221 -0.63916,0.199218 -0.193687,0.07748 -0.373537,0.166026 -0.53955,0.265625 -0.160484,0.09409 -0.307131,0.188161 -0.439942,0.282227 l -1.294922,-1.7
09961 c 0.232421,-0.171538 0.484212,-0.329253 0.755371,-0.473145 0.276692,-0.143868 0.575519,-0.26838 0.896485,-0.373535 0.320961,-0.1106647 0.666826,-0.1964393 1.037597,-0.2573239 0.370765,-0.06086 0.766435,-0.091296 1.187012,-0.091309 0.597651,1.23e-5 1.139969,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/34.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/34.png
new file mode 100644
index 0000000..7e2ab31
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/34.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/34.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/34.svg
new file mode 100644
index 0000000..c67f8ec
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/34.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.803816,19.493301 -1.460938,0 0,2.515137 -2.498535,0 0,-2.515137 -5.013672,0 0,-1.784668 5.154785,-7.8359371 2.357422,0 0,7.6284181 1.460938,0 0,1.992187 m -3.959473,-1.992187 0,-2.058594 c -5e-6,-0.07193 -5e-6,-0.17431 0,-0.307129 0.0055,-0.138339 0.01106,-0.293287 0.0166,-0.464844 0.0055,-0.171541 0.01106,-0.348625 0.0166,-0.53125 0.01106,-0.182609 0.01936,-0.356925 0.0249,-0.522949 0.01106,-0.166007 0.01936,-0.309887 0.0249,-0.43164 0.01106,-0.12727 0.01936,-0.218579 0.0249,-0.273926 l -0.07471,0 c -0.09961,0.232431 -0.213058,0.478687 -0.340332,0.738769 -0.121749,0.2601 -0.262862,0.520191 -0.42334,0.780274 l -2.02539,3.071289 2.755859,0"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/35.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/35.png
new file mode 100644
index 0000000..02118e3
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/35.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/35.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/35.svg
new file mode 100644
index 0000000..da7780a
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/35.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 20.761335,14.255508 c 0.520177,8e-6 1.004389,0.08025 1.452637,0.240723 0.448235,0.160489 0.838372,0.395678 1.17041,0.705566 0.332024,0.309903 0.592114,0.697272 0.780274,1.16211 0.188142,0.459315 0.282218,0.987797 0.282226,1.585449 -8e-6,0.658532 -0.102385,1.250654 -0.307129,1.776367 -0.20476,0.520184 -0.506355,0.962892 -0.904785,1.328125 -0.398444,0.359701 -0.893724,0.636394 -1.48584,0.830078 -0.586594,0.193685 -1.261723,0.290528 -2.02539,0.290528 -0.304366,0 -0.605961,-0.01384 -0.904785,-0.0415 -0.298831,-0.02767 -0.586591,-0.06917 -0.863282,-0.124512 -0.27116,-0.04981 -0.531251,-0.116211 -0.780273,-0.199219 -0.243491,-0.08301 -0.464845,-0.17985 -0.664063,-0.290527 l 0,-2.216309 c 0.193684,0.11068 0.417805,0.215823 0.672364,0.31543 0.254555,0.09408 0.517413,0.177086 0.788574,0.249024 0.27669,0.06641 0.553383,0.121746 0.830078,0.166015 0.276689,0.03874 0.539547,0.05811 0.788574,0.05811 0.741532,2e-6 1.305985,-0.152179 1.69336,-0.456543 0.387364,-0.309893 0.581048
,-0.799639 0.581054,-1.469239 -6e-6,-0.597651 -0.190924,-1.051427 -0.572754,-1.361328 -0.376307,-0.315424 -0.960128,-0.473139 -1.751464,-0.473144 -0.143884,5e-6 -0.298832,0.0083 -0.464844,0.0249 -0.160485,0.01661 -0.320967,0.03874 -0.481446,0.06641 -0.15495,0.02768 -0.304364,0.05811 -0.448242,0.09131 -0.143882,0.02767 -0.268394,0.05811 -0.373535,0.09131 l -1.020996,-0.547852 0.456543,-6.1840821 6.408203,0 0,2.1748051 -4.183594,0 -0.199218,2.382324 c 0.177079,-0.03873 0.381832,-0.07747 0.614257,-0.116211 0.237952,-0.03873 0.542314,-0.0581 0.913086,-0.05811"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/36.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/36.png
new file mode 100644
index 0000000..30f4fdf
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/36.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/36.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/36.svg
new file mode 100644
index 0000000..348549a
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/36.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 16.428328,16.853653 c -1e-6,-0.581049 0.03044,-1.159336 0.09131,-1.734863 0.06641,-0.575514 0.17985,-1.126132 0.340332,-1.651856 0.166015,-0.531241 0.387369,-1.023753 0.664063,-1.477539 0.282224,-0.453765 0.636391,-0.846669 1.0625,-1.178711 0.431637,-0.337553 0.946285,-0.600411 1.543945,-0.788574 0.603185,-0.1936727 1.305984,-0.2905151 2.108398,-0.2905274 0.116205,1.23e-5 0.243483,0.00278 0.381836,0.0083 0.13834,0.00555 0.276686,0.013847 0.415039,0.024902 0.143873,0.00555 0.282219,0.016614 0.415039,0.033203 0.132805,0.016614 0.251783,0.035982 0.356934,0.058105 l 0,2.0502924 c -0.210294,-0.04979 -0.434415,-0.08853 -0.672363,-0.116211 -0.232429,-0.03319 -0.467618,-0.04979 -0.705567,-0.0498 -0.747076,1e-5 -1.361333,0.09408 -1.842773,0.282226 -0.48145,0.182627 -0.863285,0.439951 -1.145508,0.771973 -0.28223,0.33204 -0.484215,0.730477 -0.605957,1.195312 -0.116214,0.464852 -0.188154,0.9795 -0.21582,1.543946 l 0.09961,0 c 0.110674,-0.199212 0.243487,-0.384596 0.398438,-0
.556153 0.160478,-0.177076 0.345862,-0.32649 0.556152,-0.448242 0.210282,-0.127271 0.445471,-0.22688 0.705566,-0.298828 0.265621,-0.07193 0.561681,-0.107902 0.888184,-0.10791 0.52571,8e-6 0.998854,0.08578 1.419434,0.257324 0.420565,0.171557 0.774732,0.42058 1.0625,0.74707 0.293286,0.326504 0.517407,0.727708 0.672363,1.203614 0.154939,0.475916 0.232413,1.021 0.232422,1.635254 -9e-6,0.658532 -0.09408,1.247887 -0.282227,1.768066 -0.182625,0.520184 -0.445483,0.962892 -0.788574,1.328125 -0.343106,0.359701 -0.758145,0.636394 -1.245117,0.830078 -0.486985,0.188151 -1.034836,0.282227 -1.643555,0.282227 -0.59766,0 -1.156579,-0.105144 -1.676758,-0.31543 -0.520185,-0.21582 -0.97396,-0.542317 -1.361328,-0.979492 -0.381837,-0.437173 -0.683432,-0.987791 -0.904785,-1.651856 -0.215821,-0.669593 -0.323731,-1.460933 -0.32373,-2.374023 m 4.216796,3.270508 c 0.226883,2e-6 0.431636,-0.0415 0.614258,-0.124512 0.188146,-0.08854 0.348627,-0.218585 0.481446,-0.390137 0.13834,-0.17708 0.243483,-0.3984
34 0.315429,-0.664062 0.07747,-0.265622 0.116205,-0.581051 0.116211,-0.946289 -6e-6,-0.592118 -0.124518,-1.056961 -0.373535,-1.394531 -0.243495,-0.343094 -0.61703,-0.514643 -1.120605,-0.514649 -0.254562,6e-6 -0.486984,0.04981 -0.697266,0.149414 -0.21029,0.09962 -0.390141,0.229661 -0.539551,0.390137 -0.149417,0.160487 -0.265628,0.340337 -0.348633,0.539551 -0.07748,0.199223 -0.116214,0.401209 -0.116211,0.605957 -3e-6,0.28223 0.0332,0.564456 0.09961,0.846679 0.07194,0.276696 0.17708,0.528486 0.315429,0.755371 0.143877,0.221357 0.318193,0.401207 0.52295,0.539551 0.210282,0.138349 0.453771,0.207522 0.730468,0.20752"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/37.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/37.png
new file mode 100644
index 0000000..6174706
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/37.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/37.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/37.svg
new file mode 100644
index 0000000..7bc04d9
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/37.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 17.51573,22.008438 4.316406,-9.960937 -5.578125,0 0,-2.1582035 8.367188,0 0,1.6103515 -4.424317,10.508789 -2.681152,0"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/38.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/38.png
new file mode 100644
index 0000000..161661d
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/38.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/38.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/38.svg
new file mode 100644
index 0000000..ec2ad98
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/38.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 20.48741,9.7149811 c 0.503575,1.23e-5 0.979486,0.060885 1.427734,0.1826172 0.448236,0.1217567 0.841139,0.3043737 1.178711,0.5478517 0.337557,0.243501 0.605949,0.547862 0.805176,0.913086 0.19921,0.365244 0.298819,0.794118 0.298828,1.286621 -9e-6,0.365243 -0.05535,0.697274 -0.166016,0.996094 -0.110685,0.293302 -0.262866,0.561694 -0.456543,0.805175 -0.193692,0.237963 -0.423347,0.451017 -0.688965,0.639161 -0.265631,0.188157 -0.553392,0.359707 -0.863281,0.514648 0.320957,0.171556 0.63362,0.362473 0.937988,0.572754 0.309889,0.210292 0.583814,0.448247 0.821778,0.713867 0.237947,0.260096 0.428865,0.55339 0.572754,0.879883 0.143871,0.326501 0.215811,0.691735 0.21582,1.095703 -9e-6,0.503583 -0.09962,0.960126 -0.298828,1.369629 -0.199227,0.409506 -0.478687,0.758139 -0.838379,1.045898 -0.359708,0.287761 -0.791348,0.509115 -1.294922,0.664063 -0.498053,0.154948 -1.048671,0.232422 -1.651855,0.232422 -0.652999,0 -1.234053,-0.07471 -1.743164,-0.224121 -0.509117,-0.149414 -0.93799
1,-0.362467 -1.286622,-0.639161 -0.348634,-0.276691 -0.614258,-0.617023 -0.796875,-1.020996 -0.177084,-0.403969 -0.265625,-0.857744 -0.265625,-1.361328 0,-0.415035 0.06087,-0.78857 0.182618,-1.120605 0.121744,-0.332027 0.287759,-0.630855 0.498046,-0.896485 0.210285,-0.265619 0.456542,-0.500808 0.73877,-0.705566 0.282224,-0.204747 0.583819,-0.384597 0.904785,-0.539551 -0.271161,-0.171543 -0.525718,-0.356927 -0.763672,-0.556152 -0.237957,-0.204746 -0.445477,-0.428866 -0.622558,-0.672363 -0.171551,-0.249016 -0.309897,-0.522942 -0.415039,-0.821778 -0.09961,-0.298819 -0.149415,-0.628083 -0.149414,-0.987793 -1e-6,-0.481435 0.09961,-0.902008 0.298828,-1.261718 0.204751,-0.365224 0.478676,-0.669585 0.821777,-0.913086 0.343097,-0.249012 0.738767,-0.434396 1.187012,-0.5561527 0.448238,-0.1217326 0.918615,-0.1826049 1.411133,-0.1826172 m -1.718262,9.0644529 c -3e-6,0.221357 0.03597,0.42611 0.10791,0.614258 0.07194,0.18262 0.17708,0.340334 0.31543,0.473145 0.143876,0.132814 0.32096,0.23
7957 0.53125,0.315429 0.210282,0.07194 0.453771,0.107912 0.730468,0.10791 0.58105,2e-6 1.015457,-0.135577 1.303223,-0.406738 0.287754,-0.27669 0.431634,-0.639157 0.431641,-1.087402 -7e-6,-0.232419 -0.04981,-0.439938 -0.149414,-0.622559 -0.09408,-0.188147 -0.218594,-0.359696 -0.373535,-0.514648 -0.14942,-0.160478 -0.32097,-0.307125 -0.514649,-0.439942 -0.19369,-0.132807 -0.387375,-0.260086 -0.581055,-0.381836 L 20.3878,16.72084 c -0.243494,0.12175 -0.464848,0.254563 -0.664062,0.398438 -0.199223,0.138351 -0.370772,0.293299 -0.514649,0.464844 -0.138349,0.16602 -0.246259,0.348637 -0.32373,0.547851 -0.07748,0.199223 -0.116214,0.415043 -0.116211,0.647461 m 1.70166,-7.188476 c -0.182622,10e-6 -0.354171,0.02768 -0.514648,0.08301 -0.154952,0.05535 -0.290532,0.13559 -0.406739,0.240723 -0.11068,0.105153 -0.199222,0.235199 -0.265625,0.390137 -0.06641,0.154957 -0.09961,0.329274 -0.09961,0.522949 -3e-6,0.232431 0.0332,0.434416 0.09961,0.605957 0.07194,0.166024 0.166012,0.315438 0.282227,0
.448242 0.121741,0.127287 0.260087,0.243498 0.415039,0.348633 0.160477,0.09962 0.32926,0.199226 0.506348,0.298828 0.171544,-0.08853 0.334793,-0.185376 0.489746,-0.290527 0.154942,-0.105135 0.290522,-0.224113 0.406738,-0.356934 0.121739,-0.138338 0.218581,-0.293286 0.290527,-0.464843 0.07193,-0.171541 0.107904,-0.367993 0.10791,-0.589356 -6e-6,-0.193675 -0.03321,-0.367992 -0.09961,-0.522949 -0.06641,-0.154938 -0.15772,-0.284984 -0.273926,-0.390137 -0.116216,-0.105133 -0.254562,-0.185374 -0.415039,-0.240723 -0.160487,-0.05533 -0.334803,-0.083 -0.522949,-0.08301"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/39.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/39.png
new file mode 100644
index 0000000..2d46b24
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/39.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/39.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/39.svg
new file mode 100644
index 0000000..664ffdd
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/39.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.554792,15.052383 c -8e-6,0.581061 -0.03321,1.162116 -0.09961,1.743164 -0.06088,0.575526 -0.174325,1.126144 -0.340332,1.651856 -0.16049,0.525719 -0.381844,1.018232 -0.664063,1.477539 -0.2767,0.453778 -0.630866,0.846681 -1.0625,1.178711 -0.426112,0.332032 -0.94076,0.59489 -1.543945,0.788574 -0.597661,0.188151 -1.300459,0.282227 -2.108398,0.282227 -0.116214,0 -0.243493,-0.0028 -0.381836,-0.0083 -0.138349,-0.0055 -0.279462,-0.01384 -0.42334,-0.0249 -0.138348,-0.0055 -0.273928,-0.0166 -0.406738,-0.0332 -0.132814,-0.01107 -0.249025,-0.02767 -0.348633,-0.0498 l 0,-2.058594 c 0.204751,0.05534 0.423338,0.09961 0.655762,0.132813 0.237953,0.02767 0.478675,0.04151 0.722168,0.0415 0.747066,2e-6 1.361324,-0.09131 1.842773,-0.273925 0.48144,-0.188149 0.863276,-0.44824 1.145508,-0.780274 0.28222,-0.337562 0.481439,-0.738766 0.597656,-1.203613 0.121738,-0.464839 0.196445,-0.97672 0.224121,-1.535645 l -0.10791,0 c -0.110683,0.199225 -0.243496,0.384609 -0.398438,0.556153 -0.1549
53,0.171554 -0.33757,0.320968 -0.547851,0.448242 -0.210292,0.127283 -0.448247,0.226892 -0.713867,0.298828 -0.26563,0.07194 -0.561691,0.107914 -0.888184,0.10791 -0.525719,4e-6 -0.998863,-0.08577 -1.419433,-0.257324 -0.420575,-0.171545 -0.777509,-0.420568 -1.070801,-0.74707 -0.287762,-0.326492 -0.509116,-0.727696 -0.664063,-1.203614 -0.154948,-0.475904 -0.232422,-1.020988 -0.232422,-1.635253 0,-0.65852 0.09131,-1.247875 0.273926,-1.768067 0.18815,-0.520172 0.453775,-0.960113 0.796875,-1.319824 0.343097,-0.365223 0.758136,-0.644682 1.245117,-0.838379 0.49251,-0.1936727 1.043128,-0.2905151 1.651856,-0.2905274 0.597651,1.23e-5 1.15657,0.1079224 1.676758,0.3237304 0.520175,0.210298 0.971184,0.534028 1.353027,0.971192 0.381828,0.437185 0.683423,0.990569 0.904785,1.660156 0.221346,0.669605 0.332023,1.458178 0.332031,2.365722 m -4.216796,-3.262207 c -0.226893,1.1e-5 -0.434412,0.04151 -0.622559,0.124512 -0.188155,0.08302 -0.351403,0.213063 -0.489746,0.390137 -0.132816,0.171559 -0.2379
59,0.392913 -0.31543,0.664062 -0.07194,0.265634 -0.107913,0.581063 -0.10791,0.946289 -3e-6,0.586596 0.124509,1.05144 0.373535,1.394532 0.24902,0.343105 0.625322,0.514654 1.128906,0.514648 0.254553,6e-6 0.486975,-0.0498 0.697266,-0.149414 0.210281,-0.0996 0.390131,-0.229648 0.539551,-0.390137 0.149408,-0.160475 0.262852,-0.340325 0.340332,-0.53955 0.083,-0.199212 0.124505,-0.401197 0.124512,-0.605958 -7e-6,-0.282218 -0.03598,-0.561677 -0.107911,-0.838378 -0.06641,-0.282218 -0.171555,-0.534008 -0.315429,-0.755372 -0.138352,-0.226878 -0.312669,-0.409495 -0.52295,-0.547851 -0.204757,-0.138336 -0.44548,-0.207509 -0.722167,-0.20752"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/4.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/4.png
new file mode 100644
index 0000000..9b9dd88
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/4.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/4.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/4.svg
new file mode 100644
index 0000000..bc06c73
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/4.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;text-anchor:start;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 20.078077,19.493301 -1.460937,0 0,2.515137 -2.498535,0 0,-2.515137 -5.013672,0 0,-1.784668 5.154785,-7.8359371 2.357422,0 0,7.6284181 1.460937,0 0,1.992187 m -3.959472,-1.992187 0,-2.058594 c -5e-6,-0.07193 -5e-6,-0.17431 0,-0.307129 0.0055,-0.138339 0.01106,-0.293287 0.0166,-0.464844 0.0055,-0.171541 0.01106,-0.348625 0.0166,-0.53125 0.01106,-0.182609 0.01936,-0.356925 0.0249,-0.522949 0.01106,-0.166007 0.01936,-0.309887 0.0249,-0.43164 0.01106,-0.12727 0.01936,-0.218579 0.0249,-0.273926 l -0.07471,0 c -0.09962,0.232431 -0.213058,0.478687 -0.340332,0.738769 -0.12175,0.2601 -0.262863,0.520191 -0.42334,0.780274 l -2.025391,3.071289 2.75586,0"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/40.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/40.png
new file mode 100644
index 0000000..fe2a68f
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/40.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/40.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/40.svg
new file mode 100644
index 0000000..5a94d1b
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/40.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.440535,19.493301 -1.460938,0 0,2.515137 -2.498535,0 0,-2.515137 -5.0136719,0 0,-1.784668 5.1547849,-7.8359371 2.357422,0 0,7.6284181 1.460938,0 0,1.992187 m -3.959473,-1.992187 0,-2.058594 c -5e-6,-0.07193 -5e-6,-0.17431 0,-0.307129 0.0055,-0.138339 0.01106,-0.293287 0.0166,-0.464844 0.0055,-0.171541 0.01106,-0.348625 0.0166,-0.53125 0.01106,-0.182609 0.01936,-0.356925 0.0249,-0.522949 0.01106,-0.166007 0.01936,-0.309887 0.0249,-0.43164 0.01106,-0.12727 0.01936,-0.218579 0.0249,-0.273926 l -0.07471,0 c -0.09961,0.232431 -0.213058,0.478687 -0.340332,0.738769 -0.121749,0.2601 -0.262863,0.520191 -0.42334,0.780274 l -2.0253904,3.071289 2.7558594,0"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.6378,15.940567 c -9e-6,0.979497 -0.07748,1.853845 -0.232422,2.623047 -0.149422,0.769208 -0.392912,1.422202 -0.730468,1.958984 -0.332039,0.536785 -0.763679,0.94629 -1.294922,1.228516 -0.525722,0.282226 -1.162115,0.42334 -1.90918,0.42334 -0.702803,0 -1.314294,-0.141114 -1.834473,-0.42334 -0.520184,-0.282226 -0.951824,-0.691731 -1.294922,-1.228516 -0.3431,-0.536782 -0.600424,-1.189776 -0.771972,-1.958984 -0.166016,-0.769202 -0.249024,-1.64355 -0.249024,-2.623047 0,-0.979485 0.07471,-1.8566 0.224121,-2.631348 0.154948,-0.77473 0.398437,-1.430491 0.730469,-1.967285 0.33203,-0.536772 0.760903,-0.946277 1.286621,-1.228515 0.525713,-0.2877487 1.162106,-0.4316287 1.90918,-0.431641 0.69726,1.23e-5 1.305984,0.1411254 1.826172,0.42334 0.520175,0.282238 0.954582,0.691743 1.303223,1.228515 0.348624,0.536794 0.608715,1.192555 0.780273,1.967286 0.171541,0.774747 0.257315,1.654629 0.257324,2.639648 m -5.760742,0 c -3e-6,1.383468 0.118975,2.423832 0.356934,3.121094 0.237952,0.6
97268 0.650223,1.0459 1.236816,1.045898 0.575516,2e-6 0.987787,-0.345863 1.236816,-1.037597 0.254552,-0.691729 0.38183,-1.734859 0.381836,-3.129395 -6e-6,-1.38899 -0.127284,-2.43212 -0.381836,-3.129395 -0.249029,-0.702789 -0.6613,-1.054188 -1.236816,-1.054199 -0.293299,1.1e-5 -0.542322,0.08855 -0.74707,0.265625 -0.199223,0.177093 -0.362471,0.439951 -0.489746,0.788574 -0.127282,0.348642 -0.218591,0.785816 -0.273926,1.311524 -0.05534,0.52019 -0.08301,1.126146 -0.08301,1.817871"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/5.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/5.png
new file mode 100644
index 0000000..f239fb6
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/5.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/5.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/5.svg
new file mode 100644
index 0000000..82fb03d
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/5.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;text-anchor:start;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 16.035597,14.255508 c 0.520177,8e-6 1.004388,0.08025 1.452637,0.240723 0.448235,0.160489 0.838371,0.395678 1.17041,0.705566 0.332023,0.309903 0.592114,0.697272 0.780273,1.16211 0.188143,0.459315 0.282218,0.987797 0.282227,1.585449 -9e-6,0.658532 -0.102385,1.250654 -0.307129,1.776367 -0.204761,0.520184 -0.506356,0.962892 -0.904785,1.328125 -0.398445,0.359701 -0.893724,0.636394 -1.48584,0.830078 -0.586594,0.193685 -1.261724,0.290528 -2.025391,0.290528 -0.304365,0 -0.60596,-0.01384 -0.904785,-0.0415 -0.298831,-0.02767 -0.586591,-0.06917 -0.863281,-0.124512 -0.271161,-0.04981 -0.531252,-0.116211 -0.780274,-0.199219 -0.24349,-0.08301 -0.464844,-0.17985 -0.664062,-0.290527 l 0,-2.216309 c 0.193684,0.11068 0.417805,0.215823 0.672363,0.31543 0.254556,0.09408 0.517414,0.177086 0.788574,0.249024 0.276691,0.06641 0.553383,0.121746 0.830078,0.166015 0.27669,0.03874 0.539548,0.05811 0.788575,0.05811 0.741532,2e-6 1.305984,-0.152179 1.693359,-0.456543 0.387364,-0.309893 0.5810
49,-0.799639 0.581055,-1.469239 -6e-6,-0.597651 -0.190924,-1.051427 -0.572754,-1.361328 -0.376307,-0.315424 -0.960128,-0.473139 -1.751465,-0.473144 -0.143884,5e-6 -0.298832,0.0083 -0.464844,0.0249 -0.160485,0.01661 -0.320966,0.03874 -0.481445,0.06641 -0.154951,0.02768 -0.304365,0.05811 -0.448242,0.09131 -0.143883,0.02767 -0.268394,0.05811 -0.373535,0.09131 l -1.020996,-0.547852 0.456542,-6.1840821 6.408204,0 0,2.1748051 -4.183594,0 -0.199219,2.382324 c 0.17708,-0.03873 0.381832,-0.07747 0.614258,-0.116211 0.237951,-0.03873 0.542313,-0.0581 0.913086,-0.05811"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/6.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/6.png
new file mode 100644
index 0000000..18866e6
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/6.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/6.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/6.svg
new file mode 100644
index 0000000..e2f62af
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/6.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;text-anchor:start;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 11.702589,16.853653 c -10e-7,-0.581049 0.03044,-1.159336 0.09131,-1.734863 0.0664,-0.575514 0.179849,-1.126132 0.340332,-1.651856 0.166014,-0.531241 0.387368,-1.023753 0.664062,-1.477539 0.282225,-0.453765 0.636391,-0.846669 1.0625,-1.178711 0.431638,-0.337553 0.946285,-0.600411 1.543945,-0.788574 0.603186,-0.1936727 1.305984,-0.2905151 2.108399,-0.2905274 0.116204,1.23e-5 0.243483,0.00278 0.381836,0.0083 0.138339,0.00555 0.276685,0.013847 0.415039,0.024902 0.143873,0.00555 0.282219,0.016614 0.415039,0.033203 0.132805,0.016614 0.251782,0.035982 0.356934,0.058105 l 0,2.0502924 c -0.210295,-0.04979 -0.434416,-0.08853 -0.672364,-0.116211 -0.232429,-0.03319 -0.467617,-0.04979 -0.705566,-0.0498 -0.747076,1e-5 -1.361334,0.09408 -1.842774,0.282226 -0.481449,0.182627 -0.863285,0.439951 -1.145507,0.771973 -0.28223,0.33204 -0.484216,0.730477 -0.605957,1.195312 -0.116214,0.464852 -0.188154,0.9795 -0.215821,1.543946 l 0.09961,0 c 0.110674,-0.199212 0.243486,-0.384596 0.39843
7,-0.556153 0.160478,-0.177076 0.345862,-0.32649 0.556153,-0.448242 0.210282,-0.127271 0.44547,-0.22688 0.705566,-0.298828 0.26562,-0.07193 0.561681,-0.107902 0.888184,-0.10791 0.52571,8e-6 0.998854,0.08578 1.419433,0.257324 0.420566,0.171557 0.774732,0.42058 1.0625,0.74707 0.293286,0.326504 0.517407,0.727708 0.672363,1.203614 0.15494,0.475916 0.232413,1.021 0.232422,1.635254 -9e-6,0.658532 -0.09408,1.247887 -0.282226,1.768066 -0.182626,0.520184 -0.445484,0.962892 -0.788575,1.328125 -0.343106,0.359701 -0.758145,0.636394 -1.245117,0.830078 -0.486985,0.188151 -1.034836,0.282227 -1.643554,0.282227 -0.597661,0 -1.15658,-0.105144 -1.676758,-0.31543 -0.520185,-0.21582 -0.973961,-0.542317 -1.361328,-0.979492 -0.381838,-0.437173 -0.683433,-0.987791 -0.904785,-1.651856 -0.215822,-0.669593 -0.323732,-1.460933 -0.323731,-2.374023 m 4.216797,3.270508 c 0.226883,2e-6 0.431635,-0.0415 0.614258,-0.124512 0.188145,-0.08854 0.348627,-0.218585 0.481445,-0.390137 0.13834,-0.17708 0.243483,-0.3
98434 0.31543,-0.664062 0.07747,-0.265622 0.116204,-0.581051 0.116211,-0.946289 -7e-6,-0.592118 -0.124518,-1.056961 -0.373535,-1.394531 -0.243496,-0.343094 -0.617031,-0.514643 -1.120606,-0.514649 -0.254562,6e-6 -0.486984,0.04981 -0.697266,0.149414 -0.21029,0.09962 -0.39014,0.229661 -0.53955,0.390137 -0.149418,0.160487 -0.265629,0.340337 -0.348633,0.539551 -0.07748,0.199223 -0.116214,0.401209 -0.116211,0.605957 -3e-6,0.28223 0.0332,0.564456 0.09961,0.846679 0.07194,0.276696 0.17708,0.528486 0.31543,0.755371 0.143876,0.221357 0.318193,0.401207 0.522949,0.539551 0.210282,0.138349 0.453772,0.207522 0.730469,0.20752"
+ id="path2846"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/7.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/7.png
new file mode 100644
index 0000000..52c3a18
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/7.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/7.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/7.svg
new file mode 100644
index 0000000..a43460f
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/7.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;text-anchor:start;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 12.789991,22.008438 4.316407,-9.960937 -5.578125,0 0,-2.1582035 8.367187,0 0,1.6103515 -4.424316,10.508789 -2.681153,0"
+ id="path2832"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/8.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/8.png
new file mode 100644
index 0000000..8a8cb21
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/8.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/8.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/8.svg
new file mode 100644
index 0000000..2c82d3f
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/8.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;text-anchor:start;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.761671,9.7149811 c 0.503576,1.23e-5 0.979487,0.060885 1.427734,0.1826172 0.448236,0.1217567 0.841139,0.3043737 1.178711,0.5478517 0.337558,0.243501 0.60595,0.547862 0.805176,0.913086 0.199211,0.365244 0.29882,0.794118 0.298828,1.286621 -8e-6,0.365243 -0.05535,0.697274 -0.166015,0.996094 -0.110686,0.293302 -0.262866,0.561694 -0.456543,0.805175 -0.193693,0.237963 -0.423348,0.451017 -0.688965,0.639161 -0.265632,0.188157 -0.553392,0.359707 -0.863281,0.514648 0.320957,0.171556 0.633619,0.362473 0.937988,0.572754 0.309888,0.210292 0.583814,0.448247 0.821777,0.713867 0.237948,0.260096 0.428866,0.55339 0.572754,0.879883 0.143872,0.326501 0.215812,0.691735 0.21582,1.095703 -8e-6,0.503583 -0.09962,0.960126 -0.298828,1.369629 -0.199227,0.409506 -0.478686,0.758139 -0.838379,1.045898 -0.359707,0.287761 -0.791348,0.509115 -1.294921,0.664063 -0.498053,0.154948 -1.048671,0.232422 -1.651856,0.232422 -0.652999,0 -1.234053,-0.07471 -1.743164,-0.224121 -0.509117,-0.149414 -0.9379
9,-0.362467 -1.286621,-0.639161 -0.348634,-0.276691 -0.614259,-0.617023 -0.796875,-1.020996 -0.177084,-0.403969 -0.265626,-0.857744 -0.265625,-1.361328 -10e-7,-0.415035 0.06087,-0.78857 0.182617,-1.120605 0.121744,-0.332027 0.287759,-0.630855 0.498047,-0.896485 0.210285,-0.265619 0.456541,-0.500808 0.73877,-0.705566 0.282224,-0.204747 0.583819,-0.384597 0.904785,-0.539551 -0.271162,-0.171543 -0.525719,-0.356927 -0.763672,-0.556152 -0.237958,-0.204746 -0.445477,-0.428866 -0.622559,-0.672363 -0.171551,-0.249016 -0.309897,-0.522942 -0.415039,-0.821778 -0.09961,-0.298819 -0.149415,-0.628083 -0.149414,-0.987793 -10e-7,-0.481435 0.09961,-0.902008 0.298828,-1.261718 0.204751,-0.365224 0.478677,-0.669585 0.821778,-0.913086 0.343096,-0.249012 0.738766,-0.434396 1.187011,-0.5561527 0.448239,-0.1217326 0.918616,-0.1826049 1.411133,-0.1826172 m -1.718262,9.0644529 c -3e-6,0.221357 0.03597,0.42611 0.107911,0.614258 0.07194,0.18262 0.17708,0.340334 0.315429,0.473145 0.143877,0.132814 0.32
096,0.237957 0.53125,0.315429 0.210283,0.07194 0.453772,0.107912 0.730469,0.10791 0.581049,2e-6 1.015457,-0.135577 1.303223,-0.406738 0.287754,-0.27669 0.431634,-0.639157 0.43164,-1.087402 -6e-6,-0.232419 -0.04981,-0.439938 -0.149414,-0.622559 -0.09408,-0.188147 -0.218593,-0.359696 -0.373535,-0.514648 -0.14942,-0.160478 -0.320969,-0.307125 -0.514648,-0.439942 -0.19369,-0.132807 -0.387375,-0.260086 -0.581055,-0.381836 L 15.662062,16.72084 c -0.243494,0.12175 -0.464848,0.254563 -0.664063,0.398438 -0.199222,0.138351 -0.370772,0.293299 -0.514648,0.464844 -0.13835,0.16602 -0.24626,0.348637 -0.323731,0.547851 -0.07748,0.199223 -0.116214,0.415043 -0.116211,0.647461 m 1.701661,-7.188476 c -0.182622,10e-6 -0.354171,0.02768 -0.514649,0.08301 -0.154952,0.05535 -0.290531,0.13559 -0.406738,0.240723 -0.110681,0.105153 -0.199223,0.235199 -0.265625,0.390137 -0.06641,0.154957 -0.09961,0.329274 -0.09961,0.522949 -3e-6,0.232431 0.0332,0.434416 0.09961,0.605957 0.07194,0.166024 0.166012,0.31543
8 0.282226,0.448242 0.121741,0.127287 0.260087,0.243498 0.415039,0.348633 0.160478,0.09962 0.32926,0.199226 0.506348,0.298828 0.171545,-0.08853 0.334793,-0.185376 0.489746,-0.290527 0.154943,-0.105135 0.290522,-0.224113 0.406738,-0.356934 0.12174,-0.138338 0.218582,-0.293286 0.290528,-0.464843 0.07193,-0.171541 0.107904,-0.367993 0.10791,-0.589356 -6e-6,-0.193675 -0.03321,-0.367992 -0.09961,-0.522949 -0.06641,-0.154938 -0.157721,-0.284984 -0.273926,-0.390137 -0.116217,-0.105133 -0.254563,-0.185374 -0.415039,-0.240723 -0.160487,-0.05533 -0.334803,-0.083 -0.522949,-0.08301"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/9.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/9.png
new file mode 100644
index 0000000..0ae412f
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/9.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/9.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/9.svg
new file mode 100644
index 0000000..b0f04c4
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/9.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;text-anchor:start;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 19.829054,15.052383 c -9e-6,0.581061 -0.03321,1.162116 -0.09961,1.743164 -0.06088,0.575526 -0.174325,1.126144 -0.340333,1.651856 -0.160489,0.525719 -0.381843,1.018232 -0.664062,1.477539 -0.2767,0.453778 -0.630866,0.846681 -1.0625,1.178711 -0.426113,0.332032 -0.940761,0.59489 -1.543945,0.788574 -0.597661,0.188151 -1.30046,0.282227 -2.108399,0.282227 -0.116214,0 -0.243492,-0.0028 -0.381836,-0.0083 -0.138348,-0.0055 -0.279462,-0.01384 -0.42334,-0.0249 -0.138348,-0.0055 -0.273927,-0.0166 -0.406738,-0.0332 -0.132814,-0.01107 -0.249025,-0.02767 -0.348633,-0.0498 l 0,-2.058594 c 0.204751,0.05534 0.423338,0.09961 0.655762,0.132813 0.237954,0.02767 0.478676,0.04151 0.722168,0.0415 0.747067,2e-6 1.361324,-0.09131 1.842773,-0.273925 0.481441,-0.188149 0.863276,-0.44824 1.145508,-0.780274 0.282221,-0.337562 0.481439,-0.738766 0.597657,-1.203613 0.121738,-0.464839 0.196445,-0.97672 0.224121,-1.535645 l -0.107911,0 c -0.110683,0.199225 -0.243495,0.384609 -0.398437,0.556153 -0.
154954,0.171554 -0.337571,0.320968 -0.547852,0.448242 -0.210291,0.127283 -0.448247,0.226892 -0.713867,0.298828 -0.265629,0.07194 -0.56169,0.107914 -0.888183,0.10791 -0.52572,4e-6 -0.998864,-0.08577 -1.419434,-0.257324 -0.420575,-0.171545 -0.777508,-0.420568 -1.070801,-0.74707 -0.287761,-0.326492 -0.509115,-0.727696 -0.664062,-1.203614 -0.154949,-0.475904 -0.232423,-1.020988 -0.232422,-1.635253 -10e-7,-0.65852 0.09131,-1.247875 0.273926,-1.768067 0.18815,-0.520172 0.453774,-0.960113 0.796875,-1.319824 0.343097,-0.365223 0.758135,-0.644682 1.245117,-0.838379 0.49251,-0.1936727 1.043127,-0.2905151 1.651855,-0.2905274 0.597651,1.23e-5 1.15657,0.1079224 1.676758,0.3237304 0.520176,0.210298 0.971184,0.534028 1.353027,0.971192 0.381829,0.437185 0.683423,0.990569 0.904786,1.660156 0.221345,0.669605 0.332022,1.458178 0.332031,2.365722 m -4.216797,-3.262207 c -0.226892,1.1e-5 -0.434412,0.04151 -0.622559,0.124512 -0.188154,0.08302 -0.351403,0.213063 -0.489746,0.390137 -0.132815,0.17155
9 -0.237959,0.392913 -0.315429,0.664062 -0.07194,0.265634 -0.107914,0.581063 -0.107911,0.946289 -3e-6,0.586596 0.124509,1.05144 0.373536,1.394532 0.249019,0.343105 0.625321,0.514654 1.128906,0.514648 0.254552,6e-6 0.486974,-0.0498 0.697266,-0.149414 0.210281,-0.0996 0.390131,-0.229648 0.53955,-0.390137 0.149408,-0.160475 0.262852,-0.340325 0.340332,-0.53955 0.083,-0.199212 0.124506,-0.401197 0.124512,-0.605958 -6e-6,-0.282218 -0.03598,-0.561677 -0.10791,-0.838378 -0.06641,-0.282218 -0.171556,-0.534008 -0.31543,-0.755372 -0.138352,-0.226878 -0.312668,-0.409495 -0.522949,-0.547851 -0.204758,-0.138336 -0.44548,-0.207509 -0.722168,-0.20752"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/bkgrnd_greydots.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/bkgrnd_greydots.png
new file mode 100644
index 0000000..2333a6d
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/bkgrnd_greydots.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/bullet_arrowblue.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/bullet_arrowblue.png
new file mode 100644
index 0000000..c235534
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/bullet_arrowblue.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/documentation.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/documentation.png
new file mode 100644
index 0000000..79d0a80
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/documentation.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/dot.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/dot.png
new file mode 100644
index 0000000..36a6859
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/dot.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/dot2.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/dot2.png
new file mode 100644
index 0000000..40aff92
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/dot2.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/green.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/green.png
new file mode 100644
index 0000000..ebb3c24
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/green.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/h1-bg.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/h1-bg.png
new file mode 100644
index 0000000..a2aad24
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/h1-bg.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/image_left.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/image_left.png
new file mode 100644
index 0000000..e8fe7a4
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/image_left.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/image_right.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/image_right.png
new file mode 100644
index 0000000..5b67443
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/image_right.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/important.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/important.png
new file mode 100644
index 0000000..f7594a3
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/important.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/important.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/important.svg
new file mode 100644
index 0000000..2d33045
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/important.svg
@@ -0,0 +1,106 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:dc="http://purl.org/dc/elements/1.1/"
+ xmlns:cc="http://creativecommons.org/ns#"
+ xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd"
+ xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
+ version="1.0"
+ width="48"
+ height="48"
+ id="svg5921"
+ sodipodi:version="0.32"
+ inkscape:version="0.46"
+ sodipodi:docname="important.svg"
+ inkscape:output_extension="org.inkscape.output.svg.inkscape"
+ inkscape:export-filename="/home/jfearn/Build/src/fedora/publican/trunk/publican-fedora/en-US/images/important.png"
+ inkscape:export-xdpi="111.32"
+ inkscape:export-ydpi="111.32">
+ <metadata
+ id="metadata2611">
+ <rdf:RDF>
+ <cc:Work
+ rdf:about="">
+ <dc:format>image/svg+xml</dc:format>
+ <dc:type
+ rdf:resource="http://purl.org/dc/dcmitype/StillImage" />
+ </cc:Work>
+ </rdf:RDF>
+ </metadata>
+ <sodipodi:namedview
+ inkscape:window-height="681"
+ inkscape:window-width="738"
+ inkscape:pageshadow="2"
+ inkscape:pageopacity="0.0"
+ guidetolerance="10.0"
+ gridtolerance="10.0"
+ objecttolerance="10.0"
+ borderopacity="1.0"
+ bordercolor="#666666"
+ pagecolor="#ffffff"
+ id="base"
+ showgrid="false"
+ inkscape:zoom="11.5"
+ inkscape:cx="20"
+ inkscape:cy="20"
+ inkscape:window-x="0"
+ inkscape:window-y="51"
+ inkscape:current-layer="svg5921" />
+ <defs
+ id="defs5923">
+ <inkscape:perspective
+ sodipodi:type="inkscape:persp3d"
+ inkscape:vp_x="0 : 20 : 1"
+ inkscape:vp_y="0 : 1000 : 0"
+ inkscape:vp_z="40 : 20 : 1"
+ inkscape:persp3d-origin="20 : 13.333333 : 1"
+ id="perspective2613" />
+ </defs>
+ <g
+ transform="matrix(0.4626799,0,0,0.4626799,-5.2934127,-3.3160376)"
+ id="g5485">
+ <path
+ d="M 29.97756,91.885882 L 55.586992,80.409826 L 81.231619,91.807015 L 78.230933,63.90468 L 96.995009,43.037218 L 69.531053,37.26873 L 55.483259,12.974592 L 41.510292,37.311767 L 14.064204,43.164717 L 32.892392,63.97442 L 29.97756,91.885882 z"
+ id="path6799"
+ style="fill:#f3de82;fill-opacity:1;enable-background:new" />
+ <path
+ d="M 55.536215,56.538729 L 55.48324,12.974601 L 41.51028,37.311813 L 55.536215,56.538729 z"
+ id="path6824"
+ style="opacity:0.91005291;fill:#f9f2cb;fill-opacity:1;enable-background:new" />
+ <path
+ d="M 55.57947,56.614318 L 78.241135,63.937979 L 96.976198,43.044318 L 55.57947,56.614318 z"
+ id="use6833"
+ style="opacity:1;fill:#d0bc64;fill-opacity:1;enable-background:new" />
+ <path
+ d="M 55.523838,56.869126 L 55.667994,80.684281 L 81.379011,91.931065 L 55.523838,56.869126 z"
+ id="use6835"
+ style="opacity:1;fill:#e0c656;fill-opacity:1;enable-background:new" />
+ <path
+ d="M 55.283346,56.742618 L 13.877363,43.200977 L 32.640089,64.069652 L 55.283346,56.742618 z"
+ id="use6831"
+ style="opacity:1;fill:#d1ba59;fill-opacity:1;enable-background:new" />
+ <path
+ d="M 55.472076,56.869126 L 55.32792,80.684281 L 29.616903,91.931065 L 55.472076,56.869126 z"
+ id="use6837"
+ style="opacity:1;fill:#d2b951;fill-opacity:1;enable-background:new" />
+ <path
+ d="M 55.57947,56.614318 L 96.976198,43.044318 L 69.504294,37.314027 L 55.57947,56.614318 z"
+ id="path7073"
+ style="opacity:1;fill:#f6e7a3;fill-opacity:1;enable-background:new" />
+ <path
+ d="M 55.523838,56.869126 L 81.379011,91.931065 L 78.214821,64.046881 L 55.523838,56.869126 z"
+ id="path7075"
+ style="opacity:1;fill:#f6e7a3;fill-opacity:1;enable-background:new" />
+ <path
+ d="M 55.283346,56.742618 L 41.341708,37.434209 L 13.877363,43.200977 L 55.283346,56.742618 z"
+ id="path7077"
+ style="opacity:1;fill:#f6e59d;fill-opacity:1;enable-background:new" />
+ <path
+ d="M 55.472076,56.869126 L 29.616903,91.931065 L 32.781093,64.046881 L 55.472076,56.869126 z"
+ id="path7079"
+ style="opacity:1;fill:#f3df8b;fill-opacity:1;enable-background:new" />
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/logo.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/logo.png
new file mode 100644
index 0000000..66a3104
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/logo.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/note.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/note.png
new file mode 100644
index 0000000..d6c4518
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/note.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/note.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/note.svg
new file mode 100644
index 0000000..70e43b6
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/note.svg
@@ -0,0 +1,111 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:dc="http://purl.org/dc/elements/1.1/"
+ xmlns:cc="http://creativecommons.org/ns#"
+ xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd"
+ xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
+ version="1.0"
+ width="48"
+ height="48"
+ id="svg5921"
+ sodipodi:version="0.32"
+ inkscape:version="0.46"
+ sodipodi:docname="note.svg"
+ inkscape:output_extension="org.inkscape.output.svg.inkscape"
+ inkscape:export-filename="/home/jfearn/Build/src/fedora/publican/trunk/publican-fedora/en-US/images/note.png"
+ inkscape:export-xdpi="111.32"
+ inkscape:export-ydpi="111.32">
+ <metadata
+ id="metadata16">
+ <rdf:RDF>
+ <cc:Work
+ rdf:about="">
+ <dc:format>image/svg+xml</dc:format>
+ <dc:type
+ rdf:resource="http://purl.org/dc/dcmitype/StillImage" />
+ </cc:Work>
+ </rdf:RDF>
+ </metadata>
+ <sodipodi:namedview
+ inkscape:window-height="1024"
+ inkscape:window-width="1205"
+ inkscape:pageshadow="2"
+ inkscape:pageopacity="0.0"
+ guidetolerance="10.0"
+ gridtolerance="10.0"
+ objecttolerance="10.0"
+ borderopacity="1.0"
+ bordercolor="#666666"
+ pagecolor="#ffffff"
+ id="base"
+ showgrid="false"
+ inkscape:zoom="11.5"
+ inkscape:cx="22.217181"
+ inkscape:cy="20"
+ inkscape:window-x="334"
+ inkscape:window-y="51"
+ inkscape:current-layer="svg5921" />
+ <defs
+ id="defs5923">
+ <inkscape:perspective
+ sodipodi:type="inkscape:persp3d"
+ inkscape:vp_x="0 : 20 : 1"
+ inkscape:vp_y="0 : 1000 : 0"
+ inkscape:vp_z="40 : 20 : 1"
+ inkscape:persp3d-origin="20 : 13.333333 : 1"
+ id="perspective18" />
+ </defs>
+ <g
+ transform="matrix(0.468275,0,0,0.468275,-5.7626904,-7.4142703)"
+ id="layer1">
+ <g
+ transform="matrix(0.115136,0,0,0.115136,9.7283,21.77356)"
+ id="g8014"
+ style="enable-background:new">
+ <g
+ id="g8518"
+ style="opacity:1">
+ <path
+ d="M -2512.4524,56.33197 L 3090.4719,56.33197 L 3090.4719,4607.3813 L -2512.4524,4607.3813 L -2512.4524,56.33197 z"
+ transform="matrix(0.1104659,-2.3734892e-2,2.2163258e-2,0.1031513,308.46782,74.820675)"
+ id="rect8018"
+ style="fill:#ffe680;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.1;stroke-linecap:butt;stroke-miterlimit:4;stroke-dashoffset:0;stroke-opacity:1" />
+ </g>
+ <g
+ transform="matrix(0.5141653,-7.1944682e-2,7.1944682e-2,0.5141653,146.04015,-82.639785)"
+ id="g8020">
+ <path
+ d="M 511.14114,441.25315 C 527.3248,533.52772 464.31248,622.82928 370.39916,640.71378 C 276.48584,658.59828 187.23462,598.29322 171.05095,506.01865 C 154.86728,413.74408 217.8796,324.44253 311.79292,306.55803 C 405.70624,288.67353 494.95747,348.97858 511.14114,441.25315 z"
+ id="path8022"
+ style="opacity:1;fill:#e0c96f;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.0804934;stroke-linecap:butt;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1" />
+ <path
+ d="M 527.8214,393.1416 C 527.8214,461.31268 472.55783,516.57625 404.38675,516.57625 C 336.21567,516.57625 280.9521,461.31268 280.9521,393.1416 C 280.9521,324.97052 336.21567,269.70695 404.38675,269.70695 C 472.55783,269.70695 527.8214,324.97052 527.8214,393.1416 z"
+ transform="matrix(1.2585415,-0.2300055,0.2168789,1.1867072,-248.76141,68.254424)"
+ id="path8024"
+ style="opacity:1;fill:#c00000;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.0804934;stroke-linecap:butt;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1" />
+ <path
+ d="M 358.5625,281.15625 C 348.09597,281.05155 337.43773,281.94729 326.71875,283.90625 C 240.96686,299.57789 183.37901,377.92385 198.15625,458.78125 C 209.70749,521.98673 262.12957,567.92122 325.40625,577.5625 L 357.25,433.6875 L 509.34375,405.875 C 509.14405,404.58166 509.0804,403.29487 508.84375,402 C 495.91366,331.24978 431.82821,281.88918 358.5625,281.15625 z"
+ id="path8026"
+ style="opacity:1;fill:#b60000;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.1;stroke-linecap:butt;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1" />
+ <path
+ d="M 294.2107,361.9442 L 282.79367,370.38482 L 261.73414,386.13346 C 253.13706,404.40842 254.3359,423.7989 259.7176,444.39774 C 273.6797,497.83861 313.42636,523.96124 369.50989,517.58957 C 398.21848,514.32797 424.51832,504.67345 440.64696,484.15958 L 469.89512,447.48298 L 294.2107,361.9442 z"
+ id="path8028"
+ style="fill:#750000;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.09999999;stroke-linecap:butt;stroke-miterlimit:4;stroke-dashoffset:0;stroke-opacity:1" />
+ <path
+ d="M 527.8214,393.1416 C 527.8214,461.31268 472.55783,516.57625 404.38675,516.57625 C 336.21567,516.57625 280.9521,461.31268 280.9521,393.1416 C 280.9521,324.97052 336.21567,269.70695 404.38675,269.70695 C 472.55783,269.70695 527.8214,324.97052 527.8214,393.1416 z"
+ transform="matrix(0.9837071,-0.1797787,0.1695165,0.9275553,-78.013985,79.234385)"
+ id="path8030"
+ style="opacity:1;fill:#d40000;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.10298239;stroke-linecap:butt;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1" />
+ <path
+ d="M 527.8214,393.1416 C 527.8214,461.31268 472.55783,516.57625 404.38675,516.57625 C 336.21567,516.57625 280.9521,461.31268 280.9521,393.1416 C 280.9521,324.97052 336.21567,269.70695 404.38675,269.70695 C 472.55783,269.70695 527.8214,324.97052 527.8214,393.1416 z"
+ transform="matrix(0.9837071,-0.1797787,0.1695165,0.9275553,-69.306684,71.273294)"
+ id="path8032"
+ style="opacity:1;fill:#e11212;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.10298239;stroke-linecap:butt;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1" />
+ </g>
+ </g>
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/red.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/red.png
new file mode 100644
index 0000000..d32d5e2
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/red.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/shade.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/shade.png
new file mode 100644
index 0000000..a73afdf
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/shade.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/shine.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/shine.png
new file mode 100644
index 0000000..a18f7c4
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/shine.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/stock-go-back.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/stock-go-back.png
new file mode 100644
index 0000000..d320f26
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/stock-go-back.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/stock-go-forward.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/stock-go-forward.png
new file mode 100644
index 0000000..1ee5a29
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/stock-go-forward.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/stock-go-up.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/stock-go-up.png
new file mode 100644
index 0000000..1cd7332
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/stock-go-up.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/stock-home.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/stock-home.png
new file mode 100644
index 0000000..122536d
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/stock-home.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/title_logo.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/title_logo.png
new file mode 100644
index 0000000..d5182b4
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/title_logo.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/title_logo.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/title_logo.svg
new file mode 100644
index 0000000..e8fd52b
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/title_logo.svg
@@ -0,0 +1,61 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="220"
+ height="70"
+ id="svg6180">
+ <defs
+ id="defs6182" />
+ <g
+ transform="translate(-266.55899,-345.34488)"
+ id="layer1">
+ <path
+ d="m 316.7736,397.581 c 0,0 0,0 -20.53889,0 0.3327,4.45245 3.92157,7.77609 8.70715,7.77609 3.38983,0 6.31456,-1.39616 8.64094,-3.65507 0.46553,-0.46679 0.99726,-0.59962 1.59519,-0.59962 0.79781,0 1.59561,0.39932 2.12692,1.06388 0.3327,0.46553 0.53216,0.99726 0.53216,1.52857 0,0.73118 -0.3327,1.52857 -0.93106,2.12734 -2.7919,2.99052 -7.51086,4.98503 -12.16403,4.98503 -8.44149,0 -15.22074,-6.77967 -15.22074,-15.22158 0,-8.44149 6.58022,-15.22074 15.02171,-15.22074 8.37529,0 14.62323,6.51317 14.62323,15.08749 0,1.26418 -1.12924,2.12861 -2.39258,2.12861 z m -12.23065,-11.76512 c -4.45329,0 -7.51085,2.92473 -8.17499,7.17731 10.03626,0 16.35083,0 16.35083,0 -0.59836,-4.05355 -3.78874,-7.17731 -8.17584,-7.17731 z"
+ id="path11"
+ style="fill:#3c6eb4" />
+ <path
+ d="m 375.46344,410.80807 c -8.44106,0 -15.22074,-6.77968 -15.22074,-15.22159 0,-8.44149 6.77968,-15.22074 15.22074,-15.22074 8.44234,0 15.22159,6.77925 15.22159,15.22074 -4.2e-4,8.44149 -6.77968,15.22159 -15.22159,15.22159 z m 0,-24.65992 c -5.31688,0 -8.77377,4.25427 -8.77377,9.43833 0,5.18364 3.45689,9.43833 8.77377,9.43833 5.31731,0 8.77504,-4.25469 8.77504,-9.43833 -4.2e-4,-5.18406 -3.45773,-9.43833 -8.77504,-9.43833 z"
+ id="path13"
+ style="fill:#3c6eb4" />
+ <path
+ d="m 412.66183,380.36574 c -4.45963,0 -7.40966,1.319 -10.01391,4.62956 l -0.24036,-1.53995 0,0 c -0.20198,-1.60743 -1.57326,-2.84926 -3.23382,-2.84926 -1.80139,0 -3.26206,1.459 -3.26206,3.26081 0,0.003 0,0.005 0,0.008 l 0,0 0,0.003 0,0 0,23.40712 c 0,1.79464 1.46194,3.25743 3.257,3.25743 1.79465,0 3.25744,-1.46279 3.25744,-3.25743 l 0,-12.56209 c 0,-5.71621 4.98502,-8.57432 10.23613,-8.57432 1.59519,0 2.85726,-1.32953 2.85726,-2.92515 0,-1.59561 -1.26207,-2.85726 -2.85768,-2.85726 z"
+ id="path15"
+ style="fill:#3c6eb4" />
+ <path
+ d="m 447.02614,395.58648 c 0.0666,-8.17541 -5.78326,-15.22074 -15.222,-15.22074 -8.44192,0 -15.28779,6.77925 -15.28779,15.22074 0,8.44191 6.64684,15.22159 14.68985,15.22159 4.01434,0 7.62682,-2.06621 9.23846,-4.22518 l 0.79359,2.01434 0,0 c 0.42589,1.13177 1.5176,1.93717 2.7978,1.93717 1.65001,0 2.98756,-1.33671 2.99009,-2.98545 l 0,0 0,-7.80687 0,0 0,-4.1556 z m -15.222,9.43833 c -5.31773,0 -8.77419,-4.25469 -8.77419,-9.43833 0,-5.18406 3.45604,-9.43833 8.77419,-9.43833 5.3173,0 8.77419,4.25427 8.77419,9.43833 0,5.18364 -3.45689,9.43833 -8.77419,9.43833 z"
+ id="path17"
+ style="fill:#3c6eb4" />
+ <path
+ d="m 355.01479,368.3337 c 0,-1.7938 -1.46194,-3.18997 -3.25659,-3.18997 -1.79422,0 -3.25743,1.39659 -3.25743,3.18997 l 0,17.1499 c -1.66097,-3.05756 -5.25026,-5.11786 -9.50495,-5.11786 -8.64052,0 -14.42336,6.51318 -14.42336,15.22074 0,8.70757 5.98229,15.22159 14.42336,15.22159 3.76555,0 7.03057,-1.55429 8.98587,-4.25554 l 0.72317,1.83428 c 0.44782,1.25912 1.64917,2.16024 3.06051,2.16024 1.78621,0 3.24984,-1.45435 3.24984,-3.24815 0,-0.005 0,-0.009 0,-0.0139 l 0,0 0,-38.95128 -4.2e-4,0 z m -15.22116,36.69111 c -5.31731,0 -8.70715,-4.25469 -8.70715,-9.43833 0,-5.18406 3.38984,-9.43833 8.70715,-9.43833 5.31773,0 8.70714,4.0544 8.70714,9.43833 0,5.38309 -3.38941,9.43833 -8.70714,9.43833 z"
+ id="path19"
+ style="fill:#3c6eb4" />
+ <path
+ d="m 287.21553,365.34023 c -0.59414,-0.0877 -1.19966,-0.13198 -1.80097,-0.13198 -6.73118,0 -12.20746,5.4767 -12.20746,12.20788 l 0,3.8132 -3.98903,0 c -1.46237,0 -2.65908,1.19671 -2.65908,2.65781 0,1.46321 1.19671,2.93738 2.65908,2.93738 l 3.98819,0 0,20.46004 c 0,1.79464 1.46236,3.25743 3.25658,3.25743 1.79507,0 3.25744,-1.46279 3.25744,-3.25743 l 0,-20.46004 4.40986,0 c 1.46194,0 2.65823,-1.47417 2.65823,-2.93738 0,-1.46152 -1.19629,-2.65823 -2.65823,-2.65823 l -4.40733,0 0,-3.8132 c 0,-3.13852 2.55323,-6.11469 5.69175,-6.11469 0.28294,0 0.56757,0.0211 0.84672,0.062 1.78031,0.26355 3.4358,-0.54269 3.70019,-2.32342 0.2627,-1.77904 -0.96606,-3.43538 -2.74594,-3.69935 z"
+ id="path21"
+ style="fill:#3c6eb4" />
+ <path
+ d="m 482.01243,363.57426 c 0,-10.06788 -8.16108,-18.22938 -18.22897,-18.22938 -10.06282,0 -18.22179,8.15475 -18.22854,18.21631 l -4.2e-4,-4.2e-4 0,14.1071 4.2e-4,4.2e-4 c 0.005,2.28463 1.85832,4.13409 4.14463,4.13409 0.007,0 0.0127,-8.4e-4 0.0194,-8.4e-4 l 0.001,8.4e-4 14.07083,0 0,0 c 10.06409,-0.004 18.22138,-8.16276 18.22138,-18.22812 z"
+ id="path25"
+ style="fill:#294172" />
+ <path
+ d="m 469.13577,349.66577 c -4.72528,0 -8.55576,3.83049 -8.55576,8.55577 0,0.002 0,0.004 0,0.006 l 0,4.52836 -4.51444,0 c -8.5e-4,0 -8.5e-4,0 -0.001,0 -4.72528,0 -8.55576,3.81193 -8.55576,8.53678 0,4.72528 3.83048,8.55577 8.55576,8.55577 4.72486,0 8.55534,-3.83049 8.55534,-8.55577 0,-0.002 0,-0.004 0,-0.006 l 0,-4.54733 4.51444,0 c 8.5e-4,0 0.001,0 0.002,0 4.72486,0 8.55534,-3.79296 8.55534,-8.51781 0,-4.72528 -3.83048,-8.55577 -8.55534,-8.55577 z m -8.55576,21.63483 c -0.004,2.48998 -2.02446,4.50811 -4.51571,4.50811 -2.49378,0 -4.53426,-2.02193 -4.53426,-4.5157 0,-2.49421 2.04048,-4.55366 4.53426,-4.55366 0.002,0 0.004,4.2e-4 0.006,4.2e-4 l 3.86971,0 c 0.001,0 0.002,-4.2e-4 0.003,-4.2e-4 0.35209,0 0.63799,0.28505 0.63799,0.63715 0,4.2e-4 -4.2e-4,8.4e-4 -4.2e-4,0.001 l 0,3.92284 -4.2e-4,0 z m 8.55534,-8.5448 c -0.001,0 -0.003,0 -0.004,0 l -3.87223,0 c -8.4e-4,0 -0.002,0 -0.002,0 -0.35252,0 -0.63757,-0.28506 -0.63757,-0.63758 l 0,-4.2e-4 0,-3.90343 c 0.004,-2.49083 2.02
446,-4.50854 4.51571,-4.50854 2.49378,0 4.53468,2.02193 4.53468,4.51613 4.2e-4,2.49336 -2.04048,4.53384 -4.53426,4.53384 z"
+ id="path29"
+ style="fill:#3c6eb4" />
+ <path
+ d="m 460.58001,362.7558 0,-4.52836 c 0,-0.002 0,-0.004 0,-0.006 0,-4.72528 3.83048,-8.55577 8.55576,-8.55577 0.71685,0 1.22623,0.0805 1.88952,0.25469 0.96774,0.25385 1.75796,1.04618 1.75838,1.96922 4.2e-4,1.11575 -0.80919,1.92621 -2.0194,1.92621 -0.57642,0 -0.78473,-0.11048 -1.62892,-0.11048 -2.49125,0 -4.51149,2.01771 -4.51571,4.50854 l 0,3.90385 0,4.2e-4 c 0,0.35252 0.28505,0.63758 0.63757,0.63758 4.3e-4,0 0.001,0 0.002,0 l 2.96521,0 c 1.10521,0 1.99747,0.88467 1.99832,1.99283 0,1.10816 -0.89353,1.99114 -1.99832,1.99114 l -3.60489,0 0,4.54733 c 0,0.002 0,0.004 0,0.006 0,4.72485 -3.83048,8.55534 -8.55534,8.55534 -0.71684,0 -1.22623,-0.0805 -1.88952,-0.25469 -0.96774,-0.25343 -1.75838,-1.04618 -1.7588,-1.9688 0,-1.11575 0.80919,-1.92663 2.01982,-1.92663 0.576,0 0.78473,0.11048 1.6285,0.11048 2.49125,0 4.51191,-2.01771 4.51613,-4.50811 0,0 0,-3.92368 0,-3.9241 0,-0.35168 -0.2859,-0.63673 -0.63799,-0.63673 -4.3e-4,0 -8.5e-4,0 -0.002,0 l -2.96521,-4.2e-4 c -1.10521,0 -1.
99831,-0.88214 -1.99831,-1.9903 -4.3e-4,-1.11533 0.90238,-1.99367 2.01939,-1.99367 l 3.58339,0 0,0 z"
+ id="path31"
+ style="fill:#ffffff" />
+ <path
+ d="m 477.41661,378.55292 2.81558,0 0,0.37898 -1.18152,0 0,2.94935 -0.45254,0 0,-2.94935 -1.18152,0 0,-0.37898 m 3.26144,0 0.67101,0 0.84937,2.26496 0.85381,-2.26496 0.67102,0 0,3.32833 -0.43917,0 0,-2.9226 -0.85828,2.28279 -0.45255,0 -0.85827,-2.28279 0,2.9226 -0.43694,0 0,-3.32833"
+ id="text6223"
+ style="fill:#294172;enable-background:new" />
+ </g>
+ <path
+ d="m 181.98344,61.675273 2.81558,0 0,0.37898 -1.18152,0 0,2.94935 -0.45254,0 0,-2.94935 -1.18152,0 0,-0.37898 m 3.26144,0 0.67101,0 0.84937,2.26496 0.85381,-2.26496 0.67102,0 0,3.32833 -0.43917,0 0,-2.9226 -0.85828,2.28279 -0.45255,0 -0.85827,-2.28279 0,2.9226 -0.43694,0 0,-3.32833"
+ id="path2391"
+ style="fill:#294172;enable-background:new" />
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/warning.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/warning.png
new file mode 100644
index 0000000..ce09951
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/warning.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/warning.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/warning.svg
new file mode 100644
index 0000000..5f2612c
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/warning.svg
@@ -0,0 +1,89 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:dc="http://purl.org/dc/elements/1.1/"
+ xmlns:cc="http://creativecommons.org/ns#"
+ xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd"
+ xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
+ version="1.0"
+ width="48"
+ height="48"
+ id="svg5921"
+ sodipodi:version="0.32"
+ inkscape:version="0.46"
+ sodipodi:docname="warning.svg"
+ inkscape:output_extension="org.inkscape.output.svg.inkscape"
+ inkscape:export-filename="/home/jfearn/Build/src/fedora/publican/trunk/publican-fedora/en-US/images/warning.png"
+ inkscape:export-xdpi="111.32"
+ inkscape:export-ydpi="111.32">
+ <metadata
+ id="metadata2482">
+ <rdf:RDF>
+ <cc:Work
+ rdf:about="">
+ <dc:format>image/svg+xml</dc:format>
+ <dc:type
+ rdf:resource="http://purl.org/dc/dcmitype/StillImage" />
+ </cc:Work>
+ </rdf:RDF>
+ </metadata>
+ <sodipodi:namedview
+ inkscape:window-height="910"
+ inkscape:window-width="1284"
+ inkscape:pageshadow="2"
+ inkscape:pageopacity="0.0"
+ guidetolerance="10.0"
+ gridtolerance="10.0"
+ objecttolerance="10.0"
+ borderopacity="1.0"
+ bordercolor="#666666"
+ pagecolor="#ffffff"
+ id="base"
+ showgrid="false"
+ inkscape:zoom="11.5"
+ inkscape:cx="20"
+ inkscape:cy="20"
+ inkscape:window-x="0"
+ inkscape:window-y="51"
+ inkscape:current-layer="svg5921" />
+ <defs
+ id="defs5923">
+ <inkscape:perspective
+ sodipodi:type="inkscape:persp3d"
+ inkscape:vp_x="0 : 20 : 1"
+ inkscape:vp_y="0 : 1000 : 0"
+ inkscape:vp_z="40 : 20 : 1"
+ inkscape:persp3d-origin="20 : 13.333333 : 1"
+ id="perspective2484" />
+ </defs>
+ <g
+ transform="matrix(0.4536635,0,0,0.4536635,-5.1836431,-4.6889387)"
+ id="layer1">
+ <g
+ transform="translate(2745.6887,-1555.5977)"
+ id="g8304"
+ style="enable-background:new">
+ <path
+ d="M -1603,1054.4387 L -1577.0919,1027.891 L -1540,1027.4387 L -1513.4523,1053.3468 L -1513,1090.4387 L -1538.9081,1116.9864 L -1576,1117.4387 L -1602.5477,1091.5306 L -1603,1054.4387 z"
+ transform="matrix(0.8233528,8.9983906e-3,-8.9983906e-3,0.8233528,-1398.5561,740.7914)"
+ id="path8034"
+ style="opacity:1;fill:#efd259;fill-opacity:1;stroke:#efd259;stroke-opacity:1" />
+ <path
+ d="M -1603,1054.4387 L -1577.0919,1027.891 L -1540,1027.4387 L -1513.4523,1053.3468 L -1513,1090.4387 L -1538.9081,1116.9864 L -1576,1117.4387 L -1602.5477,1091.5306 L -1603,1054.4387 z"
+ transform="matrix(0.6467652,7.0684723e-3,-7.0684723e-3,0.6467652,-1675.7492,927.16391)"
+ id="path8036"
+ style="opacity:1;fill:#a42324;fill-opacity:1;stroke:#a42324;stroke-opacity:1" />
+ <path
+ d="M -2686.7886,1597.753 C -2686.627,1596.5292 -2686.5462,1595.6987 -2686.5462,1595.218 C -2686.5462,1593.1637 -2688.0814,1592.0711 -2690.9899,1592.0711 C -2693.8985,1592.0711 -2695.4336,1593.12 -2695.4336,1595.218 C -2695.4336,1595.961 -2695.3528,1596.7914 -2695.1912,1597.753 L -2692.929,1614.4491 L -2689.0508,1614.4491 L -2686.7886,1597.753"
+ id="path8038"
+ style="font-size:107.13574219px;font-style:normal;font-weight:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;stroke-width:1px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1;font-family:Bitstream Charter" />
+ <path
+ d="M -2690.9899,1617.8197 C -2693.6124,1617.8197 -2695.8118,1619.9346 -2695.8118,1622.6416 C -2695.8118,1625.3486 -2693.6124,1627.4635 -2690.9899,1627.4635 C -2688.2829,1627.4635 -2686.168,1625.264 -2686.168,1622.6416 C -2686.168,1619.9346 -2688.2829,1617.8197 -2690.9899,1617.8197"
+ id="path8040"
+ style="font-size:107.13574219px;font-style:normal;font-weight:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;stroke-width:1px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1;font-family:Bitstream Charter" />
+ </g>
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/watermark-draft.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/watermark-draft.png
new file mode 100644
index 0000000..0ead5af
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/watermark-draft.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/yellow.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/yellow.png
new file mode 100644
index 0000000..223865d
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/Common_Content/images/yellow.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/index.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/index.html
new file mode 100644
index 0000000..fcba9a9
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/index.html
@@ -0,0 +1,23203 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Ghid RPM</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><meta name="description" content="O scurtă trecere în revistă și un sumar al subiectului și scopului cărții, în mod tradițional nu mai lung(ă) de un paragraf. Notă: trecerea în revistă va apărea pe prima pagină a cărții și în câmpul #description al fișierului spec aparținând RPM-ului cărții" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><div xml:lang="ro" class="book" id="id1414586" lang="ro"><div class="titlepage"><div><div class="producttitle" font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><span class="productname">Schiță Documentație Fedora</span> <span class="productnumber"></span></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><h1 id="id1414586" class="title">Ghid RPM</h1></div>
<div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><h2 class="subtitle">scurt descriptor</h2></div><p class="edition">Ediție 0</p><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><h3 class="corpauthor">
+ <span class="inlinemediaobject"><object data="Common_Content/images/title_logo.svg" type="image/svg+xml"> Logo</object></span>
+
+ </h3></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><div xml:lang="ro" class="authorgroup" lang="ro"><div class="author"><h3 class="author"><span class="firstname">Eric</span> <span class="surname">Foster-Johnson</span></h3></div><div class="author"><h3 class="author"><span class="firstname">Stuart</span> <span class="surname">Ellis</span></h3><code class="email"><a class="email" href="mailto:stuart at elsn.org">stuart at elsn.org</a></code></div><div class="author"><h3 class="author"><span class="firstname">Ben</span> <span class="surname">Cotton</span></h3><code class="email"><a class="email" href="mailto:bcotton at fedoraproject.org">bcotton at fedoraproject.org</a></code></div></div></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><p class="copyright">Copyright © 2005,2010 Red Hat, Inc. and others</p></div><hr /><div font-family="sans-serif,Symbol,ZapfDin
gbats" font-weight="bold" font-size="12pt" text-align="center"><div id="id743752" class="legalnotice"><h1 class="legalnotice"></h1><div class="para">
+ Copyright <span class="trademark"></span>© 2005,2010 Red Hat, Inc. and others.
+ </div><div class="para">
+ The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at <a href="http://creativecommons.org/licenses/by-sa/3.0/">http://creativecommons.org/licenses/by-sa/3.0/</a>. The original authors of this document, and Red Hat, designate the Fedora Project as the "Attribution Party" for purposes of CC-BY-SA. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version.
+ </div><div class="para">
+ Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
+ </div><div class="para">
+ Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, MetaMatrix, Fedora, the Infinity Logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.
+ </div><div class="para">
+ For guidelines on the permitted uses of the Fedora trademarks, refer to <a href="https://fedoraproject.org/wiki/Legal:Trademark_guidelines">https://fedoraproject.org/wiki/Legal:Trademark_guidelines</a>.
+ </div><div class="para">
+ <span class="trademark">Linux</span>® is the registered trademark of Linus Torvalds in the United States and other countries.
+ </div><div class="para">
+ <span class="trademark">Java</span>® is a registered trademark of Oracle and/or its affiliates.
+ </div><div class="para">
+ <span class="trademark">XFS</span>® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
+ </div><div class="para">
+ <span class="trademark">MySQL</span>® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
+ </div><div class="para">
+ All other trademarks are the property of their respective owners.
+ </div></div></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><div class="abstract"><h6>Rezumat</h6><div class="para">
+ O scurtă trecere în revistă și un sumar al subiectului și scopului cărții, în mod tradițional nu mai lung(ă) de un paragraf. Notă: trecerea în revistă va apărea pe prima pagină a cărții și în câmpul #description al fișierului spec aparținând RPM-ului cărții
+ </div></div></div></div><hr /></div><div class="toc"><dl><dt><span class="preface"><a href="#ch-intro-packaging">Introducing Package Management</a></span></dt><dd><dl><dt><span class="sect1"><a href="#id744074">1. Installing, Removing, and Upgrading Applications</a></span></dt><dt><span class="sect1"><a href="#id870642">2. Overcoming the Installation Obstacles</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id775456">2.1. Application-level utilities</a></span></dt><dt><span class="sect2"><a href="#id1414533">2.2. Built-in system utilities</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id488776">3. Linux Software Management Tools: Packages</a></span></dt><dt><span class="sect1"><a href="#id593047">4. Summary</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-intro-rpm">1. Introduction to RPM</a></span></dt><dd><dl><dt><span class="sect1"><a href="#id822579">1.1. The Need for Linux Package Management Systems</a></span></dt><dt><span class="s
ect1"><a href="#id787809">1.2. RPM Design Goals</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id978840">1.2.1. Ease of use</a></span></dt><dt><span class="sect2"><a href="#id1356769">1.2.2. Package-oriented focus</a></span></dt><dt><span class="sect2"><a href="#id939937">1.2.3. Package upgradability</a></span></dt><dt><span class="sect2"><a href="#id556947">1.2.4. Package interdependencies</a></span></dt><dt><span class="sect2"><a href="#id633500">1.2.5. Query capabilities</a></span></dt><dt><span class="sect2"><a href="#id485232">1.2.6. Package verification</a></span></dt><dt><span class="sect2"><a href="#id734929">1.2.7. Multiple architectures</a></span></dt><dt><span class="sect2"><a href="#id855386">1.2.8. Pristine sources</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id532045">1.3. RPM Terminology</a></span></dt><dt><span class="sect1"><a href="#id627397">1.4. Summary</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-rpm-overview">2
. RPM Overview</a></span></dt><dd><dl><dt><span class="sect1"><a href="#id854538">2.1. Understanding the Package File</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id816046">2.1.1. RPM file format</a></span></dt><dt><span class="sect2"><a href="#id662734">2.1.2. Binary RPMs and Source RPMs</a></span></dt><dt><span class="sect2"><a href="#id586540">2.1.3. Source RPMs</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id732014">2.2. Querying the RPM Database</a></span></dt><dt><span class="sect1"><a href="#id555672">2.3. Running RPM Commands</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id586423">2.3.1. Working with the <code class="command">rpm</code> command</a></span></dt><dt><span class="sect2"><a href="#id664136">2.3.2. Other RPM commands</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id622461">2.4. Summary</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-using-rpm">3. Using RPM</a></span></dt><dd><dl><dt><span clas
s="sect1"><a href="#id534995">3.1. The <code class="command">rpm</code> Command</a></span></dt><dt><span class="sect1"><a href="#id578718">3.2. Upgrading and Installing Software</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id554587">3.2.1. Upgrading with the <code class="command">rpm</code> command</a></span></dt><dt><span class="sect2"><a href="#id596004">3.2.2. Upgrading packages</a></span></dt><dt><span class="sect2"><a href="#id809735">3.2.3. Freshening up</a></span></dt><dt><span class="sect2"><a href="#id583586">3.2.4. Installing Packages</a></span></dt><dt><span class="sect2"><a href="#id816163">3.2.5. Installing Over the Internet</a></span></dt><dt><span class="sect2"><a href="#id567480">3.2.6. Installing source RPMs</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id1373416">3.3. Removing Software</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id1067283">3.3.1. Checking that the package has been removed</a></span></dt><dt><span class=
"sect2"><a href="#id935675">3.3.2. Removing multiple packages at a time</a></span></dt><dt><span class="sect2"><a href="#id787355">3.3.3. Options when removing packages</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id821991">3.4. Other <code class="command">rpm</code> Command Options</a></span></dt><dt><span class="sect1"><a href="#id566157">3.5. Summary</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-using-rpm-db">4. Using the RPM Database</a></span></dt><dd><dl><dt><span class="section"><a href="#RPM_Guide-Using_RPM_DB-querying_database">4.1. Querying the RPM Database</a></span></dt><dd><dl><dt><span class="section"><a href="#id631876">4.1.1. Querying packages</a></span></dt><dt><span class="section"><a href="#RPM_Guide-Using_RPM_DB-query_everything">4.1.2. Querying everything</a></span></dt><dt><span class="section"><a href="#RPM_Guide-Using_RPM_DB-refining_query">4.1.3. Refining the query</a></span></dt><dt><span class="section"><a href="#RPM
_Guide-Using_RPM_DB-which_package">4.1.4. Finding which packages own files</a></span></dt></dl></dd><dt><span class="section"><a href="#RPM_Guide-Using_RPM_DB-getting_information">4.2. Getting Information on Packages</a></span></dt><dd><dl><dt><span class="section"><a href="#RPM_Guide-USing_RPM_DB-getting_information-describing_packages">4.2.1. Describing packages</a></span></dt><dt><span class="section"><a href="#RPM_Guide-Using_RPM_DB-package_groups">4.2.2. Package groups</a></span></dt><dt><span class="section"><a href="#id491747">4.2.3. Listing the files in a package</a></span></dt><dt><span class="section"><a href="#RPM_Guide-Using_RPM_DB-listing_conf_files">4.2.4. Listing the configuration files for a package</a></span></dt><dt><span class="section"><a href="#id1301235">4.2.5. Listing the documentation files for a package</a></span></dt><dt><span class="section"><a href="#RPM_Guide-Using_RPM_DB-file_state">4.2.6. Listing the state of the files in a package</a></span></
dt><dt><span class="section"><a href="#RPM_Guide-Using_RPM_DB-listing_scripts">4.2.7. Listing the scripts in a package</a></span></dt><dt><span class="section"><a href="#RPM_Guide-Using_RPM_DB-Listing_changed">4.2.8. Listing what has changed</a></span></dt><dt><span class="section"><a href="#RPM_Guide-Using_RPM_DB-Combining_queries">4.2.9. Combining queries</a></span></dt><dt><span class="section"><a href="#RPM_Guide-Using_RPM_DB-Cusomt_queries">4.2.10. Creating custom queries</a></span></dt><dt><span class="section"><a href="#RPM_Guide-Using_RPM_DB-Query_format_tags">4.2.11. Working With Query Format Tags</a></span></dt><dt><span class="section"><a href="#RPM_Guide-Using_RPM_DB-Querying_for_package_information">4.2.12. Querying for Package Information</a></span></dt><dt><span class="section"><a href="#RPM_Guide-Using_RPM_DB-Formatting_arrays">4.2.13. Formatting Arrays</a></span></dt><dt><span class="section"><a href="#RPM_Guide-Using_RPM_DB-Special_formatting">4.2.14. Speci
al Formatting</a></span></dt><dt><span class="section"><a href="#RPM_Guide-Using_RPM_DB-querying_pacakge_dependencies">4.2.15. Querying for Package Dependencies</a></span></dt><dt><span class="section"><a href="#RPM-Guide-Using_RPM_DB-Querying_file_information">4.2.16. Querying for File Information</a></span></dt><dt><span class="section"><a href="#RPM_Guide-Using_RPM_DB-Other_Query_Format_Tags">4.2.17. Other Query Format Tags</a></span></dt></dl></dd><dt><span class="section"><a href="#id878995">4.3. Other queries</a></span></dt><dt><span class="section"><a href="#RPM_Guide-Using_RPM_DB-Getting_information_on_package_files">4.4. Getting Information on Package Files</a></span></dt><dd><dl><dt><span class="section"><a href="#RPM_Guide_Using_RPM_DB-Querying_package_files_remotely">4.4.1. Querying Package Files Remotely</a></span></dt><dt><span class="section"><a href="#RPM-Guide-Using_RPM-DB-verifying_packages">4.4.2. Verifying Installed RPM Packages</a></span></dt><dt><span c
lass="section"><a href="#RPM_GUide-Using_RPM_DB-working_with_RPM_db">4.4.3. Working With the RPM Database</a></span></dt><dt><span class="section"><a href="#RPM_Guide-Using_RPM_DB-summary">4.4.4. Summary</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-dependencies">5. Package Dependencies</a></span></dt><dd><dl><dt><span class="sect1"><a href="#id1301254">5.1. Understanding the Dependency Concept</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id754278">5.1.1. Capabilities</a></span></dt><dt><span class="sect2"><a href="#id656923">5.1.2. Version dependencies</a></span></dt><dt><span class="sect2"><a href="#id509482">5.1.3. Conflicts</a></span></dt><dt><span class="sect2"><a href="#id801957">5.1.4. Obsoletes</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id791830">5.2. Checking for Dependencies</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id508593">5.2.1. Determining the capabilities a package requires</a></span></dt>
<dt><span class="sect2"><a href="#id1330229">5.2.2. Determining the capabilities a package provides</a></span></dt><dt><span class="sect2"><a href="#id978084">5.2.3. Checking for conflicts</a></span></dt><dt><span class="sect2"><a href="#id744095">5.2.4. Determining which packages require a certain capability</a></span></dt><dt><span class="sect2"><a href="#id641701">5.2.5. Determining which package provides a certain capability</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id514023">5.3. Triggers</a></span></dt><dt><span class="sect1"><a href="#id615970">5.4. Summary</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-transactions">6. Transactions</a></span></dt><dd><dl><dt><span class="sect1"><a href="#id594651">6.1. Understanding Transactions</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id538656">6.1.1. When do you need transactions?</a></span></dt><dt><span class="sect2"><a href="#id567248">6.1.2. Backing out of transactions</a></span
></dt></dl></dd><dt><span class="sect1"><a href="#id634510">6.2. Transactions with the rpm Command</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id608937">6.2.1. Transaction IDs</a></span></dt><dt><span class="sect2"><a href="#id881620">6.2.2. Rolling Back Transactions</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id638162">6.3. Saving Old Packages</a></span></dt><dt><span class="sect1"><a href="#id834924">6.4. Summary</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-management-software">7. RPM Management Software</a></span></dt><dd><dl><dt><span class="sect1"><a href="#id595261">7.1. Locating RPMs</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id736680">7.1.1. rpmfind and rpm2html</a></span></dt><dt><span class="sect2"><a href="#id869488">7.1.2. RPM Sites On the Internet</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id561016">7.2. Graphical RPM Management</a></span></dt><dd><dl><dt><span class="sect2"><a href="#i
d561039">7.2.1. Nautilus</a></span></dt><dt><span class="sect2"><a href="#id734494">7.2.2. Red Hat Package Management</a></span></dt><dt><span class="sect2"><a href="#id579713">7.2.3. KPackage</a></span></dt><dt><span class="sect2"><a href="#id856872">7.2.4. Gnome-RPM</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id503396">7.3. Extending RPM Management</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id554830">7.3.1. AutoRPM</a></span></dt><dt><span class="sect2"><a href="#id760680">7.3.2. AutoUpdate</a></span></dt><dt><span class="sect2"><a href="#id715873">7.3.3. The Red Hat Network and up2date</a></span></dt><dt><span class="sect2"><a href="#id750620">7.3.4. Current</a></span></dt><dt><span class="sect2"><a href="#id750644">7.3.5. urpmi and RpmDrake</a></span></dt><dt><span class="sect2"><a href="#id697201">7.3.6. apt-rpm</a></span></dt><dt><span class="sect2"><a href="#id559117">7.3.7. The poldek</a></span></dt></dl></dd><dt><span class="sect1"><a hr
ef="#id591000">7.4. Summary</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-creating-rpms">8. Creating RPMs: An Overview</a></span></dt><dd><dl><dt><span class="sect1"><a href="#id819374">8.1. Preparing to Build RPMs</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id863998">8.1.1. Planning what you want to build</a></span></dt><dt><span class="sect2"><a href="#id599111">8.1.2. Gathering the software to package</a></span></dt><dt><span class="sect2"><a href="#id600670">8.1.3. Creating a reproducible build of the software</a></span></dt><dt><span class="sect2"><a href="#id592939">8.1.4. Planning for Upgrades</a></span></dt><dt><span class="sect2"><a href="#id633627">8.1.5. Outlining Any Dependencies</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id784426">8.2. Building RPMs</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id934340">8.2.1. Setting up the directory structure</a></span></dt><dt><span class="sect2"><a href="#id563449">8
.2.2. Placing your sources into the directory structure</a></span></dt><dt><span class="sect2"><a href="#id789919">8.2.3. Creating the spec file</a></span></dt><dt><span class="sect2"><a href="#id727163">8.2.4. Building RPMs with the rpmbuild command</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id761902">8.3. Verifying Your RPMS</a></span></dt><dt><span class="sect1"><a href="#id969647">8.4. Summary</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-specfiles">9. Working with Spec Files</a></span></dt><dd><dl><dt><span class="sect1"><a href="#id636173">9.1. Reading Spec Files</a></span></dt><dt><span class="sect1"><a href="#id726244">9.2. Writing Spec Files</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id622244">9.2.1. Comments</a></span></dt><dt><span class="sect2"><a href="#id656356">9.2.2. Storing spec files on disk</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id621366">9.3. Defining Package Information</a></span></dt><d
d><dl><dt><span class="sect2"><a href="#id1336268">9.3.1. Describing the package</a></span></dt><dt><span class="sect2"><a href="#id864211">9.3.2. Setting build locations</a></span></dt><dt><span class="sect2"><a href="#id1361246">9.3.3. Naming source files</a></span></dt><dt><span class="sect2"><a href="#id562402">9.3.4. Naming patches</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id818931">9.4. Controlling the Build</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id786190">9.4.1. Preparing for the build</a></span></dt><dt><span class="sect2"><a href="#id763342">9.4.2. Building the software</a></span></dt><dt><span class="sect2"><a href="#id1412942">9.4.3. Installing the software</a></span></dt><dt><span class="sect2"><a href="#id838965">9.4.4. Cleaning up after the build</a></span></dt><dt><span class="sect2"><a href="#id496151">9.4.5. Defining installation scripts</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id848369">9.5. Filling the L
ist of Files</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id716381">9.5.1. Using wildcards</a></span></dt><dt><span class="sect2"><a href="#id886328">9.5.2. Naming directories of files</a></span></dt><dt><span class="sect2"><a href="#id1413650">9.5.3. Marking files as documentation or configuration files</a></span></dt><dt><span class="sect2"><a href="#id732681">9.5.4. Setting file attributes</a></span></dt><dt><span class="sect2"><a href="#id611823">9.5.5. Verifying the %files section</a></span></dt><dt><span class="sect2"><a href="#id587858">9.5.6. Filling the list of files automatically</a></span></dt><dt><span class="sect2"><a href="#id555916">9.5.7. Handling RPM build errors for unpackaged files</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id581967">9.6. Adding Change Log Entries</a></span></dt><dt><span class="sect1"><a href="#id673788">9.7. Defining Spec File Macros</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id673805">9.7.1. Bui
lt-in macros</a></span></dt><dt><span class="sect2"><a href="#id538862">9.7.2. Spec file-specific macros</a></span></dt><dt><span class="sect2"><a href="#id726602">9.7.3. Defining new macros</a></span></dt><dt><span class="sect2"><a href="#id578192">9.7.4. Specifying parameters to macros</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id756998">9.8. Creating XML Spec Files</a></span></dt><dt><span class="sect1"><a href="#id1413321">9.9. Summary</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-advanced-packaging">10. Creare avansată pachete RPM</a></span></dt><dd><dl><dt><span class="sect1"><a href="#id862470">10.1. Definirea dependențelor pachetelor</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id739772">10.1.1. Numirea dependențelor</a></span></dt><dt><span class="sect2"><a href="#id749803">10.1.2. Setarea premiselor</a></span></dt><dt><span class="sect2"><a href="#id550502">10.1.3. Numirea dependențelor de construcție</a></span></d
t><dt><span class="sect2"><a href="#id550512">10.1.4. Generarea automată de dependențe</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id523284">10.2. Setarea triggerelor</a></span></dt><dt><span class="sect1"><a href="#id864441">10.3. Scrierea scripturilor de verificare</a></span></dt><dt><span class="sect1"><a href="#id919420">10.4. Crearea subpachetelor.</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id680225">10.4.1. Furnizarea informațiilor pentru subpachete</a></span></dt><dt><span class="sect2"><a href="#id1413121">10.4.2. Definirea scripturilor pentru subpachete</a></span></dt><dt><span class="sect2"><a href="#id919281">10.4.3. Construirea subpachetelor</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id864110">10.5. Creating Relocatable Packages</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id670616">10.5.1. Setting up the prefixes</a></span></dt><dt><span class="sect2"><a href="#id773908">10.5.2. Define the files section
</a></span></dt><dt><span class="sect2"><a href="#id831211">10.5.3. Problems creating relocatable packages</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id777632">10.6. Defining Conditional Builds</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id676244">10.6.1. Defining conditional macros</a></span></dt><dt><span class="sect2"><a href="#id970594">10.6.2. Using conditional blocks</a></span></dt><dt><span class="sect2"><a href="#id679472">10.6.3. Using architecture-based conditionals</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id790812">10.7. Summary</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-rpmbuild">11. Controlling the Build with <code class="command">rpmbuild</code></a></span></dt><dd><dl><dt><span class="sect1"><a href="#id569546">11.1. Building RPMs with the rpmbuild Command</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id566973">11.1.1. Customizing the build</a></span></dt><dt><span class="sect2"><a h
ref="#id575664">11.1.2. Testing the build</a></span></dt><dt><span class="sect2"><a href="#id553875">11.1.3. Debugging the build</a></span></dt><dt><span class="sect2"><a href="#id516418">11.1.4. Cleaning up</a></span></dt><dt><span class="sect2"><a href="#id1415379">11.1.5. Building for other platforms</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id625711">11.2. Building RPMs Without an External Spec File</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id625725">11.2.1. Options for working with tar archives</a></span></dt><dt><span class="sect2"><a href="#id818541">11.2.2. The expected archive structure</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id1005965">11.3. Working with Source RPMs</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id753269">11.3.1. Rebuilding binary RPMS from source RPMs</a></span></dt><dt><span class="sect2"><a href="#id1315118">11.3.2. Recompiling binaries from source RPMs</a></span></dt><dt><span class="
sect2"><a href="#id744420">11.3.3. SRPMS? Finding source RPMs</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id570726">11.4. Signing Built RPMs</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id570739">11.4.1. Checking that the GPG software is installed</a></span></dt><dt><span class="sect2"><a href="#id619927">11.4.2. Configuring a signature</a></span></dt><dt><span class="sect2"><a href="#id785579">11.4.3. Signing with the rpmbuild command</a></span></dt><dt><span class="sect2"><a href="#id757369">11.4.4. Signing with the rpm command</a></span></dt><dt><span class="sect2"><a href="#id639407">11.4.5. Verifying signatures</a></span></dt><dt><span class="sect2"><a href="#id723247">11.4.6. Importing public keys</a></span></dt><dt><span class="sect2"><a href="#id550839">11.4.7. Getting the Red Hat public key</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id714646">11.5. Summary</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-extr
a-packaging-tools">12. Supplemental Packaging Software</a></span></dt><dd><dl><dt><span class="sect1"><a href="#id943659">12.1. Packaging Aids</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id943675">12.1.1. Using VIM spec plugins to improve spec file editing</a></span></dt><dt><span class="sect2"><a href="#id853827">12.1.2. Adding functions with emacs rpm-spec-mode</a></span></dt><dt><span class="sect2"><a href="#id1329990">12.1.3. Validating and debugging spec files with rpmlint</a></span></dt><dt><span class="sect2"><a href="#id571366">12.1.4. Generating the %files section with RUST</a></span></dt><dt><span class="sect2"><a href="#id737961">12.1.5. setup.sh and MakeRPM.pl</a></span></dt><dt><span class="sect2"><a href="#id561611">12.1.6. Manipulating Package Files with rpm2cpio</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id854931">12.2. Summary</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-packaging-guidelines">13. Packaging Guid
elines</a></span></dt><dd><dl><dt><span class="sect1"><a href="#id739793">13.1. Avoiding Common Problems</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id803805">13.1.1. Scan the mailing lists</a></span></dt><dt><span class="sect2"><a href="#id584631">13.1.2. Use rpmbuild</a></span></dt><dt><span class="sect2"><a href="#id661855">13.1.3. Don’t try to defeat the system</a></span></dt><dt><span class="sect2"><a href="#id657967">13.1.4. Turn off automatic dependency generation</a></span></dt><dt><span class="sect2"><a href="#id668195">13.1.5. Don't list directories in %files</a></span></dt><dt><span class="sect2"><a href="#id795087">13.1.6. Handling circular dependencies</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id716645">13.2. Following Good Practices</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id615282">13.2.1. Preparation</a></span></dt><dt><span class="sect2"><a href="#id669869">13.2.2. Building</a></span></dt></dl></dd><dt><span cl
ass="sect1"><a href="#id570966">13.3. Summary</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-scripting">14. Automating RPM with Scripts</a></span></dt><dd><dl><dt><span class="sect1"><a href="#id1415954">14.1. Scripting</a></span></dt><dt><span class="sect1"><a href="#id754838">14.2. Distinguishing Scripting Languages from Programming Languages</a></span></dt><dt><span class="sect1"><a href="#id652088">14.3. Deciding When to Program and When to Script</a></span></dt><dt><span class="sect1"><a href="#id669084">14.4. Shell Scripting Basics</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id746568">14.4.1. Writing a script</a></span></dt><dt><span class="sect2"><a href="#id675446">14.4.2. Running a script</a></span></dt><dt><span class="sect2"><a href="#id712323">14.4.3. Problems running scripts</a></span></dt><dt><span class="sect2"><a href="#id820565">14.4.4. Turning a script into a command</a></span></dt><dt><span class="sect2"><a href="#id682469">14
.4.5. Passing command-line options to your script</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id818713">14.5. Examining RPM Files</a></span></dt><dt><span class="sect1"><a href="#id553708">14.6. Querying the RPM Database</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id800912">14.6.1. Querying for all packages installed at the same time</a></span></dt><dt><span class="sect2"><a href="#id979252">14.6.2. Reading HTML documentation for a package</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id561272">14.7. Where to Go From Here</a></span></dt><dt><span class="sect1"><a href="#id628097">14.8. Summary</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-programming-c">15. Programming RPM with C</a></span></dt><dd><dl><dt><span class="sect1"><a href="#id772965">15.1. Programming with the C Library</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id612187">15.1.1. Setting Up a C Programming Environment</a></span></dt><dt><spa
n class="sect2"><a href="#id692296">15.1.2. Setting Up the RPM Programming Environment</a></span></dt><dt><span class="sect2"><a href="#id726502">15.1.3. Using the RPM Library</a></span></dt><dt><span class="sect2"><a href="#id607656">15.1.4. Compiling and Linking RPM Programs</a></span></dt><dt><span class="sect2"><a href="#id812831">15.1.5. Getting information on your RPM environment</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id677086">15.2. The Power of popt</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id573466">15.2.1. Popt aliases</a></span></dt><dt><span class="sect2"><a href="#id854018">15.2.2. Programming with popt</a></span></dt><dt><span class="sect2"><a href="#id785286">15.2.3. Handling Errors</a></span></dt><dt><span class="sect2"><a href="#id870911">15.2.4. Running a popt example</a></span></dt><dt><span class="sect2"><a href="#id853423">15.2.5. Handling rpm command-line options</a></span></dt></dl></dd><dt><span class="sect1"><a href
="#id784404">15.3. Working with RPM Files</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id791650">15.3.1. Opening RPM files</a></span></dt><dt><span class="sect2"><a href="#id673138">15.3.2. Reading the RPM lead and signature</a></span></dt><dt><span class="sect2"><a href="#id865045">15.3.3. Reading header information</a></span></dt><dt><span class="sect2"><a href="#id678698">15.3.4. A shortcut to header information</a></span></dt><dt><span class="sect2"><a href="#id676439">15.3.5. Closing RPM files</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id569976">15.4. Programming with the RPM Database</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id808107">15.4.1. Database iterators</a></span></dt><dt><span class="sect2"><a href="#id749729">15.4.2. Dependency Sets</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id659876">15.5. Comparing an RPM File to an Installed Package</a></span></dt><dt><span class="sect1"><a href="#id582358">15.6. W
here to Go from Here</a></span></dt><dt><span class="sect1"><a href="#id577217">15.7. Summary</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-rpm-programming-python">16. Programming RPM with Python</a></span></dt><dd><dl><dt><span class="sect1"><a href="#id556037">16.1. Setting Up a Python Development Environment</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id870764">16.1.1. Installing the base Python packages</a></span></dt><dt><span class="sect2"><a href="#id590825">16.1.2. Using Python for graphics</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id713551">16.2. The Python API Hierarchy</a></span></dt><dt><span class="sect1"><a href="#id605418">16.3. Programming with the RPM Database</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id938108">16.3.1. Accessing the RPM database</a></span></dt><dt><span class="sect2"><a href="#id1298510">16.3.2. Querying the RPM database</a></span></dt><dt><span class="sect2"><a href="#id752269">
16.3.3. Examining the package header</a></span></dt><dt><span class="sect2"><a href="#id668577">16.3.4. Querying for specific packages</a></span></dt><dt><span class="sect2"><a href="#id498480">16.3.5. Printing information on packages</a></span></dt><dt><span class="sect2"><a href="#id652749">16.3.6. Refining queries</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id759668">16.4. Reading Package Files</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id759681">16.4.1. Reading headers from package files</a></span></dt><dt><span class="sect2"><a href="#id859682">16.4.2. Setting the verification flags</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id791873">16.5. Dependency Comparisons</a></span></dt><dt><span class="sect1"><a href="#id772730">16.6. Installing and Upgrading Packages</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id582317">16.6.1. Building up the transaction set</a></span></dt><dt><span class="sect2"><a href="#id773876">16
.6.2. Transaction elements</a></span></dt><dt><span class="sect2"><a href="#id641465">16.6.3. Checking and reordering the transaction elements</a></span></dt><dt><span class="sect2"><a href="#id693782">16.6.4. Running the transaction</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id639900">16.7. Where to Go from Here</a></span></dt><dt><span class="sect1"><a href="#id587324">16.8. Summary</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-programming-perl">17. Programming RPM with Perl</a></span></dt><dd><dl><dt><span class="sect1"><a href="#id623163">17.1. Getting and Using the Perl RPM Modules</a></span></dt><dt><span class="sect1"><a href="#id699498">17.2. Working with RPM Files</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id725917">17.2.1. Opening package files</a></span></dt><dt><span class="sect2"><a href="#id690852">17.2.2. Listing tags from the package</a></span></dt><dt><span class="sect2"><a href="#id542112">17.2.3. Convenience
methods</a></span></dt><dt><span class="sect2"><a href="#id764123">17.2.4. Listing the name and version</a></span></dt><dt><span class="sect2"><a href="#id803926">17.2.5. Checking whether the package is a source package</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id507880">17.3. Programming with the RPM Database</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id668033">17.3.1. Opening the database</a></span></dt><dt><span class="sect2"><a href="#id578109">17.3.2. Finding packages</a></span></dt><dt><span class="sect2"><a href="#id578128">17.3.3. Iterating over packages</a></span></dt><dt><span class="sect2"><a href="#id639329">17.3.4. Additional query subroutines</a></span></dt><dt><span class="sect2"><a href="#id880328">17.3.5. Getting information on packages</a></span></dt><dt><span class="sect2"><a href="#id717333">17.3.6. Comparing versions</a></span></dt><dt><span class="sect2"><a href="#id591364">17.3.7. Closing the database</a></span></dt></dl>
</dd><dt><span class="sect1"><a href="#id604517">17.4. Where to Go from Here</a></span></dt><dt><span class="sect1"><a href="#id798437">17.5. Summary</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-other-linuxes">18. Using RPM on Non-Red Hat Linuxes</a></span></dt><dd><dl><dt><span class="sect1"><a href="#id811830">18.1. Troubleshooting RPM Installation Issues</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id601628">18.1.1. Dealing with RPM versions</a></span></dt><dt><span class="sect2"><a href="#id581595">18.1.2. Dealing with divisions of software into packages</a></span></dt><dt><span class="sect2"><a href="#id540699">18.1.3. Dealing with dependency issues</a></span></dt><dt><span class="sect2"><a href="#id589152">18.1.4. Dealing with install locations</a></span></dt><dt><span class="sect2"><a href="#id806921">18.1.5. When all else fails, rebuild from the source package</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id789105">18.2. Ha
ndling Problems Building RPMs</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id660708">18.2.1. Writing distribution-specific packages</a></span></dt><dt><span class="sect2"><a href="#id492519">18.2.2. Dealing with automatic dependency generation</a></span></dt><dt><span class="sect2"><a href="#id962201">18.2.3. Dealing with different macros</a></span></dt><dt><span class="sect2"><a href="#id649087">18.2.4. Making relocatable packages</a></span></dt><dt><span class="sect2"><a href="#id1317565">18.2.5. Creating an RPM build environment</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id571016">18.3. Dealing with Non-RPM-Based Linux Versions</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id571028">18.3.1. Handling non-RPM packages with alien</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id682499">18.4. Standardizing RPMs</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id682517">18.4.1. Filesystem Hierarchy Standard</a></span><
/dt><dt><span class="sect2"><a href="#id562919">18.4.2. RPM adoption</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id772912">18.5. Summary</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-other-os">19. RPM on Other Operating Systems</a></span></dt><dd><dl><dt><span class="sect1"><a href="#id586148">19.1. Running RPM on Other Operating Systems</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id658642">19.1.1. Getting RPM for your system</a></span></dt><dt><span class="sect2"><a href="#id734430">19.1.2. Running RPM on Windows</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id734462">19.2. Bootstrapping RPM On Other Operating Systems</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id876773">19.2.1. Downloading the RPM software</a></span></dt><dt><span class="sect2"><a href="#id876798">19.2.2. Extracting the software</a></span></dt><dt><span class="sect2"><a href="#id573957">19.2.3. Reading the INSTALL file</a></span></dt><
dt><span class="sect2"><a href="#id573981">19.2.4. Libraries required by RPM</a></span></dt><dt><span class="sect2"><a href="#id855206">19.2.5. Tools for building RPM</a></span></dt><dt><span class="sect2"><a href="#id794537">19.2.6. Compiling RPM</a></span></dt><dt><span class="sect2"><a href="#id688202">19.2.7. Handling problems</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id561376">19.3. Setting Up the RPM System</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id561388">19.3.1. Setting up the RPM database</a></span></dt><dt><span class="sect2"><a href="#id617415">19.3.2. Creating the RPM environment</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id663021">19.4. Creating Non-Linux RPMS</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id762951">19.4.1. Setting up a build environment</a></span></dt><dt><span class="sect2"><a href="#id1109836">19.4.2. Cross-building packages</a></span></dt></dl></dd><dt><span class="sect1"><a href="#
id518158">19.5. Summary</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-customizing-rpm">20. Customizing RPM Behavior</a></span></dt><dd><dl><dt><span class="sect1"><a href="#id732671">20.1. Customizing with RPM Macros</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id599573">20.1.1. Defining macros</a></span></dt><dt><span class="sect2"><a href="#id624350">20.1.2. Customizing Macros</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id870277">20.2. Configuring RPM Settings</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id870293">20.2.1. Viewing the current settings</a></span></dt><dt><span class="sect2"><a href="#id579200">20.2.2. Locating the rpmrc files</a></span></dt><dt><span class="sect2"><a href="#id750695">20.2.3. Changing settings</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id559842">20.3. Adding Popt Aliases</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id700319">20.3.1. Defining aliases</a></span
></dt><dt><span class="sect2"><a href="#id835474">20.3.2. Customizing popt aliases</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id743957">20.4. Summary</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-command-reference">21. RPM Command Reference</a></span></dt><dd><dl><dt><span class="sect1"><a href="#id886624">21.1. The rpm Command</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id576688">21.1.1. Upgrade, freshen, and install options</a></span></dt><dt><span class="sect2"><a href="#id582449">21.1.2. Erase options</a></span></dt><dt><span class="sect2"><a href="#id640206">21.1.3. Signature options</a></span></dt><dt><span class="sect2"><a href="#id745360">21.1.4. Verify options</a></span></dt><dt><span class="sect2"><a href="#id620160">21.1.5. Database options</a></span></dt><dt><span class="sect2"><a href="#id665079">21.1.6. Miscellaneous options</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id650496">21.2. The rpmbuild Com
mand</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id650509">21.2.1. Building from a spec file</a></span></dt><dt><span class="sect2"><a href="#id784858">21.2.2. Building from a compressed tar archive</a></span></dt><dt><span class="sect2"><a href="#id703405">21.2.3. Rebuilding RPMs from source RPMs</a></span></dt><dt><span class="sect2"><a href="#id563539">21.2.4. Customizing the build</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-specfile-syntax">22. Spec File Syntax</a></span></dt><dd><dl><dt><span class="sect1"><a href="#id764656">22.1. Package Information Tags</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id690830">22.1.1. Comments</a></span></dt><dt><span class="sect2"><a href="#id843939">22.1.2. Build settings</a></span></dt><dt><span class="sect2"><a href="#id1283550">22.1.3. Dependency tags</a></span></dt><dt><span class="sect2"><a href="#id642245">22.1.4. Source files</a></span></dt></dl></dd><dt><span class="sect1"
><a href="#id662269">22.2. Macros</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id662281">22.2.1. Variable definition macros</a></span></dt><dt><span class="sect2"><a href="#id622855">22.2.2. Conditional macros</a></span></dt><dt><span class="sect2"><a href="#id571162">22.2.3. Built-in macros</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id853518">22.3. Build Sections</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id1363142">22.3.1. Build preparation</a></span></dt><dt><span class="sect2"><a href="#id1363163">22.3.2. Build</a></span></dt><dt><span class="sect2"><a href="#id860560">22.3.3. Installation</a></span></dt><dt><span class="sect2"><a href="#id613014">22.3.4. Clean up</a></span></dt><dt><span class="sect2"><a href="#id613035">22.3.5. Install and uninstall scripts</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id731001">22.4. File Tags</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id887593">22.4.1. Making reloca
table packages</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id887623">22.5. The Change Log</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-rpm-evolution">23. RPM Feature Evolution</a></span></dt><dt><span class="chapter"><a href="#ch-package-structure">24. RPM Package File Structure</a></span></dt><dd><dl><dt><span class="sect1"><a href="#id680686">24.1. The Package File</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id829652">24.1.1. The file identifier</a></span></dt><dt><span class="sect2"><a href="#id530474">24.1.2. The signature</a></span></dt><dt><span class="sect2"><a href="#id946419">24.1.3. The header</a></span></dt><dt><span class="sect2"><a href="#id588134">24.1.4. The payload</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-online-resources">25. RPM Resources</a></span></dt><dd><dl><dt><span class="sect1"><a href="#id847900">25.1. Finding RPM Sites</a></span></dt><dd><dl><dt><span class="sect2"><a h
ref="#id529167">25.1.1. The main rpm.org site</a></span></dt><dt><span class="sect2"><a href="#id745432">25.1.2. RPM locator sites</a></span></dt><dt><span class="sect2"><a href="#id626826">25.1.3. RPM tools sites</a></span></dt><dt><span class="sect2"><a href="#id823415">25.1.4. Programming sites</a></span></dt><dt><span class="sect2"><a href="#id574081">25.1.5. Sites related to RPM</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id652975">25.2. Accessing RPM Mailing Lists and Newsgroups</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-development-tools">26. Linux Text Editors and Development Tools</a></span></dt><dd><dl><dt><span class="sect1"><a href="#id928395">26.1. General Text Editors</a></span></dt><dt><span class="sect1"><a href="#id788731">26.2. Programming Text Editors</a></span></dt><dt><span class="sect1"><a href="#id773190">26.3. Integrated Development Environments for C Programming</a></span></dt><dt><span class="sect1"><a href="#id73
7936">26.4. Integrated Development Environments for Python Programming</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-licensing">27. Licensing RPM</a></span></dt><dd><dl><dt><span class="sect1"><a href="#id699117">27.1. The GNU General Public License</a></span></dt></dl></dd><dt><span class="appendix"><a href="#appe-Publican-Revision_History">A. Istoria reviziilor</a></span></dt><dt><span class="index"><a href="#id634964">Index</a></span></dt></dl></div><div xml:lang="ro" class="preface" id="ch-intro-packaging" lang="ro"><div class="titlepage"><div><div><h1 class="title">Introducing Package Management</h1></div></div></div><div class="para">
+ This chapter covers:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Issues in software management
+ </div></li><li class="listitem"><div class="para">
+ Examining Linux management tools
+ </div></li><li class="listitem"><div class="para">
+ Introducing the package concept
+ </div></li></ul></div><div class="para">
+ In 1991, a young Finnish graduate student started a new personal hobby. He had acquired an Intel 386 computer and had spent a few weeks exploring it and playing early PC computer games. Eventually, however, he grew bored with the limitations of the MS-DOS environment that had come with his toy and decided that he wanted an operating system for it that he could use more productively. After exploring Minix, a feature-limited teaching operating system, he decided he needed a full-featured OS.
+ </div><div class="para">
+ At that time, no full-featured PC operating systems were freely available, so he decided to write his own operating system. Today, that small hobby OS that Linus Torvalds started almost as a whim has become Linux, a significant new variant of Unix that runs millions of the world's network servers and, increasingly, desktop computers and embedded processors.
+ </div><div class="para">
+ Linux has grown up, successfully making the transition from a one-man personal project to a functional, full-featured operating system used by many of the world's major corporations and deployed on millions of corporate and personal systems. Along the way, Linux has had to address many of the same issues any new operating system must face. One of these concerns is how software for Linux, and how the Linux operating system itself, should be installed. How can administrators safely remove software packages without affecting other installed packages? And how can you safely upgrade packages? Answering these questions is what this book is all about.
+ </div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id744074" class="title">Installing, Removing, and Upgrading Applications</h1></div></div></div><div class="para">
+ Applications for most operating systems consist of multiple files that must be copied to specific locations on the computer's file system before each application can be run. This is true for common PC operating systems such as MS-DOS or Microsoft Windows, as well as for Unix and Linux.
+ </div><div class="para">
+ In the case of a Unix-like operating system such as Linux, other issues must also be considered. Unix and Linux are multiple-user systems, so they must track ownership of files. Furthermore, Unix and Linux use a system of file permissions. Administrators can grant some users access to files and can control how users may access those files, for example, allowing some users the permission to read only certain files. Administrators can deny other users access to the same files. So, installation of an application on Linux requires consideration of all these details. After files are copied into their appropriate locations, they must be granted correct permissions and correct ownerships.
+ </div><div class="para">
+ Similarly, administrators occasionally need to remove installed software from the computer. Maybe the program is no longer needed; maybe it does not work correctly for the needed task, or maybe the space it is using is needed for more important programs. In addition, installed software sometimes needs to be upgraded. Perhaps a new version of the software has come out and the currently installed version needs to be replaced with the presumably improved version. In most respects, software upgrades are the same as the removal of one application (the old version), followed by installation of another application (the new version). Upgrades do, however, have additional issues. Many applications must be configured before they can be used. Ideally, the upgrade for an installed application takes the current configuration into account, preserving old configuration information and applying it to the recently installed version.
+ </div><div class="para">
+ All these considerations make installation of a new application onto Unix or Linux a labor-intensive process. To further complicate matters, Unix applications have primarily been distributed as source code. To install a new application, such as the Apache Web server, you download the source code for that application—in this case, from the Apache Project's Web page (<a href="http://httpd.apache.org">http://httpd.apache.org</a>). Typically, the source code is provided in some sort of archive (such as the Zip archival and compression format often used in the Windows world or the tar archive format typically used in the Unix world) that you must then unpack. After unpacking this source code, you have to configure it to support the options and systems you want, compiling it to produce an executable program that can run on your particular operating system (CPU combination).
+ </div><div class="para">
+ After compiling the source code, you still have to install the application by putting all of its components (executable programs, documentation, configuration files, and so forth) into the correct locations on your hard drive and setting correct permissions on all those files. You might also need to perform other steps to prepare the system for the software. In the case of Apache, for example, some space needs to be set aside for storage of Web-access logs, and a special user account needs to be created so that the Apache Web server can operate more securely. Finally, you are ready to try running the application you have spent so much time installing.
+ </div><div class="para">
+ To help with all these tasks, precompiled software is becoming increasingly prevalent in the Unix and Linux communities, so you might be able to find executable (precompiled binary) copies of the application you wish to install that are appropriate for your particular machine's CPU. In that case, download an archive of the compiled application and unpack it. Then skip the compilation step, since that has already been done for you. The other steps required to install the package (copying files into correct locations, setting file permissions, and doing any needed system or application configuration) are exactly the same as the steps performed to install that application from source code. Once those steps are finished, you are ready to test your freshly installed application.
+ </div><div class="para">
+ When you run your newly installed application, you might be thrilled, perhaps discovering that it is something you want to use regularly. On the other hand, you might discover that you have no use for the software you have just installed, deciding that you want to uninstall it.
+ </div><div class="para">
+ Uninstallation occurs by reversing the installation steps. Remember any special steps you have performed (such as adding a user account), and undo those. Then remember all the files you have installed and where you have installed them. Manually delete them. As you can see, this can become a pretty tedious exercise.
+ </div><div class="para">
+ If you like the application you have installed, you will likely find yourself wanting to upgrade it eventually. The Apache Web server, for example, like any network service, must be upgraded whenever security problems are found and fixed. If you find that you need to upgrade Apache, you need to back up your Apache configuration files and then uninstall Apache. The next step is to install a new version of Apache, applying your Apache-configuration customizations to your new installation of Apache.
+ </div><div class="para">
+ All of this is a big pain. There has to be a better way. And there is.
+ </div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id870642" class="title">Overcoming the Installation Obstacles</h1></div></div></div><div class="para">
+ None of the tasks you must perform to install, upgrade, or uninstall applications are especially difficult. However, these steps quickly become daunting when you consider all the files that must be managed. A full Fedora installation provides around 3,000 executable commands and over 160,000 total files (some other Linux distributions are even larger!). Obviously, managing all these files by hand, although theoretically possible, is not technically feasible. On a smaller scale, even management of single applications is not practical. The Postfix e-mail server application, for example, consists of around 275 files scattered in a dozen or so different directories. Imagine trying to remember and manually remove all of those files (and only those files) to uninstall Postfix from your system!
+ </div><div class="para">
+ All the steps needed to manage software on Unix or Linux systems are hardly unique to Unix; all operating systems have similar procedures that must be followed to make software usable on the system. For this reason, many approaches have been adopted toward software installation, uninstallation, and upgrading.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id775456" class="title">Application-level utilities</h1></div></div></div><div class="para">
+ Some operating systems, such as MS-DOS, have supplied absolutely no built-in tools for software management. Installation of applications on such systems occurs in one of two ways: software is installed manually, using file-copy utilities to put all the application files in the appropriate places on the system, or software is installed using a custom-written installation application (as is usually the case for MS-DOS applications).
+ </div><div class="para">
+ Once installed, software can be uninstalled in one of two ways: you can manually delete each file installed for the application (assuming you can even remember them all), or the application might come with a custom uninstallation utility that can be run to remove the application. Upgrading an already installed application on such a system uses a similar procedure. If the application comes with an installation utility capable of handling application upgrades, you can use the utility to perform the upgrade. Otherwise, the software must be manually upgraded using the procedure described previously.
+ </div><div class="note"><div class="admonition_header"><h2>Current Windows Versions</h2></div><div class="admonition"><div class="para">
+ Current versions of Windows, such as Windows XP, have a central database of installed applications.
+ </div></div></div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id1414533" class="title">Built-in system utilities</h1></div></div></div><div class="para">
+ Other operating systems have come with built-in utilities that a system administrator can use to manage the system’s software. These utilities can be run to install the software on the system; typically, they take some of the work out of manually installing software, dealing with issues such as figuring out which files need to be put where on the system. Once installed, these utilities typically track the files that have been installed. This knowledge can usually be used to uninstall those applications automatically. Since the software knows which files are associated with the application, it can be told to uninstall the application, and it can find and delete all the files that belong to that application.
+ </div><div class="para">
+ These built-in utilities typically come in two different forms. One type focuses on managing the installation process, providing custom utilities that can be used to perform the otherwise manual tasks of compiling software and copying files into their final locations. The three major freely available Berkeley Unix, or BSD, operating systems, NetBSD, FreeBSD, and OpenBSD, for example, ship with a software-management system called, variously, ports (FreeBSD and OpenBSD) or packages (NetBSD).
+ </div><div class="para">
+ The ports system is composed of extensions to the normal Unix software-compilation utilities that help it automate and track many of the steps of a standard source-code compilation. When using ports, you still download source code, unarchive it, configure it, compile it, and install it, but the ports software automates many of these steps. Furthermore, the ports system does limited tracking of the files it installs. Although it does not offer more advanced features (such as an interface to search all installed files to see what application supplied that file) or the ability to upgrade installed applications, it does provide the ability to uninstall applications that are installed using ports. These sorts of limitations are typical of management applications that function as the ports system does, by enhancing the compilation and installation phases of application installation. The packages system on NetBSD has similar limitations.
+ </div><div class="para">
+ Other system-management utilities focus less attention on compiling an application for installation and more attention on the files that must be installed on the system after the application has been compiled.
+ </div><div class="para">
+ For example, the standard System V Unix package-management software supplied with most commercial Unix systems (Sun's Solaris, for example) devotes no attention to management of software compilation at all. Instead, it tracks the individual files associated with each application in a system database.
+ </div><div class="para">
+ To install software using the System V tools, you must compile the software. After compiling the software in the standard fashion, prepare a list of the files from that compilation that need to be installed on the system. Be certain to state where the files need to be installed and what permissions and ownerships they need to have once installed. Then run a series of commands that look at this list, find the files listed in it, and archive them into one file, along with a copy of this list that specifies where they should be installed and the ownerships and permissions. This single archive file can then be transferred to other machines, where a System V software-management command can be used to install it. This System V installation command (typically called <code class="command">pkgadd</code>) unpacks the archive, copies the files into their final destinations based on the enclosed listing, and sets permissions and ownerships on the files as specified by the listing. Fin
ally, this <code class="command">pkgadd</code> command registers the list of freshly installed files into a system-wide database of installed files.
+ </div><div class="para">
+ Such a system offers several advantages over manual software installation. Software can now be installed and uninstalled easily, and the system-wide database of installed files can be readily searched to locate installed applications and files. However, this sort of system also has severe limitations; it is far less flexible in the software-configuration stages than software such as the FreeBSD ports system, which offers great control over the software-compilation stage of software installation.
+ </div></div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id488776" class="title">Linux Software Management Tools: Packages</h1></div></div></div><div class="para">
+ Initially, Linux had neither type of software-management tool. In the early days of Linux, you installed Linux by cross-compiling it under a different operating system (Minix), then manually installing the compiled Linux programs into the appropriate locations to produce a working system. As Linux has matured, however, it has acquired software-management tools that have made software installation, removal, and upgrade significantly easier than in the early days. The exact software-management tool used on modern Linux systems varies from distribution to distribution, but both approaches to system management can be found in the tools used by various distributions.
+ </div><div class="para">
+ The Gentoo Linux (<a href="http://www.gentoo.org/">http://www.gentoo.org/</a>) distribution, for example, uses a software-management system called Portage, which is very similar to the FreeBSD ports system. Like ports, Portage provides great control over software compilation and installation, providing a collection of scripts that automate much of the basic work of downloading and compiling software.
+ </div><div class="para">
+ At the other end of the spectrum, the now-defunct deepLinux distribution used a software-management system called <code class="command">deep-package</code>. <code class="command">deep-package</code> was intended to be a complete reimplementation of the Solaris <code class="command">pkgadd</code> utility and its helpers. Like the Solaris <code class="command">pkgadd</code> software, <code class="command">deep-package</code> paid no attention to half of the question of how to manage software, focusing entirely on software installation and tracking issues while entirely ignoring the initial compilation of the software.
+ </div><div class="para">
+ More typically, however, Linux software-management tools use an approach somewhere between the two extremes represented by Portage and deep-package. Most Linux software-management tools provide software that manages the compilation of software, similarly to the FreeBSD ports tools. However, these software-management tools typically produce packages from the software they compile. Much like the archives produced by the System V software-management tools, packages are simply archive files that contain two things: a collection of related files, which together have a common use, and a script that provides all the metadata about those files necessary to install and manage those files.
+ </div><div class="para">
+ Typically, packages represent applications. For example, a Postfix package contains the 275 files that make up Postfix and a script that specifies where on the system those 275 files need to be placed, as well as what permissions and ownership those files need. A single command can then take this Postfix package file, extract its 275 archived files, and use the script to place those files correctly on the system.
+ </div><div class="para">
+ In addition, most Linux software-management tools have a database component that tracks files and applications that have been installed using the package-management software, helping the package manager do its job of easing the management of installed software.
+ </div><div class="para">
+ In the case of a full Fedora installation, this package-management software maintains a database of information regarding all 160,000 files on the system; as applications are installed on the system, this database is updated with information regarding the new application and the locations of its component files. This database is the key component, making it possible to manage the system. Since this database remembers which 275 files compose the Postfix application, it ensures that I can uninstall Postfix with a single command that accesses this database, without my having to remember the locations of all 275 files that make up the Postfix application.
+ </div><div class="para">
+ A wide variety of software-management tools are available for Linux to help lessen the work involved with installing, removing, and upgrading applications installed on the system. This book focuses on one of these tools, the RPM Package Management software, or RPM.
+ </div><div class="note"><div class="admonition_header"><h2>Change of Name</h2></div><div class="admonition"><div class="para">
+ RPM was originally called Red Hat Package Manager. After adoption by other Linux distributions, the name has changed to simply the RPM Package Manager. The RPM initials remain the same.
+ </div></div></div><div class="para">
+ As the original name implies, RPM was developed by Red Hat, Inc., the major Linux distributor in the United States. Even though the original name seems to point to a Red Hat-only solution, most Linux distributions use the RPM software. The RPM software provides a foundation needed by Linux system administrators throughout the world. You can even use RPM on other operating systems, both Linux and non-Linux, as covered in <a class="xref" href="#ch-other-linuxes">Cap. 18, <em>Using RPM on Non-Red Hat Linuxes</em></a> and <a class="xref" href="#ch-other-os">Cap. 19, <em>RPM on Other Operating Systems</em></a>, respectively.
+ </div><div class="para">
+ The RPM system provides all of the features needed to manage applications, including a database of installed packages with their version numbers, the ability to install, remove, and update packages, and the ability to recompile an application from a source code RPM package.
+ </div><div class="para">
+ The remaining chapters in Part I go into depth on what you can do with RPM packages and the commands you need to work with the RPM system:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ <a class="xref" href="#ch-intro-rpm">Cap. 1, <em>Introduction to RPM</em></a> provides an overview of the RPM system, exploring what it was designed for and where it has weaknesses.
+ </div></li><li class="listitem"><div class="para">
+ <a class="xref" href="#ch-rpm-overview">Cap. 2, <em>RPM Overview</em></a> discusses the technical details of how the RPM system works, where the database of packages gets stored, and what commands should be available for working with RPM packages.
+ </div></li><li class="listitem"><div class="para">
+ <a class="xref" href="#ch-using-rpm">Cap. 3, <em>Using RPM</em></a> continues the discussion by covering the three major tasks you need to perform with RPM packages: installing software, removing software, and upgrading software you have already installed.
+ </div></li><li class="listitem"><div class="para">
+ <a class="xref" href="#ch-using-rpm-db">Cap. 4, <em>Using the RPM Database</em></a> covers the RPM database, how it works, where it resides, and how you can use it to better manage your system.
+ </div></li><li class="listitem"><div class="para">
+ <a class="xref" href="#ch-dependencies">Cap. 5, <em>Package Dependencies</em></a> delves into package dependencies, a very important concept. Most major applications depend on a number of other packages. Sometimes these dependencies get very complex, with one package depending on particular versions of other packages. With thousands of packages on your system, this can lead to a big mess. This chapter helps you to sort through the issues.
+ </div></li><li class="listitem"><div class="para">
+ <a class="xref" href="#ch-transactions">Cap. 6, <em>Transactions</em></a> covers the important issue of transactions, so that you can ensure your system gets updated in an orderly manner and so that you can roll back changes if something does not work out.
+ </div></li><li class="listitem"><div class="para">
+ <a class="xref" href="#ch-management-software">Cap. 7, <em>RPM Management Software</em></a> introduces a host of tools that can help you find RPM packages as well as manage the packages on your system. This includes graphical interfaces on top of the RPM system and special Internet search sites devoted just to RPM packages.
+ </div></li></ol></div><div class="para">
+ Later chapters cover creating RPM packages, programming with RPM, and extending the functionality provided by the base RPM system.
+ </div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id593047" class="title">Summary</h1></div></div></div><div class="para">
+ Modern operating systems have large complex sets of applications, resulting in thousands of files to keep track of for upgrades, installation, and removal of packages. All this complexity has lead Linux vendors to develop a variety of package-management tools.
+ </div><div class="para">
+ This chapter briefly introduced the RPM Package Manager, or RPM for short. The next chapter provides an overview of the RPM system, showing how all the parts fit together.
+ </div></div></div><div xml:lang="ro" class="chapter" id="ch-intro-rpm" lang="ro"><div class="titlepage"><div><div><h2 class="title">Cap. 1. Introduction to RPM</h2></div></div></div><div class="toc"><dl><dt><span class="sect1"><a href="#id822579">1.1. The Need for Linux Package Management Systems</a></span></dt><dt><span class="sect1"><a href="#id787809">1.2. RPM Design Goals</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id978840">1.2.1. Ease of use</a></span></dt><dt><span class="sect2"><a href="#id1356769">1.2.2. Package-oriented focus</a></span></dt><dt><span class="sect2"><a href="#id939937">1.2.3. Package upgradability</a></span></dt><dt><span class="sect2"><a href="#id556947">1.2.4. Package interdependencies</a></span></dt><dt><span class="sect2"><a href="#id633500">1.2.5. Query capabilities</a></span></dt><dt><span class="sect2"><a href="#id485232">1.2.6. Package verification</a></span></dt><dt><span class="sect2"><a href="#id734929">1.2.7. Multiple archit
ectures</a></span></dt><dt><span class="sect2"><a href="#id855386">1.2.8. Pristine sources</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id532045">1.3. RPM Terminology</a></span></dt><dt><span class="sect1"><a href="#id627397">1.4. Summary</a></span></dt></dl></div><div class="para">
+ This chapter covers:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Examining the history of package management
+ </div></li><li class="listitem"><div class="para">
+ Introducing RPM features
+ </div></li><li class="listitem"><div class="para">
+ Getting acquainted with RPM terminology
+ </div></li></ul></div><div class="para">
+ Several package managers are available for Linux to track and manipulate the applications installed on the system. The most widely used of these Linux package managers is the RPM Package Manager (formerly the Red Hat Package Manager), or RPM for short, the subject of this book
+ </div><div class="para">
+ Although RPM was initially developed for Red Hat Linux, a combination of technical features and good timing has resulted in RPM’s becoming the de facto standard for packaging software on most Linux distributions. The fact that Red Hat released the source code to the RPM software under an open-source license also helped its adoption.
+ </div><div class="para">
+ More recently, the RPM package file format has been adopted as the official standard for Linux as part of the Linux Standards Base, or LSB. Described at <a href="http://www.linuxbase.org/">http://www.linuxbase.org/</a>, the Linux Standards Base is an attempt to set a baseline that all Linux distributions should follow. The LSB has helped system administrators by providing some commonality across distributions, as in the location of certain files. The history of Linux package managers is largely intertwined with the history of Linux distributions.
+ </div><div class="para">
+ Strictly speaking, Linux refers to a single piece of software, the Unix-like kernel that Linus Torvalds and cohorts have scattered all over the Internet and have been developing since 1991. This Linux kernel is a marvelous piece of software, currently comprising over 3.7 million lines of freely-licensed source code and accompanying documentation. Together, these factors provide a fast, full-featured, stable operating system kernel for use on more than 30 different processor architectures, ranging from embedded systems such as watches and PDAs, to desktop and server systems, all the way up to mainframes and supercomputing clusters.
+ </div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id822579" class="title">The Need for Linux Package Management Systems</h1></div></div></div><div class="para">
+ Although Linux is an excellent core component of an operating system suitable for a wide variety of real-world applications, this Linux kernel by itself is not sufficient for accomplishing most tasks. The technical definition of exactly what constitutes an operating system is a matter of debate.
+ </div><div class="para">
+ Despite this controversy, it is clear that most users of Linux require both the Linux kernel and a large suite of accompanying software (a shared C library; traditional Unix utilities such as <code class="command">grep</code>, <code class="command">awk</code>, and <code class="command">sed</code>; an editor, such as <code class="command">vi</code>; a shell, such as the Bourne-Again <code class="command">bash</code> shell; and so forth) to complete the various tasks for which they typically employ Linux.
+ </div><div class="para">
+ Users expect Linux to include server software such as the Apache Web server, desktop software such as the OpenOffice.org office productivity suite, and a host of other packages. In fact, most Linux users don’t make the distinction between the kernel (technically the only part that is Linux) and all the extra packages (technically “everything elseâ€) that comes with a Linux distribution. Most users simply refer to the whole thing as “Linux.â€
+ </div><div class="para">
+ Some Linux distributions include thousands of packages on six or more CD-ROMs. This situation alone cries out for effective package-management software. And this doesn’t include the extra packages that don’t come with Linux distributions but which organizations need to create an effective working environment.
+ </div><div class="para">
+ Furthermore, the Linux kernel and these various software applications are typically made available by their developers in source code formats only, and they can be installed manually only after compiling them from source code.
+ </div><div class="para">
+ Most people do not have the technical skills necessary to cross-compile an entire operating system. Even if they do, they usually do not want to devote the time and effort required to bootstrap and compile an operating system just to be able to run Linux.
+ </div><div class="para">
+ Fortunately, the early Linux programmers quickly realized the impracticality of source-code only releases early in Linux's development and created what they called distributions—collections of precompiled binaries of the Linux kernel and other necessary software that users often wanted. Rather than installing Minix, compiling the Linux kernel and other required software applications under Minix, and installing those compiled binaries of the Linux kernel and essential Linux applications, users could just install these distributions, immediately having a functional Linux environment in which to work.
+ </div><div class="para">
+ Early distributions, such as MCC and SLS, initially represented little more than archived snapshots of their developer's hard drive. They offered the user performing the installation little or no control over what applications were put on the system. Whatever the distribution developer had on his hard drive was what the distribution installer got on her hard drive. Even this was much better than rolling your own distribution by hand. SLS, for example, stood for Soft Landing System, and was designed to make the experience of installing Linux easier, hence providing a “soft landing.†MCC Interim Linux, from the Manchester Computing Centre, was the first distribution to sport a combined boot/root disk, another attempt to make life easier for those adopting Linux.
+ </div><div class="para">
+ Distribution developers quickly realized, however, that more flexibility was needed and began looking for ways to provide choices both during and after installation. The Slackware distribution, for example, divided applications into several functional categories. All users installed the base distribution; users could then selectively install only the additional supplemental categories they needed. If networking support was desired, for example, the networking bundle could be installed. Similarly, if a graphical user interface was desired, the X bundle could be installed, making the X Window System available. This concept offered rudimentary control over what was installed but only at a very coarse level. Installing the X bundle put several applications (multiple X terminal emulators, several different window managers, and so forth) on the system, and all users who installed the bundle got all of those applications whether they wanted them all or not.
+ </div><div class="para">
+ The next logical step in distribution evolution was the development of more advanced tools to control what was installed. Several distributions independently developed the notion of application-level installation management. The developers of these distributions realized that Slackware and similar distributions were heading in the right direction, but simply had not made software management granular enough. Slackware allowed installation and uninstallation (after a fashion) of bundles of related applications, but what was really needed was installation and uninstallation on an application-by-application basis.
+ </div><div class="para">
+ In late 1993, Rik Faith, Doug Hoffman, and Kevin Martin began releasing the first public betas of the BOGUS Linux distribution. BOGUS was notable for the package management system (<code class="command">pms</code>) software that was used with it for installation and uninstallation of all software on an application-by-application basis. Shortly thereafter, in the summer of 1994, the first public betas of Red Hat Commercial Linux were released. Red Hat initially used Red Hat Software Program Packages (RPP) as the basis of its Linux distribution. Like <code class="command">pms</code>, RPP was a system-management tool that allowed for easy installation and uninstallation of applications. In late 1993, Ian Murdock founded the Debian Gnu/Linux distribution. He began seriously developing its <code class="command">dpkg</code> application-management software by the summer of 1994. Like <code class="command">pms</code> and RPP, <code class="command">dpkg</code> made it possible to m
anage each application on the system.
+ </div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id787809" class="title">RPM Design Goals</h1></div></div></div><div class="para">
+ All of these early system-management tools took a similar approach. They provided the capability to install an entire application with a single command, to track the files it put on the system, and to remove those files by using another single command. As the preponderance of multiple early tools suggests, this approach to system management was popular. All of these early tools, however, had numerous technical or practical deficiencies. Some tools were designed only for Linux on 32-bit Intel-compatible hardware, even though Linux by this point was already running on other CPUs in addition to the IA32 family. As Linux was spreading to multiple architectures, a package-management system that could produce packages for multiple architectures was needed. Other tools had technical flaws in how they prepared packages, making it difficult to verify that packages had been prepared correctly or to see exactly how the software was prepared.
+ </div><div class="para">
+ Because of these concerns, after their initial releases of RPP-based distributions, Red Hat looked closely at both their own RPP software and other software such as BOGUS's <code class="command">pms</code> software. Developers at Red Hat, particularly Marc Ewing and Erik Troan, set out to develop what they initially called the Red Hat Package Manager (RPM). Based on experiences with earlier Linux packaging software and knowledge about packaging tools used on other platforms, Red Hat had several design goals in mind when they developed RPM. These design points include the following features:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Ease of use
+ </div></li><li class="listitem"><div class="para">
+ Package-oriented focus
+ </div></li><li class="listitem"><div class="para">
+ Upgradability of packages
+ </div></li><li class="listitem"><div class="para">
+ Tracking of package interdependencies
+ </div></li><li class="listitem"><div class="para">
+ Query capabilities
+ </div></li><li class="listitem"><div class="para">
+ Verification
+ </div></li><li class="listitem"><div class="para">
+ Support for multiple architectures
+ </div></li><li class="listitem"><div class="para">
+ Use of pristine sources
+ </div></li></ul></div><div class="para">
+ The following sections demonstrate how Red Hat incorporated each of these design goals into RPM.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id978840" class="title">Ease of use</h1></div></div></div><div class="para">
+ Perhaps the primary design goal for RPM is that it must be easy to use. Manual software installation has been the primary method of putting software onto Unix boxes for over 30 years now and has worked very well for those three decades. To offer a compelling reason to use the new software, RPM must be significantly easier to use than other Linux package-management tools. For that reason, most tasks that can be handled using RPM were designed to be carried out via a single command. For example, software installation using RPM requires a single command (<strong class="userinput"><code>rpm -U software_package</code></strong>), while manual software installation using older manual methods typically requires at least six steps to complete the same task:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ <code class="command">tar zxf <em class="replaceable"><code>software_package</code></em></code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">cd <em class="replaceable"><code>software_package</code></em></code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">./configure</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">make</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">su</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">make install</code>
+ </div></li></ol></div><div class="para">
+ Similarly, removal of applications installed using RPM requires a single command (<strong class="userinput"><code>rpm -e <em class="replaceable"><code>software_package</code></em></code></strong>); manual removal of an installed application requires that each file associated with that application be manually deleted.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id1356769" class="title">Package-oriented focus</h1></div></div></div><div class="para">
+ Like its predecessors, RPM is intended to operate on a package level. Rather than operating on a single-file basis (as when you manually install software using Unix command-line tools like mv and cp) or on an entire system basis (as with many PC operating systems, which provide the ability to upgrade entire releases but not to upgrade individual components), RPM provides software that can manage hundreds or thousands of packages.
+ </div><div class="para">
+ Each package is a discrete bundle of related files and associated documentation and configuration information; typically, each package is a separate application. By focusing on the package as the managed unit, RPM makes installation and deletion of applications extremely straightforward.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id939937" class="title">Package upgradability</h1></div></div></div><div class="para">
+ In addition to its package-oriented focus, RPM is designed to support upgrading packages. Once an application has been installed from an RPM package, a newer version of the same application can be installed using RPM. Doing so upgrades the existing application, removing its old files and replacing them with new files. In addition, however, RPM takes care to preserve any customizations that have been made to that application. The Apache Web server application, for example, is commonly installed on Linux machines that need the ability to serve Web pages.
+ </div><div class="para">
+ Apache's configuration information, which specifies things such as which files on the system should be made available as Web pages and who should be able to access those Web pages, is stored in a text file, typically <code class="filename">/etc/httpd/conf/httpd.conf</code>. Suppose Apache has been installed using RPM and that you have then customized <code class="filename">httpd.conf</code> to specify its configuration. If you upgrade Apache using RPM, as part of the upgrade procedure, the RPM application will take precautions to preserve the customizations you have made to the Apache configuration. In contrast, manual upgrades of applications often overwrite any existing configuration files, losing all site customizations the system administrator has made.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id556947" class="title">Package interdependencies</h1></div></div></div><div class="para">
+ Software that manages the applications installed on the system on an application level (such as RPM) does have one potential drawback in comparison with system-wide software management systems (such as PC operating systems like Microsoft Windows or OS/2, which allow the entire system to be upgraded but do not generally allow individual components to be upgraded, added, or removed). Software applications often have interdependencies; some applications work only when other applications are installed.
+ </div><div class="para">
+ The Postfix and Sendmail mail transfer agent (MTA) applications that are commonly used on Linux boxes to serve e-mail, for example, can both be configured to require users to authenticate themselves (by submitting a correct user name and password) successfully before they can use the e-mail server. This feature is often used to prevent unauthorized access to the e-mail server, preventing unscrupulous advertisers from using the server as a tool to send unsolicited commercial e-mail (or UCE, popularly known as spam). For this optional feature of Postfix and Sendmail to work, however, additional software must be installed. Both applications use another application, Cyrus SASL, which provides the Simple Authentication and Security Layer (SASL) software that Postfix or Sendmail can use to check user names and passwords. In other words, Postfix and Sendmail depend on Cyrus SASL.
+ </div><div class="para">
+ For system-wide software management systems, logical interdependencies between system components such as these are easy to track. All required components are included as part of the system, and upgrading the system upgrades all these components, ensuring that all can still interoperate. On Microsoft Windows 2000, IIS (the application used on Windows to serve Web pages) requires several other applications such as <code class="command">EventLog</code> (the Windows application that records system events, much like the Linux <code class="command">syslogd</code> and <code class="command">klogd</code> software) to be present. Since Windows is managed on a system level, not a package level, this dependency is guaranteed to be satisfied. On Linux systems using RPM, however, the situation is different. On Linux, for example, the Postfix application requires the <code class="command">syslogd</code> application, which records system events. However, RPM provides the flexibility to in
stall some applications but not install others or to uninstall others later. When you install Postfix, you have no guarantee that <code class="command">syslogd</code> is already installed. If <code class="command">syslogd</code> is not installed, Postfix will not work correctly.
+ </div><div class="para">
+ To avoid problems, Red Hat developers realized that RPMs must also track dependency information about what software they require for correct functionality, and that the RPM install and uninstall applications must use this dependency information. Because of dependencies, installing Postfix using RPM on a system without <code class="command">syslogd</code> installed generates a warning that <code class="command">syslogd</code> must also be installed. Similarly, attempting to uninstall <code class="command">syslogd</code> from a system that already has Postfix installed generates a warning that installed applications require the software that is being deleted. These warnings can be overridden if necessary, but by default RPM enforces these dependencies (refusing, for example, to let you uninstall <code class="command">syslogd</code> without also uninstalling applications that require it, such as Postfix), preventing you from accidentally breaking applications by inadvertently
uninstalling other software that they require to operate.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id633500" class="title">Query capabilities</h1></div></div></div><div class="para">
+ As part of its implementation, the RPM software maintains a database on the system of all packages that have been installed, and documenting which files those packages have installed on the system. RPM is designed to be queried easily, making it possible for you to search this database to determine what applications have been installed on the system and to see which packages have supplied each file on the system. This feature makes RPM-based systems extremely easy to use, since a single RPM command can be used to view all installed applications on the system.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id485232" class="title">Package verification</h1></div></div></div><div class="para">
+ RPM also maintains a variety of information about each installed file in this system database, such as what permissions each file should have and what size each file should be. Red Hat developers designed this database to be useful for software verification. Over time, installed software will fail to work for reasons as mundane as the system administrator setting incorrect permissions on files or as exotic as nuclear decay of one of the computer's atoms releasing an alpha particle that can affect the computer's memory, corrupting that bit of memory and causing errors. Although RPM cannot prevent all errors that cause installed software to fail (obviously, there's not a single thing any software can do to prevent nuclear decay), it can be used to eliminate common errors. When an application fails, you can use the RPM database to make sure that all files associated with that application still have correct Unix file permissions and that no files associated with that applicati
on have become altered or corrupted.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id734929" class="title">Multiple architectures</h1></div></div></div><div class="para">
+ Most of the RPM design goals mentioned so far are intended primarily to ease the life of system administrators and others who regularly install, remove, and upgrade applications or who need to see what is installed or verify that installed applications have been installed correctly. Some of the design goals for RPM are intended primarily not for those sorts of users of RPM but for users who must prepare software to be installed using RPM.
+ </div><div class="para">
+ One of the major limitations of early Linux package management utilities was that they could produce packages suitable only for installation on one type of computer: those that used 32-bit Intel-compatible CPUs. By 1994, Linux was beginning to support other CPUs in addition to the originally supported Intel CPUs. (Initially, Digital's Alpha processor and Motorola's 68000 series of processors were among the first additional CPUs that Linux supported. These days, Linux supports dozens of CPU architectures.) This posed a problem for distribution developers such as Red Hat and Debian, and for application vendors who desired to package their software for use on Linux. Because the available packaging methods could not produce packages for multiple architectures, packagers making software for multiple CPUs had to do extra work to prepare their packages.
+ </div><div class="para">
+ Furthermore, once the packagers had prepared packages, no method was available to indicate the architecture the packages targeted, making it difficult for end users to know on which machine types they could install the packages.
+ </div><div class="para">
+ Red Hat decided to overcome these limitations by incorporating architecture support into RPM, adding features so that the basic setup a packager performs to create a package could be leveraged to produce packages that would run on various CPUs, and so that end users could look at a package and immediately identify for which types of systems it was intended.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id855386" class="title">Pristine sources</h1></div></div></div><div class="para">
+ The BOGUS distribution's <code class="command">pms</code> packaging system introduced the use of pristine source code to prepare packages. With Red Hat's early RPP package system and other similar early efforts, software packagers would compile software manually, then run commands to produce a package of that compiled software. Any changes made to the application's original source code were not recorded and would have to be recreated by the next person to package that software. Furthermore, end users wanting to know what changes had been made to the software they were running had no method of accessing that information.
+ </div><div class="para">
+ With RPM, Red Hat developed a package system that produced two types of packages: binary and source. Binary packages are compiled software that can be installed and used. Source packages contain the source code for that software, along with a file documenting how that source code must be compiled to produce that binary package. This feature is probably the single most significant difference between modern Linux packaging software (such as RPM) and the packaging software used on other systems (such as the pkg format that commercial Unix systems use). Source packaging makes the job of software packager easier, since packagers can use old source packages as a reference when preparing new versions of those packages. Source packages are also convenient for the end user, because they make it easily possible to change options with which that software was compiled and to produce a new binary package that supports the features the user needs.
+ </div></div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id532045" class="title">RPM Terminology</h1></div></div></div><div class="para">
+ When working with RPM, understanding the package concept is key. RPM packages are provided as compressed archive files that contain one or more files, as well as instructions specifying installation information about those files, including the ownerships and permissions that should be applied to each file during installation. The instructions can also contain scripts to be run after installation or before uninstallation. These package files are extremely convenient; they provide a single file that can be easily transferred between machines for installation rather than having to transfer each file to be installed.
+ </div><div class="para">
+ To help in installation and management, all package files are labeled with highly identifiable names. Package files have four-part names, which typically look something like:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">kernel-smp-2.6.32.9-3.i686.rpm</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">kernel-smp-2.6.32.9-3.x86_64.rpm</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">kernel-smp-2.6.32.9-3.ppc.rpm</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">rootfiles-7.2-1.noarch.rpm</code>
+ </div></li></ul></div><div class="para">
+ Here, the four parts of each name are separated from each other by dashes or periods. The structure of the package file name is
+ </div><div class="para">
+ <code class="filename">name-version-release.architecture.rpm</code>
+ </div><div class="para">
+ The name identifies what software is contained within the archive file. Typically, this is a name of an application or package that the archive installs on the system. For example, <code class="filename">kernel-smp</code> can be installed to provide a very important application, the SMP (symmetric multiprocessing, meaning it supports systems with more than one CPU in them) version of the Linux kernel, on the system. Sometimes, rather than an application, the software is a collection of other files needed on the system. The <code class="filename">rootfiles</code> package, for example, is not an application but is a collection of basic environmental configuration files for the <code class="systemitem">root</code> user's account (such as <code class="filename">/root/.bashrc</code>, the <code class="systemitem">root</code> user's Bash configuration file) that provides a usable, preconfigured working environment for the <code class="systemitem">root</code> user.
+ </div><div class="para">
+ The second field in every package file's name is the version field. This field identifies the version number of the software that is contained in the package file. For example, <code class="filename">kernel-smp-2.6.32.9</code> indicates the RPM holds the 2.6.32.9 release of the SMP version of the Linux kernel, and <code class="filename">rootfiles-7.2</code> is the 7.2 release of the <code class="filename">rootfiles</code> configuration files.
+ </div><div class="para">
+ Every package file name also has a third component: the release field. This field identifies which release of that version of the software the package file contains. Package files contain both software and instructions about how to install that software. As packages of a particular version of software are being prepared, mistakes are sometimes made in these instruction files, or bugs are sometimes fixed within a software version; more recent package files of that software version need to be prepared that correct the problem. The –1 in the <code class="filename">rootfiles-7.2-1</code> package shows this is the first release of the 7.2 version of the <code class="filename">rootfiles</code> software. The packager of <code class="filename">rootfiles</code> version 7.2 got everything right on the first try and had no need to prepare more than one release. The –3 in the <code class="filename">kernel-smp-2.6.32.9-3</code> package, on the other hand, is the third release of th
e 2.6.32.9 version of the SMP-capable Linux kernel. This release incorporates new patches to fix bugs present in older releases of the 2.6.32.9 version of the Linux SMP kernel. The software packager increased the release number so that end users could distinguish the more recent, bug-fixed package file from the older, less bug-free package file.
+ </div><div class="para">
+ The final field in package file names is the architecture, which identifies the system types for which the package file is appropriate. For example, the <code class="filename">kernel-smp-2.6.32.9-3.x86_64</code> package is intended for use on machines with a 64-bit CPU, and <code class="filename">kernel-smp-2.6.32-9-3.i686</code> is intended for use on machines with an i686 (Pentium-class) CPU or better. An architecture name of noarch indicates this is a special architecture such that the files in the package work on any architecture. Typically, this is because the files are all interpreted scripts, not binary executables, or are documentation.
+ </div><div class="para">
+ RPM supports various architectures. Table 2-1 presents the architectures available for different platforms as of RPM version 4.7.
+ </div><div class="para">
+ Table 2-1 Supported Architectures
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Platform
+ </div>
+
+ </td><td>
+ <div class="para">
+ Architectures
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Intel-compatible 32-bit
+ </div>
+
+ </td><td>
+ <div class="para">
+ i386, i486, i586, i686, athlon, geode, pentium3, pentium4
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Intel-compatible 64-bit
+ </div>
+
+ </td><td>
+ <div class="para">
+ x86_64, amd64
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Intel Itanium
+ </div>
+
+ </td><td>
+ <div class="para">
+ ia64
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ HPAlpha (formerly Digital, Compaq)
+ </div>
+
+ </td><td>
+ <div class="para">
+ alpha, alphaev5, alphaev56, alphapca56, alphaev6, alphaev67
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Sparc/Ultra Sparc (Sun)
+ </div>
+
+ </td><td>
+ <div class="para">
+ sparc, sparcv8, sparcv9, sparc64, sparc64v, sun4, sun4c, sun4d, sun4m, sun4u,
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ ARM
+ </div>
+
+ </td><td>
+ <div class="para">
+ armv3l, armv4b, armv4l, armv5tel, armv5tejl, armv6l,armv7l
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ MIPS
+ </div>
+
+ </td><td>
+ <div class="para">
+ mips, mipsel
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Power PC
+ </div>
+
+ </td><td>
+ <div class="para">
+ ppc, ppciseries, ppcpseries, ppc64, ppc8260, ppc8560, ppc32dy4
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Motorola 68000 series
+ </div>
+
+ </td><td>
+ <div class="para">
+ m68k, m68kmint, atarist, atariste, ataritt, falcon, atariclone, milan, hades
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ SGI MIPS
+ </div>
+
+ </td><td>
+ <div class="para">
+ Sgi
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ IBM RS6000
+ </div>
+
+ </td><td>
+ <div class="para">
+ rs6000
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ IBM S/390
+ </div>
+
+ </td><td>
+ <div class="para">
+ i370, s390x, s390
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Platform independent
+ </div>
+
+ </td><td>
+ <div class="para">
+ noarch
+ </div>
+
+ </td></tr></tbody></table></div><div class="note"><div class="admonition_header"><h2>Architecture Compatibility</h2></div><div class="admonition"><div class="para">
+ When choosing an appropriate architecture for your machine, be aware that more recent architectures typically run software that targets older architectures within the same family; the reverse, however, is not true. For example, within the 32-bit Intel-compatible architectures, a 686-class (Pentium II / III / IV) machine runs files within i386, i486, i586, and i686 RPM package files, but a 386-class (80386) machine runs files within i386 RPM package files only. Similarly, for the Alpha architecture, more recent Alpha EV68 CPUs can run programs from RPM package files with alphaev67, alphaev6, alphaev56, alphaev5, and alpha architectures, but an older Alpha EV56 machine can run programs from RPM package files with alpha, alphaev5, or alphaev56 architectures only.
+ </div></div></div><div class="para">
+ Notice that the four fields in RPM package file names are separated from each other by punctuation, either a dash (-) or a period (.). Periods and dashes, however, are also allowed within fields. 7.2 is a valid version number, just as <code class="filename">kernel-source</code> is a valid software name. Finally, keep in mind that all RPM package files use an .rpm file-name extension to denote that they are RPMs.
+ </div><div class="para">
+ Once installed, package names are slightly different from package file names. Package files, which can be downloaded from the Internet, copied off of CDs, and otherwise easily transferred between machines, always have names that looks like name-version-release.architecture.rpm. Installed packages, however, have names that look like <code class="filename">name-version-release</code>. Once installed, packages are referred to without the architecture field and the .rpm extension. Furthermore, installed packages consist of lots of files, not a single RPM file. For example, the package file <code class="filename">kernel-smp-2.6.32.9-3.i686.rpm</code> after installation is referred to as <code class="filename">kernel-smp-2.6.32.9-3</code>. To simplify usage even further, installed packages can be referred to by their name field only, so this file would become simply <code class="filename">kernel-smp</code>.
+ </div><div class="warning"><div class="admonition_header"><h2>Software Names May Differ from Package Names</h2></div><div class="admonition"><div class="para">
+ Once installed, the name of the package does not have to be the same as the name portion of the original package file. By convention though, the package name matches the name, version, and release part of the file name.
+ </div></div></div><div class="para">
+ Usage of the name field by itself to name packages assumes that multiple versions or releases of that particular software are not installed. However, it is in some cases necessary to install different versions or releases of the same package. My desktop at home is a 64-bit AMD system. On it, I have the following Linux kernels installed:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ kernel-2.6.32.9-70.fc12
+ </div></li><li class="listitem"><div class="para">
+ kernel-2.6.32.10-90.fc12
+ </div></li><li class="listitem"><div class="para">
+ kernel-2.6.32.11-99.fc12
+ </div></li></ul></div><div class="para">
+ This example uses the <code class="command">rpm <code class="option">–q</code></code> command to query for all installed versions of the given package, <code class="filename">kernel</code>.
+ </div><div class="note"><div class="admonition_header"><h2>The RPM Database</h2></div><div class="admonition"><div class="para">
+ <a class="xref" href="#ch-using-rpm-db">Cap. 4, <em>Using the RPM Database</em></a> covers querying the RPM database in depth.
+ </div></div></div><div class="para">
+ I have three different versions installed on this system. Since I have multiple packages installed of the <code class="filename">kernel</code> software, I have to use the full package name (such as <code class="filename">kernel-2.6.32.11-99</code>) whenever I want to work with my installed <code class="filename">kernel</code> packages.
+ </div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id627397" class="title">Summary</h1></div></div></div><div class="para">
+ The RPM system wasn’t created to solve some theoretical problem. Instead, it is the result of years of hard-won practical experience in trying to manage systems with a large number of applications. RPM builds upon older systems that were created to solve some of the problems faced by system administrators. RPM goes further, though, and tries to provide a complete package-management solution. This includes the ability to deal with wrinkles that Linux faces but that many other operating systems do not need to address.
+ </div><div class="para">
+ For example, most other operating systems don’t support more than one or two processor architectures. Sun’s Solaris, for example, supports only the SPARC and Intel architectures. Linux supports these and more. Most other operating systems also don’t include nearly so many applications. From the OpenOffice.org office suite to the Apache Web server, Linux distributions are literally packed with applications. As a final point, most other operating systems provide mainly closed-source applications. Linux, on the other hand, includes thousands of open-source applications.
+ </div><div class="para">
+ From the perspective of the organizations making Linux distributions, these wrinkles make Linux harder to manage. Luckily for end users, the solution to these problems helps make the RPM system better able to manage user systems:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Supports Multiple Architectures — The RPM system tags each package with the processor architecture.
+ </div></li><li class="listitem"><div class="para">
+ Permits Multiple Software Versions in Parallel — RPM allows for multiple versions of the same package to be installed on the same system.
+ </div></li><li class="listitem"><div class="para">
+ One File Per Program — RPM packs all of the files in a package into one file, called an RPM file, for easy transfer to other systems.
+ </div></li><li class="listitem"><div class="para">
+ Requires Only One Command Per Action — Most RPM operations such as installing or removing packages require only a single command to run.
+ </div></li><li class="listitem"><div class="para">
+ Uses Pristine Sourcecode — The RPM system supports building RPM packages from a pristine set of sources. This means you can reproduce the commands required to build an application, improving quality.
+ </div></li></ol></div><div class="para">
+ This chapter introduced the RPM system and the history behind it. The next chapter delves into the RPM basics, including files, database, and commands.
+ </div></div></div><div xml:lang="ro" class="chapter" id="ch-rpm-overview" lang="ro"><div class="titlepage"><div><div><h2 class="title">Cap. 2. RPM Overview</h2></div></div></div><div class="toc"><dl><dt><span class="sect1"><a href="#id854538">2.1. Understanding the Package File</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id816046">2.1.1. RPM file format</a></span></dt><dt><span class="sect2"><a href="#id662734">2.1.2. Binary RPMs and Source RPMs</a></span></dt><dt><span class="sect2"><a href="#id586540">2.1.3. Source RPMs</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id732014">2.2. Querying the RPM Database</a></span></dt><dt><span class="sect1"><a href="#id555672">2.3. Running RPM Commands</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id586423">2.3.1. Working with the <code class="command">rpm</code> command</a></span></dt><dt><span class="sect2"><a href="#id664136">2.3.2. Other RPM commands</a></span></dt></dl></dd><dt><span class="sec
t1"><a href="#id622461">2.4. Summary</a></span></dt></dl></div><div class="para">
+ This chapter covers:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Understanding the package file
+ </div></li><li class="listitem"><div class="para">
+ Querying the RPM database
+ </div></li><li class="listitem"><div class="para">
+ Running RPM commands
+ </div></li></ul></div><div class="para">
+ Working with RPM packages, files, commands, and databases can be complicated. There are thousands of files, for hundreds if not thousands of packages, installed on your system. You need some way to manage it all. The RPM system can help you do that.
+ </div><div class="para">
+ This chapter provides an overview of the components that make up the RPM system for package management: package files, databases, and RPM commands.
+ </div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id854538" class="title">Understanding the Package File</h1></div></div></div><div class="para">
+ RPM provides for installing, upgrading and removing packages. Typically, each package is an application and all the necessary files associated with that application. For example, the Apache Web server comes with a number of configuration files, a large set of documentation files, and the Apache server itself. All of this fits into one RPM package.
+ </div><div class="para">
+ One of the main advantages of the RPM system is that each .rpm file holds a complete package. For example, the following file holds the <code class="filename">mlocate</code> package:
+ </div><div class="para">
+ <code class="filename">mlocate-0.22.2-2.i686.rpm</code>
+ </div><div class="para">
+ Based on the naming conventions discussed in <a class="xref" href="#ch-intro-rpm">Cap. 1, <em>Introduction to RPM</em></a>, this package represents <code class="filename">mlocate</code> package, version 0.22.2, second build of an RPM package, for i686 (Intel) architecture systems.
+ </div><div class="para">
+ With a single command, you can copy an .rpm file to another Linux system and install it, getting the complete contents of the package, or you can use other commands to remove or update the package.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id816046" class="title">RPM file format</h1></div></div></div><div class="para">
+ RPM files hold a number of tagged data items and a payload, the files to install on your system. The tagged data items describe the package and can contain optional features. For example, the NAME tag holds the package name. The optional PRE tag holds a pre-installation script, a script that the rpm command runs prior to installing the files in the package payload.
+ </div><div class="para">
+ Under the covers, RPM package files contain four sections. The first is a leading identification area that marks the file as an RPM package (created with a particular version of the RPM system). The remaining sections are the signature, the tagged data (called the header), and the payload. Each of these sections has important information about the package, although the payload section contains the actual content of the package.
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term">Signature</span></dt><dd><div class="para">
+ The signature appears after the lead or identifier section, which marks the file as an RPM file. Like your signature when you sign a check, the RPM signature helps verify the integrity of the package. No, the signature doesn’t check for bugs in software applications. Instead, it ensures that you have downloaded a valid RPM archive.
+ </div><div class="para">
+ The signature works by performing a mathematical function on the header and archive sections of the file. The mathematical function can be an encryption process, such as PGP (Pretty Good Privacy), or a message digest in MD5 format.
+ </div></dd><dt class="varlistentry"><span class="term">Header</span></dt><dd><div class="para">
+ The header contains zero or more tagged blocks of data that pertain to the package. The header contains information such as copyright messages, version numbers, and package summaries.
+ </div></dd><dt class="varlistentry"><span class="term">Payload</span></dt><dd><div class="para">
+ The payload section contains the actual files used in the package. These files are installed when you install the package. To save space, data in the payload section is compressed in GNU <code class="command">gzip</code> format.
+ </div></dd></dl></div><div class="para">
+ Once uncompressed, the data is in <code class="command">cpio</code> format, which is how the <code class="command">rpm2cpio</code> command (introduced in the "Other RPM commands" section later in this chapter) can do its work.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id662734" class="title">Binary RPMs and Source RPMs</h1></div></div></div><div class="para">
+ There are two main types of RPM packages: binary (or applications) and source. A binary RPM has been compiled for a particular architecture. For example, the Apache Web server compiled for an Intel Pentium, or i686, architecture won’t work on a Sharp Zaurus, which runs an Intel ARM processor. To run on both systems, you would need two separate packages: one for the Pentium i686 and one for the ARM.
+ </div><div class="para">
+ In addition to binary RPMs, you can get source code RPMs. These RPMs are packages that provide the source code for other packages.
+ </div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id758310" class="title">Binary RPMs</h1></div></div></div><div class="para">
+ Binary RPMs hold complete applications or libraries of functions compiled for a particular architecture. Most binary RPMs contain complete applications, such as the Apache Web server or the AbiWord word processor. These application binary RPMs usually depend on a number of system libraries which are, in turn, also provided by binary RPMs.
+ </div><div class="note"><div class="admonition_header"><h2>Finding More Software</h2></div><div class="admonition"><div class="para">
+ <a class="xref" href="#ch-management-software">Cap. 7, <em>RPM Management Software</em></a> covers a number of locations where you can find RPM applications galore. Your Linux installation CDs or DVDs are also a great source for applications. Most Linux distributions come with more applications than you can imagine using.
+ </div></div></div><div class="para">
+ Although most binary RPMs are complete applications, others provide libraries. For example, the Simple DirectMedia Layer library (SDL), which provides graphics for many games, can be packaged as an RPM file. A number of programs, mostly games, use this library for enhanced multimedia such as rich graphics. RPMs that provide libraries allow multiple applications to share the same library. Typically, the libraries are packaged into separate RPMs from the applications.
+ </div><div class="para">
+ In addition to binary RPMs that hold applications or libraries compiled for a particular architecture, RPM supports the concept of platform-independent binary RPMs. These platform-independent RPMs, called noarch as a shorted form of “no architecture†dependencies, provide applications or libraries that are not dependent on any platform. Applications written in Perl, Python, or other scripting languages often do not depend on code compiled for a particular architecture. In addition, compiled Java applications are usually free of platform dependencies.
+ </div></div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id586540" class="title">Source RPMs</h1></div></div></div><div class="para">
+ The <code class="filename">mlocate</code> package, mentioned previously, contains the <code class="filename">mlocate</code> application used to search for files on the system. The source code used to create this application is stored in an <code class="filename">mlocate</code> source RPM, for example:
+ </div><div class="para">
+ <code class="filename">mlocate-0.22.2-2.src.rpm</code>
+ </div><div class="para">
+ By convention, source RPMs have a file name ending in .src.rpm.
+ </div><div class="para">
+ Source RPMs should contain all the commands, usually in scripts, necessary to recreate the binary RPM. Having a source RPM means that you can recreate the binary RPM at any time. This is a very important goal of the RPM system.
+ </div><div class="note"><div class="admonition_header"><h2>Source RPMs and Open Source Licencing</h2></div><div class="admonition"><div class="para">
+ Source RPMs have nothing to do with open-source software licenses. Linux is famous for being an open-source operating system. In RPM terms, that means the source code for the Linux kernel and most Linux applications are freely available as source RPMs. But you can also make source RPMs for proprietary programs. The key issue is that you are unlikely to distribute the source RPMs for proprietary packages.
+ </div><div class="para">
+ Furthermore, a number of open-source applications are not available as source RPMs. That's a shame, since source RPMs would make these applications easier to install.
+ </div></div></div><div class="para">
+ While source RPMs hold the commands necessary to create the binary RPM, there may be differences in your Linux environment that would result in rebuilding a binary RPM that is different from the original binary RPM. For example, the compile scripts for some packages may add in optional code depending on which libraries or which versions of libraries are found on your system. <a class="xref" href="#ch-packaging-guidelines">Cap. 13, <em>Packaging Guidelines</em></a> covers many issues in creating RPMs, and <a class="xref" href="#ch-other-linuxes">Cap. 18, <em>Using RPM on Non-Red Hat Linuxes</em></a> and <a class="xref" href="#ch-other-os">Cap. 19, <em>RPM on Other Operating Systems</em></a> cover issues related to other versions of Linux and other operating systems, respectively. If you follow the guidelines when making your own RPMs, you should result in source RPMs that reproduce binary RPMs as consistently as possible.
+ </div></div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id732014" class="title">Querying the RPM Database</h1></div></div></div><div class="para">
+ The RPM database holds information about all the RPM packages installed on your system. You can use this database to query what is installed, to help determine if you have the latest versions of software, and to verify that your system is properly set up, at least from a packaging point of view.
+ </div><div class="para">
+ The RPM database itself is stored in the directory <code class="filename">/var/lib/rpm/</code>, and should contain files like the following:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">Basenames</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">Conflictname</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">__db.001</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">__db.002</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">__db.003</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">Dirnames</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">Filemd5s</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">Group</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">Installtid</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">Name</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">Packages</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">Providename</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">Provideversion</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">Pubkeys</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">Requirename</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">Requireversion</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">Sha1header</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">Sigmd5</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">Triggername</code>
+ </div></li></ul></div><div class="note"><div class="admonition_header"><h2>The RPM Database</h2></div><div class="admonition"><div class="para">
+ <a class="xref" href="#ch-using-rpm-db">Cap. 4, <em>Using the RPM Database</em></a> covers the database in more detail.
+ </div></div></div><div class="para">
+ These files make up the RPM database. The file <code class="filename">__db.001</code> and similar files are lock files used by the RPM system. The other files are databases in Berkeley DB format. The most important file is <code class="filename">Packages</code>. The <code class="filename">Packages</code> file contains the header tag information for each package indexed by an index number for each package. This number slowly grows with time.
+ </div><div class="para">
+ The other files, such as <code class="filename">Name</code>, <code class="filename">Providename</code>, and <code class="filename">Group</code>, exist to speed access to particular types of information. Treat your RPM database with care. Back up the files, especially after upgrading, installing, or removing packages.
+ </div><div class="note"><div class="admonition_header"><h2>Recreating The RPM Database</h2></div><div class="admonition"><div class="para">
+ Only the <code class="filename">Packages</code> file is essential. You can recreate the rest of the files using the <code class="command">rpm <code class="option">--rebuilddb</code></code> command, introduced in <a class="xref" href="#ch-using-rpm-db">Cap. 4, <em>Using the RPM Database</em></a>.
+ </div></div></div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id555672" class="title">Running RPM Commands</h1></div></div></div><div class="para">
+ The primary RPM command is simply <code class="command">rpm</code>. One of the original goals of the RPM system is providing ease of use. In support of this goal, just about everything you want to do with the RPM system can be done with this one command. For most usage, the command-line parameters to the <code class="command">rpm</code> command determine the actions it should take.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id586423" class="title">Working with the <code class="command">rpm</code> command</h1></div></div></div><div class="para">
+ The <code class="command">rpm</code> command performs the most common package-management functions, along with a host of uncommon functions as well. The table below lists the main operations you can perform with the <code class="command">rpm</code> command and the command-line options to specify the given operations.
+ </div><div class="table" id="tb-rpm-operations"><h6>Tabel 2.1. The main <code class="command">rpm</code> operations</h6><div class="table-contents"><table summary="The main rpm operations" border="1"><colgroup><col class="Operation" width="33%" /><col class="Short Option" width="33%" /><col class="Long Option" width="33%" /></colgroup><thead><tr><th>
+ Operation
+ </th><th>
+ Short Option
+ </th><th>
+ Long Option
+ </th></tr></thead><tbody><tr><td>
+ Upgrade/install
+ </td><td>
+ -U
+ </td><td>
+ --upgrade
+ </td></tr><tr><td>
+ Install
+ </td><td>
+ -I
+ </td><td>
+ --install
+ </td></tr><tr><td>
+ Remove
+ </td><td>
+ -e
+ </td><td>
+ --erase
+ </td></tr><tr><td>
+ Query
+ </td><td>
+ -q
+ </td><td>
+ --query
+ </td></tr><tr><td>
+ Verify
+ </td><td>
+ -V
+ </td><td>
+ --verify
+ </td></tr><tr><td>
+ Check signature
+ </td><td>
+ -K
+ </td><td>
+ --checksig
+ </td></tr><tr><td>
+ Freshen (upgrade) already-installed package
+ </td><td>
+ -F
+ </td><td>
+ --freshen
+ </td></tr><tr><td>
+ Initialize database
+ </td><td>
+ None
+ </td><td>
+ --initdb
+ </td></tr><tr><td>
+ Rebuild database
+ </td><td>
+ None
+ </td><td>
+ --rebuilddb
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ Using this table as a guide, you can explore the options to the <code class="command">rpm</code> command. To install or upgrade a package, use the <code class="option">-U</code> command-line option:
+ </div><pre class="screen">
+<strong class="userinput"><code>rpm -U <em class="replaceable"><code>filename.rpm</code></em></code></strong></pre><div class="para">
+ For example, to install the <code class="filename">mlocate</code> RPM used as an example in this chapter, run the following command:
+ </div><pre class="screen">
+<strong class="userinput"><code>rpm -U <em class="replaceable"><code>mlocate-0.22.2-2.i686.rpm</code></em></code></strong></pre><div class="para">
+ To get extra feedback, you can use a command like the following, with the <code class="option">-h</code> and <code class="option">-v</code> options in conjunction with the <code class="option">–U</code> option:
+ </div><pre class="screen">
+<strong class="userinput"><code>rpm -Uhv <em class="replaceable"><code>mlocate-0.22.2-2.i686.rpm</code></em></code></strong></pre><div class="para">
+ When you run this command you will see more output than the default, which is no output unless there are errors. With the <code class="option">–h</code> option, the <code class="command">rpm</code> command will print a series of hash marks, #, to provide feedback that the command is still running. With the <code class="option">–v</code> option, the <code class="command">rpm</code> command provides more verbose messages.
+ </div><div class="note"><div class="admonition_header"><h2>Installing a Package</h2></div><div class="admonition"><div class="para">
+ The most common command to install a package is:
+ </div><pre class="screen">
+<strong class="userinput"><code>rpm -Uhv <em class="replaceable"><code>package_file.rpm</code></em></code></strong></pre><div class="para">
+ This command upgrades a package with extra output. If the package has not been installed, this command installs the package. See <a class="xref" href="#ch-using-rpm">Cap. 3, <em>Using RPM</em></a> for more on upgrading and installing.
+ </div></div></div><div class="para">
+ To remove a package (called erase in RPM terminology), use the <code class="option">–e</code> command-line option:
+ </div><pre class="screen">
+<strong class="userinput"><code>rpm –e <em class="replaceable"><code>package_name</code></em></code></strong></pre><div class="note"><div class="admonition_header"><h2>Using File Extensions</h2></div><div class="admonition"><div class="para">
+ Notice that you install a package file using the file name that ends in .rpm, but uninstall or erase a package without the .rpm extension. This is because you install RPM files, but once installed, you work with the installed packages. The file name and the package name do not have to correspond, but typically (and sanely) they have the same base name.
+ </div></div></div><div class="para">
+ To list every RPM package installed on your system, use a command like the following.
+ </div><pre class="screen">
+<strong class="userinput"><code>rpm –qa</code></strong></pre><div class="para">
+ Expect to wait while this command completes. Most Linux systems have numerous packages installed, which will result in many lines of output. To better see the output, you can pipe this command to the more command, as shown following:
+ </div><pre class="screen">
+<strong class="userinput"><code>rpm –qa | more</code></strong></pre><div class="para">
+ You will then see the package listing one screen at a time.
+ </div><div class="note"><div class="admonition_header"><h2><code class="command">rpm</code> Options</h2></div><div class="admonition"><div class="para">
+ <a class="xref" href="#ch-command-reference">Cap. 21, <em>RPM Command Reference</em></a> lists all the options for the <code class="command">rpm</code> command.
+ </div></div></div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id664136" class="title">Other RPM commands</h1></div></div></div><div class="para">
+ In addition to <code class="command">rpm</code>, the RPM system includes a few more commands, including <code class="command">rpmbuild</code> and <code class="command">rpm2cpio</code>.
+ </div><div class="para">
+ The <code class="command">rpmbuild</code> command helps build RPM packages. Its usage is discussed in depth in Part II of this book.
+ </div><div class="para">
+ The <code class="command">rpm2cpio</code> command exports an RPM package file into the format that the <code class="command">cpio</code> command expects. The <code class="filename">cpio</code> command works with many tape-backup packages. You can also take advantage of the fact that <code class="filename">cpio</code> can list the individual files in a <code class="filename">cpio</code> archive or extract files. To list the files in an RPM package, use a command like the following:
+ </div><pre class="screen">
+<strong class="userinput"><code>rpm2cpio <em class="replaceable"><code>package_file.rpm</code></em> | cpio –t</code></strong></pre><div class="para">
+ For example, the following command lists all the files in the <code class="filename">mlocate</code> package:
+ </div><pre class="screen">
+<strong class="userinput"><code>rpm2cpio <em class="replaceable"><code>mlocate-0.22.2-2.i686.rpm</code></em> | cpio –t</code></strong></pre><div class="para">
+ To display:
+ </div><pre class="screen">
+<code class="computeroutput"> ./etc/cron.daily/mlocate.cron ./etc/updatedb.conf ./usr/bin/locate ./usr/bin/updatedb ./usr/share/doc/mlocate-0.22.2 ./usr/share/doc/mlocate-0.22.2/AUTHORS ./usr/share/doc/mlocate-0.22.2/COPYING ./usr/share/doc/mlocate-0.22.2/NEWS ./usr/share/doc/mlocate-0.22.2/README ./usr/share/locale/bg/LC_MESSAGES/mlocate.mo ./usr/share/locale/ca/LC_MESSAGES/mlocate.mo ./usr/share/locale/cs/LC_MESSAGES/mlocate.mo ./usr/share/locale/da/LC_MESSAGES/mlocate.mo ./usr/share/locale/de/LC_MESSAGES/mlocate.mo ./usr/share/locale/es/LC_MESSAGES/mlocate.mo ./usr/share/locale/fr/LC_MESSAGES/mlocate.mo ./usr/share/locale/hu/LC_MESSAGES/mlocate.mo ./usr/share/locale/it/LC_MESSAGES/mlocate.mo ./usr/share/locale/ja/LC_MESSAGES/mlocate.mo ./usr/share/locale/ms/LC_MESSAGES/mlocate.mo ./usr/share/locale/nl/LC_MESSAGES/mlocate.mo ./usr/share/locale/pl/LC_MESSAGES/mlocate.mo ./usr/share/locale/pt/LC_MESSAGES/mlocate.mo ./usr/share/locale/pt_BR/LC_MESSAGES/mlocate.mo ./usr/share/
locale/sr/LC_MESSAGES/mlocate.mo ./usr/share/locale/sr at latin/LC_MESSAGES/mlocate.mo ./usr/share/locale/sv/LC_MESSAGES/mlocate.mo ./usr/share/locale/zh_CN/LC_MESSAGES/mlocate.mo ./usr/share/man/man1/locate.1.gz ./usr/share/man/man5/mlocate.db.5.gz ./usr/share/man/man5/updatedb.conf.5.gz ./usr/share/man/man8/updatedb.8.gz ./var/lib/mlocate 555 blocks </code></pre><div class="para">
+ The <code class="command">rpm2cpio</code> command can also help if you want to extract a single file from the RPM package, using the <code class="command">cpio <code class="option">–ivd</code></code> command-line options, as follows:
+ </div><pre class="screen">
+ <strong class="userinput"><code>rpm2cpio <em class="replaceable"><code>mlocate-0.22.2-2.i686.rpm</code></em> | cpio –ivd <em class="replaceable"><code>usr/share/doc/mlocate-0.22.2/README</code></em></code></strong></pre><div class="para">
+ This command will output local <code class="filename">usr/share/doc/mlocate-0.22.2/README</code> subdirectories and the <code class="filename">README</code> file located under <code class="filename">usr/share/doc/mlocate-0.22.2</code>.
+ </div><div class="para">
+ The <code class="option">–i</code> option tells <code class="command">cpio</code> to extract files. The <code class="option">–d</code> option tells <code class="command">cpio</code> to make any local subdirectories as needed (<code class="filename">usr/share/doc/mlocate-0.22.2</code>, in this example), and the <code class="option">–v</code> option asks <code class="command">cpio</code> to politely output verbose messages about what it does. Of course, verbose is in the eye of the beholder; with many Unix and Linux commands, verbose output is still somewhat terse.
+ </div></div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id622461" class="title">Summary</h1></div></div></div><div class="para">
+ The RPM files, the RPM database, and the RPM commands are the primary components that make up the RPM system. This chapter introduces you to the format and types of RPM files, the importance of maintaining the database, and the basic rpm command.
+ </div><div class="para">
+ The next chapter covers the most frequently used RPM commands. These commands allow you to install, uninstall, and update RPM packages.
+ </div></div></div><div xml:lang="ro" class="chapter" id="ch-using-rpm" lang="ro"><div class="titlepage"><div><div><h2 class="title">Cap. 3. Using RPM</h2></div></div></div><div class="toc"><dl><dt><span class="sect1"><a href="#id534995">3.1. The <code class="command">rpm</code> Command</a></span></dt><dt><span class="sect1"><a href="#id578718">3.2. Upgrading and Installing Software</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id554587">3.2.1. Upgrading with the <code class="command">rpm</code> command</a></span></dt><dt><span class="sect2"><a href="#id596004">3.2.2. Upgrading packages</a></span></dt><dt><span class="sect2"><a href="#id809735">3.2.3. Freshening up</a></span></dt><dt><span class="sect2"><a href="#id583586">3.2.4. Installing Packages</a></span></dt><dt><span class="sect2"><a href="#id816163">3.2.5. Installing Over the Internet</a></span></dt><dt><span class="sect2"><a href="#id567480">3.2.6. Installing source RPMs</a></span></dt></dl></dd><dt><span
class="sect1"><a href="#id1373416">3.3. Removing Software</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id1067283">3.3.1. Checking that the package has been removed</a></span></dt><dt><span class="sect2"><a href="#id935675">3.3.2. Removing multiple packages at a time</a></span></dt><dt><span class="sect2"><a href="#id787355">3.3.3. Options when removing packages</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id821991">3.4. Other <code class="command">rpm</code> Command Options</a></span></dt><dt><span class="sect1"><a href="#id566157">3.5. Summary</a></span></dt></dl></div><div class="para">
+ This chapter covers:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Installing and upgrading software
+ </div></li><li class="listitem"><div class="para">
+ Removing software
+ </div></li></ul></div><div class="para">
+ This chapter covers the most common uses for RPM: installing, removing, and upgrading software. These are the most frequently used RPM commands.
+ </div><div class="para">
+ The RPM system includes the options you might expect, such as installing a package, but there’s a lot more you can do. For example, you can install packages from remote sites using HTTP or FTP to download the package to install. There are quite a few other <code class="command">rpm</code> options you can use to get information and feedback on installation, for example.
+ </div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id534995" class="title">The <code class="command">rpm</code> Command</h1></div></div></div><div class="para">
+ Just about everything you do with RPM requires the <code class="command">rpm</code> command. As a nice added benefit, just about everything you do with RPM requires a single invocation of the <code class="command">rpm</code> command. That means common tasks such as installing and removing software can be done quickly and efficiently. The basics of the <code class="command">rpm</code> command are not very hard, and you can perform the basic tasks within a few minutes of reading this chapter.
+ </div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id578718" class="title">Upgrading and Installing Software</h1></div></div></div><div class="para">
+ To install software, you need something to install. Typically, this is a file packaged as RPM, using a file-name extension of <code class="filename">rpm</code>. Of course, this isn’t required, but just about every RPM package is stored in a file with a <code class="filename">rpm</code> extension. For example, the following file holds an RPM package, ready to be installed:
+ </div><div class="para">
+ <code class="filename">jikes-1.16-1.i386.rpm</code>
+ </div><div class="para">
+ This package holds an application named <code class="command">jikes</code> (a Java language compiler application). From the discussion in the last two chapters, you should be able to determine the version of the program this RPM holds and which release of the RPM package this represents.
+ </div><div class="para">
+ Other RPMs hold sources, the program source codes used to create an application or programming library. For example, the following file holds a source RPM:
+ </div><div class="para">
+ <code class="filename">jikes-1.16-1.src.rpm</code>
+ </div><div class="para">
+ The <code class="filename">src</code> in the package name is short for source. This file-naming convention is not required, but is used by just about all source code packages. (Following conventions helps other administrators know what to expect.)
+ </div><div class="note"><div class="admonition_header"><h2>Building Packages from Source RPMs</h2></div><div class="admonition"><div class="para">
+ Refer to <a class="xref" href="#ch-creating-rpms">Cap. 8, <em>Creating RPMs: An Overview</em></a> and <a class="xref" href="#ch-rpmbuild">Cap. 11, <em>Controlling the Build with <code class="command">rpmbuild</code></em></a> for information on building RPMs from source RPMs.
+ </div></div></div><div class="para">
+ The <code class="command">rpm</code> command provides three main operations for upgrading and installing packages:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term">Upgrade</span></dt><dd><div class="para">
+ An upgrade operation means installing a new version of a package and removing all previous versions of the same package. If you have not installed a package previously, the upgrade operation will install the package.
+ </div></dd><dt class="varlistentry"><span class="term">Freshen</span></dt><dd><div class="para">
+ A freshen operation means to install a new version of a package only if you have already installed another version of the package.
+ </div></dd><dt class="varlistentry"><span class="term">Install</span></dt><dd><div class="para">
+ An install operation installs a package for the first time. It also, through special command-line parameters, allows you to install multiple versions of a package, usually not what you want. So, in the vast majority of cases, you want to run the upgrade operation for all package installations.
+ </div></dd></dl></div><div class="para">
+ The following sections cover the command-line options that apply to these operations.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id554587" class="title">Upgrading with the <code class="command">rpm</code> command</h1></div></div></div><div class="para">
+ </div><div class="para">
+ Almost all installation steps use the <code class="command">rpm</code> command with the <code class="option">–U</code> option, short for upgrade, as introduced in <a class="xref" href="#ch-rpm-overview">Cap. 2, <em>RPM Overview</em></a> . The basic syntax is:
+ </div><div class="para">
+ <code class="command">rpm</code> <code class="option">-U</code> <em class="replaceable"><code>package_name</code></em>
+ </div><div class="para">
+ For example:
+ </div><div class="para">
+
+<pre class="screen">
+<strong class="userinput"><code>rpm –U jikes-1.16-1.i386.rpm</code></strong></pre>
+
+ </div><div class="para">
+ You can also use the <code class="option">--upgrade</code> long option in place of <code class="option">-U</code>.
+ </div><div class="para">
+ Unless something goes wrong, you won’t see any response except for the shell prompt ready for your next command. Options for the <code class="command">rpm</code> command, covered shortly, present positive feedback that the package has been installed.
+ </div><div class="para">
+ The <code class="command">rpm</code> command may print out warnings, such as the one following:
+ </div><pre class="screen">
+<code class="computeroutput">warning: pyxf86config-0.3.1-2.i386.rpm: Header V3 DSA signature: NOKEY, key ID 897da07a</code></pre><div class="para">
+ This warning comes from the fact that the package was signed, but the key was not found. <a class="xref" href="#ch-rpmbuild">Cap. 11, <em>Controlling the Build with <code class="command">rpmbuild</code></em></a> covers signing packages. In most cases, warnings such as this one are not that serious. Errors, though, should be treated seriously.
+ </div><div class="note"><div class="admonition_header"><h2><code class="systemitem">root</code> Permissions</h2></div><div class="admonition"><div class="para">
+ Just about every package you want to upgrade or install requires <code class="systemitem">root</code>, or super user, permissions. That’s because most Linux application RPMs hold files that must be installed in a protected directory such as <code class="filename">/usr/bin/</code>. In addition, RPM requires root access to modify the RPM database. Even if you could modify the system directories like <code class="filename">/usr/bin/</code>, you must also be able to modify the RPM database to successfully install or remove packages.
+ </div></div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id720199" class="title">Checking That the Package Is Installed</h1></div></div></div><div class="para">
+ Use the <code class="command">rpm –q</code> command to quickly verify a package has been installed. To verify, you need to use the name of the installed package, not the name of the RPM file. You can also use a partial package name, such as <code class="filename">jikes</code> in this case. For example:
+ </div><pre class="screen">
+<strong class="userinput"><code>rpm –q <em class="replaceable"><code>jikes</code></em></code></strong></pre><div class="para">
+ When you run this command, you should see a response like the following:
+ </div><pre class="screen">
+<code class="computeroutput">jikes-1.16-1</code></pre><div class="para">
+ The response shows that the package named <code class="filename">jikes-1.16-1</code> has been installed. This package name corresponds to the RPM file used in the preceding installation example.
+ </div><div class="para">
+ </div><div class="para">
+ The <code class="command">rpm -q</code> command just asks the RPM database if the package has been installed. There may be other issues with the package that this command won’t show. For now, though, the <code class="command">rpm –q</code> command verifies that package has been installed.
+ </div><div class="para">
+ If the package has been not installed, you will see a message similar to the following:
+ </div><pre class="screen">
+<code class="computeroutput">package jikes is not installed</code></pre></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id772244" class="title">Getting Feedback During Installation and upgrades</h1></div></div></div><div class="para">
+ The <code class="option">-h</code> option to the <code class="command">rpm</code> command prints out # signs, also called hash marks (hence the <code class="option">-h</code>). These hash marks provide some confirmation that the <code class="command">rpm</code> command is still running. This is important, since large packages may take a long time to install or upgrade. Run this command like the following:
+ </div><pre class="screen">
+<strong class="userinput"><code>rpm -Uh jikes-1.16-1.i386.rpm</code></strong></pre><div class="para">
+ You'll see this output:
+ </div><pre class="screen">
+<code class="computeroutput">########################################### [100%] ########################################### [100%]</code></pre><div class="para">
+ The hash marks are printed one at a time as the command does its work. If the package was not created properly, you may see warnings like the following:
+ </div><pre class="screen">
+<code class="computeroutput">########################################### [100%] warning: user cabbey does not exist - using root warning: user cabbey does not exist - using root warning: user cabbey does not exist - using root ########################################### [100%]</code></pre><div class="note"><div class="admonition_header"><h2>Reinstalling Packages</h2></div><div class="admonition"><div class="para">
+ You can install a package more than once. The <code class="command">rpm</code> command won't complain. The upgrade operation, though, will remove all other versions of a package. This is one more reason to use the <code class="option">–U</code> upgrade option.
+ </div></div></div><div class="para">
+ In addition to hash marks, you can get more verbose output from the tight-lipped <code class="command">rpm</code> command. The <code class="option">-v</code> option to the <code class="command">rpm</code> command tells the command to print out verbose information as the command runs. Remember, though, that verbose is used in the traditional Unix and Linux meaning, which is normally not all that verbose. In the Unix/Linux context, verbose usually means slightly more than nothing. The syntax for the command follows:
+ </div><pre class="screen">
+<strong class="userinput"><code>rpm -Uhv jikes-1.16-1.i386.rpm</code></strong></pre><div class="para">
+ With the <code class="option">-v</code> command-line option, you will see output more like the following:
+ </div><pre class="screen">
+<code class="computeroutput">Preparing... ########################################### [100%] 1:jikes ########################################### [100%]</code></pre><div class="note"><div class="admonition_header"><h2>Standard Command for Package Installation</h2></div><div class="admonition"><div class="para">
+ The most common command to install a package is <code class="command">rpm -Uhv <em class="replaceable"><code>package_file.rpm</code></em></code>. That is, upgrade with verbose output and hashes.
+ </div></div></div><div class="para">
+ To get extra verbose information, use the <code class="option">-vv</code> command-line option. Think of this as doubly verbose. Usually, though, this extra information has no meaning unless you are debugging an RPM package that you are building. See the chapters in Part II on Creating RPMs for more on how to build RPM packages.
+ </div><div class="para">
+ A double-verbose command uses much the same syntax as shown previously:
+ </div><pre class="screen">
+<strong class="userinput"><code>rpm -Uhvv jikes-1.16-1.i386.rpm</code></strong></pre><div class="para">
+ With the double-verbose option, the output appears as follows:
+ </div><pre class="screen">
+<code class="computeroutput">D: ============== jikes-1.16-1.i386.rpm D: Expected size: 702988 = lead(96)+sigs(100)+pad(4)+data(702788) D: Actual size: 702988 D: jikes-1.16-1.i386.rpm: MD5 digest: OK (2dba32192eca23eb480d1d02a9b6c022) D: added binary package [0] D: found 0 source and 1 binary packages D: opening db environment /var/lib/rpm/Packages joinenv D: opening db index /var/lib/rpm/Packages rdonly mode=0x0 D: locked db index /var/lib/rpm/Packages D: ========== +++ jikes-1.16-1 D: opening db index /var/lib/rpm/Depends create mode=0x0 D: Requires: <code class="command">rpm</code>lib(PayloadFilesHavePrefix) <= 4.0-1 YES (rpmlib provides) D: opening db index /var/lib/rpm/Providename rdonly mode=0x0 D: opening db index /var/lib/rpm/Pubkeys rdonly mode=0x0 D: read h# 9 Header V3 DSA signature: NOKEY, key ID 897da07a D: Requires: ld-linux.so.2 YES (db provides) D: read h# 9 Header V3 DSA signature: NOKEY, key ID 897da07a D: Requires: libc.so.6 YES (db provides) D: read h#
9 Header V3 DSA signature: NOKEY, key ID 897da07a D: Requires: libm.so.6 YES (db provides) D: read h# 633 Header V3 DSA signature: NOKEY, key ID 897da07a D: Requires: libstdc++-libc6.2-2.so.3 YES (db provides) D: read h# 9 Header V3 DSA signature: NOKEY, key ID 897da07a D: Requires: libc.so.6(GLIBC_2.0) YES (db provides) D: read h# 9 Header V3 DSA signature: NOKEY, key ID 897da07a D: Requires: libc.so.6(GLIBC_2.1) YES (db provides) D: read h# 9 Header V3 DSA signature: NOKEY, key ID 897da07a D: Requires: libc.so.6(GLIBC_2.1.3) YES (db provides) D: Requires: <code class="command">rpm</code>lib(CompressedFileNames) <= 3.0.4-1 YES (rpmlib provides) D: closed db index /var/lib/rpm/Pubkeys D: closed db index /var/lib/rpm/Depends D: closed db index /var/lib/rpm/Providename D: closed db index /var/lib/rpm/Packages D: closed db environment /var/lib/rpm/Packages D: ========== recording tsort relations D: ========== tsorting packages (order, #predecessors, #succesors, tree, depth)D
: 0 0 0 0 0 +jikes-1.16-1 D: installing binary packages D: opening db environment /var/lib/rpm/Packages joinenv D: opening db index /var/lib/rpm/Packages create mode=0x42 D: getting list of mounted filesystems D: sanity checking 1 elements D: opening db index /var/lib/rpm/Name create mode=0x42 D: read h# 707 Header sanity check: OK D: computing 3 file fingerprints Preparing... D: computing file dispositions D: opening db index /var/lib/rpm/Basenames create mode=0x42 ########################################### [100%] package jikes-1.16-1 is already installed D: closed db index /var/lib/rpm/Basenames D: closed db index /var/lib/rpm/Name D: closed db index /var/lib/rpm/Packages D: closed db environment /var/lib/rpm/Packages</code></pre><div class="note"><div class="admonition_header"><h2>Short and Long Options</h2></div><div class="admonition"><div class="para">
+ Although most Unix and Linux applications use a single minus sign for command-line options, such as <code class="command">rpm</code> <code class="option">-U</code>, many programs use two minus signs to indicate longer option names. For example, with the <code class="command">rpm</code> command, <code class="option">-U</code> and <code class="option">--upgrade</code> are treated the same. You can use the short option, <code class="option">-U</code>, or the long option, <code class="option">--upgrade</code>.
+ </div><div class="para">
+ There are long options for virtually every short option. There are also long options that are rarely used, for which there are no short options.
+ </div></div></div><div class="para">
+ One rarely used feedback option is <code class="option">--percent</code>. The <code class="option">--percent</code> option prints out decimal numbers that show the percentage completed as the <code class="command">rpm</code> command executes. This option is most useful if you wrap the <code class="command">rpm</code> command within some other command, such as a graphical user interface created from a Perl, Python, or Tcl/Tk script.
+ </div><div class="para">
+ The basic syntax is:
+ </div><pre class="screen">
+<strong class="userinput"><code>rpm -U --percent jikes-1.16-1.i386.rpm</code></strong></pre><div class="para">
+ When you run this command, you see output like the following:
+ </div><pre class="screen">
+<code class="computeroutput">%% 0.000000 %% 2.661902 %% 5.318614 %% 10.632039 %% 15.945465 %% 18.602177 %% 23.915603 %% 29.229028 %% 34.542453 %% 39.855879 %% 45.169304 %% 50.482729 %% 53.139442 %% 55.796154 %% 61.109580 %% 66.423005 %% 71.736430 %% 74.393143 %% 79.706568 %% 82.363281 %% 87.676706 %% 90.333419 %% 95.646844 %% 98.303557 %% 99.422736 %% 99.910411 %% 99.994892 %% 100.000000</code></pre><div class="para">
+ These decimal numbers output by the <code class="option">--percent</code> option are really meant to be input into another program, perhaps a program that shows a graphical progress meter. Each number output then updates the meter.
+ </div><div class="note"><div class="admonition_header"><h2>Percentages may be Approximate</h2></div><div class="admonition"><div class="para">
+ Don't trust the numbers too much. Claiming the package is 53.139442 percent installed just asks the user to be skeptical that it is exactly that far.
+ </div></div></div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id553783" class="title">The Installation Task In Detail</h1></div></div></div><div class="para">
+ You can use the <code class="command">rpm –U</code> command or the <code class="command">rpm –i</code> command to install a package. When the <code class="command">rpm</code> command installs a package, it goes through a number of steps:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Checking the package and the files it wants to install
+ </div></li><li class="listitem"><div class="para">
+ Performing preinstallation tasks
+ </div></li><li class="listitem"><div class="para">
+ Uncompressing the files and placing them in the proper locations
+ </div></li><li class="listitem"><div class="para">
+ Performing post-processing tasks
+ </div></li><li class="listitem"><div class="para">
+ Updating the RPM Database
+ </div></li></ol></div><div class="para">
+ When checking the package, <code class="command">rpm</code> checks that all the dependencies are installed. Dependencies are packages required by the RPM package you want to install. For example, a database-administration package for a particular database may require that the database itself was already installed.
+ </div><div class="para">
+ In addition to checking for dependencies, the <code class="command">rpm</code> command checks for conflicting packages. For example, when you are trying to install an older version of a package on top of a newer version, running the <code class="command">rpm</code> command alerts you to that conflict. This conflict-checking goes deeper than packages, though. Individual files may conflict if you are trying to install a package that has an older version of a particular file.
+ </div><div class="para">
+ After the checks, the <code class="command">rpm</code> command executes the preinstallation tasks (covered in depth in Part II). After all this preparatory work, the <code class="command">rpm</code> command finally gets down to business and installs the files in the package. These files are stored in compressed format (compressed with <code class="command">gzip</code> compression) inside the RPM file.
+ </div><div class="para">
+ After installing the files, there may be some post-processing tasks (also covered in Part II). At the end of its run, the <code class="command">rpm</code> command updates the RPM database to reflect the new package information. This update is very important and allows you to track packages.
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id879296" class="title">Taking a Test Drive</h1></div></div></div><div class="para">
+ The <code class="option">--test</code> command-line option tells the <code class="command">rpm</code> command to test the installation or upgrade process but not to install the file. For example, the following command performs an upgrade or install of the <code class="filename">jikes</code> package, but in test mode only. No files will actually be installed.
+ </div><pre class="screen">
+<strong class="userinput"><code>rpm -U --test jikes-1.16-1.i386.rpm</code></strong></pre><div class="para">
+ This command will print nothing if the tested installation or upgrade runs smoothly. If, on the other hand, a problem results from the tested installation, you will receive an error message. If the package is already installed, you will see a message like the following:
+ </div><pre class="screen">
+<code class="computeroutput">package jikes-1.16-1 is already installed</code></pre><div class="para">
+ If the file is corrupted, you will see output like the following:
+ </div><pre class="screen">
+<code class="computeroutput">chap4.txt: not an <code class="command">rpm</code> package (or package manifest):</code></pre><div class="para">
+ This example was run against a file that was clearly not an RPM package.
+ </div><div class="para">
+ The test option can help you determine package dependencies, too.
+ </div><div class="para">
+ You can often determine dependencies at a glance--if you know something about the software you are installing. For example, if you know that Ruby is a scripting language, you can guess that packages starting with <code class="filename">eruby</code>, such as <code class="filename">eruby-devel-0.9.8-2.i386.rpm</code>, will depend on a base <code class="filename">ruby</code> package.
+ </div><div class="para">
+ To show this, query for any <code class="filename">ruby</code> packages by using a command like the following:
+ </div><pre class="screen">
+<strong class="userinput"><code>rpm -q ruby</code></strong></pre><div class="para">
+ If you have not installed a <code class="filename">ruby</code> package, you'll see a message like the following:
+ </div><pre class="screen">
+<code class="computeroutput">package ruby is not installed</code></pre><div class="note"><div class="admonition_header"><h2>Package Names</h2></div><div class="admonition"><div class="para">
+ Most packages use all lowercase names. Thus, you can expect packages for the Ruby scripting language to start with <code class="filename">ruby</code>.
+ </div></div></div><div class="para">
+ Package dependencies can quickly devolve into a nightmare in which one package depends upon another and that package in turn depends on yet another.
+ </div><div class="para">
+ This is where the <code class="option">--test</code> option comes in handy, since you can check that the dependencies are resolved prior to trying to install. (Note that the <code class="command">rpm</code> command will check dependencies on real installs as well. The <code class="option">--test</code> option just allows you to check that the installation will succeed prior to trying it.) For example, if you try to install a package named <code class="filename">eruby-devel-0.9.8-2.i386.rpm</code>, you may want to run a <code class="option">--test</code> option first:
+ </div><pre class="screen">
+<strong class="userinput"><code>rpm -U --test eruby-devel-0.9.8-2.i386.rpm</code></strong></pre><div class="para">
+ You'll then see a response like the following, presuming you have no <code class="filename">ruby</code> packages installed:
+ </div><pre class="screen">
+<code class="computeroutput">error: Failed dependencies: eruby-libs = 0.9.8 is needed by eruby-devel-0.9.8-2</code></pre><div class="para">
+ Now you can see that the package in the file <code class="filename">eruby-devel-0.9.8-2.i386.rpm</code> depends on another package, <code class="filename">eruby-libs</code> in this case. In fact, this package depends on the <code class="filename">eruby-libs</code> package having a version number of 0.9.8. These packages are obviously interrelated. From the name <code class="filename">eruby-libs</code>, you can guess that the package will be in a file with a name like <code class="filename">eruby-libs-0.9.8-2.i386.rpm</code>. (I cheated and used the actual package on the Red Hat installation CDs.)
+ </div><div class="para">
+ But you can see how the version numbers of the two files, and the RPM revision levels, match up, as follows:
+ </div><div class="para">
+ <code class="filename">eruby-devel-0.9.8-2.i386.rpm</code>
+ </div><div class="para">
+ <code class="filename">eruby-libs-0.9.8-2.i386.rpm</code>
+ </div><div class="para">
+ So, now you think your problems are over. You have the package that <code class="filename">eruby-devel-0.9.8-2.i386.rpm</code> depends on: <code class="filename">eruby-libs-0.9.8-2.i386.rpm</code>. Just to be careful, though, you can test that package as well, with a command like the following:
+ </div><pre class="screen">
+<strong class="userinput"><code>rpm -U --test eruby-libs-0.9.8-2.i386.rpm</code></strong></pre><div class="para">
+ Alas, this output leads you farther down into dependency nightmare:
+ </div><pre class="screen">
+<code class="computeroutput">error: Failed dependencies: ruby-libs >= 1.6.4 is needed by eruby-libs-0.9.8-2 libruby.so.1.6 is needed by eruby-libs-0.9.8-2</code></pre><div class="para">
+ This short example shows why it makes sense to test packages prior to installing or upgrading them.
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id664963" class="title">Installing or upgrading More Than One Package At A Time</h1></div></div></div><div class="para">
+ Up to now, all the examples shown have used the <code class="command">rpm</code> command to install or upgrade one package at a time. You can optionally choose to install or upgrade a number of packages at the same time. Just list each file name on the <code class="command">rpm</code> command line. The basic syntax follows:
+ </div><pre class="screen">
+<strong class="userinput"><code>rpm -U package1.rpm <em class="replaceable"><code>package2.rpm .. package100.rpm</code></em></code></strong></pre><div class="para">
+ Simply list all the packages one after another. For example:
+ </div><pre class="screen">
+<strong class="userinput"><code>rpm -U aspell-en-ca-0.33.7.1-16.i386.rpm aspell-en-gb-0.33.7.1-16.i386.rpm</code></strong></pre><div class="para">
+ This command installs two packages, the <code class="filename">aspell</code> packages for Canadian and British English, respectively.
+ </div><div class="para">
+ The <code class="option">--noorder</code> option tells the <code class="command">rpm</code> command not to reorder the packages you are trying to install. Usually, the <code class="command">rpm</code> command will reorder the list of packages in the best order for handling the dependencies. This option really only comes into play when you are installing more than one package where the packages depend on each other. In most cases, you do not want to use this option, since this may mean that packages fail to properly install because necessary packages are not already installed.
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id974844" class="title">Installing in Different Directories</h1></div></div></div><div class="para">
+ The <code class="option">--prefix</code> and <code class="option">--relocate</code> options should make the <code class="command">rpm</code> command relocate a package to a new location. Not all packages allow relocations, though. The basic format of the command with the <code class="option">--prefix</code> option is:
+ </div><pre class="screen">
+<strong class="userinput"><code>rpm -U --prefix <em class="replaceable"><code>/new/directory package.rpm</code></em></code></strong></pre><div class="para">
+ With the <code class="option">--relocate</code> option, the command format is:
+ </div><pre class="screen">
+<strong class="userinput"><code>rpm -i --relocate <em class="replaceable"><code>/old/directory=/new/directory package.rpm</code></em></code></strong></pre><div class="para">
+ You can also use the <code class="option">--root</code> option to specify a different directory for the <code class="command">rpm</code> command to assume is the system's root, or <code class="filename">/</code>, directory. This causes the <code class="command">rpm</code> command to install files under the new root, instead of in system locations under <code class="filename">/</code>. This option is most useful for testing the installation of a complete system under a test directory. The command should use the following format:
+ </div><pre class="screen">
+<strong class="userinput"><code>rpm -U --root /tmp --dbpath /var/lib/rpm jikes-1.16-1.i386.rpm</code></strong></pre><div class="para">
+ The <code class="option">--root</code> option tells the <code class="command">rpm</code> command that the root for this install is in <code class="filename">/tmp/</code>. Installs with the <code class="option">--root</code> option take place within a <code class="command">chroot()</code> environment. This is often useful for setting up a test environment.
+ </div><div class="para">
+ The <code class="option">--dbpath</code> option tells the <code class="command">rpm</code> command that the RPM database is located in the normal location, <code class="filename">/var/lib/rpm/</code>.
+ </div><div class="para">
+ Using the <code class="option">--dbpath</code> and <code class="option">--root</code> options will give you problems unless you have installed all the dependencies in the same virtual root directory. This includes all the standard Linux C libraries. For example, if you just run the example command, you'll see error output like the following:
+ </div><pre class="screen">
+<code class="computeroutput">error: Failed dependencies: ld-linux.so.2 is needed by jikes-1.16-1 libc.so.6 is needed by jikes-1.16-1 libm.so.6 is needed by jikes-1.16-1 libstdc++-libc6.2-2.so.3 is needed by jikes-1.16-1 libc.so.6(GLIBC_2.0) is needed by jikes-1.16-1 libc.so.6(GLIBC_2.1) is needed by jikes-1.16-1 libc.so.6(GLIBC_2.1.3) is needed by jikes-1.16-1</code></pre><div class="para">
+ You can use the <code class="option">--badreloc</code> option with the <code class="option">--relocate</code> option to permit relocations on all files in the package. Usually, only those paths to files that are listed as relocatable are supported by the <code class="option">--relocate</code> option.
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id607948" class="title">Forcing the Issue</h1></div></div></div><div class="para">
+ A number of <code class="command">rpm</code> options cause the <code class="command">rpm</code> command to complain about problems and, in general, fail to install your package. You can use a number of options to run roughshod over the RPM and get it to do what you want.
+ </div><div class="para">
+ The <code class="option">--replacepkgs</code> option tells the <code class="command">rpm</code> command to replace, or reinstall, packages it may have already installed.
+ </div><div class="para">
+ The <code class="option">--replacefiles</code> option tells the <code class="command">rpm</code> command to overwrite files owned by a another package.
+ </div><div class="para">
+ The <code class="option">--justdb</code> option tells the <code class="command">rpm</code> command to update the RPM database, not to install the files. You will need to be logged in as the root user to modify the RPM database.
+ </div><div class="para">
+ The <code class="option">--nosuggest</code> option tells the <code class="command">rpm</code> command to skip any suggestions for packages that may fill in missing dependencies. You almost never want to use this option.
+ </div><div class="para">
+ The <code class="option">--excludepath</code> option tells the <code class="command">rpm</code> command to exclude all files that start with the given path. For example:
+ </div><pre class="screen">
+<strong class="userinput"><code>rpm -U --excludepath /usr/lib eruby-devel-0.9.8-2.i386.rpm</code></strong></pre><div class="para">
+ This command installs or upgrades all the files in the package, except for those files that would be placed in a directory starting with <code class="filename">/usr/lib/</code>.
+ </div><div class="para">
+ The <code class="option">--allfiles</code> option tells the <code class="command">rpm</code> command to install or upgrade all files in the package, regardless of whether the files exist or not on your hard disk.
+ </div><div class="para">
+ The <code class="option">--oldpackage</code> tells the <code class="command">rpm</code> command to allow you to install an older version of a package on top of a more recent one. You don't usually want to do this, but you may need to under the following circumstances:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ If the more recent package has some bug or security vulnerability and you need to downgrade to a former version.
+ </div></li><li class="listitem"><div class="para">
+ If the more recent package won't work with some other package that depends on a particular former version of a package.
+ </div></li></ol></div><div class="para">
+ The latter case is very common if you upgrade your system in a piecemeal fashion. If a low-level library changes, it may take a while for all the packages that depend on the low-level library to get updated to use the latest version.
+ </div><div class="para">
+ Note that when you purchase an upgraded version of Linux, such as Red Hat Linux, all the packages with the product should be properly aligned with each other as to versions. This alignment problem is an issue that the Linux vendors, such as Red Hat, need to take care of. The main problems occur when you need packages beyond those offered with your Linux distribution.
+ </div><div class="para">
+ To combine some of these options, you can use <code class="option">--force</code>, which tells the <code class="command">rpm</code> command to turn on the <code class="option">--replacepkgs</code>, <code class="option">--replacefiles</code>, and <code class="option">--oldpackage</code> modes.
+ </div><div class="para">
+ The <code class="option">--nodeps</code> command-line option tells the <code class="command">rpm</code> command to skip the dependencies check and install anyway.
+ </div><div class="warning"><div class="admonition_header"><h2>Avoid Forcing Package Operations</h2></div><div class="admonition"><div class="para">
+ The <code class="command">rpm</code> command complains with good reason. Unless you really, really know what you are doing, don't force the issue by using these command-line options.
+ </div></div></div><div class="para">
+ Consider the <code class="filename">eruby-devel-0.9.8-2.i386.rpm</code> from the previous example. You can force the <code class="command">rpm</code> command to install this package, even though it depends on another package that in turn depends on yet another. The following command will force the installation of the package in the <code class="filename">eruby-devel-0.9.8-2.i386.rpm</code> file:
+ </div><pre class="screen">
+<strong class="userinput"><code>rpm -U --nodeps eruby-devel-0.9.8-2.i386.rpm</code></strong></pre><div class="para">
+ Just to be sure, you can query for the package using a command like the following.
+ </div><pre class="screen">
+<strong class="userinput"><code>rpm -q eruby-devel</code></strong></pre><div class="para">
+ The response should be:
+ </div><pre class="screen">
+<code class="computeroutput">eruby-devel-0.9.8-2</code></pre><div class="para">
+ The package is installed, but it likely won't work, since it really does depend on other packages. These package dependencies aren’t for show. You may have a valid reason to force a package to get installed, but you should go back later to try to resolve all the dependencies.
+ </div><div class="para">
+ In addition to forcing the <code class="command">rpm</code> command not to do certain things, you can use the <code class="option">--aid</code> option to have the <code class="command">rpm</code> command do something nice for you. The <code class="option">--aid</code> option tells the <code class="command">rpm</code> command to add all the packages it would suggest into the set of packages to install. The <code class="command">rpm</code> command has enough information to suggest a package or packages that ought to contain the dependent files.
+ </div><div class="para">
+ The <code class="option">--aid</code> option depends on a separate package that contains an RPM database with all packages installed. For Red Hat Linux, this package is <code class="filename">rpmdb-redhat</code>. This separate database, built as if all packages were installed (all packages that come with Red Hat Linux in this case), allows the <code class="command">rpm</code> command to search for which packages would solve dependencies.
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id571085" class="title">Skipping the Scripts</h1></div></div></div><div class="para">
+ As part of the package installation, as well as removal, the RPM package may have scripts that the <code class="command">rpm</code> command should run. These include pre- and post-installation scripts, as well as pre- and post-uninstallation scripts. These scripts can perform options such as automatically configuring the application based on the target environment. For example, an installation script may try to detect whether a site uses Postfix or Sendmail for transferring mail messages and configure the newly-installed package accordingly.
+ </div><div class="para">
+ In most cases, the <code class="command">rpm</code> command will execute these scripts at the proper time, unless you explicitly turn the command to skip the scripts. The <code class="option">--noscripts</code> option tells the <code class="command">rpm</code> command to skip running the pre- and post-installation scripts.
+ </div><div class="para">
+ If you want, you can exercise a finer grain of control. The <code class="option">--nopre</code> option tells the <code class="command">rpm</code> command to skip any pre-installation scripts. The <code class="option">--nopost</code> option tells the <code class="command">rpm</code> command to skip any post-installation scripts.
+ </div><div class="para">
+ Similarly, the <code class="option">--nopreun</code> option tells the <code class="command">rpm</code> command to skip any pre-uninstallation scripts, and the <code class="option">--nopostun</code> option tells the <code class="command">rpm</code> command to skip any post-uninstallation scripts.
+ </div><div class="para">
+ The <code class="option">--noscripts</code> option is the same as turning on all these options.
+ </div><div class="para">
+ The table below summarizes these options.
+ </div><div class="table" id="tb-skipping-scripts"><h6>Tabel 3.1. Skipping scripts</h6><div class="table-contents"><table summary="Skipping scripts" border="1"><colgroup><col class="Option" width="50%" /><col class="Usage" width="50%" /></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Usage
+ </th></tr></thead><tbody><tr><td>
+ <div class="para">
+ <code class="option">--nopre</code>
+ </div>
+
+ </td><td>
+ <div class="para">
+ Skip pre-installation scripts.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ <code class="option">--nopost</code>
+ </div>
+
+ </td><td>
+ <div class="para">
+ Skip post-installation scripts.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ <code class="option">--nopreun</code>
+ </div>
+
+ </td><td>
+ <div class="para">
+ Skip pre-uninstallation scripts.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ <code class="option">--nopostun</code>
+ </div>
+
+ </td><td>
+ <div class="para">
+ Skip post-uninstallation scripts.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ <code class="option">--noscripts</code>
+ </div>
+
+ </td><td>
+ <div class="para">
+ Skip all the scripts; same as <code class="option">--nopre</code>, <code class="option">--nopost</code>, <code class="option">--nopreun</code>, and <code class="option">--nopostun</code>.
+ </div>
+
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ In most cases, you never want to disable these scripts. Many RPMs uses these scripts to perform the final steps of the installation, especially the post-installation scripts. For example, the Mozilla Web browser and most network services require some kind of post-processing (using a post-installation script) or the packages will not be properly installed.
+ </div><div class="para">
+ In addition to pre- and post-installation scripts, the RPM system supports triggers, a topic covered in detail in <a class="xref" href="#ch-advanced-packaging">Cap. 10, <em>Creare avansată pachete RPM</em></a>.
+ </div><div class="para">
+ During installation, you can tell the <code class="command">rpm</code> command not to execute all the triggers or not to execute certain triggers. The <code class="option">--notriggers</code> option tells the <code class="command">rpm</code> command to skip all triggers.
+ </div><div class="para">
+ You can gain more fine-grained control with a further set of options in place of <code class="option">--notriggers</code>. The <code class="option">--notriggerin</code> option turns off triggers during installation. The <code class="option">--notriggerun</code> option turns off uninstallation triggers, and the <code class="option">--notriggerpostun</code> option turns off the post-uninstallation triggers.
+ </div><div class="para">
+ The <code class="option">--notriggers</code> option is the same as all three, <code class="option">--notriggerin</code>, <code class="option">--notriggerun</code>, and <code class="option">--notriggerpostun</code>.
+ </div><div class="para">
+ The table below summarizes these options.
+ </div><div class="table" id="tb-skipping-triggers"><h6>Tabel 3.2. Skipping Triggers</h6><div class="table-contents"><table summary="Skipping Triggers" border="1"><colgroup><col class="Option" width="50%" /><col class="Usage" width="50%" /></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Usage
+ </th></tr></thead><tbody><tr><td>
+ <div class="para">
+ <code class="option">--notriggerin</code>
+ </div>
+
+ </td><td>
+ <div class="para">
+ Skip installation triggers.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ <code class="option">--notriggerun</code>
+ </div>
+
+ </td><td>
+ <div class="para">
+ Skip uninstallation triggers.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ <code class="option">--notriggerpostun</code>
+ </div>
+
+ </td><td>
+ <div class="para">
+ Skip post-uninstallation triggers.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ <code class="option">--notriggers</code>
+ </div>
+
+ </td><td>
+ <div class="para">
+ Skip all the triggers; same as <code class="option">--notriggerin</code>, <code class="option">--notriggerun</code>, and <code class="option">--notriggerpostun</code>.
+ </div>
+
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id823152" class="title">Ignorance Is Bliss</h1></div></div></div><div class="para">
+ The <code class="command">rpm</code> command supports several ignore options that tell the command to ignore some aspect of a package it would normally complain about.
+ </div><div class="para">
+ The <code class="option">--ignorearch</code> option tells the <code class="command">rpm</code> command to ignore the architecture of the package and install the package, even if the architecture of the package and the architecture of your system do not match. This is a very dangerous option. Linux runs on everything from tiny wristwatches, PDAs such as the Sharp Zaurus, PCs, Macintosh PCs, RISC servers, and all the way up to huge supercomputers and mainframes. If you try to install a binary package compiled for the ARM or PowerPC processor on an Intel-architecture Linux system, the package will at best fail. At worst, it may damage parts of your system.
+ </div><div class="para">
+ Similarly, the <code class="option">--ignoreos</code> command-line option tells the <code class="command">rpm</code> command to ignore the operating system. Again, this is likely not a good idea in most situations. Applications compiled for Windows generally won’t run on Linux. SCO Unix systems, however, can run some Linux applications, so you may have a valid reason to ignore the operating system. Again, use only with extreme care.
+ </div><div class="para">
+ The <code class="option">--ignoresize</code> option tells the <code class="command">rpm</code> command to ignore or skip a check of your hard disk to ensure it has enough space to install the package.
+ </div><div class="warning"><div class="admonition_header"><h2>Ignoring Storage Limits</h2></div><div class="admonition"><div class="para">
+ Don't use the <code class="option">--ignoresize</code> option if you have a nearly full hard disk, especially for a root, or <code class="filename">/</code>, partition.
+ </div></div></div><div class="para">
+ The <code class="option">--nodigest</code> option tells the <code class="command">rpm</code> command to skip the test of the digest, the special value that helps verify the package correctness.
+ </div><div class="para">
+ The <code class="option">--nosignature</code> option tells the <code class="command">rpm</code> command to skip the test of the digest, the encrypted key, that helps also verify the package correctness.
+ </div><div class="warning"><div class="admonition_header"><h2>Unsafe Options</h2></div><div class="admonition"><div class="para">
+ Use these <code class="command">rpm</code> command-line options with extreme care and only after carefully considering the circumstances. Wrongful use of these options may damage your operating system.
+ </div></div></div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id1105852" class="title">Documentation? What Documentation?</h1></div></div></div><div class="para">
+ The <code class="option">--excludedocs</code> command-line option tells the <code class="command">rpm</code> command to ignore any files in the RPM package that are marked as documentation. Considering the general lack of documentation for many Linux applications, you are really asking for trouble by invoking this option. If the documentation takes up a lot of disk space, however, you may want to avoid installing documentation files. This is about the only situation in which this option makes sense.
+ </div><div class="para">
+ In reverse of <code class="option">--excludedocs</code>, the <code class="option">--includedocs</code> command-line parameter tells the <code class="command">rpm</code> command to install documentation. This is usually the default, so you rarely need this option.
+ </div></div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id596004" class="title">Upgrading packages</h1></div></div></div><div class="para">
+ The <code class="command">rpm</code> <code class="option">–U</code> command works for both installation of new packages and for upgrading. When you get beyond simple installations, you begin to see the power of the RPM system where most operations require just one command. The <code class="command">rpm -U</code> command is a very powerful tool and performs some complex operations with just one command. For example, the following commands show the sequence for upgrading the <code class="filename">jpilot</code> package, which is used for Palm PDA synchronization.
+ </div><pre class="screen">
+<strong class="userinput"><code># rpm -q jpilot</code></strong></pre><pre class="screen">
+<code class="computeroutput">jpilot-0.97-1</code></pre><pre class="screen">
+<strong class="userinput"><code># rpm -U jpilot-0.99.2-8.i386.rpm # rpm -q jpilot</code></strong></pre><pre class="screen">
+<code class="computeroutput">jpilot-0.99.2-8</code></pre><div class="para">
+ Note that the old version of the <code class="filename">jpilot</code> package is no longer installed. The <code class="command">rpm -U</code> command removed that package.
+ </div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id699650" class="title">Options When Upgrading</h1></div></div></div><div class="para">
+ You can pass more than one package name on the command line when upgrading. In addition, you can use the installation and upgrade options discussed previously when upgrading.
+ </div><div class="note"><div class="admonition_header"><h2>Uninstallation Scripts</h2></div><div class="admonition"><div class="para">
+ When upgrading, the <code class="option">--noscripts</code> option only turns off the scripts from the new package. If an old package is removed, the uninstallation scripts for the old package still get executed.
+ </div></div></div><div class="para">
+ When upgrading, you can also use the <code class="option">--repackage</code> option, which works the same as when removing packages. The <code class="option">--repackage</code> option tells the <code class="command">rpm</code> command to create a package, an RPM file, from any packages it would erase. Note that this option will not create a complete package. You will not be able to reinstall a package created by the <code class="option">--repackage</code> option. At best, the <code class="option">--repackage</code> option provides a backup of the old package, from which you could create a working package. Be careful with the <code class="option">--repackage</code> option.
+ </div><div class="para">
+ For example, the following command shows how to upgrade a package with the <code class="option">--repackage</code> option.
+ </div><pre class="screen">
+<strong class="userinput"><code>rpm -U --repackage jpilot-0.99.2-8.i386.rpm</code></strong></pre><div class="note"><div class="admonition_header"><h2>Consistent Package Names</h2></div><div class="admonition"><div class="para">
+ Upgrading and freshening depend on versions of a particular package keeping the same base package name between versions. For most packages this is true, but some packages violate this convention. For example, the Java programming developer's kit (JDK) uses the name <code class="filename">jdk-1.3.1_01.i386.rpm</code> for the 1.3.1 version but changes to <code class="filename">j2sdk-1_4_0_01-fcs-linux-i386.rpm</code> for the 1.4.0 version.
+ </div></div></div><div class="para">
+ Watch out for package-name changes like this.
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id569309" class="title">Smart Upgrades</h1></div></div></div><div class="para">
+ The <code class="command">rpm</code> command really shines in the upgrade process. Not only can you upgrade a package with one simple command, but the <code class="command">rpm</code> command has some built-in smarts that really help.
+ </div><div class="para">
+ When upgrading, the <code class="command">rpm</code> command checks each file in the package. It actually compares checksums of the files. An MD5 checksum is a small value computed from the data in a file. Any change to a file results in a different checksum value.
+ </div><div class="para">
+ The <code class="command">rpm</code> command compares the checksums of three versions of each file: the version of the file from the old package, the version of the file in the new package, and the version of the file on disk.
+ </div><div class="para">
+ The <code class="command">rpm</code> command looks at all three versions of the files to handle the common case where you may have edited a configuration file on disk. This is where the <code class="command">rpm</code> command starts working with some upgrade rules. Note that this special processing only applies to files marked as configuration files within the RPM. <a class="xref" href="#ch-specfiles">Cap. 9, <em>Working with Spec Files</em></a> covers how to mark files as configuration files.
+ </div><div class="para">
+ If the file on disk is identical to the file in the original package, meaning you have not changed the file, the <code class="command">rpm</code> command simply installs the file from the new version of the package on top of the old file.
+ </div><div class="para">
+ If the original package configuration file and the new package file are the same, that is, the file has not changed between the package versions, but the configuration file has been changed on disk, the <code class="command">rpm</code> command leaves that file alone. The <code class="command">rpm</code> command makes the assumption that if the file hasn’t changed between versions of the package, and you have modified the file, chances are your file will work with the new package. This takes care of the common case where you have edited an application’s configuration files.
+ </div><div class="para">
+ But if the file on disk is different from the original version of the file, and the file on disk is different from the new version of the file, the <code class="command">rpm</code> command installs the new version of the file on top of your changed version. This is because the new version of the file is known to work with the new package. The <code class="command">rpm</code> command saves your work by backing up your modified configuration file, renaming the file with a new <code class="filename">.rpmsave</code> extension. The <code class="command">rpm</code> command also warns you that it is backing up your modified file with a message that tells you the old file name and the new file name.
+ </div><div class="para">
+ If the RPM package uses the option <code class="command">%config(noreplace)</code> with the file, then the <code class="command">rpm</code> command will store the new file with a <code class="filename">rpm</code>new extension if you have modified the file on disk.
+ </div><div class="para">
+ </div></div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id809735" class="title">Freshening up</h1></div></div></div><div class="para">
+ A freshen operation means to install a new version of a package only if you have already installed another version of the package. Thus, a freshen operation is very similar to the upgrade operation except that a freshen requires you to have previously installed the package, while an upgrade can install a package for the first time. The basic syntax for freshening a package is to use the <code class="option">-F</code> option.
+ </div><pre class="screen">
+<strong class="userinput"><code>rpm -F <em class="replaceable"><code>package_name</code></em></code></strong></pre><div class="para">
+ You can also use the <code class="option">--freshen</code> long option in place of <code class="option">-F</code>.
+ </div><div class="para">
+ As with upgrading, the options to the <code class="command">rpm</code> command are the same, except for the <code class="option">-F</code> or <code class="option">--freshen</code> option that indicates the operation. These are the options discussed in the sections on upgrading and installing software.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id583586" class="title">Installing Packages</h1></div></div></div><div class="para">
+ The <code class="option">–i</code> or <code class="option">--install</code> option tells the <code class="command">rpm</code> command to run an installation operation, which, as you’d suspect, installs packages. The basic syntax is:
+ </div><pre class="screen">
+<strong class="userinput"><code>rpm –i <em class="replaceable"><code>filename.rpm</code></em></code></strong></pre><div class="para">
+ For example:
+ </div><pre class="screen">
+<strong class="userinput"><code>rpm –i jikes-1.16-1.i386.rpm</code></strong></pre><div class="warning"><div class="admonition_header"><h2>Use Upgrade, Rather Than Install</h2></div><div class="admonition"><div class="para">
+ You should normally install packages with <code class="command">rpm</code> <code class="option">-U</code>, not <code class="command">rpm</code> <code class="option">-i</code>. One of the main reasons is that <code class="command">rpm</code> <code class="option">-i</code> allows you to install multiple instances of the same (identical) package. This is usually not what you want.
+ </div></div></div><div class="para">
+ The <code class="command">rpm –i</code> command works with the installation options discussed previously. The <code class="option">–U</code>, <code class="option">-F</code> and <code class="option">–i</code> options all accept mostly the same options, except as discussed previously.
+ </div><div class="para">
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id816163" class="title">Installing Over the Internet</h1></div></div></div><div class="para">
+ All the commands to install packages covered so far assume that you have a local RPM file that you want to install. This is by far the most common case, but you can also use the <code class="command">rpm</code> command to install packages available on a network. With the <code class="command">rpm</code> command, you can get the packages to install by using the FTP or HTTP network protocols.
+ </div><div class="para">
+ With the File Transfer Protocol (FTP), the <code class="command">rpm</code> command connects to an FTP file server, downloads the named package, and installs that package. With the HyperText Transfer Protocol (HTTP) used for Web pages, the <code class="command">rpm</code> command connects to a Web server, downloads the named package, and installs that package.
+ </div><div class="warning"><div class="admonition_header"><h2>Name Spoofing</h2></div><div class="admonition"><div class="para">
+ When using either FTP or HTTP, you need to provide the name of the remote server. An attack on your system can compromise the system of converting server host names into network addresses, thus spoofing the <code class="command">rpm</code> command into installing a malicious package from the wrong host.
+ </div></div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id567974" class="title">Installing Using FTP</h1></div></div></div><div class="para">
+ The key to making the network protocols work with the <code class="command">rpm</code> command is that you need to create a URL for the remote file name. The basic format of the command follows:
+ </div><pre class="screen">
+<strong class="userinput"><code>rpm -i <em class="replaceable"><code>ftp://hostname/path/to/file/filename.rpm</code></em></code></strong></pre><div class="para">
+ Note the use of ftp: in the URL for the file.
+ </div><div class="para">
+ For example, the following downloads a package from an IBM FTP server.
+ </div><pre class="screen">
+<strong class="userinput"><code>rpm -i ftp://www-126.ibm.com/pub/jikes/jikes-1.16-1.src.rpm</code></strong></pre><div class="para">
+ Many FTP servers require users to log in. If you do not pass a user name and password on the <code class="command">rpm</code> command line, the <code class="command">rpm</code> command will prompt you for the missing data.
+ </div><div class="para">
+ You can add a user name prior to the host name, separating the user name from the host name with an at sign, @. For example:
+ </div><pre class="screen">
+<strong class="userinput"><code>rpm -i ftp://unclejoe@www-126.ibm.com/pub/jikes/jikes-1.16-1.src.rpm</code></strong></pre><div class="para">
+ In this case, the user name is unclejoe.
+ </div><div class="note"><div class="admonition_header"><h2>Credentials are Examples</h2></div><div class="admonition"><div class="para">
+ These examples do not show valid user names or passwords.
+ </div></div></div><div class="para">
+ With just a user name, the <code class="command">rpm</code> command will prompt you for the password. You can also include the password on the <code class="command">rpm</code> command line. Separate the user name from the password with a colon (:).
+ </div><div class="para">
+ For example:
+ </div><pre class="screen">
+<strong class="userinput"><code>rpm -i ftp://unclejoe:workers@www-126.ibm.com/pub/jikes/jikes-1.16-1.src.rpm</code></strong></pre><div class="para">
+ In this case, the user name is unclejoe and the password is workers.
+ </div><div class="para">
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id585685" class="title">Installing Using HTTP</h1></div></div></div><div class="para">
+ The <code class="command">rpm</code> command supports the HTTP protocol, used by most Web servers, as well as FTP. Similar to accessing a file via FTP, you need to pass the <code class="command">rpm</code> command a URL identifying the file. For example:
+ </div><pre class="screen">
+<strong class="userinput"><code>rpm –i http://ftp.redhat.com/pub/contrib/noarch/SRPMS/Squeak-sources-3-1.src.rpm</code></strong></pre></div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id567480" class="title">Installing source RPMs</h1></div></div></div><div class="para">
+ Source RPMs contain the source code used to build an application or programming library and the scripts used to build the software into the application or library. These scripts are called the recipes for building the software.
+ </div><div class="para">
+ Source RPMs usually contain program source code. They may also contain patches to program sources, scripts to build the program, special files used by desktop environments, icons, and other files considered to be part of the source code, such as programming guides.
+ </div><div class="note"><div class="admonition_header"><h2>Patch Files</h2></div><div class="admonition"><div class="para">
+ A patch is a file that contains just the differences between one version of a file and another. The differences include the actual text that has changed and enough contextual information that a program can locate where the changes are to take place. Usually, a patch is created with the <code class="command">diff</code> command, and the source code is patched with the <code class="command">patch</code> command.
+ </div></div></div><div class="para">
+ In most cases, each binary RPM will have a corresponding source RPM. This is not always true, however.
+ </div><div class="para">
+ One source RPM may contain enough shared program code to build multiple application RPMs. Furthermore, the source code is not available for all packages. Commercial applications, for example, rarely come with source code. In this case, obviously, no source RPMs are available. Or, a source RPM for a commercial application may provide no source code, but still provide a way to build the resulting application. See <a class="xref" href="#ch-specfiles">Cap. 9, <em>Working with Spec Files</em></a> for more on the source files and options for not including the sources in a source RPM.
+ </div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id730249" class="title">Open-source Software</h1></div></div></div><div class="para">
+ Linux, and thousands of applications that run on Linux, are called open-source software. That’s because the program source code for Linux and these applications are available.
+ </div><div class="para">
+ Many users feel having access to the source code is vital, especially because:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Vendors may stop supporting a package. With the sources, you can conceivably maintain the packages yourself, or more likely, others can take up the task and maintain these crucial packages.
+ </div></li><li class="listitem"><div class="para">
+ Having the source code makes it easier to track down and fix security vulnerabilities, although malicious users also have access to the same source code.
+ </div></li><li class="listitem"><div class="para">
+ You can enhance and extend packages for which the program sources are available.
+ </div></li></ul></div><div class="para">
+ Linux applications are available under a variety of open-source licenses. (In fact, it may seem that there are as many licenses as packages.) See the site <a href="http://www.opensource.org/licenses/">http://www.opensource.org/licenses/</a> for details.
+ </div></div></div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id1373416" class="title">Removing Software</h1></div></div></div><div class="para">
+ The <code class="command">rpm</code> command is good for more than just installing and upgrading software packages. Many times, you will need to remove packages as well.
+ </div><div class="para">
+ To remove a package, use the <code class="option">-e</code> option to the <code class="command">rpm</code> command, short for erase. The basic syntax follows:
+ </div><pre class="screen">
+<strong class="userinput"><code>rpm -e <em class="replaceable"><code>package_name</code></em></code></strong></pre><div class="note"><div class="admonition_header"><h2>Use Package Names, Not File Names</h2></div><div class="admonition"><div class="para">
+ When erasing or removing packages, use the package name, not the RPM file name. If you think about this, it makes sense. You don't always have the original RPM files when the time comes to remove a package.
+ </div></div></div><div class="para">
+ For example:
+ </div><pre class="screen">
+<strong class="userinput"><code>rpm -e jikes-1.16-1</code></strong></pre><div class="para">
+ This example removes the <code class="filename">jikes-1.16-1</code> package used in previous examples.
+ </div><div class="note"><div class="admonition_header"><h2><code class="systemitem">root</code> Access is Required</h2></div><div class="admonition"><div class="para">
+ You will need to use the <code class="systemitem">root</code> account, or super user, to remove most packages. This is because the package files themselves are protected. In addition, the RPM database is protected.
+ </div></div></div><div class="para">
+ This is only natural, since most RPMs are used to install system-level commands and applications.
+ </div><div class="para">
+ When removing a package, the <code class="command">rpm</code> command first checks that no other packages depend on the package you intend to remove. This is very important, since you otherwise can damage your Linux system by inadvertently removing packages needed by the rest of the system.
+ </div><div class="para">
+ The <code class="command">rpm</code> command supports the <code class="option">--test</code> option for removing packages as well as when installing. As with installing, the <code class="option">--test</code> option tells the <code class="command">rpm</code> command to test to see whether it can remove the given package but not to force the removal.
+ </div><div class="para">
+ For example, if you try to remove the very important-looking <code class="filename">syslinux-1.75-3</code> package, you can use the <code class="option">--test</code> option to see if this works.
+ </div><div class="para">
+ For example:
+ </div><pre class="screen">
+<strong class="userinput"><code>rpm -e --test syslinux-1.75-3</code></strong></pre><div class="para">
+ This command will issue an error such as the following:
+ </div><pre class="screen">
+<code class="computeroutput">error: Failed dependencies: syslinux is needed by (installed) mkbootdisk-1.4.8-1</code></pre><div class="note"><div class="admonition_header"><h2>Alternative Option Name</h2></div><div class="admonition"><div class="para">
+ When removing packages, you can use the long option name, <code class="option">--erase</code>, in place of <code class="option">–e</code>.
+ </div></div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id1067283" class="title">Checking that the package has been removed</h1></div></div></div><div class="para">
+ As before, you can use the <code class="command">rpm</code> <code class="option">–q</code> command to query whether a package is installed. After running the <code class="command">rpm</code> <code class="option">–e</code> command, you can run the <code class="command">rpm</code> <code class="option">–q</code> command to check whether the package has been removed. If the <code class="command">rpm</code> <code class="option">–q</code> command shows that the package is not installed, that tells you the erase operation has worked.
+ </div><div class="para">
+ For example:
+ </div><pre class="screen">
+<strong class="userinput"><code># rpm -q jikes</code></strong></pre><pre class="screen">
+<code class="computeroutput">jikes-1.16-1</code></pre><pre class="screen">
+<strong class="userinput"><code># rpm -e jikes-1.16-1 # rpm -q jikes</code></strong></pre><pre class="screen">
+<strong class="userinput"><code>package jikes is not installed</code></strong></pre></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id935675" class="title">Removing multiple packages at a time</h1></div></div></div><div class="para">
+ You can remove multiple packages at once by listing each package consecutively on the command line. For example:
+ </div><pre class="screen">
+<strong class="userinput"><code>rpm -e aspell-en-ca-0.33.7.1-16 aspell-en-gb-0.33.7.1-16</code></strong></pre><div class="para">
+ This command removes the <code class="filename">aspell-en-ca-0.33.7.1-16</code> and <code class="filename">aspell-en-gb-0.33.7.1-16</code> packages.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id787355" class="title">Options when removing packages</h1></div></div></div><div class="para">
+ The <code class="option">--allmatches</code> option tells the <code class="command">rpm</code> command to remove all packages with names that match the names you pass on the command line. If you do not use the <code class="option">--allmatches</code> option, the <code class="command">rpm</code> command will issue an error if more than one package matches the name or names you pass on the command line.
+ </div><div class="para">
+ The <code class="option">--nodeps</code> option tells the <code class="command">rpm</code> command to skip the test of dependencies. Use this option when you really, really, want to uninstall a package.
+ </div><div class="warning"><div class="admonition_header"><h2>Unsafe Commands</h2></div><div class="admonition"><div class="para">
+ Using any option that does not perform the full removal of the package, or skips some of the checks built into the <code class="command">rpm</code> command, can result in damage to your Linux system. Use these options with care.
+ </div></div></div><div class="para">
+ The <code class="option">--repackage</code> option, described previously, tells the <code class="command">rpm</code> command to create a package, an RPM file, from any packages it would erase. These packages will appear in the default repackage directory, which is normally <code class="filename">/var/spool/repackage/</code>. Check your RPM settings to be sure of the directory configured on your system.
+ </div><div class="note"><div class="admonition_header"><h2>Repackaged Files</h2></div><div class="admonition"><div class="para">
+ Packages created with the <code class="option">--repackage</code> option are not full packages. You cannot install these packages.
+ </div></div></div><div class="para">
+ Similar to the options when installing or upgrading packages, you can use the <code class="option">--noscripts</code> and <code class="option">--notriggers</code> options when removing packages. The <code class="option">--noscripts</code> option tells the <code class="command">rpm</code> command not to run any uninstallation scripts. You can refine this by using either <code class="option">--nopreun</code> or <code class="option">--nopostun</code> in place of the <code class="option">--noscripts</code> option.
+ </div><div class="para">
+ The <code class="option">--nopreun</code> option tells the <code class="command">rpm</code> command not to run the pre-uninstallation scripts. The <code class="option">--nopostun</code> option tells the <code class="command">rpm</code> command not to run the post-uninstallation scripts.
+ </div><div class="para">
+ The <code class="option">--notriggers</code> option works in a similar fashion. The <code class="option">--notriggers</code> option tells the <code class="command">rpm</code> command not to execute any triggers. For a finer grain of control, use <code class="option">--notriggerun</code> to prevent any uninstallation triggers and <code class="option">--notriggerpostun</code> to prevent any post-uninstallation triggers.
+ </div></div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id821991" class="title">Other <code class="command">rpm</code> Command Options</h1></div></div></div><div class="para">
+ Options such as <code class="option">-v</code> (for more verbose output) work with the <code class="command">rpm</code> command for installing, removing, and upgrading packages, as well as most other uses of the <code class="command">rpm</code> command.
+ </div><div class="para">
+ Other <code class="command">rpm</code> command options, which work with most RPM actions, include <code class="option">--quiet</code> to turn off most output except for errors, and <code class="option">--root</code>, covered previously.
+ </div><div class="para">
+ The <code class="option">--rcfile</code> option tells the <code class="command">rpm</code> command to use one or more other files to initialize the RPM system. These files tell the <code class="command">rpm</code> command the system architecture, operating system, and default location of the RPM database, among a host of other settings.
+ </div><div class="note"><div class="admonition_header"><h2><code class="filename">rc</code> Files</h2></div><div class="admonition"><div class="para">
+ The term <code class="filename">rc</code> comes from Unix shells, with initialization files such as <code class="filename">.cshrc</code> for the C shell, <code class="command">csh</code>. The term <code class="filename">rc</code> was originally a shorthand for run commands. An <code class="filename">rc</code> is a file of commands that run when the application starts up. For example, the C shell, <code class="command">csh</code>, runs the commands in file named <code class="filename">.cshrc</code> when the shell starts.
+ </div></div></div><div class="para">
+ In most cases, the application looks in the user home directory for a specific file tied to the application. For the <code class="command">rpm</code> command, this file is <code class="filename">.rpmrc</code>. The leading period makes the file hidden for most directory listings.
+ </div><div class="para">
+ In addition to the user-level file of commands, most applications supporting this mechanism have a way for site administrators to customize the command for all users. For example, your system may have a file named <code class="filename">/etc/rpmrc</code> (with no leading period) that customizes the <code class="command">rpm</code> command for all users on your system. See <a class="xref" href="#ch-customizing-rpm">Cap. 20, <em>Customizing RPM Behavior</em></a> for a more in-depth look at the chain of these files.
+ </div><div class="para">
+ The syntax for the <code class="option">--rcfile</code> option is
+ </div><div class="para">
+ <code class="option">--rcfile</code> <em class="replaceable"><code>filename</code></em>
+ </div><div class="para">
+ You can also supply more than one file name. This syntax follows:
+ </div><div class="para">
+ <code class="option">--rcfile</code> <em class="replaceable"><code>filename1:filename2:filename3</code></em>
+ </div><div class="para">
+ Separate each file name with a colon.
+ </div><div class="para">
+ With Red Hat Linux, the default set of initialization files are:
+ </div><pre class="screen">
+<code class="computeroutput">/usr/lib/rpm/rpmrc:/usr/lib/rpm/redhat/rpmrc:/etc/rpmrc:~/.rpmrc</code></pre><div class="note"><div class="admonition_header"><h2>Tilde (~) Denotes Home Directory</h2></div><div class="admonition"><div class="para">
+ The <code class="filename">~/.rpmrc</code> means to look in the user's home directory for a file named <code class="filename">rpmrc</code>.
+ </div><div class="para">
+ You can use the <code class="option">--showrc</code> option to list all the <code class="filename">rc</code> settings.
+ </div></div></div><div class="note"><div class="admonition_header"><h2>The <code class="option">--showrc</code> Option</h2></div><div class="admonition"><div class="para">
+ See <a class="xref" href="#ch-customizing-rpm">Cap. 20, <em>Customizing RPM Behavior</em></a> for more on the <code class="option">--showrc</code> option.
+ </div></div></div><div class="para">
+ The <code class="option">--version</code> option tells the <code class="command">rpm</code> command to print out the version number of the command and then exit. For example:
+ </div><pre class="screen">
+<strong class="userinput"><code>rpm --version</code></strong></pre><div class="para">
+ This command prints out a version number, like the following:
+ </div><pre class="screen">
+<code class="computeroutput">RPM version 4.1</code></pre><div class="para">
+ The <code class="option">--dbpath</code> option, mentioned previously, tells the <code class="command">rpm</code> command to use a different RPM database. This is useful when testing a complete system install, where you want to change the RPM database but don't want that to affect your running Linux system. In this case, you can use a different RPM database and test out your changes. The basic syntax for this option is:
+ </div><div class="para">
+ <code class="option">--dbpath</code> <em class="replaceable"><code>directory_name</code></em>
+ </div><div class="para">
+ The <code class="option">--pipe</code> option tells the <code class="command">rpm</code> command to send, or pipe, its output to another program. The syntax for this option is:
+ </div><div class="para">
+ <code class="option">--pipe</code> <em class="replaceable"><code>command_to_send_out_to</code></em>
+ </div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id566157" class="title">Summary</h1></div></div></div><div class="para">
+ This chapter covered the easy part of managing packages, the common actions of installing, removing, and upgrading software.
+ </div><div class="para">
+ The <code class="command">rpm</code> <code class="option">–e</code> command removes packages. The <code class="command">rpm</code> <code class="option">–U</code> command upgrades packages by installing new packages and removing old versions of all the packages upgraded. RPM upgrades also work for installing new packages. The <code class="command">rpm</code> <code class="option">–F</code> command freshens packages. This command only upgrades a package if an older version of the package has already been installed. The <code class="command">rpm</code> <code class="option">–i</code> command installs packages.
+ </div><div class="para">
+ The table below summarizes the <code class="command">rpm</code> command-line options for installing, removing, and upgrading packages.
+ </div><div class="table" id="tb-rpm-command-options"><h6>Tabel 3.3. Installing, Removing, and Upgrading with the <code class="command">rpm</code> command</h6><div class="table-contents"><table summary="Installing, Removing, and Upgrading with the rpm command" border="1"><colgroup><col class="Command" width="50%" /><col class="Usage" width="50%" /></colgroup><thead><tr><th>
+ Command
+ </th><th>
+ Usage
+ </th></tr></thead><tbody><tr><td>
+ <div class="para">
+ <code class="command">rpm –i <em class="replaceable"><code>install_options package_files</code></em></code>
+ </div>
+
+ </td><td>
+ <div class="para">
+ Install packages.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ <code class="command">rpm –e <em class="replaceable"><code>remove_options packages</code></em></code>
+ </div>
+
+ </td><td>
+ <div class="para">
+ Erase, remove, packages.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ <code class="command">rpm –U <em class="replaceable"><code>install_options package_files</code></em></code>
+ </div>
+
+ </td><td>
+ <div class="para">
+ Upgrade or install packages. Use this option for installations.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ <code class="command">rpm –Uvh <em class="replaceable"><code>install_options package_files</code></em></code>
+ </div>
+
+ </td><td>
+ <div class="para">
+ Upgrade or install packages with extra output. This is the recommended command to install packages.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ <code class="command">rpm –F <em class="replaceable"><code>install_options package_files</code></em></code>
+ </div>
+
+ </td><td>
+ <div class="para">
+ Freshen packages.
+ </div>
+
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ Unfortunately, modern system management gets more complex than that. The next chapter delves into package dependencies and the nightmare you can get into when one package depends on another that then depends on another, ad infinitum.
+ </div></div></div><div xml:lang="ro" class="chapter" id="ch-using-rpm-db" lang="ro"><div class="titlepage"><div><div><h2 class="title">Cap. 4. Using the RPM Database</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#RPM_Guide-Using_RPM_DB-querying_database">4.1. Querying the RPM Database</a></span></dt><dd><dl><dt><span class="section"><a href="#id631876">4.1.1. Querying packages</a></span></dt><dt><span class="section"><a href="#RPM_Guide-Using_RPM_DB-query_everything">4.1.2. Querying everything</a></span></dt><dt><span class="section"><a href="#RPM_Guide-Using_RPM_DB-refining_query">4.1.3. Refining the query</a></span></dt><dt><span class="section"><a href="#RPM_Guide-Using_RPM_DB-which_package">4.1.4. Finding which packages own files</a></span></dt></dl></dd><dt><span class="section"><a href="#RPM_Guide-Using_RPM_DB-getting_information">4.2. Getting Information on Packages</a></span></dt><dd><dl><dt><span class="section"><a href="#RPM_Guide-U
Sing_RPM_DB-getting_information-describing_packages">4.2.1. Describing packages</a></span></dt><dt><span class="section"><a href="#RPM_Guide-Using_RPM_DB-package_groups">4.2.2. Package groups</a></span></dt><dt><span class="section"><a href="#id491747">4.2.3. Listing the files in a package</a></span></dt><dt><span class="section"><a href="#RPM_Guide-Using_RPM_DB-listing_conf_files">4.2.4. Listing the configuration files for a package</a></span></dt><dt><span class="section"><a href="#id1301235">4.2.5. Listing the documentation files for a package</a></span></dt><dt><span class="section"><a href="#RPM_Guide-Using_RPM_DB-file_state">4.2.6. Listing the state of the files in a package</a></span></dt><dt><span class="section"><a href="#RPM_Guide-Using_RPM_DB-listing_scripts">4.2.7. Listing the scripts in a package</a></span></dt><dt><span class="section"><a href="#RPM_Guide-Using_RPM_DB-Listing_changed">4.2.8. Listing what has changed</a></span></dt><dt><span class="section"><a h
ref="#RPM_Guide-Using_RPM_DB-Combining_queries">4.2.9. Combining queries</a></span></dt><dt><span class="section"><a href="#RPM_Guide-Using_RPM_DB-Cusomt_queries">4.2.10. Creating custom queries</a></span></dt><dt><span class="section"><a href="#RPM_Guide-Using_RPM_DB-Query_format_tags">4.2.11. Working With Query Format Tags</a></span></dt><dt><span class="section"><a href="#RPM_Guide-Using_RPM_DB-Querying_for_package_information">4.2.12. Querying for Package Information</a></span></dt><dt><span class="section"><a href="#RPM_Guide-Using_RPM_DB-Formatting_arrays">4.2.13. Formatting Arrays</a></span></dt><dt><span class="section"><a href="#RPM_Guide-Using_RPM_DB-Special_formatting">4.2.14. Special Formatting</a></span></dt><dt><span class="section"><a href="#RPM_Guide-Using_RPM_DB-querying_pacakge_dependencies">4.2.15. Querying for Package Dependencies</a></span></dt><dt><span class="section"><a href="#RPM-Guide-Using_RPM_DB-Querying_file_information">4.2.16. Querying for File
Information</a></span></dt><dt><span class="section"><a href="#RPM_Guide-Using_RPM_DB-Other_Query_Format_Tags">4.2.17. Other Query Format Tags</a></span></dt></dl></dd><dt><span class="section"><a href="#id878995">4.3. Other queries</a></span></dt><dt><span class="section"><a href="#RPM_Guide-Using_RPM_DB-Getting_information_on_package_files">4.4. Getting Information on Package Files</a></span></dt><dd><dl><dt><span class="section"><a href="#RPM_Guide_Using_RPM_DB-Querying_package_files_remotely">4.4.1. Querying Package Files Remotely</a></span></dt><dt><span class="section"><a href="#RPM-Guide-Using_RPM-DB-verifying_packages">4.4.2. Verifying Installed RPM Packages</a></span></dt><dt><span class="section"><a href="#RPM_GUide-Using_RPM_DB-working_with_RPM_db">4.4.3. Working With the RPM Database</a></span></dt><dt><span class="section"><a href="#RPM_Guide-Using_RPM_DB-summary">4.4.4. Summary</a></span></dt></dl></dd></dl></div><div class="para">
+ This chapter covers:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Querying the RPM database
+ </div></li><li class="listitem"><div class="para">
+ Getting information on RPM files
+ </div></li><li class="listitem"><div class="para">
+ Finding out which packages own files on your system
+ </div></li><li class="listitem"><div class="para">
+ Verifying installed packages
+ </div></li><li class="listitem"><div class="para">
+ Backing up the RPM database
+ </div></li><li class="listitem"><div class="para">
+ Repairing damaged RPM databases
+ </div></li></ul></div><div class="para">
+ Every package you install with RPM is recorded in the RPM database. The RPM system includes commands to query this database to find out which packages are installed and to provide quite a few details about these packages.
+ </div><div class="para">
+ This chapter covers querying both the RPM database and RPM package files. Both types of query are important:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Query the RPM database to see what is installed, or not installed, on your system.
+ </div></li><li class="listitem"><div class="para">
+ Query package files to see what the files require, as well as what the files provide.
+ </div></li></ul></div><div class="para">
+ In addition to querying the RPM database, you can use the database to verify packages. Since this database is so important to the management of your Linux system, this chapter covers how to back it up, as well as how to repair a damaged RPM database.
+ </div><div class="section" id="RPM_Guide-Using_RPM_DB-querying_database"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="RPM_Guide-Using_RPM_DB-querying_database">4.1. Querying the RPM Database</h2></div></div></div><div class="para">
+ In <a class="xref" href="#ch-using-rpm">Cap. 3, <em>Using RPM</em></a> , you saw that the rpm command usually takes one major command-line option to tell it the operation to perform and a myriad of command-line options to customize the operation. The rpm command may also take the name of one or more RPM package files or the name of one or more installed packages. For example, the <code class="command">rpm –i</code> command performs an installation operation, and the <code class="command">rpm –U</code> command performs an upgrade.
+ </div><div class="para">
+ For querying the RPM database, the major command-line option is <code class="literal">–q</code>, short for query. This option tells the rpm command to query the RPM database. You can also use the long option <code class="literal">--query</code>.
+ </div><div class="para">
+ In the last few chapters, you've used the <code class="literal">–q</code> option with the rpm command to query just for the presence or absence of installed packages. You can expand the <code class="literal">-q</code> option to perform a wide array of queries to find out information about the packages installed on a Linux system.
+ </div><div class="section"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id631876">4.1.1. Querying packages</h3></div></div></div><div class="para">
+ The basic format of the <code class="command">rpm –q</code> command follows:
+ </div><div class="para">
+ <code class="command">rpm –q <em class="replaceable"><code>package_name</code></em></code>
+ </div><div class="para">
+ You need to provide the name of a package to query. For example:
+ </div><div class="para">
+ <code class="command">rpm -q telnet-0.17</code>
+ </div><div class="para">
+ This command returns the name of the package, if installed. For example:
+ </div><pre class="screen">
+ telnet-0.17-20
+</pre><div class="para">
+ If the package is not installed, you’ll see a message like the following:
+ </div><pre class="screen">
+ package telnet-0.17 is not installed
+</pre><div class="para">
+ You can provide the whole package name to the rpm command, which includes the name, the version, and the RPM package number, as discussed in <a class="xref" href="#ch-rpm-overview">Cap. 2, <em>RPM Overview</em></a> . You can also just provide the name and version number, as shown previously, or just the base name of the package.
+ </div><div class="para">
+ For example, the following command uses just the base name of the package:
+ </div><div class="para">
+ <code class="command">rpm -q telnet</code>
+ </div><pre class="screen">
+ telnet-0.17-20
+</pre><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ The rpm –q command expects a package name. Although it supports some amount of customized queries, you really need to know which packages you want the rpm command to report on.
+ </div></div></div><div class="para">
+ You can provide more than one package name; the rpm command reports on each package, as shown following.
+ </div><div class="para">
+ <code class="command">rpm -q telnet telnet-server</code>
+ </div><pre class="screen">
+ telnet-0.17-20
+ telnet-server-0.17-20
+</pre><div class="para">
+ You need to change the way you query if you want to perform searches when you do not know the full package name in advance. The following sections cover options for creating various queries.
+ </div></div><div class="section" id="RPM_Guide-Using_RPM_DB-query_everything"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="RPM_Guide-Using_RPM_DB-query_everything">4.1.2. Querying everything</h3></div></div></div><div class="para">
+ Up to now, we have used the rpm command to query only for specific packages. The <code class="literal">–a</code> option tells the rpm command to query for all packages. You can also use the longer option, <code class="literal">--all</code>, in place of <code class="literal">–a</code>.
+ </div><div class="para">
+ For example:
+ </div><div class="para">
+ <code class="command">rpm -qa</code>
+ </div><div class="para">
+ This command returns every package installed on your system, quite a few packages. The packages are returned one per line, as shown following.
+ </div><div class="para">
+
+<pre class="screen">m17n-db-gujarati-1.5.5-4.fc13.noarch
+libvisual-0.4.0-9.fc12.x86_64
+hal-filesystem-0.5.14-3.fc13.x86_64
+fedora-logos-13.0.2-1.fc13.noarch
+kdepim-runtime-libs-4.4.5-1.fc13.x86_64
+lpsolve-5.5.0.15-3.fc13.x86_64
+kipi-plugins-1.2.0-1.fc13.x86_64
+kbd-1.15-9.fc12.x86_64
+perl-Glib-1.201-4.fc12.x86_64
+kdeplasma-addons-4.4.5-1.fc13.x86_64
+</pre>
+
+ </div><div class="para">
+ This output has been modified to meet size constraints. Try the <code class="command">rpm –qa</code> command to see the full output for your system.
+ </div><div class="para">
+ There may be over a thousand packages on your system. Even so, the <code class="command">rpm –qa</code> command executes surprisingly fast.
+ </div></div><div class="section" id="RPM_Guide-Using_RPM_DB-refining_query"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="RPM_Guide-Using_RPM_DB-refining_query">4.1.3. Refining the query</h3></div></div></div><div class="para">
+ When you query all the installed packages, you get too much output for most purposes, other than to get a general idea of the magnitude of packages installed on your system. But if you cannot remember a package name, there's no real option, other than writing your own RPM query program.
+ </div><div class="para">
+ You can take advantage of the power of the Linux shells, though, and the wonderful ability to pipe the output of one command into another to work around this problem. With the large amount of output, you may want to pipe the output to the <code class="command">more</code> or <code class="command">less</code> programs, and display the output one page at a time.
+ </div><div class="para">
+ Even with <code class="command">more</code> and <code class="command">less</code>, the <code class="command">rpm –qa</code> command outputs too much information to be really useful, unless you can somehow filter the information automatically.
+ </div><div class="section" id="RPM_Guide-Using_RPM_DB-refining-grep"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="RPM_Guide-Using_RPM_DB-refining-grep">4.1.3.1. Piping the Output To grep</h4></div></div></div><div class="para">
+ The Linux (and Unix) <code class="command">grep</code> command provides a powerful tool for filtering through textual data. If you pipe the output of the <code class="command">rpm –qa</code> command into the <code class="command">grep</code> command, you have a powerful search engine at your fingertips.
+ </div><div class="para">
+ For example, if you know that most packages that provide tools for the SSH service have "ssh" in their names, you can find all these packages by using a command like the following:
+ </div><div class="para">
+ <code class="command">rpm -qa | grep ssh</code>
+ </div><div class="para">
+ This command outputs packages such as the following:
+ </div><pre class="screen">ksshaskpass-0.5.3-1.fc13.x86_64
+openssh-server-5.4p1-3.fc13.x86_64
+libssh2-1.2.4-1.fc13.i686
+openssh-askpass-5.4p1-3.fc13.x86_64
+libssh2-1.2.4-1.fc13.x86_64
+openssh-5.4p1-3.fc13.x86_64
+openssh-clients-5.4p1-3.fc13.x86_64
+libssh-0.4.4-1.fc13.x86_64</pre><div class="para">
+ You can also use the --pipe option to the rpm command, introduced in <a class="xref" href="#ch-using-rpm">Cap. 3, <em>Using RPM</em></a> . With this option, your command becomes:
+ </div><div class="para">
+ <code class="command">rpm -qa --pipe "grep ssh"</code>
+ </div><div class="note"><div class="admonition_header"><h2>Notă</h2></div><div class="admonition"><div class="para">
+ <a class="xref" href="#ch-rpm-programming-python">Cap. 16, <em>Programming RPM with Python</em></a> covers programming with the RPM system with the Python scripting language.
+ </div></div></div><div class="para">
+ You can take advantage of some of the options that the grep command supports, including -i for ignoring the case of the string to match, --regexp to pass a regular expression to grep, and -v, to output only those entries that do not match the search string.
+ </div><div class="note"><div class="admonition_header"><h2>Notă</h2></div><div class="admonition"><div class="para">
+ If you are unfamiliar with grep, the online manual pages for the grep command provide a listing of the command-line options available for grep as well as a short tutorial on regular expressions supported by grep.
+ </div></div></div><div class="para">
+ Table 5-1 lists some of the common package-naming conventions. Remember that these are just conventions, not hard-and-fast rules. You can use these conventions in concert with rpm queries.
+ </div><div class="para">
+ Table 5-1 Common Naming Conventions on Linux
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Convention
+ </div>
+
+ </td><td>
+ <div class="para">
+ Usually indicates
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Starts with g
+ </div>
+
+ </td><td>
+ <div class="para">
+ GNOME desktop application or a GNU application, especially GNU C programming tools and libraries
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Starts with j
+ </div>
+
+ </td><td>
+ <div class="para">
+ Cross-platform Java application
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Starts with k
+ </div>
+
+ </td><td>
+ <div class="para">
+ KDE desktop application, Linux kernel package, or Kerberos security package
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Starts with py
+ </div>
+
+ </td><td>
+ <div class="para">
+ Python application
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Starts with rh
+ </div>
+
+ </td><td>
+ <div class="para">
+ Red Hat application, usually for configuring your system
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Starts with tk
+ </div>
+
+ </td><td>
+ <div class="para">
+ Graphical Tcl application
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Starts with x
+ </div>
+
+ </td><td>
+ <div class="para">
+ X Window System graphical desktop application
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Ends with wm
+ </div>
+
+ </td><td>
+ <div class="para">
+ Window manager for controlling the layout of windows on the screen
+ </div>
+
+ </td></tr></tbody></table></div></div><div class="section" id="RPM_Guide-Using_RPM_DB-refining-wildcards"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="RPM_Guide-Using_RPM_DB-refining-wildcards">4.1.3.2. Querying with Wildcards</h4></div></div></div><div class="para">
+ In addition to using other Linux commands, the rpm command supports some search options. You can pass a wildcard to <code class="command">rpm –qa</code> (but not just <code class="command">rpm –q</code>, you need the <code class="literal">–a</code> to look for all packages). For example:
+ </div><div class="para">
+ <code class="command">rpm -qa "kernel*"</code>
+ </div><pre class="screen">kernel-2.6.33.6-147.fc13.x86_64
+kernel-2.6.33.5-112.fc13.x86_64
+kernel-devel-2.6.33.5-112.fc13.x86_64
+kernel-headers-2.6.33.6-147.fc13.x86_64
+kernel-2.6.33.5-124.fc13.x86_64
+kernel-devel-2.6.33.5-124.fc13.x86_64
+kernel-devel-2.6.33.6-147.fc13.x86_64</pre><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ The quotation marks around "kernel*" are to prevent the Linux shell from expanding the wildcard character, *, to try to match a list of file names in the local directory. By passing the command-line parameter as "kernel*", the rpm program gets to see the * character. Otherwise, the shell expands the parameter and the program, rpm in this case, never sees the *.
+ </div></div></div><div class="para">
+ This command searches for all package names starting with send. You can reverse this with an exclamation mark. For example:
+ </div><div class="para">
+ $ rpm -qa '!send*'
+ </div><div class="para">
+ This command works sort of like <code class="command">grep –v</code> and searches for all packages that do not start with "send".
+ </div><div class="para">
+ There are quite a few other Linux commands you can use in pipelines with the <code class="command">rpm –qa</code> command to better filter and display the data, such as <code class="command">wc –l</code> to count the number of packages that you query. You can also use a number of other query options to find out more specialized information from the RPM database.
+ </div></div></div><div class="section" id="RPM_Guide-Using_RPM_DB-which_package"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="RPM_Guide-Using_RPM_DB-which_package">4.1.4. Finding which packages own files</h3></div></div></div><div class="para">
+ One of the common problems with package management comes when you want to track a given file on your system back to the package that “owns†the file (that is, the package that, when installed, installed the particular file).
+ </div><div class="para">
+ The <code class="option">-qf</code> option tells the rpm command to query for all packages that own a particular file. You can also use the longer option, <code class="option">--file</code>, in place of <code class="option">–f</code>. The basic syntax follows:
+ </div><div class="para">
+ <code class="command">rpm -qf <em class="replaceable"><code>filename</code></em></code>
+ </div><div class="para">
+ For example, the grep command used in previous examples is really a file. (Just about all Linux commands are a file of some sort, be it a shell script or an executable application.) You can use a few Linux commands to determine which package provides this handy program.
+ </div><div class="para">
+ First, we need the exact path to the file. For Linux commands, you can use the <code class="command">which</code> command, if the program is in your path. (The grep program must be in your path, or commands with grep will fail.)
+ </div><div class="para">
+ Try the following command:
+ </div><div class="para">
+ <code class="command">which grep</code>
+ </div><div class="para">
+ This command returns the path to grep:
+ </div><div class="para">
+
+<pre class="screen">/bin/grep</pre>
+
+ </div><div class="para">
+ We can now check which package owns this file with the following command:
+ </div><div class="para">
+ <code class="command">rpm -qf /bin/grep</code>
+ </div><div class="para">
+
+<pre class="screen">grep-2.6.3-1</pre>
+
+ </div><div class="para">
+ You can also use the Linux back-tick operator to perform this check with one command.
+ </div><div class="para">
+ <code class="command">rpm -qf `which grep`</code>
+ </div><div class="para">
+
+<pre class="screen">grep-2.6.3-1</pre>
+
+ </div><div class="para">
+ If you use the bash shell, you can use the $(command parameters) syntax in place of the back tick, or `, characters. For example:
+ </div><div class="para">
+ <code class="command">rpm -qf $(which grep)</code>
+ </div><div class="para">
+
+<pre class="screen">grep-2.6.3-1</pre>
+
+ </div><div class="para">
+ If no package owns a given file, you’ll see output like the following:
+ </div><div class="para">
+ <code class="command">rpm -qf mail</code>
+ </div><div class="para">
+
+<pre class="screen">file mail is not owned by any package</pre>
+
+ </div><div class="para">
+ Often, the package that owns a file does not have an intuitive name. The ssh command, for example, is owned by the openssh-clients package, as shown following:
+ </div><div class="para">
+ <code class="command">rpm -qf `which ssh`</code>
+ </div><div class="para">
+
+<pre class="screen">openssh-clients-5.4p1-3</pre>
+
+ </div><div class="para">
+ As you can see, the name of a command does not always correspond directly to the name of the package that provides that command. This is where the <code class="command">rpm –qf</code> command proves very useful. Otherwise, you would just have to know that OpenSSH is the project responsible for this command.
+ </div><div class="note"><div class="admonition_header"><h2>Symbolic Links</h2></div><div class="admonition"><div class="para">
+ The <code class="command">rpm -qf</code> command follows symbolic links. This was not always true with older versions of RPM, but modern RPM versions can trace package ownership to files placed in linked directories.
+ </div><div class="para">
+ For example, the directory /usr/lib/X11 is a link to the real directory, /usr/X11R6/lib/X11. You can track the package ownership of a file in that directory, XKeysymDB, for example, by using the following command:
+ </div><div class="para">
+ <code class="command">rpm -qf /usr/lib/X11/XKeysymDB</code>
+ </div><div class="para">
+
+<pre class="screen">XFree86-4.2.0-72</pre>
+
+ </div><div class="para">
+ This file, XKeysymDB, really resides in /usr/X11R6/lib/X11.
+ </div></div></div></div></div><div class="section" id="RPM_Guide-Using_RPM_DB-getting_information"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="RPM_Guide-Using_RPM_DB-getting_information">4.2. Getting Information on Packages</h2></div></div></div><div class="para">
+ The query options for the rpm command include a whole set of options that return information about the files that make up a package, the scripts, and other parts of the original package. The following sections cover these options.
+ </div><div class="section" id="RPM_Guide-USing_RPM_DB-getting_information-describing_packages"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="RPM_Guide-USing_RPM_DB-getting_information-describing_packages">4.2.1. Describing packages</h3></div></div></div><div class="para">
+ The <code class="option">–i</code> option with an rpm query command tells the rpm command to output descriptive information about the package. You can also use the longer option, <code class="option">--info</code>, in place of <code class="option">–i</code>. The basic syntax is:
+ </div><div class="para">
+ <code class="command">rpm -qi <em class="replaceable"><code>package</code></em></code>
+ </div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ The order of the command-line options is very important. Remember that the rpm command has the following general syntax:
+ </div><div class="para">
+ <code class="command">rpm <em class="replaceable"><code>–MajorOperation</code></em> <em class="replaceable"><code>–extra_options packages_or_files</code></em></code>
+ </div><div class="para">
+ <code class="command">rpm –i</code> installs packages and <code class="command">rpm –q</code> queries packages. The <code class="command">rpm –qi</code> command outputs the descriptive information on packages. If you make a mistake and place the <code class="literal">i</code> in front of the <code class="literal">q</code>, you are telling the rpm command to perform a different operation.
+ </div></div></div><div class="para">
+ When you run this command, being very careful with the order of the options, you’ll see output like the following, which describes the tcsh shell package.
+ </div><div class="para">
+ <code class="command">rpm -qi tcsh-6.17-6</code>
+ </div><pre class="screen">Name : tcsh Relocations: (not relocateable)
+Version : 6.17 Vendor: Fedora Project
+Release : 6 Build Date: Tue 15 Dec 2009 11:28:11 AM EST
+Install Date: Fri 27 Aug 2010 07:41:03 PM EDT Build Host: localhost
+Group : System Environment/Shells Source RPM: tcsh-6.17-6.fc13.src.rpm
+Size : 1191282 License: BSD
+Signature : RSA/SHA256, Fri 05 Feb 2010 09:30:43 AM EST, Key ID 7edc6ad6e8e40fde
+Packager : Fedora Project
+URL : http://www.tcsh.org/
+Summary : An enhanced version of csh, the C shell
+Description :
+Tcsh is an enhanced but completely compatible version of csh, the C
+shell. Tcsh is a command language interpreter which can be used both
+as an interactive login shell and as a shell script command processor.
+Tcsh includes a command line editor, programmable word completion,
+spelling correction, a history mechanism, job control and a C language
+like syntax.
+</pre><div class="para">
+ The sections on custom queries following in this chapter show how you can query for any information stored in a package header, including all of the information shown with <code class="command">rpm –qi</code>, as well as any other header tag.
+ </div></div><div class="section" id="RPM_Guide-Using_RPM_DB-package_groups"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="RPM_Guide-Using_RPM_DB-package_groups">4.2.2. Package groups</h3></div></div></div><div class="para">
+ RPM packages can be placed into groups, merely arbitrary names for a set of packages. The <code class="command">rpm –qi</code> command, shown previously, lists the group for a package, if there is one. For the tcsh package shown in the previous example, the package is <code class="literal">System Environment/Shells</code>.
+ </div><div class="para">
+ The <code class="option">–g</code> option to <code class="command">rpm –q</code> tells rpm to list all the packages in a given group. You can also use the longer option, <code class="option">--group</code>, in place of <code class="option">–g</code>. The basic syntax follows:
+ </div><div class="para">
+ <code class="command">rpm –qg <em class="replaceable"><code>group_name</code></em></code>
+ </div><div class="para">
+ For example:
+ </div><div class="para">
+ <code class="command">rpm -qg "System Environment/Shells"</code>
+ </div><pre class="screen">dash-0.5.5.1-3.x86_64
+bash-4.1.7-1.x86_64
+tcsh-6.17-6.x86_64</pre><div class="note"><div class="admonition_header"><h2>Spaces in group names</h2></div><div class="admonition"><div class="para">
+ This group has a space in its name, so you need quotation marks to pass the group name as one parameter to the rpm command.
+ </div></div></div></div><div class="section"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id491747">4.2.3. Listing the files in a package</h3></div></div></div><div class="para">
+ The <code class="option">–l</code> (ell) option queries all the files in a package. You can also use the longer option, --list, in place of –l. The basic syntax is:
+ </div><div class="para">
+ rpm –ql package
+ </div><div class="para">
+ For example, to query the files in the tcsh package, you’ll see the following:
+ </div><div class="para">
+ <code class="command">rpm -ql tcsh</code>
+ </div><pre class="screen">
+ /bin/csh
+ /bin/tcsh
+ /usr/share/doc/tcsh-6.10
+ /usr/share/doc/tcsh-6.10/FAQ
+ /usr/share/doc/tcsh-6.10/Fixes
+ /usr/share/doc/tcsh-6.10/NewThings
+ /usr/share/doc/tcsh-6.10/complete.tcsh
+ /usr/share/doc/tcsh-6.10/eight-bit.txt
+ /usr/share/doc/tcsh-6.10/tcsh.html
+ /usr/share/doc/tcsh-6.10/tcsh.html/header.html
+ /usr/share/doc/tcsh-6.10/tcsh.html/index.html
+ /usr/share/doc/tcsh-6.10/tcsh.html/lists.html
+ /usr/share/doc/tcsh-6.10/tcsh.html/tcsh.man
+ /usr/share/doc/tcsh-6.10/tcsh.html/tcsh.man2html
+ /usr/share/doc/tcsh-6.10/tcsh.html/top.html
+ /usr/share/locale/de/LC_MESSAGES/tcsh
+ /usr/share/locale/el/LC_MESSAGES/tcsh
+ /usr/share/locale/es/LC_MESSAGES/tcsh
+ /usr/share/locale/fr/LC_MESSAGES/tcsh
+ /usr/share/locale/it/LC_MESSAGES/tcsh
+ /usr/share/locale/ja/LC_MESSAGES/tcsh
+ /usr/share/man/man1/tcsh.1.gz
+</pre><div class="note"><div class="admonition_header"><h2>Listing multiple packages</h2></div><div class="admonition"><div class="para">
+ You can pass more than one package name to this option, but it won’t tell you which package owns which file. Use the <code class="option">--filesbypkg</code> option to list files by package.
+ </div><div class="para">
+ For example:
+ </div><div class="para">
+ <code class="command">rpm -q --filesbypkg file openssh-clients</code>
+ </div><pre class="screen">
+ file /usr/bin/file
+ file /usr/share/magic
+ file /usr/share/magic.mgc
+ file /usr/share/magic.mime
+ file /usr/share/man/man1/file.1.gz
+ file /usr/share/man/man5/magic.5.gz
+ openssh-clients /etc/ssh/ssh_config
+ openssh-clients /usr/bin/sftp
+ openssh-clients /usr/bin/slogin
+ openssh-clients /usr/bin/ssh
+ openssh-clients /usr/bin/ssh-add
+ openssh-clients /usr/bin/ssh-agent
+ openssh-clients /usr/bin/ssh-keyscan
+ openssh-clients /usr/share/man/man1/sftp.1.gz
+ openssh-clients /usr/share/man/man1/slogin.1.gz
+ openssh-clients /usr/share/man/man1/ssh-add.1.gz
+ openssh-clients /usr/share/man/man1/ssh-agent.1.gz
+ openssh-clients /usr/share/man/man1/ssh-keyscan.1.gz
+ openssh-clients /usr/share/man/man1/ssh.1.gz
+</pre><div class="para">
+ Use this option without –l, because the –l option will also list the files alone, without any package name.
+ </div></div></div><div class="para">
+ The –v (verbose) option can give you more information on the files when used with the various query options. For example:
+ </div><div class="para">
+ <code class="command">rpm -qlv tcsh</code>
+ </div><pre class="screen">
+lrwxrwxrwx 1 root root 4 Dec 15 2009 /bin/csh -> tcsh
+-rwxr-xr-x 1 root root 386984 Dec 15 2009 /bin/tcsh
+drwxr-xr-x 2 root root 0 Dec 15 2009 /usr/share/doc/tcsh-6.17
+-rw-r--r-- 1 root root 17782 Mar 2 2006 /usr/share/doc/tcsh-6.17/BUGS
+-rw-r--r-- 1 root root 12773 May 19 2004 /usr/share/doc/tcsh-6.17/FAQ
+-rw-r--r-- 1 root root 85246 Jul 10 2009 /usr/share/doc/tcsh-6.17/Fixes
+-rw-r--r-- 1 root root 6518 Oct 2 1998 /usr/share/doc/tcsh-6.17/NewThings
+-rw-r--r-- 1 root root 11809 May 19 2004 /usr/share/doc/tcsh-6.17/WishList
+-rw-r--r-- 1 root root 56615 Oct 1 2007 /usr/share/doc/tcsh-6.17/complete.tcsh
+-rw-r--r-- 1 root root 46682 Dec 15 2009 /usr/share/locale/de/LC_MESSAGES/tcsh
+-rw-r--r-- 1 root root 48387 Dec 15 2009 /usr/share/locale/el/LC_MESSAGES/tcsh
+-rw-r--r-- 1 root root 45670 Dec 15 2009 /usr/share/locale/en/LC_MESSAGES/tcsh
+-rw-r--r-- 1 root root 48234 Dec 15 2009 /usr/share/locale/es/LC_MESSAGES/tcsh
+-rw-r--r-- 1 root root 45130 Dec 15 2009 /usr/share/locale/et/LC_MESSAGES/tcsh
+-rw-r--r-- 1 root root 47757 Dec 15 2009 /usr/share/locale/fi/LC_MESSAGES/tcsh
+-rw-r--r-- 1 root root 47978 Dec 15 2009 /usr/share/locale/fr/LC_MESSAGES/tcsh
+-rw-r--r-- 1 root root 49085 Dec 15 2009 /usr/share/locale/it/LC_MESSAGES/tcsh
+-rw-r--r-- 1 root root 33848 Dec 15 2009 /usr/share/locale/ja/LC_MESSAGES/tcsh
+-rw-r--r-- 1 root root 45160 Dec 15 2009 /usr/share/locale/pl/LC_MESSAGES/tcsh
+-rw-r--r-- 1 root root 46148 Dec 15 2009 /usr/share/locale/ru/LC_MESSAGES/tcsh
+-rw-r--r-- 1 root root 45492 Dec 15 2009 /usr/share/locale/uk/LC_MESSAGES/tcsh
+lrwxrwxrwx 1 root root 9 Dec 15 2009 /usr/share/man/man1/csh.1.gz -> tcsh.1.gz
+-rw-r--r-- 1 root root 63984 Dec 15 2009 /usr/share/man/man1/tcsh.1.gz
+</pre><div class="para">
+ This information is the same as a long listing on the files.
+ </div><div class="para">
+ As you can see, the <code class="option">–l</code> option results in quite a lot of output. In some cases, though, you aren’t interested in documentation and other miscellaneous files in the package. It’s the commands and libraries that cause the most package-related problems. To help with this, you can use a series of rpm options to list only certain types of files.
+ </div></div><div class="section" id="RPM_Guide-Using_RPM_DB-listing_conf_files"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="RPM_Guide-Using_RPM_DB-listing_conf_files">4.2.4. Listing the configuration files for a package</h3></div></div></div><div class="para">
+ The <code class="option">–c</code> option tells <code class="command">rpm –q</code> to list the configuration files for a package. You can also use the longer option, <code class="option">--configfiles</code>, in place of <code class="option">–c</code>. The basic syntax is:
+ </div><div class="para">
+ <code class="command">rpm –qc <em class="replaceable"><code>package_name</code></em></code>
+ </div><div class="para">
+ For example:
+ </div><div class="para">
+ <code class="command">rpm -qc bash</code>
+ </div><pre class="screen">
+ /etc/skel/.bash_logout
+ /etc/skel/.bash_profile
+ /etc/skel/.bashrc
+</pre><div class="para">
+ This command lists the configuration files for the bash package.
+ </div><div class="para">
+ Some packages don’t have configuration files, as shown following:
+ </div><div class="para">
+ <code class="command">rpm -qc python</code>
+ </div><pre class="screen">
+
+</pre><div class="para">
+ In this case, the rpm command provides no output. Other packages have a lot of configuration files, such as the sendmail mail transfer agent, as shown following:
+ </div><div class="para">
+ <code class="command">rpm -qc sendmail</code>
+ </div><pre class="screen">
+ /etc/aliases
+ /etc/mail/Makefile
+ /etc/mail/access
+ /etc/mail/domaintable
+ /etc/mail/helpfile
+ /etc/mail/local-host-names
+ /etc/mail/mailertable
+ /etc/mail/sendmail.mc
+ /etc/mail/statistics
+ /etc/mail/trusted-users
+ /etc/mail/virtusertable
+ /etc/rc.d/init.d/sendmail
+ /etc/sendmail.cf
+ /etc/sysconfig/sendmail
+ /usr/lib/sasl/Sendmail.conf
+</pre><div class="para">
+ As with the <code class="option">–l</code> option, the <code class="option">–v</code> option provides more information on each file, as shown following:
+ </div><div class="para">
+ <code class="command">rpm -qcv bash</code>
+ </div><pre class="screen">
+-rw-r--r-- 1 root root 18 May 21 13:32 /etc/skel/.bash_logout
+-rw-r--r-- 1 root root 176 May 21 13:32 /etc/skel/.bash_profile
+-rw-r--r-- 1 root root 124 May 21 13:32 /etc/skel/.bashrc
+</pre></div><div class="section"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id1301235">4.2.5. Listing the documentation files for a package</h3></div></div></div><div class="para">
+ Similarly to the <code class="option">–c</code> option, the <code class="option">–d</code> option tells the <code class="command">rpm –q</code> command to list just the documentation files for a package. The basic syntax is:
+ </div><div class="para">
+ <code class="command">rpm –qd <em class="replaceable"><code>package_name</code></em></code>
+ </div><div class="para">
+ For example:
+ </div><div class="para">
+ <code class="command">rpm -qd tcsh</code>
+ </div><pre class="screen">
+ /usr/share/doc/tcsh-6.10/FAQ
+ /usr/share/doc/tcsh-6.10/Fixes
+ /usr/share/doc/tcsh-6.10/NewThings
+ /usr/share/doc/tcsh-6.10/complete.tcsh
+ /usr/share/doc/tcsh-6.10/eight-bit.txt
+ /usr/share/doc/tcsh-6.10/tcsh.html/header.html
+ /usr/share/doc/tcsh-6.10/tcsh.html/index.html
+ /usr/share/doc/tcsh-6.10/tcsh.html/lists.html
+ /usr/share/doc/tcsh-6.10/tcsh.html/tcsh.man
+ /usr/share/doc/tcsh-6.10/tcsh.html/tcsh.man2html
+ /usr/share/doc/tcsh-6.10/tcsh.html/top.html
+ /usr/share/man/man1/tcsh.1.gz
+</pre><div class="note"><div class="admonition_header"><h2>Getting more information</h2></div><div class="admonition"><div class="para">
+ You can add the –v option to all of the file-listing options to get more information.
+ </div></div></div><div class="para">
+ You can also use the longer option, <code class="option">--docfiles</code>, in place of <code class="option">–d</code>.
+ </div></div><div class="section" id="RPM_Guide-Using_RPM_DB-file_state"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="RPM_Guide-Using_RPM_DB-file_state">4.2.6. Listing the state of the files in a package</h3></div></div></div><div class="para">
+ The <code class="option">–s</code> option to the <code class="command">rpm –q</code> command lists the state of each file in a package. The basic syntax is:
+ </div><div class="para">
+ <code class="command">rpm –qs <em class="replaceable"><code>package_name</code></em></code>
+ </div><div class="para">
+ For example:
+ </div><div class="para">
+ <code class="command">rpm -qs tcsh</code>
+ </div><pre class="screen">
+ normal /bin/csh
+ normal /bin/tcsh
+ normal /usr/share/doc/tcsh-6.10
+ normal /usr/share/doc/tcsh-6.10/FAQ
+ normal /usr/share/doc/tcsh-6.10/Fixes
+ normal /usr/share/doc/tcsh-6.10/NewThings
+ normal /usr/share/doc/tcsh-6.10/complete.tcsh
+ normal /usr/share/doc/tcsh-6.10/eight-bit.txt
+ normal /usr/share/doc/tcsh-6.10/tcsh.html
+ normal /usr/share/doc/tcsh-6.10/tcsh.html/header.html
+ normal /usr/share/doc/tcsh-6.10/tcsh.html/index.html
+ normal /usr/share/doc/tcsh-6.10/tcsh.html/lists.html
+ normal /usr/share/doc/tcsh-6.10/tcsh.html/tcsh.man
+ normal /usr/share/doc/tcsh-6.10/tcsh.html/tcsh.man2html
+ normal /usr/share/doc/tcsh-6.10/tcsh.html/top.html
+ not installed /usr/share/locale/de/LC_MESSAGES/tcsh
+ not installed /usr/share/locale/el/LC_MESSAGES/tcsh
+ not installed /usr/share/locale/es/LC_MESSAGES/tcsh
+ not installed /usr/share/locale/fr/LC_MESSAGES/tcsh
+ not installed /usr/share/locale/it/LC_MESSAGES/tcsh
+ not installed /usr/share/locale/ja/LC_MESSAGES/tcsh
+ normal /usr/share/man/man1/tcsh.1.gz
+</pre><div class="para">
+ You can also use the long option, <code class="option">--state</code>, in place of <code class="option">–s</code>.
+ </div><div class="para">
+ You can combine the <code class="option">–s</code> option with other file filters, such as <code class="option">–d</code>, for listing only the documentation files for a package.
+ </div><div class="para">
+ Table 5-2 lists the states that RPM supports.
+ </div><div class="para">
+ Table 5-2 RPM File States
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ State
+ </div>
+
+ </td><td>
+ <div class="para">
+ Usage
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ normal
+ </div>
+
+ </td><td>
+ <div class="para">
+ The file has been installed.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ not installed
+ </div>
+
+ </td><td>
+ <div class="para">
+ The file from the package is not installed.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ replaced
+ </div>
+
+ </td><td>
+ <div class="para">
+ The file has been replaced.
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ Sometimes files in a package may have been skipped during installation with options such as <code class="option">--excludedocs</code>. This can lead to non-normal states. You may have also modified files installed from a given package.
+ </div></div><div class="section" id="RPM_Guide-Using_RPM_DB-listing_scripts"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="RPM_Guide-Using_RPM_DB-listing_scripts">4.2.7. Listing the scripts in a package</h3></div></div></div><div class="para">
+ RPM packages can have preinstallation, postinstallation, preuninstallation, and postuninstallation scripts. These are scripts that the rpm command will execute before and after installing a package, as well as before and after removing the package. The <code class="option">--scripts</code> option to the <code class="command">rpm –q</code> command lists the scripts associated with a package. The basic syntax follows:
+ </div><div class="para">
+ <code class="command">rpm -q --scripts <em class="replaceable"><code>package_name</code></em></code>
+ </div><div class="para">
+ For example:
+ </div><div class="para">
+ <code class="command">rpm -q --scripts tcsh</code>
+ </div><pre class="screen">
+if [ ! -f /etc/shells ]; then
+ echo "/bin/tcsh" >> /etc/shells
+ echo "/bin/csh" >> /etc/shells
+else
+ grep -q '^/bin/tcsh$' /etc/shells || \
+ echo "/bin/tcsh" >> /etc/shells
+ grep -q '^/bin/csh$' /etc/shells || \
+ echo "/bin/csh" >> /etc/shells
+fi
+postuninstall scriptlet (using /bin/sh):
+if [ ! -x /bin/tcsh ]; then
+ grep -v '^/bin/tcsh$' /etc/shells | \
+ grep -v '^/bin/csh$' > /etc/shells.rpm && \
+ mv /etc/shells.rpm /etc/shells
+fi
+</pre><div class="para">
+ The simple scripts shown here add an entry to the /etc/shells file and clean up the entry when uninstalled.
+ </div><div class="important"><div class="admonition_header"><h2>Cleaning up</h2></div><div class="admonition"><div class="para">
+ Cleaning up any changes your package makes on uninstallation is a very good idea. See the chapters in Part II, Creating RPMs, for details on making your own well-behaved packages.
+ </div></div></div><div class="para">
+ Other packages have more complex scripts, as shown following:
+ </div><div class="para">
+ <code class="command">rpm -q --scripts sendmail</code>
+ </div><pre class="screen">
+preinstall scriptlet (using /bin/sh):
+/usr/sbin/useradd -u 47 -d /var/spool/mqueue -r -s /sbin/nologin mailnull >/dev/null 2>&1
+/usr/sbin/useradd -u 51 -d /var/spool/mqueue -r -s /sbin/nologin smmsp >/dev/null 2>&1
+exit 0
+postinstall scriptlet (using /bin/sh):
+/sbin/chkconfig --add sendmail
+# Set up the alternatives files for MTAs.
+/usr/sbin/alternatives --install /usr/sbin/sendmail mta /usr/sbin/sendmail.sendmail 90 \
+ --slave /usr/bin/mailq mta-mailq /usr/bin/mailq.sendmail \
+ --slave /usr/bin/newaliases mta-newaliases /usr/bin/newaliases.sendmail \
+ --slave /usr/bin/rmail mta-rmail /usr/bin/rmail.sendmail \
+ --slave /usr/lib/sendmail mta-sendmail /usr/lib/sendmail.sendmail \
+ --slave /etc/pam.d/smtp mta-pam /etc/pam.d/smtp.sendmail \
+ --slave /usr/share/man/man8/sendmail.8.gz mta-sendmailman /usr/share/man/man8/sendmail.sendmail.8.gz \
+ --slave /usr/share/man/man1/mailq.1.gz mta-mailqman /usr/share/man/man1/mailq.sendmail.1.gz \
+ --slave /usr/share/man/man1/newaliases.1.gz mta-newaliasesman /usr/share/man/man1/newaliases.sendmail.1.gz \
+ --slave /usr/share/man/man5/aliases.5.gz mta-aliasesman /usr/share/man/man5/aliases.sendmail.5.gz \
+ --initscript sendmail
+
+# Rebuild maps
+{
+ chown root /etc/aliases.db /etc/mail/access.db \
+ /etc/mail/mailertable.db /etc/mail/domaintable.db \
+ /etc/mail/virtusertable.db
+ SM_FORCE_DBREBUILD=1 /etc/mail/make
+ SM_FORCE_DBREBUILD=1 /etc/mail/make aliases
+} > /dev/null 2>&1
+exit 0
+preuninstall scriptlet (using /bin/sh):
+if [ $1 = 0 ]; then
+ /etc/rc.d/init.d/sendmail stop >/dev/null 2>&1
+ /sbin/chkconfig --del sendmail
+ /usr/sbin/alternatives --remove mta /usr/sbin/sendmail.sendmail
+fi
+exit 0
+postuninstall scriptlet (using /bin/sh):
+if [ "$1" -ge "1" ]; then
+ /etc/rc.d/init.d/sendmail condrestart >/dev/null 2>&1
+ mta=`readlink /etc/alternatives/mta`
+ if [ "$mta" == "/usr/sbin/sendmail.sendmail" ]; then
+ /usr/sbin/alternatives --set mta /usr/sbin/sendmail.sendmail
+ fi
+fi
+exit 0
+</pre><div class="para">
+ In this case, the main script is the post-install script, which tries to convert old-format data into the new format, thereby helping users upgrade to the newer release.
+ </div></div><div class="section" id="RPM_Guide-Using_RPM_DB-Listing_changed"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="RPM_Guide-Using_RPM_DB-Listing_changed">4.2.8. Listing what has changed</h3></div></div></div><div class="para">
+ The <code class="option">--changelog</code> option lists what has changed, as described in a file that logs changes, from previous versions of a given package. The change log is just a convention, so not all packages will sport this nifty feature. In addition, the change log for many packages documents the changes in the RPM packaging, not the changes in the underlying application. If a change log is available, however, this can prove a very good way to help determine whether you want to upgrade to a new version of a package.
+ </div><div class="para">
+ For example, a network server application may have been updated to fix some security problems. In that case, you likely want to upgrade. Other changes may not affect your site, leading you to decide not to upgrade.
+ </div><div class="para">
+ The basic format of the command is:
+ </div><div class="para">
+ <code class="command">rpm –q --changelog <em class="replaceable"><code>package_name</code></em></code>
+ </div><div class="para">
+ For example, the following shows the beginning of the changelog for the bash package:
+ </div><div class="para">
+ <code class="command">rpm -q --changelog bash</code>
+ </div><pre class="screen">
+* Fri May 21 2010 Roman Rakus rrakus at redhat.com - 4.1.7-1
+- Patch level 7
+
+* Wed Mar 31 2010 Roman Rakus rrakus at redhat.com - 4.1.2-4
+- Corrected requires patch (#563301)
+
+* Fri Jan 22 2010 rrakus at redhat.com 4.1.2-3
+- Don't use cond-rmatch patch
+- Use manso patch
+- Include COPYING in base bash rpm
+
+* Fri Jan 22 2010 rrakus at redhat.com 4.1.2-2
+- Correct patchlevel 2
+
+* Fri Jan 22 2010 Roman Rakus rrakus at redhat.com 4.1.2-1
+- Patchlevel 4.2
+- Removed old patch
+- Returned back manso patch
+
+* Fri Jan 08 2010 Roman Rakus rrakus at redhat.com 4.1.0-2
+- Include COPYING in doc dir
+
+* Mon Jan 04 2010 Roman Rakus rrakus at redhat.com - 4.1.0-1
+- Upstream 4.1
+
+* Sun Dec 27 2009 Roman Rakus rrakus at redhat.com - 4.1-0.2.rc1
+- Fixed patch for fuzz=0
+
+* Sun Dec 27 2009 Roman Rakus rrakus at redhat.com - 4.1-0.1.rc1
+- Upstream 4.1.rc1
+
+* Fri Dec 11 2009 Roman Rakus rrakus at redhat.com - 4.0.35-2
+- Don't segfault when TERM=eterm* and EMACS is unset (#530911)
+
+* Thu Oct 29 2009 Roman Rakus rrakus at redhat.com - 4.0.35-1
+- Patch level 35
+</pre></div><div class="section" id="RPM_Guide-Using_RPM_DB-Combining_queries"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="RPM_Guide-Using_RPM_DB-Combining_queries">4.2.9. Combining queries</h3></div></div></div><div class="para">
+ The rpm command is very flexible in allowing you to combine queries. Just start the command with <code class="command">rpm –q</code> and add the various options either on their own, such as <code class="option">–q</code> with <code class="option">–s</code> and <code class="option">–f</code>, or together, such as <code class="option">–qsf</code>.
+ </div><div class="para">
+ The following sections show a few handy combinations of the options you can use for real-world package-management tasks.
+ </div><div class="section" id="RPM_Guide-Using_RPM_DB-Combining_queries-Decription_documentation"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="RPM_Guide-Using_RPM_DB-Combining_queries-Decription_documentation">4.2.9.1. Listing Package Description and Documentation Files</h4></div></div></div><div class="para">
+ To find information on a package and where it is documented, use the <code class="option">–qdi</code> option to rpm (a combination of the <code class="option">–q</code>, <code class="option">–d</code>, and <code class="option">–i</code> options):
+ </div><div class="para">
+ <code class="command">rpm -qdi grep</code>
+ </div><pre class="screen">
+Name : grep Relocations: (not relocatable)
+Version : 2.6.3 Vendor: Fedora Project
+Release : 1.fc13 Build Date: Wed 07 Apr 2010 05:58:58 PM EDT
+Install Date: Fri 27 Aug 2010 07:03:07 PM EDT Build Host: x86-06.phx2.fedoraproject.org
+Group : Applications/Text Source RPM: grep-2.6.3-1.fc13.src.rpm
+Size : 800493 License: GPLv3+
+Signature : RSA/SHA256, Wed 07 Apr 2010 06:48:20 PM EDT, Key ID 7edc6ad6e8e40fde
+Packager : Fedora Project
+URL : http://www.gnu.org/software/grep/
+Summary : Pattern matching utilities
+Description :
+The GNU versions of commonly used grep utilities. Grep searches through
+textual input for lines which contain a match to a specified pattern and then
+prints the matching lines. GNU's grep utilities include grep, egrep and fgrep.
+
+GNU grep is needed by many scripts, so it shall be installed on every system.
+/usr/share/doc/grep-2.6.3/ABOUT-NLS
+/usr/share/doc/grep-2.6.3/AUTHORS
+/usr/share/doc/grep-2.6.3/COPYING
+/usr/share/doc/grep-2.6.3/ChangeLog
+/usr/share/doc/grep-2.6.3/NEWS
+/usr/share/doc/grep-2.6.3/README
+/usr/share/doc/grep-2.6.3/THANKS
+/usr/share/doc/grep-2.6.3/TODO
+/usr/share/info/grep.info.gz
+/usr/share/man/man1/egrep.1.gz
+/usr/share/man/man1/fgrep.1.gz
+/usr/share/man/man1/grep.1.gz
+</pre><div class="para">
+ It can sometimes be difficult to track down the documentation for a given package. Some packages use Unix manual pages; others use info files, and still others provide HTML for other formatted manuals. Some have no real documentation at all.
+ </div></div><div class="section" id="RPM_Guide-Using_RPM_DB-Combining_queries-State_of_config_files"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="RPM_Guide-Using_RPM_DB-Combining_queries-State_of_config_files">4.2.9.2. Listing the State of Configuration Files</h4></div></div></div><div class="para">
+ To find the state of all the configuration files for a given Linux command, use a command with the <code class="option">–qcsf</code> option with the name of the file, as shown here, or the <code class="option">-qcs</code> option with the name of a package.
+ </div><div class="para">
+ For example:
+ </div><div class="para">
+ <code class="command">rpm -qcsf /bin/bash</code>
+ </div><pre class="screen">
+normal /etc/skel/.bash_logout
+normal /etc/skel/.bash_profile
+normal /etc/skel/.bashrc
+</pre></div><div class="section" id="RPM_Guide-Using_RPM_DB-Combining_queries-Recently_installed"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="RPM_Guide-Using_RPM_DB-Combining_queries-Recently_installed">4.2.9.3. Listing the Most Recently Installed Packages</h4></div></div></div><div class="para">
+ To list the most recently installed packages, use the following command with the <code class="option">--last</code> option. This is very useful if you recently installed or upgraded a number of packages and something unexpected happens. If you cannot remember the package names, you can use the <code class="option">--last</code> option to list out packages in reverse order of installation.
+ </div><div class="para">
+ You can pipe the output of a query to the head command to show only the last ten packages that were installed or upgraded, as shown following:
+ </div><div class="para">
+ <code class="command">rpm -qa --last | head</code>
+ </div><pre class="screen">
+kmod-nvidia-2.6.34.6-47.fc13.x86_64-256.53-1.fc13 Sat 18 Sep 2010 09:54:48 AM EDT
+xorg-x11-drv-nvidia-256.53-1.fc13 Sat 18 Sep 2010 09:51:00 AM EDT
+kmod-nvidia-2.6.34.6-54.fc13.x86_64-256.53-1.fc13.3 Sat 18 Sep 2010 09:50:59 AM EDT
+xorg-x11-drv-nvidia-libs-256.53-1.fc13 Sat 18 Sep 2010 09:50:57 AM EDT
+google-talkplugin-1.5.1.0-1 Wed 15 Sep 2010 07:38:46 PM EDT
+mythplugins-0.23.1-2.fc13 Sun 12 Sep 2010 09:35:42 PM EDT
+mythweather-0.23.1-2.fc13 Sun 12 Sep 2010 09:35:40 PM EDT
+perl-DateTime-Format-ISO8601-0.07-1.fc13 Sun 12 Sep 2010 09:35:39 PM EDT
+perl-DateTime-Format-Builder-0.7901-5.fc13 Sun 12 Sep 2010 09:35:38 PM EDT
+perl-Class-Factory-Util-1.7-6.fc13 Sun 12 Sep 2010 09:35:37 PM EDT
+</pre><div class="para">
+ You can pass options to the head command to show more or fewer than ten lines. In general, starting with the last ten packages can help you track down something you installed the day before.
+ </div></div></div><div class="section" id="RPM_Guide-Using_RPM_DB-Cusomt_queries"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="RPM_Guide-Using_RPM_DB-Cusomt_queries">4.2.10. Creating custom queries</h3></div></div></div><div class="para">
+ The <code class="option">--qf</code> or <code class="option">--queryformat</code> option allows you to create custom queries with the rpm command, although in a rather difficult manner. You need to pass a query format string, the syntax of which originates with the C printf function and requires precision.
+ </div><div class="para">
+ The basic syntax of the query format is <code class="option">%{tag_name}</code>. (The percent sign is about the only part that comes from the C printf function.) You can combine tag names to display more than one item per package. You can also add formatting options following C language conventions.
+ </div><div class="para">
+ For example, to list all package names, use a command like the following (the output is abbreviated):
+ </div><div class="para">
+ <code class="command">rpm -qa --qf "%{NAME}"</code>
+ </div><pre class="screen">
+libxml2tcp_wrappers-libstracerouteperl-Config-Tinylibsampleratefedora-icon-themefftw2dvb-appsreport-plugin-localsaveglib2-develqwtintltoolperl-Locale-Maketext-Gettextliblastfmxorg-x11-fonts-ISO8859-1-100dpilibpng-devellibgeotifffontconfigPackageKit-glibshared-mime-infoxorg-x11-drv-sisusbxmlgraphics-commonsopenoffice.org-graphicfilterm17n-db-oriyadejavu-sans-fontslibselinux-pythonapr-utilxorg-x11-drv-cirruslibsilcmysql-serverpnm2ppanssmythmusicdbus-glibcyrus-sasl-libfedora-release-notesekigaperl-Net-SSLeayperl-HTML-Parsermingettyphp-clixorg-x11-drv-nvidia-libspatchgnome-games-extra
+</pre><div class="para">
+ This command used the simplest format, which is just the value of the tag in the package headers, in this case the package names. Because we used no other formatting, this command outputs all the package names smashed together. To deal with this problem in the output, you can place a \n, the C language convention for a newline character, at the end of the format string. This fixes the output considerably.
+ </div><div class="para">
+ For example (showing just the first few entries):
+ </div><div class="para">
+ <code class="command">rpm -qa --qf "%{NAME}\n"</code>
+ </div><pre class="screen">
+libxml2
+tcp_wrappers-libs
+traceroute
+perl-Config-Tiny
+libsamplerate
+fedora-icon-theme
+fftw2
+dvb-apps
+report-plugin-localsave
+glib2-devel
+</pre><div class="para">
+ This command provides a custom query that is essentially the same as <code class="command">rpm -qa</code>. You’ll likely not use this command in favor of the simpler rpm option, but you can use this example as a guide for creating your own custom queries.
+ </div><div class="note"><div class="admonition_header"><h2>popt aliases</h2></div><div class="admonition"><div class="para">
+ A great many of the command-line options to the rpm command are defined as popt aliases. These popt aliases define the rpm command-line options in terms of longer query format strings. See <a class="xref" href="#ch-customizing-rpm">Cap. 20, <em>Customizing RPM Behavior</em></a> for more information on popt.
+ </div></div></div><div class="para">
+ You can add items to the query string and use C language conventions for formatting and controlling the amount of space provided for each item output. For example, the following command prints the name and platform for all packages, showing the first few entries, formatted with 20 characters for each item:
+ </div><div class="para">
+ <code class="command">rpm -qa --qf "%-20{NAME} %-20{PLATFORM}\n"</code>
+ </div><pre class="screen">
+libxml2 x86_64-redhat-linux-gnu
+tcp_wrappers-libs i686-redhat-linux-gnu
+traceroute x86_64-redhat-linux-gnu
+perl-Config-Tiny noarch-redhat-linux-gnu
+libsamplerate x86_64-redhat-linux-gnu
+fedora-icon-theme noarch-redhat-linux-gnu
+fftw2 x86_64-redhat-linux-gnu
+dvb-apps x86_64-redhat-linux-gnu
+report-plugin-localsave x86_64-redhat-linux-gnu
+glib2-devel x86_64-redhat-linux-gnu
+</pre></div><div class="section" id="RPM_Guide-Using_RPM_DB-Query_format_tags"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="RPM_Guide-Using_RPM_DB-Query_format_tags">4.2.11. Working With Query Format Tags</h3></div></div></div><div class="para">
+ To build queries with the <code class="option">--queryformat</code> option, you need to know what tags you can use. To list the names of the available query format tags, use the <code class="option">--querytags</code> option, which returns a large set of tags, truncated here for space:
+ </div><div class="para">
+ <code class="command">rpm --querytags</code>
+ </div><pre class="screen">
+ NAME
+ VERSION
+ RELEASE
+ SUMMARY
+ DESCRIPTION
+ BUILDTIME
+</pre><div class="para">
+ Each of these tags also has a version with a <code class="literal">RPMTAG_</code> prefix, such as <code class="literal">RPMTAG_NAME</code>. You can use this tags with or without the <code class="literal">RPMTAG_</code> prefix. For example:
+ </div><div class="para">
+ <code class="command">rpm -q --qf "%{RPMTAG_NAME}\n" sendmail</code>
+ </div><pre class="screen">
+ sendmail
+</pre><div class="para">
+ Note how this command uses the <code class="option">–q</code> option to query for one package, instead of <code class="option">–qa</code> to query for all packages. You can use query formats with any of the rpm queries.
+ </div><div class="para">
+ The next sections cover the available tags based on the type of the information stored in the tag.
+ </div></div><div class="section" id="RPM_Guide-Using_RPM_DB-Querying_for_package_information"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="RPM_Guide-Using_RPM_DB-Querying_for_package_information">4.2.12. Querying for Package Information</h3></div></div></div><div class="para">
+ Many of the query format tags refer to package-information data stored in the RPM header, introduced in <a class="xref" href="#ch-rpm-overview">Cap. 2, <em>RPM Overview</em></a> . Table 5-3 lists the package-information tags.
+ </div><div class="para">
+ Table 5-3 Package-information query tags
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Tag
+ </div>
+
+ </td><td>
+ <div class="para">
+ Holds
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ NAME
+ </div>
+
+ </td><td>
+ <div class="para">
+ Package name
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ VERSION
+ </div>
+
+ </td><td>
+ <div class="para">
+ Version number
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RELEASE
+ </div>
+
+ </td><td>
+ <div class="para">
+ Release number
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ SUMMARY
+ </div>
+
+ </td><td>
+ <div class="para">
+ One-line summary of the package contents
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ DESCRIPTION
+ </div>
+
+ </td><td>
+ <div class="para">
+ Descriptive text about the package
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ BUILDTIME
+ </div>
+
+ </td><td>
+ <div class="para">
+ Time package was built
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ BUILDHOST
+ </div>
+
+ </td><td>
+ <div class="para">
+ Host package was built on
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ SIZE
+ </div>
+
+ </td><td>
+ <div class="para">
+ Size of all the regular files in the payload
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ LICENSE
+ </div>
+
+ </td><td>
+ <div class="para">
+ License package was released under
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ GROUP
+ </div>
+
+ </td><td>
+ <div class="para">
+ Descriptive group or category name for the package
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ OS
+ </div>
+
+ </td><td>
+ <div class="para">
+ Operating system package was built for
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ ARCH
+ </div>
+
+ </td><td>
+ <div class="para">
+ Architecture, such as i386
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ SOURCERPM
+ </div>
+
+ </td><td>
+ <div class="para">
+ The associated source RPM
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ CHANGELOGTIME
+ </div>
+
+ </td><td>
+ <div class="para">
+ Array of changelog times
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ CHANGELOGNAME
+ </div>
+
+ </td><td>
+ <div class="para">
+ Array of changelog names
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ CHANGELOGTEXT
+ </div>
+
+ </td><td>
+ <div class="para">
+ Array of changelog text entries
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ PREIN
+ </div>
+
+ </td><td>
+ <div class="para">
+ Pre-install script
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ POSTIN
+ </div>
+
+ </td><td>
+ <div class="para">
+ Post-install script
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ PREUN
+ </div>
+
+ </td><td>
+ <div class="para">
+ Pre-uninstall script
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ POSTUN
+ </div>
+
+ </td><td>
+ <div class="para">
+ Post uninstall script
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ PLATFORM
+ </div>
+
+ </td><td>
+ <div class="para">
+ Platform
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ All of these tags, except for the <code class="literal">CHANGELOGTIME</code>, <code class="literal">CHANGELOGTEXT</code> and <code class="literal">CHANGELOGNAME</code> tags, are single-value tags.
+ </div></div><div class="section" id="RPM_Guide-Using_RPM_DB-Formatting_arrays"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="RPM_Guide-Using_RPM_DB-Formatting_arrays">4.2.13. Formatting Arrays</h3></div></div></div><div class="para">
+ Many of the header entries are arrays, so the header tags can hold more than one item. For example, RPM packages can have more than one file in the payload.
+ </div><div class="para">
+ To specify a format for each item in an array, use square brackets. For example:
+ </div><div class="para">
+ <code class="command">rpm -q --queryformat "[%-50{FILENAMES} %{FILESIZES}\n]" sendmail</code>
+ </div><pre class="screen">
+/etc/NetworkManager/dispatcher.d/10-sendmail 96
+/etc/mail 4096
+/etc/mail/Makefile 92
+/etc/mail/access 469
+/etc/mail/access.db 0
+/etc/mail/aliasesdb-stamp 0
+/etc/mail/domaintable 233
+/etc/mail/domaintable.db 0
+/etc/mail/helpfile 5584
+/etc/mail/local-host-names 64
+</pre><div class="para">
+ This example lists the files and file sizes within a package, with the listing of files truncated for size.
+ </div><div class="para">
+ If you want to mix array tags with non-array tags, you can use an equals sign, <code class="literal">=</code>, in front of the tag name to specify that the given tag should be repeated for each item in the array. For example:
+ </div><div class="para">
+ <code class="command">rpm -q --queryformat "[%-15{=NAME} %-50{FILENAMES}\n]" sendmail bash</code>
+ </div><pre class="screen">
+sendmail /etc/NetworkManager/dispatcher.d/10-sendmail
+sendmail /etc/mail
+sendmail /etc/mail/Makefile
+sendmail /etc/mail/access
+sendmail /etc/mail/access.db
+bash /bin/bash
+bash /bin/sh
+bash /etc/skel/.bash_logout
+bash /etc/skel/.bash_profile
+bash /etc/skel/.bashrc
+</pre><div class="para">
+ This example, also truncated for size, lists the package name along with the file name for the files contained in these two packages.
+ </div></div><div class="section" id="RPM_Guide-Using_RPM_DB-Special_formatting"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="RPM_Guide-Using_RPM_DB-Special_formatting">4.2.14. Special Formatting</h3></div></div></div><div class="para">
+ Some of the tags within an RPM package header contain special binary information that usually makes no sense when printed out. To help with these header tags, you can use special RPM formatting options, using a syntax like the following:
+ </div><div class="para">
+ <code class="literal">%{tag:special_format}</code>
+ </div><div class="para">
+ For example, to print the <code class="literal">INSTALLTIME</code> tag, use <code class="literal">%{INSTALLTIME:date}</code>, which specifies to print the <code class="literal">INSTALLTIME</code> tag in date format. For example:
+ </div><div class="para">
+ <code class="command">rpm -q --qf "%{NAME}-%{VERSION}-%{RELEASE} %{INSTALLTIME:date}\n" bash</code>
+ </div><pre class="screen">
+bash-4.1.7-1.fc13 Fri 27 Aug 2010 07:02:33 PM EDT
+</pre><div class="para">
+ This example prints the <code class="literal">NAME-VERSION-RELEASE</code> of the package, along with the <code class="literal">INSTALLTIME</code> in date format.
+ </div><div class="para">
+ Most tags in a header are optional. You can print the value of these tags, but you may get nothing. To help deal with this, you can use a conditional operator based loosely on the C language ternary operator. The basic syntax is:
+ </div><div class="para">
+ <code class="literal">%|tag?{print_if_present}:{print_if_absent}|</code>
+ </div><div class="para">
+ With the normal %{tag} syntax, this conditional syntax gets complicated really fast. You need to break the elements down. For example:
+ </div><div class="para">
+ <code class="command">rpm -q --qf "%{NAME} %|EPOCH?{%{EPOCH}}:{(no Epoch)}|\n" perl</code>
+ </div><pre class="screen">
+ perl 4
+</pre><div class="para">
+ If the package has a value for the <code class="literal">EPOCH</code> tag, you will see output as shown in this example. Most packages do not have an <code class="literal">EPOCH</code> defined, in which case, you will \ see output like the following:
+ </div><div class="para">
+ RPM files likely hold packages that are not installed. If you query one of these packages, you will get the alternative text, as shown following:
+ </div><div class="para">
+ <code class="command">rpm -q --qf "%{NAME} %|EPOCH?{%{EPOCH}}:{(no Epoch)}|\n" sendmail</code>
+ </div><pre class="screen">
+sendmail (no Epoch)
+</pre><div class="para">
+ See the "Getting Information on Package Files" section in this chapter for more on querying RPM package files. Other special-formatting options are described in the following sections on the dependency and file information tags.
+ </div></div><div class="section" id="RPM_Guide-Using_RPM_DB-querying_pacakge_dependencies"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="RPM_Guide-Using_RPM_DB-querying_pacakge_dependencies">4.2.15. Querying for Package Dependencies</h3></div></div></div><div class="para">
+ A number of tags provide package dependency information. Each of these tags comes in triples, which are formatted similarly. For example, for the capabilities a package requires, you have the REQUIRENAME, REQUIREVERSION, and REQUIREFLAGS tags.
+ </div><div class="para">
+ The REQUIRENAME tag holds an array of required capability names. The REQUIREVERSION tag holds an array of the versions of the required capabilities. The REQUIREFLAGS tag ties the two together with a set of bit flags that specify whether the requirement is for a version less than the given number, equal to the given number, greater than or equal to the given number, and so on.
+ </div><div class="para">
+ Table 5-4 lists the dependency tags.
+ </div><div class="para">
+ Table 5-4 Dependency query tags
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Tag
+ </div>
+
+ </td><td>
+ <div class="para">
+ Holds
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ CONFLICTFLAGS
+ </div>
+
+ </td><td>
+ <div class="para">
+ Array of flags for the capabilities this package conflicts
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ CONFLICTNAME
+ </div>
+
+ </td><td>
+ <div class="para">
+ Array of capabilities that this package conflicts
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ CONFLICTVERSION
+ </div>
+
+ </td><td>
+ <div class="para">
+ Array of version numbers that this package conflicts
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ REQUIREFLAGS
+ </div>
+
+ </td><td>
+ <div class="para">
+ Array of flags for the capabilities this package requires
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ REQUIRENAME
+ </div>
+
+ </td><td>
+ <div class="para">
+ Array of capabilities that this package requires
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ REQUIREVERSION
+ </div>
+
+ </td><td>
+ <div class="para">
+ Array of version numbers that this package requires
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ OBSOLETENAME
+ </div>
+
+ </td><td>
+ <div class="para">
+ Array of capabilities that this package obsoletes
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ OBSOLETEFLAGS
+ </div>
+
+ </td><td>
+ <div class="para">
+ Array of flags for the capabilities this package obsoletes
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ OBSOLETEVERSION
+ </div>
+
+ </td><td>
+ <div class="para">
+ Array of version numbers that this package obsoletes
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ PROVIDENAME
+ </div>
+
+ </td><td>
+ <div class="para">
+ Array of capabilities that this package provides
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ PROVIDEFLAGS
+ </div>
+
+ </td><td>
+ <div class="para">
+ Array of flags for the capabilities this package provides
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ PROVIDEVERSION
+ </div>
+
+ </td><td>
+ <div class="para">
+ Array of version numbers that this package provides
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ Each of these tags is an array. The PROVIDENAME, PROVIDEVERSION, and PROVIDEFLAGS tags work similarly for the capabilities this package provides. The CONFLICTNAME, CONFLICTVERSION, and CONFLICTFLAGS tags specify the conflicts, and, the OBSOLETENAME, OBSOLETEVERSION, and OBSOLETEFLAGS tags specify the obsolete dependencies.
+ </div><div class="para">
+ The depflags special-formatting option prints out the flag tags, such as REQUIREFLAGS, in human-readable format. For example, the following command lists the requirements for a package:
+ </div><div class="para">
+ $ rpm -q --qf \
+ </div><div class="para">
+ "[%{REQUIRENAME} %{REQUIREFLAGS:depflags} %{REQUIREVERSION}\n]" sendmail
+ </div><div class="para">
+ rpmlib(VersionedDependencies) <= 3.0.3-1
+ </div><div class="para">
+ chkconfig >= 1.3
+ </div><div class="para">
+ /usr/sbin/useradd
+ </div><div class="para">
+ /bin/mktemp
+ </div><div class="para">
+ fileutils
+ </div><div class="para">
+ gawk
+ </div><div class="para">
+ sed
+ </div><div class="para">
+ sh-utils
+ </div><div class="para">
+ procmail
+ </div><div class="para">
+ bash >= 2.0
+ </div><div class="para">
+ /bin/sh
+ </div><div class="para">
+ rpmlib(PayloadFilesHavePrefix) <= 4.0-1
+ </div><div class="para">
+ rpmlib(CompressedFileNames) <= 3.0.4-1
+ </div><div class="para">
+ For those requirements that have specific version numbers, this command prints out the version number along with the operator, such as >= for a version greater than or equal to the given number.
+ </div><div class="para">
+ Note that for many of the requirements, there is no specific version information.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ In addition to normal capabilities, most packages will have some RPM-related requirements as well, which specify any required RPM versions, for example, rpmlib(CompressedFileNames).
+ </div></div><div class="section" id="RPM-Guide-Using_RPM_DB-Querying_file_information"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="RPM-Guide-Using_RPM_DB-Querying_file_information">4.2.16. Querying for File Information</h3></div></div></div><div class="para">
+ The file-information tags hold data on the files within the package payload, that is, the files the rpm command installs when you install the package. These tags are arrays, with one value per file.
+ </div><div class="para">
+ Table 5-5 lists the file-information tags.
+ </div><div class="para">
+ Table 5-5 File-information query tags
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Tag
+ </div>
+
+ </td><td>
+ <div class="para">
+ Holds
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ OLDFILENAMES
+ </div>
+
+ </td><td>
+ <div class="para">
+ Array of full file names, used in older packages
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ FILESIZES
+ </div>
+
+ </td><td>
+ <div class="para">
+ Array of sizes for each file
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ FILEMODES
+ </div>
+
+ </td><td>
+ <div class="para">
+ Array of permissions for each file
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ FILERDEVS
+ </div>
+
+ </td><td>
+ <div class="para">
+ Array of rdev values for each file
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ FILEMTIMES
+ </div>
+
+ </td><td>
+ <div class="para">
+ Array of modified times for each file
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ FILEMD5S
+ </div>
+
+ </td><td>
+ <div class="para">
+ MD5 checksum for each file
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ FILELINKTOS
+ </div>
+
+ </td><td>
+ <div class="para">
+ Array of link information for each file
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ FILEFLAGS
+ </div>
+
+ </td><td>
+ <div class="para">
+ Array of flags for each file
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ FILEUSERNAME
+ </div>
+
+ </td><td>
+ <div class="para">
+ Array of user names for the file owners
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ FILEGROUPNAME
+ </div>
+
+ </td><td>
+ <div class="para">
+ Array of group names for the file owners
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ FILEDEVICES
+ </div>
+
+ </td><td>
+ <div class="para">
+ Array of devices for each file
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ FILEINODES
+ </div>
+
+ </td><td>
+ <div class="para">
+ Array of inodes for each file
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ FILELANGS
+ </div>
+
+ </td><td>
+ <div class="para">
+ Array of language flags for each file
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ DIRINDEXES
+ </div>
+
+ </td><td>
+ <div class="para">
+ Array of values that matches the DIRNAMES with the BASENBAMES
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ BASENAMES
+ </div>
+
+ </td><td>
+ <div class="para">
+ Array of file base names
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ DIRNAMES
+ </div>
+
+ </td><td>
+ <div class="para">
+ Array of directories that matches up with BASENAMES
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ The <code class="literal">OLDFILENAMES</code> tag is used when the files are not compressed, when the <code class="literal">REQUIRENAME</code> tag does not indicate rpmlib(CompressedFileNames).
+ </div><div class="para">
+ The <code class="literal">FILESIZES</code> tag specifies the size of each file in the payload, while the <code class="literal">FILEMODES</code> tag specifies the file modes (permissions) and the <code class="literal">FILEMTIMES</code> tag holds the last modification time for each file.
+ </div><div class="para">
+ The <code class="literal">BASENAMES</code> tag holds an array of the base file names for the files in the payload. The <code class="literal">DIRNAMES</code> tag holds an array of the directories for the files. The <code class="literal">DIRINDEXES</code> tag contains an index into the <code class="literal">DIRNAMES</code> for the directory. Each RPM must have either <code class="literal">OLDFILENAMES</code> or the triple of <code class="literal">BASENAMES</code>, <code class="literal">DIRNAMES</code>, and <code class="literal">DIRINDEXES</code>, but not both.
+ </div><div class="para">
+ When listing file information, use the square bracket array syntax with your query formats. You can use the perms special formatting option for the file modes. For example:
+ </div><pre class="screen">
+$ rpm -q --qf "[%-15{=NAME} %-36{FILENAMES} %{FILEMODES:perms}\n]" sudo
+sudo /etc/pam.d/sudo -rw-r--r--
+sudo /etc/pam.d/sudo-i -rw-r--r--
+sudo /etc/sudoers -r--r-----
+sudo /etc/sudoers.d drwxr-x---
+sudo /usr/bin/sudo ---s--x--x
+sudo /usr/bin/sudoedit ---s--x--x
+sudo /usr/bin/sudoreplay ---x--x--x
+sudo /usr/libexec/sesh -rwxr-xr-x
+sudo /usr/libexec/sudo_noexec.so -rwxr-xr-x
+sudo /usr/sbin/visudo -rwxr-xr-x
+sudo /usr/share/doc/sudo-1.7.4p4 drwxr-xr-x
+sudo /usr/share/doc/sudo-1.7.4p4/ChangeLog -rw-r--r--
+sudo /usr/share/doc/sudo-1.7.4p4/HISTORY -rw-r--r--
+sudo /usr/share/doc/sudo-1.7.4p4/LICENSE -rw-r--r--
+sudo /usr/share/doc/sudo-1.7.4p4/NEWS -rw-r--r--
+sudo /usr/share/doc/sudo-1.7.4p4/README -rw-r--r--
+sudo /usr/share/doc/sudo-1.7.4p4/README.LDAP -rw-r--r--
+sudo /usr/share/doc/sudo-1.7.4p4/TROUBLESHOOTING -rw-r--r--
+sudo /usr/share/doc/sudo-1.7.4p4/UPGRADE -rw-r--r--
+sudo /usr/share/doc/sudo-1.7.4p4/sample.pam -rw-r--r--
+sudo /usr/share/doc/sudo-1.7.4p4/sample.sudoers -rw-r--r--
+sudo /usr/share/doc/sudo-1.7.4p4/sample.syslog.conf -rw-r--r--
+sudo /usr/share/doc/sudo-1.7.4p4/schema.ActiveDirectory -rw-r--r--
+sudo /usr/share/doc/sudo-1.7.4p4/schema.OpenLDAP -rw-r--r--
+sudo /usr/share/doc/sudo-1.7.4p4/schema.iPlanet -rw-r--r--
+sudo /usr/share/doc/sudo-1.7.4p4/sudoers.ldap.pod -rw-r--r--
+sudo /usr/share/doc/sudo-1.7.4p4/sudoers2ldif -rw-r--r--
+sudo /usr/share/man/man5/sudoers.5.gz -rw-r--r--
+sudo /usr/share/man/man5/sudoers.ldap.5.gz -rw-r--r--
+sudo /usr/share/man/man8/sudo.8.gz -rw-r--r--
+sudo /usr/share/man/man8/sudoedit.8.gz -rw-r--r--
+sudo /usr/share/man/man8/sudoreplay.8.gz -rw-r--r--
+sudo /usr/share/man/man8/visudo.8.gz -rw-r--r--
+sudo /var/db/sudo drwx------
+</pre></div><div class="section" id="RPM_Guide-Using_RPM_DB-Other_Query_Format_Tags"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="RPM_Guide-Using_RPM_DB-Other_Query_Format_Tags">4.2.17. Other Query Format Tags</h3></div></div></div><div class="para">
+ In addition to all these tags, there are a number of other miscellaneous tags, many of which are listed in Table 5-6.
+ </div><div class="para">
+ Table 5-6 Other query tags
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Tag
+ </div>
+
+ </td><td>
+ <div class="para">
+ Holds
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ ARCHIVESIZE
+ </div>
+
+ </td><td>
+ <div class="para">
+ Uncompressed size of the payload section
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ COOKIE
+ </div>
+
+ </td><td>
+ <div class="para">
+ Holds an opaque string
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMVERSION
+ </div>
+
+ </td><td>
+ <div class="para">
+ Holds the version of the RPM tool used to create the package
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ OPTFLAGS
+ </div>
+
+ </td><td>
+ <div class="para">
+ Compiler optimization flags used to build the package
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ PAYLOADFORMAT
+ </div>
+
+ </td><td>
+ <div class="para">
+ Must be cpio for LSB-compliant packages
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ PAYLOADCOMPRESSOR
+ </div>
+
+ </td><td>
+ <div class="para">
+ Must be gzip for LSB-compliant packages
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ PAYLOADFLAGS
+ </div>
+
+ </td><td>
+ <div class="para">
+ Must be 9 for LSB-compliant packages
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RHNPLATFORM
+ </div>
+
+ </td><td>
+ <div class="para">
+ Holds an opaque string
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ FILEVERIFYFLAGS
+ </div>
+
+ </td><td>
+ <div class="para">
+ Bitmask that specifies which tests to perform to verify the files after an install
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ For example, you can list the version of RPM that created a package with a command like the following:
+ </div><pre class="screen">
+$ rpm -qp --qf "%{name} - rpm %{rpmversion}\n" *.rpm
+qt - rpm 4.7.2
+qt - rpm 4.7.2
+qt-devel - rpm 4.7.2
+qt-mysql - rpm 4.7.2
+qt-sqlite - rpm 4.7.2
+qt-sqlite - rpm 4.7.2
+qt-x11 - rpm 4.7.2
+qt-x11 - rpm 4.7.2
+</pre><div class="note"><div class="admonition_header"><h2>Cross Reference</h2></div><div class="admonition"><div class="para">
+ See <a class="xref" href="#ch-package-structure">Cap. 24, <em>RPM Package File Structure</em></a> for a listing of all the tags in an RPM file.
+ </div></div></div></div></div><div class="section"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="id878995">4.3. Other queries</h2></div></div></div><div class="para">
+ If what you’ve seen so far isn’t enough, the rpm command supports a number of extra queries, mostly of use to developers.
+ </div><div class="para">
+ Table 5-7 summarizes these extra queries.
+ </div><div class="para">
+ Table 5-7 Extra Queries
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Option
+ </div>
+
+ </td><td>
+ <div class="para">
+ Meaning
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --dump
+ </div>
+
+ </td><td>
+ <div class="para">
+ Dumps out extra information on files
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --fileid md5_id
+ </div>
+
+ </td><td>
+ <div class="para">
+ Queries for the package with the given MD5 digest
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --hdrid sha1_header_id
+ </div>
+
+ </td><td>
+ <div class="para">
+ Queries for the package with the given header identifier number, in SHA1 format
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --last
+ </div>
+
+ </td><td>
+ <div class="para">
+ Reorders the output of the rpm command to show the most recently-installed packages first
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --pkgid md5_id
+ </div>
+
+ </td><td>
+ <div class="para">
+ Queries for the package with the given MD5 package ID
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --querybynumber number
+ </div>
+
+ </td><td>
+ <div class="para">
+ Queries for the given entry, by number, in the RPM database
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --tid transaction_id
+ </div>
+
+ </td><td>
+ <div class="para">
+ Queries for the package or packages with the given transaction ID
+ </div>
+
+ </td></tr></tbody></table></div></div><div class="section" id="RPM_Guide-Using_RPM_DB-Getting_information_on_package_files"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="RPM_Guide-Using_RPM_DB-Getting_information_on_package_files">4.4. Getting Information on Package Files</h2></div></div></div><div class="para">
+ In addition to querying the RPM database about installed packages, the rpm command provides the handy ability to extract information from RPM files. This is very useful for determining whether you want to install a given package or not. It also helps with the simple task of figuring out what a package’s purpose, especially if names like kudzu, anaconda, or dia don’t immediately tell you what the corresponding packages provide.
+ </div><div class="para">
+ The <code class="literal">–p</code> option tells the rpm command to provide information on the given package file. The basic syntax is:
+ </div><div class="para">
+ <code class="command">rpm –qp <em class="replaceable"><code>query_options</code></em> <em class="replaceable"><code>filename</code></em></code>
+ </div><div class="para">
+ You can use the longer option, <code class="literal">--package</code>, in place of <code class="literal">–p</code>. You can also pass more than one RPM file to the command.
+ </div><div class="para">
+ The query information options shown previously for installed packages also work for RPM files. For example, to list the configuration files for a package, combine the <code class="literal">-q</code>, <code class="literal">-p</code>, and <code class="literal">-c</code> options with the name of a package file, as shown following:
+ </div><pre class="screen">
+$ rpm -qpc qt-4.6.2-17.fc12.x86_64.rpm
+/etc/Trolltech.conf
+</pre><div class="para">
+ To list all the files in an RPM package, combine the <code class="literal">-q</code>, <code class="literal">-p</code>, and <code class="literal">-l</code> options (example output truncated):
+ </div><pre class="screen">
+$ rpm -qpl qt-4.6.2-17.fc12.x86_64.rpm
+/etc/Trolltech.conf
+/usr/bin/qdbus
+/usr/lib64/libQtCore.so.4
+/usr/lib64/libQtCore.so.4.6
+/usr/lib64/libQtCore.so.4.6.2
+/usr/lib64/libQtDBus.so.4
+/usr/lib64/libQtDBus.so.4.6
+/usr/lib64/libQtDBus.so.4.6.2
+/usr/lib64/libQtNetwork.so.4
+/usr/lib64/libQtNetwork.so.4.6
+</pre><div class="section" id="RPM_Guide_Using_RPM_DB-Querying_package_files_remotely"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="RPM_Guide_Using_RPM_DB-Querying_package_files_remotely">4.4.1. Querying Package Files Remotely</h3></div></div></div><div class="para">
+ As shown in <a class="xref" href="#ch-using-rpm">Cap. 3, <em>Using RPM</em></a> , you can access RPM package files over a network using FTP or HTTP connections. To query remote files, use the same rules as shown in <a class="xref" href="#ch-using-rpm">Cap. 3, <em>Using RPM</em></a> , with the following syntax:
+ </div><div class="para">
+ <code class="command">rpm -qp ftp://<em class="replaceable"><code>username</code></em>:<em class="replaceable"><code>password</code></em>@<em class="replaceable"><code>hostname</code></em>:<em class="replaceable"><code>port</code></em>/<em class="replaceable"><code>path/to/rpm/file</code></em></code>
+ </div><div class="para">
+ <code class="command">rpm -qp http://<em class="replaceable"><code>hostname</code></em>:<em class="replaceable"><code>port</code></em>/<em class="replaceable"><code>path/to/rpm/file</code></em></code>
+ </div><div class="para">
+ If your system resides behind a firewall with a proxy server, use the options in the following table to name the proxy. Note that these proxy options only work with the TIS Firewall toolkit.
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Network Proxy Option
+ </div>
+
+ </td><td>
+ <div class="para">
+ Meaning
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --ftpproxy proxy_hostname
+ </div>
+
+ </td><td>
+ <div class="para">
+ Names the proxy system
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --ftpport proxy_port_number
+ </div>
+
+ </td><td>
+ <div class="para">
+ Network port number on the proxy system
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --httpproxy proxy_hostname
+ </div>
+
+ </td><td>
+ <div class="para">
+ Names the proxy system
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --httpport proxy_port_number
+ </div>
+
+ </td><td>
+ <div class="para">
+ Network port number on the proxy system
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ </div></div><div class="section" id="RPM-Guide-Using_RPM-DB-verifying_packages"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="RPM-Guide-Using_RPM-DB-verifying_packages">4.4.2. Verifying Installed RPM Packages</h3></div></div></div><div class="para">
+ You can do a lot more than just query packages in the RPM database. You can ask the rpm command to verify packages with the <code class="option">-V</code> (or <code class="option">--verify</code>) option. The rpm -V command will also report missing dependencies.
+ </div><div class="para">
+ The basic syntax is:
+ </div><div class="para">
+ <code class="command">rpm -V <em class="replaceable"><code>verify_options</code></em> <em class="replaceable"><code>package_name</code></em></code>
+ </div><div class="para">
+ For example:
+ </div><pre class="screen">
+ rpm -V telnet
+ #
+</pre><div class="para">
+ If everything checks out, you'll get no response. The rpm command reports problems only. For example, if you have an installation of the telnet-server package that is missing some files, the rpm -V command will let you know, as shown following:
+ </div><pre class="screen">
+ $ rpm -V telnet-server
+ missing c /etc/xinetd.d/telnet
+ missing /usr/sbin/in.telnetd
+ missing d /usr/share/man/man5/issue.net.5.gz
+</pre><div class="para">
+ In this example, the c and d stand for configuration and documentation files, respectively.
+ </div><div class="para">
+ Note
+ </div><div class="section" id="RPM_Guide-Using_RPM_DB-verifying_system"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="RPM_Guide-Using_RPM_DB-verifying_system">4.4.2.1. Verifying your entire system</h4></div></div></div><div class="para">
+ To verify your entire system, use the <code class="option">-a</code> option.
+ </div><div class="para">
+ For example:
+ </div><pre class="screen">
+ # rpm -Va
+ SM5....T c /usr/share/info/dir
+ .......T c /etc/krb5.conf
+ .......T /usr/share/pixmaps/gnome-default-dlg.png
+ .......T /usr/share/pixmaps/gnome-error.png
+ .......T /usr/share/pixmaps/gnome-info.png
+ .......T /usr/share/pixmaps/gnome-question.png
+ .......T /usr/share/pixmaps/gnome-warning.png
+ S.5....T c /etc/sysconfig/pcmcia
+ .....U.. /dev/winradio0
+</pre><div class="para">
+ Each line that the rpm command outputs indicates a problem with the given file. The rpm command uses letter codes to show the type of the problem. Table 5-8 lists the letter codes with their meanings.
+ </div><div class="para">
+ Table 5-8 RPM verify output codes
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Code
+ </div>
+
+ </td><td>
+ <div class="para">
+ Meaning
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ S
+ </div>
+
+ </td><td>
+ <div class="para">
+ File size differs.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ M
+ </div>
+
+ </td><td>
+ <div class="para">
+ File mode differs.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ 5
+ </div>
+
+ </td><td>
+ <div class="para">
+ The MD5 checksum differs.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ D
+ </div>
+
+ </td><td>
+ <div class="para">
+ The major and minor version numbers differ on a device file.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ L
+ </div>
+
+ </td><td>
+ <div class="para">
+ A mismatch occurs in a link.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ U
+ </div>
+
+ </td><td>
+ <div class="para">
+ The file ownership differs.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ G
+ </div>
+
+ </td><td>
+ <div class="para">
+ The file group owner differs.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ T
+ </div>
+
+ </td><td>
+ <div class="para">
+ The file time (mtime) differs.
+ </div>
+
+ </td></tr></tbody></table></div></div><div class="section" id="RPM_Guide-Using_RPM_DB-controlling_verification"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="RPM_Guide-Using_RPM_DB-controlling_verification">4.4.2.2. Controlling the verification</h4></div></div></div><div class="para">
+ You can use a number of options to tell the verification command specifically what to check for or not check for. Table 5-9 lists these options.
+ </div><div class="para">
+ Table 5-9 Controlling the verification
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Option
+ </div>
+
+ </td><td>
+ <div class="para">
+ Usage
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nodeps
+ </div>
+
+ </td><td>
+ <div class="para">
+ Don't verify dependencies.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nodigest
+ </div>
+
+ </td><td>
+ <div class="para">
+ Don't verify the package or header digests.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nofiles
+ </div>
+
+ </td><td>
+ <div class="para">
+ Don't verify the file attributes.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --noscripts
+ </div>
+
+ </td><td>
+ <div class="para">
+ Don't try to verify the scripts.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nosignature
+ </div>
+
+ </td><td>
+ <div class="para">
+ Don't verify the package or header signatures.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nolinkto
+ </div>
+
+ </td><td>
+ <div class="para">
+ Don't verify the link file attribute.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nomd5
+ </div>
+
+ </td><td>
+ <div class="para">
+ Don't verify the MD5 digest file attribute.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nosize
+ </div>
+
+ </td><td>
+ <div class="para">
+ Don't verify the file size attribute.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nouser
+ </div>
+
+ </td><td>
+ <div class="para">
+ Don't verify the file owner attribute.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nogroup
+ </div>
+
+ </td><td>
+ <div class="para">
+ Don't verify the file group owner attribute.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nomtime
+ </div>
+
+ </td><td>
+ <div class="para">
+ Don't verify the file mtime attribute.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nomode
+ </div>
+
+ </td><td>
+ <div class="para">
+ Don't verify the file mode attribute.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nordev
+ </div>
+
+ </td><td>
+ <div class="para">
+ Don't verify the file rdev attribute.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -a
+ </div>
+
+ </td><td>
+ <div class="para">
+ Verify all packages in a given group.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -g group
+ </div>
+
+ </td><td>
+ <div class="para">
+ Verify all packages in a given group.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -p file
+ </div>
+
+ </td><td>
+ <div class="para">
+ Verify the given RPM file.
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ The <code class="option">--nofiles</code> option is often used with <code class="option"> –Va</code> to verify the whole system but skip tests of file attributes. This command is used so often it has become an idiom for RPM usage, especially for debugging RPM problems. Run a command like the following:
+ </div><div class="para">
+ <code class="command">rpm -Va --nofiles</code>
+ </div></div></div><div class="section" id="RPM_GUide-Using_RPM_DB-working_with_RPM_db"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="RPM_GUide-Using_RPM_DB-working_with_RPM_db">4.4.3. Working With the RPM Database</h3></div></div></div><div class="para">
+ As mentioned in <a class="xref" href="#ch-rpm-overview">Cap. 2, <em>RPM Overview</em></a> , the RPM database is stored in /var/lib/rpm. The files in that directory are Berkeley DB files, as shown by the file command:
+ </div><pre class="screen">
+ # file /var/lib/rpm/*
+ /var/lib/rpm/Basenames: Berkeley DB (Hash, version 7, native byte-order)
+ /var/lib/rpm/Conflictname: Berkeley DB (Hash, version 7, native byte-order)
+ /var/lib/rpm/__db.001: data
+ /var/lib/rpm/__db.002: X11 SNF font data, LSB first
+ /var/lib/rpm/__db.003: X11 SNF font data, LSB first
+ /var/lib/rpm/Dirnames: Berkeley DB (Btree, version 8, native byte-order)
+ /var/lib/rpm/Filemd5s: Berkeley DB (Btree, version 8, native byte-order)
+ /var/lib/rpm/Group: Berkeley DB (Hash, version 7, native byte-order)
+ /var/lib/rpm/Installtid: Berkeley DB (Btree, version 8, native byte-order)
+ /var/lib/rpm/Name: Berkeley DB (Hash, version 7, native byte-order)
+ /var/lib/rpm/Packages: Berkeley DB (Hash, version 7, native byte-order)
+ /var/lib/rpm/Providename: Berkeley DB (Hash, version 7, native byte-order)
+ /var/lib/rpm/Provideversion: Berkeley DB (Btree, version 8, native byte-order)
+ /var/lib/rpm/Requirename: Berkeley DB (Hash, version 7, native byte-order)
+ /var/lib/rpm/Requireversion: Berkeley DB (Btree, version 8, native byte-order)
+ /var/lib/rpm/Sha1header: Berkeley DB (Btree, version 8, native byte-order)
+ /var/lib/rpm/Sigmd5: Berkeley DB (Btree, version 8, native byte-order)
+ /var/lib/rpm/Triggername: Berkeley DB (Hash, version 7, native byte-order)
+</pre><div class="para">
+ Each file is a separate database in Berkeley DB format, except for a few __db data files. (These are not really X11 font files, just plain data files. The file command is confused by the data in the files.)
+ </div><div class="note"><div class="admonition_header"><h2>The Berkeley DB Library</h2></div><div class="admonition"><div class="para">
+ Available from Oracle at http://www.oracle.com/technetwork/database/berkeleydb/overview/, the Berkeley DB library provides a simple database API. This is not a traditional relational database. Instead, data values are stored in what amounts to a persistent hash table of name/value pairs. This type of database is very quick to look up a named entry (such as a package name) but is not so quick for iterating over all the entries.
+ </div></div></div><div class="para">
+ The RPM database is really a number of Berkeley DB databases, each designed for a different type of query.
+ </div><div class="para">
+ If something goes wrong with your RPM database, you can first try to rebuild it. If that fails, you may need to initialize a new database, although that is generally not needed. First and foremost, however, you should back up this database.
+ </div><div class="section" id="RPM_Guide-Using_RPM_DB-Backing_up_RPM_db"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="RPM_Guide-Using_RPM_DB-Backing_up_RPM_db">4.4.3.1. Backing up the RPM database</h4></div></div></div><div class="para">
+ As mentioned before, the RPM database resides in the /var/lib/rpm. You can back up the RPM database by using a command such as the following:
+ </div><div class="para">
+ <code class="command">tar cf <em class="replaceable"><code>rpmdb.tar</code></em> /var/lib/rpm</code>
+ </div></div><div class="section" id="RPM_Guide-Using_RPM_DB-rebuilding_RPM-db"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="RPM_Guide-Using_RPM_DB-rebuilding_RPM-db">4.4.3.2. Rebuilding the RPM database</h4></div></div></div><div class="para">
+ If the RPM database has been corrupted in some way, you can use the <code class="option">--rebuilddb</code> option to tell the rpm command to rebuild your database. For example:
+ </div><div class="para">
+ <code class="command">rpm --rebuilddb</code>
+ </div><div class="para">
+ This command rebuilds the RPM database from the installed packages, the file named <code class="filename">Packages</code> in the /var/lib/rpm directory. Only the <code class="filename">Packages</code> file is required. All the other files can be recreated from the <code class="filename">Packages</code> file. If your database is OK, this command won't do much, other than shrink the size of your RPM database by removing unused entries. This command will take some time to execute, though.
+ </div><div class="warning"><div class="admonition_header"><h2>Avertisment</h2></div><div class="admonition"><div class="para">
+ Before running this command, back up your RPM database.
+ </div></div></div><div class="para">
+ To check that the <code class="command">rpm --rebuilddb</code> command has not damaged the RPM database, you can check with a file listing, query all packages, and then check the results of the <code class="command">rpm –rebuilddb</code> command with another file listing when done.
+ </div></div><div class="section" id="RPM_Guide-Using_RPM_DB-new_db"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="RPM_Guide-Using_RPM_DB-new_db">4.4.3.3. Creating a new RPM database</h4></div></div></div><div class="para">
+ If all else fails, use the <code class="option">--initdb</code> option to tell the rpm command to create a new empty RPM database. In almost all cases, you do not want to create a new RPM database, since this database will be empty. It will not have any knowledge about the packages you have already installed on your system. That could lead to a lot of problems, since you have the files installed, but the RPM system just doesn’t know about them.
+ </div><div class="para">
+ The basic syntax follows.
+ </div><div class="para">
+ <code class="command">rpm --initdb</code>
+ </div><div class="para">
+ If the RPM system cannot be rebuilt, you may have to reinstall the operating system to recreate a clean system. In general, if things are this far gone, reinstalling may be your best answer instead of wiping the RPM database and creating an empty database.
+ </div><div class="para">
+ You can also use the <code class="option">--dbpath</code> option to tell the rpm command to create an RPM database in a different directory.
+ </div><div class="para">
+ For example:
+ </div><pre class="screen">
+ mkdir /tmp/rpm
+ rpm --initdb --dbpath /tmp/rpm
+</pre><div class="para">
+ These commands create a temporary directory and an RPM database in the /tmp/rpm directory.
+ </div><div class="para">
+ After running this command, you can examine the files created.
+ </div></div></div><div class="section" id="RPM_Guide-Using_RPM_DB-summary"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="RPM_Guide-Using_RPM_DB-summary">4.4.4. Summary</h3></div></div></div><div class="para">
+ This chapter covers the rpm command options to query the RPM database and RPM package files. You can determine the packages installed on your system, as well as which packages are responsible for the files on your system.
+ </div><div class="para">
+ The RPM database maintains a lot of information about the files and packages on your system. Thus, it is crucial for managing your Linux systems. You should back up the RPM database before and after any installation, upgrade, or removal of packages.
+ </div><div class="para">
+ You can also use the <code class="option">--rebuilddb</code> option to the rpm command to rebuild a damaged RPM database.
+ </div></div></div></div><div xml:lang="ro" class="chapter" id="ch-dependencies" lang="ro"><div class="titlepage"><div><div><h2 class="title">Cap. 5. Package Dependencies</h2></div></div></div><div class="toc"><dl><dt><span class="sect1"><a href="#id1301254">5.1. Understanding the Dependency Concept</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id754278">5.1.1. Capabilities</a></span></dt><dt><span class="sect2"><a href="#id656923">5.1.2. Version dependencies</a></span></dt><dt><span class="sect2"><a href="#id509482">5.1.3. Conflicts</a></span></dt><dt><span class="sect2"><a href="#id801957">5.1.4. Obsoletes</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id791830">5.2. Checking for Dependencies</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id508593">5.2.1. Determining the capabilities a package requires</a></span></dt><dt><span class="sect2"><a href="#id1330229">5.2.2. Determining the capabilities a package provides</a></span></dt><dt><spa
n class="sect2"><a href="#id978084">5.2.3. Checking for conflicts</a></span></dt><dt><span class="sect2"><a href="#id744095">5.2.4. Determining which packages require a certain capability</a></span></dt><dt><span class="sect2"><a href="#id641701">5.2.5. Determining which package provides a certain capability</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id514023">5.3. Triggers</a></span></dt><dt><span class="sect1"><a href="#id615970">5.4. Summary</a></span></dt></dl></div><div class="para">
+ This chapter covers:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Understanding dependencies
+ </div></li><li class="listitem"><div class="para">
+ Package capabilities
+ </div></li><li class="listitem"><div class="para">
+ Version dependencies
+ </div></li><li class="listitem"><div class="para">
+ Checking dependencies
+ </div></li><li class="listitem"><div class="para">
+ Triggers
+ </div></li></ul></div><div class="para">
+ Packages aren’t built in a vacuum. Web applications, for example, build on system networking libraries, system-encryption libraries, and system-file input and output libraries.
+ </div><div class="para">
+ This chapter covers dependencies between packages, along with ways to discover and manage those dependencies.
+ </div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id1301254" class="title">Understanding the Dependency Concept</h1></div></div></div><div class="para">
+ A dependency occurs when one package depends on another. You might think it would make for an easier-to-manage system if no package depended on any others, but you’d face a few problems, not the least of which would be dramatically increased disk usage.
+ </div><div class="para">
+ Packages on your Linux system depend on other packages. Just about every package with an application, for example, depends on the system C libraries, since these libraries provide common facilities that just about every program uses. Network applications typically depend on low-level networking libraries. These dependencies really work in your favor, since a security bug fix in the network libraries can update all applications that make use of the updated libraries.
+ </div><div class="para">
+ Furthermore, sharing software means that each package has less code to maintain and thus improved quality. Code sharing has been in the computer lexicon since the 1960s.
+ </div><div class="para">
+ Although quite a few packages depend on system-level libraries, some packages depend on applications defined in other packages. The Emacs text editor package, for example, depends on the Perl scripting language, specifically, the perl command. Database client programs usually depend on the database server applications.
+ </div><div class="para">
+ The RPM database tracks dependency information, so it can, for example, stop attempts to remove packages that other packages depend on or inform users of dependent packages upon installation.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id754278" class="title">Capabilities</h1></div></div></div><div class="para">
+ In RPM terminology, each package provides capabilities. A capability is simply a text string that the package claims it provides. In most cases, a capability names a file or a package. But the capability can be any arbitrary text string.
+ </div><div class="para">
+ Other packages can then depend on certain capabilities. (You can use this concept in building your own packages.) Each package lists the capabilities it requires as well as the capabilities it provides.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ Package dependencies and capabilities are very important when creating spec files for building your own RPM packages, the subject of <a class="xref" href="#ch-specfiles">Cap. 9, <em>Working with Spec Files</em></a> .
+ </div><div class="para">
+ When you install a package, the capability information is stored in the RPM database. When you remove a package, the rpm command checks the RPM database. If the package you are trying to remove provides a capability that another package needs, the command will generate an error. If you try to remove a package that other packages depend on, you'll see an error like the following:
+ </div><div class="para">
+ # rpm -e setup
+ </div><div class="para">
+ error: Failed dependencies:
+ </div><div class="para">
+ setup is needed by (installed) basesystem-8.0-1
+ </div><div class="para">
+ setup >= 2.0.3 is needed by (installed) initscripts-6.95-1
+ </div><div class="para">
+ setup >= 2.5.4-1 is needed by (installed) filesystem-2.1.6-5
+ </div><div class="para">
+ setup is needed by (installed) xinetd-2.3.7-2
+ </div><div class="para">
+ setup is needed by (installed) dump-0.4b28-4
+ </div><div class="para">
+ To verify that the package has not been removed, you can query for the package after trying to remove it, as shown following:
+ </div><div class="para">
+ # rpm -q setup
+ </div><div class="para">
+ setup-2.5.20-1
+ </div><div class="para">
+ This shows that the rpm command has not removed the setup package due to the errors.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ <a class="xref" href="#ch-using-rpm">Cap. 3, <em>Using RPM</em></a> covers ways to force the rpm command to do what you want, although this can cause problems if you try to force the issue and remove a crucial package. In virtually all cases, do not use any of the force options, as this can cause problems with the RPM system, since the force options are purposely ignoring safety checks performed by the rpm command.
+ </div><div class="para">
+ Many capabilities that packages require are system libraries, especially shared libraries. Shared libraries, which usually have a .so file extension (short for shared object), provide a memory-efficient means for applications to share program code. These libraries may also have a .so.number extension, such as libc.so.6.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ Shared libraries on Windows are called DLLs, short for Dynamic Link Libraries. The implementations differ, but the Windows DLL concept is similar to Linux and Unix shared objects.
+ </div><div class="para">
+ Shared libraries have been part of Linux for a long time and have nothing to do with the RPM system. Shared libraries accessed by a program, however, represent natural dependencies. Because so many programs depend on shared libraries, the RPM system can automatically handle many shared-library dependencies.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ To list the shared libraries that a program accesses, use the ldd command, for example:
+ </div><div class="para">
+ $ ldd /bin/grep
+ </div><div class="para">
+ libc.so.6 => /lib/i686/libc.so.6 (0x42000000)
+ </div><div class="para">
+ /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
+ </div><div class="para">
+ Other dependencies include version-specific dependencies.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id656923" class="title">Version dependencies</h1></div></div></div><div class="para">
+ An application may depend on a capability provided by another package. It may also depend on the capability that a specific version of another package provides. For example, some add-ons to the Apache Web server depend on the version of Apache. The Apache 2.0 version made a number of changes that affect add-on packages. Some Apache add-on packages depend on version 1.3; others depend on version 2.0.
+ </div><div class="para">
+ Most package dependencies assume some level of compatibility and require a version at or above a given version number (for example, version 2.0 or later).
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ You’ll see more version dependencies when applications make major changes, such as the change from 1.3 to 2.0 for the Apache Web server.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id509482" class="title">Conflicts</h1></div></div></div><div class="para">
+ Some packages may provide capabilities that interfere with those in other packages. This is called a conflict. Installing conflicting packages is an error. For example, the httpd package (the Apache Web server) conflicts with the thttpd package. Both packages want to provide the primary Web server for a system.
+ </div><div class="para">
+ The RPM system will prevent you from installing packages that conflict with other packages. You can force the issue, using the techniques described in <a class="xref" href="#ch-using-rpm">Cap. 3, <em>Using RPM</em></a> , and override the RPM system. But in most cases, you should not install packages that conflict.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id801957" class="title">Obsoletes</h1></div></div></div><div class="para">
+ The RPM system supports one more type of dependency, called obsoletes. This refers to a capability that a package provides that makes another capability obsolete. For example, a new version of the perl interpreter may make an older version obsolete. In most cases, the obsoletes dependency should be used when the name of a package changes. For example, the apache Web server package became the httpd package. You would expect the new package, httpd, to obsolete the old package name, apache.
+ </div><div class="para">
+ This brings the total to four types of dependencies that the RPM system tracks:
+ </div><div class="para">
+ *Requires, which tracks the capabilities a package requires
+ </div><div class="para">
+ *Provides, which tracks the capabilities a package provides for other packages
+ </div><div class="para">
+ *Conflicts, which describes the capabilities that if installed, conflict with capabilities in a package
+ </div><div class="para">
+ *Obsoletes, which describes the capabilities that this package will make obsolete
+ </div><div class="para">
+ Packages advertise this dependency information. Each dependency holds the type, such as requires, a capability, such as a shared library or a package name, and optionally a version number, such as requiring the python package at a version number greater than or equal to 2.2 (python >= 2.2).
+ </div><div class="para">
+ </div><div class="para">
+ You can check package dependencies by using, as you’d guess, the rpm command.
+ </div></div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id791830" class="title">Checking for Dependencies</h1></div></div></div><div class="para">
+ The rpm –q command queries the RPM database or RPM package files. With the right options to this command, you can check for the four types of package dependencies as well. These options are based on the concept of capabilities introduced previously.
+ </div><div class="para">
+ You can query what capabilities a package requires. You can also query what capabilities a package provides. You can query for the obsoleting and conflicting information as well. Furthermore, given a capability, you can query which packages require this capability as well as which packages provide this capability.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ There are quite a few more options you can use with the rpm –q command for querying packages. See <a class="xref" href="#ch-using-rpm-db">Cap. 4, <em>Using the RPM Database</em></a> for more on querying packages and package files.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id508593" class="title">Determining the capabilities a package requires</h1></div></div></div><div class="para">
+ The first and most important step is to determine what capabilities a package requires. If all the required capabilities are met, you can safely install the package (barring other things that can go wrong, such as conflicts). The requires dependencies are by far the most important.
+ </div><div class="para">
+ The --requires option to the rpm –q command lists the capabilities a given package requires. The basic syntax is:
+ </div><div class="para">
+ rpm –q query_options --requires packages
+ </div><div class="para">
+ For example:
+ </div><div class="para">
+ $ rpm -qp --requires sendmail-8.12.5-7.i386.rpm
+ </div><div class="para">
+ /usr/sbin/alternatives
+ </div><div class="para">
+ rpmlib(VersionedDependencies) <= 3.0.3-1
+ </div><div class="para">
+ chkconfig >= 1.3
+ </div><div class="para">
+ /usr/sbin/useradd
+ </div><div class="para">
+ /bin/mktemp
+ </div><div class="para">
+ fileutils
+ </div><div class="para">
+ gawk
+ </div><div class="para">
+ sed
+ </div><div class="para">
+ sh-utils
+ </div><div class="para">
+ procmail
+ </div><div class="para">
+ bash >= 2.0
+ </div><div class="para">
+ /bin/sh
+ </div><div class="para">
+ /bin/sh
+ </div><div class="para">
+ /bin/sh
+ </div><div class="para">
+ /bin/sh
+ </div><div class="para">
+ /bin/sh
+ </div><div class="para">
+ rpmlib(PayloadFilesHavePrefix) <= 4.0-1
+ </div><div class="para">
+ rpmlib(CompressedFileNames) <= 3.0.4-1
+ </div><div class="para">
+ /bin/bash
+ </div><div class="para">
+ libcrypto.so.2
+ </div><div class="para">
+ libcrypt.so.1
+ </div><div class="para">
+ libc.so.6
+ </div><div class="para">
+ libc.so.6(GLIBC_2.0)
+ </div><div class="para">
+ libc.so.6(GLIBC_2.1)
+ </div><div class="para">
+ libc.so.6(GLIBC_2.1.3)
+ </div><div class="para">
+ libc.so.6(GLIBC_2.2)
+ </div><div class="para">
+ libdb-4.0.so
+ </div><div class="para">
+ libgdbm.so.2
+ </div><div class="para">
+ libhesiod.so.0
+ </div><div class="para">
+ liblber.so.2
+ </div><div class="para">
+ libldap.so.2
+ </div><div class="para">
+ libnsl.so.1
+ </div><div class="para">
+ libnsl.so.1(GLIBC_2.0)
+ </div><div class="para">
+ libresolv.so.2
+ </div><div class="para">
+ libresolv.so.2(GLIBC_2.0)
+ </div><div class="para">
+ libresolv.so.2(GLIBC_2.2)
+ </div><div class="para">
+ libsasl.so.7
+ </div><div class="para">
+ libssl.so.2
+ </div><div class="para">
+ This example tests an RPM package file, sendmail-8.12.5-7.i386.rpm, for the requires dependency, in other words, what capabilities the package requires. The sendmail package depends on a lot of other parts of the system, as you can see in the response to the command shown previously. Most of the dependencies are for system libraries (all the dependencies ending in .so or .so.number). This package requires other capabilities (packages in this case). It also requires the chkconfig package at a specific version, version 1.3 or higher, and the bash package at version 2.0 or higher. The sendmail package also requires a particular version of the RPM system (the rpmlib dependency).
+ </div><div class="para">
+ Warning
+ </div><div class="para">
+ Always check what a package requires before installing the package. You can also use the --test option when trying to install the package to first test whether the installation can proceed. See <a class="xref" href="#ch-using-rpm">Cap. 3, <em>Using RPM</em></a> for details on installing packages and the --test option. The rpm command will perform all these checks for you anyway. Checking in advance, though, with the --test option, helps avoid dependency hell with circular dependencies.
+ </div><div class="para">
+ You can also check for what an installed package requires with the --requires option. For example:
+ </div><div class="para">
+ rpm -q --requires sendmail
+ </div><div class="para">
+ You can use the -R short option in place of the --requires option.
+ </div><div class="para">
+ This command returns the same data as the previous command but queries an installed package rather than an RPM package file.
+ </div><div class="para">
+ You might assume that applications have the most dependencies, which is true. But even source packages may depend on other packages, often the packages needed to build the sources into an application. For example, the following command lists the capabilities required by a source RPM:
+ </div><div class="para">
+ $ rpm -qp --requires telnet-0.17-23.src.rpm
+ </div><div class="para">
+ ncurses-devel
+ </div><div class="para">
+ Some packages require particular versions of other packages, for example:
+ </div><div class="para">
+ rpm -qp --requires xcdroast-0.98a9-18.src.rpm
+ </div><div class="para">
+ imlib-devel >= 1.9.13-9
+ </div><div class="para">
+ gtk+-devel >= 1.2.10
+ </div><div class="para">
+ desktop-file-utils >= 0.2.92
+ </div><div class="para">
+ rpmlib(CompressedFileNames) <= 3.0.4-1
+ </div><div class="para">
+ This example shows that the xcdroast source package requires the imlib-devel capability (in this case, a package) at version 1.9.13-9 or higher, the gtk+-devel package at version 1.2.10 or higher, and the desktop-file-utils package at version 0.2.92 or higher. This is a more stringent requirement than just depending on the given packages being installed. This RPM is also an older RPM package, based on the requirement for the rpmlib to be prior or equal to 3.0.4-1.
+ </div><div class="para">
+ Some packages may require a particular version of the rpmlib, or RPM library. For example, the setup package contains special system configuration files, including the default password file, /etc/passwd.
+ </div><div class="para">
+ $ rpm -q --requires setup
+ </div><div class="para">
+ rpmlib(PayloadFilesHavePrefix) <= 4.0-1
+ </div><div class="para">
+ rpmlib(CompressedFileNames) <= 3.0.4-1
+ </div><div class="para">
+ As shown in this example, this package depends only on capabilities of the RPM system itself. The particular requirements shown here specify how the rpm command should treat the package payload, including how the files are listed in the package and what type of compression is used.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id1330229" class="title">Determining the capabilities a package provides</h1></div></div></div><div class="para">
+ Packages require capabilities, and they can provide capabilities for other packages to require. To list the capabilities a package provides, use the --provides option. These capabilities can be arbitrary names, shared libraries (.so files), and the package name itself. The basic syntax is:
+ </div><div class="para">
+ rpm –q query_options --provides packages
+ </div><div class="para">
+ For example, the tcsh shell package provides two capabilities, at a particular version number, as shown following:
+ </div><div class="para">
+ $ rpm -q --provides tcsh
+ </div><div class="para">
+ csh = 6.12
+ </div><div class="para">
+ tcsh = 6.12-2
+ </div><div class="para">
+ Other packages provide a lot more, including shared libraries. The httpd package provides a long list of capabilities, as shown following:
+ </div><div class="para">
+ $ rpm -q --provides httpd
+ </div><div class="para">
+ webserver
+ </div><div class="para">
+ httpd-mmn = 20020628
+ </div><div class="para">
+ libapr.so.0
+ </div><div class="para">
+ libaprutil.so.0
+ </div><div class="para">
+ mod_access.so
+ </div><div class="para">
+ mod_actions.so
+ </div><div class="para">
+ mod_alias.so
+ </div><div class="para">
+ mod_asis.so
+ </div><div class="para">
+ mod_auth_anon.so
+ </div><div class="para">
+ mod_auth_dbm.so
+ </div><div class="para">
+ mod_auth_digest.so
+ </div><div class="para">
+ mod_auth.so
+ </div><div class="para">
+ mod_autoindex.so
+ </div><div class="para">
+ mod_cern_meta.so
+ </div><div class="para">
+ mod_cgi.so
+ </div><div class="para">
+ mod_dav_fs.so
+ </div><div class="para">
+ mod_dav.so
+ </div><div class="para">
+ mod_deflate.so
+ </div><div class="para">
+ mod_dir.so
+ </div><div class="para">
+ mod_env.so
+ </div><div class="para">
+ mod_expires.so
+ </div><div class="para">
+ mod_headers.so
+ </div><div class="para">
+ mod_imap.so
+ </div><div class="para">
+ mod_include.so
+ </div><div class="para">
+ mod_info.so
+ </div><div class="para">
+ mod_log_config.so
+ </div><div class="para">
+ mod_mime_magic.so
+ </div><div class="para">
+ mod_mime.so
+ </div><div class="para">
+ mod_negotiation.so
+ </div><div class="para">
+ mod_proxy_connect.so
+ </div><div class="para">
+ mod_proxy_ftp.so
+ </div><div class="para">
+ mod_proxy_http.so
+ </div><div class="para">
+ mod_proxy.so
+ </div><div class="para">
+ mod_rewrite.so
+ </div><div class="para">
+ mod_setenvif.so
+ </div><div class="para">
+ mod_speling.so
+ </div><div class="para">
+ mod_status.so
+ </div><div class="para">
+ mod_suexec.so
+ </div><div class="para">
+ mod_unique_id.so
+ </div><div class="para">
+ mod_userdir.so
+ </div><div class="para">
+ mod_usertrack.so
+ </div><div class="para">
+ mod_vhost_alias.so
+ </div><div class="para">
+ httpd = 2.0.40-8
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id978084" class="title">Checking for conflicts</h1></div></div></div><div class="para">
+ Use the --conflicts option to check what conflicts with a given package. The basic syntax is:
+ </div><div class="para">
+ rpm –q query_options --conflicts packages
+ </div><div class="para">
+ For example:
+ </div><div class="para">
+ # rpm -q --conflicts httpd
+ </div><div class="para">
+ thttpd
+ </div><div class="para">
+ This command tells you that the httpd package (the Apache Web server) conflicts with the thttpd package. Both packages provide a similar capability. By marking the conflict, the httpd package tells you that you cannot normally install both the httpd and thttpd packages on a system. This information comes from the httpd package, which has an entry in the package that indicates the conflict. The conflict is not guaranteed. These packages may work together, but the creator of the httpd package felt that httpd would not work with the thttpd package and helpfully let us all know.
+ </div><div class="para">
+ The RPM system will report on the conflicts and indicate an error if you try to install conflicting packages. The idea of conflicts really gives package creators a way to alert users to potential problems and to tell us that one package likely won’t work with another.
+ </div><div class="para">
+ The force options discussed in <a class="xref" href="#ch-using-rpm">Cap. 3, <em>Using RPM</em></a> allow you to override conflicts, if absolutely necessary. In most cases, though, a conflict presents you with the choice to install one or the other of the packages, but not both.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id744095" class="title">Determining which packages require a certain capability</h1></div></div></div><div class="para">
+ In addition to querying capabilities and requirements of a particular package, you can query the capabilities themselves. This function allows you to check which packages require a given capability.
+ </div><div class="para">
+ The --whatrequires option tells the rpm command to report on which packages in the RPM database require a certain capability. The basic syntax is:
+ </div><div class="para">
+ rpm –q query_options --whatrequires capability
+ </div><div class="para">
+ Some packages are not required by anything:
+ </div><div class="para">
+ $ rpm -q --whatrequires tcsh
+ </div><div class="para">
+ no package requires tcsh
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ Don’t worry about the poor tcsh package being lonely. Because other packages do not require this package, you can easily remove the tcsh package without affecting the rest of your system.
+ </div><div class="para">
+ This example shows a package name as the capability. Shared libraries are also considered capabilities. You can query on these as well. For example:
+ </div><div class="para">
+ $ rpm -q --whatrequires librpm-4.1.so
+ </div><div class="para">
+ rpm-4.1-1.06
+ </div><div class="para">
+ net-snmp-5.0.1-6
+ </div><div class="para">
+ rpm-python-4.1-1.06
+ </div><div class="para">
+ rpm-devel-4.1-1.06
+ </div><div class="para">
+ rpm-build-4.1-1.06
+ </div><div class="para">
+ This example shows that the core RPM library is used by a number of RPM-related packages, along with, oddly enough, the net-snmp system-management package.
+ </div><div class="para">
+ The capability you query for must be an explicit capability. For example, you will get different results if you query for the bash package or the command, /bin/bash. If you query for the bash package, you will see the packages that explicitly require the capability bash. For example:
+ </div><div class="para">
+ $ rpm -q --whatrequires bash
+ </div><div class="para">
+ gpm-1.19.3-20
+ </div><div class="para">
+ info-4.0b-3
+ </div><div class="para">
+ initscripts-6.40-1
+ </div><div class="para">
+ sendmail-8.11.6-3
+ </div><div class="para">
+ sysklogd-1.4.1-4
+ </div><div class="para">
+ vixie-cron-3.0.1-63
+ </div><div class="para">
+ ypbind-1.8-1
+ </div><div class="para">
+ ypserv-1.3.12-2
+ </div><div class="para">
+ If you instead query for the capability /bin/bash, that is, the file /bin/bash, you will see a different list of packages. For example:
+ </div><div class="para">
+ $ rpm -q --whatrequires /bin/bash
+ </div><div class="para">
+ apmd-3.0final-34
+ </div><div class="para">
+ at-3.1.8-20
+ </div><div class="para">
+ autofs-3.1.7-21
+ </div><div class="para">
+ autofs-3.1.7-21
+ </div><div class="para">
+ bash-2.05-8
+ </div><div class="para">
+ bind-9.1.3-4
+ </div><div class="para">
+ cipe-1.4.5-6
+ </div><div class="para">
+ crontabs-1.10-1
+ </div><div class="para">
+ dialog-0.9a-5
+ </div><div class="para">
+ gpm-1.19.3-20
+ </div><div class="para">
+ hotplug-2001_04_24-11
+ </div><div class="para">
+ initscripts-6.40-1
+ </div><div class="para">
+ ipchains-1.3.10-10
+ </div><div class="para">
+ iproute-2.2.4-14
+ </div><div class="para">
+ kudzu-0.99.23-1
+ </div><div class="para">
+ logwatch-2.1.1-3
+ </div><div class="para">
+ man-1.5i2-6
+ </div><div class="para">
+ mkbootdisk-1.4.2-3
+ </div><div class="para">
+ mkinitrd-3.2.6-1
+ </div><div class="para">
+ mutt-1.2.5i-17
+ </div><div class="para">
+ openssh-server-3.1p1-2
+ </div><div class="para">
+ pine-4.44-1.72.0
+ </div><div class="para">
+ rpm-build-4.0.3-1.03
+ </div><div class="para">
+ rusers-server-0.17-12
+ </div><div class="para">
+ sendmail-8.11.6-3
+ </div><div class="para">
+ shapecfg-2.2.12-7
+ </div><div class="para">
+ sharutils-4.2.1-8
+ </div><div class="para">
+ sysklogd-1.4.1-4
+ </div><div class="para">
+ tetex-1.0.7-30
+ </div><div class="para">
+ ucd-snmp-4.2.1-7
+ </div><div class="para">
+ vixie-cron-3.0.1-63
+ </div><div class="para">
+ xinetd-2.3.3-1
+ </div><div class="para">
+ ypbind-1.8-1
+ </div><div class="para">
+ ypserv-1.3.12-2
+ </div><div class="para">
+ There is no short form for the --whatrequires option.
+ </div><div class="para">
+ Other capabilities, especially system-level shared libraries, are used by a large number of packages. For example:
+ </div><div class="para">
+ # rpm -q --whatrequires libcrypt.so.1 | sort
+ </div><div class="para">
+ autofs-3.1.7-21
+ </div><div class="para">
+ cvs-1.11.1p1-3
+ </div><div class="para">
+ cyrus-sasl-1.5.24-23
+ </div><div class="para">
+ cyrus-sasl-devel-1.5.24-23
+ </div><div class="para">
+ cyrus-sasl-plain-1.5.24-23
+ </div><div class="para">
+ fetchmail-5.9.0-1
+ </div><div class="para">
+ ircii-4.4Z-7
+ </div><div class="para">
+ krbafs-1.0.9-2
+ </div><div class="para">
+ nss_ldap-172-2
+ </div><div class="para">
+ openldap12-1.2.12-4
+ </div><div class="para">
+ openldap-2.0.11-13
+ </div><div class="para">
+ openldap-clients-2.0.11-13
+ </div><div class="para">
+ pam-0.75-19
+ </div><div class="para">
+ pam_krb5-1.46-1
+ </div><div class="para">
+ passwd-0.64.1-7
+ </div><div class="para">
+ perl-5.6.0-17
+ </div><div class="para">
+ pine-4.44-1.72.0
+ </div><div class="para">
+ pwdb-0.61.1-3
+ </div><div class="para">
+ python-1.5.2-35
+ </div><div class="para">
+ rsh-0.17-5
+ </div><div class="para">
+ rsh-server-0.17-5
+ </div><div class="para">
+ screen-3.9.9-3
+ </div><div class="para">
+ sendmail-8.11.6-3
+ </div><div class="para">
+ shadow-utils-20000902-4
+ </div><div class="para">
+ sh-utils-2.0.11-5
+ </div><div class="para">
+ SysVinit-2.78-19
+ </div><div class="para">
+ tcsh-6.10-6
+ </div><div class="para">
+ util-linux-2.11f-17
+ </div><div class="para">
+ vim-enhanced-5.8-7
+ </div><div class="para">
+ wu-ftpd-2.6.1-20
+ </div><div class="para">
+ xinetd-2.3.3-1
+ </div><div class="para">
+ ypserv-1.3.12-2
+ </div><div class="para">
+ yp-tools-2.5-1
+ </div><div class="para">
+ Quite a few packages require encryption and decryption (the purpose of this library), making this library crucial to operating the system. Many of the packages listed here are in turn depended on by even more packages.
+ </div><div class="para">
+ To help trace back capabilities, you can combine the queries. For example:
+ </div><div class="para">
+ $ rpm -q --provides sendmail
+ </div><div class="para">
+ smtpdaemon
+ </div><div class="para">
+ sendmail = 8.11.6-3
+ </div><div class="para">
+ $ rpm -q --whatrequires smtpdaemon
+ </div><div class="para">
+ fetchmail-5.9.0-1
+ </div><div class="para">
+ mutt-1.2.5i-17
+ </div><div class="para">
+ The first command lists the capabilities that the sendmail package provides, including the generic capability of smtpdaemon. You can then list which packages require this particular capability, as shown in the second command. This is a big help for wading through a mess of packages depending on packages depending on yet more packages.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id641701" class="title">Determining which package provides a certain capability</h1></div></div></div><div class="para">
+ To complete the circle, you can query for which package provides a certain capability. This knowledge allows you to trace a requirement back to the package that provides it.
+ </div><div class="para">
+ The --whatprovides option tells the rpm command to list the capabilities a package provides. Use the --whatprovides option with the –q, or query, option to the rpm command. (There is no short form for the --whatrprovides option.)
+ </div><div class="para">
+ The basic syntax follows:
+ </div><div class="para">
+ rpm –q --whatprovides capability
+ </div><div class="para">
+ For example, to query what package provides the capability webserver, use the following command:
+ </div><div class="para">
+ $ rpm -q --whatprovides webserver
+ </div><div class="para">
+ httpd-2.0.40-8
+ </div><div class="para">
+ In this case, the capability is identified by an arbitrary string, webserver. This is a generic name for a given capability, serving Web pages.
+ </div><div class="para">
+ You can also trace individual files using the --whatprovides option. For example:
+ </div><div class="para">
+ $ rpm -q --whatprovides /etc/skel/.bashrc
+ </div><div class="para">
+ bash-2.05-8
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ The rpm –qf command, covered in the last chapter, is an easier way to get to the same information when tracking which package provides a particular file. For example:
+ </div><div class="para">
+ rpm -qf /etc/skel/.bashrc
+ </div><div class="para">
+ bash-2.05-8
+ </div><div class="para">
+ If you are querying particular files, use rpm –qf. If you are querying capabilities, use --whatprovides.
+ </div></div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id514023" class="title">Triggers</h1></div></div></div><div class="para">
+ A trigger is a script that gets run when a package is installed or uninstalled. Triggers allow packages that depend on other packages to properly configure themselves when those other packages are installed or removed.
+ </div><div class="para">
+ The --triggers option to the rpm command lists any trigger scripts in a given package. For example:
+ </div><div class="para">
+ $ rpm -q --triggers sendmail
+ </div><div class="para">
+ triggerpostun script (through /bin/sh) -- sendmail < 8.10.0
+ </div><div class="para">
+ /sbin/chkconfig --add sendmail
+ </div><div class="para">
+ This shows that the sendmail mail transfer agent (mail-sending program) provides a short trigger script.
+ </div><div class="para">
+ In contrast, the anonftp (anonymous file transfer) package has a fairly complex set of triggers, as shown following:
+ </div><div class="para">
+ $ rpm -q --triggers anonftp
+ </div><div class="para">
+ triggerin script (through /bin/sh) -- glibc
+ </div><div class="para">
+ copy() { file="`ls --sort=time $1 |head -n 1`"; ln -f "$file" "$2" 2>/dev/null |
+ </div><div class="para">
+ | cp -df "$file" "$2"; }
+ </div><div class="para">
+ # Kill off old versions
+ </div><div class="para">
+ rm -f /var/ftp/lib/ld-* /var/ftp/lib/libc* /var/ftp/lib/libnsl* /var/ftp/lib/lib
+ </div><div class="para">
+ nss_files* &>/dev/null || :
+ </div><div class="para">
+ # Copy parts of glibc, needed by various programs in bin.
+ </div><div class="para">
+ LIBCVER=`basename $(ls --sort=time /lib/libc-*.so |head -n 1) .so |cut -f2- -d-`
+ </div><div class="para">
+ copy /lib/ld-${LIBCVER}.so /var/ftp/lib
+ </div><div class="para">
+ copy /lib/libc-${LIBCVER}.so /var/ftp/lib
+ </div><div class="para">
+ copy /lib/libnsl-${LIBCVER}.so /var/ftp/lib
+ </div><div class="para">
+ copy /lib/libnss_files-${LIBCVER}.so /var/ftp/lib
+ </div><div class="para">
+ md5sum /var/ftp/lib/lib*-*.so /var/ftp/lib/libtermcap.so.*.*.* 2>/dev/null >/var
+ </div><div class="para">
+ /ftp/lib/libs.md5
+ </div><div class="para">
+ chmod 0400 /var/ftp/lib/libs.md5
+ </div><div class="para">
+ # Use ldconfig to build symlinks and whatnot.
+ </div><div class="para">
+ [ ! -e /var/ftp/etc/ld.so.conf ] && touch /var/ftp/etc/ld.so.conf
+ </div><div class="para">
+ /sbin/ldconfig -r /var/ftp
+ </div><div class="para">
+ triggerin script (through /bin/sh) -- fileutils
+ </div><div class="para">
+ copy() { file="`ls --sort=time $1 |head -n 1`"; ln -f "$file" "$2" 2>/dev/null |
+ </div><div class="para">
+ | cp -df "$file" "$2"; }
+ </div><div class="para">
+ copy /bin/ls /var/ftp/bin
+ </div><div class="para">
+ md5sum `ls /var/ftp/bin/* |grep -v bin.md5` >/var/ftp/bin/bin.md5
+ </div><div class="para">
+ chmod 0400 /var/ftp/bin/bin.md5
+ </div><div class="para">
+ triggerin script (through /bin/sh) -- cpio
+ </div><div class="para">
+ copy() { file="`ls --sort=time $1 |head -n 1`"; ln -f "$file" "$2" 2>/dev/null |
+ </div><div class="para">
+ | cp -df "$file" "$2"; }
+ </div><div class="para">
+ copy /bin/cpio /var/ftp/bin
+ </div><div class="para">
+ md5sum `ls /var/ftp/bin/* |grep -v bin.md5` >/var/ftp/bin/bin.md5
+ </div><div class="para">
+ chmod 0400 /var/ftp/bin/bin.md5
+ </div><div class="para">
+ triggerin script (through /bin/sh) -- tar
+ </div><div class="para">
+ copy() { file="`ls --sort=time $1 |head -n 1`"; ln -f "$file" "$2" 2>/dev/null |
+ </div><div class="para">
+ | cp -df "$file" "$2"; }
+ </div><div class="para">
+ copy /bin/tar /var/ftp/bin
+ </div><div class="para">
+ md5sum `ls /var/ftp/bin/* |grep -v bin.md5` >/var/ftp/bin/bin.md5
+ </div><div class="para">
+ chmod 0400 /var/ftp/bin/bin.md5
+ </div><div class="para">
+ triggerin script (through /bin/sh) -- gzip
+ </div><div class="para">
+ copy() { file="`ls --sort=time $1 |head -n 1`"; ln -f "$file" "$2" 2>/dev/null |
+ </div><div class="para">
+ | cp -df "$file" "$2"; }
+ </div><div class="para">
+ copy /bin/gzip /var/ftp/bin
+ </div><div class="para">
+ ln -sf gzip /var/ftp/bin/zcat
+ </div><div class="para">
+ md5sum `ls /var/ftp/bin/* |grep -v bin.md5` >/var/ftp/bin/bin.md5
+ </div><div class="para">
+ chmod 0400 /var/ftp/bin/bin.md5
+ </div><div class="para">
+ triggerin script (through /bin/sh) -- libtermcap
+ </div><div class="para">
+ copy() { file="`ls --sort=time $1 |head -n 1`"; ln -f "$file" "$2" 2>/dev/null |
+ </div><div class="para">
+ | cp -df "$file" "$2"; }
+ </div><div class="para">
+ rm -f /var/ftp/lib/libtermcap.so.*.*.* &>/dev/null || :
+ </div><div class="para">
+ copy '/lib/libtermcap.so.*.*.*' /var/ftp/lib
+ </div><div class="para">
+ md5sum /var/ftp/lib/lib*-*.so /var/ftp/lib/libtermcap.so.*.*.* 2>/dev/null >/var
+ </div><div class="para">
+ /ftp/lib/libs.md5
+ </div><div class="para">
+ chmod 0400 /var/ftp/lib/libs.md5
+ </div><div class="para">
+ # Use ldconfig to build symlinks and whatnot.
+ </div><div class="para">
+ [ ! -e /var/ftp/etc/ld.so.conf ] && touch /var/ftp/etc/ld.so.conf
+ </div><div class="para">
+ /sbin/ldconfig -r /var/ftp
+ </div><div class="para">
+ triggerin script (through /bin/sh) -- ncompress
+ </div><div class="para">
+ copy() { file="`ls --sort=time $1 |head -n 1`"; ln -f "$file" "$2" 2>/dev/null |
+ </div><div class="para">
+ | cp -df "$file" "$2"; }
+ </div><div class="para">
+ copy /usr/bin/compress /var/ftp/bin
+ </div><div class="para">
+ md5sum `ls /var/ftp/bin/* |grep -v bin.md5` >/var/ftp/bin/bin.md5
+ </div><div class="para">
+ chmod 0400 /var/ftp/bin/bin.md5
+ </div><div class="para">
+ triggerpostun script (through /bin/sh) -- anonftp 4.0
+ </div><div class="para">
+ if [ "$2" != 1 ] ; then
+ </div><div class="para">
+ # The user has multiple glibc packages installed. We can't read the
+ </div><div class="para">
+ # user's mind, so don't do anything.
+ </div><div class="para">
+ exit 0
+ </div><div class="para">
+ fi
+ </div><div class="para">
+ copy() { file="`ls --sort=time $1 |head -n 1`"; ln -f "$file" "$2" 2>/dev/null |
+ </div><div class="para">
+ | cp -df "$file" "$2"; }
+ </div><div class="para">
+ # Kill off old versions
+ </div><div class="para">
+ rm -f /var/ftp/lib/ld-* /var/ftp/lib/libc* /var/ftp/lib/libnsl* /var/ftp/lib/lib
+ </div><div class="para">
+ nss_files* &>/dev/null || :
+ </div><div class="para">
+ # Copy parts of glibc, needed by various programs in bin.
+ </div><div class="para">
+ LIBCVER=`basename /lib/libc-*.so .so | cut -f2- -d-`
+ </div><div class="para">
+ copy /lib/ld-${LIBCVER}.so /var/ftp/lib
+ </div><div class="para">
+ copy /lib/libc-${LIBCVER}.so /var/ftp/lib
+ </div><div class="para">
+ copy /lib/libnsl-${LIBCVER}.so /var/ftp/lib
+ </div><div class="para">
+ copy /lib/libnss_files-${LIBCVER}.so /var/ftp/lib
+ </div><div class="para">
+ copy /bin/ls /var/ftp/bin
+ </div><div class="para">
+ copy /bin/cpio /var/ftp/bin
+ </div><div class="para">
+ copy /bin/tar /var/ftp/bin
+ </div><div class="para">
+ copy /bin/gzip /var/ftp/bin
+ </div><div class="para">
+ ln -sf gzip /var/ftp/bin/zcat
+ </div><div class="para">
+ copy /usr/bin/compress /var/ftp/bin
+ </div><div class="para">
+ rm -f /var/ftp/lib/libtermcap.so.*.*.* &>/dev/null || :
+ </div><div class="para">
+ copy '/lib/libtermcap.so.*.*.*' /var/ftp/lib
+ </div><div class="para">
+ # Use ldconfig to build symlinks and whatnot.
+ </div><div class="para">
+ [ ! -e /var/ftp/etc/ld.so.conf ] && touch /var/ftp/etc/ld.so.conf
+ </div><div class="para">
+ /sbin/ldconfig -r /var/ftp
+ </div><div class="para">
+ # Generate md5sums for verifyscript
+ </div><div class="para">
+ md5sum /var/ftp/lib/lib*-*.so /var/ftp/lib/libtermcap.so.*.*.* 2>/dev/null >/var
+ </div><div class="para">
+ /ftp/lib/libs.md5
+ </div><div class="para">
+ chmod 0400 /var/ftp/lib/libs.md5
+ </div><div class="para">
+ md5sum `ls /var/ftp/bin/* |grep -v bin.md5` >/var/ftp/bin/bin.md5
+ </div><div class="para">
+ chmod 0400 /var/ftp/bin/bin.md5
+ </div><div class="para">
+ Reading through the scripts indicates that this package seems to be triggered by the glibc standard C programming library package. You can confirm this by using the --triggeredby option to the rpm command, as shown following:
+ </div><div class="para">
+ $ rpm -q --triggeredby glibc
+ </div><div class="para">
+ anonftp-4.0-9
+ </div><div class="para">
+ The anonftp package needs to be notified on changes to the glibc package, so that the anonftp package can properly set up its application. It actually uses part of glibc and is therefore highly susceptible to changes in the glibc package. Thus, the use of triggers provides essentially an extended form of dependencies. The anonftp package in this example depends so much on the glibc package that it needs to execute scripts whenever the glibc package changes.
+ </div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id615970" class="title">Summary</h1></div></div></div><div class="para">
+ Linux comes with many packages. Most of these packages depend on some other packages installed on your system. In RPM terms, packages provide capabilities and depend on capabilities that other packages provide. When the rpm command checks the RPM database for dependencies, it checks to ensure that all the capabilities that a given package requires are met by other installed packages.
+ </div><div class="para">
+ You can trace the capabilities a package requires with the --requires option to the rpm command. You can see what capabilities a package provides for others with the --provides option.
+ </div><div class="para">
+ Once you know a capability, you can query which package provides that capability with the --whatprovides option to the rpm command. And you can see which packages require that capability with the --whatrequires option.
+ </div><div class="para">
+ Triggers are an extended form of dependencies. A trigger is a script that gets executed when other packages are installed or removed. This allows a package with a high dependence on another package to track changes in that package and reconfigure itself as needed.
+ </div><div class="para">
+ The next chapter delves into transactions, which provide a safe means to install a set of packages. With transactions, either all the packages get installed, or none.
+ </div></div></div><div xml:lang="ro" class="chapter" id="ch-transactions" lang="ro"><div class="titlepage"><div><div><h2 class="title">Cap. 6. Transactions</h2></div></div></div><div class="toc"><dl><dt><span class="sect1"><a href="#id594651">6.1. Understanding Transactions</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id538656">6.1.1. When do you need transactions?</a></span></dt><dt><span class="sect2"><a href="#id567248">6.1.2. Backing out of transactions</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id634510">6.2. Transactions with the rpm Command</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id608937">6.2.1. Transaction IDs</a></span></dt><dt><span class="sect2"><a href="#id881620">6.2.2. Rolling Back Transactions</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id638162">6.3. Saving Old Packages</a></span></dt><dt><span class="sect1"><a href="#id834924">6.4. Summary</a></span></dt></dl></div><div class="para">
+ This chapter covers:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Understanding transactions
+ </div></li><li class="listitem"><div class="para">
+ Querying for packages based on transactions
+ </div></li><li class="listitem"><div class="para">
+ Rolling back transactions
+ </div></li><li class="listitem"><div class="para">
+ Saving old packages when upgrading
+ </div></li></ul></div><div class="para">
+ When packages depend on other packages, you may have to install multiple packages to add a single application. Some of the packages may install cleanly; others may not. But you have to install all of the packages to get the complete application. The designers of the RPM system understood this problem and added the concept of transactions to RPM.
+ </div><div class="para">
+ This chapter covers transactions and how they can help you cleanly install a set of dependent packages. But transactions won’t solve all your problems. You still have to resolve conflicts and dependencies by using the techniques provided in the last three chapters.
+ </div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id594651" class="title">Understanding Transactions</h1></div></div></div><div class="para">
+ A transaction is a way to delimit a set of operations. All the operations can be undone, often called rolled back. Once rolled back, the system is back in the same state it was prior to the transaction. If all the operations succeed, though, the system will be in a new state. The key issue is that all of the operations must complete successfully, or you can roll back the entire transaction. The assumption is that if any of the operations fail, the system will be in an inconsistent or erroneous state. Transactions are a way to prevent that.
+ </div><div class="para">
+ Transactions are common when working with databases, but they are just as important when working with packages.
+ </div><div class="para">
+ Starting with RPM version 4.0.4, transactions and rollbacks became a workable part of any administrator's toolkit. With RPM, the rpm command sets up a transaction any time you attempt to install, remove, or upgrade more than one package. The rpm command automatically makes a transaction.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id538656" class="title">When do you need transactions?</h1></div></div></div><div class="para">
+ Whenever you install or remove packages, the RPM system assigns a transaction and a transaction ID to the set of packages. You can then perform operations on the packages that share the same ID, including rolling back the transaction.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ Rollbacks work only for package upgrades with the 4.1 version of the RPM system, not package installs
+ </div><div class="para">
+ The RPM system saves an image of the RPM package header for each package installed or removed. You can use this image, along with RPM transaction IDs, to back out of transactions should something go wrong when setting up your system.
+ </div><div class="para">
+ The main advantage of transactions with RPM, though, is the fact that the rpm command automatically sets up a transaction for all the packages on each command line and does not perform the operation if any package fails. This ability to automatically set up transactions for each call to the rpm command eliminates many errors when working with packages.
+ </div><div class="para">
+ Use a transaction when you need to be sure that a set of packages install properly.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id567248" class="title">Backing out of transactions</h1></div></div></div><div class="para">
+ With RPM, backing out of a transaction involves two operations: rolling back the transaction and reinstalling the former packages to restore the previous system state. In the simplest case, the rpm command handles all the tasks for you. If you try to install, upgrade, or remove multiple packages and any package fails, the rpm command will restore the system state for you.
+ </div><div class="para">
+ This automatic support for transactions is a great help to system administrators, but it only applies when you first install, upgrade, or remove the packages. If you have upgraded your system and later discover problems, then you can also use the --rollback option to roll the system back from a set of upgrades, in a limited set of circumstances.
+ </div></div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id634510" class="title">Transactions with the rpm Command</h1></div></div></div><div class="para">
+ To set up an RPM transaction, you don't have to do much. All you need to do is pass more than one RPM package on the rpm command line. For example, to set up a transaction for installing three packages, use a command like the following:
+ </div><div class="para">
+ rpm -ihv package1.rpm package2.rpm package3.rpm
+ </div><div class="para">
+ If any of the packages fail to install, the rpm command will not install any packages. All of the packages will be installed, or none.
+ </div><div class="para">
+ This way, if you have a number of packages that together perform some function, such as an Integrated Development Environment (IDE), along with program-language compilers and other software-development tools, you can ensure that all get installed.
+ </div><div class="para">
+ As an example, say you need to install the gnorpm package, which provides a graphical front end for the rpm command, and the rpmrebuild package, which allows you to create RPMs from already-installed packages.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ The gnorpm command is covered in <a class="xref" href="#ch-management-software">Cap. 7, <em>RPM Management Software</em></a> . The rpmrebuild package is covered in the "Saving Old Packages" section in this chapter.
+ </div><div class="para">
+ You can install these packages with a transaction by using the following command:
+ </div><div class="para">
+ # rpm -ihv gnorpm-0.9-1.i386.rpm rpmrebuild-1.0-0.noarch.rpm
+ </div><div class="para">
+ Preparing... ########################################### [100%]
+ </div><div class="para">
+ package gnorpm-0.9-1 is already installed
+ </div><div class="para">
+ The rpmrebuild package can be installed. (We know this since the rpm command did not issue an error about this package.) But because it was on the same command line as the gnorpm package, the transaction failed. No packages were installed.
+ </div><div class="para">
+ To check that the rpmrebuild package was not installed (that is, to check that the transaction worked as expected), you can use the rpm –q command to see if the rpmrebuild package was installed or not. To do so, use a command like the following:
+ </div><div class="para">
+ # rpm -q rpmrebuild
+ </div><div class="para">
+ package rpmrebuild is not installed
+ </div><div class="para">
+ This shows that the rpmrebuild package was not installed, even though the package could be installed on its own. To check that the package could be installed, you can use the --test option, as shown following:
+ </div><div class="para">
+ # rpm -i --test rpmrebuild-1.0-0.noarch.rpm
+ </div><div class="para">
+ #
+ </div><div class="para">
+ This command shows that the rpmrebuild package would install successfully on its own. If there were problems, the rpm command would have issued an error message.
+ </div><div class="para">
+ This example shows that when you try to install multiple packages with the rpm command, should any fail, the rpm command will not install any.
+ </div><div class="para">
+ The rpm command works similarly for removing packages and upgrading packages. When removing packages, you’ll see an error like the following if any of the packages on the command line cannot be removed:
+ </div><div class="para">
+ # rpm -e setup jikes-1.17
+ </div><div class="para">
+ error: Failed dependencies:
+ </div><div class="para">
+ setup is needed by (installed) basesystem-8.0-1
+ </div><div class="para">
+ setup >= 2.0.3 is needed by (installed) initscripts-6.95-1
+ </div><div class="para">
+ setup >= 2.5.4-1 is needed by (installed) filesystem-2.1.6-5
+ </div><div class="para">
+ setup is needed by (installed) xinetd-2.3.7-2
+ </div><div class="para">
+ setup is needed by (installed) dump-0.4b28-4
+ </div><div class="para">
+ The setup package could not be removed because it had several capabilities needed by other packages. You can check that the jikes package was not removed by using the rpm –q command, even though it had no failed dependencies:
+ </div><div class="para">
+ # rpm -q jikes
+ </div><div class="para">
+ jikes-1.17-1
+ </div><div class="para">
+ This package was not removed because it appeared as part of the same command that failed, so none of the operations were performed.
+ </div><div class="para">
+ When upgrading, you will also see an error message if any of the package upgrades fail. For example:
+ </div><div class="para">
+ # rpm -Uhv jikes-1.14-1.i386.rpm autoupdate-3.1.5-1.noarch.rpm
+ </div><div class="para">
+ error: jikes-1.14-1.i386.rpm cannot be installed
+ </div><div class="para">
+ You can then check that the jikes package, in this example, was not downgraded to the earlier version with the rpm –q command:
+ </div><div class="para">
+ # rpm -q jikes
+ </div><div class="para">
+ jikes-1.17-1
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id608937" class="title">Transaction IDs</h1></div></div></div><div class="para">
+ The rpm command gives every package installed a transaction ID. The transaction ID is a Unix time stamp (number of seconds since January 1, 1970). You can then perform some operations on packages based on the transaction ID.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ The fact that a transaction ID uses a Unix timestamp may change in the future.
+ </div><div class="para">
+ All the packages installed at the same time are given the same transaction ID. This means that you can perform operations on a set of packages, the packages that were installed together.
+ </div><div class="para">
+ But there’s also a downside to this. All the packages installed when you first installed or upgraded your Linux system are given the same transaction ID. This means you cannot selectively act on these packages using the transaction ID, because you will likely get far more packages than you want to work on.
+ </div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id672205" class="title">Viewing RPM Transaction IDs</h1></div></div></div><div class="para">
+ To view the install transaction ID (a date code) for a given package, you can use a command like the following:
+ </div><div class="para">
+ $ rpm -q --qf "%-20{NAME} %-20{INSTALLTID}\n" jikes
+ </div><div class="para">
+ jikes 1035589778
+ </div><div class="para">
+ This command uses the --qf or --queryformat option to specify the data to return from the RPM query command. In this case, the command requests the name of the package as well as the transaction ID (TID) for installation.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ <a class="xref" href="#ch-using-rpm-db">Cap. 4, <em>Using the RPM Database</em></a> describes the --queryformat option.
+ </div><div class="para">
+ There is also a transaction ID for removal, the REMOVETID. You can also query for this ID. For example, if a package hasn't been removed, you'll see an entry like the following:
+ </div><div class="para">
+ $ rpm -qa --qf "%-20{NAME} %-20{REMOVETID}\n" termcap
+ </div><div class="para">
+ termcap (none)
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id729772" class="title">Viewing the Packages Associated with a Transaction ID</h1></div></div></div><div class="para">
+ Once you have a transaction ID, you can use the --tid option, short for transaction ID, to query for the package associated with a given transaction, using a command like the following:
+ </div><div class="para">
+ $ rpm -q --tid 1035589778
+ </div><div class="para">
+ jikes-1.17-1
+ </div><div class="para">
+ This example uses the transaction ID that the earlier query example returned. If you installed more than one package at the same time, you will see a listing of all the packages that share the transaction ID.
+ </div><div class="para">
+ For example, to see many packages with one transaction ID, you can query for packages installed when you installed or upgraded your version of Linux. First, query for the transaction ID of a package you know was installed with the Linux distribution, such as setup on a Red Hat system:
+ </div><div class="para">
+ $ rpm -q --qf "%-20{NAME} %-20{INSTALLTID}\n" setup
+ </div><div class="para">
+ setup 1033838323
+ </div><div class="para">
+ Second, use this transaction ID and query for all packages with this ID, using code like the following:
+ </div><div class="para">
+ $ rpm -q --tid 1033838323 | more
+ </div><div class="para">
+ redhat-menus-0.26-1
+ </div><div class="para">
+ glibc-2.2.93-5
+ </div><div class="para">
+ cracklib-2.7-18
+ </div><div class="para">
+ gdbm-1.8.0-18
+ </div><div class="para">
+ gmp-4.1-4
+ </div><div class="para">
+ libacl-2.0.11-2
+ </div><div class="para">
+ libjpeg-6b-21
+ </div><div class="para">
+ linc-0.5.2-2
+ </div><div class="para">
+ pcre-3.9-5
+ </div><div class="para">
+ shadow-utils-20000902-12
+ </div><div class="para">
+ libtermcap-2.0.8-31
+ </div><div class="para">
+ freetype-2.1.2-7
+ </div><div class="para">
+ info-4.2-5
+ </div><div class="para">
+ fileutils-4.1.9-11
+ </div><div class="para">
+ psmisc-20.2-6
+ </div><div class="para">
+ ntp-4.1.1a-9
+ </div><div class="para">
+ mount-2.11r-10
+ </div><div class="para">
+ cracklib-dicts-2.7-18
+ </div><div class="para">
+ krb5-libs-1.2.5-6
+ </div><div class="para">
+ cyrus-sasl-2.1.7-2
+ </div><div class="para">
+ usermode-1.63-1
+ </div><div class="para">
+ Xft-2.0-1
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ Be sure to replace the transaction ID shown here with the transaction ID obtained by querying your system.
+ </div><div class="para">
+ This example shows just a few of the packages installed when the Red Hat Linux was installed.
+ </div><div class="para">
+ With these options, you can find the transaction IDs for given packages and can use the rpm command to install, remove, or otherwise modify the packages that share a transaction ID.
+ </div></div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id881620" class="title">Rolling Back Transactions</h1></div></div></div><div class="para">
+ The --rollback option to the rpm command allows you to roll back upgrades based on a time. Use a command like the following:
+ </div><div class="para">
+ # rpm –U --rollback "3 months ago"
+ </div><div class="para">
+ </div><div class="para">
+ The --rollback option is very limited in what it can do. The --rollback option works only for packages that have been upgraded. You cannot rollback the initial installation of a package. This is to prevent you from accidentally rolling back all packages.
+ </div><div class="para">
+ The --rollback option works best if you want to restore the system to a previous state, prior to performing any other RPM operations. That is, soon after you upgraded a package and decide that it isn’t working right. If you have modified the RPM system after performing the transaction you want to rollback, there may be unintended consequences if any new package depends on the packages you want to roll back. In addition, the --rollback option only works in limited situations but does not always report when these conditions are not met. The rpm command may simply do nothing, or it may remove packages you do not expect.
+ </div><div class="para">
+ Warning
+ </div><div class="para">
+ Before running the --rollback option, backup your RPM database as described in <a class="xref" href="#ch-using-rpm-db">Cap. 4, <em>Using the RPM Database</em></a> .
+ </div><div class="para">
+ Because of all these limitations, rollbacks do not work in all situations. In place of the --rollback option, you can use the query shortcuts introduced in <a class="xref" href="#ch-using-rpm-db">Cap. 4, <em>Using the RPM Database</em></a> and find the packages you have installed recently (if that is what you want to roll back). In this case, you can use the rpm command to remove the packages you want to get rid of and reinstall the packages you want to restore.
+ </div><div class="para">
+ In many cases, this manual approach is safest, and you will have a clearer understanding about what was installed or upgraded on your system.
+ </div></div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id638162" class="title">Saving Old Packages</h1></div></div></div><div class="para">
+ When installing, removing, or upgrading, you can use the --repackage command-line option to save a version of something like the old package to a file, making a backup of the older package contents.
+ </div><div class="para">
+ Warning
+ </div><div class="para">
+ The package created by the --repackage option is not a complete RPM package. You can use the rpmbuild command to make it into a complete package, but by itself, it will not be a complete package. See <a class="xref" href="#ch-specfiles">Cap. 9, <em>Working with Spec Files</em></a>, <a class="xref" href="#ch-advanced-packaging">Cap. 10, <em>Creare avansată pachete RPM</em></a>, and <a class="xref" href="#ch-rpmbuild">Cap. 11, <em>Controlling the Build with <code class="command">rpmbuild</code></em></a> for more on building packages.
+ </div><div class="para">
+ </div><div class="para">
+ You can later reinstall the old files, once they have been made into a complete package. This can be quite useful if something goes wrong or the upgraded package has bugs. You can fall back to the old package if needed.
+ </div><div class="para">
+ By default, the --repackage option puts the old package in the /var/spool/repackage directory. Other common directories are /var/spool/up2date or /var/tmp. Your RPM configuration determines the directory used by this option.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ The up2date name comes from the Red Hat service for keeping a system up to date with regard to package versions.
+ </div><div class="para">
+ For example, say you have a package, jikes (a Java programming language compiler used in previous examples) that you want to upgrade. But you are worried that the new version may not work properly.
+ </div><div class="para">
+ First, check the version you have. For example:
+ </div><div class="para">
+ # rpm -q jikes
+ </div><div class="para">
+ jikes-1.14-1
+ </div><div class="para">
+ This shows you are at version 1.14 of the jikes Java compiler. You can then upgrade to version 1.17 while repackaging the old version, as shown following:
+ </div><div class="para">
+ # rpm -Uhv --repackage jikes-1.17-glibc2.2-1.i386.rpm
+ </div><div class="para">
+ Preparing... ########################################### [100%]
+ </div><div class="para">
+ Repackaging...
+ </div><div class="para">
+ 1:jikes ########################################### [100%]
+ </div><div class="para">
+ Upgrading...
+ </div><div class="para">
+ 1:jikes ########################################### [100%]
+ </div><div class="para">
+ This upgrade has kept a copy of the old package in the /var/spool/repackage directory. You can verify this with the following command:
+ </div><div class="para">
+ $ ls -l /var/spool/repackage/
+ </div><div class="para">
+ total 692
+ </div><div class="para">
+ -rw-r--r-- 1 root root 703037 Oct 25 18:49 jikes-1.14-1.i386.rpm
+ </div><div class="para">
+ You can see a version of the old package, with the old version number.
+ </div><div class="para">
+ Warning
+ </div><div class="para">
+ This is not the same as the original package. This is not a complete package.
+ </div><div class="para">
+ The repackaged RPM contains a snapshot of the package’s files as they were on your hard disk, not as they were when you originally installed the package. Thus, the contents may differ if the files have changed on your hard disk. In addition, the --repackage option may not properly sign the package as the original was.
+ </div><div class="para">
+ In addition to the --repackage option with the rpm command, you can use a free tool called rpmrebuild to make snapshots of any installed packages.
+ </div><div class="para">
+ Written by Eric Gerbier, rpmrebuild allows you to create an RPM from the installed, and perhaps modified, version of a package. You don’t have to upgrade, remove, or install a new package, as you do with the --repackage option.
+ </div><div class="para">
+ Download rpmrebuild from http://rpmrebuild.sourceforge.net/.
+ </div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id834924" class="title">Summary</h1></div></div></div><div class="para">
+ Transactions allow you to install multiple packages as a group and know that either all the packages will succeed in installing or none of them will. This is very important if you have a set of interlocking packages that you need to install.
+ </div><div class="para">
+ All the packages you install, remove, or upgrade on the same command line are automatically made part of a transaction. The rpm command will ensure that all packages can be installed, removed, or upgraded, and will not perform the operation unless all will succeed.
+ </div><div class="para">
+ All packages installed or removed are given a transaction ID, which uses a Unix timestamp (the number of seconds since January 1, 1970). All packages installed or removed at the same time are given the same transaction ID. You can then query by transaction IDs to perform operations on all the packages installed together.
+ </div><div class="para">
+ The --repackage option tells the rpm command to make a backup RPM of the current package when you are installing or upgrading a more recent version or removing the package. By default, the backup RPM is placed in the /var/spool/repackage directory. Note that a package created this way is not exactly the same as the original package. Files may have changed on disk. In addition, packages created with the --repackage option are not real valid RPM packages. You cannot install these packages without performing extra operations to create a real RPM package from the repackaged data.
+ </div><div class="para">
+ </div></div></div><div xml:lang="ro" class="chapter" id="ch-management-software" lang="ro"><div class="titlepage"><div><div><h2 class="title">Cap. 7. RPM Management Software</h2></div></div></div><div class="toc"><dl><dt><span class="sect1"><a href="#id595261">7.1. Locating RPMs</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id736680">7.1.1. rpmfind and rpm2html</a></span></dt><dt><span class="sect2"><a href="#id869488">7.1.2. RPM Sites On the Internet</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id561016">7.2. Graphical RPM Management</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id561039">7.2.1. Nautilus</a></span></dt><dt><span class="sect2"><a href="#id734494">7.2.2. Red Hat Package Management</a></span></dt><dt><span class="sect2"><a href="#id579713">7.2.3. KPackage</a></span></dt><dt><span class="sect2"><a href="#id856872">7.2.4. Gnome-RPM</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id503396">7.3. Extending RPM Managem
ent</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id554830">7.3.1. AutoRPM</a></span></dt><dt><span class="sect2"><a href="#id760680">7.3.2. AutoUpdate</a></span></dt><dt><span class="sect2"><a href="#id715873">7.3.3. The Red Hat Network and up2date</a></span></dt><dt><span class="sect2"><a href="#id750620">7.3.4. Current</a></span></dt><dt><span class="sect2"><a href="#id750644">7.3.5. urpmi and RpmDrake</a></span></dt><dt><span class="sect2"><a href="#id697201">7.3.6. apt-rpm</a></span></dt><dt><span class="sect2"><a href="#id559117">7.3.7. The poldek</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id591000">7.4. Summary</a></span></dt></dl></div><div class="para">
+ This chapter covers:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Finding packages in RPM format
+ </div></li><li class="listitem"><div class="para">
+ Graphical tools to manage RPM packages
+ </div></li><li class="listitem"><div class="para">
+ Extending RPM management with additional tools
+ </div></li></ul></div><div class="para">
+ You can find a variety of software packages to ease the work of managing RPM-based systems. These utilities can help you find a specific software application packaged using RPM or search through a collection of RPM-packaged software to locate applications with specific features. Similarly, several utilities provide features to ease long-term system-management tasks. These applications provide features such as automatic updating of existing installed software with more recent versions or simplification of software installation by automating installation of any required software dependencies.
+ </div><div class="para">
+ This chapter covers a number of tools for finding packages in RPM format, as well as tools to help manage the RPMs on your system.
+ </div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id595261" class="title">Locating RPMs</h1></div></div></div><div class="para">
+ RPM provides a powerful tool for managing software installed on a system. With a single command, an entire application can be installed on the system in a ready-to-run configuration. With a different command, the entire application can be removed without having manually to track down all of the associated files scattered throughout the hard drive. For RPM to work, however, the software being managed must be packaged in the proper RPM format. RPM packages can be easily prepared if necessary, but you can save time by using the wide variety of software already available in the RPM format. The only trick to using this RPM-packaged software is finding it.
+ </div><div class="para">
+ As you start to search for RPM packages on the Internet, you’ll find thousands of packages available. Many of these packages are built specifically for various Linux distributions, such as Conectiva, SUSE, Red Hat, or Mandrake. In many cases, the Linux distribution won’t matter, but in general it's best to download packages built for your version of Linux, such as Red Hat.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ Although the examples in this book assume Red Hat Linux as a base, just about everything applies to all versions of Linux that use the RPM system, unless noted otherwise.
+ </div><div class="para">
+ Internet search engines are popular, but they aren’t very helpful for finding RPM packages, especially because lots of Web pages have the term rpm (including those covering revolutions per minute). A more efficient approach is to use one of the RPM-specific Internet search tools such as rpmfind.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id736680" class="title">rpmfind and rpm2html</h1></div></div></div><div class="para">
+ One popular free tool for locating RPMs is rpmfind, written by Daniel Veillard. This tool provides a command-line utility that can search for packages by name or description, displaying or optionally downloading any matching packages it finds. It can even provide a list of the dependencies that those matching packages require to run and can download those required dependencies as well.
+ </div><div class="para">
+ When searching for packages, rpmfind can search both the software already installed on the local system and remote databases, including the databases located at http://rpmfind.net/.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ The databases at http://rpmfind.net/ are, in turn, created by another utility: rpm2html. Both are covered in the sections following.
+ </div><div class="para">
+ Commonly, rpmfind is used to search for packages by name, though it can be used to search package descriptions for key words. For example, I might want to find new e-mail clients to install on my system. I happen to know that one popular Linux e-mail client is Ximian’s evolution, so I search for that.
+ </div><div class="para">
+ The basic syntax for rpmfind follows:
+ </div><div class="para">
+ rpmfind package_name
+ </div><div class="para">
+ For example, to search for evolution, use a command like the following:
+ </div><div class="para">
+ $ rpmfind evolution
+ </div><div class="para">
+ Resource evolution already installed
+ </div><div class="para">
+ $
+ </div><div class="para">
+ Before accessing the Internet, rpmfind searches my local system and finds that I already have evolution installed, so it does not even bother searching for copies to download. It looks like I’m forgetful, not remembering that I already have evolution installed. At this point, I might realize that I already have the software I need, or I might decide to search for a similar application, such as exmh, another popular Unix e-mail client.
+ </div><div class="para">
+ To search for exmh (which in this example has not been installed), use a command like the following:
+ </div><div class="para">
+ $ rpmfind exmh
+ </div><div class="para">
+ Installing exmh will require 7301 KBytes
+ </div><div class="para">
+ </div><div class="para">
+ ### To Transfer:
+ </div><div class="para">
+ ftp://ftp.redhat.com/pub/redhat/linux/7.2/en/os/i386/RedHat/RPMS//nmh-1.0.4-9.i3
+ </div><div class="para">
+ 86.rpm
+ </div><div class="para">
+ ftp://ftp.redhat.com/pub/redhat/linux/7.2/en/os/i386/RedHat/RPMS//exmh-2.4-2.noarch.rpm
+ </div><div class="para">
+ Do you want to download these files to /tmp [Y/n/a/i] ? : a
+ </div><div class="para">
+ transferring
+ </div><div class="para">
+ ftp://ftp.redhat.com/pub/redhat/linux/7.2/en/os/i386/RedHat/RPMS//nmh-1.0.4-9.i386.rpm
+ </div><div class="para">
+ saving to /tmp/nmh-1.0.4-9.i386.rpm
+ </div><div class="para">
+ transferring
+ </div><div class="para">
+ ftp://ftp.redhat.com/pub/redhat/linux/7.2/en/os/i386/RedHat/RPMS//exmh-2.4-2.noarch.rpm
+ </div><div class="para">
+ saving to /tmp/exmh-2.4-2.noarch.rpm
+ </div><div class="para">
+ rpm -U /tmp/nmh-1.0.4-9.i386.rpm /tmp/exmh-2.4-2.noarch.rpm
+ </div><div class="para">
+ $
+ </div><div class="para">
+ Here, rpmfind searches my local system for exmh. Since exmh is not installed there, rpmfind searches the databases at http://rpmfind.net/ and does two things: it finds exmh, and it learns that exmh depends upon another package: nmh. After double-checking and learning that nmh is not installed on my local system, rpmfind gives me a choice regarding whether I should download both of those packages; rpmfind gives me four possible answers:
+ </div><div class="para">
+ Do you want to download these files to /tmp [Y/n/a/i] ? : a
+ </div><div class="para">
+ My possible answers were:
+ </div><div class="para">
+ YYes, do download the files.
+ </div><div class="para">
+ NNo, do not download the files.
+ </div><div class="para">
+ AGet all. By default, run in Automatic mode, trying to upgrade packages after they are downloaded
+ </div><div class="para">
+ IInstall packages after download.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ Any user can download packages, but usually only the root user can install packages. Unless you are logged in as root, rpmfind will likely fail to install the downloaded RPMs.
+ </div><div class="para">
+ Because I select the "a" answer, rpmfind downloads all necessary packages to /tmp and tries to upgrade the packages automatically by running the following command:
+ </div><div class="para">
+ rpm -U /tmp/nmh-1.0.4-9.i386.rpm /tmp/exmh-2.4-2.noarch.rpm
+ </div><div class="para">
+ In this case, the rpm -U command silently fails, since I am not running it as root and do not have permission to install software.
+ </div><div class="para">
+ If the name of a package is unknown, rpmfind also supports searching by keywords. The --apropos pattern option tells rpmfind to search through all package descriptions in the databases for the pattern. If I do not know the names of any e-mail clients, I might use this code for my search:
+ </div><div class="para">
+ $ rpmfind --apropos "mail client"
+ </div><div class="para">
+ Searching the RPM catalog for mail client ...
+ </div><div class="para">
+ 1:
+ </div><div class="para">
+ ftp://ftp.redhat.com/pub/redhat/linux/7.2/en/os/i386/RedHat/RPMS//netscape-communicator-4.78-2.i386.rpm
+ </div><div class="para">
+ netscape-communicator : A Web browser, news reader and e-mail client.
+ </div><div class="para">
+ 2:
+ </div><div class="para">
+ ftp://ftp.redhat.com/pub/redhat/linux/7.2/en/os/i386/RedHat/RPMS//sylpheed-0.5.0-3.i386.rpm
+ </div><div class="para">
+ sylpheed : A GTK+ based, lightweight, and fast email client.
+ </div><div class="para">
+ <snip>
+ </div><div class="para">
+ 364: ftp://ftp.pld.org.pl/PLD-1.0/dists/ra/PLD/SRPMS/SRPMS/sylpheed-0.7.4-1.src.rpm
+ </div><div class="para">
+ sylpheed : GTK+ based fast e-mail client
+ </div><div class="para">
+ From my search, rpmfind returns the following output (with most of the entries edited out for space):
+ </div><div class="para">
+ Found 364 packages related to mail client
+ </div><div class="para">
+ $
+ </div><div class="para">
+ With this command, rpmfind connects to the databases at http://rpmfind.net/ and returns the location of all packages whose description contains the text “mail clientâ€. Notice that 364 packages are found; there are lots of e-mail clients available for Linux! That number, however, is slightly misleading. Some of the packages found are prepared for the distribution I am running (Red Hat Linux version 7.2), but others are not. Result #364, for example, appears to be the Polish(ed) Linux Distribution 1.0 package of sylpheed, the same software offered to me packaged for my Red Hat Linux version 7.2 system in Result #2.
+ </div><div class="para">
+ Warning
+ </div><div class="para">
+ Use caution when working with rpmfind. By default, it connects to the databases on the server http://rpmfind.net/ and queries them. These databases are indexes of all RPM-based distributions, and of all versions of each RPM-based distribution, and of all architectures, and of both source and binary RPMs for all these distributions!
+ </div><div class="para">
+ To help you avoid being overwhelmed with results (such as the 364 results I obtain when I search for “mail clientâ€), options are available to fine-tune rpmfind’s searches in various ways. Common options are presented in Table 8-1.
+ </div><div class="para">
+ Table 8-1SEARCH OPTIONS FOR rpmfind
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Option
+ </div>
+
+ </td><td>
+ <div class="para">
+ Result
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -v
+ </div>
+
+ </td><td>
+ <div class="para">
+ increases verbosity of output (can be used multiple times)
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -s server
+ </div>
+
+ </td><td>
+ <div class="para">
+ connects to a specific rpmfind database server
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --sources package
+ </div>
+
+ </td><td>
+ <div class="para">
+ looks for source RPMs of the package
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --apropos key word(s)
+ </div>
+
+ </td><td>
+ <div class="para">
+ looks by keyword instead of package name
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --dist dist
+ </div>
+
+ </td><td>
+ <div class="para">
+ restricts packages to a specific distribution
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --latest package
+ </div>
+
+ </td><td>
+ <div class="para">
+ finds the most current version of package available
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --upgrade package
+ </div>
+
+ </td><td>
+ <div class="para">
+ finds the most current dependencies available for package
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ The rpmfind databases that rpmfind searches are created using the utility rpm2html. If you desire, rpm2html can be used to set up a local mirror of the databases at rpmfind.net or to make a custom database of locally available RPMs for in-house use.
+ </div><div class="para">
+ rpm2html
+ </div><div class="para">
+ The rpm2html utility generates HTML Web pages that describe RPM packages. Very simple in concept, rpm2html has proven very useful over the years.
+ </div><div class="para">
+ With rpm2html, each package is displayed as a single HTML page that describes the package using information much like that returned by the rpm -qi command, covered in <a class="xref" href="#ch-using-rpm">Cap. 3, <em>Using RPM</em></a> . The HTML page also lists the capabilities the package requires and those it provides. This shows the needed dependency information. Finally, the page includes a download link to download the RPM file.
+ </div><div class="para">
+ All packages of the same name, such as the exmh e-mail client, are collected on summary pages. The summary page tries to list all RPMs for all Linux distributions that provide the given package. For exmh, for example, the database as of this writing includes 71 versions of the exmh package, for Conectiva Linux, Mandrake Linux, Yellow Dog PowerPC Linux, and so on. The summary page also links to the URL in the RPMs that is listed as the home page for the application.
+ </div><div class="para">
+ Used together with its database, rpm2html provides a powerful RPM-centric search engine. You can find more on rpm2html at rpmfind.net/linux/rpm2html/ or just access an RPM search site such as rpmfind.net.
+ </div><div class="para">
+ In addition to rpm2html, the program pdbv creates a set of cross-linked HTML files that list the packages on your system. Pdbv doesn’t support searching and wasn’t built as a front end for search sites, so it is simpler than rpm2html. Instead, pdbv just creates a set of HTML pages that list data that you can query with the rpm command, including the package descriptions, the capabilities required and provided, as well as all the files in the package.
+ </div><div class="para">
+ The primary advantage of pdbv is that it runs relatively quickly to provide you a snapshot of your system.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id869488" class="title">RPM Sites On the Internet</h1></div></div></div><div class="para">
+ In addition to the command-line RPM search tools, a number of Web sites provide handy front ends to databases of available packages. These Web sites make it easy to query for packages and also provide snapshots of what is happening in Linux development, especially with the sites that list recently created RPMs.
+ </div><div class="para">
+ The following sections list some of the more popular sites.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ As with anything on the Internet, sites come and go. I’ve used rpmfind.net for years, but it is always possible that any of these sites may suddenly disappear.
+ </div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id564347" class="title">rpmfind.net</h1></div></div></div><div class="para">
+ The rpmfind utility is associated with an online database available at www.rpmfind.net. You can search this site and see the results in the same format as that created by the rpm2html utility. In essence, this site acts as an HTML front end to the rpmfind query commands. By providing a search engine accessible from a Web browser, instead of the command line as used by the rpmfind utility, the rpmfind.net site is easy to search and also displays the data in an easier-to-read format.
+ </div><div class="para">
+ Use the rpmfind command when you know you want to install something. Use the rpmfind.net Web site when you want to browse through the lists of available RPMs.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ You can download the rpmfind command RPM from the rpmfind.net site.
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id612808" class="title">freshrpms.net</h1></div></div></div><div class="para">
+ The site name,freshrpms.net, is a play on the popular but oddly named Linux site freshmeat.net. The freshmeat.net site provides listings of newly-updated applications for Linux and other operating systems. The freshrpms.net site provides a similar service devoted to freshly-made RPMs.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ You don’t always want the most recently made RPMs. Sometimes it's good to wait a while and see if others have faced problems with a given RPM before downloading it.
+ </div><div class="para">
+ One of the best features of the freshrpms.net site is that it also provides links to the RPM spec files for the packages it references. This is a very useful source of examples when you try to build RPMs.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ See <a class="xref" href="#ch-specfiles">Cap. 9, <em>Working with Spec Files</em></a> for more on RPM spec files.
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id813155" class="title">RPM PBone Search</h1></div></div></div><div class="para">
+ The site http://rpm.pbone.net/ provides a database of RPM packages you can search. This site also lists quite a few recently created RPMs. In fact, much of the focus here lies in finding the latest updates to the applications you run.
+ </div><div class="para">
+ The feature I like most about the PBone search is the ability to specify which Linux distributions to search by using a set of check boxes. Although in theory most Linux RPMs should work on most Linux distributions, I prefer to get something made for and tested on my version of Linux.
+ </div><div class="para">
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id487181" class="title">Other Sites</h1></div></div></div><div class="para">
+ Table 8-2 lists additional sites where you can find RPMs. As with all listings of Internet sites, these may come and go.
+ </div><div class="para">
+ Table 8-2MORE RPM SITES
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Site
+ </div>
+
+ </td><td>
+ <div class="para">
+ Holds
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ http://plf.zarb.org/
+ </div>
+
+ </td><td>
+ <div class="para">
+ The Penguin Liberation Front has RPMs that for legal reasons cannot be included in the Mandrake Linux distribution.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ www.math.unl.edu/~rdieter/Projects/
+ </div>
+
+ </td><td>
+ <div class="para">
+ Rex Dieter’s RPM site
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ www.rpmhelp.net/
+ </div>
+
+ </td><td>
+ <div class="para">
+ Mandrake Linux RPMs
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ www.aucs.org/rpmcenter/
+ </div>
+
+ </td><td>
+ <div class="para">
+ Edwin Chan's Red Hat RPMs
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ www.owlriver.com/projects/links/
+ </div>
+
+ </td><td>
+ <div class="para">
+ Owl River Company RPMs
+ </div>
+
+ </td></tr></tbody></table></div></div></div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id561016" class="title">Graphical RPM Management</h1></div></div></div><div class="para">
+ Once appropriate RPMs have been obtained, they have to be installed before the application they provide can be used. You can use the rpm command-line utility to do this. The rpmfind utility also has the capability to launch the rpm utility automatically to install any software located. In addition to these two tools, however, several graphical applications are available that provide basic RPM package-management capabilities. Most of these programs offer easy-to-use GUIs that can be used to install and uninstall packages, to query packages, and to verify installed packages.
+ </div><div class="para">
+ Even though Linux and Unix fans generally aren’t bothered by command-line tools such as rpm, many newcomers to Linux fret over the seeming difficulty of the command line. They are more used to graphical applications and, in many cases, are more productive in a graphical environment. Keeping with the Linux tradition of freedom of choice, you can use the command-line tools such as the rpm commandor pick from a variety of graphical tools.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id561039" class="title">Nautilus</h1></div></div></div><div class="para">
+ Nautilus provides a visually appealing file manager that is part of the GNOME desktop. Nautilus acts as a normal file manager that can also display some types of files, such as images. In addition, you can launch applications that Nautilus knows about when you double click files. Figure 8-1 shows Nautilus in action.
+ </div><div class="para">
+ Insert 54965-0 fg0801.tif
+ </div><div class="para">
+ Figure 8-1: Browsing RPM files with Nautilus.
+ </div><div class="para">
+ If you double click an RPM file (a file ending with the extension .rpm), Nautilus will install the RPM file. First, though, Nautilus will prompt you for the root password, since you must be logged in as root to install RPMs. Figure 8-2 shows Nautilus prompting for a password.
+ </div><div class="para">
+ Insert 54965-0 fg0802.tif
+ </div><div class="para">
+ Figure 8-2: You must be logged in as root to install packages.
+ </div><div class="para">
+ After some time processing, you should see the Completed System Preparation window, as shown in Figure 8-3.
+ </div><div class="para">
+ Insert 54965-0 fg0803.tif
+ </div><div class="para">
+ Figure 8-3: Installing RPM files with Nautilus.
+ </div><div class="para">
+ When you install RPMs with Nautilus, it really runs the Red Hat Package Management tool.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ Nautilus only supports RPM functionality starting with Red Hat Linux 8.0. This functionality may not be supported in other versions of Linux.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id734494" class="title">Red Hat Package Management</h1></div></div></div><div class="para">
+ The redhat-config-packages application (say that three times fast) comes new with Red Hat Linux 8.0. You can use the Python program in this package to manage the packages that come with Red Hat Linux, using an interface that is very similar to the Red Hat Linux installation program. This similarity may make it easier for many users to manage their packages, although I found the program a bit short on explanations.
+ </div><div class="para">
+ To run this program, you first have to do a bit of searching to find it. It appears under the System Settings menu from the main Red Hat Start menu under the default Bluecurve desktop. Select the Packages choice to launch this program. You can also start the program from the command line with the following command:
+ </div><div class="para">
+ # redhat-config-packages
+ </div><div class="para">
+ This program takes a long time to read in all the information and start up. Once started, the interface provides the same categories and much the same look as the Red Hat Linux installer, as shown in Figure 8-4.
+ </div><div class="para">
+ Insert 54965-0 fg0804.tif
+ </div><div class="para">
+ Figure 8-4: The redhat-config-packages package manager.
+ </div><div class="para">
+ The packages tool divides the packages into groups. Inside each group, the packages are divided into two sets: standard and extra packages. (Red Hat places the packages into these categories, striving to make a reasonable division among the many packages that come with Linux.) If you click the check box for a group, the tool will queue up all the standard packages within that group for installation. If you uncheck a check box for a group that was checked before, the tool will queue up all the installed packages in that group for removal, both standard and extra.
+ </div><div class="para">
+ Warning
+ </div><div class="para">
+ Installing or removing all the packages in a group when you don’t know what is in the group is not a good idea.
+ </div><div class="para">
+ To delve into a group and see what is inside, click the Details link associated with that group. Clicking the Details link will bring up a window where you can check individual packages for installation and uncheck individual packages for removal. Figure 8-5 shows the details of the Web Server group.
+ </div><div class="para">
+ Insert 54965-0 fg0805.tif
+ </div><div class="para">
+ Figure 8-5: Package details for the Web Server group.
+ </div><div class="para">
+ Once you have selected all the packages you want to install, and unselected all the packages you want to remove, click the Update button on the main window of the package-management tool. After some processing, you should see the Completed System Preparation window, which lists the amount of disk space required for the new packages and the amount that will be freed by the packages to be removed. Figure 8-6 shows this window.
+ </div><div class="para">
+ Insert 54965-0 fg0806.tif
+ </div><div class="para">
+ Figure 8-6: The Completed Systems Preparation window.
+ </div><div class="para">
+ Click the Show Details button to see a complete list of all the packages to be installed and removed.
+ </div><div class="para">
+ Warning
+ </div><div class="para">
+ If the packages you choose to install depend on any other packages, the package-management tool will automatically add these packages to the list to be installed. More important, if any packages installed on your system depend on any of the packages you have marked for removal, the tool will add those additional installed packages to the list to be removed. Always examine the Show Details window to see what will really be installed and removed.
+ </div><div class="para">
+ Figure 8-7 shows the window with the package details.
+ </div><div class="para">
+ Insert 54965-0 fg0807.tif
+ </div><div class="para">
+ Figure 8-7: The Show Details window.
+ </div><div class="para">
+ The package-management tool worries me. It has an absolutely beautiful look, but it tries to do too much, especially when removing packages. Always use this program with care. I much prefer to just launch it with single packages from the Nautilus file manager.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id579713" class="title">KPackage</h1></div></div></div><div class="para">
+ One popular graphical RPM management tool is KPackage, supplied with the KDE Desktop. (You can find this product at www.kde.org). KPackage offers basic package-management functionality. It can install and uninstall packages and display information about installed and available packages’ contents and headers. In addition, KPackage supports a wide variety of package formats in addition to RPMs. Be aware, however, that KPackage cannot automatically resolve dependencies. When you are installing new software packages, any dependencies required by that software must first be manually installed.
+ </div><div class="para">
+ When started, KPackage presents a basic two-paned interface.
+ </div><div class="para">
+ The left-hand panel lists Installed packages already on the system, Updated packages available to update the system, New packages available for installation, and All packages (both installed and available for installation/upgrade). When displaying package lists, KPackage organizes the displayed packages into categories based on their group.
+ </div><div class="para">
+ The right-hand panel lists information about the package currently selected in the left-hand panel. Information displayed includes the package Properties, listing the package’s header, and the File List of files that package owns. Figure 8-8 shows this panel on the right side of the interface.
+ </div><div class="para">
+ Note: old fig 8-8 deleted; renumber all remaining to match. Chapter has been changed to reflect deletion.
+ </div><div class="para">
+ Insert 54965-0 fg0808.tif
+ </div><div class="para">
+ Figure 8-8: The KPackage interface, showing properties of the selected package
+ </div><div class="para">
+ After packages have been selected, they can be installed or uninstalled, as shown in Figure 8-9
+ </div><div class="para">
+ Insert 54965-0 fg0809.tif
+ </div><div class="para">
+ Figure 8-9: KPackage installs the selected package on your command.
+ </div><div class="para">
+ In addition to supporting RPM, KPackage can be used on systems that use other packaging methods. Current versions of KPackage support Debian’s dpkg and the BSD projects’ package formats as well as RPM.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id856872" class="title">Gnome-RPM</h1></div></div></div><div class="para">
+ The GNOME Desktop (www.gnome.org) provides another graphical RPM-management tool, Gnome-RPM. Also known as gnorpm, Gnome-RPM is very similar to KPackage in terms of its basic functionality, although Gnome-RPM can manage only RPMs.
+ </div><div class="para">
+ When started, Gnome-RPM presents a hierarchical list of installed packages, arranged by group, as shown in Figure 8-10:
+ </div><div class="para">
+ Insert 54965-0 fg0810.tif
+ </div><div class="para">
+ Figure 8-10: The main Gnome-RPM window.
+ </div><div class="para">
+ After a specific package has been selected, you can can query to see its details, as shown in Figure 8-11:
+ </div><div class="para">
+ Insert 54965-0 fg0811.tif
+ </div><div class="para">
+ Figure 78-11: Querying the details for a package.
+ </div><div class="para">
+ With Gnome-RPM, you can also filter the list of packages to see only the list of uninstalled RPMs, as shown in Figure 8-12.
+ </div><div class="para">
+ Insert 54965-0 fg0812.tif
+ </div><div class="para">
+ Figure 78-12: Filtering to see only the uninstalled packages.
+ </div><div class="para">
+ Like KPackage, when installing new software, Gnome-RPM lacks the ability to automatically install any dependencies needed by that software.
+ </div></div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id503396" class="title">Extending RPM Management</h1></div></div></div><div class="para">
+ RPM makes it very easy to install and uninstall software from systems. One simple command installs an entire application onto the computer, and another removes all files associated with an application. Using RPM to install and uninstall software can become tedious in some situations, however. Manually installing software on one system is no great task, but what if that same software package needs to be installed on all the computers in the department? Or on all the computers in a company? Suddenly, that one rpm -i command has become a major chore!
+ </div><div class="para">
+ Similarly, keeping one system up-to-date with the latest vendor errata, although an extremely important administrative task, is not terribly time-consuming or difficult — simply download all the errata and associated packages from the vendor; then use the command rpm -Fvh to install the packages on the system, freshening all installed software with the latest updates of that software.
+ </div><div class="para">
+ If several machines are being managed, though, the task becomes slightly more difficult. Now the vendor errata and packages must be manually copied to each machine, and rpm -Fvh must be run on each machine to update it. If many machines are being managed, and those systems are running different versions of the operating system (so that they require different errata), the task becomes even more complicated. Separate errata packages must be downloaded for every operating system version in use; then the appropriate errata collections must be pushed to each machine and manually freshened. To make life as a system administrator even more frustrating, sometimes vendor-supplied errata cannot be installed using the freshen option. A package supplied as one RPM in the initial operating-system release might be split into two RPMs for the errata, for example. When this happens, freshen cannot be used. Instead, the administrator must determine what software is currently installed on t
he system, and the errata for that software must be manually installed. Typically, this involves several rounds of comparing output from rpm -qa with the list of current errata, using rpm -Uvh to upgrade only the appropriate errata for that system.
+ </div><div class="para">
+ Worse yet, errata updating should ideally be done on an automatic basis. While rpm commands can be scheduled using system utilities such as cron or at, obviously this cannot be done when the rpm commands to be scheduled need to be interactive.
+ </div><div class="para">
+ Installation of new packages can pose problems as well. New software will often have logical dependencies upon other software that is also not currently installed. Although RPM does track software dependencies, it does not magically find all dependencies an application needs, nor does it automatically install them along with the initial application. Instead, all required “helper†applications must be searched out and manually installed. Then the desired software can be installed.
+ </div><div class="para">
+ These and similar problems are very common in the real world. Typically, system administrators manage as many as 200 or more systems. Manually logging into 200 systems and executing an rpm -i command every time another application is needed is not practical. Even when managing one system, downloading errata and manually installing it regularly quickly becomes tedious.
+ </div><div class="para">
+ Like any regular system-administration task, it should be automated. When installing new software on machines, managing dependencies and downloading and installing required support software becomes tiresome as well.
+ </div><div class="para">
+ To aid with these common problems, a variety of helper applications are available for RPM. These management aids can perform functions such as automatically managing dependencies. When an application is being installed using one of these helpers, the utility also finds and installs any required dependencies. Similarly, when errata are being installed, these management aids can automatically determine which errata are needed by the current system, even in situations in which rpm -F does not work. Some of these tools can even be used to manage clusters of computers. Running one command applies the RPM install or delete on the entire group of machines. All of these commands are designed with scriptability in mind, making them perfect for use automatically via tools such as cron or at.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id554830" class="title">AutoRPM</h1></div></div></div><div class="para">
+ One popular tool to lessen the work involved with administering RPM-based systems is AutoRPM. Written by Kirk Bauer, AutoRPM is available under a free MIT-style license from the home page www.autorpm.org.
+ </div><div class="para">
+ A Perl script, AutoRPM provides several features that make it especially useful. First, it can create local mirrors of RPM repositories. Typically, this feature might be used to create a local archive of errata for a Linux distribution. AutoRPM can also compare all currently installed RPMs against a list stored elsewhere. This list can be either an FTP site or a directory on the local system. After comparing the currently-installed RPMs against the list, AutoRPM can then update any packages from the list site that are newer than what is installed on the local system. This way, you can define one site or directory as the master site of the package versions that need to get installed on all systems and let AutoRPM ensure that all computers on your network are up to date.
+ </div><div class="para">
+ Together, these two functions make AutoRPM very convenient for keeping systems current with all errata the vendor releases. They can also be used to create a method of distributing software to a network of systems. For example, every workstation in the department can run AutoRPM, configured to watch a common directory on a local NFS server. Installing new software on every workstation in the department occurs simply by copying an RPM of the software into that directory, letting AutoRPM do the rest of the work.
+ </div><div class="para">
+ AutoRPM is designed to be used both automatically from cron and interactively from the command line. By default, AutoRPM runs via a nightly cron job and downloads all updates for software currently installed on the system. It then stores these updates in a local directory, typically /var/spool/autorpm, and e-mails an administrator a notification on the new updates. The administrator can then log onto the system and manually install the updates using the rpm command. AutoRPM can also be easily configured to install automatically any new packages it downloads. If AutoRPM is so configured, the system administrator does not even have to log in and run rpm commands to keep the system up-to-date!
+ </div><div class="para">
+ In interactive mode, AutoRPM provides a basic set of commands, listed in Table 8-2.
+ </div><div class="para">
+ Table 8-2Basic AutoRPM commands
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Command
+ </div>
+
+ </td><td>
+ <div class="para">
+ Usage
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ ?
+ </div>
+
+ </td><td>
+ <div class="para">
+ displays help on the various commands
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Help
+ </div>
+
+ </td><td>
+ <div class="para">
+ displays help on the various commands
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Info
+ </div>
+
+ </td><td>
+ <div class="para">
+ displays information about an RPM
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Fullinfo
+ </div>
+
+ </td><td>
+ <div class="para">
+ displays complete information about an RPM
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Install
+ </div>
+
+ </td><td>
+ <div class="para">
+ installs RPMs onto the system
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Add
+ </div>
+
+ </td><td>
+ <div class="para">
+ adds RPMs to the queue of RPMs to be processed
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Remove
+ </div>
+
+ </td><td>
+ <div class="para">
+ deletes RPMs from the queue of RPMs waiting to be processed
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ List
+ </div>
+
+ </td><td>
+ <div class="para">
+ displays all RPMs currently in the queue waiting to be processed
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Cd
+ </div>
+
+ </td><td>
+ <div class="para">
+ changes the local directory
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Auto
+ </div>
+
+ </td><td>
+ <div class="para">
+ executes commands defined in the system-wide configuration file
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Set
+ </div>
+
+ </td><td>
+ <div class="para">
+ displays or modifies current AutoRPM settings
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Abort
+ </div>
+
+ </td><td>
+ <div class="para">
+ exits without saving changes
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Exit
+ </div>
+
+ </td><td>
+ <div class="para">
+ Exits and saves changes
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ The commands that manipulate RPMs (such as install, used to install an RPM) accept as arguments both paths to RPM files on the local system, and also URLs pointing to RPMs on an FTP repository. In addition, they support wild cards and directory accesses, so a command such as install ftp://ftp.redhat.com/pub/redhat/linux/updates/current/* can be used to install all errata for the current release of Red Hat Linux.
+ </div><div class="para">
+ In addition to interactive mode, AutoRPM provides a noninteractive mode, suitable for use through cron. In noninteractive mode, invoked by the command autorpm --notty auto, AutoRPM consults the configuration file /etc/autorpm.conf to decide what to do. By default, /etc/autorpm.d/autorpm.conf is configured to download, but not automatically install, all errata for the release of Red Hat Linux running on the local system. Editing this file makes it possible to use AutoRPM to download all errata — or errata for other Linux distributions — or to install errata automatically once downloaded.
+ </div><div class="para">
+ Typically, AutoRPM is used to automate installation of errata updates and other software on all machines in the enterprise. To do this, one machine is selected to serve as a file server. On it, AutoRPM is configured to download and install all errata. The directory where the errata are stored on that server is then exported to the other machines in the enterprise, which also run AutoRPM. These other machines have AutoRPM configured to install all files that the file server exports. Using a configuration such as this, all machines in the enterprise get all security updates automatically installed. In addition, installing a desired new software application on all hosts in the enterprise can be done simply by copying an RPM of the application onto the file server, making it available for the AutoRPM nightly updates to access and install automatically.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id760680" class="title">AutoUpdate</h1></div></div></div><div class="para">
+ AutoUpdate, written by Gerald Teschl, is another Perl script that can be used to automate RPM downloads or installations. Available freely under the terms of the GNU GPL from www.mat.univie.ac.at/~gerald/ftp/autoupdate, AutoUpdate is very similar to AutoRPM in terms of both functionality and potential applications. Unlike AutoRPM, AutoUpdate offers no interactive capability. However, AutoUpdate does have the capability to manage dependencies correctly; when using AutoUpdate to install software that depends upon other uninstalled software, AutoUpdate attempts to resolve the dependencies and to install all necessary software packages.
+ </div><div class="para">
+ AutoUpdate bases all decisions about what software to download or install upon its configuration file, /etc/autoupdate.d/autoupdate.conf. By default, AutoUpdate provides several additional configuration files pre-defined for downloading updates for the most popular RPM-based Linux distributions (Red Hat Linux, Mandrake Linux, Caldera/SCO OpenLinux, and SUSE Linux). The autoupdate.conf file can be modified to configure AutoUpdate to install software automatically.
+ </div><div class="para">
+ Table 8-3 lists the five commands that compose all the utilities provided by AutoUpdate:
+ </div><div class="para">
+ Table 8-3AutoUpdate commands
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Command
+ </div>
+
+ </td><td>
+ <div class="para">
+ Usage
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ autodld
+ </div>
+
+ </td><td>
+ <div class="para">
+ downloads updated versions of all installed software
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ autoget
+ </div>
+
+ </td><td>
+ <div class="para">
+ downloads specific RPMs from remote sites
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ autoupd
+ </div>
+
+ </td><td>
+ <div class="para">
+ installs more recent versions of currently installed software
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ autoins
+ </div>
+
+ </td><td>
+ <div class="para">
+ installs specific applications
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ automerge
+ </div>
+
+ </td><td>
+ <div class="para">
+ merges new RPMs into an existing directory of RPMs, removing any old versions
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ autopurge
+ </div>
+
+ </td><td>
+ <div class="para">
+ removes old RPMs from an existing directory of RPMs.
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ These tools can access remote files by using a variety of methods. Like AutoRPM, AutoUptodate can download files if given an FTP URL. AutoUpdate can also access HTTP URLs and local files. Its additional dependency-tracking functionality and support for additional file-access methods make it suitable for use in cases where AutoRPM might be inappropriate. AutoUpdate cannot be used interactively, however, making AutoRPM more useful for nonautomated purposes.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id715873" class="title">The Red Hat Network and up2date</h1></div></div></div><div class="para">
+ Some vendors of RPM-based Linux distributions also provide utilities that can help with management of the distributions they create. Red Hat has created two complementary products, the Red Hat Network (RHN) and up2date, which together provide much the same functionality for managing Red Hat Linux installations as tools such as AutoUpdate and AutoRPM, as well as offering more advanced features.
+ </div><div class="para">
+ Red Hat Network is a subscription-based service offered by Red Hat Red Hat Network makes software available for installation via the network. (A free evaluation is also available.) After registering machines with Red Hat Network, administrators can pull updates or new software for installation to those registered machines. In addition, administrators have access to a Web-based administrative console from which they can view the systems they manage and can push software out to those systems.
+ </div><div class="para">
+ Red Hat offers two tiers of access to Red Hat Network. Basic Service subscriptions to Red Hat Network provide the ability to manage single systems. Multiple machines can be subscribed by the same administrator for Basic Service level Red Hat Network access, but they must all be managed independently. The administrator must push out errata to each machine separately. Workgroup Service subscriptions provide the same functionality as Basic Service subscriptions, but they also provide the ability to group multiple machines for simultaneous administration. All errata updates for all machines subscribed to Workgroup Service can be pushed out by a single action, for example. Furthermore, Workgroup Service subscriptions can allow management by multiple administrators if desired, making it possible for large organizations to share responsibilities among administrators.
+ </div><div class="para">
+ When using Red Hat Network to manage machines with Workgroup Service subscriptions, Red Hat also offers two optional services: Red Hat Network Proxy Server and Red Hat Network Satellite. The Red Hat Network Proxy Server is, as its name suggests, a proxy server for the Red Hat Network. Using it, errata pushed out via Red Hat Network is downloaded by the organization (only once) to a central server in-house. All machines in that organization subscribed to Red Hat Network get their updated software from that in-house proxy server, significantly reducing the network bandwidth requirements needed to keep large organizations up to date.
+ </div><div class="para">
+ In addition, the Red Hat Network Proxy Server can be used to provide all subscribed machines with software not provided with Red Hat Linux. Custom “channels†of supplemental software can be created on the Proxy Server, and machines can be subscribed to those channels as desired. Using this feature, different departments in the organization with different software needs can create independent channels for each department, ensuring that machines get only the software needed on them. Similarly, distinct channels can be created for separate classes of machines, ensuring that servers get only software appropriate for server machines and that desktops only get only software that desktop machines need.
+ </div><div class="para">
+ The Red Hat Network is normally centrally administered through Red Hat. Machines subscribed to the Red Hat Network have a system profile on file with Red Hat that details the system’s essential configuration information (what software is installed on it, what CPU architecture it contains, and so forth) needed to determine which software errata are appropriate for that system. Similarly, the Web console through which machines subscribed to Red Hat Network can be administered is also located on a Red Hat server. Customers wishing to use Red Hat Network services, but not wanting the dependency upon Internet access to Red Hat, can create an in-house Red Hat Network by using the Red Hat Network Satellite. This solution is often practical for customers who need to keep system information confidential or for customers whose systems are not able to access the Internet.
+ </div><div class="para">
+ Red Hat provides several interfaces for administering machines subscribed to the Red Hat Network. A Web-management console is available at https://rhn.redhat.com/. Administrators of machines subscribed to any level of the Red Hat Network can simply log into this Web site and perform a variety of package-management operations from their Web browsers. In addition to viewing other things, administrators can see what software is currently installed, select and install Red Hat Linux errata or new software, or schedule a time for automatic installation of Red Hat Linux errata.
+ </div><div class="para">
+ When using Red Hat Network, rhnsd is a client-side daemon that should be run on subscribed systems. It periodically launches a helper utility, rhn_check, which connects to the Red Hat Network servers and checks for any actions (such as a scheduled installation of errata) that an administrator has selected in the Web console. If any actions have been scheduled for that client machine, rhn_check on the client initiates those actions. By default, rhnsd runs rhn_check every two hours. This time can be increased to check for configuration changes as frequently as every hour if necessary.
+ </div><div class="para">
+ In addition, Red Hat provides client-side tools that can be used in a more interactive fashion to connect to the Red Hat Network from subscribed systems. The up2date program provides a graphical and command-line tool that can be used to install packages from Red Hat Network servers. When installing a new package, up2date automatically installs any necessary dependencies the package requires, making it a very convenient tool for adding software to the system. up2date can also be run in update mode, thus telling it to install all updates available for the software already installed on the system. Commonly used options with up2date include those listed in Table 8-4.
+ </div><div class="para">
+ Table 8-4Options for the up2date command
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Option
+ </div>
+
+ </td><td>
+ <div class="para">
+ Usage
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --configure
+ </div>
+
+ </td><td>
+ <div class="para">
+ Start a dialog for configuring up2date options
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -d
+ </div>
+
+ </td><td>
+ <div class="para">
+ Download packages but do not install them
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -f
+ </div>
+
+ </td><td>
+ <div class="para">
+ Force packages to be installed, even if they have been marked to be skipped
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -i
+ </div>
+
+ </td><td>
+ <div class="para">
+ Download and install packages
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -l
+ </div>
+
+ </td><td>
+ <div class="para">
+ List available updated versions of already installed packages
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --showall
+ </div>
+
+ </td><td>
+ <div class="para">
+ List all available packages, including packages not currently installed at all
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -k
+ </div>
+
+ </td><td>
+ <div class="para">
+ List local directories containing packages
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nosig
+ </div>
+
+ </td><td>
+ <div class="para">
+ Disable GPG package signature checking
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --src
+ </div>
+
+ </td><td>
+ <div class="para">
+ Download both source and binary RPMs
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nosrc
+ </div>
+
+ </td><td>
+ <div class="para">
+ Do not download source RPMs
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -p
+ </div>
+
+ </td><td>
+ <div class="para">
+ Update the list of installed packages associated with this computer in the Red Hat Network database
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --whatprovides
+ </div>
+
+ </td><td>
+ <div class="para">
+ Ask the RHN servers which packages will resolve the listed dependencies
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --solvedeps
+ </div>
+
+ </td><td>
+ <div class="para">
+ Ask the RHN servers which packages will resolve the listed dependencies, then downloads and installs those packages
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --tmpdir
+ </div>
+
+ </td><td>
+ <div class="para">
+ Specify the temporary directory to which packages should be downloaded
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -u
+ </div>
+
+ </td><td>
+ <div class="para">
+ Update all software currently installed on the system to the latest available version
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nox
+ </div>
+
+ </td><td>
+ <div class="para">
+ Short for No X, this disables the X-based GUI, instead using only the command-line interface
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -v
+ </div>
+
+ </td><td>
+ <div class="para">
+ Provide more verbose output
+ </div>
+
+ </td></tr></tbody></table></div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id750620" class="title">Current</h1></div></div></div><div class="para">
+ The up2date command, the Red Hat Network client software, is open-source software released by Red Hat under the terms of the GNU GPL. Red Hat Network Proxy Server and Red Hat Network Satellite, the server applications with which up2date interacts, are not freely available, open-source applications. For this reason, an effort is underway to develop servers available under the terms of the GNU GPL that can be used with up2date clients. The main program in this effort is called current, which refers to keeping your systems current.
+ </div><div class="para">
+ The current server can be downloaded from http://current.tigris.org. Although not yet as functional as Red Hat Network Proxy Server or Red Hat Network Satellite, current can already be used to create a RPM repository from which up2date-using clients can retrieve and install software. More advanced features, such as support for multiple “channels†of software, will be added to current in future releases.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id750644" class="title">urpmi and RpmDrake</h1></div></div></div><div class="para">
+ Mandrake provides a set of software similar to the combination of up2date and Red Hat Network or current that can be used with the Mandrake Linux distribution. Links to the source code for the Mandrake applications can be found at www.linux-mandrake.com/cooker/urpmi.html. This suite of applications is typically referred to as urpmi and includes both the urpmi command and several helper applications. urpmi itself is a command that acts as a wrapper around the rpm command. When given the name of a package to install, urpmi determines what dependencies, if any, required by the application are not already resolved and offers to install the packages necessary to fulfill those dependencies.
+ </div><div class="para">
+ When installing packages, urpmi can install from a variety of sources: FTP repositories, Web servers, local or NFS directories, and removable media such as CD-ROMs. The helper application urpmi.addmedia is used to add package sources, and the corresponding utility urpmi.removemedia is used to remove package sources no longer desired.
+ </div><div class="para">
+ Mandrake’s urpmi program includes one very handy feature. It comes with an autoirpm helper utility that can be used to configure the system to install packages on demand. This is done by running the command autoirpm.update-all, an application that scans all packages available for installation via urpmi. For every package available through urpmi, autoirpm.update-all determines what executable programs it provides, and it creates a symbolic link from that executable’s name to the autoirpm script. Attempting to execute such a symbolic link executes autoirpm, which in turn automatically uses urpmi to install the associated package. The result: on-demand installation of packages when users on the system attempt to execute the programs that those packages provide.
+ </div><div class="para">
+ Two different interfaces are available for urpmi. The urpmi command starts up urpmi in command-line mode, and the gurpmi command (or urpmi --X) starts urpmi in a graphical X-based mode. In addition, Mandrake provides a more full-featured graphical application: RpmDrake. RpmDrake provides the same package-management capabilities as urpmi, including the capability to install all required dependencies whenever installing any new packages.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id697201" class="title">apt-rpm</h1></div></div></div><div class="para">
+ Another free RPM management utility is available that provides many of the features of both vendor solutions such as up2date or urpmi and of third-party utilities such as autoUpdate or KPackage. This tool is apt-rpm, a port of the Debian Project’s excellent apt (Advanced Package Tool) software.
+ </div><div class="para">
+ The Debian Project (www.debian.org/) is a nonprofit volunteer group that develops a Linux distribution, Debian GNU/Linux. The group uses a different package format, dpkg, which was developed independently of and simultaneous to Red Hat’s creation of RPM. The two formats, dpkg and RPM, are very similar in terms of utility and functionality. In addition to having created a package format, the Debian Project later developed a collection of software, apt, which could be used to manage and install dpkg-format software. And, since Debian distributions are typically installed over the Internet, this apt software has to supply advanced distributed package management functionality.
+ </div><div class="para">
+ In many respects, Debian’s implementation of apt is very similar to the functionality provided by Red Hat’s up2date/Red Hat Network products or Mandrake’s urpmi software. On Debian systems, apt is a client tool used to select and install new software packages or to update existing packages already installed on the system. To do this, it accesses a user-configured list of resources that supply new packages; these resources are typically the Debian Project’s FTP or Web servers, though they can also be CD-ROMs or local or remote file systems. For apt to be able to download packages from a resource such as a CD-ROM or an FTP server, that resource must supply two things: the software packages being downloaded and a database supplying metadata about all the packages in the repository. These resource databases are essential for apt to operate. For this reason, apt can only be used to update systems from apt-capable repositories.
+ </div><div class="para">
+ Although apt was created by the Debian Project and designed for dpkg-format software packages, nothing about apt requires that it inherently be usable only with dpkg-format packages. Because of this, and because of its powerful capabilities, Conectiva, a Brazilian Linux distribution vendor (www.conectiva.com), extended apt to support management of RPM packages in addition to dpkg packages. Conectiva’s work, commonly referred to as apt-rpm, makes the apt client software available for use on any RPM-based Linux distribution. Conectiva also provides its customers with access to apt-capable FTP servers. A related project, apt4rpm (http://apt4rpm.sourceforge.net/), supplies the necessary utilities that can be used to make any RPM repository apt-capable. By creating apt-capable servers using apt4rpm and then installing apt-rpm on the client systems, any RPM-based distribution, such as Red Hat Linux, Mandrake Linux, Caldera/SCO OpenLinux, or SUSE Linux, can then be easily manag
ed using apt.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ The freshrpms.net site, mentioned previously, provides a touted apt repository.
+ </div><div class="para">
+ Administrators managing multiple dispersed machines as well as those used to Debian administration often find it useful to configure their machines to use apt; its dependency tracking is far better than any other tool, except for Red Hat’s up2date/RHN combination. To use apt, administrators must install it on their machines and have access to an apt-capable RPM repository for the distribution they use. Several public FTP sites that support apt are now available for most of the major RPM-based distributions. Also, the administrator can create another apt-capable repository.
+ </div><div class="para">
+ Configuration of machines to use apt is simple. The apt and libapt RPMs simply need to be installed. Although binaries are sometimes available, the best success can usually be obtained by building binary RPMs from the latest Conectiva apt SRPM (source RPM), available at ftp://ftp.conectiva.com/pub/conectiva/EXPERIMENTAL/apt/.
+ </div><div class="para">
+ Once apt and libapt RPMs are installed, the sources.list file in /etc/apt needs to be modified to reference the apt-capable software site that will be used. For example, to configure a machine to access the apt-capable Red Hat Linux 7.2 software distributed by the Tuxfamily.org server, the /etc/apt/sources.list file needs to list:
+ </div><div class="para">
+ rpm http://apt-rpm.tuxfamily.org/apt redhat-7.2-i386/redhat os
+ </div><div class="para">
+ rpm http://apt-rpm.tuxfamily.org/apt redhat-updates-7.2/redhat os
+ </div><div class="para">
+ These two lines, respectively, access the Red Hat Linux 7.2 and Red Hat Linux 7.2 errata RPMs being served by the system apt-rpm.tuxfamily.org. If you also want access to source RPMs, the following lines are necessary as well.
+ </div><div class="para">
+ rpm-src http://apt-rpm.tuxfamily.org/apt redhat-7.2-i386/redhat os
+ </div><div class="para">
+ rpm-src http://apt-rpm.tuxfamily.org/apt redhat-updates-7.2/redhat os
+ </div><div class="para">
+ In addition to, or instead of, using public apt-capable servers, many sites want to create their own apt servers. If apt is being used to manage all the machines in the enterprise, a custom apt server might be needed that contains apt-accessible RPMs of all the custom software used in the enterprise. This can be done using the tools provided by the apt4rpm package (http://apt4rpm.sourceforge.net).
+ </div><div class="para">
+ Once apt has been installed on clients, and the clients have been configured to access an apt-capable server, keeping systems updated is simple. The command apt-get update updates the client system’s apt database of available software, after which the command apt-get upgrade upgrades all currently installed software to the latest version available in the software repository. By listing a site that provides vendor errata updates in /etc/apt/sources.list and then setting up a nightly cron job to run the apt-get upgrade command, administrators can be sure that client systems always have the latest errata installed. You can use a similar technique to ensure that all client systems are always up to date with the latest custom in-house applications. To do this, set up your own apt server and ensure that the latest custom applications are placed on the apt server.
+ </div><div class="para">
+ In addition, apt simplifies interactive installation of RPMs on systems that are using it. The command apt-get install package retrieves the named RPM from the apt-capable software repository and installs it. If the package requires any dependencies that are not already resolved, apt will ask for confirmation, then download and install the package and all dependencies. Similarly, apt-get remove package uninstalls the named RPM. If any other packages depend on it, it will prompt for confirmation, then uninstall the named RPM and all of its dependencies.
+ </div><div class="para">
+ In addition to these command-line utilities, several graphical front-end tools for manipulating apt are currently being ported for use with apt-rpm. Because of its ease of use for automating installation of system errata and necessary custom software, and because of the excellent dependency tracking it provides for interactive installation and uninstallation of software, apt-rpm can be excellent for managing RPM-based systems.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id559117" class="title">The poldek</h1></div></div></div><div class="para">
+ Also similar to the Debian apt tool, a utility called the poldek works like apt-get. The poldek was designed to quickly scan through dependencies and install a number of packages at once. You can specify all the packages to install in a file.
+ </div><div class="para">
+ The poldek automatically downloads any needed dependencies. The poldek can download files over the Internet and also help create the packages for storage on CD-ROMs. The poldek optimizes the set of packages to reduce the number of times users have to switch CDs.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ For more on the poldek, see poldek.pld.org.pl.
+ </div></div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id591000" class="title">Summary</h1></div></div></div><div class="para">
+ This chapter has covered a number of tools for finding packages in RPM format, as well as tools to help manage the RPMs on your system. The rpm command does a great job of installing, removing, and upgrading packages. You can use it or choose from one of the many graphical RPM management tools shown in this chapter.
+ </div><div class="para">
+ The rpmfind utility helps find RPM packages on Internet servers. You can use rpmfind to find the latest version of the packages installed on your system.
+ </div><div class="para">
+ The Nautilus file manager allows you to browse files on disk, and it installs any RPM files you double-click.
+ </div><div class="para">
+ Red Hat Linux 8 comes with a new package-management tool available from the System Settings menu. Be careful with this tool, though, as it automatically installs--and removes--dependent packages.
+ </div><div class="para">
+ AutoRPM and AutoUpdate provide utilites that you can run periodically to ensure that your systems are up to date. The Red Hat Network and up2date also provides this capability.
+ </div><div class="para">
+ The Debian GNU/Linux apt system provides many of the same capabilities as RPM, along with the network-updating capabilities of up2date and the Red Hat Network. You can use special apt packages that adapt apt for RPM-based Linux distributions and get the best of both the RPM system and the apt system.
+ </div><div class="para">
+ The next chapter starts the major section on creating RPMs. The RPM system reduces a lot of the burden of administering Linux systems. You can take advantage of this when building any sort of software for distribution--or even when managing your own system.
+ </div></div></div><div xml:lang="ro" class="chapter" id="ch-creating-rpms" lang="ro"><div class="titlepage"><div><div><h2 class="title">Cap. 8. Creating RPMs: An Overview</h2></div></div></div><div class="toc"><dl><dt><span class="sect1"><a href="#id819374">8.1. Preparing to Build RPMs</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id863998">8.1.1. Planning what you want to build</a></span></dt><dt><span class="sect2"><a href="#id599111">8.1.2. Gathering the software to package</a></span></dt><dt><span class="sect2"><a href="#id600670">8.1.3. Creating a reproducible build of the software</a></span></dt><dt><span class="sect2"><a href="#id592939">8.1.4. Planning for Upgrades</a></span></dt><dt><span class="sect2"><a href="#id633627">8.1.5. Outlining Any Dependencies</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id784426">8.2. Building RPMs</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id934340">8.2.1. Setting up the directory structure</a></
span></dt><dt><span class="sect2"><a href="#id563449">8.2.2. Placing your sources into the directory structure</a></span></dt><dt><span class="sect2"><a href="#id789919">8.2.3. Creating the spec file</a></span></dt><dt><span class="sect2"><a href="#id727163">8.2.4. Building RPMs with the rpmbuild command</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id761902">8.3. Verifying Your RPMS</a></span></dt><dt><span class="sect1"><a href="#id969647">8.4. Summary</a></span></dt></dl></div><div class="para">
+ This chapter covers:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Preparing to build RPMs
+ </div></li><li class="listitem"><div class="para">
+ Planning for RPMs
+ </div></li><li class="listitem"><div class="para">
+ Explaining the build process
+ </div></li><li class="listitem"><div class="para">
+ Using build files
+ </div></li><li class="listitem"><div class="para">
+ Seeing the results
+ </div></li><li class="listitem"><div class="para">
+ Verifying your RPMs
+ </div></li></ul></div><div class="para">
+ Thus far in this book, all the commands presented have been used to manage or query packages. With this chapter, though, you start creating RPMs of your own. Even if you do not produce applications on your own, you may want to create RPM packages out of software you use, if only for the ease of management that the RPM system provides.
+ </div><div class="para">
+ Creating RPMs allows you to create a consistent set of applications for use on all systems in your organization and easily manage those applications. You may create RPMs of applications developed in house or RPMs of applications developed elsewhere that you need to customize for your environment. Making RPMs of the customized applications reduces work and makes the customizations consistent.
+ </div><div class="para">
+ This chapter introduces the RPM system from the point of view of creating RPMs and demonstrates the steps and planning necessary to make your own packages. As such, this chapter introduces the RPM-building topics covered in depth in the remaining chapters in this part.
+ </div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id819374" class="title">Preparing to Build RPMs</h1></div></div></div><div class="para">
+ The RPM-building task starts with gathering all the material you want to bundle into an RPM package and then defining the RPM directives to make your package. The final steps are to build and test an RPM. This sounds easy, and for the most part it is fairly straightforward.
+ </div><div class="para">
+ The main problems arise when you try to define the many RPM directives for your package. In addition, some of the elements in an RPM can be complex, such as upgrade scripts.
+ </div><div class="para">
+ The main tasks in building RPMs are:
+ </div><div class="para">
+ 1.Planning what you want to build
+ </div><div class="para">
+ 2.Gathering the software to package
+ </div><div class="para">
+ 3.Patching the software as needed
+ </div><div class="para">
+ 4.Creating a reproducible build of the software
+ </div><div class="para">
+ 5.Planning for upgrades
+ </div><div class="para">
+ 6.Outlining any dependencies
+ </div><div class="para">
+ 7.Building the RPMs
+ </div><div class="para">
+ 8.Testing the RPMs
+ </div><div class="para">
+ The sections in this chapter cover the initial planning stages and provide an overview of the process of building RPMs. The remaining chapters in Part II go in depth into the process of building RPMs.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id863998" class="title">Planning what you want to build</h1></div></div></div><div class="para">
+ The first step in the entire RPM-building process is simply to decide exactly what you want to make into an RPM. Is this an application, a programming library, a set of system configuration files, or a documentation package? If this is an application, is it customized or patched? Think these issues over and decide what you want to package as an RPM.
+ </div><div class="para">
+ In most cases, you want to create both a source package and a binary package containing the built sources. You need a binary package because that holds the RPM you want to install on other systems. You need the source package so you can recreate the binary package at any time. And, if the sources get updated, you can quickly make a new binary RPM from the updated sources if you have already defined a source RPM.
+ </div><div class="para">
+ Most packages start with a source RPM, although you have the option to skip making a source RPM. It is a good idea to make the source RPM, however, because it makes it easier to reproduce the final binary RPM. Once of the key goals of the RPM system is to allow for reproducible builds, and making source RPMs is just one step to help towards this goal.
+ </div><div class="para">
+ Creating a source RPM also allows you to transfer the entire set of sources for a package to another system, since the source RPM is just one file and it contains all the program sources along with the instructions, called a spec file, for building the binary RPM. Furthermore, creating a source RPM makes it easier to create binary RPMs on different processor architectures or different versions of Linux.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ Not all programs are portable to multiple-processor architectures. But many Linux programs can simply be recompiled on another architecture to make a binary program for that architecture. That's because there are a lot of common APIs for Linux applications and because most programs are not processor dependent. This is not true of all programs, so your mileage may vary.
+ </div><div class="para">
+ Source packages are not that hard to make, and they provide a single package, and single file, that holds all the sources necessary to build your binary package. In addition, once you have a source RPM, it is very easy to build a binary RPM.
+ </div><div class="para">
+ Binary packages are likely the real reason you want to make an RPM. You can package an application, a programming library, or almost anything you want. Armed with a binary RPM, you can transfer one file to another machine and install the application there, taking full advantage of the RPM system.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id599111" class="title">Gathering the software to package</h1></div></div></div><div class="para">
+ Whether you are writing your own software or merely packaging software found elsewhere, the next step is to gather the software you want to bundle into an RPM. This includes the applications or libraries you want to package, as well as the program source code.
+ </div><div class="para">
+ In general, you’ll be doing one of three things:
+ </div><div class="para">
+ *Packaging your own software
+ </div><div class="para">
+ *Packaging someone else’s software
+ </div><div class="para">
+ *Packaging someone else’s stuff after first customizing or patching the software
+ </div><div class="para">
+ In all cases, you need to gather the software together and decide whether you want everything to go into one bundle or a number of bundles.
+ </div><div class="para">
+ As covered in <a class="xref" href="#ch-intro-rpm">Cap. 1, <em>Introduction to RPM</em></a> , a major tenet of the philosophy behind RPM is to start with pristine—unmodified--sources. You may need to patch or customize the sources for your environment, but you can always go back to the original sources.
+ </div><div class="para">
+ Starting with pristine sources provides a number of advantages, including the following:
+ </div><div class="para">
+ *You clearly separate any changes you have made to the software from the original software.
+ </div><div class="para">
+ *You make it easier to get an upgrade of the original sources, since your changes are cleanly separated from the original sources. With each new release of the software, you can determine which of your changes, if any, are still needed. This is especially important if you are packaging an application created by another organization into an RPM.
+ </div><div class="para">
+ *You have a reproducible way to recreate everything in the package. Since you start with unmodified sources, you can always go back to the beginning of the process and start again. Thus, your RPMs don’t depend on any actions taken beforehand, such as patching, that you may later forget to do because the steps are not automated as part of the RPM-building process.
+ </div><div class="para">
+ Start with pristine sources; then patch as needed. A patch is an automated set of modifications to the source code. Use the diff command to build a patch and the patch command to apply the patch (that is, to modify the source code). Keep the original sources separate from any patches you need to make the software work in your environment.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ See the online manual pages for the patch and diff commands for more information on how to create and apply a patch.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id600670" class="title">Creating a reproducible build of the software</h1></div></div></div><div class="para">
+ The RPM system will automate the steps to create an application, as long as you configure the RPM with the proper steps, such as which make targets to run. Unfortunately, configuring the proper steps is not always easy. So before trying to make an RPM, you need to figure out how to build the application or library you plan to package into an RPM. Once you have figured out how to build the application or library, you can set up a reproducible build. The RPM system can then automate this build.
+ </div><div class="para">
+ To build the software, you’ll need to use a variety of Linux tools. The specific tools you need depend largely on where the original software came from. The following sections outline some of the more common techniques for preparing and building Linux software.
+ </div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id438489" class="title">Unpacking Software</h1></div></div></div><div class="para">
+ Many applications are downloaded in compressed tar format, often called a tarball. A tarball is merely an archive file built by the tar command that has been compressed, usually using the gzip command.
+ </div><div class="para">
+ In most cases, these files have a name such as the following:
+ </div><div class="para">
+ filename.tar.gz
+ </div><div class="para">
+ filename.tgz
+ </div><div class="para">
+ filename.tar.Z
+ </div><div class="para">
+ For the first two cases, use the gunzip command to unzip the file; then use the tar command to extract the file, for example:
+ </div><div class="para">
+ $ gunzip filename.tgz
+ </div><div class="para">
+ $ tar xf filename.tar
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ In the case of a file name ending in .Z, use the uncompress program instead of gunzip.
+ </div><div class="para">
+ Once you have unpacked the sources, start looking around at the files.
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id599539" class="title">Reading the README</h1></div></div></div><div class="para">
+ Many applications come with a very handy file named README, or something similar, such as README.txt. As the name implies, you should read this file. The README file answers some of the most common questions about a particular application.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ You really should read any file named README or any variant of README.
+ </div><div class="para">
+ Other useful files include those named INSTALL or some close variant. Read these files, too. Usually, the README or the INSTALL file will tell you what you need to do to build the software.
+ </div><div class="para">
+ Once you have extracted the source code files and read all the available documentation, the next step is to build, usually compile, the application or library.
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id634401" class="title">Building Programs with Linux Build Tools</h1></div></div></div><div class="para">
+ Most applications or libraries need to be built into executable programs or compiled archived libraries. This process of building can be as simple as just compiling, but is usually more involved. Most Linux applications and libraries use a build tool called make to manage the building of the source code and creation of the executable programs. The make command uses a file, normally named Makefile, that contains the rules for building the software. You will usually find a Makefile in each directory in the source code
+ </div><div class="para">
+ Each Makefile contains a set of targets that define things that make can build. Each target defines the commands to run to build a particular thing (make targets are purely arbitrary, although some conventions are usually followed). Some combination of the targets results in a built application. The make program runs the targets that you specify on the command line, or the Makefile rules indicate it needs to run based on the targets you specify on the command line.
+ </div><div class="para">
+ You need to tell make the target to build the application or library you want to package into an RPM. Each target is defined within the Makefile. The conventional make targets to build and install a program are:
+ </div><div class="para">
+ make
+ </div><div class="para">
+ make install
+ </div><div class="para">
+ When you call the make command without the name of a target, make builds the default target, named all. This target usually compiles the program or library. The install target should install the program.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ The names of these make targets are conventions shared by many but not all programs. Other common targets include clean, which should clean up any files built.
+ </div><div class="para">
+ </div><div class="para">
+ The commands in the Makefile may be specific to a given system. For example, the traditional command for compiling C programs is cc, short for C Compiler. You may have the gcc command (GNU C Compiler) instead. The options passed to the C compiler may differ depending on the architecture of the system. Other commands may exist but be located in different locations. SUSE Linux, for example, puts a lot of programs in /opt.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ These system-dependent issues mostly apply to various versions of Unix. Most modern Linux systems are fairly similar. Because many packages, such as sendmail, have a long UNIX history, you’ll find all sorts of complications in the Makefiles or many Makefiles provided with many applications. If we could just convince everyone to give up all non-Linux operating systems, this task would be much simpler.
+ </div><div class="para">
+ Because the Makefiles are platform specific, a number of tools have been developed to create the proper Makefile, usually by running a program that knows about your system's architecture. The simplest of these tools is the manual approach. You may download a program and find files such as Makefile.amiga, Makefile.solaris, and Makefile.linux. You need to copy the file for your system architecture to the name Makefile.
+ </div><div class="para">
+ The following sections discuss other tools for creating Makefiles.
+ </div><div class="para">
+ </div><div class="sect4"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id800683" class="title">imake</h1></div></div></div><div class="para">
+ A program called imake is used mostly for X Window graphical applications, and typically older X Window applications. The imake command uses a file named Imakefile that contains rules used to build a platform-specific Makefile. This allows X Window applications, which run on many architectures and operating systems, to come with fairly generic build scripts.
+ </div><div class="para">
+ When you see an Imakefile, use the following general set of commands to compileand install an application:
+ </div><div class="para">
+ $ xmkmf
+ </div><div class="para">
+ $ make
+ </div><div class="para">
+ $ make install
+ </div><div class="para">
+ These commands work for most X Window applications. The xmkmf command is a script that runs the imake command to create a Makefile. If the xmkmf command is not available or if this command does not work, you may need to run a command such as the following:
+ </div><div class="para">
+ make Makefile
+ </div><div class="para">
+ Or, if there are multiple directories of source code, try the following command:
+ </div><div class="para">
+ make Makefiles
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ For more on imake, see www.dubois.ws/software/imake-stuff/.
+ </div></div><div class="sect4"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id777870" class="title">The configure script</h1></div></div></div><div class="para">
+ Most Linux programs, especially server-side or command-line programs, use a script called configure. The configure script outputs a platform-specific Makefile.
+ </div><div class="para">
+ If you see a script named configure in the source files, try the following commands to build and install the program:
+ </div><div class="para">
+ $ ./configure
+ </div><div class="para">
+ $ make
+ </div><div class="para">
+ $ make install
+ </div><div class="para">
+ The ./configure command runs the script in the local directory, which outputs a Makefile configured for your system. The make command builds the program and the make install command installs the program.
+ </div><div class="para">
+ The configure script is created by a set of tools including automake and autoconf, which use generic files usually named configure.in and makefile.am, among other files, to create the generic configure script.
+ </div><div class="para">
+ In many cases, you’ll need to pass parameters to the configure script. One of the most common parameters is --prefix, which tells the configure script the name of the starting directory from which to base all other paths. This is the root directory for building the application.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ For more on the configure system, autoconf, and automake, see www.airs.com/ian/configure/.
+ </div></div><div class="sect4"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id898763" class="title">Building Perl modules</h1></div></div></div><div class="para">
+ Perl is a scripting language used heavily on Linux systems, especially by administrators. Most Perl modules and packages use the following set of commands to create a system-specific Makefile and to build the module:
+ </div><div class="para">
+ $ perl Makefile.PL
+ </div><div class="para">
+ $ make
+ </div><div class="para">
+ $ make test
+ </div><div class="para">
+ $ make install
+ </div><div class="para">
+ If you see a file named Makefile.PL, chances are these are the commands to run to build the application or module.
+ </div><div class="para">
+ The goal of all these steps is to figure out how to make a reproducible build of the application or library you want to package in RPM format. Once you have a build, the next step is to plan for upgrades.
+ </div></div></div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id592939" class="title">Planning for Upgrades</h1></div></div></div><div class="para">
+ Any application or library you package in RPM format is likely to get upgraded sometime. When this happens, you’ll need to make a new RPM. This new RPM must handle not only installing the package, but also handling any upgrade issues. You need to think about the following issues:
+ </div><div class="para">
+ *How to install the RPM for the new version of the software. Are there any necessary install scripts?
+ </div><div class="para">
+ *How to remove the previous RPM package. If your package has an install script, then you may need an uninstall script to cleanly remove any changes made to the system by the install script. The RPM system handles the removal of the files in the package. You need to handle the task of undoing any changes made to the system during installation.
+ </div><div class="para">
+ At this point in time, the main effort is to keep these issues in mind and plan ahead, since these issues will come up with any upgrade.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id633627" class="title">Outlining Any Dependencies</h1></div></div></div><div class="para">
+ Often, the hardest task is getting make to build a program properly. One potential problem is assuring that all the dependencies are included. As you work with make, keep track of any other libraries that the program you are trying to build requires. These libraries will become dependencies when you get to the stage of making the RPM.
+ </div><div class="para">
+ In most cases you do not want to include the dependencies in your RPM. Instead, each dependency should have its own RPM for each necessary library. In many cases, you should be able to find RPMs for these dependencies. Keep track of the packages that provide the dependencies.
+ </div><div class="para">
+ After you have built the application, planned for upgrades and outlined dependencies, you can make an RPM.
+ </div></div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id784426" class="title">Building RPMs</h1></div></div></div><div class="para">
+ In previous chapters, just about everything you want to do with RPMs is accomplished with the rpm command. Building RPMs is one exception. Just about everything you want to do to build an RPM is done by the rpmbuild command, often with a single command.
+ </div><div class="para">
+ Warning
+ </div><div class="para">
+ Older RPM manuals refer to using the –b option to the rpm command to create RPMs. Don’t use that option. Instead, always use the rpmbuild command. The reason for this change is that starting with version 4.1, RPM no longer maps the rpm -b command to the real command, rpmbuild.
+ </div><div class="para">
+ When building RPMs, go through the following steps:
+ </div><div class="para">
+ 1.Set up the directory structure.
+ </div><div class="para">
+ 2.Place the sources in the right directory.
+ </div><div class="para">
+ 3.Create a spec file that tells the rpmbuild command what to do.
+ </div><div class="para">
+ 4.Build the source and binary RPMs.
+ </div><div class="para">
+ The following sections provide details for these steps.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id934340" class="title">Setting up the directory structure</h1></div></div></div><div class="para">
+ The RPM system expects five directories, as listed in Table 9-1.
+ </div><div class="para">
+ Table 9-1 RPM directories
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Directory
+ </div>
+
+ </td><td>
+ <div class="para">
+ Usage
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ BUILD
+ </div>
+
+ </td><td>
+ <div class="para">
+ The rpmbuild command builds software in this directory.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMS
+ </div>
+
+ </td><td>
+ <div class="para">
+ The rpmbuild command stores binary RPMs it creates in this directory.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ SOURCES
+ </div>
+
+ </td><td>
+ <div class="para">
+ You should put the sources for the application in this directory.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ SPECS
+ </div>
+
+ </td><td>
+ <div class="para">
+ You should place the spec file for each RPM you plan to make in this directory.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ SRPMS
+ </div>
+
+ </td><td>
+ <div class="para">
+ The rpmbuild command places source RPMs in this directory.
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ The RPMS directory usually has a number of architecture-specific subdirectories, such as the following (on an Intel architecture system):
+ </div><div class="para">
+ $ ls RPMS
+ </div><div class="para">
+ athlon
+ </div><div class="para">
+ i386
+ </div><div class="para">
+ i486
+ </div><div class="para">
+ i586
+ </div><div class="para">
+ i686
+ </div><div class="para">
+ noarch
+ </div><div class="para">
+ By default, Red Hat Linux systems expect RPMs to be built in the /usr/src/redhat directory.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ This directory is obviously specific to Red Hat Linux. On other Linux distributions, you'll likely see other directories.
+ </div><div class="para">
+ Within the /usr/src/redhat directory, you’ll see the subdirectories listed in Table 9-1, as follows:
+ </div><div class="para">
+ $ ls /usr/src/redhat
+ </div><div class="para">
+ BUILD
+ </div><div class="para">
+ RPMS
+ </div><div class="para">
+ SOURCES
+ </div><div class="para">
+ SPECS
+ </div><div class="para">
+ SRPMS
+ </div><div class="para">
+ At first, it seems rather odd to be using a system directory to build RPMs. But remember that the RPM system was originally built to create Linux distributions. You can also change the default directories by modifying your rpmrc settings.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ See <a class="xref" href="#ch-customizing-rpm">Cap. 20, <em>Customizing RPM Behavior</em></a> for more on the use of the rpmrc settings.
+ </div><div class="para">
+ For now, it is easiest to just change to the /usr/src/redhat directory and work from this location. To start, you will need to change ownership or permissions on these files so you can build RPMs while logged in as a normal user.
+ </div><div class="para">
+ Warning
+ </div><div class="para">
+ Do not build RPMs while logged in as root. Mistakes in building packages can have serious consequences if you are logged in as root.
+ </div><div class="para">
+ To build RPMs, you really need only two things:
+ </div><div class="para">
+ *Your sources in the SOURCES directory
+ </div><div class="para">
+ *Your spec file in the SPECS directory
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id563449" class="title">Placing your sources into the directory structure</h1></div></div></div><div class="para">
+ You can place all the source files directly in the /usr/src/redhat/SOURCES directory. In most cases, however, it is easier to create a tarball of the sources you want to build and place the tarball file in the /usr/src/redhat/SOURCES directory. The RPM specifications for commands necessary to extract the sources from such a file are trivial. Furthermore, the tarball, when extracted, should create a subdirectory specific to your package. This keeps your source code separate from other packages that also have source code in the SOURCES directory.
+ </div><div class="para">
+ The best strategy is to start in a directory of your own making, create the tarball file from the sources, and then copy the tarball file to the /usr/src/redhat/SOURCES directory.
+ </div><div class="para">
+ The convention for these tarball files is package-version.tar.gz. For example:
+ </div><div class="para">
+ jikes-1.17.tar.gz
+ </div><div class="para">
+ Place a file like this into the /usr/src/redhat/SOURCES directory. This file should include all the sources, all the build scripts, and any documentation you want to install as part of the package.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id789919" class="title">Creating the spec file</h1></div></div></div><div class="para">
+ The spec file, short for specification file, defines all the actions the rpmbuild command should take to build your application, as well as all the actions necessary for the rpm command to install and remove the application. Each source RPM should have the necessary spec file for building a binary RPM.
+ </div><div class="para">
+ The spec file is a text file. The normal naming convention is to name the file with the package name and a .spec filename extension. For example, the jikes package spec file would be named jikes.spec.
+ </div><div class="para">
+ Inside the spec file, format the information on the package using a special syntax. This syntax defines how to build the package, version numbers, dependency information, and everything else you can query about a package. This syntax differs slightly depending on the sections in the spec file. The following sections describe these spec file sections and the necessary syntax in each section.
+ </div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id712792" class="title">The introduction section</h1></div></div></div><div class="para">
+ The introduction section contains information about the package, the type of information shown with the rpm -qi command. For example:
+ </div><div class="para">
+ Summary: java source to bytecode compiler
+ </div><div class="para">
+ %define version 1.17
+ </div><div class="para">
+ Copyright: IBM Public License, http://ibm.com/developerworks/oss/license10.html
+ </div><div class="para">
+ Group: Development/Languages
+ </div><div class="para">
+ Name: jikes
+ </div><div class="para">
+ Prefix: /usr
+ </div><div class="para">
+ Provides: jikes
+ </div><div class="para">
+ Release: 1
+ </div><div class="para">
+ Source: jikes-%{version}.tar.gz
+ </div><div class="para">
+ URL: http://ibm.com/developerworks/opensource/jikes
+ </div><div class="para">
+ Version: %{version}
+ </div><div class="para">
+ Buildroot: /tmp/jikesrpm
+ </div><div class="para">
+ </div><div class="para">
+ %description
+ </div><div class="para">
+ The IBM Jikes compiler translates Java source files to bytecode. It
+ </div><div class="para">
+ also supports incremental compilation and automatic makefile generation,
+ </div><div class="para">
+ and is maintained by the Jikes Project:
+ </div><div class="para">
+ http://ibm.com/developerworks/opensource/jikes/
+ </div><div class="para">
+ In this example, you can see the Source: definition of a compressed tar archive associated with a particular version number. This also names a Buildroot: setting that defines where the files will get built into a working program. You can see the description of the package that will get printed with the rpm –qi command.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ You can further divide this first section into the preamble and other areas. For simplicity, I grouped all introductary parts of a spec file into one introduction section.
+ </div><div class="para">
+ This example comes from a real-world RPM spec file. It does not follow all the rules for creating RPMs. This example:
+ </div><div class="para">
+ *Should not explicitly provide jikes, the name of the package.
+ </div><div class="para">
+ *Should not include a Copyright tag, as this tag is deprecated.
+ </div><div class="para">
+ *Uses a %define for the version when the rpmbuild command can create a version macro for you.
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id899992" class="title">The prep section</h1></div></div></div><div class="para">
+ The prep section, short for prepare, defines the commands necessary to prepare for the build. If you are starting with a compressed tar archive (a tarball) of the sources, the prep section needs to extract the sources.
+ </div><div class="para">
+ For example:
+ </div><div class="para">
+ %prep
+ </div><div class="para">
+ %setup -q
+ </div><div class="para">
+ The prep section starts with a %prep statement.
+ </div><div class="para">
+ This example uses the %setup RPM macro, which knows about tar archives, to extract the files. In most cases, this will be all you need in your spec file prep section.
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id670936" class="title">The build section</h1></div></div></div><div class="para">
+ The spec file build section contains the commands to build the software. Usually, this will include just a few commands, since most of the real instructions appear in the Makefile. For example:
+ </div><div class="para">
+ %build
+ </div><div class="para">
+ ./configure CXXFLAGS=-O3 --prefix=$RPM_BUILD_ROOT/usr
+ </div><div class="para">
+ make
+ </div><div class="para">
+ The build section starts with a %build statement.
+ </div><div class="para">
+ The commands shown for this build section run the configure script, covered in the previous section on Linux build tools, and then run the make command with the default maketarget. If things unfold as they should, this procedure builds the software.
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id1002353" class="title">The install section</h1></div></div></div><div class="para">
+ The spec file install section holds the commands necessary to install the newly built application or library. In most cases, your install section should clean out the Buildroot directory and run the make install command. For example:
+ </div><div class="para">
+ %install
+ </div><div class="para">
+ rm -fr $RPM_BUILD_ROOT
+ </div><div class="para">
+ make install
+ </div><div class="para">
+ The install section starts with an %install statement.
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id697851" class="title">The clean section</h1></div></div></div><div class="para">
+ The clean section cleans up the files that the commands in the other sections create:
+ </div><div class="para">
+ %clean
+ </div><div class="para">
+ rm -rf $RPM_BUILD_ROOT
+ </div><div class="para">
+ The clean section starts with a %clean statement
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id697874" class="title">The files section</h1></div></div></div><div class="para">
+ Finally, the files section lists the files to go into the binary RPM, along with the defined file attributes. For example:
+ </div><div class="para">
+ %files
+ </div><div class="para">
+ %defattr(-,root,root)
+ </div><div class="para">
+ /usr/bin/jikes
+ </div><div class="para">
+ %doc /usr/doc/jikes-%{version}/license.htm
+ </div><div class="para">
+ %doc /usr/man/man1/jikes.1*
+ </div><div class="para">
+ The files section starts with a %files statement
+ </div><div class="para">
+ The %doc macro marks certain files as documentation. This allows the RPM to distinguish the files holding documentation from the other files in the RPM.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ This example skips the install and uninstall script sections, as well as a verification section. There are also no triggers defined in this RPM spec file. All of these topics are covered in <a class="xref" href="#ch-specfiles">Cap. 9, <em>Working with Spec Files</em></a> and <a class="xref" href="#ch-advanced-packaging">Cap. 10, <em>Creare avansată pachete RPM</em></a>.
+ </div><div class="para">
+ Once you have written your spec file, and placed the files in the SOURCES and SPECS directories under /usr/src/redhat, you’ll see files like the following:
+ </div><div class="para">
+ $ ls –CF /usr/src/redhat/*
+ </div><div class="para">
+ /usr/src/redhat/BUILD:
+ </div><div class="para">
+ </div><div class="para">
+ /usr/src/redhat/RPMS:
+ </div><div class="para">
+ athlon/ i386/ i486/ i586/ i686/ noarch/
+ </div><div class="para">
+ </div><div class="para">
+ /usr/src/redhat/SOURCES:
+ </div><div class="para">
+ jikes-1.17.tar.gz
+ </div><div class="para">
+ </div><div class="para">
+ /usr/src/redhat/SPECS:
+ </div><div class="para">
+ jikes.spec
+ </div><div class="para">
+ </div><div class="para">
+ /usr/src/redhat/SRPMS:
+ </div><div class="para">
+ That is, with a clean system and no other RPMs being built, you'll see a spec file in /usr/src/redhat/SPECS and the sources in /usr/src/redhat/SOURCES. In this example, the sources are in a compressed tar archive. (For this, the RPM spec file, jikes.spec needs to have a command in the prep section to extract the files.)
+ </div><div class="para">
+ You should now be ready to build an RPM.
+ </div></div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id727163" class="title">Building RPMs with the rpmbuild command</h1></div></div></div><div class="para">
+ To build RPMs with the rpmbuild command, use the following basic syntax:
+ </div><div class="para">
+ rpmbuild -bBuildStage spec_file
+ </div><div class="para">
+ The -b option tells rpmbuild to build an RPM. The extra BuildStage option is a special code that tells the rpmbuild command how far to go when building. Table 9-2 lists these options:
+ </div><div class="para">
+ Table 9-2 Options for building with rpmbuild
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Option
+ </div>
+
+ </td><td>
+ <div class="para">
+ Usage
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -ba
+ </div>
+
+ </td><td>
+ <div class="para">
+ Build all, both a binary and source RPM
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -bb
+ </div>
+
+ </td><td>
+ <div class="para">
+ Build a binary RPM
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -bc
+ </div>
+
+ </td><td>
+ <div class="para">
+ Build (compile) the program but do not make the full RPM, stopping just after the %build section
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -bp
+ </div>
+
+ </td><td>
+ <div class="para">
+ Prepare for building a binary RPM, and stop just after the %prep section
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -bi
+ </div>
+
+ </td><td>
+ <div class="para">
+ Create a binary RPM and stop just after the %install section
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -bl
+ </div>
+
+ </td><td>
+ <div class="para">
+ Check the listing of files for the RPM and generate errors if the buildroot is missing any of the files to be installed
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -bs
+ </div>
+
+ </td><td>
+ <div class="para">
+ Build a source RPM only
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ Note
+ </div><div class="para">
+ See chapter 12 for advanced options you can use with rpmbuild.
+ </div><div class="para">
+ For example, to set up all the necessary files and prepare for building, run the following command:
+ </div><div class="para">
+ rpmbuild –bp specfile
+ </div><div class="para">
+ This example runs through the %prep section, and stops immediately after this section. With the jikes package, for example, you’ll see a result like the following:
+ </div><div class="para">
+ $ rpmbuild -bp /usr/src/redhat/SPECS/jikes.spec
+ </div><div class="para">
+ Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.72435
+ </div><div class="para">
+ + umask 022
+ </div><div class="para">
+ + cd /usr/src/redhat/BUILD
+ </div><div class="para">
+ + LANG=C
+ </div><div class="para">
+ + export LANG
+ </div><div class="para">
+ + cd /usr/src/redhat/BUILD
+ </div><div class="para">
+ + rm -rf jikes-1.17
+ </div><div class="para">
+ + /usr/bin/gzip -dc /usr/src/redhat/SOURCES/jikes-1.17.tar.gz
+ </div><div class="para">
+ + tar -xf -
+ </div><div class="para">
+ + STATUS=0
+ </div><div class="para">
+ + '[' 0 -ne 0 ']'
+ </div><div class="para">
+ + cd jikes-1.17
+ </div><div class="para">
+ ++ /usr/bin/id -u
+ </div><div class="para">
+ + '[' 500 = 0 ']'
+ </div><div class="para">
+ ++ /usr/bin/id -u
+ </div><div class="para">
+ + '[' 500 = 0 ']'
+ </div><div class="para">
+ + /bin/chmod -Rf a+rX,g-w,o-w .
+ </div><div class="para">
+ + exit 0
+ </div><div class="para">
+ After running this command, the source files are extracted into the /usr/src/redhat/BUILD directory, under the jikes-1.17 subdirectory. Using a subdirectory keeps the sources for this package from intermixing with the sources for other packages.
+ </div><div class="para">
+ Running a directory listing on the /usr/src/redhat/BUILD/jikes-1.17 subdirectory shows what the spec file %prep section commands have done. For example:
+ </div><div class="para">
+ $ ls -1 /usr/src/redhat/BUILD/jikes-1.17
+ </div><div class="para">
+ acinclude.m4
+ </div><div class="para">
+ aclocal.m4
+ </div><div class="para">
+ AUTHORS
+ </div><div class="para">
+ ChangeLog
+ </div><div class="para">
+ config.guess
+ </div><div class="para">
+ config.sub
+ </div><div class="para">
+ configure
+ </div><div class="para">
+ configure.in
+ </div><div class="para">
+ COPYING
+ </div><div class="para">
+ depcomp
+ </div><div class="para">
+ doc
+ </div><div class="para">
+ INSTALL
+ </div><div class="para">
+ install-sh
+ </div><div class="para">
+ jikes.spec
+ </div><div class="para">
+ Makefile.am
+ </div><div class="para">
+ Makefile.in
+ </div><div class="para">
+ missing
+ </div><div class="para">
+ mkinstalldirs
+ </div><div class="para">
+ NEWS
+ </div><div class="para">
+ README
+ </div><div class="para">
+ src
+ </div><div class="para">
+ TODO
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ From these sources, you see a configure script. The configure script gives a good indication of how the software needs to be built. This example also shows a README file. You know what to do with these files.
+ </div><div class="para">
+ The actual source code is in the /usr/src/redhat/BUILD/jikes-1.17/src directory. The user documentation is stored in the /usr/src/redhat/BUILD/jikes-1.17/doc directory.
+ </div><div class="para">
+ To build a binary RPM, use the –bb option to the rpmbuild command. For example:
+ </div><div class="para">
+ $ rpmbuild -bb /usr/src/redhat/SPECS/jikes.spec
+ </div><div class="para">
+ Warning
+ </div><div class="para">
+ Don’t build packages when you are logged in as the root user. Log in as a normal user instead. This is to limit the damage caused to your system if the spec file or the Makefile contains errors that delete system files, for example. If you are logged in as the root user, you will have permission to perform these destructive acts. If you are logged in as a normal user, though, these RPM spec file and Makefile errors will fail to run, because you don’t have permission to modify system files.
+ </div><div class="para">
+ This command results in a lot of output, most coming from the configure script. (This script examines the C programming environment on your system.) When the rpmbuild command completes, you’ll see the binary RPM in the proper subdirectory of the RPMS directory. You can see the RPM with a directory listing, for example:
+ </div><div class="para">
+ $ls /usr/src/redhat/RPMS/i386:
+ </div><div class="para">
+ jikes-1.17-1.i386.rpm
+ </div><div class="para">
+ To stop execution just after the %install section, use a command like the following:
+ </div><div class="para">
+ rpmbuild –bi specfile
+ </div><div class="para">
+ For example:
+ </div><div class="para">
+ # rpmbuild -bi /usr/src/redhat/SPECS/jikes.spec
+ </div><div class="para">
+ To build a source RPM out of the files you have (in this case a tar archive of the sources and the spec file), use a command like the following:
+ </div><div class="para">
+ rpmbuild –bs specfile
+ </div><div class="para">
+ For example:
+ </div><div class="para">
+ $ rpmbuild -bs /usr/src/redhat/SPECS/jikes.spec
+ </div><div class="para">
+ When done, you’ll see the source RPM in the /usr/src/redhat/SRPMS directory:
+ </div><div class="para">
+ $ ls /usr/src/redhat/SRPMS
+ </div><div class="para">
+ jikes-1.17-1.src.rpm
+ </div><div class="para">
+ To clean out the files created by building these RPMs, use the --clean option to the rpmbuild command:
+ </div><div class="para">
+ rpmbuild --clean specfile
+ </div><div class="para">
+ For example:
+ </div><div class="para">
+ $ rpmbuild --clean /usr/src/redhat/SPECS/jikes.spec
+ </div><div class="para">
+ Executing(--clean): /bin/sh -e /var/tmp/rpm-tmp.21908
+ </div><div class="para">
+ + umask 022
+ </div><div class="para">
+ + cd /usr/src/redhat/BUILD
+ </div><div class="para">
+ + rm -rf jikes-1.17
+ </div><div class="para">
+ + exit 0
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ <a class="xref" href="#ch-rpmbuild">Cap. 11, <em>Controlling the Build with <code class="command">rpmbuild</code></em></a> covers a number of addition options for the rpmbuild command that you can use to customize the build.
+ </div></div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id761902" class="title">Verifying Your RPMS</h1></div></div></div><div class="para">
+ After you've built an RPM, you can use the techniques from <a class="xref" href="#ch-using-rpm-db">Cap. 4, <em>Using the RPM Database</em></a> to verify the RPM. You can also use the –bl option to the rpmbuild command to verify the list of files in the RPM. Use a command like the following:
+ </div><div class="para">
+ rpmbuild –bl spec_file
+ </div><div class="para">
+ For example:
+ </div><div class="para">
+ $ rpmbuild -bl /usr/src/redhat/SPECS/jikes.spec
+ </div><div class="para">
+ Processing files: jikes-1.17-1
+ </div><div class="para">
+ error: File not found: /tmp/jikesrpm/usr/bin/jikes
+ </div><div class="para">
+ error: File not found: /tmp/jikesrpm/usr/doc/jikes-1.17/license.htm
+ </div><div class="para">
+ error: File not found by glob: /tmp/jikesrpm/usr/man/man1/jikes.1*
+ </div><div class="para">
+ Provides: jikes
+ </div><div class="para">
+ </div><div class="para">
+ </div><div class="para">
+ RPM build errors:
+ </div><div class="para">
+ File not found: /tmp/jikesrpm/usr/bin/jikes
+ </div><div class="para">
+ File not found: /tmp/jikesrpm/usr/doc/jikes-1.17/license.htm
+ </div><div class="para">
+ File not found by glob: /tmp/jikesrpm/usr/man/man1/jikes.1*
+ </div><div class="para">
+ This example shows a number of errors. The -bl option checks that all the necessary files are located within the buildroot directory. The buildroot directory is a location that acts like the final installed root directory. From the previous example, this package was not properly built yet.
+ </div><div class="para">
+ In a situation like this, you can start over, or use the --short-circuit option to restart the build from a given section in the spec file. As you create an RPM, you will need to go back and forth restarting the build as you detect and fix errors.
+ </div><div class="para">
+ </div><div class="para">
+ You can also use the rpm command with options such as –V for verification on a fully-built package. For example:
+ </div><div class="para">
+ $ rpm -Vp /usr/src/redhat/RPMS/i386/jikes-1.17-1.i386.rpm
+ </div><div class="para">
+ S.5....T /usr/bin/jikes
+ </div><div class="para">
+ .......T d /usr/doc/jikes-1.17/license.htm
+ </div><div class="para">
+ ..5....T d /usr/man/man1/jikes.1.gz
+ </div><div class="para">
+ In this case, you see some file sizes and times differ. These differences can be explained by the fact that the original package was compiled on a different system and older version of Red Hat Linux than the version compiled locally.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ See the on "Verifying Installed RPM Packages" section in <a class="xref" href="#ch-using-rpm-db">Cap. 4, <em>Using the RPM Database</em></a> for more on the -V option.
+ </div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id969647" class="title">Summary</h1></div></div></div><div class="para">
+ This chapter introduced the task of building RPMs, whether building RPMs from your own applications or from software you have gathered elsewhere. In both cases, the steps for building the RPMs are the same.
+ </div><div class="para">
+ In most cases, you should build an RPM of the sources for your application, an RPM that can be used to reproduce the build of the application. Create a second RPM that holds the binary application. Once you set up the commands and define the spec file for the binary RPM, making a source RPM is trivial.
+ </div><div class="para">
+ Use the rpmbuild command to create RPMs. This command uses an RPM spec file to define the commands and settings for creating the RPM.
+ </div><div class="para">
+ The next chapter delves into the spec files that define the RPM directives for your packages.
+ </div></div></div><div xml:lang="ro" class="chapter" id="ch-specfiles" lang="ro"><div class="titlepage"><div><div><h2 class="title">Cap. 9. Working with Spec Files</h2></div></div></div><div class="toc"><dl><dt><span class="sect1"><a href="#id636173">9.1. Reading Spec Files</a></span></dt><dt><span class="sect1"><a href="#id726244">9.2. Writing Spec Files</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id622244">9.2.1. Comments</a></span></dt><dt><span class="sect2"><a href="#id656356">9.2.2. Storing spec files on disk</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id621366">9.3. Defining Package Information</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id1336268">9.3.1. Describing the package</a></span></dt><dt><span class="sect2"><a href="#id864211">9.3.2. Setting build locations</a></span></dt><dt><span class="sect2"><a href="#id1361246">9.3.3. Naming source files</a></span></dt><dt><span class="sect2"><a href="#id562402">9.3.4. Naming pat
ches</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id818931">9.4. Controlling the Build</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id786190">9.4.1. Preparing for the build</a></span></dt><dt><span class="sect2"><a href="#id763342">9.4.2. Building the software</a></span></dt><dt><span class="sect2"><a href="#id1412942">9.4.3. Installing the software</a></span></dt><dt><span class="sect2"><a href="#id838965">9.4.4. Cleaning up after the build</a></span></dt><dt><span class="sect2"><a href="#id496151">9.4.5. Defining installation scripts</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id848369">9.5. Filling the List of Files</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id716381">9.5.1. Using wildcards</a></span></dt><dt><span class="sect2"><a href="#id886328">9.5.2. Naming directories of files</a></span></dt><dt><span class="sect2"><a href="#id1413650">9.5.3. Marking files as documentation or configuration files</a></span></dt><
dt><span class="sect2"><a href="#id732681">9.5.4. Setting file attributes</a></span></dt><dt><span class="sect2"><a href="#id611823">9.5.5. Verifying the %files section</a></span></dt><dt><span class="sect2"><a href="#id587858">9.5.6. Filling the list of files automatically</a></span></dt><dt><span class="sect2"><a href="#id555916">9.5.7. Handling RPM build errors for unpackaged files</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id581967">9.6. Adding Change Log Entries</a></span></dt><dt><span class="sect1"><a href="#id673788">9.7. Defining Spec File Macros</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id673805">9.7.1. Built-in macros</a></span></dt><dt><span class="sect2"><a href="#id538862">9.7.2. Spec file-specific macros</a></span></dt><dt><span class="sect2"><a href="#id726602">9.7.3. Defining new macros</a></span></dt><dt><span class="sect2"><a href="#id578192">9.7.4. Specifying parameters to macros</a></span></dt></dl></dd><dt><span class="sec
t1"><a href="#id756998">9.8. Creating XML Spec Files</a></span></dt><dt><span class="sect1"><a href="#id1413321">9.9. Summary</a></span></dt></dl></div><div class="para">
+ This chapter covers:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Writing spec files
+ </div></li><li class="listitem"><div class="para">
+ Defining package information
+ </div></li><li class="listitem"><div class="para">
+ Controlling the build
+ </div></li><li class="listitem"><div class="para">
+ Listing the files in the package
+ </div></li><li class="listitem"><div class="para">
+ Defining spec file macros
+ </div></li></ul></div><div class="para">
+ The previous chapter introduces the concepts of how to build RPMs, and briefly covered the spec file, which controls how RPM packages are built and installed. This chapter delves into how to create spec files and the next chapter covers advanced spec file topics such as using conditional commands and making relocatable packages.
+ </div><div class="para">
+ A spec file defines all the commands and values that are required for creating a package, everything from the name and version number to the actual commands used to build the program you are packaging.
+ </div><div class="para">
+ This chapter covers the spec file syntax and how to write spec files. In goes in depth into defining information about your package, controlling how the software will be built, defining what exactly should go into the package, and customizing your build with RPM macros.
+ </div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id636173" class="title">Reading Spec Files</h1></div></div></div><div class="para">
+ The first step to learning more about spec files is to read through some of the huge number of spec files for the source RPMs that come with your Linux distribution. Looking at these files will show two things right away:
+ </div><div class="para">
+ *You will see that the spec file syntax is not really as complicated as it appears.
+ </div><div class="para">
+ *You will see how many others have solved problems similar to those you need to solve.
+ </div><div class="para">
+ I’ve used real-world examples throughout this book, to show how the RPMs you need to deal with actually work. Some of the more interesting packages include anything that has a client and a server component, anything with networking or e-mail, and anything that installs a system service. All these types of packages solve problems that you will commonly face. Some useful spec files to look at are those for anonftp, telnet, vnc, and sendmail. To get these spec files, you need to install the corresponding source RPMs for each of these packages.
+ </div><div class="para">
+ As you read through spec files, you’ll start to see common patterns in how packages are defined, named, the macros used, and common elements in the build sections of the spec files. You’ll also see how network services are installed on Linux, as well as example install and uninstall scripts. The next sections provide more information on the things to look for within spec files.
+ </div><div class="para">
+ Furthermore, even with the plethora of options RPM provides, if you know shell scripting basics and something about how C programs are normally built, with configure scripts and make commands, you will find most spec files relatively easy to understand.
+ </div><div class="para">
+ The following sections go into the details of writing your own spec files. Keep your example spec files handy as you read through these sections.
+ </div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id726244" class="title">Writing Spec Files</h1></div></div></div><div class="para">
+ Spec files are text files containing RPM directives. These directives use a simple syntax of a tag name, a colon, and a value:
+ </div><div class="para">
+ TagName: value
+ </div><div class="para">
+ For example:
+ </div><div class="para">
+ Version: 1.15
+ </div><div class="para">
+ This example sets the package version to 1.15. The name of the item is not case sensitive, so tag names of version, Version, or VERSION all set the same value. This syntax works for most settings, including Name, Release, and so on.
+ </div><div class="para">
+ In addition to this directive syntax, you can define macros using the RPM %define syntax. For example:
+ </div><div class="para">
+ %define major 2
+ </div><div class="para">
+ This example defines a macro named major with a value of 2. Once defined, you can access macros using the %{macro_name} or just %macro_name syntaxes. For example:
+ </div><div class="para">
+ source: %{name}-%{version}.tar.gz
+ </div><div class="para">
+ See the section "Defining Spec File Macros" later in this chapter for more options for macros.
+ </div><div class="para">
+ Major sections in the spec file are also delimited with % markers. For example, the build section starts with %build on a line by itself.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ The multiple uses of the % sign aren’t really that confusing in practice. Read through some spec files and you should find most of the commands are easily understood.
+ </div><div class="para">
+ Blank lines separate sections in the spec file, which makes sense for readability as well.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id622244" class="title">Comments</h1></div></div></div><div class="para">
+ To help document your work, you can include comments (to yourself and others reading the spec file). Any line starting with a hash character, #, holds a comment. RPM will ignore comments.
+ </div><div class="para">
+ # This is a comment.
+ </div><div class="para">
+ In spec files, comments are mostly to help explain your syntax choices to yourself should you view the spec file later. Comments are a good thing. You should comment heavily, especially for any choice that deviates from the norm. For example, if you provide special C compiler options for building the package, add comments to describe why you picked the options and how necessary they are. Such comments help immensely should you need to port the RPM to another architecture or modify how it was built.
+ </div><div class="para">
+ Tip
+ </div><div class="para">
+ Avoid single percent signs, %, in comments. For example:
+ </div><div class="para">
+ # Added new commands to %prep
+ </div><div class="para">
+ The rpmbuild command may report an error of a second %prep section. To get around this problem, use two percent signs, such as %%prep, in spec file comments.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id656356" class="title">Storing spec files on disk</h1></div></div></div><div class="para">
+ As discussed in <a class="xref" href="#ch-creating-rpms">Cap. 8, <em>Creating RPMs: An Overview</em></a> , the rpmbuild command expands source RPMs to the /usr/src/redhat directory. Under this directory, the RPM system assumes five subdirectories, listed in Table 10-1.
+ </div><div class="para">
+ Table 10-1 Default RPM directories
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Directory
+ </div>
+
+ </td><td>
+ <div class="para">
+ Usage
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ BUILD
+ </div>
+
+ </td><td>
+ <div class="para">
+ Where the rpmbuild command builds software
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMS
+ </div>
+
+ </td><td>
+ <div class="para">
+ Where the rpmbuild command stores binary RPMs it creates
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ SOURCES
+ </div>
+
+ </td><td>
+ <div class="para">
+ Where you should put the sources for the application
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ SPECS
+ </div>
+
+ </td><td>
+ <div class="para">
+ Where you should place the spec file
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ SRPMS
+ </div>
+
+ </td><td>
+ <div class="para">
+ Where the rpmbuild command places source RPMs
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ The spec files you create should be stored in the SPECS directory while building RPMs. (You can store your spec files permanently in any location you desire.)
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ These directories are the default directories. See <a class="xref" href="#ch-specfile-syntax">Cap. 22, <em>Spec File Syntax</em></a> for changing RPM default values. In addition, these are the defaults for Red Hat Linux. See <a class="xref" href="#ch-other-linuxes">Cap. 18, <em>Using RPM on Non-Red Hat Linuxes</em></a> and <a class="xref" href="#ch-other-linuxes">Cap. 18, <em>Using RPM on Non-Red Hat Linuxes</em></a> for discussions on other versions of Linux and other non-Linux operating systems, respectively.
+ </div><div class="para">
+ With the knowledge of the spec file syntax covered in the preceding sections, you can start to write spec files. The first step is to define the basic package information.
+ </div></div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id621366" class="title">Defining Package Information</h1></div></div></div><div class="para">
+ Most of the package information you need to enter into a spec file fleshes out the information you can query for a given package, such as the name, version, and release information, along with a longer description and a one-line summary.
+ </div><div class="para">
+ This gets a little more complicated when you set build locations, name source files, and name patches. The following sections cover how to specify the package information.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id1336268" class="title">Describing the package</h1></div></div></div><div class="para">
+ The first part of the spec file defines macros (covered in the section "Defining Spec File Macros"), and describes the package. Starting with the basics, you need a name, version, and release. You also should provide a longer description. For legal reasons, you may need to include ownership and copyright information.
+ </div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id1336281" class="title">Naming the Package</h1></div></div></div><div class="para">
+ The most important part of the package description is the NVR, or Name-Version-Release information, because this information is so crucial for the RPM system to compare versions and track dependencies.
+ </div><div class="para">
+ Set the name with the Name: directive. For example:
+ </div><div class="para">
+ Name: myapp
+ </div><div class="para">
+ The name should not contain any spaces or other whitespace characters such as tabs or newlines. Remember, RPM files are named, by default, name-version-release.rpm, or name-version-release-architecture.rpm, so use valid characters for file names.
+ </div><div class="para">
+ The version number is used in version comparisons. The RPM comparison algorithm is fairly complex, but can get fooled by strange version numbers. So, your best bet is to stick to dotted numerics, such as 1.5 or 2.3.1.1.4 or 1.0. Version numbers such as these will compare best from within the RPM system. For example:
+ </div><div class="para">
+ Version: 1.1.2
+ </div><div class="para">
+ You cannot use a dash in the version number, as RPM uses the dash to separate the Name-Version-Release elements. You can use a dash in the package name, though.
+ </div><div class="para">
+ The release number should start at 1 for the first RPM you build for a given version of the package, and count up from there. For example:
+ </div><div class="para">
+ Release: 1
+ </div><div class="para">
+ The release differentiates newer updates of the RPM itself, even if the underlying application hasn’t changed. (The application may be compiled with different compiler options, though.) For most usage, simply start at 1 and each time you modify the spec file and recreate the package, increment the release number.
+ </div><div class="para">
+ If the version number is not enough to allow for comparisons, for example, if the version numbering scheme has changed radically between releases, you can define an Epoch: directive. For example:
+ </div><div class="para">
+ Epoch: 3
+ </div><div class="para">
+ If you renumber your versions, use an Epoch setting to clarify the version history. For example, Sun Microsystems went from SunOS 4.1 to Solaris 2. The Epoch: helps RPM properly handle strange version number changes. Define the Epoch: as a whole number such as 1, 2, or 3.
+ </div><div class="para">
+ Warning
+ </div><div class="para">
+ Avoid using the Epoch: directive if at all possible. It is far better to use a sane version-numbering scheme than to try to resolve the mess with epoch values. The main problems with using an epoch value are that epochs are hidden from users in most cases, and using epochs can lead to very strange-looking tasks such as a newer package with a version number that looks older than the older package.
+ </div><div class="para">
+ The older Serial: directive also works similarly to the Epoch: directive. For example:
+ </div><div class="para">
+ Serial: 6
+ </div><div class="para">
+ Like the Epoch:, the Serial: directive should be a number that counts upward. Modern packages should use the Epoch: directive instead of Serial:, since Serial: has been deprecated for many, many rpm versions.
+ </div><div class="para">
+ The Group: directive provides a classification for your packages. If at all possible, use a category name that already exists for other packages, such as System Environment/Shells for a Linux shell. For example:
+ </div><div class="para">
+ Group: System Environment/Shells
+ </div><div class="para">
+ Many graphical installation tools divide packages by these categories, so you want to fit into the existing group names if possible. (See <a class="xref" href="#ch-using-rpm-db">Cap. 4, <em>Using the RPM Database</em></a> for more on querying group information from RPMs.) The official list of groups are located in the file /usr/share/doc/rpm-4.1/GROUPS for RPM 4.1, and in a similar location for other RPM versions.
+ </div><div class="para">
+ The Distribution: directive is used by Linux distribution vendors such as Red Hat to identify that the package is part of a given distribution, or was built for a particular distribution. Most packages created outside of the Linux vendors don’t provide this directive.
+ </div><div class="para">
+ Distribution: Red Hat Linux
+ </div><div class="para">
+ The Icon: directive names an icon file stored in the RPM. The file format should be XPM or GIF, with an extension of .xpm or .gif, respectively. Some packaging tools will use this icon in a package display.
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id1009045" class="title">Specifying Company Information</h1></div></div></div><div class="para">
+ For legal reasons, you probably want to specify the organization behind the RPM, any copyright or licensing information, as well as a URL to find out more information. Even if you are not concerned about corporate legal issues, you may want to identify where the package came from. Use the following directives to provide this information.
+ </div><div class="para">
+ The Vendor: directive names the company or organization behind an RPM. For example:
+ </div><div class="para">
+ Vendor: The Really Cool Company
+ </div><div class="para">
+ The URL: directive provides a URL to your company or organization home page, or perhaps to a URL for a particular application. For example:
+ </div><div class="para">
+ URL: http://mycompany.yow/products/coolstuff
+ </div><div class="para">
+ Similarly, the Packager: directive provides an optional name and e-mail address for the person who created the RPM:
+ </div><div class="para">
+ Packager: Bob Marley <marley at reggae.com>
+ </div><div class="para">
+ The License: and Copyright: directives provide legal information about your package. Older packages tended to use Copyright: as a statement of the package’s license, not copyright. For example:
+ </div><div class="para">
+ Copyright: BSD
+ </div><div class="para">
+ License: LGPL
+ </div><div class="para">
+ Warning
+ </div><div class="para">
+ The Copyright: directive is deprecated in favor of License:.
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id772593" class="title">Filling in the Description</h1></div></div></div><div class="para">
+ The Summary: directive provides a one-line short description of the package. You should not exceed much more than 50 characters when writing your summary. For example:
+ </div><div class="para">
+ Summary: A program that does exactly what you want
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ The Summary: directive of the spec file replaces the older Description: directive.
+ </div><div class="para">
+ The %description section allows for longer text describing your package. Fill in as many lines as you need after the %description section. For example:
+ </div><div class="para">
+ %description
+ </div><div class="para">
+ This is a really cool package. It contains the really cool
+ </div><div class="para">
+ program that provides a maximum return on investment,
+ </div><div class="para">
+ or ROI, for achieving your crucial business objectives
+ </div><div class="para">
+ utilizing world-class high-caliber componentized software
+ </div><div class="para">
+ implemented with world-class quality and performance
+ </div><div class="para">
+ metrics.
+ </div><div class="para">
+ The %description section supports a limited amount of formatting. Blank lines are assumed to separate paragraphs. Some graphical user interface installation programs will reformat paragraphs into a nicer-looking font and change the display width.
+ </div><div class="para">
+ Lines in the %description section that start with whitespace, such as a space or tab, will be treated as preformatted text and displayed as is, normally with a fixed-width font. The rpm command supports text formatting this way. Other rpm programs may not.
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id850275" class="title">Specifying the Platform Architecture</h1></div></div></div><div class="para">
+ Spec files can announce that a package can run on more than one operating system or is tied to a particular version of a particular operating system.
+ </div><div class="para">
+ For example, the Excludearch: directive states that a package should not be built on the given architecture or architectures. For example:
+ </div><div class="para">
+ ExcludeArch: sparc s390 s390x
+ </div><div class="para">
+ This example excludes the SPARC and S/390 mainframe architectures. You can provide more than one architecture in the directive, separated by spaces or commas.
+ </div><div class="para">
+ Similarly, the Exclusivearch: directive states that a package can only be built on the given architecture or architectures. For example:
+ </div><div class="para">
+ ExclusiveArch: i386 ia64 alpha
+ </div><div class="para">
+ This example identifies the package as only working on the Intel i386, IA-64, and Alpha architectures.
+ </div><div class="para">
+ The Excludeos: and Exclusiveos: directives restrict the operating system. For example:
+ </div><div class="para">
+ Excludeos: windows
+ </div><div class="para">
+ This example states that the package should not be built on Windows. In contrast, the Exclusiveos: directive names only the operating system or systems that the package can be built on. For example:
+ </div><div class="para">
+ Exclusiveos: linux
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ <a class="xref" href="#ch-other-linuxes">Cap. 18, <em>Using RPM on Non-Red Hat Linuxes</em></a> and <a class="xref" href="#ch-other-os">Cap. 19, <em>RPM on Other Operating Systems</em></a> cover RPMs on other versions of Linux and other operating systems, respectively.
+ </div></div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id864211" class="title">Setting build locations</h1></div></div></div><div class="para">
+ RPM supports two build-related directories with very similar names, the build directory and the buildroot.
+ </div><div class="para">
+ The build directory is the location where RPM actually builds the software, compiling source code, running the configure script, and so on. Normally, you do not need to worry about the build directory as the rpmbuild command properly changes to this directory as needed.
+ </div><div class="para">
+ The buildroot, on the other hand, acts as a staging area that looks like the final installation directory. The name buildroot refers to the fact that the final installation directory is usually the root directory, /. The install section of the spec file (covered in the section "Installing the Software") installs files into the buildroot directory in the proper subdirectories, as if the files were really under the system root directory, /. This allows the buildroot directory to hold all the final installed files for a package, so you can see what will really be installed by the package.
+ </div><div class="para">
+ You should always set the buildroot by defining a Buildroot: entry in your spec file. For example:
+ </div><div class="para">
+ </div><div class="para">
+ Buildroot: %{_tmppath}/%{name}-%{version}-root
+ </div><div class="para">
+ This example sets the buildroot under the temporary directory named in the %_tmppath macro. The subdirectory is named based on the name and version of the package. For example, for a package named ypbind and a version 1.12, with a %_tmppath value of /tmp, the final buildroot directory would be:
+ </div><div class="para">
+ /tmp/ypbind-1.12-root
+ </div><div class="para">
+ Once you set a buildroot, your scripts run from the spec file and commands within the spec file can access the buildroot using the RPM_BUILD_ROOT environment variable. You normally need to access the RPM_BUILD_ROOT environment variable in the install section of the spec file (covered in the section "Installing the Software").
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ You can override the buildroot with the --buildroot command-line parameter to the rpmbuild command.
+ </div><div class="para">
+ The buildroot replaces the older, and now obsolete directive, Root:.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id1361246" class="title">Naming source files</h1></div></div></div><div class="para">
+ Most packages have one or more bundles of source code, which you need to name in the spec file. In most cases, you will have a compressed tar archive of source files. These may be files developed by your organization or downloaded from an Internet site. You can define one or more source tags, counting from 0. For example:
+ </div><div class="para">
+ Source0: telnet-client.tar.gz
+ </div><div class="para">
+ Source1: telnet-xinetd
+ </div><div class="para">
+ Source2: telnet.wmconfig
+ </div><div class="para">
+ In this example, Source0: refers to a compressed tar archive. The rpmbuild program will extract the files into the buildroot directory. The Source1: and Source2: directives name individual source files. You can name compressed tar archives or individual files as needed.
+ </div><div class="para">
+ If you just have one Source directive, you can skip the 0. For example:
+ </div><div class="para">
+ Source: telnet-client.tar.gz
+ </div><div class="para">
+ You can also use FTP or HTTP URLs to name sources. For example:
+ </div><div class="para">
+ Source0: ftp://ftp.somesite.yow/pub/linux/%{telnet_version}.tar.gz
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ The URLs listed in source directives are for convenience and future reference only. RPM will not download these files.
+ </div><div class="para">
+ The files named by the Source directives will get included into the source RPM. Sometimes you need to keep some sources out of the source RPM. This could be for proprietary sources you cannot ship, or simply due to size. The Nosource: directive tells RPM to skip a source file from the source RPM. For example:
+ </div><div class="para">
+ NoSource: 0
+ </div><div class="para">
+ This example means that the first source item should not be included in the package.
+ </div><div class="para">
+ NoSource: 3
+ </div><div class="para">
+ This example means that the third source item should not be included in the package. The NoPatch directive works similarly. In addition, do not place more than one number on any given NoSource or NoPatch directive.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ Using the Nosource: or NoPatch: directives, covered following, mean you are creating a source RPM that cannot be rebuilt unless you also have the sources or patches, respectively, that were used to create the original RPM.
+ </div><div class="para">
+ If the package contains a Nosource: or Nopatch: directive, rpmbuild will use a file-name extension of .nosrc.rpm instead of .src.rpm.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id562402" class="title">Naming patches</h1></div></div></div><div class="para">
+ Patches are named similar to sources, using a similar syntax. For example:
+ </div><div class="para">
+ Patch1: telnet-client-cvs.patch
+ </div><div class="para">
+ Patch2: telnetd-0.17.diff
+ </div><div class="para">
+ Patch3: telnet-0.17-env.patch
+ </div><div class="para">
+ Patch4: telnet-0.17-issue.patch
+ </div><div class="para">
+ Patch5: telnet-0.17-sa-01-49.patch
+ </div><div class="para">
+ Patch6: telnet-0.17-env-5x.patch
+ </div><div class="para">
+ Patch10: telnet-0.17-pek.patch
+ </div><div class="para">
+ Note that you can have Patch directives are not numbered sequentially, such as the Patch10: directive in this example. In addition, you must apply each patch manually using %patch directives.
+ </div><div class="para">
+ The patch files may be individual files or compressed (with gzip) patch files.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ See the patch and diff online manual pages for more on patches.
+ </div><div class="para">
+ Patches are important because they allow you to start with pristine sources, the source code for the original application. You can then apply patches as needed to get a working application, more clearly separating the work needed to create an RPM from the original application source code.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ <a class="xref" href="#ch-packaging-guidelines">Cap. 13, <em>Packaging Guidelines</em></a> discusses packaging guidelines and best practices. Starting from pristine sources is one of the best practices.
+ </div><div class="para">
+ Similar to the sources directives, you can define a Nopatch: directive, which defines a patch that is applied to the sources, but is not included in the source RPM.
+ </div></div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id818931" class="title">Controlling the Build</h1></div></div></div><div class="para">
+ After describing information about the package, the crucial step comes when you need to build the package. The spec file should contain all the commands needed to build the application or library you want to package. But, and this is the important part, most of the build process should be run from a Makefile or other conventional way to build applications. Using a build tool such as make means that you can test the application outside of the RPM system. You don’t need an RPM to build the application. Instead, you use the RPM to package the application.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ <a class="xref" href="#ch-creating-rpms">Cap. 8, <em>Creating RPMs: An Overview</em></a> covers make and other Linux build tools.
+ </div><div class="para">
+ In RPM terms, building the package is split into four steps:
+ </div><div class="para">
+ 1.Preparing for building, including unpacking the sources
+ </div><div class="para">
+ 2.Building
+ </div><div class="para">
+ 3.Installing the application or library
+ </div><div class="para">
+ 4.Cleaning up
+ </div><div class="para">
+ The next sections cover how to control the build run by rpmbuild by defining commands within your spec files.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id786190" class="title">Preparing for the build</h1></div></div></div><div class="para">
+ The %prep section defines the commands to prepare for the build. In most cases, you can run the simple %setup macro. For example:
+ </div><div class="para">
+ %prep
+ </div><div class="para">
+ %setup -q
+ </div><div class="para">
+ This command changes to the build directory, typically /usr/src/redhat/BUILD, and then extracts the source files. This macro expects that at least one of the source files will create the necessary subdirectory under /usr/src/redhat/BUILD. This subdirectory should be named with the package name and version, such as telnet-1.0.1. If you are not using a compressed tar archive that will automatically create the right subdirectory, add the –c option to the %setup macro. The –c option creates the subdirectory for extracting the sources.
+ </div><div class="para">
+ The –q command-line option runs in quiet mode with minimal output. The –T option disables the automatic extraction of compressed tar files. You can set the name of the build subdirectory with the –n option.
+ </div><div class="para">
+ Normally, the %setup macro deletes the subdirectory prior to extracting the sources. You can disable the directory deletion with the –D option.
+ </div><div class="para">
+ Table 10-2 summarizes the %setup command-line parameters. Many of these options apply mostly for subpackages, a topic covered in <a class="xref" href="#ch-advanced-packaging">Cap. 10, <em>Creare avansată pachete RPM</em></a> .
+ </div><div class="para">
+ Table 10-2 Command-line parameters for %setup
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Parameter
+ </div>
+
+ </td><td>
+ <div class="para">
+ Usage
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -a number
+ </div>
+
+ </td><td>
+ <div class="para">
+ Only unpack the source directive of the given number, such as –a 0 for source0:, after changing to the directory.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -b number
+ </div>
+
+ </td><td>
+ <div class="para">
+ Only unpack the source directive of the given number, such as –b 0 for source0:, before changing to the directory.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -c
+ </div>
+
+ </td><td>
+ <div class="para">
+ Create directory before unpacking, used if your sources will not create the directory as part of unpacking.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -D
+ </div>
+
+ </td><td>
+ <div class="para">
+ Do not delete the directory before unpacking.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -n name
+ </div>
+
+ </td><td>
+ <div class="para">
+ Name the directory as name.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -q
+ </div>
+
+ </td><td>
+ <div class="para">
+ Run quietly with minimal output.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -T
+ </div>
+
+ </td><td>
+ <div class="para">
+ Disable the automatic unpacking of the archives.
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ The %setup directive can automatically extract tar, zip, gzip, bzip2, pack, compress, and lzh compressed files. The tar-gzip format is most widely used, though.
+ </div><div class="para">
+ Like the %setup macro, the %patch directive applies a patch to the sources. Use this macro in your %prep section if you have patches. You need a %patch directive for each patch.
+ </div><div class="para">
+ The %patch directive accepts –p and other command-line parameters for the underlying patch command. The –p option, with a number, such as –p0, tells the patch command to remove that many slashes from the file names within the patch. A –p0 option tells the patch command to remove no slashes, a –p1 option tells patch to remove one slash, and correspondingly, one directory level from the files in the patch. You can also pass other options for the patch command.
+ </div><div class="para">
+ Use these options if you need them for the patch command when manually patching the sources. Otherwise, you can set up your %prep section as follows, for a spec file with two patches:
+ </div><div class="para">
+ %prep
+ </div><div class="para">
+ %setup –q
+ </div><div class="para">
+ %patch1
+ </div><div class="para">
+ %patch2
+ </div><div class="para">
+ Use numbers to identify which patch to apply. For example, %patch0 corresponds to the patch file named with the Patch0: directive.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ You must define a separate %patch directive for each patch. In most packages, this format, %patch1, %patch2, and so on, is used.
+ </div><div class="para">
+ The %patch directive without a number corresponds to %patch0.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ See the patch and diff online manual pages for more on patches.
+ </div><div class="para">
+ In addition to the options supported by the patch command, you can use special options to the %patch directive to control how the directive works. The –P option tells the %patch directive to apply a given patch. For example, to only apply the patch named with the Patch2: directive, use the following %patch directive:
+ </div><div class="para">
+ %patch –P 2
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ This is an uppercase P. The lowercase p performs a different function, described earlier in this section. The -P option is rarely used. Instead, patches are normally applied with %patch0, %patch1, and so on directives.
+ </div><div class="para">
+ </div><div class="para">
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id763342" class="title">Building the software</h1></div></div></div><div class="para">
+ The %prep section prepares for the build, which the %build section performs. You need to fill in the %build section with all the commands necessary to build the software. In most cases, this consists simply of the following commands:
+ </div><div class="para">
+ %build
+ </div><div class="para">
+ ./configure
+ </div><div class="para">
+ make
+ </div><div class="para">
+ In this case, the %build section runs two commands, ./configure to run the configure script, and make to build the software. For most applications, this may be all you need. You can use the %configure macro in place of the call to the ./configure script. For example:
+ </div><div class="para">
+ %build
+ </div><div class="para">
+ %configure
+ </div><div class="para">
+ make
+ </div><div class="para">
+ Most spec files should use the %configure macro, since it automatically sets many environment variables that are often used within the configure script, especially path-related values such as the online manual path, the temporary directory, and so on. You can use the rpm --eval to see how the %configure macro expands. For example:
+ </div><div class="para">
+ $ rpm --eval '%configure'
+ </div><div class="para">
+ </div><div class="para">
+ CFLAGS="${CFLAGS:--O2 -march=i386 -mcpu=i686}" ; export CFLAGS ;
+ </div><div class="para">
+ CXXFLAGS="${CXXFLAGS:--O2 -march=i386 -mcpu=i686}" ; export CXXFLAGS ;
+ </div><div class="para">
+ FFLAGS="${FFLAGS:--O2 -march=i386 -mcpu=i686}" ; export FFLAGS ;
+ </div><div class="para">
+ [ -f configure.in ] && libtoolize --copy --force ;
+ </div><div class="para">
+ ./configure i386-redhat-linux \
+ </div><div class="para">
+ --prefix=/usr \
+ </div><div class="para">
+ --exec-prefix=/usr \
+ </div><div class="para">
+ --bindir=/usr/bin \
+ </div><div class="para">
+ --sbindir=/usr/sbin \
+ </div><div class="para">
+ --sysconfdir=/etc \
+ </div><div class="para">
+ --datadir=/usr/share \
+ </div><div class="para">
+ --includedir=/usr/include \
+ </div><div class="para">
+ --libdir=/usr/lib \
+ </div><div class="para">
+ --libexecdir=/usr/libexec \
+ </div><div class="para">
+ --localstatedir=/var \
+ </div><div class="para">
+ --sharedstatedir=/usr/com \
+ </div><div class="para">
+ --mandir=/usr/share/man \
+ </div><div class="para">
+ --infodir=/usr/share/info
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ The vast majority of the work of building the software should remain in the Makefile where it belongs. The commands in the spec file should invoke the targets defined in the Makefile. Don’t place too much logic in your RPM spec file as this makes it harder to test the application or library you plan to package.
+ </div><div class="para">
+ If you intend to support relocatable packages, covered in <a class="xref" href="#ch-advanced-packaging">Cap. 10, <em>Creare avansată pachete RPM</em></a> , you will likely need to pass a --prefix option to the configure script. For example:
+ </div><div class="para">
+ %build
+ </div><div class="para">
+ ./configure --prefix=$RPM_BUILD_ROOT/usr
+ </div><div class="para">
+ make
+ </div><div class="para">
+ You can also pass other options to the configure script, as needed, for compiling the application.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id1412942" class="title">Installing the software</h1></div></div></div><div class="para">
+ The %install section should install the software built in the %build section. If your Makefile contains all the instructions to install, you can define an %install section as follows:
+ </div><div class="para">
+ %install
+ </div><div class="para">
+ make install PREFIX=$RPM_BUILD_ROOT/usr
+ </div><div class="para">
+ In most cases, you need to pass some parameter to make or install or another command to install all files into the buildroot directory, as shown in this example with the $RPM_BUILD_ROOT environment variable. You need to look within the Makefile to determine if the make variable should be PREFIX, prefix, or something else.
+ </div><div class="para">
+ Sometimes, you want to call the install command instead of make to perform the installation. For example:
+ </div><div class="para">
+ %install
+ </div><div class="para">
+ install -m755 myapp $RPM_BUILD_ROOT/usr/bin/myapp
+ </div><div class="para">
+ This example uses a hypothetical application name of myapp.
+ </div><div class="para">
+ Many packages use the %makeinstall macro, which runs the make install command. For example:
+ </div><div class="para">
+ %install
+ </div><div class="para">
+ rm -rf $RPM_BUILD_ROOT
+ </div><div class="para">
+ %makeinstall
+ </div><div class="para">
+ This example also cleans the files from the buildroot. Use the rpm --eval command to see how the %makeinstall macro expands. For example:
+ </div><div class="para">
+ $ rpm --eval '%makeinstall'
+ </div><div class="para">
+ </div><div class="para">
+ make \
+ </div><div class="para">
+ prefix=/usr \
+ </div><div class="para">
+ exec_prefix=/usr \
+ </div><div class="para">
+ bindir=/usr/bin \
+ </div><div class="para">
+ sbindir=/usr/sbin \
+ </div><div class="para">
+ sysconfdir=/etc \
+ </div><div class="para">
+ datadir=/usr/share \
+ </div><div class="para">
+ includedir=/usr/include \
+ </div><div class="para">
+ libdir=/usr/lib \
+ </div><div class="para">
+ libexecdir=/usr/libexec \
+ </div><div class="para">
+ localstatedir=/var \
+ </div><div class="para">
+ sharedstatedir=/usr/com \
+ </div><div class="para">
+ mandir=/usr/share/man \
+ </div><div class="para">
+ infodir=/usr/share/info \
+ </div><div class="para">
+ install
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ RPM 4.2 adds a %check section after the %install.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id838965" class="title">Cleaning up after the build</h1></div></div></div><div class="para">
+ The %clean section should clean up after the build and installation, removing compiled files and other files created as part of the build. If you use a buildroot, discussed previously, then you can provide a %clean section like the following:
+ </div><div class="para">
+ %clean
+ </div><div class="para">
+ rm -rf $RPM_BUILD_ROOT
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id496151" class="title">Defining installation scripts</h1></div></div></div><div class="para">
+ In addition to the sections described previously for controlling the build of the package software, you can define more scripts in your RPM spec files. RPM supports a script run prior to installation, %pre, and a script run after installation, %post. The same concepts apply when a package is erased, or uninstalled. The %preun script is run just before the uninstall and the %postun script just after the uninstall.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ <a class="xref" href="#ch-advanced-packaging">Cap. 10, <em>Creare avansată pachete RPM</em></a> covers triggers, another form of script that gets run when packages are installed or removed.
+ </div><div class="para">
+ Start your scripts with the RPM section marker for the given script, such as %pre for the pre-install script. Then, place the shell commands you want to run. For example, the following define %post, %preun and %postun scripts from the ypbind networking package:
+ </div><div class="para">
+ %post
+ </div><div class="para">
+ /sbin/chkconfig --add ypbind
+ </div><div class="para">
+ </div><div class="para">
+ %preun
+ </div><div class="para">
+ if [ "$1" = 0 ] ; then
+ </div><div class="para">
+ /sbin/service ypbind stop > /dev/null 2>&1
+ </div><div class="para">
+ /sbin/chkconfig --del ypbind
+ </div><div class="para">
+ fi
+ </div><div class="para">
+ exit 0
+ </div><div class="para">
+ </div><div class="para">
+ %postun
+ </div><div class="para">
+ if [ "$1" -ge 1 ]; then
+ </div><div class="para">
+ /sbin/service ypbind condrestart > /dev/null 2>&1
+ </div><div class="para">
+ fi
+ </div><div class="para">
+ exit 0
+ </div><div class="para">
+ Few packages need to perform any work prior to installation, so the %pre script is rarely used.
+ </div><div class="para">
+ In this example, the chkconfig command is called to update the runlevel information for system services after installation and prior to removal. This is an example where just installing the application, ypbind in this case, is not enough. Since this application acts as a system service, more work needs to be done to finish the installation with the %pre script or clean up the service on removal with the %preun script.
+ </div><div class="para">
+ Warning
+ </div><div class="para">
+ Do not try to write interactive scripts. Many users install RPMs automatically. In such cases, or if the user runs a graphical RPM tool, any information your scripts output will be lost. User input will not be available.
+ </div><div class="para">
+ The rpm command will pass one argument to your scripts, shown as $1 in the previous example, which holds a count of the number of versions of the package that are installed. Table 10-3 lists the counts for specific cases.
+ </div><div class="para">
+ Table 10-3 Install and uninstall script count values
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Action
+ </div>
+
+ </td><td>
+ <div class="para">
+ Count
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Install the first time
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Upgrade
+ </div>
+
+ </td><td>
+ <div class="para">
+ 2 or higher (depending on the number of versions installed)
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Remove last version of package
+ </div>
+
+ </td><td>
+ <div class="para">
+ 0
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ The previous script example accesses the count using the shell variable $1.
+ </div></div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id848369" class="title">Filling the List of Files</h1></div></div></div><div class="para">
+ The %files section holds a list of all the files that RPM should install from the package. This list should be exhaustive, so that the RPM system knows exactly what your package installs. There are some options, though, to name all the files within a directory to help with packages containing hundreds of files.
+ </div><div class="para">
+ In the default case, each line under the %files section names a separate file with its full path. For example:
+ </div><div class="para">
+ %files
+ </div><div class="para">
+ /usr/X11R6/bin/xtoolwait
+ </div><div class="para">
+ /usr/X11R6/man/man1/xtoolwait.1
+ </div><div class="para">
+ This example lists two files, /usr/X11R6/bin/xtoolwait and /usr/X11R6/man/man1/xtoolwait.1, presumably an online manual files.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id716381" class="title">Using wildcards</h1></div></div></div><div class="para">
+ In addition to naming each file on a line, you can use glob-style wildcards. For example:
+ </div><div class="para">
+ %files
+ </div><div class="para">
+ /usr/X11R6/bin/xtoolwait
+ </div><div class="para">
+ /usr/X11R6/man/man1/xtoolwait.*
+ </div><div class="para">
+ This example states that all files in /usr/X11R6/man/man1 that start with xtoolwait. should be included in the package.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id886328" class="title">Naming directories of files</h1></div></div></div><div class="para">
+ In addition to using wildcard globs, you can specify whole directories as part of your package. For example:
+ </div><div class="para">
+ %files
+ </div><div class="para">
+ /usr/X11R6/bin/xtoolwait
+ </div><div class="para">
+ /etc/xtoolwait
+ </div><div class="para">
+ This example names all the files in the directory /etc/xtoolwait as part of the package. Be very careful when listing this directory. Do not include a system directory such as /usr/bin, as RPM will assume your package owns all of /usr/bin, which contains hundreds of commands. This can be a problem when you try to remove a package.
+ </div><div class="para">
+ It is OK to name a subdirectory that your package owns. For example, while /etc is a system directory, /etc/xtoolwait is a reasonable directory for the xtoolwait package to control.
+ </div><div class="para">
+ If you just want to include an empty directory in the package, and not the files within the directory, use the %dir directive in front of the directory name. For example:
+ </div><div class="para">
+ %files
+ </div><div class="para">
+ /usr/X11R6/bin/xtoolwait
+ </div><div class="para">
+ %dir /etc/xtoolwait
+ </div><div class="para">
+ This example states that the package contains the /usr/X11R6/bin/xtoolwait program and the empty directory /etc/xtoolwait.
+ </div><div class="para">
+ In addition to the straight list of files or directories, RPM provides other options, starting with marking certain files as documentation or configuration files.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id1413650" class="title">Marking files as documentation or configuration files</h1></div></div></div><div class="para">
+ RPM keeps special track of files within a package that hold documentation or configuration data. You need to identify these files with special directives.
+ </div><div class="para">
+ The %doc directive marks a file as a documentation file. For example:
+ </div><div class="para">
+ %files
+ </div><div class="para">
+ /usr/X11R6/bin/xtoolwait
+ </div><div class="para">
+ %doc /usr/X11R6/man/man1/xtoolwait.*
+ </div><div class="para">
+ This example lists all the included files in /usr/X11R6/man/man1 as documentation files.
+ </div><div class="para">
+ If you don’t include the full path to a documentation file or files, the RPM system will create a special documentation directory for the package, and place those files into that directory. For example:
+ </div><div class="para">
+ %doc README NEWS
+ </div><div class="para">
+ This example places the files README and NEWS into a newly created package-specific directory, typically a subdirectory under /usr/share/doc or /usr/doc.
+ </div><div class="para">
+ The %docdir directive names a directory that holds documentation. All files under that directory in the package will get automatically marked as documentation files. For example:
+ </div><div class="para">
+ %files
+ </div><div class="para">
+ /usr/X11R6/bin/xtoolwait
+ </div><div class="para">
+ %docdir /usr/X11R6/man/man1
+ </div><div class="para">
+ /usr/X11R6/man/man1/xtoolwait.*
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ In addition to the marked directories, the standard Linux documentation directories, such as /usr/share/man, are automatically assumed to be documentation directories.
+ </div><div class="para">
+ Similar to the %doc directive, the %config directive marks a file as configuration. For example:
+ </div><div class="para">
+ %files
+ </div><div class="para">
+ /sbin/ypbind
+ </div><div class="para">
+ %config /etc/rc.d/init.d/*
+ </div><div class="para">
+ %config /etc/yp.conf
+ </div><div class="para">
+ %doc README NEWS
+ </div><div class="para">
+ A special option to the %config directive, noreplace, tells RPM not to overwrite, or replace a configuration file. For example:
+ </div><div class="para">
+ %files
+ </div><div class="para">
+ /sbin/ypbind
+ </div><div class="para">
+ %config /etc/rc.d/init.d/*
+ </div><div class="para">
+ %config(noreplace) /etc/yp.conf
+ </div><div class="para">
+ %doc README NEWS
+ </div><div class="para">
+ Use this option to help protect local modifications. If you use %config(noreplace), the file will not overwrite an existing file that has been modified. If the file has not been modified on disk, the rpm command will overwrite the file. But, if the file has been modified on disk, the rpm command will copy the new file with an extra file-name extension of .rpmnew.
+ </div><div class="para">
+ Similarly, %config(missingok) means that the file does not have to exist on disk. You can use this modifier for files or links that are created during the %post scripts but will need to be removed if the package is removed.
+ </div><div class="para">
+ Another special modifier, %ghost, tells the rpm command that the file should not be included in the package. You can use this to name the needed attributes for a file that the program, when installed, will create. For example, you may want to ensure that a program’s log file has certain attributes.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id732681" class="title">Setting file attributes</h1></div></div></div><div class="para">
+ When your package is installed, you can control the file attributes as well as the files that get included into the package. This is very useful since most packages are installed by the root user and you don’t always want the root user owning the files.
+ </div><div class="para">
+ The %attr directive allows you to control the permissions for a particular file. The format is:
+ </div><div class="para">
+ %attr(mode, user, group) filename
+ </div><div class="para">
+ For example:
+ </div><div class="para">
+ %attr(0644, root, root) /etc/yp.conf
+ </div><div class="para">
+ This example sets the file permissions to 644, the user and the group to root. If you don’t need to specify a value, use a dash, -, to leave the setting as is for the file. For example:
+ </div><div class="para">
+ %attr(-, root, -) /etc/yp.conf
+ </div><div class="para">
+ Note that you can combine directives, one after another. For example:
+ </div><div class="para">
+ %config %attr(-, root, -) /etc/yp.conf
+ </div><div class="para">
+ You can also use spaces instead of commas as delimiters. For example:
+ </div><div class="para">
+ %attr(0700 root root) %dir /var/tux
+ </div><div class="para">
+ </div><div class="para">
+ In addition to using %attr to set the attributes for a file, you should use the %defattr directive to set the default attributes for all files in the package. For example:
+ </div><div class="para">
+ %files
+ </div><div class="para">
+ %defattr(-,root,root)
+ </div><div class="para">
+ /usr/X11R6/bin/xtoolwait
+ </div><div class="para">
+ /usr/X11R6/man/man1/xtoolwait.*
+ </div><div class="para">
+ Just about every spec file uses the %defattr directive as this directive eliminates a lot of work you need to do to set file attributes individually. In addition, using the %defattr directive is considered a best practice when creating packages.
+ </div><div class="para">
+ You can also mark files for a particular language. For example, from the tcsh shell package:
+ </div><div class="para">
+ %files
+ </div><div class="para">
+ %defattr(-,root,root)
+ </div><div class="para">
+ %doc FAQ Fixes NewThings complete.tcsh eight-bit.txt tcsh.html
+ </div><div class="para">
+ %{_bindir}/tcsh
+ </div><div class="para">
+ %{_bindir}/csh
+ </div><div class="para">
+ %{_mandir}/*/*
+ </div><div class="para">
+ %lang(de) %{_datadir}/locale/de/LC_MESSAGES/tcsh*
+ </div><div class="para">
+ %lang(el) %{_datadir}/locale/el/LC_MESSAGES/tcsh*
+ </div><div class="para">
+ %lang(en) %{_datadir}/locale/en/LC_MESSAGES/tcsh*
+ </div><div class="para">
+ %lang(es) %{_datadir}/locale/es/LC_MESSAGES/tcsh*
+ </div><div class="para">
+ %lang(et) %{_datadir}/locale/et/LC_MESSAGES/tcsh*
+ </div><div class="para">
+ %lang(fi) %{_datadir}/locale/fi/LC_MESSAGES/tcsh*
+ </div><div class="para">
+ %lang(fr) %{_datadir}/locale/fr/LC_MESSAGES/tcsh*
+ </div><div class="para">
+ %lang(it) %{_datadir}/locale/it/LC_MESSAGES/tcsh*
+ </div><div class="para">
+ %lang(ja) %{_datadir}/locale/ja/LC_MESSAGES/tcsh*
+ </div><div class="para">
+ %lang(pl) %{_datadir}/locale/pl/LC_MESSAGES/tcsh*
+ </div><div class="para">
+ %lang(ru) %{_datadir}/locale/ru/LC_MESSAGES/tcsh*
+ </div><div class="para">
+ %lang(uk) %{_datadir}/locale/uk/LC_MESSAGES/tcsh*
+ </div><div class="para">
+ This example marks certain files as only being of use with particular languages, such as ja for the Japanese text and fr for the French text.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id611823" class="title">Verifying the %files section</h1></div></div></div><div class="para">
+ You can use the %verify directive to control which tests RPM uses when verifying a package.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ See <a class="xref" href="#ch-using-rpm-db">Cap. 4, <em>Using the RPM Database</em></a> for more on package verification.
+ </div><div class="para">
+ The %verify directive names the tests to include or not include. Table 10-4 lists the tests.
+ </div><div class="para">
+ Table 10-4 Package verification tests
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Test
+ </div>
+
+ </td><td>
+ <div class="para">
+ Usage
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ group
+ </div>
+
+ </td><td>
+ <div class="para">
+ Verifies the group of the file
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ maj
+ </div>
+
+ </td><td>
+ <div class="para">
+ Verifies the file’s major device number
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ md5
+ </div>
+
+ </td><td>
+ <div class="para">
+ Verifies the file’s MD5 checksum
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ min
+ </div>
+
+ </td><td>
+ <div class="para">
+ Verifies the file’s minor device number
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ mode
+ </div>
+
+ </td><td>
+ <div class="para">
+ Verifies the file mode, or permissions
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ mtime
+ </div>
+
+ </td><td>
+ <div class="para">
+ Verifies the file’s last modification time
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ owner
+ </div>
+
+ </td><td>
+ <div class="para">
+ Verifies the owner of the file
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ size
+ </div>
+
+ </td><td>
+ <div class="para">
+ Verifies the file’s size
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ symlink
+ </div>
+
+ </td><td>
+ <div class="para">
+ Verifies a symbolic link
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ With the %verify directive, you can name test, such as shown following:
+ </div><div class="para">
+ %verify(owner group size) /etc/yp.conf
+ </div><div class="para">
+ This example limits the tests to owner, group, and size. (The default is to perform all the tests.) You can also use the word not to specify that RPM should not run one or more tests. For example:
+ </div><div class="para">
+ %verify(not owner) /etc/yp.conf
+ </div><div class="para">
+ This example turns off just the owner test.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id587858" class="title">Filling the list of files automatically</h1></div></div></div><div class="para">
+ The -f option to the %files section allows you to read in a list of file names from a file. This file is assumed to look like the contents of the %files section, holding one file name per line. You can also include the various directives for files such as %attr or %doc. For example:
+ </div><div class="para">
+ %files -f list_of_filenames.txt
+ </div><div class="para">
+ You can combine this list with filename entries, such as the following:
+ </div><div class="para">
+ %files -f xconfig_files.txt
+ </div><div class="para">
+ %defattr(-,root,root)
+ </div><div class="para">
+ /usr/X11R6/bin/xtoolwait
+ </div><div class="para">
+ /usr/X11R6/man/man1/xtoolwait.1
+ </div><div class="para">
+ This example reads in a list of file names from the file named xconfig_files.txt and also includes two additional files.
+ </div><div class="para">
+ This list of files works best if you cannot determine the file names in advance. The build may create different files based on various macro values. In addition, you may not know the final paths for the files until build time.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id555916" class="title">Handling RPM build errors for unpackaged files</h1></div></div></div><div class="para">
+ Starting with RPM 4.1, rpmbuild will exit if all files in the $RPM_BUILD_ROOT directory are not found in the %files section (or in a file that lists file names used with the -f option). This is officially known as a Fascist build policy and you can turn it off with the following macros.
+ </div><div class="para">
+ The %_unpackaged_files_terminate_build macro, if set to 1, tells rpmbuild to exit if it finds files that are in the $RPM_BUILD_ROOT directory but not listed as part of the package. Set this macro to 0 to turn off the Fascist build policy. For example:
+ </div><div class="para">
+ %define _unpackaged_files_terminate_build 0
+ </div><div class="para">
+ You can also control the flag that specifies whether missing documentation files cause rpmbuild to exit. Set the %_missing_doc_files_terminate_build macro to 0 to turn off this feature:
+ </div><div class="para">
+ %define _missing_doc_files_terminate_build 0
+ </div><div class="para">
+ See the "Defining Spec File Macros" section later in the chapter for more on using macros.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ You can also store this setting in a macro file so that it applies for all packages you build. See <a class="xref" href="#ch-customizing-rpm">Cap. 20, <em>Customizing RPM Behavior</em></a> for more on macro files.
+ </div><div class="para">
+ While the Fascist build policy may be an annoyance, it can prove very useful. Chances are your spec file has an error if you have files in the $RPM_BUILD_ROOT directory that are not listed in the %files section. The Fascist build policy helps catch these errors. In addition, since the error outputs a list of files in the $RPM_BUILD_ROOT directory that are not listed in the %files section, you can often paste this list into your %files section.
+ </div></div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id581967" class="title">Adding Change Log Entries</h1></div></div></div><div class="para">
+ The change log usually appears at the end of a spec file and is marked with %changelog. It holds messages for each significant change. You should add a change log entry for each major change to the application. For example, if you download a new version of the software you are packaging, add a change log entry for the new version:
+ </div><div class="para">
+ %changelog
+ </div><div class="para">
+ * Fri Jun 21 2002 Bob Marley <marley at reggae.com>
+ </div><div class="para">
+ - Downloaded version 1.4, applied patches
+ </div><div class="para">
+ </div><div class="para">
+ * Tue May 08 2001 Peter Tosh <tosh at reggae.com> 1.3-1
+ </div><div class="para">
+ - updated to 1.3
+ </div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id673788" class="title">Defining Spec File Macros</h1></div></div></div><div class="para">
+ The RPM system defines a lot of handy macros so that your spec files can work regardless of where system directories are located. You simply use the macro, such as %_bindir, in place of hard-coded paths. The %_bindir macro, for example, identifies the default directory for binary executables, /usr/bin.
+ </div><div class="para">
+ Use these macros wherever possible to avoid hard-coded paths and settings.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id673805" class="title">Built-in macros</h1></div></div></div><div class="para">
+ RPM includes a host of built-in macros, including the following useful directories:
+ </div><div class="para">
+ %_prefix /usr
+ </div><div class="para">
+ %_exec_prefix %{_prefix}
+ </div><div class="para">
+ %_bindir %{_exec_prefix}/bin
+ </div><div class="para">
+ %_sbindir %{_exec_prefix}/sbin
+ </div><div class="para">
+ %_libexecdir %{_exec_prefix}/libexec
+ </div><div class="para">
+ %_datadir %{_prefix}/share
+ </div><div class="para">
+ %_sysconfdir %{_prefix}/etc
+ </div><div class="para">
+ %_sharedstatedir %{_prefix}/com
+ </div><div class="para">
+ %_localstatedir %{_prefix}/var
+ </div><div class="para">
+ %_libdir %{_exec_prefix}/lib
+ </div><div class="para">
+ %_includedir %{_prefix}/include
+ </div><div class="para">
+ %_oldincludedir /usr/include
+ </div><div class="para">
+ %_infodir %{_prefix}/info
+ </div><div class="para">
+ %_mandir %{_prefix}/man
+ </div><div class="para">
+ The example directories shown above come from the standard RPM macro file, /usr/lib/rpm/macros, instead of the Red Hat-specific file, /usr/lib/rpm/redhat/macros, which holds:
+ </div><div class="para">
+ </div><div class="para">
+ %_prefix /usr
+ </div><div class="para">
+ %_sysconfdir /etc
+ </div><div class="para">
+ %_localstatedir /var
+ </div><div class="para">
+ %_infodir /usr/share/info
+ </div><div class="para">
+ %_mandir /usr/share/man
+ </div><div class="para">
+ %_initrddir %{_sysconfdir}/rc.d/init.d
+ </div><div class="para">
+ %_defaultdocdir %{_usr}/share/doc
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id538862" class="title">Spec file-specific macros</h1></div></div></div><div class="para">
+ Most of the pre-defined RPM macros hold directory paths or architecture information. RPM also includes a set of useful macros that you can use to help debug problematic spec files and well as perform common tasks in spec files. Table 10-5 lists these debugging and special spec file macros.
+ </div><div class="para">
+ Table 10-5 Special spec-file macros
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Macro
+ </div>
+
+ </td><td>
+ <div class="para">
+ Usage
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ %dump
+ </div>
+
+ </td><td>
+ <div class="para">
+ Prints out macro values
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ %{echo:message}
+ </div>
+
+ </td><td>
+ <div class="para">
+ Prints message to stderr
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ %{error:message}
+ </div>
+
+ </td><td>
+ <div class="para">
+ Prints message to stderr and returns BADSPEC
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ %{expand:expression}
+ </div>
+
+ </td><td>
+ <div class="para">
+ Like eval, expands expression
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ %{F:file_exp}
+ </div>
+
+ </td><td>
+ <div class="para">
+ Expands file_exp to a file name
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ %global name value
+ </div>
+
+ </td><td>
+ <div class="para">
+ Defines a global macro
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ %{P:patch_exp}
+ </div>
+
+ </td><td>
+ <div class="para">
+ Expands patch_exp to a patch file name
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ %{S:source_exp}
+ </div>
+
+ </td><td>
+ <div class="para">
+ Expands source_exp to a source file name
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ %trace
+ </div>
+
+ </td><td>
+ <div class="para">
+ Toggles the printing of debugging information
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ %{uncompress:filename}
+ </div>
+
+ </td><td>
+ <div class="para">
+ Tests if file filename is compressed. If so, uncompresses and includes in the given context. If not compressed, calls cat to include file in given context.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ %undefine macro
+ </div>
+
+ </td><td>
+ <div class="para">
+ Undefines the given macro
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ %{warn:message}
+ </div>
+
+ </td><td>
+ <div class="para">
+ Prints message to stderr
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ Note
+ </div><div class="para">
+ To see the current list of macros, put a %dump at the start of your spec file.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id726602" class="title">Defining new macros</h1></div></div></div><div class="para">
+ In addition to the built-in macros, you can define your own to make it easier to manage your packages. Define a new spec file macro with the following syntax:
+ </div><div class="para">
+ %define macro_name value
+ </div><div class="para">
+ For example:
+ </div><div class="para">
+ %define major 2
+ </div><div class="para">
+ %define minor 2
+ </div><div class="para">
+ %define patchlevel 7
+ </div><div class="para">
+ You can then use a macro with the %macro_name or %{macro_name} syntax. For example:
+ </div><div class="para">
+ Version: %{major}.%{minor}.%{patchlevel}
+ </div><div class="para">
+ You can also expand the results of running shell commands using a %(command) syntax with parenthesis instead of curly braces. For example:
+ </div><div class="para">
+ %define today %(date)
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id578192" class="title">Specifying parameters to macros</h1></div></div></div><div class="para">
+ Most macros perform simple text substitution. You can also pass parameters to macros, and access those parameters within your macros, similarly to how shell scripts get command-line parameters.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ <a class="xref" href="#ch-scripting">Cap. 14, <em>Automating RPM with Scripts</em></a> covers shell scripting with RPM.
+ </div><div class="para">
+ With parameters, you can expand the normal definition of a macro to the following:
+ </div><div class="para">
+ %define macro_name(options) value
+ </div><div class="para">
+ Any text within the parenthesis is passed to getopt(3), and acts as parameters to the macro. This is performed when the macro is expanded. You can also pass options to the macro using the %macro_name syntax (without curly braces). For example:
+ </div><div class="para">
+ %foo 1 2 3
+ </div><div class="para">
+ This example passes the parameters 1, 2, and 3 to the macro foo. Inside the macro, you can use a shell script-like syntax to access the parameters through special macros. Table 10-6 lists these macros.
+ </div><div class="para">
+ Table 10-6 Parameter macros inside a macro expansion
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Macro
+ </div>
+
+ </td><td>
+ <div class="para">
+ Holds
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ %0
+ </div>
+
+ </td><td>
+ <div class="para">
+ The name of the macro
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ %*
+ </div>
+
+ </td><td>
+ <div class="para">
+ All the parameters to the macro, except for any processed options
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ %#
+ </div>
+
+ </td><td>
+ <div class="para">
+ The number of parameters
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ %1
+ </div>
+
+ </td><td>
+ <div class="para">
+ The first parameter
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ %2
+ </div>
+
+ </td><td>
+ <div class="para">
+ The second parameter
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ %3
+ </div>
+
+ </td><td>
+ <div class="para">
+ The third parameter, and so on with %4, %5 and beyond
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ %{-p}
+ </div>
+
+ </td><td>
+ <div class="para">
+ Holds -p if the -p parameter was passed to the macro; otherwise holds nothing
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ %{-p*}
+ </div>
+
+ </td><td>
+ <div class="para">
+ Holds the value passed with the -p parameter, if the -p parameter was passed to the macro; otherwise holds nothing
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ %{-p:text}
+ </div>
+
+ </td><td>
+ <div class="para">
+ Holds text if the -p parameter was passed to the macro; otherwise holds nothing
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ Note that all parameters listed in Table 10-6 hold the remaining parameters after getopt(3) processing. You can use these macros within the definition of your own macros. You can also nest macros, such as the following:
+ </div><div class="para">
+ %define mypatch() patch %{-p:-p%{-p*}}
+ </div><div class="para">
+ This macro expands to the patch command if no -p parameter was passed. If you pass a -p parameter, such as -p 1, then the macro expands to -p with the value of the -p parameter:
+ </div><div class="para">
+ patch -p1
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ This type of syntax is used heavily with the patch command.
+ </div></div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id756998" class="title">Creating XML Spec Files</h1></div></div></div><div class="para">
+ RPM spec files are text files containing structured information. It is a natural progression to write RPM spec files using XML. The tool rpmxmlbuild will build an RPM package from an XML-formatted spec file.
+ </div><div class="para">
+ For example, Listing 10-1 holds a spec file in XML format.
+ </div><div class="para">
+ Listing 10-1: An XML spec file.
+ </div><div class="para">
+ <?xml version="1.0"?>
+ </div><div class="para">
+ <spec distribution="RPM Test" vendor="rpm.org"
+ </div><div class="para">
+ name="bash" version="2.05a" release="02test"
+ </div><div class="para">
+ copyright="GPL"
+ </div><div class="para">
+ url="http://www.gnu.org/software/bash/bash.html">
+ </div><div class="para">
+ </div><div class="para">
+ <source name="%{name}-%{version}.tar.bz2"
+ </div><div class="para">
+ size="1434025" md5="c29b50db808003e39558a0f6354f4cad"
+ </div><div class="para">
+ path="%{name}-%{version}">
+ </div><div class="para">
+ </source>
+ </div><div class="para">
+ </div><div class="para">
+ <buildrequires>
+ </div><div class="para">
+ <require name="bash" />
+ </div><div class="para">
+ <require name="gcc" />
+ </div><div class="para">
+ <require name="make" />
+ </div><div class="para">
+ </buildrequires>
+ </div><div class="para">
+ </div><div class="para">
+ <!-- packages -->
+ </div><div class="para">
+ <package group="System/Base" autoreqprov="no">
+ </div><div class="para">
+ <requires>
+ </div><div class="para">
+ <require name="glibc" />
+ </div><div class="para">
+ </requires>
+ </div><div class="para">
+ <summary>The Bash package contains the bash program.</summary>
+ </div><div class="para">
+ <description>%{summary}
+ </div><div class="para">
+ Bash is the Bourne-Again SHell, which is a widely used command interpreter
+ </div><div class="para">
+ on Unix systems. Bash is a program that reads from standard input, the
+ </div><div class="para">
+ keyboard. A user types something and the program will evaluate what he has
+ </div><div class="para">
+ typed and do something with it, like running a program.</description>
+ </div><div class="para">
+ <files list="%{name}.files.lst" />
+ </div><div class="para">
+ </package>
+ </div><div class="para">
+ </div><div class="para">
+ <package name="bash-doc" group="Documentation/System/Base" autoreqprov="no">
+ </div><div class="para">
+ <requires>
+ </div><div class="para">
+ <require name="%{name}" />
+ </div><div class="para">
+ </requires>
+ </div><div class="para">
+ <summary>Documentation for the bash package.</summary>
+ </div><div class="para">
+ <description>%{summary}</description>
+ </div><div class="para">
+ <pre script="%{name}-doc.pre.sh" />
+ </div><div class="para">
+ <files list="%{name}-doc.files.lst" />
+ </div><div class="para">
+ </package>
+ </div><div class="para">
+ </div><div class="para">
+ <!-- scripts to create the package -->
+ </div><div class="para">
+ <prep script="%{name}.prep.sh">
+ </div><div class="para">
+ <setup />
+ </div><div class="para">
+ <script>echo &quot;Prep completed&quot;</script>
+ </div><div class="para">
+ </prep>
+ </div><div class="para">
+ <build script="%{name}.build.sh" />
+ </div><div class="para">
+ <install script="%{name}.install.sh" />
+ </div><div class="para">
+ <clean script="%{name}.clean.sh" />
+ </div><div class="para">
+ </div><div class="para">
+ <!-- changelog -->
+ </div><div class="para">
+ <changelog>
+ </div><div class="para">
+ <changes date="Mon Aug 26 2002" version="2.05a-02test"
+ </div><div class="para">
+ author="" author-email="">
+ </div><div class="para">
+ <change>Added setup macro to extract files</change>
+ </div><div class="para">
+ <change>Initial version ready for jbj</change>
+ </div><div class="para">
+ </changes>
+ </div><div class="para">
+ </changelog>
+ </div><div class="para">
+ </spec>
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ XML spec files are a very experimental feature. Future releases of RPM will likely provide more support for XML spec files. The format will likely change.
+ </div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id1413321" class="title">Summary</h1></div></div></div><div class="para">
+ This chapter covers spec files, the files that define how to build packages. Start your spec file by defining package information, such as the name, version, and release number. You can also add a detailed description to help administrators decide whether to install your packages.
+ </div><div class="para">
+ You need to name all of the source and patch files used to build the package. In most cases, the source files are compressed tar archives. After naming all the sources and patches, you need to control how the rpmbuild command should build your package. This comes in four sections.
+ </div><div class="para">
+ The %prep section prepares for the build by extracting the source files and applying patches. The %build section defines the commands to build the software, normally something as simple as running a configure script and then the make command. The %install section contains the commands for installing the software. And, the %clean section provides commands to clean up after the build.
+ </div><div class="para">
+ For these sections, you can use handy RPM macros for common tasks, such as running the configure script or the make install command. You can also define scripts the rpm command should run before and after installing, as well as before and after removing the package.
+ </div><div class="para">
+ Spec files contain a listing of all the files that should go into the package, as well as where those files should be placed on the user’s hard disk.
+ </div><div class="para">
+ You can define RPM macros in your spec files to make commands that can work with different directory structures as well as simplify common commands.
+ </div><div class="para">
+ While it may seem that this chapter described a great many options for making spec files, there’s more to come. The next chapter covers advanced spec file topics such as triggers, conditional builds, and specifying dependencies.
+ </div></div></div><div xml:lang="ro" class="chapter" id="ch-advanced-packaging" lang="ro"><div class="titlepage"><div><div><h2 class="title">Cap. 10. Creare avansată pachete RPM</h2></div></div></div><div class="toc"><dl><dt><span class="sect1"><a href="#id862470">10.1. Definirea dependențelor pachetelor</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id739772">10.1.1. Numirea dependențelor</a></span></dt><dt><span class="sect2"><a href="#id749803">10.1.2. Setarea premiselor</a></span></dt><dt><span class="sect2"><a href="#id550502">10.1.3. Numirea dependențelor de construcție</a></span></dt><dt><span class="sect2"><a href="#id550512">10.1.4. Generarea automată de dependențe</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id523284">10.2. Setarea triggerelor</a></span></dt><dt><span class="sect1"><a href="#id864441">10.3. Scrierea scripturilor de verificare</a></span></dt><dt><span class="sect1"><a href="#id919420">10.4. Crearea subpachetelor.</a><
/span></dt><dd><dl><dt><span class="sect2"><a href="#id680225">10.4.1. Furnizarea informațiilor pentru subpachete</a></span></dt><dt><span class="sect2"><a href="#id1413121">10.4.2. Definirea scripturilor pentru subpachete</a></span></dt><dt><span class="sect2"><a href="#id919281">10.4.3. Construirea subpachetelor</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id864110">10.5. Creating Relocatable Packages</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id670616">10.5.1. Setting up the prefixes</a></span></dt><dt><span class="sect2"><a href="#id773908">10.5.2. Define the files section</a></span></dt><dt><span class="sect2"><a href="#id831211">10.5.3. Problems creating relocatable packages</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id777632">10.6. Defining Conditional Builds</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id676244">10.6.1. Defining conditional macros</a></span></dt><dt><span class="sect2"><a href="#id970594">10.6.
2. Using conditional blocks</a></span></dt><dt><span class="sect2"><a href="#id679472">10.6.3. Using architecture-based conditionals</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id790812">10.7. Summary</a></span></dt></dl></div><div class="para">
+ Acest capitol acoperă:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Se definește informația despre dependențele pachetelor
+ </div></li><li class="listitem"><div class="para">
+ Setare trigger-e
+ </div></li><li class="listitem"><div class="para">
+ Scriere scripturi de verificare
+ </div></li><li class="listitem"><div class="para">
+ Creare subpachete
+ </div></li><li class="listitem"><div class="para">
+ Creare pachete relocabile
+ </div></li><li class="listitem"><div class="para">
+ Definire construcții condiționale
+ </div></li></ul></div><div class="para">
+ Capitolul anterior a introdus fișierul spec RPM, care controlează cum sunt construite și instalate pachetele RPM. Acest capitol intră mai adânc în subiecte mai avansate despre fișiere spec cum ar fi utilizarea comenzilor condiționale și creare de pachete relocabile, începând cu instrucțiuni despre cum să specificați dependențele pachetelor
+ </div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id862470" class="title">Definirea dependențelor pachetelor</h1></div></div></div><div class="para">
+ Dependențele sunt una dintre cele mai importante părți ale sistemului RPM. Baza de date RPM caută dependențele între pachete pentru a vă permite să vă administrați sistemul mai bine. Dependențele apar când un pachet depinde de un altul. Sistemul RPM se asigură că dependențele sunt îndeplinite la actualizare, instalare sau la ștergerea pachetelor. Pornind de la acest concept simplu, RPM suportă patru tipuri de dependențe:
+ </div><div class="para">
+ *Requirements (cerințe), unde un pachet cere o capabilitate asigurată de către alt pachet.
+ </div><div class="para">
+ *Provides (asigură), o listă de capabilități asigurate de pachetul dvs.
+ </div><div class="para">
+ *Conflicts (conflict), unde un pachet este în conflict cu o capabilitate asigurată de alt pachet
+ </div><div class="para">
+ *Obsoletes (scos din uz), unde un pachet scoate din uz capabilitățiasigurate de un altul.
+ </div><div class="para">
+ Referință încrucișată
+ </div><div class="para">
+ <a class="xref" href="#ch-dependencies">Cap. 5, <em>Package Dependencies</em></a> are mai multe informații despre dependențe.Dependențele tip obsoletes sunt folosite de obicei doar când un pachet este redenumit, ca de exemplu pachetul apache care a devenit httpd, începând cu Red Hat Linux 8.0. Pachetul httpd scoate din uz pachetul apache.
+ </div><div class="para">
+ Puteți enumera toate dependențele în fișierul dvs. spec. Cea mai folosită informație legată de dependențe este cea legată de cerințele unui pachet.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id739772" class="title">Numirea dependențelor</h1></div></div></div><div class="para">
+ În fișierele dvs. spec puteți numi dependențele pentru pachetul dvs. Sintaxa de bază este:
+ </div><div class="para">
+ Requires: capabilitate
+ </div><div class="para">
+ În cele mai multe cazuri, capabilitatea ar trebui să fie numele unui alt pachet. Acest exemplu setează o dependență de tip requires. Acest lucru înseamnă că pachetul cere acea capabilitate. Folosiți o sintaxă asemănătoare și la alte tipuri de dependențe:
+ </div><div class="para">
+ Provides: capabilitate
+ </div><div class="para">
+ Obsoletes: capabilitate
+ </div><div class="para">
+ Conflicts: capabilitate
+ </div><div class="para">
+ Puteți pune mai mult de o singură capabilitate pe linia cu dependențele. De exemplu:
+ </div><div class="para">
+ Requires: bash perl
+ </div><div class="para">
+ Puteți folosi spații sau virgule pentru a separa capabilitățile. De exemplu:
+ </div><div class="para">
+ Requires: bash, perl
+ </div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id606839" class="title">Specificarea versiunii dependențelor</h1></div></div></div><div class="para">
+ Puteți adăuga și informații despre versiune, de exemplu:
+ </div><div class="para">
+ Requires: bash >= 2.0
+ </div><div class="para">
+ Aceasta înseamnă că pachetul cere capabilitatea bash (un pachet) cu versiunea 2.0 sau mai sus. Aceeași logică se aplică la alte tipuri de dependențe.Spre exemplu:
+ </div><div class="para">
+ Conflicts: bash >= 2.0
+ </div><div class="para">
+ Acest exemplu arată că pachetul este în conflict cu toate versiunile bash 2.0 sau mai recente
+ </div><div class="para">
+ Tabelul 11-1 enumerează comparațiile de versiuni pe care le puteți folosi.
+ </div><div class="para">
+ Tabel 11-1 Comparații de versiuni dependențe
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Comparație
+ </div>
+
+ </td><td>
+ <div class="para">
+ Semnificație
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ pachet < versiune
+ </div>
+
+ </td><td>
+ <div class="para">
+ Un pachet de versiune mai veche
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ pachet > versiune
+ </div>
+
+ </td><td>
+ <div class="para">
+ Un pachet de versiune mai nouă
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ pachet >= versiune
+ </div>
+
+ </td><td>
+ <div class="para">
+ Un pachet de versiune mai nouă sau la fel
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ pachet <= versiune
+ </div>
+ <div class="para">
+ </div>
+
+ </td><td>
+ <div class="para">
+ Un pachet de versiune mai veche sau la fel
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ pachet = versiune
+ </div>
+
+ </td><td>
+ <div class="para">
+ Un pachet de versiune egală
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ pachet
+ </div>
+
+ </td><td>
+ <div class="para">
+ Pachet la orice versiune
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ RPM suportă o sintaxă extinsă pentru compararea versiunilor. Acesta esteformatul complet:
+ </div><div class="para">
+ Perioadă:Versiune-Lansare
+ </div><div class="para">
+ De exemplu:
+ </div><div class="para">
+ 1:5.6.0-17
+ </div><div class="para">
+ În acest caz, perioada este 1, versiunea este 5.6.0 iar lansarea este 17.În cele mai multe cazuri veți avea nevoie doar de versiune. Perioada permitemanevrarea versiunilor greu de comparat. Numărul de lansare nu este folosit aproape niciodată. Acest lucru are sens pentru că leagă o dependență de o anumităconstrucție a pachetului RPM mai degrabă decât de o versiune a programului în sine.Acest tip de dependență poate fi de folos doar dacă schimbați radical modul deconstrucție al unui pachet.
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id813678" class="title">Creare CAPABILITIES virtuale</h1></div></div></div><div class="para">
+ Dependențele sunt bazate pe capabilități, cele mai multe dintre acestea fiindpachete. Puteți crea capabilități virtuale, care sunt doar nume definite de dvs.De exemplu, pachetul sendmail asigură o capabilitate virtuală numită smtpdaemon.De exemplu:
+ </div><div class="para">
+ Provides: smtpdaemon
+ </div><div class="para">
+ Această capabilitate se referă la serviciul general SMTP pentru trimitereamesajelor e-mail. Nu există un fișier cu acest nume. Este doar o capabilitate,text arbitrar. Alte pachete cer această capabilitate, cum ar fi aplicațiafetchmail de descărcare și forwardare e-mail, și mutt, un client de mail.
+ </div><div class="para">
+ Prin folosirea unei capabilități virtuale, alte pachete pot asigura capabilitatea, și, cel mai important, aplicațiile client pot cere această capabilitate fără a trebui să știe ce pachet asigură capabilitatea de a trimite mesaje e-mail. De exemplu, pachetele exim și postfix, agenți de transport mail ca și sendmail, pot asiguraaceeași capabilitate.
+ </div><div class="para">
+ Notă
+ </div><div class="para">
+ Desigur, veți dori să vă asigurați că aceste pachete intră în conflict unelecu altele.
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id561328" class="title">Numirea dependențelor în motoare de scripting și module</h1></div></div></div><div class="para">
+ Limbaje de scripting ca Perl sau Tcl permit module adiționale. Pachetul dvs. poate avea nevoie de unele dintre aceste module. RPM folosește o sintaxă specialăcu paranteze pentru a indica dependențe de module de scripting. De exemplu:
+ </div><div class="para">
+ Requires: perl(Carp) >= 3.2
+ </div><div class="para">
+ Aceasta indică o cerere pentru modulul adițional Carp pentru Perl, cu o versiune mai recentă sau egală cu 3.2.
+ </div></div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id749803" class="title">Setarea premiselor</h1></div></div></div><div class="para">
+ O premisă este similară cu o dependență require, doar că o premisătrebuie instalată înainte de un anume pachet. Specificați o premisă după cum urmează:
+ </div><div class="para">
+ PreReq: capability
+ </div><div class="para">
+ Puteți include dependențe cu număr-versiune, cum ar fi:
+ </div><div class="para">
+ PreReq: capability >= version
+ </div><div class="para">
+ De obicei, o PreReq: se comportă ca o Requires:, de fapt, directiva PreReq:există doar pentru a permite ordonarea manuală a dependențelor. RPM garantează că pachetul PreReq: va fi instalat înainte de pachetul care numește dependențaPreReq: .
+ </div><div class="para">
+ Referință încrucișată
+ </div><div class="para">
+ <a class="xref" href="#ch-packaging-guidelines">Cap. 13, <em>Packaging Guidelines</em></a> descrie problema comună detratare a dependențelor circulare folosind premise.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id550502" class="title">Numirea dependențelor de construcție</h1></div></div></div><div class="para">
+ Pachetul dvs., odată construit, are un set de dependențe. Aceste dependențe sunt importante pentru oricine care instalează pachetul. Dar există și probleme cu dependențele la construirea pachetelor. Dependențele de construcție vă permit să precizați de ce este nevoie pentru a construi pachetul. Chiar dacă credeți că acest lucru e același cu ce este necesar pentru a instala pachetul, în mod normal nu este așa. Distribuțiile de Linux tind să împartă software-ul în pachete necesare la rulare și pachete pentru dezvoltatori (runtime și development)De exemplu, pachetul python conține runtime-ul necesar pentru executarea scripturilorscrise în Python. Pachetul python-devel asigură abilitatea de a scrie extensii ale limbajului Python
+ </div><div class="para">
+ RPM vă permite să definiți dependențe în timpul construirii în fișierele dvs. spec folosind următoarele directive:
+ </div><div class="para">
+ BuildRequires:
+ </div><div class="para">
+ BuildConflicts:
+ </div><div class="para">
+ BuildPreReq:
+ </div><div class="para">
+ Aceste directive se comportă ca Requires:, Conflicts:, respectiv PreReq:, exceptând faptul că dependențele sunt necesare pentru construirea pachetului, nu pentru instalarea lui. De exemplu, pachetul dvs. poate avea nevoie de un compilator C pentru construcție, sau ar putea avea nevoie de un instrument special de construit sau o bibliotecă de dezvoltare
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id550512" class="title">Generarea automată de dependențe</h1></div></div></div><div class="para">
+ Pentru că multe dependențe sunt legate de bibliotecile shared, sistemul RPM va genera automat dependențe provide pentru orice fișier din pachetele dvs.care este obiect shared sau fișier .so. RPM va genera de asemenea dependențerequire pentru toate fișierele din lista %files care cer biblioteci shared.Pentru a realiza acest lucru, RPM folosește comanda ldd, care determină bibliotecile shared folosite de o aplicație.
+ </div><div class="para">
+ în plus, scripturile find-requires și find-provides din /usr/lib/rpm pot determina dependențele scripturilor Perl, Python și Tcl și alte dependențe,cum ar fi dependențele pachetelor Java, în mod automat. Scriptul find-requiresdetermină dependențele requires automat, iar scriptul find-provides determină dependențele provides
+ </div><div class="para">
+ Referință încrucișată
+ </div><div class="para">
+ <a class="xref" href="#ch-packaging-guidelines">Cap. 13, <em>Packaging Guidelines</em></a> tratează oprirea generării automate a dependențelor.
+ </div></div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id523284" class="title">Setarea triggerelor</h1></div></div></div><div class="para">
+ Triggerele oferă posibilități unui pachet de a acționa când statusul de instalare al altui pachet se schimbă. Un trigger este un script pe care îl definiți în fișierul spec al pachetului dvs. care este rulat de sistemulRPM când statusul unui anume pachet se schimbă. Dacă pachetul dvs. depindeîntr-un anume fel de alt pachet, un trigger poate permite pachetului dvs. săse ocupe de schimbările din celălalt pachet
+ </div><div class="para">
+ Triggerele nu sunt un înlocuitor pentru dependențele pachetelor. În schimb,triggerele sunt folositoare când doriți să schimbați instalarea unui pachetîn funcție de alte pachete instalate. De exemplu, dacă pachetul dvs. este unclient de mail, pachetul dvs. va avea nevoie de un agent de transfer mail, sauMTA. Linux suportă mai mulți agenți de transfer mail, cum ar fi sendmail, vmailexim, qmail și postfix
+ </div><div class="para">
+ În mod uzual un sistem va avea un agent de transfer mail instalat. În cele mai multe cazuri, pentru un client de mail nu va conta ce MTA este instalat,atâta timp cât există. (De fapt, mare parte din aceste pachete ar trebui marcate ca fiind în conflict, asigurându-ne astfel că un sistem dat poateavea doar unul.)
+ </div><div class="para">
+ Scriptul %triggerin este rulat când un anume pachet-țintă este instalat sau actualizat. Scriptul %triggerin este de asemenea rulat când pachetul dvs esteinstalat sau actualizat, cu condiția ca pachetul-țintă să fie deja instalat.La fel, scriptul %triggerun este rulat dacă pachetul-țintă este dezinstalat.Este de asemenea rulat dacă pachetul dvs. este dezinstalat și pachetul-țintăeste instalat. Scriptul %triggerpostun este rulat după ce pachetul-țintă a fostdezinstalat. Nu este rulat dacă pachetul dvs. este dezinstalat.
+ </div><div class="para">
+ Pentru a defini unul dintre aceste scripturi, este necesar să specificaținumele pachetului-țintă; de exemplu:
+ </div><div class="para">
+ %triggerin -- tcsh
+ </div><div class="para">
+ comenzi script...
+ </div><div class="para">
+ Acest exemplu setează un trigger pentru pachetul tcsh. Dacă pachetul tcsh este instalat sau actualizat, RPM va rula scriptul. Dacă pachetul dvs. este instalat sau actualizat și pachetul tcsh este instalat, RPM de asemenea va rula scriptul.
+ </div><div class="para">
+ Definiți scriptul %triggerun în mod similar:
+ </div><div class="para">
+ triggerun -- tcsh
+ </div><div class="para">
+ comenzi script...
+ </div><div class="para">
+ Puteți folosi de asemenea numere de versiune în definiția scriptului triggerpentru a rula scriptul doar în cazul unei anumite versiuni. De exemplu:
+ </div><div class="para">
+ %triggerpostun -- vixie-cron < 3.0.1-56
+ </div><div class="para">
+ /sbin/chkconfig --del crond
+ </div><div class="para">
+ /sbin/chkconfig --add crond
+ </div><div class="para">
+ Acest exemplu, din pachetul de planificare vixie-cron, rulează un triggerpost-uninstall (postdezinstalare) pentru același pachet, dar pentru versiunimai vechi. Pentru a defini scripturi trigger pentru versiuni specifice, folosiți aceeași sintaxă ca pentru dependențele requires la stabilirea versiunii și a comparațiilor.
+ </div><div class="para">
+ Triggerele sunt rulate prin /bin/sh, cel mai folosit motor de shell scripting. Folosind opțiunea -p totuși, puteți specifica un alt interpretor de scripting. De exemplu, pentru a scrie un script Perl, definiți triggerulca mai jos:
+ </div><div class="para">
+ %triggerpostun -p /usr/bin/perl -- vixie-cron < 3.0.1-56
+ </div><div class="para">
+ system("/sbin/chkconfig --del crond");
+ </div><div class="para">
+ system("/sbin/chkconfig --add crond");
+ </div><div class="para">
+ Prin subpachete, definite în cele ce urmează, puteți folosi o opțiune -npentru a lega scriptul trigger de un subpachet. De exemplu:
+ </div><div class="para">
+ %triggerpostun -n subpackage_name -- vixie-cron < 3.0.1-56
+ </div><div class="para">
+ /sbin/chkconfig --del crond
+ </div><div class="para">
+ /sbin/chkconfig --add crond
+ </div><div class="para">
+ În scripturile dvs trigger, $1, primul argument al liniei de comanda, conține numărul de instanțe ale pachetului dvs. care vor rămâne după completarea operațiunii.Al doilea argument, $2, conține numărul de instanțe ale pachetului-țintă care vor rămâne după operațiune. Astfel, dacă $2 e 0, pachetul-țintă va fi dezinstalat.
+ </div><div class="para">
+ Pachetul anonftp, menționat în <a class="xref" href="#ch-dependencies">Cap. 5, <em>Package Dependencies</em></a>, are multe triggere. Multe dintre ele fac disponibile mai multe comenzi pentru pachetul anonftp. Acest pachet de rețea este de asemenea legat strâns de versiunea bibliotecii de C, glibc, după cum se vede în lista 11-1
+ </div><div class="para">
+ Lista 11-1: Scripturile trigger ale pachetului anonftp.
+ </div><div class="para">
+ triggerin -- glibc
+ </div><div class="para">
+ copy() { file="`ls --sort=time $1 |head -n 1`"; ln -f "$file" "$2" 2>/dev/null |
+ </div><div class="para">
+ | cp -df "$file" "$2"; }
+ </div><div class="para">
+ # Terminare versiuni mai vechi
+ </div><div class="para">
+ rm -f /var/ftp/lib/ld-* /var/ftp/lib/libc* /var/ftp/lib/libnsl* /var/ftp/lib/lib
+ </div><div class="para">
+ nss_files* &>/dev/null || :
+ </div><div class="para">
+ # Părți copie din glibc, de care este nevoie în bin.
+ </div><div class="para">
+ LIBCVER=`basename $(ls --sort=time /lib/libc-*.so |head -n 1) .so |cut -f2- -d-`
+ </div><div class="para">
+ copiere /lib/ld-${LIBCVER}.so /var/ftp/lib
+ </div><div class="para">
+ copiere /lib/libc-${LIBCVER}.so /var/ftp/lib
+ </div><div class="para">
+ copiere /lib/libnsl-${LIBCVER}.so /var/ftp/lib
+ </div><div class="para">
+ copiere /lib/libnss_files-${LIBCVER}.so /var/ftp/lib
+ </div><div class="para">
+ md5sum /var/ftp/lib/lib*-*.so /var/ftp/lib/libtermcap.so.*.*.* 2>/dev/null >/var
+ </div><div class="para">
+ /ftp/lib/libs.md5
+ </div><div class="para">
+ chmod 0400 /var/ftp/lib/libs.md5
+ </div><div class="para">
+ # Folosiți ldconfig pentru a construi legături simbolice și așa mai departe.
+ </div><div class="para">
+ [ ! -e /var/ftp/etc/ld.so.conf ] && touch /var/ftp/etc/ld.so.conf
+ </div><div class="para">
+ /sbin/ldconfig -r /var/ftp
+ </div><div class="para">
+ </div><div class="para">
+ %triggerin -- fileutils
+ </div><div class="para">
+ copy() { file="`ls --sort=time $1 |head -n 1`"; ln -f "$file" "$2" 2>/dev/null |
+ </div><div class="para">
+ | cp -df "$file" "$2"; }
+ </div><div class="para">
+ copiere /bin/ls /var/ftp/bin
+ </div><div class="para">
+ md5sum `ls /var/ftp/bin/* |grep -v bin.md5` >/var/ftp/bin/bin.md5
+ </div><div class="para">
+ chmod 0400 /var/ftp/bin/bin.md5
+ </div><div class="para">
+ </div><div class="para">
+ %triggerin -- cpio
+ </div><div class="para">
+ copy() { file="`ls --sort=time $1 |head -n 1`"; ln -f "$file" "$2" 2>/dev/null |
+ </div><div class="para">
+ | cp -df "$file" "$2"; }
+ </div><div class="para">
+ copiere /bin/cpio /var/ftp/bin
+ </div><div class="para">
+ md5sum `ls /var/ftp/bin/* |grep -v bin.md5` >/var/ftp/bin/bin.md5
+ </div><div class="para">
+ chmod 0400 /var/ftp/bin/bin.md5
+ </div><div class="para">
+ </div><div class="para">
+ %triggerin -- tar
+ </div><div class="para">
+ copy() { file="`ls --sort=time $1 |head -n 1`"; ln -f "$file" "$2" 2>/dev/null |
+ </div><div class="para">
+ | cp -df "$file" "$2"; }
+ </div><div class="para">
+ copiere /bin/tar /var/ftp/bin
+ </div><div class="para">
+ md5sum `ls /var/ftp/bin/* |grep -v bin.md5` >/var/ftp/bin/bin.md5
+ </div><div class="para">
+ chmod 0400 /var/ftp/bin/bin.md5
+ </div><div class="para">
+ </div><div class="para">
+ %triggerin -- gzip
+ </div><div class="para">
+ copy() { file="`ls --sort=time $1 |head -n 1`"; ln -f "$file" "$2" 2>/dev/null |
+ </div><div class="para">
+ | cp -df "$file" "$2"; }
+ </div><div class="para">
+ copiere /bin/gzip /var/ftp/bin
+ </div><div class="para">
+ ln -sf gzip /var/ftp/bin/zcat
+ </div><div class="para">
+ md5sum `ls /var/ftp/bin/* |grep -v bin.md5` >/var/ftp/bin/bin.md5
+ </div><div class="para">
+ chmod 0400 /var/ftp/bin/bin.md5
+ </div><div class="para">
+ </div><div class="para">
+ %triggerin -- libtermcap
+ </div><div class="para">
+ copy() { file="`ls --sort=time $1 |head -n 1`"; ln -f "$file" "$2" 2>/dev/null |
+ </div><div class="para">
+ | cp -df "$file" "$2"; }
+ </div><div class="para">
+ rm -f /var/ftp/lib/libtermcap.so.*.*.* &>/dev/null || :
+ </div><div class="para">
+ copiere '/lib/libtermcap.so.*.*.*' /var/ftp/lib
+ </div><div class="para">
+ md5sum /var/ftp/lib/lib*-*.so /var/ftp/lib/libtermcap.so.*.*.* 2>/dev/null >/var
+ </div><div class="para">
+ /ftp/lib/libs.md5
+ </div><div class="para">
+ chmod 0400 /var/ftp/lib/libs.md5
+ </div><div class="para">
+ # Folosiți ldconfig pentru a construi legături simbolice și așa mai departe.
+ </div><div class="para">
+ [ ! -e /var/ftp/etc/ld.so.conf ] && touch /var/ftp/etc/ld.so.conf
+ </div><div class="para">
+ /sbin/ldconfig -r /var/ftp
+ </div><div class="para">
+ </div><div class="para">
+ %triggerin -- ncompress
+ </div><div class="para">
+ copy() { file="`ls --sort=time $1 |head -n 1`"; ln -f "$file" "$2" 2>/dev/null |
+ </div><div class="para">
+ | cp -df "$file" "$2"; }
+ </div><div class="para">
+ copiere /usr/bin/compress /var/ftp/bin
+ </div><div class="para">
+ md5sum `ls /var/ftp/bin/* |grep -v bin.md5` >/var/ftp/bin/bin.md5
+ </div><div class="para">
+ chmod 0400 /var/ftp/bin/bin.md5
+ </div><div class="para">
+ </div><div class="para">
+ %triggerpostun -- anonftp 4.0
+ </div><div class="para">
+ if [ "$2" != 1 ] ; then
+ </div><div class="para">
+ # Utilizatorul are mai multe pachete glibc instalate. Nu putem citi
+ </div><div class="para">
+ # mintea utilizatorului, deci nu se va face nimic.
+ </div><div class="para">
+ exit 0
+ </div><div class="para">
+ fi
+ </div><div class="para">
+ copy() { file="`ls --sort=time $1 |head -n 1`"; ln -f "$file" "$2" 2>/dev/null |
+ </div><div class="para">
+ | cp -df "$file" "$2"; }
+ </div><div class="para">
+ # Terminare versiuni mai vechi
+ </div><div class="para">
+ rm -f /var/ftp/lib/ld-* /var/ftp/lib/libc* /var/ftp/lib/libnsl* /var/ftp/lib/lib
+ </div><div class="para">
+ nss_files* &>/dev/null || :
+ </div><div class="para">
+ # Părți copie din glibc, de care este nevoie în bin.
+ </div><div class="para">
+ LIBCVER=`basename /lib/libc-*.so .so | cut -f2- -d-`
+ </div><div class="para">
+ copiere /lib/ld-${LIBCVER}.so /var/ftp/lib
+ </div><div class="para">
+ copiere /lib/libc-${LIBCVER}.so /var/ftp/lib
+ </div><div class="para">
+ copiere /lib/libnsl-${LIBCVER}.so /var/ftp/lib
+ </div><div class="para">
+ copiere /lib/libnss_files-${LIBCVER}.so /var/ftp/lib
+ </div><div class="para">
+ copiere /bin/ls /var/ftp/bin
+ </div><div class="para">
+ copiere /bin/cpio /var/ftp/bin
+ </div><div class="para">
+ copiere /bin/tar /var/ftp/bin
+ </div><div class="para">
+ copiere /bin/gzip /var/ftp/bin
+ </div><div class="para">
+ ln -sf gzip /var/ftp/bin/zcat
+ </div><div class="para">
+ copiere /usr/bin/compress /var/ftp/bin
+ </div><div class="para">
+ rm -f /var/ftp/lib/libtermcap.so.*.*.* &>/dev/null || :
+ </div><div class="para">
+ copiere '/lib/libtermcap.so.*.*.*' /var/ftp/lib
+ </div><div class="para">
+ # Folosiți ldconfig pentru a construi legături simbolice și așa mai departe.
+ </div><div class="para">
+ [ ! -e /var/ftp/etc/ld.so.conf ] && touch /var/ftp/etc/ld.so.conf
+ </div><div class="para">
+ /sbin/ldconfig -r /var/ftp
+ </div><div class="para">
+ # Generare md5sum pentru verifyscript (script de verificare)
+ </div><div class="para">
+ md5sum /var/ftp/lib/lib*-*.so /var/ftp/lib/libtermcap.so.*.*.* 2>/dev/null >/var
+ </div><div class="para">
+ /ftp/lib/libs.md5
+ </div><div class="para">
+ chmod 0400 /var/ftp/lib/libs.md5
+ </div><div class="para">
+ md5sum `ls /var/ftp/bin/* |grep -v bin.md5` >/var/ftp/bin/bin.md5
+ </div><div class="para">
+ chmod 0400 /var/ftp/bin/bin.md5
+ </div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id864441" class="title">Scrierea scripturilor de verificare</h1></div></div></div><div class="para">
+ RPM tratează automat verificarea pachetelor, controlând instalarea fișierelor corespunzătoare și testarea fișierelor pentru mărimea potrivită și alte atribute. S-ar putea să aveți nevoie de mai mult totuși pentru a vă asigura că totul este în regulă. Cu RPM, puteți:
+ </div><div class="para">
+ *Controlați testele folosite la verificarea fiecărui fișier, așa ca în<a class="xref" href="#ch-specfiles">Cap. 9, <em>Working with Spec Files</em></a>
+ </div><div class="para">
+ *Creați un script de verificare care efectuează alte teste
+ </div><div class="para">
+ Dacă doriți să efectuați alt test pentru a verifica pachetul, ca de exemplu să verificați dacă un fișier de configurare conține o anume setare (și că acea setare este validă), puteți completa %verifyscript în fișierul spec. %verifyscript se comportă în mare parte ca și scripturile %pre sau %post, cu diferența că %verifyscript este executat în timpul verificării pachetului. Completați un %verifyscript după cum urmează:
+ </div><div class="para">
+ %verifyscript
+ </div><div class="para">
+ your script commands ....
+ </div><div class="para">
+ Acțiuni comune pentru %verifyscript ar fi verificarea unei intrări într-un fișier de configurare a sistemului, ca de exemplu un script de pornire în timpul init sau /etc/shells (care listează shellurile disponibile). Acestea sunt fișiere care aparțin altor pachete care ar putea trebui modificate corespunzător pentru ca un pachet să fie instalat cum trebuie. Dacă pachetul este într-o asemenea situație, scrieți un %verifyscript. În scriptul dvs, direcționați toate erorile spre stderr.
+ </div><div class="para">
+ Referință încrucișată
+ </div><div class="para">
+ A se vedea <a class="xref" href="#ch-using-rpm-db">Cap. 4, <em>Using the RPM Database</em></a> pentru detalii despre verificarea pachetelor.
+ </div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id919420" class="title">Crearea subpachetelor.</h1></div></div></div><div class="para">
+ Un fișier spec poate defini mai multe pachete. Aceste pachete adiționale se numesc subpachete. Subpachetele există pentru a trata cazuri în care nu doriți să asociați un fișier spec cu un pachet. În schimb, puteți defini mai multe pacheteîn fișierul spec, după caz. De exemplu, poate doriți să construiți pachetele runtimeși developer împreună, sau părțile client și server al eunei aplicații folosind subpachete. De asemenea, împărțirea seturilor de documentație mari în subpachete separate este o operațiune comună.
+ </div><div class="para">
+ Folosind subpachete, aveți:
+ </div><div class="para">
+ *Un fișier spec
+ </div><div class="para">
+ *Un pachet RPM sursă
+ </div><div class="para">
+ *Un set de comenzi de construcție
+ </div><div class="para">
+ *Pachete RPM binare multiple, câte unul per pachet sau subpachet
+ </div><div class="para">
+ În majoritatea cazurilor, subpachetele sunt create doar ca mijloc de a divide fișierele produse de un pachet în pachete separate. De exemplu, veți observa de multe ori biblioteci de development și fișiere headersunt separate într-un pachet diferit de pachetul principal al aplicației.Câteodată documentația este despărțită de pachetul principal, sau aplicațiile client și server sunt împărțite în pachete separate. Până la urmă acest faptrezultă în mutarea fișierelor în subpachete și nimic mai mult.
+ </div><div class="para">
+ Pentru a defini un subpachet într-un fișier spec, începeți cu directiva %package. De exemplu:
+ </div><div class="para">
+ %package nume_subpachet
+ </div><div class="para">
+ În mod implicit numele subpachetului va fi numele pachetului, o liniuță și numele subpachetului așa cum apare în directiva %package. De exemplu:
+ </div><div class="para">
+ %package server
+ </div><div class="para">
+ Acest exemplu denumește un subpachet server care este un subpachet real inclusîn pachetul telnet. În acest caz, numele subpachetului server va fi telnet-server, adică formatul de nume este pachet-subpachet.
+ </div><div class="para">
+ Dacă nu doriți acest format de nume, puteți folosi opțiunea -n a directivei %package pentru a defini un nume complet nou, folosindurmătoarea sintaxă:
+ </div><div class="para">
+ %package -n nume_nou_subpachet
+ </div><div class="para">
+ De exemplu:
+ </div><div class="para">
+ %package –n my-telnet-server
+ </div><div class="para">
+ Cu opțiunea -n puteți specifica numele întreg al subpachetului. Sistemul RPM nu va prefixa numele cu cel al pachetului care îl include.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id680225" class="title">Furnizarea informațiilor pentru subpachete</h1></div></div></div><div class="para">
+ La definirea unui subpachet trebuie să furnizați atâtea directive legate de informații despre pachet câte aveți nevoie, incluzând cel puțin directivele Summary:,Group:, și %description.
+ </div><div class="para">
+ %package server
+ </div><div class="para">
+ Requires: xinetd
+ </div><div class="para">
+ Group: System Environment/Daemons
+ </div><div class="para">
+ Sumar: Partea server pentru protocolul de login la distanță telnet
+ </div><div class="para">
+ Directiva %description pentru subpachete necesită numele subpachetuluifolosind următoarea sintaxă
+ </div><div class="para">
+ %description subpachet
+ </div><div class="para">
+ De exemplu:
+ </div><div class="para">
+ %description server
+ </div><div class="para">
+ Telnet este un protocol popular pentru logarea la sisteme la distanță
+ </div><div class="para">
+ via internet. Pachetul telnet-server include un daemon telnet care suportă login la distanță la mașina gazdă.
+ </div><div class="para">
+ Daemonul telnet este activat implicit. Puteți dezactiva
+ </div><div class="para">
+ daemonul telnet prin editarea /etc/xinetd.d/telnet.
+ </div><div class="para">
+ Dacă ați folosit opțiunea -n cu directiva %package, trebuie să repetațiopțiunea -n cu directiva %description. De exemplu:
+ </div><div class="para">
+ %description –n my-telnet-server
+ </div><div class="para">
+ Telnet este un protocol popular pentru logarea la sisteme la distanță
+ </div><div class="para">
+ via internet. Pachetul telnet-server include un daemon telnet care suportă login la distanță la mașina gazdă.
+ </div><div class="para">
+ Daemonul telnet este activat implicit. Puteți dezactiva
+ </div><div class="para">
+ daemonul telnet prin editarea /etc/xinetd.d/telnet.
+ </div><div class="para">
+ Același concept funcționează la secțiunea %files. Aveți nevoie de o secțiune%files separată pentru fiecare subpachet. De exemplu:
+ </div><div class="para">
+ %files server
+ </div><div class="para">
+ %defattr(-,root,root)
+ </div><div class="para">
+ %{_sbindir}/in.telnetd
+ </div><div class="para">
+ %{_mandir}/man5/issue.net.5*
+ </div><div class="para">
+ %{_mandir}/man8/in.telnetd.8*
+ </div><div class="para">
+ %{_mandir}/man8/telnetd.8*
+ </div><div class="para">
+ Din nou, dacă ați folosit opțiunea -n cu directiva %package, trebuie să repetați opțiunea -n cu secțiunea %files. De exemplu:
+ </div><div class="para">
+ %files –n my-telnet-server
+ </div><div class="para">
+ %defattr(-,root,root)
+ </div><div class="para">
+ %{_sbindir}/in.telnetd
+ </div><div class="para">
+ %{_mandir}/man5/issue.net.5*
+ </div><div class="para">
+ %{_mandir}/man8/in.telnetd.8*
+ </div><div class="para">
+ %{_mandir}/man8/telnetd.8*
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id1413121" class="title">Definirea scripturilor pentru subpachete</h1></div></div></div><div class="para">
+ Așa cum definiți secțiuni %files și %description separate pentru subpachete, la fel puteți defini scripturi install si uninstallpentru subpachete. Sintaxa e asemănătoare cu cea pentru secțiunile%files și %description:
+ </div><div class="para">
+ %pre subpachet
+ </div><div class="para">
+ De exemplu, Lista 11-2 afișează scripturile de la pachetul VNC.
+ </div><div class="para">
+ Lista 11-2: scripturile install și uninstall pentru pachetul VNC.
+ </div><div class="para">
+ %post server
+ </div><div class="para">
+ if [ "$1" = 1 ]; then
+ </div><div class="para">
+ /sbin/chkconfig --add vncserver
+ </div><div class="para">
+ fi
+ </div><div class="para">
+ </div><div class="para">
+ %preun server
+ </div><div class="para">
+ if [ "$1" = 0 ]; then
+ </div><div class="para">
+ /sbin/service vncserver stop >/dev/null 2>&1
+ </div><div class="para">
+ /sbin/chkconfig --del vncserver
+ </div><div class="para">
+ fi
+ </div><div class="para">
+ </div><div class="para">
+ %postun server
+ </div><div class="para">
+ if [ "$1" -ge "1" ]; then
+ </div><div class="para">
+ /sbin/service vncserver condrestart >/dev/null 2>&1
+ </div><div class="para">
+ fi
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id919281" class="title">Construirea subpachetelor</h1></div></div></div><div class="para">
+ Secțiunile build din fișierul spec servesc un dublu scop. Aceste secțiunisunt folosite pentru construirea pachetului principal precum și a subpachetelor.Este unul din motivele pentru care există atâtea opțiuni în macroul %setup.
+ </div><div class="para">
+ Macroul %setup permite despachetarea selectivă a surselor, în contrast cu opțiunea implicită de a despacheta toate sursele. De exemplu, definiția macroului %setup următor dă comenzii rpmbuild instrucțiuni specifice pentru despachetarea unui fișier sursă:
+ </div><div class="para">
+ %setup –D- T –a 1
+ </div><div class="para">
+ In this example, the –D option disables the automatic deletion of the directory where the sources will be unpacked. This means any previous contents of this directory, perhaps for other subpackages, will be left alone. The –T option disables the automatic unpacking of the source files, and the –a 1 option specifies to only unpack the first source file. You may need to use options like these when working with subpackages. Though, in most cases, subpackages are just means to partition the package files into separate packages. In cases like this, you will likely not need any of these special %setup options.
+ </div><div class="para">
+ Referință încrucișată
+ </div><div class="para">
+ <a class="xref" href="#ch-specfiles">Cap. 9, <em>Working with Spec Files</em></a> covers the %setup macro and lists the available options.
+ </div></div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id864110" class="title">Creating Relocatable Packages</h1></div></div></div><div class="para">
+ A relocatable package allows a user to specify where to install the package. For example, if you build a package for Red Hat Linux, the normal directory for binary executable programs is /usr/bin. Other versions of Linux, though, may place executable programs into /opt/bin, for example. If your package forces the use of /usr/bin, then your package won’t work on these other systems.
+ </div><div class="para">
+ Referință încrucișată
+ </div><div class="para">
+ <a class="xref" href="#ch-other-linuxes">Cap. 18, <em>Using RPM on Non-Red Hat Linuxes</em></a> covers using RPM on other versions of Linux.
+ </div><div class="para">
+ With a relocatable package, though, you allow the user to redefine the top-level directories for your package, such as changing from /usr/bin to /opt/bin in the previous example. Making relocatable packages is generally considered a good thing, as you make the user’s life easier.
+ </div><div class="para">
+ To set up a relocatable package, you need to:
+ </div><div class="para">
+ *Set up the prefix directives for the top-level directories
+ </div><div class="para">
+ *Define the files under the prefix directories
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id670616" class="title">Setting up the prefixes</h1></div></div></div><div class="para">
+ The Prefix: directive names a top-level directory as a prefix you can relocate to another directory. For example:
+ </div><div class="para">
+ Prefix: /usr
+ </div><div class="para">
+ This states that all files under /usr can be relocated to other directories by simply mapping /usr to some other directory, such as /opt, on the rpm command line when installing or upgrading the package.
+ </div><div class="para">
+ Notă
+ </div><div class="para">
+ You can define more than one Prefix: directive to list more than one top-level directory.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id773908" class="title">Define the files section</h1></div></div></div><div class="para">
+ When you use a Prefix: directive in your spec file, all files in the %files section must be under the directory named with the Prefix: directive. For example, from the jikes compiler package:
+ </div><div class="para">
+ Prefix: /usr
+ </div><div class="para">
+ </div><div class="para">
+ ...
+ </div><div class="para">
+ </div><div class="para">
+ %files
+ </div><div class="para">
+ %defattr(-,root,root)
+ </div><div class="para">
+ /usr/bin/jikes
+ </div><div class="para">
+ %doc /usr/doc/jikes-%{version}/license.htm
+ </div><div class="para">
+ %doc /usr/man/man1/jikes.1*
+ </div><div class="para">
+ In this example, all the files are under the /usr directory. All files in the %files section must be located under one of the Prefix: directories. If you have more than one top-level directory, such as /usr and /etc, define more than one Prefix: directive. For example:
+ </div><div class="para">
+ Prefix: /usr
+ </div><div class="para">
+ Prefix: /etc
+ </div><div class="para">
+ Referință încrucișată
+ </div><div class="para">
+ <a class="xref" href="#ch-using-rpm">Cap. 3, <em>Using RPM</em></a> covers how to install or upgrade packages into different directories using the --relocate and --prefix options.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id831211" class="title">Problems creating relocatable packages</h1></div></div></div><div class="para">
+ Not all packages work well as relocatable packages. Some packages have files that simply must go into a certain location and are therefore not relocatable. Some packages have programs that are hard-coded to look for files in a particular location and therefore cannot be relocated elsewhere. Other packages have symbolic links that also may not be relocatable. Furthermore, your package may provide software that is referenced by other packages, in the known directories. Relocating such a package will disable other software packages, packages you may not even know about.
+ </div><div class="para">
+ If your packages face any of these problems, chances are that making the package relocatable is not a good idea.
+ </div><div class="para">
+ In addition, if you use the %doc directive with local file names, remember that RPM will make a package-specific documentation directory, normally under /usr/doc. For example:
+ </div><div class="para">
+ %doc README NEWS
+ </div><div class="para">
+ This may defeat your attempts to create a relocatable package, unless you have a Prefix: directive with /usr, because the normal location is under /usr/doc, and all files in the %files section must start with one of the directories named with Prefix: directives.
+ </div></div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id777632" class="title">Defining Conditional Builds</h1></div></div></div><div class="para">
+ With the ability to define macros inside spec files, and also to use macros defined elsewhere, you gain a lot of control over how your package gets built. You can go further, though, and use special directives to perform only certain commands based on certain conditions. This adds a powerful capability to your spec files, and also makes it much easier to do things like build for multiple versions of Linux or other operating systems, as well as handle various backwards-compatibility issues.
+ </div><div class="para">
+ To define conditional build commands, you need to create conditional constructs in your package’s spec file. In addition, you need to define macros that the conditional constructs use to determine whether or not to execute a set of spec file directives.
+ </div><div class="para">
+ Referință încrucișată
+ </div><div class="para">
+ See <a class="xref" href="#ch-customizing-rpm">Cap. 20, <em>Customizing RPM Behavior</em></a> for more on macro file locations, and <a class="xref" href="#ch-other-linuxes">Cap. 18, <em>Using RPM on Non-Red Hat Linuxes</em></a> and <a class="xref" href="#ch-other-os">Cap. 19, <em>RPM on Other Operating Systems</em></a> for more on using RPM on other versions of Linux and other operating systems, respectively.
+ </div><div class="para">
+ RPM supports a number of ways to make parts of your spec file enabled or disabled based on certain conditions. These include conditional macros, conditional blocks, and special directives based on the system architecture.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id676244" class="title">Defining conditional macros</h1></div></div></div><div class="para">
+ You can use a special syntax to test for the existence of macros. For example:
+ </div><div class="para">
+ %{?macro_to_test: expression}
+ </div><div class="para">
+ This syntax tells RPM to expand the expression if the macro macro_to_test exists. If the macro macro_to_test does not exist, nothing will be output. You can also reverse this test. A leading exclamation point, !, tests for the non-existence of a macro:
+ </div><div class="para">
+ %{!?macro_to_test: expression}
+ </div><div class="para">
+ In this example, if the macro_to_test macro does not exist, RPM will expand the expression.
+ </div><div class="para">
+ If you want, you can omit the expression and just test for the existence of the macro. If it exists, RPM will use the value of the macro. If the macro does not exist, RPM will use nothing. For example:
+ </div><div class="para">
+ %build
+ </div><div class="para">
+ ./configure %{?_with_ldap}
+ </div><div class="para">
+ make
+ </div><div class="para">
+ In this case, if the _with_ldap macro exists, the value of that macro will get passed on the command line to the configure script. If the _with_ldap macro does not exist, nothing extra will be passed on the command line to the configure script. This is very important when creating commands to build or install packages.
+ </div><div class="para">
+ Referință încrucișată
+ </div><div class="para">
+ Many of the macros you will test this way are set up with the --with command-line parameter. See <a class="xref" href="#ch-other-linuxes">Cap. 18, <em>Using RPM on Non-Red Hat Linuxes</em></a> for details.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id970594" class="title">Using conditional blocks</h1></div></div></div><div class="para">
+ The %if macro enables all the directives up to the %endif directive, if the condition is true. This is much like scripting languages. For example:
+ </div><div class="para">
+ %if %{old_5x}
+ </div><div class="para">
+ %define b5x 1
+ </div><div class="para">
+ %undefine b6x
+ </div><div class="para">
+ %endif
+ </div><div class="para">
+ In this case, if the %old_5x macro has a value, the test will be true and all the directives inside the block will get executed.
+ </div><div class="para">
+ A %else allows you to specify what to do if the test is not successful. For example:
+ </div><div class="para">
+ %if %{old_5x}
+ </div><div class="para">
+ %define b5x 1
+ </div><div class="para">
+ %undefine b6x
+ </div><div class="para">
+ %else
+ </div><div class="para">
+ %define b6x 1
+ </div><div class="para">
+ %undefine b5x
+ </div><div class="para">
+ %endif
+ </div><div class="para">
+ In this case, if the %old_5x macro has a value, then all the directives up to the %else will get executed. Otherwise, if the %old_5x macro has no value, the directives from the %else to the %endif will get executed.
+ </div><div class="para">
+ Again, use an exclamation point to negate the test. For example:
+ </div><div class="para">
+ %if ! %{old_5x}
+ </div><div class="para">
+ %define b5x 1
+ </div><div class="para">
+ %undefine b6x
+ </div><div class="para">
+ %endif
+ </div><div class="para">
+ You can use a && for an AND test. For example:
+ </div><div class="para">
+ %if %{old_5x} && %{old_6x}
+ </div><div class="para">
+ %{error: You cannot build for .5x and .6x at the same time}
+ </div><div class="para">
+ %quit
+ </div><div class="para">
+ %endif
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id679472" class="title">Using architecture-based conditionals</h1></div></div></div><div class="para">
+ In addition to the general-purpose %if conditional directive, you can use special directives that test for processor architecture and operating system.
+ </div><div class="para">
+ The %ifarch directive enables all the directives up to the %endif directive, if the processor architecture matches the values you pass to the %ifarch directive. For example:
+ </div><div class="para">
+ %ifarch sparc
+ </div><div class="para">
+ %define b5x 1
+ </div><div class="para">
+ %undefine b6x
+ </div><div class="para">
+ %endif
+ </div><div class="para">
+ This block will only get executed if the processor architecture is SPARC.
+ </div><div class="para">
+ Referință încrucișată
+ </div><div class="para">
+ <a class="xref" href="#ch-customizing-rpm">Cap. 20, <em>Customizing RPM Behavior</em></a> covers RPM architecture and operating system names.
+ </div><div class="para">
+ You can pass more than one architecture name, separated by commas or spaces. For example:
+ </div><div class="para">
+ %ifarch sparc alpha
+ </div><div class="para">
+ %define b5x 1
+ </div><div class="para">
+ %undefine b6x
+ </div><div class="para">
+ %endif
+ </div><div class="para">
+ This example tests if the processor architecture is SPARC or Alpha.
+ </div><div class="para">
+ As with the %if directive, you can also use an %else, to cover all cases where the test is not true. For example:
+ </div><div class="para">
+ %ifarch sparc alpha
+ </div><div class="para">
+ %define b5x 1
+ </div><div class="para">
+ %undefine b6x
+ </div><div class="para">
+ %else
+ </div><div class="para">
+ %define b6x 1
+ </div><div class="para">
+ %undefine b5x
+ </div><div class="para">
+ %endif
+ </div><div class="para">
+ This example tests if the processor architecture is SPARC or Alpha. If so, the directives from the %ifarch to the %else are executed. If not, the directives from the %else to the %endif are executed.
+ </div><div class="para">
+ The %ifnarch directive reverses the %ifarch test. That is, %ifnarch tests if the architecture is not one of the values listed. The following example tests if the processor architecture is not an i386 or an Alpha.
+ </div><div class="para">
+ %ifnarch i386 alpha
+ </div><div class="para">
+ %define b5x 1
+ </div><div class="para">
+ %undefine b6x
+ </div><div class="para">
+ %endif
+ </div><div class="para">
+ </div><div class="para">
+ The %ifos directive tests for the operating system. For example:
+ </div><div class="para">
+ %ifos linux
+ </div><div class="para">
+ %define b5x 1
+ </div><div class="para">
+ %undefine b6x
+ </div><div class="para">
+ %endif
+ </div><div class="para">
+ This example tests if the operating system is Linux. You can reverse the test with the %ifnos directive. For example:
+ </div><div class="para">
+ %ifnos irix
+ </div><div class="para">
+ %define b5x 1
+ </div><div class="para">
+ %undefine b6x
+ </div><div class="para">
+ %endif
+ </div><div class="para">
+ This example tests if the operating system is not Irix.
+ </div></div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id790812" class="title">Summary</h1></div></div></div><div class="para">
+ This chapter covers advanced topics in creating packages. Dependencies are very important. You need to specify which packages or capabilities your package requires, so the RPM system can ensure that all requirements are met before allowing users to install the package. If you do not specify the dependencies properly, then you are defeating the integrity of the RPM system.
+ </div><div class="para">
+ In addition to specifying what your package requires, it is also important to specify other dependency information. For example, if your package conflicts with another package, you need to very clearly state this. E-mail and Web server packages often conflict with other servers of the same type.
+ </div><div class="para">
+ You can specify both package dependencies as well as build dependencies. For example, you may need certain developer libraries to build your package, but not to install it. These are build dependencies.
+ </div><div class="para">
+ To help manage dependencies between packages and system configuration issues, you can set up trigger scripts. A trigger is a script in your package that gets executed when another package is installed or removed. If your package, for example, is an e-mail client program, it may need to execute a script should the e-mail server package change. This is a great usage for triggers.
+ </div><div class="para">
+ If your package has a complicated installation, the normal RPM verification won’t be sufficient. To help the RPM system ensure the integrity of all the packages, you can write a verify script in your spec file to perform any extra commands necessary to verify your package has been properly installed.
+ </div><div class="para">
+ Relocatable packages allow users to install your packages in different locations than originally planned. This is very useful when working with more than one version of Linux, or with other operating systems. For example, most Linux commands are stored in /usr/bin, at least for Red Hat Linux. Other Linux distributions, or other operating systems may specify that programs added to the original set should be stored in /opt/bin and not /usr/bin, for example. Making your package relocatable helps users in these situations.
+ </div><div class="para">
+ Conditional directives in your spec file allow you to control the build on different processor architectures and operating systems. The %if directive tests if a value is set. If so, then all the directives up to the %endif directive are executed. If you need to execute a different set of directives, use %else. In this case, if the %if test is true, RPM executes the directives up to the %else. If the test is not true, RPM executes the directives up to the %endif.
+ </div><div class="para">
+ Once you have your spec file defined, the next step is to start building packages. The next chapter covers options for the rpmbuild command and how you can use rpmbuild to make your packages.
+ </div></div></div><div xml:lang="ro" class="chapter" id="ch-rpmbuild" lang="ro"><div class="titlepage"><div><div><h2 class="title">Cap. 11. Controlling the Build with <code class="command">rpmbuild</code></h2></div></div></div><div class="toc"><dl><dt><span class="sect1"><a href="#id569546">11.1. Building RPMs with the rpmbuild Command</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id566973">11.1.1. Customizing the build</a></span></dt><dt><span class="sect2"><a href="#id575664">11.1.2. Testing the build</a></span></dt><dt><span class="sect2"><a href="#id553875">11.1.3. Debugging the build</a></span></dt><dt><span class="sect2"><a href="#id516418">11.1.4. Cleaning up</a></span></dt><dt><span class="sect2"><a href="#id1415379">11.1.5. Building for other platforms</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id625711">11.2. Building RPMs Without an External Spec File</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id625725">11.2.1. Options for
working with tar archives</a></span></dt><dt><span class="sect2"><a href="#id818541">11.2.2. The expected archive structure</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id1005965">11.3. Working with Source RPMs</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id753269">11.3.1. Rebuilding binary RPMS from source RPMs</a></span></dt><dt><span class="sect2"><a href="#id1315118">11.3.2. Recompiling binaries from source RPMs</a></span></dt><dt><span class="sect2"><a href="#id744420">11.3.3. SRPMS? Finding source RPMs</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id570726">11.4. Signing Built RPMs</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id570739">11.4.1. Checking that the GPG software is installed</a></span></dt><dt><span class="sect2"><a href="#id619927">11.4.2. Configuring a signature</a></span></dt><dt><span class="sect2"><a href="#id785579">11.4.3. Signing with the rpmbuild command</a></span></dt><dt><span class="sect2"><a h
ref="#id757369">11.4.4. Signing with the rpm command</a></span></dt><dt><span class="sect2"><a href="#id639407">11.4.5. Verifying signatures</a></span></dt><dt><span class="sect2"><a href="#id723247">11.4.6. Importing public keys</a></span></dt><dt><span class="sect2"><a href="#id550839">11.4.7. Getting the Red Hat public key</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id714646">11.5. Summary</a></span></dt></dl></div><div class="para">
+ This chapter covers:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Building with the <code class="command">rpmbuild</code> command
+ </div></li><li class="listitem"><div class="para">
+ Building RPMs without an external spec file
+ </div></li><li class="listitem"><div class="para">
+ Working with source RPMs
+ </div></li><li class="listitem"><div class="para">
+ Optimizing builds
+ </div></li><li class="listitem"><div class="para">
+ Signing built RPMs
+ </div></li></ul></div><div class="para">
+ The preceding chapters in this Part cover details on how to put together RPMs. This chapter rounds out the discussion by delving into more details on the rpmbuild command.
+ </div><div class="para">
+ You can customize how rpmbuild creates RPMs, and you can use RPM commands to test and debug your package.
+ </div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id569546" class="title">Building RPMs with the rpmbuild Command</h1></div></div></div><div class="para">
+ The rpmbuild command provides a workhorse command for building RPMs in all sorts of ways. The basic syntax, as shown in <a class="xref" href="#ch-creating-rpms">Cap. 8, <em>Creating RPMs: An Overview</em></a>, is:
+ </div><div class="para">
+ rpmbuild -bBuildStage spec_file
+ </div><div class="para">
+ The BuildStage is a letter, such as c, to prepare and compile the application, executing through the %build section, or i, to execute through the %install section. This allows you a good deal of flexibility for building the entire RPM or stopping at some point prior to a full build.
+ </div><div class="para">
+ There’s more to the rpmbuild command, though. Quite a few additional options allow you to further customize the build.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ As mentioned in <a class="xref" href="#ch-creating-rpms">Cap. 8, <em>Creating RPMs: An Overview</em></a> , previous versions of the RPM system used the rpm command with a -b, for build, option. This option is no longer supported. Use the rpmbuild command to build RPMs.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id566973" class="title">Customizing the build</h1></div></div></div><div class="para">
+ You can customize the rpmbuild command with the options listed in Table 12-1.
+ </div><div class="para">
+ Table 12-1 Extra build options for the rpmbuild command
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Option
+ </div>
+
+ </td><td>
+ <div class="para">
+ Usage
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --buildroot directory
+ </div>
+
+ </td><td>
+ <div class="para">
+ Override the default root directory for building with directory, generally not very useful since most packages already name a buildroot
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --clean
+ </div>
+
+ </td><td>
+ <div class="para">
+ Remove the build tree after building
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nobuild
+ </div>
+
+ </td><td>
+ <div class="para">
+ Just test the spec file and do not run the build
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --rmsource
+ </div>
+
+ </td><td>
+ <div class="para">
+ Remove the sources after the build
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --rmspec
+ </div>
+
+ </td><td>
+ <div class="para">
+ Remove the spec file after the build
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --short-circuit
+ </div>
+
+ </td><td>
+ <div class="para">
+ With the -bc or -bi options, jump directly to the given stage and resume the build from that stage
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --sign
+ </div>
+
+ </td><td>
+ <div class="para">
+ Sign the package with a GPG signature
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --target platform
+ </div>
+
+ </td><td>
+ <div class="para">
+ Build for the given platform. May not work if you don't have the other platform build commands, such as cross compilers, set up. Can work for Intel platforms with i386, i686, and so on.
+ </div>
+
+ </td></tr></tbody></table></div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id575664" class="title">Testing the build</h1></div></div></div><div class="para">
+ One of the most useful options is --nobuild, which tells the rpmbuild command to not build anything. This may seem silly, but the --nobuild option is very useful for testing whether your RPMs can be built. With the --nobuild option, the rpmbuild command parses the spec file and checks for errors, but does not run any of the build stages.
+ </div><div class="para">
+ The --buildroot allows you to specify a different top-level directory for building, overriding the BuildRoot tag in the spec file. This means you can build in a separate location, which is helpful in case there are mistakes. Using a separate directory means the build won’t get mixed with anything else in the build root directory.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id553875" class="title">Debugging the build</h1></div></div></div><div class="para">
+ The --short-circuit option tells the rpmbuild command to restart at a particular location in the build. Rather than working its way through all the steps up to the build stage you ask for, the --short-circuit option allows the rpmbuild command to restart just at the step you ask for.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ This works with the -bc and -bi options only, as well as the -tc and -ti options covered later in this chapter.
+ </div><div class="para">
+ For example, if you run the rpmbuild -bc command to stop after the %build section, you can use the --short-circuit option to restart the build at the %build section. If you found a problem in the %build section and corrected it, you can quickly get going again by restarting the build at the %build section rather than extracting all the sources yet again.
+ </div><div class="para">
+ This option is most useful when you are compiling a package, hit an error, and fix that error. Without the --short-circuit option, you’ll likely end up spending a lot of time recompiling the code you have already compiled.
+ </div><div class="para">
+ During normal development of an RPM package, you will likely execute each build section, one at a time, stop, fix any errors and restart where you left off. You’ll go through this cycle a number of times before the RPM finally builds right.
+ </div><div class="para">
+ Warning
+ </div><div class="para">
+ Never distribute an RPM made with the --short-circuit option. Instead, once you have everything working, start from scratch and rebuild the RPM. This is to avoid any problems with a partially-created RPM.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id516418" class="title">Cleaning up</h1></div></div></div><div class="para">
+ The --clean option tells the rpmbuild command to remove the build tree when complete. This helps ensure that the next time you run the rpmbuild command, you are starting from a known situation.
+ </div><div class="para">
+ For example:
+ </div><div class="para">
+ $ rpmbuild --clean /usr/src/redhat/SPECS/jikes.spec
+ </div><div class="para">
+ Executing(--clean): /bin/sh -e /var/tmp/rpm-tmp.98247
+ </div><div class="para">
+ + umask 022
+ </div><div class="para">
+ + cd /usr/src/redhat/BUILD
+ </div><div class="para">
+ + rm -rf jikes-1.17
+ </div><div class="para">
+ + exit 0
+ </div><div class="para">
+ You can use the --clean option alone, as shown previously, or in concert with another option such as -bi to build and install a binary RPM. In the latter case, the rpmbuild command will clean the built files after the rest of the command finishes.
+ </div><div class="para">
+ Similarly, the --rmsource option tells the rpmbuild command to remove the sources after completing the command. You can call this option with another option, such as -bi for building and installing a binary RPM (and then removing the sources), or alone on the command line to remove the sources only.
+ </div><div class="para">
+ For example:
+ </div><div class="para">
+ rpmbuild --rmsource jikes.spec
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ The abbreviation rm is short for remove. It comes from the Linux rm command, used for removing files.
+ </div><div class="para">
+ The --rmspec option tells the rpmbuild command to remove the spec file when done with the command. As with the --rmsource option, you can use the --rmspec option in conjunction with another rpmbuild option or on its own to just remove the spec file.
+ </div><div class="para">
+ For example:
+ </div><div class="para">
+ rpmbuild --rmspec jikes.spec
+ </div><div class="para">
+ Warning
+ </div><div class="para">
+ The file you are removing with this command is the spec file you are passing to the command. Be careful, because you cannot undo this operation and you have now lost your spec file, except inside your source package.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id1415379" class="title">Building for other platforms</h1></div></div></div><div class="para">
+ The --target option tells the rpmbuild command to build a package for another platform. You need to pass the name of the platform. For example:
+ </div><div class="para">
+ rpmbuild -bi --target i486-redhat-linux
+ </div><div class="para">
+ The basic format is:
+ </div><div class="para">
+ cpu-vendor-os
+ </div><div class="para">
+ For example, i686-redhat-linux specifies a 686 CPU with Red Hat Linux. Other CPUs include ppc for PowerPC and sparc for Sun SPARC.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ The --target option sets the target architecture at build time. <a class="xref" href="#ch-using-rpm">Cap. 3, <em>Using RPM</em></a> covers how you can use the --ignoreos and --ignorearch options when installing RPMs to ignore the operating system and architecture that is flagged within the RPM. Of course, this works only if you are installing on a compatible architecture.
+ </div><div class="para">
+ On the surface level, the --target option overrides some of the macros in the spec file, %_target, %_target_arch, and %_target_os. This flags the RPM for the new target platform.
+ </div><div class="para">
+ Under the covers, setting the architecture macros is not enough. You really cannot create a PowerPC executable, for example, on an Intel-architecture machine, unless you have a PowerPC cross compiler, a compiler that can make PowerPC executables.
+ </div><div class="para">
+ Warning
+ </div><div class="para">
+ Set the target with care. Make sure you can really build executable programs for that architecture.
+ </div><div class="para">
+ If you try to compile a system that uses the GNU configure system to configure the build, your target will likely be ignored. For example, if you try to build the aforementioned jikes package with a target of ppc-ibm-aix, to specify IBM’s UNIX, called AIX, on a PowerPC architecture, you will see the target ignored as the configure system detects that it's running on Linux on an i686 architecture.
+ </div><div class="para">
+ For example:
+ </div><div class="para">
+ $ rpmbuild -bc --target ppc-ibm-aix /usr/src/redhat/SPECS/jikes.spec
+ </div><div class="para">
+ Building target platforms: ppc-ibm-aix
+ </div><div class="para">
+ Building for target ppc-ibm-aix
+ </div><div class="para">
+ Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.94955
+ </div><div class="para">
+ + umask 022
+ </div><div class="para">
+ + cd /usr/src/redhat/BUILD
+ </div><div class="para">
+ + LANG=C
+ </div><div class="para">
+ + export LANG
+ </div><div class="para">
+ + cd /usr/src/redhat/BUILD
+ </div><div class="para">
+ + rm -rf jikes-1.17
+ </div><div class="para">
+ + /usr/bin/gzip -dc /usr/src/redhat/SOURCES/jikes-1.17.tar.gz
+ </div><div class="para">
+ + tar -xf -
+ </div><div class="para">
+ + STATUS=0
+ </div><div class="para">
+ + '[' 0 -ne 0 ']'
+ </div><div class="para">
+ + cd jikes-1.17
+ </div><div class="para">
+ ++ /usr/bin/id -u
+ </div><div class="para">
+ + '[' 500 = 0 ']'
+ </div><div class="para">
+ ++ /usr/bin/id -u
+ </div><div class="para">
+ + '[' 500 = 0 ']'
+ </div><div class="para">
+ + /bin/chmod -Rf a+rX,g-w,o-w .
+ </div><div class="para">
+ + exit 0
+ </div><div class="para">
+ Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.15710
+ </div><div class="para">
+ + umask 022
+ </div><div class="para">
+ + cd /usr/src/redhat/BUILD
+ </div><div class="para">
+ + cd jikes-1.17
+ </div><div class="para">
+ + LANG=C
+ </div><div class="para">
+ + export LANG
+ </div><div class="para">
+ + ./configure CXXFLAGS=-O3 --prefix=/tmp/jikesrpm/usr
+ </div><div class="para">
+ checking for a BSD-compatible install... /usr/bin/install -c
+ </div><div class="para">
+ checking whether build environment is sane... yes
+ </div><div class="para">
+ checking for gawk... gawk
+ </div><div class="para">
+ checking whether make sets ${MAKE}... yes
+ </div><div class="para">
+ checking whether to enable maintainer-specific portions of Makefiles... no
+ </div><div class="para">
+ checking build system type... i686-pc-linux-gnu
+ </div><div class="para">
+ checking host system type... i686-pc-linux-gnu
+ </div><div class="para">
+ checking for g++... g++
+ </div><div class="para">
+ As you can see, the command starts out with the target as the platform, but the configure script soon overrides that, as shown at the end of the truncated output.
+ </div></div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id625711" class="title">Building RPMs Without an External Spec File</h1></div></div></div><div class="para">
+ Most of the options for the rpmbuild command require an RPM spec file. This file defines all the necessary parameters for the RPM to build. If you’ve downloaded an application, though, you may not have all the information needed to build a spec file. In addition, writing the spec file is the most time-consuming task when building RPMs. If you are lucky, the provider of a given application may have already created a spec file and included the spec file within the source distribution.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id625725" class="title">Options for working with tar archives</h1></div></div></div><div class="para">
+ A special set of options aims toward building RPMs with spec files stored in tar archives, also called tarballs. Tarballs are files combined with the tar (tape archiver) utility and then optionally compressed, usually with the gzip command. Because this format is used so often for UNIX and Linux software, you can use a set of -t options to the rpmbuild command that mimic the -b options.
+ </div><div class="para">
+ The basic syntax follows:
+ </div><div class="para">
+ rpmbuild -tBuildStage compressed_tar_archive
+ </div><div class="para">
+ The -t option is a lot like the -b option covered in <a class="xref" href="#ch-creating-rpms">Cap. 8, <em>Creating RPMs: An Overview</em></a> , except -t tells rpmbuild to build an RPM from a compressed tar archive instead of from an RPM spec file. You still need a spec file. These commands just assume that the spec file is located within the tar archive. The extra BuildStage option is a special code that tells the rpmbuild command how far to go when building. Table 12-2 lists these options:
+ </div><div class="para">
+ Table 12-2 Options for building with rpmbuild with tar archives
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Option
+ </div>
+
+ </td><td>
+ <div class="para">
+ Usage
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -ta
+ </div>
+
+ </td><td>
+ <div class="para">
+ Build all, both a binary and source RPM
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -tb
+ </div>
+
+ </td><td>
+ <div class="para">
+ Build a binary RPM
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -tc
+ </div>
+
+ </td><td>
+ <div class="para">
+ Stop after the %build section
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -tp
+ </div>
+
+ </td><td>
+ <div class="para">
+ Stop after the %prep section
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -ti
+ </div>
+
+ </td><td>
+ <div class="para">
+ Stop after the %install section
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -tl
+ </div>
+
+ </td><td>
+ <div class="para">
+ Check the listing of files for the RPM
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -ts
+ </div>
+
+ </td><td>
+ <div class="para">
+ Build a source RPM only
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ Note
+ </div><div class="para">
+ These command-line options work with a tar archive or a compressed tar archive.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id818541" class="title">The expected archive structure</h1></div></div></div><div class="para">
+ To build a package this way, the tar archive must have enough of an expected structure, such as a configure script and a Makefile with the expected make targets. The most crucial element is that the tar archive must have the package spec file.That’s because the rpmbuild command doesn’t know how to build every program in the universe. Instead, rpmbuild expects to find a spec file to tell it what to do. If you see an error like the following, then your tar archive likely is missing the spec file:
+ </div><div class="para">
+ $ rpmbuild -tc vixie-cron*tar.gz
+ </div><div class="para">
+ error: Name field must be present in package: (main package)
+ </div><div class="para">
+ error: Version field must be present in package: (main package)
+ </div><div class="para">
+ error: Release field must be present in package: (main package)
+ </div><div class="para">
+ error: Summary field must be present in package: (main package)
+ </div><div class="para">
+ error: Group field must be present in package: (main package)
+ </div><div class="para">
+ error: License field must be present in package: (main package)
+ </div><div class="para">
+ These errors show expected tags from the missing spec file.
+ </div><div class="para">
+ </div><div class="para">
+ </div></div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id1005965" class="title">Working with Source RPMs</h1></div></div></div><div class="para">
+ Most of your work with the rpmbuild command will likely be to create binary RPMs after you have the sources for an application and a spec file. You can also get a lot of mileage out of source RPMs, whether you build them or download them.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ <a class="xref" href="#ch-specfiles">Cap. 9, <em>Working with Spec Files</em></a> covers the spec file in depth.
+ </div><div class="para">
+ Because they are RPMs themselves, source RPMs act like other RPMs. For example, you can use the rpm -i command to install a source RPM. This installs the sources provided by the source RPM, not the actual application. Normally, when you install a source RPM on a Red Hat Linux system, the package gets installed into /usr/src/redhat.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ This directory is obviously specific to Red Hat Linux. On other Linux distributions, you'll likely see directories such as /usr/src/OpenLinux for SCO (formerly Caldera) OpenLinux.
+ </div><div class="para">
+ Installing a source RPM is not exactly the same as installing a binary RPM. For example, the rpm command does not update the RPM database when you install a source RPM. In addition, listing the files in a source RPM only shows the relative paths, not the full paths.
+ </div><div class="para">
+ Once installation is complete, you can use the rpmbuild command to create a binary RPM from the sources in the source RPM, using the -b command-line options introduced in <a class="xref" href="#ch-creating-rpms">Cap. 8, <em>Creating RPMs: An Overview</em></a> . The next sections show more shortcuts with source RPMs.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id753269" class="title">Rebuilding binary RPMS from source RPMs</h1></div></div></div><div class="para">
+ As a shortcut, you do not have to install a source RPM to create a binary RPM. Instead, you can build the binary RPM directory using the --rebuild option.
+ </div><div class="para">
+ The --rebuild option tells the rpmbuild command to rebuild a binary RPM from a source RPM file. The basic syntax is:
+ </div><div class="para">
+ rpmbuild --rebuild package.src.rpm
+ </div><div class="para">
+ This command builds a binary RPM out of a source RPM with a minimum of fuss. For example:
+ </div><div class="para">
+ $ rpmbuild --rebuild unix2dos-2.2-17.src.rpm
+ </div><div class="para">
+ Installing unix2dos-2.2-17.src.rpm
+ </div><div class="para">
+ Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.15828
+ </div><div class="para">
+ + umask 022
+ </div><div class="para">
+ + cd /usr/src/redhat/BUILD
+ </div><div class="para">
+ + LANG=C
+ </div><div class="para">
+ + export LANG
+ </div><div class="para">
+ + cd /usr/src/redhat/BUILD
+ </div><div class="para">
+ + rm -rf unix2dos-2.2
+ </div><div class="para">
+ + /bin/mkdir -p unix2dos-2.2
+ </div><div class="para">
+ + cd unix2dos-2.2
+ </div><div class="para">
+ + /usr/bin/gzip -dc /usr/src/redhat/S OURCES/unix2dos-2.2.src.tar.gz
+ </div><div class="para">
+ + tar -xf -
+ </div><div class="para">
+ + STATUS=0
+ </div><div class="para">
+ + '[' 0 -ne 0 ']'
+ </div><div class="para">
+ ++ /usr/bin/id -u
+ </div><div class="para">
+ + '[' 500 = 0 ']'
+ </div><div class="para">
+ ++ /usr/bin/id -u
+ </div><div class="para">
+ + '[' 500 = 0 ']'
+ </div><div class="para">
+ + /bin/chmod -Rf a+rX,g-w,o-w .
+ </div><div class="para">
+ + echo 'Patch #0 (unix2dos-mkstemp.patch):'
+ </div><div class="para">
+ Patch #0 (unix2dos-mkstemp.patch):
+ </div><div class="para">
+ + patch -p1 -b --suffix .sec -s
+ </div><div class="para">
+ + echo 'Patch #1 (unix2dos-2.2-segfault.patch):'
+ </div><div class="para">
+ Patch #1 (unix2dos-2.2-segfault.patch):
+ </div><div class="para">
+ + patch -p1 -b --suffix .segf -s
+ </div><div class="para">
+ + echo 'Patch #2 (unix2dos-2.2-manpage.patch):'
+ </div><div class="para">
+ Patch #2 (unix2dos-2.2-manpage.patch):
+ </div><div class="para">
+ + patch -p1 -b --suffix .man -s
+ </div><div class="para">
+ + perl -pi -e 's,^#endif.*,#endif,g;s,^#else.*,#else,g' unix2dos.c unix2dos.h
+ </div><div class="para">
+ + exit 0
+ </div><div class="para">
+ Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.60650
+ </div><div class="para">
+ + umask 022
+ </div><div class="para">
+ + cd /usr/src/redhat/BUILD
+ </div><div class="para">
+ + cd unix2dos-2.2
+ </div><div class="para">
+ + LANG=C
+ </div><div class="para">
+ + export LANG
+ </div><div class="para">
+ + gcc -O2 -march=i386 -mcpu=i686 -ounix2dos unix2dos.c
+ </div><div class="para">
+ + exit 0
+ </div><div class="para">
+ Executing(%install): /bin/sh -e /var/tmp/rpm-tmp.35128
+ </div><div class="para">
+ + umask 022
+ </div><div class="para">
+ + cd /usr/src/redhat/BUILD
+ </div><div class="para">
+ + cd unix2dos-2.2
+ </div><div class="para">
+ + LANG=C
+ </div><div class="para">
+ + export LANG
+ </div><div class="para">
+ + rm -rf /var/tmp/unix2dos-root
+ </div><div class="para">
+ + mkdir -p /var/tmp/unix2dos-root/usr/bin /var/tmp/unix2dos-
+ </div><div class="para">
+ root/usr/share/man/man1
+ </div><div class="para">
+ + install -m755 unix2dos /var/tmp/unix2dos-root/usr/bin
+ </div><div class="para">
+ + install -m444 unix2dos.1 /var/tmp/unix2dos-root/usr/share/man/man1
+ </div><div class="para">
+ + /usr/lib/rpm/redhat/brp-compress
+ </div><div class="para">
+ + /usr/lib/rpm/redhat/brp-strip
+ </div><div class="para">
+ + /usr/lib/rpm/redhat/brp-strip-comment-note
+ </div><div class="para">
+ Processing files: unix2dos-2.2-17
+ </div><div class="para">
+ Executing(%doc): /bin/sh -e /var/tmp/rpm-tmp.12033
+ </div><div class="para">
+ + umask 022
+ </div><div class="para">
+ + cd /usr/src/redhat/BUILD
+ </div><div class="para">
+ + cd unix2dos-2.2
+ </div><div class="para">
+ + DOCDIR=/var/tmp/unix2dos-root/usr/share/doc/unix2dos-2.2
+ </div><div class="para">
+ + export DOCDIR
+ </div><div class="para">
+ + rm -rf /var/tmp/unix2dos-root/usr/share/doc/unix2dos-2.2
+ </div><div class="para">
+ + /bin/mkdir -p /var/tmp/unix2dos-root/usr/share/doc/unix2dos-2.2
+ </div><div class="para">
+ + cp -pr COPYRIGHT /var/tmp/unix2dos-root/usr/share/doc/unix2dos-2.2
+ </div><div class="para">
+ + exit 0
+ </div><div class="para">
+ Finding Provides: /usr/lib/rpm/find-provides
+ </div><div class="para">
+ Finding Requires: /usr/lib/rpm/find-requires
+ </div><div class="para">
+ PreReq: rpmlib(PayloadFilesHavePrefix) <= 4.0-1 rpmlib(CompressedFileNames)
+ </div><div class="para">
+ <= 3.0.4-1
+ </div><div class="para">
+ Requires(rpmlib): rpmlib(PayloadFilesHavePrefix) <= 4.0-1
+ </div><div class="para">
+ rpmlib(CompressedFileNames) <= 3.0.4-1
+ </div><div class="para">
+ Requires: libc.so.6 libc.so.6(GLIBC_2.0) libc.so.6(GLIBC_2.1)
+ </div><div class="para">
+ Checking for unpackaged file(s): /usr/lib/rpm/check-files /var/tmp/unix2dos-root
+ </div><div class="para">
+ Wrote: /usr/src/redhat/RPMS/i386/unix2dos-2.2-17.i386.rpm
+ </div><div class="para">
+ Executing(%clean): /bin/sh -e /var/tmp/rpm-tmp.47653
+ </div><div class="para">
+ + umask 022
+ </div><div class="para">
+ + cd /usr/src/redhat/BUILD
+ </div><div class="para">
+ + cd unix2dos-2.2
+ </div><div class="para">
+ + rm -rf /var/tmp/unix2dos-root
+ </div><div class="para">
+ + exit 0
+ </div><div class="para">
+ Executing(--clean): /bin/sh -e /var/tmp/rpm-tmp.47653
+ </div><div class="para">
+ + umask 022
+ </div><div class="para">
+ + cd /usr/src/redhat/BUILD
+ </div><div class="para">
+ + rm -rf unix2dos-2.2
+ </div><div class="para">
+ + exit 0
+ </div><div class="para">
+ With the --rebuild option, the rpmbuild command installs the source RPM for you and then performs the preparation, compile, and installation stages of building a binary RPM. Unless there are errors, you should have a new binary RPM file.
+ </div><div class="para">
+ When complete, the rpmbuild --rebuild command cleans out the built files in the build directory, as if the --clean option were used. The rpmbuild --rebuild command also removes the installed sources and spec file upon completion.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id1315118" class="title">Recompiling binaries from source RPMs</h1></div></div></div><div class="para">
+ If you just want to recompile the files in a source RPM, you can use the --recompile option. The --recompile option tells the rpmbuild command to recompile the binary application from a source RPM.
+ </div><div class="para">
+ For example:
+ </div><div class="para">
+ rpmbuild --recompile package.src.rpm
+ </div><div class="para">
+ This is the same as installing the source RPM and then running rpmbuild -bc --clean with the package spec file.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ There is no difference between --recompile and --rebuild in RPM 4.1. RPM 4.2 fixes this problem.
+ </div><div class="para">
+ </div><div class="para">
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id744420" class="title">SRPMS? Finding source RPMs</h1></div></div></div><div class="para">
+ Often, source RPMs are abbreviated as SRPMs. In fact, if you see a directory named SRPM or SRPMS, chances are the directory holds source RPMs. (Red Hat uses this convention for its Linux distributions.)
+ </div><div class="para">
+ The SRPMS directories on Red Hat CD-ROMs or on the Red Hat FTP Internet site, ftp.redhat.com, indicate directories that hold source RPMs.
+ </div></div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id570726" class="title">Signing Built RPMs</h1></div></div></div><div class="para">
+ Signing RPMs adds an extra level of trustworthiness to your RPMs. A digital signature helps establish that the package comes from you, really you, and not from someone masquerading as you. Unfortunately, the RPM system requires a bit of set up work before you can sign RPMs.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id570739" class="title">Checking that the GPG software is installed</h1></div></div></div><div class="para">
+ To sign packages, you need to ensure that you have the gpg command installed and configured. To check that this command is installed, use a command like the following:
+ </div><div class="para">
+ $ rpm -qf `which gpg`
+ </div><div class="para">
+ gnupg-1.0.7-6
+ </div><div class="para">
+ This shows that the command is available.
+ </div><div class="para">
+ GPG and PGP? Acronyms Explained
+ </div><div class="para">
+ The RPM documentation uses GPG and PGP pretty much interchangeably, so much so, in fact, that you may think these are typographical errors. Not so.
+ </div><div class="para">
+ PGP stands for Pretty Good Privacy. Invented by Phil Zimmerman, PGP was originally invented to encrypt e-mail to allow for private communication. Based on a public-key cryptography algorithm, PGP also supports encrypted digital signatures. These signatures allow you to verify that a package you have downloaded really comes from the vendor you think it does. You do this by using the vendor’s public key.
+ </div><div class="para">
+ GPG stands for GNU Privacy Guard, a free, open-source implementation of PGP from the GNU project. GPG aims to be compatible with the OpenPGP Internet standard as defined in RFC 2440. It started when a number of developers wanted a free implementation. One such free implementation, GPG, allows Linux vendors such as Red Hat to include PGP in their products. So, in a sense, GPG provides PGP.
+ </div><div class="para">
+ PGP has a long and somewhat troubled history as an open-source product and as a commercial product. See www.philzimmermann.com for background on PGP and its long history. See www.gnupg.org for more details on GPG.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id619927" class="title">Configuring a signature</h1></div></div></div><div class="para">
+ To configure a signature, you first need to create a new key with the gpg command, using the --gen-key option, as shown following:
+ </div><div class="para">
+ $ gpg --gen-key
+ </div><div class="para">
+ gpg (GnuPG) 1.0.7; Copyright (C) 2002 Free Software Foundation, Inc.
+ </div><div class="para">
+ This program comes with ABSOLUTELY NO WARRANTY.
+ </div><div class="para">
+ This is free software, and you are welcome to redistribute it
+ </div><div class="para">
+ under certain conditions. See the file COPYING for details.
+ </div><div class="para">
+ </div><div class="para">
+ gpg: Warning: using insecure memory!
+ </div><div class="para">
+ gpg: please see http://www.gnupg.org/faq.html for more information
+ </div><div class="para">
+ gpg: keyring `/home2/ericfj/.gnupg/secring.gpg' created
+ </div><div class="para">
+ gpg: keyring `/home2/ericfj/.gnupg/pubring.gpg' created
+ </div><div class="para">
+ Please select what kind of key you want:
+ </div><div class="para">
+ (1) DSA and ElGamal (default)
+ </div><div class="para">
+ (2) DSA (sign only)
+ </div><div class="para">
+ (4) ElGamal (sign and encrypt)
+ </div><div class="para">
+ (5) RSA (sign only)
+ </div><div class="para">
+ Your selection? 1
+ </div><div class="para">
+ DSA keypair will have 1024 bits.
+ </div><div class="para">
+ About to generate a new ELG-E keypair.
+ </div><div class="para">
+ minimum keysize is 768 bits
+ </div><div class="para">
+ default keysize is 1024 bits
+ </div><div class="para">
+ highest suggested keysize is 2048 bits
+ </div><div class="para">
+ What keysize do you want? (1024)
+ </div><div class="para">
+ </div><div class="para">
+ Requested keysize is 1024 bits
+ </div><div class="para">
+ Please specify how long the key should be valid.
+ </div><div class="para">
+ 0 = key does not expire
+ </div><div class="para">
+ <n> = key expires in n days
+ </div><div class="para">
+ <n>w = key expires in n weeks
+ </div><div class="para">
+ <n>m = key expires in n months
+ </div><div class="para">
+ <n>y = key expires in n years
+ </div><div class="para">
+ Key is valid for? (0)
+ </div><div class="para">
+ </div><div class="para">
+ You need a User-ID to identify your key; the software constructs the user id
+ </div><div class="para">
+ from Real Name, Comment and Email Address in this form:
+ </div><div class="para">
+ "Heinrich Heine (Der Dichter) <heinrichh at duesseldorf.de>"
+ </div><div class="para">
+ </div><div class="para">
+ Real name: Eric Foster-Johnson
+ </div><div class="para">
+ Email address: please_no_spam at nospam.com
+ </div><div class="para">
+ Comment: Example for Red Hat RPM Guide
+ </div><div class="para">
+ You selected this USER-ID:
+ </div><div class="para">
+ "Eric Foster-Johnson (Example for Red Hat RPM Guide) <erc at no_spam.com>"
+ </div><div class="para">
+ Change (N)ame, (C)omment, (E)mail or (O)kay/(Q)uit?
+ </div><div class="para">
+ O
+ </div><div class="para">
+ You need a Passphrase to protect your secret key.
+ </div><div class="para">
+ </div><div class="para">
+ Enter passphrase:
+ </div><div class="para">
+ We need to generate a lot of random bytes. It is a good idea to perform
+ </div><div class="para">
+ some other action (type on the keyboard, move the mouse, utilize the
+ </div><div class="para">
+ disks) during the prime generation; this gives the random number
+ </div><div class="para">
+ generator a better chance to gain enough entropy.
+ </div><div class="para">
+ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ </div><div class="para">
+ +++++++++++++++++++++++++++++++++++..+++++..++++++++++>++++++++++........+++++
+ </div><div class="para">
+ gpg: /home2/ericfj/.gnupg/trustdb.gpg: trustdb created
+ </div><div class="para">
+ public and secret key created and signed.
+ </div><div class="para">
+ key marked as ultimately trusted.
+ </div><div class="para">
+ </div><div class="para">
+ pub 1024D/01681C24 2002-11-05 Eric Foster-Johnson (Example for Red Hat RPM
+ </div><div class="para">
+ Guide) <please_no_spam at nospam.com>
+ </div><div class="para">
+ Key fingerprint = 8C14 A2E9 47D1 301B 2153 7CDF BEE5 9C10 0268 1D24
+ </div><div class="para">
+ sub 1024g/1A15D6C8 2002-11-05
+ </div><div class="para">
+ You can choose the default options for most choices. You need to enter a real name, an e-mail address, and a pass phrase. Remember the pass phrase. You will need to enter the pass phrase every time you wish to sign a package.
+ </div><div class="para">
+ Once you have a key, the next step is to set up some RPM macros. There are a number of places you can do this, but using the .rpmmacros file in your home directory is one of the easiest. Edit this file as shown in the following example:
+ </div><div class="para">
+ %_signature gpg
+ </div><div class="para">
+ %_gpg_path /home2/ericfj/.gnupg
+ </div><div class="para">
+ %_gpg_name EricFJ (Eric Key) <erc at no_spam.com>
+ </div><div class="para">
+ %_gpgbin /usr/bin/gpg
+ </div><div class="para">
+ Add lines like these to the $HOME/.rpmmacros file. (Create this file if it does not exist.)
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ <a class="xref" href="#ch-customizing-rpm">Cap. 20, <em>Customizing RPM Behavior</em></a> covers RPM macros and the $HOME/.rpmmacros file.
+ </div><div class="para">
+ Inside the file, change the %gpg_path macro to the .gnupg directory under your home directory (or the root user’s home directory). Change the %_gpg_name macro to the name you have entered into the gpg program.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id785579" class="title">Signing with the rpmbuild command</h1></div></div></div><div class="para">
+ The --sign option tells the rpmbuild command to sign the created package. You need to have configured the RPM system for your signature as shown in the previous sections.
+ </div><div class="para">
+ When you then build an RPM, you will be prompted for your pass phrase prior to the package build. For example, the following shows this prompt (and truncates the rest of the rpmbuild messages that follow):
+ </div><div class="para">
+ $ rpmbuild -bb --sign xtoolwait-1.2.spec
+ </div><div class="para">
+ Enter pass phrase:
+ </div><div class="para">
+ Pass phrase is good.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id757369" class="title">Signing with the rpm command</h1></div></div></div><div class="para">
+ In addition to the --sign option for the rpmbuild command, you can sign packages that have already been created using the rpm command. The --addsign and --resign options generate new signatures and insert them into the passed-in package file. The basic syntax is:
+ </div><div class="para">
+ rpm --addsign package.rpm
+ </div><div class="para">
+ rpm --resign package.rpm
+ </div><div class="para">
+ The --addsign option adds another signature to the RPM. RPM versions prior to 4.1 allowed you to sign a package with multiple keys, which causes problems for automatic verification. Because of that, use the --resign option, which removes the old signature and inserts a new signature into the package.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id639407" class="title">Verifying signatures</h1></div></div></div><div class="para">
+ You can verify the RPM signature to ensure that the package has not been modified since it has been signed. Verification also checks that the package is signed by the key that matches the claimed vendor.
+ </div><div class="para">
+ To verify the signature in an RPM, use the -K option to the rpm command. The basic syntax is:
+ </div><div class="para">
+ rpm -K package.rpm
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ This is the rpm command, not the rpmbuild command.
+ </div><div class="para">
+ This command accepts the options shown in Table 12-3 to turn off checking for certain types of signatures.
+ </div><div class="para">
+ Table 12-3 Options to turn off signature checking
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Option
+ </div>
+
+ </td><td>
+ <div class="para">
+ Usage
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nogpg
+ </div>
+
+ </td><td>
+ <div class="para">
+ Don’t check for GPG signatures
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nomd5
+ </div>
+
+ </td><td>
+ <div class="para">
+ Don’t check for MD5 signatures
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nopgp
+ </div>
+
+ </td><td>
+ <div class="para">
+ Don’t check for PGP signatures
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ You can also use the --checksig option, which is the same as -K. When you run this command on a package that has a verifiable key, you will see output like the following:
+ </div><div class="para">
+ # rpm -K xtoolwait-1.3-3.src.rpm
+ </div><div class="para">
+ xtoolwait-1.3-3.src.rpm: (sha1) dsa sha1 md5 gpg OK
+ </div><div class="para">
+ This verifies that the package has not been changed from when it was first signed. It also verifies that the signature matches the public key from the vendor of the package. This goes a long ways toward verifying that the package is indeed legitimate.
+ </div><div class="para">
+ To get more information, add a -v (verbose) option. For example:
+ </div><div class="para">
+ $ rpm -Kv vixie-cron-3.0.1-69.src.rpm
+ </div><div class="para">
+ vixie-cron-3.0.1-69.src.rpm:
+ </div><div class="para">
+ Header V3 DSA signature: OK, key ID db42a60e
+ </div><div class="para">
+ Header SHA1 digest: OK (ecbb244ab022ecd23114bb1d6c9bdeb74f8d9520)
+ </div><div class="para">
+ MD5 digest: OK (fb0a75eca1d526d391c36dc956c23bdd)
+ </div><div class="para">
+ V3 DSA signature: OK, key ID db42a60e
+ </div><div class="para">
+ If you run this command on a package that does not verify, you’ll see an error like the following:
+ </div><div class="para">
+ # rpm --checksig xtoolwait-1.3-3.src.rpm
+ </div><div class="para">
+ xtoolwait-1.3-3.src.rpm: (SHA1) DSA sha1 md5 (GPG) NOT OK (MISSING KEYS: GPG#db42a60e)
+ </div><div class="para">
+ Items that fail are listed in uppercase, such as DSA, while items that succeed appear in lowercase. In this example, the sha1 and md5 tests succeeded, while the DSA test failed. This failure does not necessarily mean that the package is not legitimate. This failure can mean one of three things:
+ </div><div class="para">
+ 1.The package was not properly signed in the first place. That is, it is a legitimate package but the package author did not properly sign the RPM.
+ </div><div class="para">
+ 2.The package has been modified in some way. That is, the package is not legitimate.
+ </div><div class="para">
+ 3.The RPM system has not been initialized with the public key from the package vendor.
+ </div><div class="para">
+ From this error, you don’t yet know whether the package is legitimate or not. The first step, though, is to check that you have imported the proper public key from the package vendor.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id723247" class="title">Importing public keys</h1></div></div></div><div class="para">
+ The --import option to the rpm command imports the public key from a given vendor. The format for this key follows:
+ </div><div class="para">
+ The following public key can be used to verify RPM packages built and
+ </div><div class="para">
+ signed by Red Hat, Inc. using `rpm -K' using the GNU GPG package.
+ </div><div class="para">
+ Questions about this key should be sent to security at redhat.com.
+ </div><div class="para">
+ </div><div class="para">
+ -----BEGIN PGP PUBLIC KEY BLOCK-----
+ </div><div class="para">
+ Version: GnuPG v1.0.0 (GNU/Linux)
+ </div><div class="para">
+ Comment: For info see http://www.gnupg.org
+ </div><div class="para">
+ </div><div class="para">
+ mQGiBDfqVEqRBADBKr3Bl6PO8BQ0H8sJoD6p9U7Yyl7pjtZqioviPwXP+DCWd4u8
+ </div><div class="para">
+ HQzcxAZ57m8ssA1LK1Fx93coJhDzM130+p5BG9mYSPShLabR3N1KXdXAYYcowTOM
+ </div><div class="para">
+ GxdwYRGr1Spw8QydLhjVfU1VSl4xt6bupPbFJbyjkg5Z3P7BlUOUJmrx3wCgobNV
+ </div><div class="para">
+ EDGaWYJcch5z5B1of/41G8kEAKii6q7Gu/vhXXnLS6m15oNnPVybyngiw/23dKjS
+ </div><div class="para">
+ ti/PYrrL2J11P2ed0x7zm8v3gLrY0cue1iSba+8glY+p31ZPOr5ogaJw7ZARgoS8
+ </div><div class="para">
+ BwjyRymXQp+8Dete0TELKOL2/itDOPGHW07SsVWOR6cmX4VlRRcWB5KejaNvdrE5
+ </div><div class="para">
+ 4XFtOd04NMgWI63uqZc4zkRa+kwEZtmbz3tHSdWCCE+Y7YVP6IUf/w6YPQFQriWY
+ </div><div class="para">
+ FiA6fD10eB+BlIUqIw80EqjsBKmCwvKkn4jg8kibUgj4/TzQSx77uYokw1EqQ2wk
+ </div><div class="para">
+ OZoaEtcubsNMquuLCMWijYhGBBgRAgAGBQI36lRyAAoJECGRgM3bQqYOhyYAnj7h
+ </div><div class="para">
+ VDY/FJAGqmtZpwVp9IlitW5tAJ4xQApr/jNFZCTksnI+4O1765F7tA==
+ </div><div class="para">
+ =3AHZ
+ </div><div class="para">
+ -----END PGP PUBLIC KEY BLOCK-----
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ For reasons of space, this is not a complete key.
+ </div><div class="para">
+ You need to pass the name of the text file that holds the key to the rpm --import command, as shown following:
+ </div><div class="para">
+ rpm --import key_file
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ You must be logged in as the root user to import keys.
+ </div><div class="para">
+ For example:
+ </div><div class="para">
+ # rpm --checksig xtoolwait-1.3-3.src.rpm
+ </div><div class="para">
+ xtoolwait-1.3-3.src.rpm: (SHA1) DSA sha1 md5 (GPG) NOT OK (MISSING KEYS: GPG#db42a60e)
+ </div><div class="para">
+ </div><div class="para">
+ # rpm --import RPM-GPG-KEY
+ </div><div class="para">
+ </div><div class="para">
+ # rpm --checksig xtoolwait-1.3-3.src.rpm
+ </div><div class="para">
+ xtoolwait-1.3-3.src.rpm: (sha1) dsa sha1 md5 gpg OK
+ </div><div class="para">
+ This example shows an error message when trying to verify the key. Then, after importing the Red Hat public key, the verification works.
+ </div><div class="para">
+ If, after importing this key, you still have problems, you can assume there are problems with the package. Many administrators will refuse to install such packages.
+ </div><div class="para">
+ Warning
+ </div><div class="para">
+ You should be careful with packages that have signatures that do not verify.
+ </div><div class="para">
+ To list the available keys, use a command like the following:
+ </div><div class="para">
+ $ rpm -qa | grep -i gpg
+ </div><div class="para">
+ gpg-pubkey-db42a60e-37ea5438
+ </div><div class="para">
+ This example shows one key installed.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ You can erase this key as if it were a package, using the rpm -e command.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id550839" class="title">Getting the Red Hat public key</h1></div></div></div><div class="para">
+ Strangely enough, the Red Hat public key is not installed when you install Red Hat Linux 8.0. If you need the key, the Red Hat public key is available on the root directory of all Red Hat Linux CD-ROMs, as shown in the following listing:
+ </div><div class="para">
+ $ ls /mnt/cdrom/
+ </div><div class="para">
+ EULA GPL README RedHat/ RPM-GPG-KEY SRPMS/ TRANS.TBL
+ </div><div class="para">
+ Simply copy the RPM-GPG-KEY file to get the public key. Then use the rpm --import command with this key file.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ You can also download this key file from the Red Hat FTP site, at ftp://ftp.redhat.com/pub/redhat/linux/8.0/en/os/i386/.
+ </div></div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id714646" class="title">Summary</h1></div></div></div><div class="para">
+ This chapter covers options for the rpmbuild command that allow you to achieve a finer grain of control over how the command works. For example, the --short-circuit option tells the rpmbuild command to build just the stages you ask for. This helps when you have problems in one area of building an RPM and don’t want to start over each time you try to see if the problem is solved.
+ </div><div class="para">
+ The rpmbuild command also supports a set of -t options that work like the -b options, except the -t options try to build an RPM from a tar archive of sources (a tarball) instead of an RPM spec file. In this case, the rpmbuild command tries to work without a spec file.
+ </div><div class="para">
+ The --rebuild option tells the rpmbuild command to install a source RPM, build the binary RPM, and clean out the installed source RPM. This provides quite a shortcut for installing binary RPMs from source RPMs.
+ </div><div class="para">
+ RPMs should be signed to provide an extra level of authentication. This system isn’t perfect, but it helps you verify that a package is from the person it says it is from and that the package has not been modified. You can check the signature on RPM packages you download. You can also, with some configuration, sign the packages you create.
+ </div><div class="para">
+ </div></div></div><div xml:lang="ro" class="chapter" id="ch-extra-packaging-tools" lang="ro"><div class="titlepage"><div><div><h2 class="title">Cap. 12. Supplemental Packaging Software</h2></div></div></div><div class="toc"><dl><dt><span class="sect1"><a href="#id943659">12.1. Packaging Aids</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id943675">12.1.1. Using VIM spec plugins to improve spec file editing</a></span></dt><dt><span class="sect2"><a href="#id853827">12.1.2. Adding functions with emacs rpm-spec-mode</a></span></dt><dt><span class="sect2"><a href="#id1329990">12.1.3. Validating and debugging spec files with rpmlint</a></span></dt><dt><span class="sect2"><a href="#id571366">12.1.4. Generating the %files section with RUST</a></span></dt><dt><span class="sect2"><a href="#id737961">12.1.5. setup.sh and MakeRPM.pl</a></span></dt><dt><span class="sect2"><a href="#id561611">12.1.6. Manipulating Package Files with rpm2cpio</a></span></dt></dl></dd><dt><span c
lass="sect1"><a href="#id854931">12.2. Summary</a></span></dt></dl></div><div class="para">
+ This chapter covers:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Understanding packaging aids
+ </div></li><li class="listitem"><div class="para">
+ Manipulating packages
+ </div></li></ul></div><div class="para">
+ RPM is intended to make system management easier, both for system administrators and other users who do all the day-to-day work of installing and removing applications and for developers and other users who do all the work of preparing applications for installation. For RPM packagers, the work involved in preparing an application for installation has two phases: first, the software must be compiled (if it is not written in an interpreted language such as Perl) and otherwise configured for the system on which it will be installed; then the RPM package of the software must be prepared by creating a spec file that properly packages it into an RPM. In contrast, packagers who choose to package applications in a simpler format, such as gzipped tarballs (compressed tar archives), have less work ahead of them, since they need only concern themselves with the first step.
+ </div><div class="para">
+ After a packager has prepared an RPM package once, RPM makes the first step (compilation and configuration) easier when the packager has to package an updated version of the same software; RPM does a lot of work to track compilation commands, any needed patches, and any configuration modifications discovered to be necessary to prepare the software. Similarly, once an RPM spec file has been produced for an application, updating that spec file to support a newer version of that application is usually trivial. For these reasons, using RPM instead of a simpler, less end-user-friendly package format (such as gzipped tarballs) is a bit of a tradeoff for the packager; preparing an RPM of an application requires a little more initial time and work than preparing a gzipped tarball of that same application, but once created, the RPM package takes less time and effort to keep current than the gzipped tarball requires.
+ </div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id943659" class="title">Packaging Aids</h1></div></div></div><div class="para">
+ However, several helper tools are also available for RPM packagers. These tools can be used at various stages in the process of producing a high-quality RPM package to simplify the tasks that an RPM packager must perform. These tools include syntax-highlighting modes for various text editors, making production and maintenance of spec files easier; macro packages for popular text editors, simplifying the generation and maintenance of spec files; tools that generate spec files, simplifying initial spec file creation; and debuggers that validate produced binary RPMs, helping ensure that the spec file used to create the packages is accurate and high quality.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id943675" class="title">Using VIM spec plugins to improve spec file editing</h1></div></div></div><div class="para">
+ Unix systems have traditionally shipped the legendary (or notorious, depending upon your point of view) vi editor (pronounced vee eye) as their default text editor. Vi was initially developed by Bill Joy in 1976 for BSD Unix. It eventually was incorporated in AT& T System V Unix as well and later was mandated by the POSIX 1003 standards (which define what an OS must have to be Unix-compatible), thereby conquering all facets of the Unix world.
+ </div><div class="para">
+ The original vi source code is no longer freely available, but several clones of the vi program have been created over the years. The most popular of these vi clones is probably Vi IMproved, or VIM (www.vim.org). VIM is the standard vi implementation (meaning that when you type vi at the command prompt, the program you really are running is vim) on many Linux distributions, including Red Hat Linux. It is also freely available for most other Unixes and even for non-Unix systems such as Microsoft Windows.
+ </div><div class="para">
+ VIM is a fully backwards-compatible implementation of the original vi editor, although it also offers many additional features that vi did not support. One VIM feature that can be extremely useful when preparing spec files is colorized syntax highlighting. VIM has an extensible interface through which it can be told about the syntax used for files of various types. Once it understands a filetype's syntax, it can color the various syntactic structures of that file in different ways. For example, when editing a Bourne shell script using VIM, comments are typically blue, control statements (if, for, do, and so on) are yellow, variables are purple, and so forth. Many people find this feature very useful, since a single glance reveals the entire logical structure of the file. Furthermore, errors in the file (such as a missing done statement failing to close a do loop in a Bourne shell script) are often immediately obvious when using such a colorizing editor.
+ </div><div class="para">
+ Usually, VIM does not understand the structure of RPM spec files. When preparing a spec file, VIM displays all text in the same color. A spec.vim syntax file is available for VIM that makes VIM aware of the syntax used for RPM spec files. When this file is used, the various structural components (%define, preamble statements, %build, and so forth) are all colorized, making the logic of the spec file readily apparent.
+ </div><div class="para">
+ The spec.vim file that provides VIM with an understanding of spec-file syntax is bundled with newer versions of VIM, or it can be downloaded from the Internet. Most RPM-based Linux distributions, including Red Hat Linux, ship this file with VIM as part of their distribution and even automatically configure VIM to load this syntax file any time an RPM spec file is being edited. When using VIM on a system that does not automatically load spec.vim whenever spec files are edited, you should download the spec.vim file (I tend to save such personal extensions in ~/etc/vim, but you can save it any place you prefer).
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ Download the spec.vim syntax file for VIM from <a href="http://www.panix.com/~elflord/vim/syntax/spec.vim">http://www.panix.com/~elflord/vim/syntax/spec.vim</a>
+ </div><div class="para">
+ Once downloaded, configure VIM to load your new syntax file. You can do this by putting the following in your ~/.vimrc file (assuming you have saved the file as ~/etc/vim/spec.vim; adjust the path as necessary if you saved it elsewhere):
+ </div><div class="para">
+ augroup syntax
+ </div><div class="para">
+ au! BufNewFile,BufReadPost *.spec so ~/etc/vim/spec.vim
+ </div><div class="para">
+ au BufNewFile,BufReadPost *.spec so ~/etc/vim/spec.vim
+ </div><div class="para">
+ augroup END
+ </div><div class="para">
+ This statement will instruct VIM to load the syntax file whenever a file named with a .spec extension is edited. You can now even customize the colors which VIM uses, if you like, by editing ~/etc/vim/spec.vim!
+ </div><div class="para">
+ The VIM editor has hundreds of built-in commands for formatting text. If necessary, it can even be extended with new commands. Furthermore, these commands can be defined in FileType plugins, so that different commands are loaded depending upon the type of file being edited (just as different syntax matching can be used depending upon the type of file being edited). Gustavo Niemeyer has written a spec plugin, pi_spec, which defines various commands that can be used when working with RPM spec files. Currently, this plugin can be used to automate maintenance of the %changelog section of RPM spec files.
+ </div><div class="para">
+ By default, the spec plugin provides a macro, spec_chglog, which is mapped to the <LocalLeader>-c key. Normally, the LocalLeader key in VIM is mapped to "\", a backslash character. This means you press \c to load the spec_chglog macro. If desired, you can instead map spec_chglog to a different key by putting a statement like the following in your ~/.vimrc file.
+ </div><div class="para">
+ au FileType spec map <buffer> C <Plug>SpecChangelog
+ </div><div class="para">
+ In this case, that statement would map the macro to the "C" key, but you can map it to a different key by replacing the "C" in the statement with whichever key or key combination you prefer.
+ </div><div class="para">
+ The spec_chglog macro checks the %changelog in the spec file currently being edited and makes sure that the last entry in this %changelog was written today and was written by you. If it was, the macro adds a new item to the entry. If it was not written today, or was written today, but not by you, the macro adds an entirely new entry. Optionally, the macro also checks that the name, version, and release of the package are correct and will update the release if it is incorrect. In addition, the macro maps the percent key, %, making it usable in command mode in VIM to move quickly between sections within a spec file.
+ </div><div class="para">
+ To help spec_chglog, you can define a few variables in your ~/.vimrc file to customize its behavior. The variable spec_chglog_format defines what the macro uses for new %changelog entries. If you do not define this variable, the macro will ask you for an e-mail address and construct it for you the first time you use the macro. Alternatively, you can customize it yourself by adding an entry like the following to your ~/.vimrc file.
+ </div><div class="para">
+ let spec_chglog_format = "%a %b %d %Y Your Name <your at email.address>"
+ </div><div class="para">
+ The preceding format is what Red Hat's developers use for Red Hat Linux spec files and results in a %changelog entry that looks like the following, with the user name and e-mail address changed to protect the innocent:
+ </div><div class="para">
+ * Mon Apr 15 2002 Bob Marley <bob at marley.yow>
+ </div><div class="para">
+ The variables in the spec_chglog_format control the time format that is used. If you want different time formats in your %changelog entry, you can replace the variables (using %A instead of %a would cause the full weekday name, such as "Monday", to be printed) using the documentation in the strftime(3) man page as a guideline.
+ </div><div class="para">
+ By default, the macro will insert new entry items after existing items. For example, if I already have a %changelog entry for today that reads as follows:
+ </div><div class="para">
+ * Mon May 6 2002 Bob Marley <bob at marley.yow>
+ </div><div class="para">
+ - Updated to newest release
+ </div><div class="para">
+ Then, using the macro to add a new entry for an additional patch I added will, by default, result in an entry that reads:
+ </div><div class="para">
+ * Mon May 6 2002 Bob Marley <bob at marley.yow>
+ </div><div class="para">
+ - Updated to newest release
+ </div><div class="para">
+ - Added Solaris compile patch
+ </div><div class="para">
+ If I want, I can instead have new items inserted before existing items, so that my second entry instead looks like
+ </div><div class="para">
+ * Mon May 6 2002 Bob Marley <bob at marley.yow>
+ </div><div class="para">
+ - Added Solaris compile patch
+ </div><div class="para">
+ - Updated to newest release
+ </div><div class="para">
+ To have new items inserted before existing items, simply add the following line to your ~/.vimrc file:
+ </div><div class="para">
+ let spec_chglog_prepend = 1
+ </div><div class="para">
+ Optionally, the macro can track version and release numbers in the %changelog entries automatically. Adding the line
+ </div><div class="para">
+ let spec_chglog_release_info = 1
+ </div><div class="para">
+ results in the first item in every changelog entry automatically reflecting the version and release, so that my %changelog entry might instead look like the following:
+ </div><div class="para">
+ * Mon May 6 2002 Bob Marley <bob at marley.yow>
+ </div><div class="para">
+ + httpd-2.0.36-2
+ </div><div class="para">
+ - Updated to newest release
+ </div><div class="para">
+ - Added Solaris compile patch
+ </div><div class="para">
+ If this feature is enabled, the macro automatically checks the version and release information to make sure that they have increased. If they haven't, it will offer to update them for you. Add the following line to your ~/.vimrc file to disable this feature, if necessary.
+ </div><div class="para">
+ let spec_chglog_never_increase_release = 1
+ </div><div class="para">
+ This spec plugin ships with newer versions of VIM. Both it and the VIM spec syntax highlighting extensions can be very useful for speeding spec file editing and debugging, and are well worth trying out if you are a VIM user.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ You can find out more about vim at www.vim.org.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id853827" class="title">Adding functions with emacs rpm-spec-mode</h1></div></div></div><div class="para">
+ Of course, not everyone in the world uses VIM. Another commonly used editor is the emacs editor originally developed by Richard M. Stallman. Unlike vi, emacs is not considered an essential Unix component and is not always found installed on a Unix system, although it is bundled with just about every Linux distribution.
+ </div><div class="para">
+ Over the years, two major emacs variants have emerged. GNU Emacs is produced by the Free Software Foundation and can be downloaded from www.gnu.org/software/emacs/emacs.html. XEmacs is based on GNU Emacs and is available from www.xemacs.org. Historically, the two differed in their user interfaces (XEmacs, as the name suggests, had an X Window interface, though GNU Emacs has one as well these days) and in some technical details of how they operated. Both are freely available under the terms of the GNU GPL, so you can download and try either or both if they are not already on your system.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ See <a class="xref" href="#ch-licensing">Cap. 27, <em>Licensing RPM</em></a> for more on the GNU GPL, or General Public License.
+ </div><div class="para">
+ Red Hat Linux includes RPMs of both GNU Emacs and XEmacs as part of the distribution, and most other Linux distributions will include one or both as well.
+ </div><div class="para">
+ Like VIM, both GNU Emacs and XEmacs support syntax highlighting. They are also both extensible, having the ability to load mode files that add new commands and functions. Stig Bjørlykke has written a mode, rpm-spec-mode.el, which works with both GNU Emacs and with XEmacs to add many functions, making it easier to use when editing RPM spec files. Red Hat Linux includes and enables this mode in both GNU Emacs and XEmacs, as do many other Linux distributions.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ You can download this emacs mode from http://tihlde.org/~stigb/rpm-spec-mode.el.
+ </div><div class="para">
+ After downloading, you will need to put the following lines in your ~/.emacs init files (for GNU Emacs) or ~/.xemacs init files (for XEmacs) to instruct emacs to load rpm-spec-mode whenever a file with a .spec extension is being edited:
+ </div><div class="para">
+ (autoload 'rpm-spec-mode "rpm-spec-mode.el" "RPM spec mode." t)
+ </div><div class="para">
+ (setq auto-mode-alist (append '(("\\.spec" . rpm-spec-mode)) auto-mode-alist))
+ </div><div class="para">
+ </div><div class="para">
+ Once installed, rpm-spec-mode will provide emacs with additional support for editing RPM spec files. Figure 13-1 shows this mode in GNU Emacs.
+ </div><div class="para">
+ 54965-0 Fg1301.tiff here; needs to be cropped to just the central window
+ </div><div class="para">
+ Figure 13-1: Gnu Emacs using rpm-spec-mode
+ </div><div class="para">
+ Figure 13-2 shows this mode in XEmacs.
+ </div><div class="para">
+ 54965-0 Fg1302.tiff here; needs to be cropped to just the central window
+ </div><div class="para">
+ Figure 13-2: XEmacs using rpm-spec-mode
+ </div><div class="para">
+ With this mode, emacs can do syntax highlighting of spec files, just like VIM. The mode file rpm-spec-mode.el contains the emacs instructions that specify what should be highlighted and what colors should be used for highlighting.
+ </div><div class="para">
+ Tip
+ </div><div class="para">
+ If you do not see syntax highlighting when you edit a spec file, your emacs session may or may not be currently configured to do syntax highlighting. First, make sure that the status bar at the bottom of your emacs window says (RPM-SPEC), indicating that rpm-spec-mode is being used. If it doesn't, double-check the rpm-spec-mode installation instructions. If the status bar does indicate that you are using rpm-spec-mode, also double-check that syntax highlighting (which, in emacs, is a global configuration option) has been enabled. In both GNU Emacs and XEmacs, the Options menu has a Syntax Highlighting option that must be enabled before emacs will colorize spec file syntactic structures.
+ </div><div class="para">
+ In addition to providing syntax colorization, rpm-spec-mode adds a variety of new functions to emacs that can be used to speed the process of creating or editing RPM spec files. These new functions appear on the RPM-Spec menu that is added to emacs by rpm-spec-mode. Many of the functions are similar to the functions added to VIM by the spec_chglog macro. Navigation functions to move quickly through a spec file are provided, so that Ctrl+C, Ctrl+N (press Ctrl+C followed by Ctrl+N) will move the cursor to the next major section of the spec file, while Ctrl+C, Ctrl+P will move the cursor to the prior major section of the spec file. Similarly, macros are also defined to increment the release tag (Ctrl+C, R) and the very handy option to add new %changelog entries (Ctrl+C, E). Like the VIM macros for adding %changelog entries, the rpm-spec-mode command checks to see if an entry already exists for today. If not, it adds a new entry, but if so, it just adds a new item to the exist
ing entry. For %changelog entries to have the correct e-mail address, the emacs variable user-mail-address must be set correctly. If it is not set on your system, you can add the following line to your emacs initialization files:
+ </div><div class="para">
+ (setq user-mail-address "your at email.address")
+ </div><div class="para">
+ In addition to these basic functions, rpm-spec-mode offers more advanced spec file creation support. Opening a new buffer in emacs for a spec file that does not already exist automatically generates a skeleton spec file.
+ </div><div class="para">
+ To further speed things up, emacs offers a number of macros for the main tasks in writing an RPM spec file. Table 13-1 lists these macros.
+ </div><div class="para">
+ Table 13-1Macro commands for The RPM SPEC MODE IN EMacs
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Command
+ </div>
+
+ </td><td>
+ <div class="para">
+ Function
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Ctrl+C Tab
+ </div>
+
+ </td><td>
+ <div class="para">
+ Adds a new tag to the spec file
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Ctrl+C Ctrl+F F
+ </div>
+
+ </td><td>
+ <div class="para">
+ Adds a new file to the %files section
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Ctrl+C Ctrl+F C
+ </div>
+
+ </td><td>
+ <div class="para">
+ Adds a new configuration file to the %files section
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Ctrl+C Ctrl+F D
+ </div>
+
+ </td><td>
+ <div class="para">
+ Adds a new documentation file to the %files section
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Ctrl+C Ctrl+F G
+ </div>
+
+ </td><td>
+ <div class="para">
+ Adds a new ghost file to the %files section
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Ctrl+C Ctrl+D D
+ </div>
+
+ </td><td>
+ <div class="para">
+ Adds a new directory to the %files section
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Ctrl+C Ctrl+D O
+ </div>
+
+ </td><td>
+ <div class="para">
+ Adds a new documentation directory to the %files section
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Ctrl+C Ctrl+C U
+ </div>
+
+ </td><td>
+ <div class="para">
+ Changes the umask in %defattr entries in %files
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Ctrl+C Ctrl+C O
+ </div>
+
+ </td><td>
+ <div class="para">
+ Changes the owner in %defattr entries in %files
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Ctrl+C Ctrl+C G
+ </div>
+
+ </td><td>
+ <div class="para">
+ Changes the group in %defattr entries in %files
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ Furthermore, rpm-spec-mode even adds macros to emacs that can be used to build RPMs from spec files without even having to exit emacs! Since the process of constructing spec files is often iterative (make new spec, build RPM from spec, find mistake, edit spec, build RPM from spec, find mistake, and so on), this capability of emacs to be used as an IDE for RPM package generation is extremely useful. Basic macros exist to do complete builds (Ctrl+C B to build a binary package, Ctrl+C S to build a source package, and Ctrl+C A to build both). Macros can also be used to execute various intermediate steps, such as the %prep stage (Ctrl+C P), the %build stage (Ctrl+C C), or the %install stage (Ctrl+C I). Various options of the build process can also be controlled, such as GPG-signing of generated packages.
+ </div><div class="para">
+ If you are a user of GNU Emacs or XEmacs, you should definitely take the time to learn to use rpm-spec-mode. Being able to build packages from within the editor where you are editing the spec file that builds those packages is a great productivity gain for many people.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id1329990" class="title">Validating and debugging spec files with rpmlint</h1></div></div></div><div class="para">
+ Both VIM and emacs extensions help with the process of initially creating spec files and with the maintenance of existing RPM spec files. After a spec file has been created, and RPMs have been created using that spec, the binary RPMs generated from the spec can be validated using the rpmlint command. The name rpmlint comes from lint, the traditional Unix utility that can "sanity-check" C source code, looking for certain classes of common C coding mistakes. The idea behind rpmlint is similar; it processes binary RPMs, checking for certain common mistakes made by RPM packagers.
+ </div><div class="para">
+ The rpmlint command currently ships with a wide variety of checks and is written using a modular interface so that additional checks can easily be added if needed. Currently, rpmlint can check that all binary files in the package are correct (making sure that a .noarch.rpm package does not contain binary files, that no binaries are being installed in /etc, that the binary file types in the package are appropriate for the package architecture, that shared libraries are configured correctly, and that all executables are stripped). It can also check the validity of files marked as configuration files in the RPM (ensuring that configuration files are only being installed in /etc, not in /usr) and that the package file complies with the distribution's policies for packages (checking things such as the compression of man pages and Info pages and the correctness of vendor and distribution fields in the package header).
+ </div><div class="para">
+ In addition, rpmlint performs a variety of checks to ensure that the package complies with the Filesystem Hierarchy Standard (verifying that files are installed in their standard locations on the system), the Linux Standards Base (verifying that package-file naming is LSB-compliant) and that files have correct ownerships and permissions. Init scripts are double-checked (for packages that have init scripts) to ensure that the basic structure of the init script is correct and that appropriate %post and %preun configuration directives are being run to configure the init script on the system. %post, %pre, and %preun scripts are also double-checked (ensuring that only valid interpreters are specified for scripts and that scripts are written in valid syntax). The validity of the package itself is also checked in various ways (ensuring that the package is GPG-signed, that the package's source RPM is correctly prepared, that the package spec file uses correct syntax, and that all
tags used in the package header are valid).
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ To find out more about the Filesystem Hierarchy Standard, see www.pathname.com/fhs/. To find out more about the Linux Standards Base, see www.linuxbase.org.
+ </div><div class="para">
+ Download rpmlint from www.lepied.com/rpmlint. It is written entirely in Python, so a Python interpreter is necessary to run it.
+ </div><div class="para">
+ Once installed, rpmlint can be configured on a system-wide basis, using the /etc/rpmlint/config file, or on a per-user basis, using the $HOME/.rpmlintrc file. This file can specify checks to perform, check output that should be ignored, and configuration options. Configuration options can be specified, listing what entries are valid for various fields in the RPM header, such as the Vendor and Packager fields. By default, Red Hat Linux ships with this configuration file set to validate packages to make sure they are suitable for Red Hat Linux; if packaging for a different distribution, this file might need to be modified.
+ </div><div class="para">
+ Once rpmlint has been installed and configured, it can be run against RPMs. For example, rpmlint helps with creating packages, such as tin (a popular Usenet client) for Red Hat Linux, since it is not included with the distribution. After preparing a tin spec file, then building RPMs from that file, you can typically double-check them using rpmlint.
+ </div><div class="para">
+ For example, when running rpmlint on a source RPM, you’ll see output like the following:
+ </div><div class="para">
+ $ rpmlint tin-1.5.12-1.src.rpm
+ </div><div class="para">
+ E: tin no-packager-tag
+ </div><div class="para">
+ W: tin invalid-license distributable
+ </div><div class="para">
+ W: tin no-url-tag
+ </div><div class="para">
+ W: tin strange-permission tin-1.5.12.tar.bz2 0664
+ </div><div class="para">
+ W: tin obsolete-tag Copyright
+ </div><div class="para">
+ $
+ </div><div class="para">
+ For the most part, this package looks fine according to the rpmlint output. The permissions on the tin source code can be changed (0644 is the "preferred" permissions), and you might want to change my spec file to use the License tag instead of the now-obsolete Copyright tag. Similarly, you might want to add a URL tag to the package to point to the URL for the software.
+ </div><div class="para">
+ When running rpmlint on a binary RPM, you’ll see output like the following:
+ </div><div class="para">
+ $ rpmlint tin-1.5.12-1.i386.rpm
+ </div><div class="para">
+ W: tin invalid-vendor None
+ </div><div class="para">
+ W: tin invalid-distribution None
+ </div><div class="para">
+ E: tin no-packager-tag
+ </div><div class="para">
+ W: tin invalid-license distributable
+ </div><div class="para">
+ W: tin no-url-tag
+ </div><div class="para">
+ $
+ </div><div class="para">
+ With this output, the binary package looks fine. You should set a I don’t bother setting a vendor, distribution, and packager but you can ignore those warnings. Similarly, rpmlint warns because it does not recognize the license type used, "distributable". You can fix this, you can ignore this, or you can modify /etc/rpmlint/config so that rpmlint recognizes "distributable" as a valid license.
+ </div><div class="para">
+ The sorts of validity checks that rpmlint can do make it valuable for ensuring the quality and consistency of RPMs. Most RPM-based Linux distributions validate their entire distribution using rpmlint. Using it for packages you prepare is a good idea as well.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id571366" class="title">Generating the %files section with RUST</h1></div></div></div><div class="para">
+ For the most part, maintaining RPM spec files is relatively straightforward. Creating spec files from scratch, however, can be a little bit more challenging. Tools like rpm-spec-mode for emacs can help with the process, generating skeleton spec file templates that can be filled in, but these sorts of tools do not address the step that most new RPM packagers seem to find most difficult: generating the %files section. Creating a complete, accurate list of all needed files supplied by an application can be difficult, particularly when it is an application with which you are unfamiliar. Most software supports installation to a temporary location; if the software you are packaging allows this, generation of %files is (almost) as simple as using BuildRoot to install the application to a temporary directory, then running an ls -lR command in that subdirectory to see all the installed files and directories. Even then, though, the output from ls -lR must be cleaned up and converted
into %files format for adding to the spec file. All of this takes time.
+ </div><div class="para">
+ A couple of tools exist to reduce the amount of work needed for this stage of the process, automating the generation of the %files section of spec files. The most sophisticated of these toolsets is RUST.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ Download RUST from www.rusthq.com.
+ </div><div class="para">
+ RUST consists of two tools: crust and rust. The crust command provides a command-line tool that can create a chroot() jail, in which software can be built and installed, and then automatically generate a spec file that documents the files that were installed. This not only eliminates the need to generate a %files section for a spec file manually but also removes the need to modify software to support installation to a temporary location using BuildRoot, a sometimes difficult task.
+ </div><div class="para">
+ The rust command provides a graphical front end to the crust command, as shown in Figure 13-3.
+ </div><div class="para">
+ 54965-0 Fg1303.tiff here
+ </div><div class="para">
+ Figure 13-3: rust, a drag-and-drop spec file generator
+ </div><div class="para">
+ The rust command provides a graphical interface that can be used to control crust and supports drag-and-drop creation of spec files. In the rust interface, two file trees are displayed. The left-hand tree displays the local file system, while the right-hand tree displays the file tree inside the crust chroot() jail. Files that should be packaged together can just be dragged from their current locations on the system (displayed in the left-hand tree) to their final destinations in the right-hand tree. You can then click the makeRPM choice to generate an RPM containing those files. Although not terribly useful for packages being generated from source code, this feature can greatly simplify creation of RPMs of applications that are only supplied in binary format (such as the Linux Adobe Acrobat reader).
+ </div><div class="para">
+ RUST's rust application can be useful in some circumstances (providing new developers a graphical tool that can be used to generate binary RPMs), and crust is more generally useful for packaging difficult-to-package software that needs to be built and installed in a chroot() jail. Unfortunately, development of RUST appears to have stopped, so extension of RUST to become a more generally useful IDE for RPM generation is not likely to happen. However, the project is licensed under the GNU GPL (<a class="xref" href="#ch-licensing">Cap. 27, <em>Licensing RPM</em></a> ), so it might be resumed by another developer or team of developers.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id737961" class="title">setup.sh and MakeRPM.pl</h1></div></div></div><div class="para">
+ Other tools that have been developed to simplify the process of creating an RPM spec file take an entirely different approach. Tools such as setup.sh, available from www.mmedia.is/~bre/programs/setup.sh, are intended to function as wrappers around the existing build commands (./configure and make) for software. These types of tools take the approach of using the standard build tools for software (since those tools must always be used to build the software, whether using RPM or compiling the software from a source tarball) and capturing the output to generate an RPM spec file automatically.
+ </div><div class="para">
+ The MakeRPM.pl Perl script, available from www.perl.com/CPAN/modules/by-authors/id/JWIED, is another example of such an approach. MakeRPM.pl is a more specialized tool than setup.sh, as MakeRPM.pl is intended only for producing RPMs from Perl modules packaged in CPAN (www.cpan.org). It is implemented as a wrapper around the standard commands (perl Makefile.PL ; make ; make test ; make install) used to install Perl CPAN software.
+ </div><div class="para">
+ MakeRPM.pl actually works quite well for its intended purpose at mdproducing packages of CPAN modules. The setup.sh script is currently viewable mainly as a proof of concept, rather than being a generally universal automatic spec file generator. In the future, when spec files are likely to be representable using a formal closed-syntax grammar, it is possible that more generalized spec file generation tools will be developed. Until that time, however, some of the previously mentioned tools, particularly the VIM and emacs extensions, can provide assistance when manually generating spec files.
+ </div><div class="para">
+ Cross-reference
+ </div><div class="para">
+ For more discussion of the future of RPM, you can turn to <a class="xref" href="#ch-rpm-evolution">Cap. 23, <em>RPM Feature Evolution</em></a> .
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id561611" class="title">Manipulating Package Files with rpm2cpio</h1></div></div></div><div class="para">
+ Normally, RPM packagers are concerned with taking source code or binary files, and producing an RPM that contains those files and can be used to install them on end-users' systems. Sometimes, packagers and end users find themselves in the opposite position, that of having a source or binary RPM package file and needing to extract its contents. An RPM can always be installed to access its contents (either source code, patches, and a spec file which get put under %_topdir for a source RPM, or software which gets put in system directories for a binary RPM), but that is often overkill. I frequently want to extract a single patch file, or the spec file, from a source RPM, but I don't really need to install the entire source RPM. Similarly, people often want to extract the contents of RPMs on systems that do not come with RPM, such as Solaris.
+ </div><div class="para">
+ Fortunately, tools are available that can process RPM package files into a format from which their content can be extracted. Structurally speaking, RPM package files are compressed cpio archives that have additional binary data added to the beginning containing various meta-data about the package (specifying its architecture and OS, for example), a GPG signature if the package is signed, and so forth. If this binary data is removed from the beginning of the RPM package file, the remainder is a System V Release 4-style cpio file that can be manipulated using any reasonably complete cpio command. Several different tools, each sporting the name rpm2cpio, are available which can do this binary data removal, converting an RPM package file into a standard cpio archive.
+ </div><div class="para">
+ RPM ships with an rpm2cpio utility that can be used to convert RPM package files to cpio files. (<a class="xref" href="#ch-rpm-overview">Cap. 2, <em>RPM Overview</em></a> introduces the rpm2cpio utility.) For example, if you have a source RPM package file and want to extract its files without having to install it, you can process it through rpm2cpio. The rpm2cpio command takes as input an RPM package file, and produces a cpio file on standard output. For example, to redirect the output to a file, use a command like the following:
+ </div><div class="para">
+ $ rpm2cpio fluxbox-0.1.8-2.src.rpm > fluxbox-0.1.8-2.cpio
+ </div><div class="para">
+ $
+ </div><div class="para">
+ This command creates a cpio archive from the package. You can later use cpio commands on the output file. You can also pipe the output of rpm2cpio through the cpio command:
+ </div><div class="para">
+ $ rpm2cpio fluxbox-0.1.8-2.src.rpm | cpio -i -d
+ </div><div class="para">
+ 656 blocks
+ </div><div class="para">
+ $
+ </div><div class="para">
+ This command extracts the contents of the package.
+ </div><div class="para">
+ This rpm2cpio command is bundled with RPM and is installed on most RPM-based Linux distributions, including Red Hat Linux. However, it is less useful on systems that do not come with RPM, such as Solaris. This "standard" implementation of rpm2cpio is written in C, and so must be compiled before it can be used. Since most commercial Unix systems do not come with a C compiler by default (unlike Linux and other free Unixes, such as the BSD operating systems), compiling this rpm2cpio code can be a major undertaking.
+ </div><div class="para">
+ Fortunately, rpm2cpio implementations are also available in a couple of other languages, in more easy-to-install formats for other operating sytsems, including as a Bourne shell script or a Perl script. The Bourne shell syntax should work on any reasonably modern Unix system (and even a few non-Unix systems; it also works on Microsoft Windows under cygwin, for example). The script in Listing 13-1should be saved to a file named rpm2cpio.sh, marked executable, and copied to a directory in your path.
+ </div><div class="para">
+ Listing 13-1: rpm2cpio as a Bourne Shell script
+ </div><div class="para">
+ #!/bin/sh
+ </div><div class="para">
+ </div><div class="para">
+ pkg=$1
+ </div><div class="para">
+ if [ "$pkg" = "" -o ! -e "$pkg" ]; then
+ </div><div class="para">
+ echo "no package supplied" 1>&2
+ </div><div class="para">
+ exit 1
+ </div><div class="para">
+ fi
+ </div><div class="para">
+ </div><div class="para">
+ leadsize=96
+ </div><div class="para">
+ o=`expr $leadsize + 8`
+ </div><div class="para">
+ set `od -j $o -N 8 -t u1 $pkg`
+ </div><div class="para">
+ il=`expr 256 \* \( 256 \* \( 256 \* $2 + $3 \) + $4 \) + $5`
+ </div><div class="para">
+ dl=`expr 256 \* \( 256 \* \( 256 \* $6 + $7 \) + $8 \) + $9`
+ </div><div class="para">
+ # echo "sig il: $il dl: $dl"
+ </div><div class="para">
+ </div><div class="para">
+ sigsize=`expr 8 + 16 \* $il + $dl`
+ </div><div class="para">
+ o=`expr $o + $sigsize + \( 8 - \( $sigsize \% 8 \) \) \% 8 + 8`
+ </div><div class="para">
+ set `od -j $o -N 8 -t u1 $pkg`
+ </div><div class="para">
+ il=`expr 256 \* \( 256 \* \( 256 \* $2 + $3 \) + $4 \) + $5`
+ </div><div class="para">
+ dl=`expr 256 \* \( 256 \* \( 256 \* $6 + $7 \) + $8 \) + $9`
+ </div><div class="para">
+ # echo "hdr il: $il dl: $dl"
+ </div><div class="para">
+ </div><div class="para">
+ hdrsize=`expr 8 + 16 \* $il + $dl`
+ </div><div class="para">
+ o=`expr $o + $hdrsize`
+ </div><div class="para">
+ </div><div class="para">
+ dd if=$pkg ibs=$o skip=1 2>/dev/null | gunzip
+ </div><div class="para">
+ After you have marked this file as executable and placed it in your command path, you can use the script just like the C language implementation of rpm2cpio. This script also takes an RPM package file as input and produces a cpio file on standard output, and so should be used in conjunction with redirection or a pipe:
+ </div><div class="para">
+ $ rpm2cpio.sh fluxbox-0.1.8-2.src.rpm | cpio -i -d
+ </div><div class="para">
+ 656 blocks
+ </div><div class="para">
+ $
+ </div><div class="para">
+ In this case, I piped the output to cpio, directly extracting it. I could have redirected the output of rpm2cpio.sh to a file instead.
+ </div><div class="para">
+ In addition to the Bourne shell implementation of rpm2cpio, a version has been written in Perl by Roger Espel Llima. The Perl rpm2cpio implementation should work on any system that has a reasonably modern Perl interpreter. To use this version of rpm2cpio, the script in Listing 13-2 should be saved to a file named rpm2cpio.pl, marked executable, and copied to a directory in your path.
+ </div><div class="para">
+ Listing 13-2:The Perl version of rpm2cpio, rpm2cpio.pl
+ </div><div class="para">
+ #!/usr/bin/perl
+ </div><div class="para">
+ </div><div class="para">
+ # Copyright (C) 1997,1998,1999, Roger Espel Llima
+ </div><div class="para">
+ #
+ </div><div class="para">
+ # Permission is hereby granted, free of charge, to any person obtaining a copy
+ </div><div class="para">
+ # of this software and any associated documentation files (the "Software"), to
+ </div><div class="para">
+ # deal in the Software without restriction, including without limitation the
+ </div><div class="para">
+ # rights to use, copy, modify, merge, publish, distribute, sublicense,
+ </div><div class="para">
+ # and/or sell copies of the Software, and to permit persons to whom the
+ </div><div class="para">
+ # Software is furnished to do so, subject to the following conditions:
+ </div><div class="para">
+ #
+ </div><div class="para">
+ # The above copyright notice and this permission notice shall be included in
+ </div><div class="para">
+ # all copies or substantial portions of the Software.
+ </div><div class="para">
+ #
+ </div><div class="para">
+ # THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+ </div><div class="para">
+ # IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+ </div><div class="para">
+ # FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+ </div><div class="para">
+ # SOFTWARE'S COPYRIGHT HOLDER(S) BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+ </div><div class="para">
+ # LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+ </div><div class="para">
+ # OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+ </div><div class="para">
+ # THE SOFTWARE
+ </div><div class="para">
+ </div><div class="para">
+ # (whew, that's done!)
+ </div><div class="para">
+ </div><div class="para">
+ # why does the world need another rpm2cpio? because the existing one
+ </div><div class="para">
+ # won't build unless you have half a ton of things that aren't really
+ </div><div class="para">
+ # required for it, since it uses the same library used to extract RPM's.
+ </div><div class="para">
+ # in particular, it won't build on the HPsUX box i'm on.
+ </div><div class="para">
+ </div><div class="para">
+ # sw 2002-Mar-6 Don't slurp the whole file
+ </div><div class="para">
+ </div><div class="para">
+ # add a path if desired
+ </div><div class="para">
+ $gzip = "gzip";
+ </div><div class="para">
+ </div><div class="para">
+ sub printhelp {
+ </div><div class="para">
+ print <<HERE;
+ </div><div class="para">
+ rpm2cpio, perl version by orabidoo <odar\@pobox.com> +sw
+ </div><div class="para">
+ dumps the contents to stdout as a cpio archive
+ </div><div class="para">
+ </div><div class="para">
+ use: rpm2cpio [file.rpm] > file.cpio
+ </div><div class="para">
+ </div><div class="para">
+ Here's how to use cpio:
+ </div><div class="para">
+ list of contents: cpio -t -i < /file/name
+ </div><div class="para">
+ extract files: cpio -d -i < /file/name
+ </div><div class="para">
+ HERE
+ </div><div class="para">
+ </div><div class="para">
+ exit 0;
+ </div><div class="para">
+ }
+ </div><div class="para">
+ </div><div class="para">
+ if ($#ARGV == -1) {
+ </div><div class="para">
+ printhelp if -t STDIN;
+ </div><div class="para">
+ $f = "STDIN";
+ </div><div class="para">
+ } elsif ($#ARGV == 0) {
+ </div><div class="para">
+ open(F, "< $ARGV[0]") or die "Can't read file $ARGV[0]\n";
+ </div><div class="para">
+ $f = 'F';
+ </div><div class="para">
+ } else {
+ </div><div class="para">
+ printhelp;
+ </div><div class="para">
+ }
+ </div><div class="para">
+ </div><div class="para">
+ printhelp if -t STDOUT;
+ </div><div class="para">
+ </div><div class="para">
+ # gobble the file up
+ </div><div class="para">
+ ##undef $/;
+ </div><div class="para">
+ ##$|=1;
+ </div><div class="para">
+ ##$rpm = <$f>;
+ </div><div class="para">
+ ##close ($f);
+ </div><div class="para">
+ </div><div class="para">
+ read $f,$rpm,96;
+ </div><div class="para">
+ </div><div class="para">
+ ($magic, $major, $minor, $crap) = unpack("NCC C90", $rpm);
+ </div><div class="para">
+ </div><div class="para">
+ die "Not an RPM\n" if $magic != 0xedabeedb;
+ </div><div class="para">
+ die "Not a version 3 or 4 RPM\n" if $major != 3 && $major != 4;
+ </div><div class="para">
+ </div><div class="para">
+ ##$rpm = substr($rpm, 96);
+ </div><div class="para">
+ </div><div class="para">
+ while (!eof($f)) {
+ </div><div class="para">
+ $pos = tell($f);
+ </div><div class="para">
+ read $f,$rpm,16;
+ </div><div class="para">
+ $smagic = unpack("n", $rpm);
+ </div><div class="para">
+ last if $smagic eq 0x1f8b;
+ </div><div class="para">
+ # Turns out that every header except the start of the gzip one is
+ </div><div class="para">
+ # padded to an 8 bytes boundary.
+ </div><div class="para">
+ if ($pos & 0x7) {
+ </div><div class="para">
+ $pos += 7;
+ </div><div class="para">
+ $pos &= ~0x7;# Round to 8 byte boundary
+ </div><div class="para">
+ seek $f, $pos, 0;
+ </div><div class="para">
+ read $f,$rpm,16;
+ </div><div class="para">
+ }
+ </div><div class="para">
+ ($magic, $crap, $sections, $bytes) = unpack("N4", $rpm);
+ </div><div class="para">
+ die "Error: header not recognized\n" if $magic != 0x8eade801;
+ </div><div class="para">
+ $pos += 16;# for header
+ </div><div class="para">
+ $pos += 16 * $sections;
+ </div><div class="para">
+ $pos += $bytes;
+ </div><div class="para">
+ seek $f, $pos, 0;
+ </div><div class="para">
+ }
+ </div><div class="para">
+ </div><div class="para">
+ if (eof($f)) {
+ </div><div class="para">
+ die "bogus RPM\n";
+ </div><div class="para">
+ }
+ </div><div class="para">
+ </div><div class="para">
+ open(ZCAT, "|gzip -cd") || die "can't pipe to gzip\n";
+ </div><div class="para">
+ print STDERR "CPIO archive found!\n";
+ </div><div class="para">
+ </div><div class="para">
+ print ZCAT $rpm;
+ </div><div class="para">
+ </div><div class="para">
+ while (read($f, ($_=''), 16384) > 0) {
+ </div><div class="para">
+ print ZCAT;
+ </div><div class="para">
+ }
+ </div><div class="para">
+ </div><div class="para">
+ close ZCAT;
+ </div><div class="para">
+ After set up, rpm2cpio.pl works much like the C and Bourne shell versions, so the following command can be used to generate a cpio archive from an RPM package file:
+ </div><div class="para">
+ $ rpm2cpio.pl fluxbox-0.1.8-2.src.rpm | cpio -i -d
+ </div><div class="para">
+ CPIO archive found!
+ </div><div class="para">
+ 656 blocks
+ </div><div class="para">
+ $
+ </div><div class="para">
+ </div><div class="para">
+ Depending upon the system you are on, one or more of these three rpm2cpio programs should work. All three are useful any time you want to extract a file or files from an RPM package file but do not actually need to install the RPM.
+ </div></div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id854931" class="title">Summary</h1></div></div></div><div class="para">
+ Creating RPM spec files and maintaining those files can be a difficult chore. A number of tools and add-ons for text editors have sprung up to help make this less of a chore.
+ </div><div class="para">
+ Users of the two most common Linux text editors, vi and emacs, can use add-ons that understand the RPM spec file syntax. These add-ons help reduce errors and, though the use of macros, can speed development of spec files by automating some of the tasks.
+ </div><div class="para">
+ The RUST tool provides a graphical interface for creating spec files that can simplify a lot of the work normally required.
+ </div><div class="para">
+ Once you’ve created an RPM package, you can use the rpmlint command to flag missing, incomplete, or incorrect elements in your RPMs.
+ </div><div class="para">
+ Another tool, called rpm2cpio in its various incarnations, allows you to extract files from an RPM package by taking advantage of the fact that RPM files use the cpio format internally. The rpm2cpio tools can output RPM data into the cpio format directly; you can then pipe the output to the cpio command to extract.
+ </div><div class="para">
+ After all this help in making RPMs and spec files, the next chapter covers a set of best-practice guidelines to help avoid problems when making your RPMs.
+ </div></div></div><div xml:lang="ro" class="chapter" id="ch-packaging-guidelines" lang="ro"><div class="titlepage"><div><div><h2 class="title">Cap. 13. Packaging Guidelines</h2></div></div></div><div class="toc"><dl><dt><span class="sect1"><a href="#id739793">13.1. Avoiding Common Problems</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id803805">13.1.1. Scan the mailing lists</a></span></dt><dt><span class="sect2"><a href="#id584631">13.1.2. Use rpmbuild</a></span></dt><dt><span class="sect2"><a href="#id661855">13.1.3. Don’t try to defeat the system</a></span></dt><dt><span class="sect2"><a href="#id657967">13.1.4. Turn off automatic dependency generation</a></span></dt><dt><span class="sect2"><a href="#id668195">13.1.5. Don't list directories in %files</a></span></dt><dt><span class="sect2"><a href="#id795087">13.1.6. Handling circular dependencies</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id716645">13.2. Following Good Practices</a></span></d
t><dd><dl><dt><span class="sect2"><a href="#id615282">13.2.1. Preparation</a></span></dt><dt><span class="sect2"><a href="#id669869">13.2.2. Building</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id570966">13.3. Summary</a></span></dt></dl></div><div class="para">
+ This chapter covers:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Avoiding common mistakes
+ </div></li><li class="listitem"><div class="para">
+ Following good practices
+ </div></li></ul></div><div class="para">
+ RPM is a complex system that helps manage thousands of packages for a complex operating system. Furthermore, RPM is very, very flexible. This flexibility makes it important that you follow the rules to create packages the proper way. Otherwise, you’ll face a host of problems with your RPMs. Following some best practices guidelines will help you avoid future problems as you release RPM updates.
+ </div><div class="para">
+ This chapter covers ways to avoid common problems as well as best-practice guidelines for creating your own RPMs.
+ </div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id739793" class="title">Avoiding Common Problems</h1></div></div></div><div class="para">
+ Developers creating RPMs seem to hit many of the same roadblocks. This section covers some of the most common problems faced by RPM users and package builders.
+ </div><div class="para">
+ Warning
+ </div><div class="para">
+ Never, never, never build RPMs logged in as the root user. See the section on Building for details.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id803805" class="title">Scan the mailing lists</h1></div></div></div><div class="para">
+ Many people have tried to solve a lot of serious problems that arise when using RPM, so if you are facing difficulties, chances are someone else has tackled those issues before. The RPM mailing list provides a technical forum for discussing RPM issues and problems. In many, if not most, cases, you can find answers to problems by scanning the mailing list archives.
+ </div><div class="para">
+ You can also sign up for the mailing list so that you can send in requests and see the responses.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ For details on viewing the RPM mailing list archives and signing up for the list, see www.rpm.org/mailing_list/. See <a href="http://groups.yahoo.com/group/rpm-list/messages">http://groups.yahoo.com/group/rpm-list/messages</a> for an archive of the list.
+ </div><div class="para">
+ If you are working with RPMs and pushing the envelope for other operating systems or complicated packages, this list is definitely worth a look.
+ </div><div class="para">
+ Before sending any messages, though, be sure to look through the message archives to see if the message has already been answered. You will save time waiting for a response if you can get an archived response right away.
+ </div><div class="para">
+ You should also ask any questions in a way that will generate the most helpful responses. This includes:
+ </div><div class="para">
+ Do your homework first. Check to see if your question has already been answered by looking at the mailing list or newsgroup archives. In the end, this saves you the most time, as you don’t have to wait for answers.
+ </div><div class="para">
+ Describe the problem and the symptoms as clearly as possible. After all, this is what you want help with.
+ </div><div class="para">
+ Use clear subject headers. This is the first part of your message that people will read. If you are not clear, the key people who could answer your questions may never even read your message. And, if they don’t read the message, you will never get an answer.
+ </div><div class="para">
+ Send your message in plain text, not HTML. Do not include a separate HTML copy of your message. This just makes it harder to read, especially for people who read collected digests of mailing lists.
+ </div><div class="para">
+ Make it easy for people to reply to you. Include your email address in your message. You might want to include a line that states something like “Please send your reply to me at†and then provide your email address.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ These tips on asking questions come from the Internet document on How to Ask Questions the Smart Way by Eric Steven Raymond and Rick Moen, available at multiple sites, including www.owlriver.com/tips/smart.
+ </div><div class="para">
+ In addition to the RPM mailing list, there is also a Usenet newsgroup, named linux.redhat.rpm. You can read this newsgroup with any newsreading program.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ Newsgroups are sometimes called discussion groups.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id584631" class="title">Use rpmbuild</h1></div></div></div><div class="para">
+ In older versions of RPM, you called the rpm –ba command to build RPMs. With RPM 4.1, you must use the rpmbuild command. If you have the rpmbuild command available, even if you are running an older version of RPM, run rpmbuild instead of rpm to build your RPMs.
+ </div><div class="para">
+ You’d be surprised at how such a simple item is one of the most-asked questions on the RPM mailing list. That’s because the rpm –ba command, and the other –b options, no longer work in RPM 4.1. These options are supported by the rpmbuild command.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id661855" class="title">Don’t try to defeat the system</h1></div></div></div><div class="para">
+ If you are finding your spec files getting more and more complex, and that you are trying to disable RPM features, chances are you are trying to defeat the system. This is not a good idea.
+ </div><div class="para">
+ The RPM system works in a certain way. You may not always agree with the way it works, but if you try to make it work in contrary ways, in most cases you’ll end up fighting RPM to no avail.
+ </div><div class="para">
+ There are certain rules, and more importantly certain conventions that RPMs should follow. The previous chapters in this section on building RPMs have outlined those conventions. Follow them. When you go against these conventions, you are really trying to defeat how the RPM system works.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id657967" class="title">Turn off automatic dependency generation</h1></div></div></div><div class="para">
+ When you build an RPM, the rpmbuild command will automatically generate dependencies on Linux shared libraries and other system commands. You can turn this off if you need to, using a number of means.
+ </div><div class="para">
+ You can disable the automatic generation of dependencies by placing the following directive in your spec file:
+ </div><div class="para">
+ Autoreq: 0
+ </div><div class="para">
+ A better approach, though, is to override the %{__find_requires} and %{__find_provides} macros, or just one of these as needed. You can null out either of these macros by adding commands like the following to your spec file:
+ </div><div class="para">
+ %define __find_requires %{nil}
+ </div><div class="para">
+ This approach is better because it allows you to override only the requires checks. In addition, you can get more specific and simply change how the automatic dependency checks are performed. For example, you can also change the definitions of these macros to perform normal dependency generation except for any problematic files or packages. These two macros resolve to shell scripts that perform the automated dependency checks, as you can see with the rpm --eval command:
+ </div><div class="para">
+ $ rpm --eval "%__find_provides"
+ </div><div class="para">
+ /usr/lib/rpm/find-provides
+ </div><div class="para">
+ rpm --eval "%__find_requires"
+ </div><div class="para">
+ /usr/lib/rpm/find-requires
+ </div><div class="para">
+ You can override these scripts to filter out any dependencies that cause problems for your packages.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id668195" class="title">Don't list directories in %files</h1></div></div></div><div class="para">
+ Unless you really mean it, don’t list directories in your %files section in your spec files. That is because the rpmbuild program will automatically add all files in that directory to your RPM. If this is a system directory, such as /usr/bin, your RPM has now claimed ownership for all the files, regardless of the source package.
+ </div><div class="para">
+ To avoid all files in the directory becoming part of the package, list the files explicitly, perhaps generating the list of files as the program builds.
+ </div><div class="para">
+ If you do need a directory installed as part of your package, use the %dir directive, described in <a class="xref" href="#ch-specfiles">Cap. 9, <em>Working with Spec Files</em></a> .
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id795087" class="title">Handling circular dependencies</h1></div></div></div><div class="para">
+ If two packages each depend on the other, you don’t want each package’s spec file to list the other in a Requires section. If this occurs, the packages won’t install without one of the force options, since each package will require the other to be installed first.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ <a class="xref" href="#ch-using-rpm">Cap. 3, <em>Using RPM</em></a> covers how to install or upgrade packages while ignoring dependency checks. In general, you do not want to ignore these checks.
+ </div><div class="para">
+ You can work around this issue by using the PreReq directive instead of Requires. For example, if package A depends on B and package B depends on A, you can place the following in the package B spec file:
+ </div><div class="para">
+ PreReq: A
+ </div><div class="para">
+ In addition, you can install both packages at the same time to avoid some of the problems with circular dependencies. Simply include both packages on the rpm –Uvh command line.
+ </div></div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id716645" class="title">Following Good Practices</h1></div></div></div><div class="para">
+ Working through problems is one thing. It’s best, however, to set up an environment to help avoid problems all together. The following sections cover what are considered the best practices for creating RPMs.
+ </div><div class="para">
+ Before you make an RPM, you should plan out what you intend to build and how it will be structured. As you build the RPM, you want to watch out for things that can go wrong, and work from a known clean environment.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id615282" class="title">Preparation</h1></div></div></div><div class="para">
+ Before you start to make an RPM, you need to follow a few steps to ensure you have everything ready.
+ </div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id615293" class="title">Create a Source RPM</h1></div></div></div><div class="para">
+ Having a source RPM allows you to transfer all the sources for a package from one system to another, along with all the instructions coded in the spec file for actually building the binary package. This is very handy for keeping track of software, and it is also very important since you can regenerate the binary RPM at any time from the source RPM. In other words, make the generation of RPMs follow the RPM conventions and fit this into your normal software build process.
+ </div><div class="para">
+ This means that for each RPM you want to build, you really need two: a source and a binary RPM. This isn’t that hard to do, since you can easily make a source RPM into a binary RPM with the rpmbuild command.
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id509215" class="title">Start with Pristine Sources</h1></div></div></div><div class="para">
+ In addition to planning on making a source RPM, you should also start with pristine, unmodified sources for the application you plan to package as an RPM. Starting with pristine sources means you can reproduce the entire process and recreate the RPM from scratch if necessary. (Quality control and configuration management people really appreciate this.)
+ </div><div class="para">
+ The pristine sources should be exactly the sources you got when you downloaded the application, or acquired it in house. This doesn’t mean that you won’t have to modify the sources eventually. For that, you create patches. The key is just to start the process with unmodified sources.
+ </div><div class="para">
+ Some RPMs have nearly 100 patches that the rpmbuild command applies when building the RPM. That is a lot of patches, too many for most applications. Even so, the process is the same. Create a patch or patches for all the changes you need to make. You can easily specify patches in the spec file.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ <a class="xref" href="#ch-specfiles">Cap. 9, <em>Working with Spec Files</em></a> covers the spec file.
+ </div><div class="para">
+ Keeping your patches separate from the original sources makes it easier to reproduce the RPM from scratch, and makes it easier to integrate a new version of the base software, since your code, in the form of patches, is separated from the base software code.
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id497224" class="title">Decide What Goes In Each Package</h1></div></div></div><div class="para">
+ You don’t have to stuff all your software into one RPM. Instead, you can often simplify your RPM by dividing it into two or three separate (but likely dependent) RPMs.
+ </div><div class="para">
+ For example, the RPM system itself has one RPM for the basic system, rpm, one for developers of the RPM system, rpm-devel, and one for those building RPMs, rpm-build. Yet another RPM provides the Python programming API, rpm-python.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ <a class="xref" href="#ch-rpm-programming-python">Cap. 16, <em>Programming RPM with Python</em></a> covers Python programming.
+ </div><div class="para">
+ This last division is important. The Python RPM draws in as a dependency the Python system itself. Adding this into, say, the core RPM package would needlessly complicate the dependencies for that package.
+ </div><div class="para">
+ When dividing your software into RPMs, keep two main issues in mind:
+ </div><div class="para">
+ *You want to divide the software into RPMs that fit the model for users of the system.
+ </div><div class="para">
+ *You want to divide the software into RPMs such that the separate RPMs are simpler to create and manage.
+ </div><div class="para">
+ The RPM system follows these guidelines, especially the first. Few users will extend the RPM system itself, which allows RPM team to shed this functionality from the core RPM and contain it in rpm-devel. Those who build RPMs fit into a different category than those who use RPMs since just about everybody needs to use RPMs to install packages, but few users actually build RPMs. Again, the separation works from a user’s perspective.
+ </div><div class="para">
+ You also want your package divisions to make each package easier to specify. You can break particularly tough dependencies into smaller units and simplify things. If the package division doesn’t simplify things, then it may not be a good idea.
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id739088" class="title">Create a Test RPM Database</h1></div></div></div><div class="para">
+ You don’t always have to work with the system RPM database. In fact, while developing RPMs, you probably don’t want to change the system database.
+ </div><div class="para">
+ If you have a test RPM database, you can install your RPMs into this test database. To do so, use the --justdb, --dbpath, --prefix, and --badreloc options. These options allow you to install an RPM into just the database, using a different database, with a different root file location (into a test directory, for example) and handle all files that were not marked for relocation, respectively.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ The --test option when installing also allows you to just test the install, not actually perform it.
+ </div><div class="para">
+ Combined, all these options mean you can use an RPM database just set up for testing and that problems won’t impact your working Linux systems. To make this work, though, you need a test RPM database.
+ </div><div class="para">
+ To be rigorous, you should create the test RPM database from scratch from a known set of packages. This will allow you to exactly verify the behavior of your RPM under different system configurations. This is the best choice since you should install the packages under a known, and non-root, directory hierarchy to avoid having file problems with the working system.
+ </div><div class="para">
+ If you want to cheat, you can copy your real RPM database to another directory and use that. Note that in this case, the file paths in the database will point to the real file locations on disk.
+ </div><div class="para">
+ Regardless of how you create a test database, recreate the database each time you run a test, so that you are sure of a known starting state. Usually this is as simple as copying a master test RPM database into a directory you use for running tests.
+ </div></div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id669869" class="title">Building</h1></div></div></div><div class="para">
+ Building RPMs isn’t as easy as it should be. You’ll often need to try again and again to get the rpmbuild command to create a working RPM. This section covers best practices to follow when performing the actual build of the RPM.
+ </div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id674726" class="title">Use Tools</h1></div></div></div><div class="para">
+ Using tools can help speed up the RPM-making process, as well as give you a head start in learning how RPMs work. RPM-building tools such as the Red Hat plugin for the Eclipse Integrated Development Environment have proven really helpful.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ <a class="xref" href="#ch-extra-packaging-tools">Cap. 12, <em>Supplemental Packaging Software</em></a> covers RPM-building tools. <a class="xref" href="#ch-development-tools">Cap. 26, <em>Linux Text Editors and Development Tools</em></a> covers the Eclipse Integrated Development Environment.
+ </div><div class="para">
+ Even though so-called real Linux hackers can make a working virtual memory system with just the cat command, don’t scoff at tools. Your time is too valuable.
+ </div><div class="para">
+ Another useful tool is the gendiff program that comes with the RPM release. The gendiff program makes it easier to create patches by avoiding the need to keep a separate directory of the original sources, The gendiff program also works on all changed files within a directory, making a patch for everything you modified.
+ </div><div class="para">
+ To work with gendiff, you need to first save a backup copy of each file you intend to edit prior to editing. Use a consistent file-name extension for the saved copies of the files, such as .orig, short for original. After you edit some files, run the gendiff command as follows:
+ </div><div class="para">
+ $ gendiff directory_name .saved_extension > patch_name.patch
+ </div><div class="para">
+ For example, if you saved the original files to a .orig extension, you can create a patch in a directory named src (short for sources) with a command like the following:
+ </div><div class="para">
+ $gendiff src .orig > mypatch.patch
+ </div><div class="para">
+ The patch file mypatch.patch will contain all the differences detected for all files in the given directory.
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id848224" class="title">Never Build RPMs as Root</h1></div></div></div><div class="para">
+ Never, never, never build RPMs logged in as the root user. Always build your RPMS while logged in as a normal user. This is hard to remember since you must be logged in as root to install an RPM. And you’ll want to test each RPM you create to see if it can install cleanly.
+ </div><div class="para">
+ Even so, never build RPMs logged in as the root user. The RPM spec file has a number of scripts and commands. An error in any of these could cause damage to your system. This includes modifying files, removing files, or copying new contents on top of system files. The root user has permission to perform all these operations.
+ </div><div class="para">
+ To avoid all this, build your RPMs while logged in as a normal user. Any problematic scripts should generate errors.
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id848250" class="title">Create a Digital Signature</h1></div></div></div><div class="para">
+ RPM 4.1 and later revisions place more importance on signing your packages. The rpm command will, by default, verify signatures on each package it reads.
+ </div><div class="para">
+ Therefore, you should create a digital signature for your packages, if only to meet user expectations. In addition, you should place a copy of your digital signature on your organization’s Web site and public key servers. Having multiple copies in multiple locations helps prevent malicious users from impersonating your keys.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ <a class="xref" href="#ch-rpmbuild">Cap. 11, <em>Controlling the Build with <code class="command">rpmbuild</code></em></a> covers signing packages.
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id755102" class="title">Copy Smartly</h1></div></div></div><div class="para">
+ Your Linux distribution probably includes more than one CD-ROM chock full of RPMs. Each of these RPMs has a spec file. You can examine these spec files and see how others choose to build their RPMs. Rather than starting from scratch, you can copy declarations from these spec files into your spec file.
+ </div><div class="para">
+ Not all these packages were made smartly. Some spec files, as you will see, are a large mess. Obviously, don’t copy these. Look for clean spec files with clear directives.
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id570054" class="title">Set Up the BuildRoot</h1></div></div></div><div class="para">
+ A BuildRoot directive sets the location where your code will be built. The convention is for you to define a subdirectory beneath the _tmppath directory. For example:
+ </div><div class="para">
+ BuildRoot: %{_tmppath}/%{name}-buildroot
+ </div><div class="para">
+ Once set, rpmbuild defines the RPM_BUILD_ROOT environment variable to the value specified for the BuildRoot.
+ </div><div class="para">
+ With the rpmbuild command, you can use the --buildroot option to specify a directory to use to override the BuildRoot directive in the spec file.
+ </div><div class="para">
+ Using a BuildRoot set to a directory that normal users have write access to allows you to build the package logged in as a normal user. It also helps separate the contents of your package from those of other RPMs.
+ </div><div class="para">
+ Always define a BuildRoot.
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id651165" class="title">Add changelog entries for each new version</h1></div></div></div><div class="para">
+ Each time you create a new version in RPM format, you should add an entry to the change log. This allows administrators to get a better idea about what changed from the previous version.
+ </div><div class="para">
+ The change log can help people decide whether or not to upgrade a package. A log entry about a security fix, for example, provides useful information to users.
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id795439" class="title">Define the Group For Your Package</h1></div></div></div><div class="para">
+ Packages are categorized into groups. These group names, while not always the best, appear in the graphical tools such as the Red Hat package manager. If your application is a Linux shell program, then users will expect to find it in the System Environment/Shells group and not the Development/Languages or System Environment/Daemons groups. This is a rather small detail, but it helps users find your package in the huge array of Linux RPMs.
+ </div><div class="para">
+ The official list of RPM groups is located in /usr/share/doc/rpm-4.1/GROUPS for RPM 4.1, and similarly-named directories for other RPM versions.
+ </div></div></div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id570966" class="title">Summary</h1></div></div></div><div class="para">
+ This chapter covers guidelines for avoiding problems when creating RPMs and following best practices to avoid future problems as well.
+ </div><div class="para">
+ When trying to avoid common problems, your best starting point is the RPM mailing list and newsgroup.
+ </div><div class="para">
+ For best practices, you should start at the very beginning when you are planning what to build into an RPM. Always start with pristine sources and then patch as needed. Your RPM should include the pristine sources and any necessary patches. You should always create a source RPM, so that you can reproduce your RPM anywhere.
+ </div><div class="para">
+ When building RPMs, copy good examples of spec files, as this will get you going far more quickly than any other technique. Use tools to help automate parts of your RPM-building process.
+ </div><div class="para">
+ Never build RPMs when logged in as the root user.
+ </div><div class="para">
+ This chapter ends the section on building RPMs. The next section covers programming to the RPM APIs.
+ </div></div></div><div xml:lang="ro" class="chapter" id="ch-scripting" lang="ro"><div class="titlepage"><div><div><h2 class="title">Cap. 14. Automating RPM with Scripts</h2></div></div></div><div class="toc"><dl><dt><span class="sect1"><a href="#id1415954">14.1. Scripting</a></span></dt><dt><span class="sect1"><a href="#id754838">14.2. Distinguishing Scripting Languages from Programming Languages</a></span></dt><dt><span class="sect1"><a href="#id652088">14.3. Deciding When to Program and When to Script</a></span></dt><dt><span class="sect1"><a href="#id669084">14.4. Shell Scripting Basics</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id746568">14.4.1. Writing a script</a></span></dt><dt><span class="sect2"><a href="#id675446">14.4.2. Running a script</a></span></dt><dt><span class="sect2"><a href="#id712323">14.4.3. Problems running scripts</a></span></dt><dt><span class="sect2"><a href="#id820565">14.4.4. Turning a script into a command</a></span></dt><dt><span
class="sect2"><a href="#id682469">14.4.5. Passing command-line options to your script</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id818713">14.5. Examining RPM Files</a></span></dt><dt><span class="sect1"><a href="#id553708">14.6. Querying the RPM Database</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id800912">14.6.1. Querying for all packages installed at the same time</a></span></dt><dt><span class="sect2"><a href="#id979252">14.6.2. Reading HTML documentation for a package</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id561272">14.7. Where to Go From Here</a></span></dt><dt><span class="sect1"><a href="#id628097">14.8. Summary</a></span></dt></dl></div><div class="para">
+ This chapter covers:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Deciding when to program and when to script
+ </div></li><li class="listitem"><div class="para">
+ Examining RPM files with scripts
+ </div></li><li class="listitem"><div class="para">
+ Querying the RPM database with scripts
+ </div></li></ul></div><div class="para">
+ The rpm command provides a very high-level view of package management. Most of the operations you need to perform require only a single invocation. Some of the command-line options to the rpm command tend to get very complex, however, especially for detailed queries. That’s where scripting can help.
+ </div><div class="para">
+ This chapter covers scripting, specifically shell scripting, with the rpm command, especially for newcomers to Linux scripting
+ </div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id1415954" class="title">Scripting</h1></div></div></div><div class="para">
+ Scripting allows you to quickly write new commands in a language, called a scripting language, that can help automate your work. Used heavily by system administrators and lightly by software developers, scripts can help remove some of the tedium from your day-to-day tasks. Scripts can also hold the complex query formats used with the rpm command so you don’t have to remember them.
+ </div><div class="para">
+ Scripts start out as text files. These text files hold commands in the scripting language. Most of these script file commands run commands installed on your system, such as rpm. To run a script, invoke a command, called an interpreter, that reads in the script file and executes the commands inside the script.
+ </div><div class="para">
+ Programming is usually considered different from scripting, even though there are many similarities. Programs start out as text files. These text files hold commands in the programming language and sometimes, not often, calls to commands installed on your system. Programs generally involve more work than scripts and are generally larger, containing more commands.
+ </div><div class="para">
+ Furthermore, most programs need to be compiled. A separate command parses the program text files and generates some form of machine code. Multiple pieces of a program may be linked together to form a command you can call from your shell prompt.
+ </div><div class="para">
+ Some programming languages, such as Java or C#, are compiled to a generic bytecode format. A compiled Java program, for example, is the same no matter what the architecture. To run such a program, you need a runtime engine such as the java command provides. (Runtime engine is a fancy term for interpreter.)
+ </div><div class="para">
+ Such differences between scripting and programming sometimes get in the way of performing real work. For example, I once worked with a group of people who were convinced that they were not programmers. They felt that programming was an art that was far beyond them. Yet, they wrote hundreds of kilobytes of scripts to create a sophisticated graphical interface for a Computer-Aided Design system. In my mind, they were programming (and doing quite well at it). In their minds, though, there was a clear distinction between scripting at mdwhat they could do at mdand programming, which was beyond them, they thought.
+ </div><div class="para">
+ Don’t get caught up in this. Use the right tool for the job.
+ </div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id754838" class="title">Distinguishing Scripting Languages from Programming Languages</h1></div></div></div><div class="para">
+ Experts differ regarding what defines a scripting language and what defines a programming language. It’s clear that languages such as Python blur the old distinction between programming and scripting.
+ </div><div class="para">
+ Originally, scripting was writing small files of commands that invoked other system commands. For example, you could write a script that wraps the Linux file command. Scripts were executed by scripting-language interpreters that parsed each command one at a time and then executed the command.
+ </div><div class="para">
+ Modern scripting languages, such as Tcl, are parsed at runtime and compiled into an internal bytecode format. Once compiled, there is no real difference from a language associated with programming such as Java.
+ </div><div class="para">
+ With a scripting language
+ </div><div class="para">
+ *You generally don’t have to compile the script in advance. The scripting language interpreter may compile the program, often to an internal byte code, but you don’t have to invoke a compiler as a separate step.
+ </div><div class="para">
+ *The facilities of the language generally provide a higher level and more abstract level of interaction with the system than with programming languages. For example, writing socket-based networking code in Tcl requires a lot less code than writing the same code in a programming language such as C. Tcl provides a more abstract view of networking; therefore, your code is a lot simpler.
+ </div><div class="para">
+ *The commands in the scripting language are mostly the commands available to you on the command line. Scripting languages introduce their own commands, too.
+ </div><div class="para">
+ *The language is generally identified as a scripting language. This is more consensus than anything else. Forth is considered an interpreted programming language, while Perl is considered a scripting language.
+ </div><div class="para">
+ Table 15-1 lists some of the more common scripting and programming languages. Note that these are the generally-accepted categories for these languages, not hard and fast rules. This should not stop you, for example, from writing programs in Perl or Python. The distinctions between programming and scripting have blurred in recent years.
+ </div><div class="para">
+ Table 15-1 Common Scripting Languages and Common Programming Languages
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Scripting Languages
+ </div>
+
+ </td><td>
+ <div class="para">
+ Programming Languages
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Bash (Bourne Again shell) Csh (C shell) JavaScript Ksh (Korn shell) Lua MS-DOS batch files Perl Python Ruby Sh (Bourne shell) Tcl
+ </div>
+
+ </td><td>
+ <div class="para">
+ Assembler BASIC C C++ C# FORTRAN Forth Java LISP Modula-2, Modula-3 Oberon Pascal
+ </div>
+
+ </td></tr></tbody></table></div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id652088" class="title">Deciding When to Program and When to Script</h1></div></div></div><div class="para">
+ Just as the distinction between programming and scripting languages has blurred in the last few years, so have the guidelines for when you should program and when you should script. The simplest rule remains, though: Use whatever techniques make you productive. In the end, no one really cares if you call it a program or a script.
+ </div><div class="para">
+ Even so, these guidelines may help:
+ </div><div class="para">
+ *If you have to perform a lot of operations on a lot of RPMs, a program will likely perform much faster than a script that calls the rpm command over and over.
+ </div><div class="para">
+ *If the task is relatively simple, scripting generally works best.
+ </div><div class="para">
+ *If you are more experienced with a particular language, use it.
+ </div><div class="para">
+ *If you need to perform complex operations, perhaps involving transactions, a program is probably the right way to go.
+ </div><div class="para">
+ *In many cases, programming languages work better for creating graphical user interfaces, although Python and Perl offer graphical user interface toolkits, such as Perl/Tk or PyQt.
+ </div><div class="para">
+ There isn’t one right way to do it. Pick what works best for you.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ This chapter covers shell scripting. <a class="xref" href="#ch-programming-c">Cap. 15, <em>Programming RPM with C</em></a> covers C programming. <a class="xref" href="#ch-rpm-programming-python">Cap. 16, <em>Programming RPM with Python</em></a> covers Python scripting and programming, and <a class="xref" href="#ch-programming-perl">Cap. 17, <em>Programming RPM with Perl</em></a> covers Perl scripting.
+ </div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id669084" class="title">Shell Scripting Basics</h1></div></div></div><div class="para">
+ For newcomers to scripting, don’t worry. A script, in this case a shell script, is merely a text file with commands mostly the same as the commands you can type at the keyboard. I’ll point out the differences.
+ </div><div class="para">
+ The following sections quickly introduce scripting for those new to this venture.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id746568" class="title">Writing a script</h1></div></div></div><div class="para">
+ For your first venture, enter the following script into a text file:
+ </div><div class="para">
+ rpm -qa | grep rpm
+ </div><div class="para">
+ This script has a two-part command. The rpm –qa part queries all RPM packages, as covered in <a class="xref" href="#ch-using-rpm">Cap. 3, <em>Using RPM</em></a> . The grep rpm part finds only packages with rpm in their names. This is a very simple script, but it can serve to show how to work with scripts.
+ </div><div class="para">
+ Save this file under the name listrpmpkgs, since this script lists RPM packages.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ If you’re new to Linux, you’ll notice there’s no program named Notepad.exe. There are, though, a plethora of Linux text editors to choose from. See <a class="xref" href="#ch-development-tools">Cap. 26, <em>Linux Text Editors and Development Tools</em></a> for a listing of Linux text-editing tools.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id675446" class="title">Running a script</h1></div></div></div><div class="para">
+ Once you’ve entered a script, you can run it with the sh command, as shown following, passing the name of your script to the sh command:
+ </div><div class="para">
+ $ sh listrpmpkgs
+ </div><div class="para">
+ librpm404-devel-4.0.4-8x.27
+ </div><div class="para">
+ librpm404-4.0.4-8x.27
+ </div><div class="para">
+ rpm404-python-4.0.4-8x.27
+ </div><div class="para">
+ rpm-4.1-1.06
+ </div><div class="para">
+ rpm-devel-4.1-1.06
+ </div><div class="para">
+ gnorpm-0.9-1
+ </div><div class="para">
+ rpm-python-4.1-1.06
+ </div><div class="para">
+ redhat-rpm-config-8.0-1
+ </div><div class="para">
+ rpm-build-4.1-1.06
+ </div><div class="para">
+ rpmrebuild-1.0-0
+ </div><div class="para">
+ Type the command you have placed in your script at the command line. There should be no difference in the output. For example:
+ </div><div class="para">
+ $ rpm -qa | grep rpm
+ </div><div class="para">
+ librpm404-devel-4.0.4-8x.27
+ </div><div class="para">
+ librpm404-4.0.4-8x.27
+ </div><div class="para">
+ rpm404-python-4.0.4-8x.27
+ </div><div class="para">
+ rpm-4.1-1.06
+ </div><div class="para">
+ rpm-devel-4.1-1.06
+ </div><div class="para">
+ gnorpm-0.9-1
+ </div><div class="para">
+ rpm-python-4.1-1.06
+ </div><div class="para">
+ redhat-rpm-config-8.0-1
+ </div><div class="para">
+ rpm-build-4.1-1.06
+ </div><div class="para">
+ rpmrebuild-1.0-0
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id712323" class="title">Problems running scripts</h1></div></div></div><div class="para">
+ The previous script example required the sh program, a Linux shell, to run the script. You also had to have the script file, such as listrpmpkgs, available. So, if you have stored the file in /home2/bin, to run the script, use the following command:
+ </div><div class="para">
+ $ sh /home2/bin/listrpmpkgs
+ </div><div class="para">
+ That’s not very convenient. Furthermore, you always have to remember where you stored the script file listrpmpkgs. To make this command work better, you can turn your script into a command.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id820565" class="title">Turning a script into a command</h1></div></div></div><div class="para">
+ To turn a script into a command, do three simple things:
+ </div><div class="para">
+ 1.Add a special magic comment to the start of the file so Linux recognizes your text file as a command script.
+ </div><div class="para">
+ 2.Change the permissions on the file so that it is marked as executable.
+ </div><div class="para">
+ 3.Copy the file to a directory located in your command path.
+ </div><div class="para">
+ Shell scripts use a # to indicate a comment, text intended for human readers that can help explain the purpose of the script. By convention, Linux shells use a #! comment in the first line of a script file as a special marker that indicates the file is a shell script. The text that comes after the #! holds the name of the command that should be used to run the script. In almost all cases, that command should be /bin/sh for a shell script.
+ </div><div class="para">
+ So edit the listrpmpkgs script again, and add the magic comment so that the file reads as follows:
+ </div><div class="para">
+ #!/bin/sh
+ </div><div class="para">
+ rpm -qa | grep rpm
+ </div><div class="para">
+ Make sure the #! comment starts at the beginning of the first line.
+ </div><div class="para">
+ Next, change the permissions on the script to mark it as an executable program. Use the chmod command to do this. The chmod command changes the file permissions. To see the permissions, run the ls –l command before changing the permissions:
+ </div><div class="para">
+ $ ls -l listrpmpkgs
+ </div><div class="para">
+ -rw-rw-r-- 1 ericfj ericfj 31 Nov 7 20:02 listrpmpkgs
+ </div><div class="para">
+ The first set of characters, the -rw-rw-r--, indicate the permissions in three batches: permissions for the file owner, the owner’s group of users, and world (everyone else). The rw means read and write, and the r alone means read only for everyone not the owner and not in the owner’s group.
+ </div><div class="para">
+ To add the permission to execute the file for the file owner only, use the following command:
+ </div><div class="para">
+ $ chmod u+x listrpmpkgs
+ </div><div class="para">
+ In this command, the u stands for the user who owns the file (for historical reasons, an o stands for others, not owner). The +x means add the x permission, short for execute permission.
+ </div><div class="para">
+ After running this command, you can see the revised permissions.
+ </div><div class="para">
+ $ ls -l listrpmpkgs
+ </div><div class="para">
+ -rwxrw-r-- 1 ericfj ericfj 31 Nov 7 20:02 listrpmpkgs
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ Use the man chmod command to see more information on this command.
+ </div><div class="para">
+ You now have a command you can run locally. For example:
+ </div><div class="para">
+ $ ./listrpmpkgs
+ </div><div class="para">
+ librpm404-devel-4.0.4-8x.27
+ </div><div class="para">
+ librpm404-4.0.4-8x.27
+ </div><div class="para">
+ rpm404-python-4.0.4-8x.27
+ </div><div class="para">
+ rpm-4.1-1.06
+ </div><div class="para">
+ rpm-devel-4.1-1.06
+ </div><div class="para">
+ gnorpm-0.9-1
+ </div><div class="para">
+ rpm-python-4.1-1.06
+ </div><div class="para">
+ redhat-rpm-config-8.0-1
+ </div><div class="para">
+ rpm-build-4.1-1.06
+ </div><div class="para">
+ rpmrebuild-1.0-0
+ </div><div class="para">
+ The next step is to copy the file to a directory in your system command path. To see which directories are in your path, run the following command:
+ </div><div class="para">
+ $ echo $PATH
+ </div><div class="para">
+ /usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:/home/ericfj/bin:/usr/java/j2sdk1.4.0_01/bin
+ </div><div class="para">
+ Pick one of these directories. The /usr/local/bin directory is a common place to share locally created commands. If this is a personal command for your own use only, a directory under your home directory will be better. In this example, the /home/ericfj/bin is one such directory.
+ </div><div class="para">
+ Copy the script file to a directory in your command path, and you are ready to go.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ If you use the C shell, csh, or the T C shell, tcsh, you need to run the rehash command to tell the shell to look again at the set of commands available in your command path.
+ </div><div class="para">
+ Enter the following command:
+ </div><div class="para">
+ $ listrpmpkgs
+ </div><div class="para">
+ librpm404-devel-4.0.4-8x.27
+ </div><div class="para">
+ librpm404-4.0.4-8x.27
+ </div><div class="para">
+ rpm404-python-4.0.4-8x.27
+ </div><div class="para">
+ rpm-4.1-1.06
+ </div><div class="para">
+ rpm-devel-4.1-1.06
+ </div><div class="para">
+ gnorpm-0.9-1
+ </div><div class="para">
+ rpm-python-4.1-1.06
+ </div><div class="para">
+ redhat-rpm-config-8.0-1
+ </div><div class="para">
+ rpm-build-4.1-1.06
+ </div><div class="para">
+ rpmrebuild-1.0-0
+ </div><div class="para">
+ You have now extended the Linux command set with your own command.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ Windows users may be used to the convention that program file names end in .exe and scripts end in .bat or .cmd. When you run these programs or scripts, you don’t include the extension, exe, .bat, or .cmd. With Linux and UNIX, though, the full file name is important, so if you name your script rpminfo.bat, you must type rpminfo.bat each time you run the script. That’s why most Linux programs and scripts have no filename extension.
+ </div><div class="para">
+ If you want to share your script with others, you should give them the right to execute it as well. You can do that with the following command:
+ </div><div class="para">
+ $ chmod a+x listrpmpkgs
+ </div><div class="para">
+ In this case, the a stands for all users.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id682469" class="title">Passing command-line options to your script</h1></div></div></div><div class="para">
+ The listrpmpkgs script used so far isn’t very useful. It performs one command and that’s it. We cannot customize it without writing a new script.
+ </div><div class="para">
+ One way to make a script more flexible is to allow it to use command-line options. Just like the rpm command accepts a zillion options, you can make your scripts accept options.
+ </div><div class="para">
+ Shells define special variables for the command-line options passed to the shell. Table 15-2 lists these options.
+ </div><div class="para">
+ Table 15-2: Shell variables for command-line options
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Variable
+ </div>
+
+ </td><td>
+ <div class="para">
+ Holds
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ $0
+ </div>
+
+ </td><td>
+ <div class="para">
+ The name of the script itself, from the command line
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ $1
+ </div>
+
+ </td><td>
+ <div class="para">
+ The first option
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ $2
+ </div>
+
+ </td><td>
+ <div class="para">
+ The second option
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ $3
+ </div>
+
+ </td><td>
+ <div class="para">
+ The third option
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ $4
+ </div>
+
+ </td><td>
+ <div class="para">
+ The fourth option
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ $5
+ </div>
+
+ </td><td>
+ <div class="para">
+ The fifth option
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ $6
+ </div>
+
+ </td><td>
+ <div class="para">
+ The sixth option
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ $7
+ </div>
+
+ </td><td>
+ <div class="para">
+ The seventh option
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ $8
+ </div>
+
+ </td><td>
+ <div class="para">
+ The eighth option
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ $9
+ </div>
+
+ </td><td>
+ <div class="para">
+ The ninth option
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ $*
+ </div>
+
+ </td><td>
+ <div class="para">
+ All command-line options
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ $#
+ </div>
+
+ </td><td>
+ <div class="para">
+ Holds the number of command-line options
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ Note
+ </div><div class="para">
+ Use $#argv in place of $# if you use the C shell to run your scripts.
+ </div><div class="para">
+ You can use these variables to allow the user to pass the text to search for, instead of always searching for rpm. With this addition, your new script, renamed rpmgrep, follows in Listing 15-1:
+ </div><div class="para">
+ Listing 15-1: rpmgrep
+ </div><div class="para">
+ #!/bin/sh
+ </div><div class="para">
+ </div><div class="para">
+ rpm -qa | grep $*
+ </div><div class="para">
+ This script now expects a command-line option that holds the text to search for. Mark this script as an executable; then you can run it as follows:
+ </div><div class="para">
+ $ ./rpmgrep python
+ </div><div class="para">
+ python-devel-2.2.1-17
+ </div><div class="para">
+ gnome-python2-gtkhtml2-1.99.11-8
+ </div><div class="para">
+ gnome-python2-canvas-1.99.11-8
+ </div><div class="para">
+ gnome-python2-1.99.11-8
+ </div><div class="para">
+ rpm404-python-4.0.4-8x.27
+ </div><div class="para">
+ orbit-python-1.99.0-4
+ </div><div class="para">
+ gnome-python2-bonobo-1.99.11-8
+ </div><div class="para">
+ gnome-python2-gconf-1.99.11-8
+ </div><div class="para">
+ libxslt-python-1.0.19-1
+ </div><div class="para">
+ libxml2-python-2.4.23-1
+ </div><div class="para">
+ python-optik-1.3-2
+ </div><div class="para">
+ python-2.2.1-17
+ </div><div class="para">
+ rpm-python-4.1-1.06
+ </div><div class="para">
+ mod_python-3.0.0-10
+ </div><div class="para">
+ python-tools-2.2.1-17
+ </div><div class="para">
+ If you want to make this command available, copy it to a directory in your command path as described in the preceding section.
+ </div></div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id818713" class="title">Examining RPM Files</h1></div></div></div><div class="para">
+ When you work with a lot of RPM files, you’ll find that you run the same commands over and over again for each new package you get. For example, you may want to see what capabilities a package requires. You can type in the rpm command each time, or write a short shell script with the necessary command-line options. Listing 15-2 shows this script.
+ </div><div class="para">
+ Listing 15-2: rpmdepend
+ </div><div class="para">
+ #!/bin/sh
+ </div><div class="para">
+ </div><div class="para">
+ rpm -qp --requires $*
+ </div><div class="para">
+ This script expects the name of an RPM package file. Run the command as follows:
+ </div><div class="para">
+ $ rpmdepend vim-common-6.1-14.i386.rpm
+ </div><div class="para">
+ rpmlib(PayloadFilesHavePrefix) <= 4.0-1
+ </div><div class="para">
+ rpmlib(CompressedFileNames) <= 3.0.4-1
+ </div><div class="para">
+ /bin/sh
+ </div><div class="para">
+ /usr/bin/awk
+ </div><div class="para">
+ libc.so.6
+ </div><div class="para">
+ libc.so.6(GLIBC_2.0)
+ </div><div class="para">
+ libc.so.6(GLIBC_2.1)
+ </div><div class="para">
+ Another common task I perform involves listing all the files in an RPM along with the descriptive information on the package. This can really help, since so many Linux packages have nondescriptive names such as dia and anaconda.
+ </div><div class="para">
+ Listing 15-3 shows the rpminfo script.
+ </div><div class="para">
+ Listing 15-3: rpminfo
+ </div><div class="para">
+ #!/bin/sh
+ </div><div class="para">
+ </div><div class="para">
+ rpm -qilp $* | less
+ </div><div class="para">
+ This script lists a potentially long set of lines, so the script pipes the output to the less command. For example:
+ </div><div class="para">
+ $ ./rpminfo perl-XML-Dumper-0.4-22.noarch.rpm
+ </div><div class="para">
+ Name : perl-XML-Dumper Relocations: /usr
+ </div><div class="para">
+ Version : 0.4 Vendor: Red Hat, Inc.
+ </div><div class="para">
+ Release : 22 Build Date: Tue 06 Aug 2002 01:53:30 PM CDT
+ </div><div class="para">
+ Install date: (not installed) Build Host: vegeta.devel.redhat.com
+ </div><div class="para">
+ Group : System Environment/Libraries Source RPM: perl-XML-Dumper-0.4-22.src.rpm
+ </div><div class="para">
+ Size : 10015 License: GPL
+ </div><div class="para">
+ Signature : DSA/SHA1, Tue 06 Aug 2002 02:11:39 PM CDT, Key ID fd372689897da07a
+ </div><div class="para">
+ Packager : Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla>
+ </div><div class="para">
+ URL : http://www.cpan.org
+ </div><div class="para">
+ Summary : Perl module for dumping Perl objects from/to XML
+ </div><div class="para">
+ Description :
+ </div><div class="para">
+ XML::Dumper dumps Perl data to XML format. XML::Dumper can also read
+ </div><div class="para">
+ XML data that was previously dumped by the module and convert it back
+ </div><div class="para">
+ to Perl. Perl objects are blessed back to their original packaging;
+ </div><div class="para">
+ if the modules are installed on the system where the perl objects are
+ </div><div class="para">
+ reconstituted from xml, they will behave as expected. Intuitively, if
+ </div><div class="para">
+ the perl objects are converted and reconstituted in the same
+ </div><div class="para">
+ environment, all should be well.
+ </div><div class="para">
+ /usr/lib/perl5/vendor_perl/5.8.0/XML/Dumper.pm
+ </div><div class="para">
+ /usr/share/man/man3/XML::Dumper.3pm.gz
+ </div><div class="para">
+ I use this script so that I know what files a package wants to install.
+ </div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id553708" class="title">Querying the RPM Database</h1></div></div></div><div class="para">
+ In addition to querying RPM files, you can script the commands you use to query the RPM database. This is most useful for the long commands with query formats, especially if you have a hard time remembering all the formats.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id800912" class="title">Querying for all packages installed at the same time</h1></div></div></div><div class="para">
+ If you want to list all the packages that were installed with the same transaction ID as a particular package, for example, you can use a script like rpmtran, in Listing 15-4.
+ </div><div class="para">
+ Listing 15-4: rpmtran
+ </div><div class="para">
+ #!/bin/sh
+ </div><div class="para">
+ </div><div class="para">
+ tid=`rpm -q --qf "%{INSTALLTID}\n" $*`
+ </div><div class="para">
+ </div><div class="para">
+ rpm -q --tid $tid
+ </div><div class="para">
+ This script uses the query format to get the transaction ID, or tid, for a particular package. It then passes this transaction ID to the rpm command to query for all packages installed with the same transaction ID.
+ </div><div class="para">
+ For example:
+ </div><div class="para">
+ $ ./rpmtran tcl
+ </div><div class="para">
+ itcl-3.2-74
+ </div><div class="para">
+ tclx-8.3-74
+ </div><div class="para">
+ tcl-8.3.3-74
+ </div><div class="para">
+ tix-8.2.0b1-74
+ </div><div class="para">
+ tkinter-2.2.1-17
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id979252" class="title">Reading HTML documentation for a package</h1></div></div></div><div class="para">
+ You can combine the rpm command with other commands as well. For example, the rpm –qd command lists the documentation files with a package. If this documentation is in HTML format, you can display this documentation in a Web browser such as Mozilla. Furthermore, by convention, the starting page for HTML documentation should be a file named index.html. Listing 15-5 combines all these factors:
+ </div><div class="para">
+ Listing 15-5: rpmmoz
+ </div><div class="para">
+ #!/bin/sh
+ </div><div class="para">
+ </div><div class="para">
+ html_file=`rpm -qd $* | grep index.html | head -n 1 `
+ </div><div class="para">
+ </div><div class="para">
+ echo "Launching Web browser with $html_file"
+ </div><div class="para">
+ </div><div class="para">
+ htmlview $html_file &
+ </div><div class="para">
+ This script searches for the documentation for a given package name, finds the first file named index.html, and launches the Web browser in the background to display this file, using the htmlview command which will likely run mozilla or your configured Web browser. When you run this command, you should see output like the following; then the Web browser should appear:
+ </div><div class="para">
+ $ ./rpmmoz rpm-devel
+ </div><div class="para">
+ Launching Web browser with /usr/share/doc/rpm-devel-4.1/apidocs/html/index.html
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ This script does not check for errors. If there are no files named index.html, the script launches the Web browser anyway. You could fix this by changing the script to validate the html_file variable prior to launching the Web browser.
+ </div></div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id561272" class="title">Where to Go From Here</h1></div></div></div><div class="para">
+ This chapter just introduces the basics for shell scripting. There are many more things you can do. The online manual pages for the bash or tcsh commands provide a wealth of reference information on these shells.
+ </div><div class="para">
+ A number of Web sites provide tutorials on bash, including http://pegasus.rutgers.edu/~elflord/unix/bash-tute.html and www.linuxorbit.com/modules.php?op=modload&name=Sections&file=index&req=viewarticle&artid=459. In addition, the Linux Documentation Project at www.tldp.org/guides.html provides a bash scripting guide, along with a number of bash- and shell-related how-to documents at www.tldp.org/HOWTO/HOWTO-INDEX/howtos.html.
+ </div><div class="para">
+ Teach Yourself Linux, by Steve Oualline and Eric Foster-Johnson (John Wiley & Sons, 2000), introduces a number of Linux topics, including text editors and scripting, for those new to Linux. And Graphical Applications with Tcl and Tk (Hungry Minds, Inc., 1997) by Eric Foster-Johnson, covers another scripting language, Tcl/Tk.
+ </div><div class="para">
+ Use your imagination. Any command that you run often or that is hard to type can be scripted. Furthermore, you can write complex scripts that automate some of the more tedious tasks you need to perform.
+ </div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id628097" class="title">Summary</h1></div></div></div><div class="para">
+ Scripting is the art of writing a set of commands into text files to speed up your work. Programming is the art of writing a set of commands into text files, compiling the text files, and getting paid more. Choosing when to program and when to script isn’t always a clear-cut decision, but generally programs are move involved and complex, while scripts are shorter tools that automate your work. This chapter provides just a glimpse of all you can do with scripts and the RPM system.
+ </div><div class="para">
+ Scripts work very well for capturing obscure syntax options for the rpm command, especially the query formats. You can figure out a command once and then save the command as a script to save time in the future.
+ </div><div class="para">
+ Scripts aren’t the best choice for all tasks, though. In many cases, you need to write a program to accomplish your goals. The next chapter delves into the RPM C programming API, rpmlib.
+ </div></div></div><div xml:lang="ro" class="chapter" id="ch-programming-c" lang="ro"><div class="titlepage"><div><div><h2 class="title">Cap. 15. Programming RPM with C</h2></div></div></div><div class="toc"><dl><dt><span class="sect1"><a href="#id772965">15.1. Programming with the C Library</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id612187">15.1.1. Setting Up a C Programming Environment</a></span></dt><dt><span class="sect2"><a href="#id692296">15.1.2. Setting Up the RPM Programming Environment</a></span></dt><dt><span class="sect2"><a href="#id726502">15.1.3. Using the RPM Library</a></span></dt><dt><span class="sect2"><a href="#id607656">15.1.4. Compiling and Linking RPM Programs</a></span></dt><dt><span class="sect2"><a href="#id812831">15.1.5. Getting information on your RPM environment</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id677086">15.2. The Power of popt</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id573466">15.2.1. Po
pt aliases</a></span></dt><dt><span class="sect2"><a href="#id854018">15.2.2. Programming with popt</a></span></dt><dt><span class="sect2"><a href="#id785286">15.2.3. Handling Errors</a></span></dt><dt><span class="sect2"><a href="#id870911">15.2.4. Running a popt example</a></span></dt><dt><span class="sect2"><a href="#id853423">15.2.5. Handling rpm command-line options</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id784404">15.3. Working with RPM Files</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id791650">15.3.1. Opening RPM files</a></span></dt><dt><span class="sect2"><a href="#id673138">15.3.2. Reading the RPM lead and signature</a></span></dt><dt><span class="sect2"><a href="#id865045">15.3.3. Reading header information</a></span></dt><dt><span class="sect2"><a href="#id678698">15.3.4. A shortcut to header information</a></span></dt><dt><span class="sect2"><a href="#id676439">15.3.5. Closing RPM files</a></span></dt></dl></dd><dt><span class="s
ect1"><a href="#id569976">15.4. Programming with the RPM Database</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id808107">15.4.1. Database iterators</a></span></dt><dt><span class="sect2"><a href="#id749729">15.4.2. Dependency Sets</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id659876">15.5. Comparing an RPM File to an Installed Package</a></span></dt><dt><span class="sect1"><a href="#id582358">15.6. Where to Go from Here</a></span></dt><dt><span class="sect1"><a href="#id577217">15.7. Summary</a></span></dt></dl></div><div class="para">
+ This chapter covers:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Using the RPM C library
+ </div></li><li class="listitem"><div class="para">
+ Setting up a development environment
+ </div></li><li class="listitem"><div class="para">
+ Programming with the RPM C library
+ </div></li><li class="listitem"><div class="para">
+ The power of <code class="command">popt</code> for command-line argument processing
+ </div></li><li class="listitem"><div class="para">
+ Comparing package files to installed packages
+ </div></li></ul></div><div class="para">
+ The RPM C library allows you to perform all the operations of the rpm command from within your own C or C++ programs.
+ </div><div class="para">
+ The reason is simple: The rpm command was created using the RPM libraries. These same libraries are available for you to use in your own programs.
+ </div><div class="para">
+ The rpm command itself is quick and, for the most part, simple. So, why would you want to write RPM programs?
+ </div><div class="para">
+ There are many reasons, some of which are listed here:
+ </div><div class="para">
+ *Speed: If you need to perform a task on many RPM files such as verifying a large set of files, then performing the task from one program will be a lot faster than launching the rpm command for each file.
+ </div><div class="para">
+ *Custom options: If you need to do something the rpm command doesn't offer, or doesn't make easy, then you may want to write your own program.
+ </div><div class="para">
+ *Convenience: If you need to make many packages quickly, with custom options, your best bet may be to create a program suited for your tasks. Before doing this, though, be sure to look into whether writing a shell script will handle your task adequately. You'll find writing RPM shell scripts goes much faster than writing whole programs.
+ </div><div class="para">
+ *Installation programs: The Windows world has standardized on graphical installation programs such as InstallShield or InstallAnywhere. The RPM system, on the other hand, has focused on automated installation with the rpm command. You can combine the best of both worlds by writing a graphical installation program on top of the RPM system.
+ </div><div class="para">
+ *Integration with environments: You may want to better integrate RPM with a Linux desktop environment such as GNOME or KDE.
+ </div><div class="para">
+ *Working with other languages: This book covers programming RPM with C, the core language for the library, as well as the Python and Perl scripting languages. You can use the RPM library, though, to help bind with other languages such as Tcl, Ruby, or even C# (especially one of the C# implementations for Linux).
+ </div><div class="para">
+ This chapter and the next cover RPM programming. This chapter covers the RPM C programming library, which provides low-level access to RPM functionality. The next chapter covers the RPM Python programming library, which provides a much higher-level of abstraction. If you are attempting to write a complex RPM program, your best bet is to try the Python API first. Even so, there is a lot you can do with the RPM C library.
+ </div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id772965" class="title">Programming with the C Library</h1></div></div></div><div class="para">
+ RPM C programs are C programs that call on functions in the RPM library, often called rpmlib. To use the rpmlib, you need to set up a C programming environment and install the rpm-devel package.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id612187" class="title">Setting Up a C Programming Environment</h1></div></div></div><div class="para">
+ At the very least, you’ll need a C compiler, gcc, and a text editor. The easiest way to get the C compiler is to install the packages grouped under Software Development with the Red Hat package management tool.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ See <a class="xref" href="#ch-management-software">Cap. 7, <em>RPM Management Software</em></a> for more on the Red Hat package management tool.
+ </div><div class="para">
+ The gcc package requires a number of capabilities. Make sure you install all the necessary packages. Just about every Linux distribution includes gcc and everything you need to develop C programs, so this should not be a problem.
+ </div><div class="para">
+ For text editors, you can use the vi or emacs text editors, or any of a number of graphical editors such as gedit.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ <a class="xref" href="#ch-development-tools">Cap. 26, <em>Linux Text Editors and Development Tools</em></a> covers Linux text editors and development tools.
+ </div><div class="para">
+ Once you have a C programming environment set up, you next need to get the RPM library for an RPM development environment.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id692296" class="title">Setting Up the RPM Programming Environment</h1></div></div></div><div class="para">
+ To program with the RPM library, you need to install the rpm-devel package. You must have a version of rpm-devel that matches your version of the rpm package. If you have Red Hat Linux, your installation CDs will also have the version of the RPM development package that corresponds to your system.
+ </div><div class="para">
+ Your program should link against the same libraries that are used by the rpm command itself in order to insure compatibility, so make sure that the version of the rpm-devel package matches the rpm package itself. In most cases, the best bet is to use the RPM programs and libraries that come with your version of Linux.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ You can also download the rpm packages from ftp://ftp.rpm.org/pub/rpm/dist/. This site includes versions of the RPM libraries going back to 1996, ancient history in terms of Linux.
+ </div><div class="para">
+ The package you need is rpm-devel. If you installed Red Hat Linux 8.0, the package is rpm-devel-4.1-1.06. This package includes header files, documentation, and libraries.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id726502" class="title">Using the RPM Library</h1></div></div></div><div class="para">
+ All C programs using the RPM library need to include the file rpmlib.h, which defines the core data structures, constants, and functions. One thing you’ll quickly note is that the RPM C library accesses RPM data at a very low level. This is one reason why many developers are moving to Python for their RPM programs, since the Python RPM API presents a higher level of abstraction.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ <a class="xref" href="#ch-rpm-programming-python">Cap. 16, <em>Programming RPM with Python</em></a> covers programming RPM with Python.
+ </div><div class="para">
+ In addition to rpmlib.h, the header file rpmcli.h defines a high-level API based on the command-line options to the rpm command. (The cli in rpmcli stands for command-line interface.) Table 16-1 lists other important RPM header files that make up the major subsystems of the RPM system.
+ </div><div class="para">
+ Table 16-1 RPM sub-system header files
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ File
+ </div>
+
+ </td><td>
+ <div class="para">
+ Defines
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpmdb.h
+ </div>
+
+ </td><td>
+ <div class="para">
+ RPM database access
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpmio.h
+ </div>
+
+ </td><td>
+ <div class="para">
+ RPM input/output routines
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ popt.h
+ </div>
+
+ </td><td>
+ <div class="para">
+ Command-line option processing
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ In addition, a number of header files define the major data objects in the RPM system and the functions that operate on these data objects. Table 16-2 lists these header files.
+ </div><div class="para">
+ Table 16-2 RPM data object header files
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ File
+ </div>
+
+ </td><td>
+ <div class="para">
+ Defines
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpmts.h
+ </div>
+
+ </td><td>
+ <div class="para">
+ Transaction sets
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpmte.h
+ </div>
+
+ </td><td>
+ <div class="para">
+ Transaction elements (packages)
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpmds.h
+ </div>
+
+ </td><td>
+ <div class="para">
+ Dependency sets
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpmfi.h
+ </div>
+
+ </td><td>
+ <div class="para">
+ File information
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ header.h
+ </div>
+
+ </td><td>
+ <div class="para">
+ Package headers
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ All the RPM include files are located in /usr/include/rpm on most versions of Linux.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ You can use the rpm command and the queries introduced in <a class="xref" href="#ch-using-rpm-db">Cap. 4, <em>Using the RPM Database</em></a> to determine exactly where the header files are located. Simply execute the following command:
+ </div><div class="para">
+ $ rpm –ql rpm-devel
+ </div><div class="para">
+ Examine the output of this command for include files.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id607656" class="title">Compiling and Linking RPM Programs</h1></div></div></div><div class="para">
+ RPM programs using the rpmlib C API are the same as C programs everywhere. You need to include the proper header files that define the API calls you need, and link with the right set of libraries.
+ </div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id607668" class="title">Include Files</h1></div></div></div><div class="para">
+ The rpm include files are located in /usr/include/rpm, so you should add this directory to the set of directories that the C compiler looks in for include files with the –I command-line option. For example:
+ </div><div class="para">
+ $ gcc –I/usr/include/rpm –c rpm1.c
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ This also means that you can install the rpm header files in other directories as needed, and just change the –I command-line option.
+ </div><div class="para">
+ To help debug problems, you probably want to add the -Wall (output all warnings) and -g (compile with debugging information). For example:
+ </div><div class="para">
+ $ gcc -Wall -g –I/usr/include/rpm –c rpm1.c
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id621045" class="title">Libraries</h1></div></div></div><div class="para">
+ The main rpm library is librpm.a, or a shared version of this same library. To do most anything with RPM programming, you need to link in the following libraries, as listed in Table 16-3.
+ </div><div class="para">
+ Table 16-3 Required rpm libraries
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Library
+ </div>
+
+ </td><td>
+ <div class="para">
+ Usage
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpm
+ </div>
+
+ </td><td>
+ <div class="para">
+ Main RPM library
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpmdb
+ </div>
+
+ </td><td>
+ <div class="para">
+ RPM database library
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpmio
+ </div>
+
+ </td><td>
+ <div class="para">
+ RPM input/output
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ popt
+ </div>
+
+ </td><td>
+ <div class="para">
+ Command-line option parsing library
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ If you are creating RPMs from your C programs, you also need to link in the rpmbuild library. To compile and link a simple RPM program, you need a command like the following:
+ </div><div class="para">
+ gcc -I/usr/include/rpm -o program program.c –lrpmbuild \
+ </div><div class="para">
+ -lrpm -lrpmdb -lrpmio –lpopt
+ </div><div class="para">
+ On some versions of Linux or on other operating systems, you’ll likely need to link a set of helper libraries, as shown following:
+ </div><div class="para">
+ gcc -I/usr/include/rpm -o program program.c –lrpmbuild \
+ </div><div class="para">
+ -lrpm -lrpmdb -lrpmio –lpopt -lelf -lbz2 -lz
+ </div><div class="para">
+ If you have installed the rpm libraries in a non-standard directory, you need to use the –L option to specify where else to look for libraries. For example:
+ </div><div class="para">
+ gcc -I/usr/include/rpm -o program program.c –L/opt/lib/rpm \
+ </div><div class="para">
+ -lrpmbuild -lrpm -lrpmdb -lrpmio –lpopt -lelf -lbz2 -lz
+ </div><div class="para">
+ The -L option tells the cc compiler to look in the /opt/lib/rpm directory as well as in the standard locations such as /usr/lib.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ Starting with RPM 4.2, you should just need to link in the rpm library. The other libraries will get pulled in automatically if needed.
+ </div></div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id812831" class="title">Getting information on your RPM environment</h1></div></div></div><div class="para">
+ A large part of the RPM system lies in system-specific configuration, including the platform you are running on, compatible platforms, and locations of various files. The RPM rc and macro systems support hundreds of options tuned to the specifics of your system, and any customizations you have configured.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ <a class="xref" href="#ch-customizing-rpm">Cap. 20, <em>Customizing RPM Behavior</em></a> covers customizing RPM.
+ </div><div class="para">
+ Your C programs need to access these RPM system settings to ensure that all data values are properly set up for your system architecture and installation. So, to start an RPM C program, you need to read in all the configuration files. To do this, call rpmReadConfigFiles.
+ </div><div class="para">
+ int rpmReadConfigFiles(const char *files, const char *target);
+ </div><div class="para">
+ The files parameter holds a colon-delimited list of files that make up your system’s configuration. The target parameter holds the target platform. You can pass NULL for both these parameters to use the RPM defaults, which is generally what you want.
+ </div><div class="para">
+ The rpmReadConfigFiles function returns a 0 on success, or –1 on errors.
+ </div><div class="para">
+ Once you have read in the configuration files, you can access values in the configuration, or print it out.
+ </div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id588601" class="title">Printing the Configuration</h1></div></div></div><div class="para">
+ To print out the configuration, call rpmShowRC.
+ </div><div class="para">
+ int rpmShowRC(FILE* output);
+ </div><div class="para">
+ Pass in an output file to print the configuration to, such as stdout. For example:
+ </div><div class="para">
+ rpmShowRC( stdout );
+ </div><div class="para">
+ The rpmShowRC function always returns 0.
+ </div><div class="para">
+ To control some of the output from rpmShowRC, and other RPM library functions, you can set the logging verbosity level by calling rpmSetVerbosity:
+ </div><div class="para">
+ void rpmSetVerbosity(int level);
+ </div><div class="para">
+ For example:
+ </div><div class="para">
+ rpmSetVerbosity(RPMMESS_NORMAL);
+ </div><div class="para">
+ Table 16-4 lists the verbosity levels from rpmio/rpmmessages.h going from least output to more output.
+ </div><div class="para">
+ Table 16-4 Output verbosity levels
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Level
+ </div>
+
+ </td><td>
+ <div class="para">
+ Usage
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMMESS_FATALERROR
+ </div>
+
+ </td><td>
+ <div class="para">
+ Only critical error conditions and above
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMMESS_ERROR
+ </div>
+
+ </td><td>
+ <div class="para">
+ Only error conditions and above
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMMESS_WARNING
+ </div>
+
+ </td><td>
+ <div class="para">
+ Only warning conditions and above
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMMESS_QUIET
+ </div>
+
+ </td><td>
+ <div class="para">
+ Same as RPMMESS_WARNING
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMMESS_NORMAL
+ </div>
+
+ </td><td>
+ <div class="para">
+ Only significant messages
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMMESS_VERBOSE
+ </div>
+
+ </td><td>
+ <div class="para">
+ Verbose informational messages
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMMESS_DEBUG
+ </div>
+
+ </td><td>
+ <div class="para">
+ Debugging messages, and everything above
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ You can put together a simple RPM program such as the one shown in Listing 16-1.
+ </div><div class="para">
+ Listing 16-1: rpm1.c
+ </div><div class="para">
+ /* Show the rpmrc settings. */
+ </div><div class="para">
+ #include <stdio.h>
+ </div><div class="para">
+ #include <stdlib.h>
+ </div><div class="para">
+ </div><div class="para">
+ #include <rpmlib.h>
+ </div><div class="para">
+ </div><div class="para">
+ </div><div class="para">
+ int main(int argc, char * argv[]) {
+ </div><div class="para">
+ </div><div class="para">
+ int status = rpmReadConfigFiles( (const char*) NULL,
+ </div><div class="para">
+ (const char*) NULL);
+ </div><div class="para">
+ </div><div class="para">
+ if (status != 0) {
+ </div><div class="para">
+ printf("Error reading RC files.\n");
+ </div><div class="para">
+ exit(-1);
+ </div><div class="para">
+ } else {
+ </div><div class="para">
+ printf("Read RC OK\n");
+ </div><div class="para">
+ }
+ </div><div class="para">
+ </div><div class="para">
+ rpmSetVerbosity(RPMMESS_NORMAL);
+ </div><div class="para">
+ </div><div class="para">
+ rpmShowRC( stdout );
+ </div><div class="para">
+ </div><div class="para">
+ exit(0);
+ </div><div class="para">
+ }
+ </div><div class="para">
+ Compile this program with a command like the following:
+ </div><div class="para">
+ $ cc -I/usr/include/rpm -o rpm1 rpm1.c -lrpm -lrpmdb -lrpmio –lpopt
+ </div><div class="para">
+ When you run this program, you should see the contents of your configuration printed to the screen.
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id854091" class="title">Expanding the Value of Macros</h1></div></div></div><div class="para">
+ With all the rc and macro configuration files, the RPM system has a lot of values, usually called macros, that you can use to refer to settings. The term macro is used because the values can be more than simple strings. You can have one macro refer to the value of other macros, for example. The basic macro syntax is:
+ </div><div class="para">
+ %name_of_macro
+ </div><div class="para">
+ For example:
+ </div><div class="para">
+ %_target
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ Most of the internal RPM macros start with an underscore, _.
+ </div><div class="para">
+ You can expand a macro with the rpm --eval command:
+ </div><div class="para">
+ $ rpm --eval %_target
+ </div><div class="para">
+ i386-linux
+ </div><div class="para">
+ You can also refer to a macro using the following syntax:
+ </div><div class="para">
+ %{name_of_macro}
+ </div><div class="para">
+ For example:
+ </div><div class="para">
+ %{_target}
+ </div><div class="para">
+ This syntax makes it easier to include a macro in combinations with other text and other macros, since it clearly delineates the macro name.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ <a class="xref" href="#ch-customizing-rpm">Cap. 20, <em>Customizing RPM Behavior</em></a> covers macros in depth. In your C programs, your code will likely need to expand the value of macros to place data in the proper directories, determine the platform architecture, and so on.
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id792471" class="title">Expanding Macros in Your Code</h1></div></div></div><div class="para">
+ You can use rpmExpand to determine the value of system macros from within your C programs.
+ </div><div class="para">
+ The rpmExpand function can expand the values of one or more macros, returning the expanded value. You can pass a variable number of parameters to rpmExpand, and you must terminate the list with a NULL:
+ </div><div class="para">
+ char* rpmExpand (const char *arg,...);
+ </div><div class="para">
+ You need to free the data returned by rpmExpand by calling free.
+ </div><div class="para">
+ The program in Listing 16-2 takes the first command-line argument to your program (after the program name) and expands that argument as a macro.
+ </div><div class="para">
+ Listing 16-2: rpmexpand.c
+ </div><div class="para">
+ /* Show some macro settings. */
+ </div><div class="para">
+ #include <stdio.h>
+ </div><div class="para">
+ #include <stdlib.h>
+ </div><div class="para">
+ </div><div class="para">
+ #include <rpmlib.h>
+ </div><div class="para">
+ #include <rpmmacro.h>
+ </div><div class="para">
+ </div><div class="para">
+ int main(int argc, char * argv[]) {
+ </div><div class="para">
+ </div><div class="para">
+ int status = rpmReadConfigFiles( (const char*) NULL,
+ </div><div class="para">
+ (const char*) NULL);
+ </div><div class="para">
+ </div><div class="para">
+ if (status != 0) {
+ </div><div class="para">
+ printf("Error reading RC files.\n");
+ </div><div class="para">
+ exit(-1);
+ </div><div class="para">
+ }
+ </div><div class="para">
+ </div><div class="para">
+ char* value = rpmExpand(argv[1], (const char*) NULL);
+ </div><div class="para">
+ </div><div class="para">
+ printf("Value of macro is [%s]\n", value);
+ </div><div class="para">
+ </div><div class="para">
+ exit(0);
+ </div><div class="para">
+ }
+ </div><div class="para">
+ Compile and link this program as shown previously.
+ </div><div class="para">
+ When you run this program, pass the name of a macro to expand. For example:
+ </div><div class="para">
+ $ ./rpmexpand %_target
+ </div><div class="para">
+ Value of macro is [i386-linux]
+ </div><div class="para">
+ You can pass multiple macros together, as shown following:
+ </div><div class="para">
+ $ ./rpmexpand %_builddir/%_target
+ </div><div class="para">
+ Value of macro is [/usr/src/redhat/BUILD/i386-linux]
+ </div><div class="para">
+ You can verify this program with the rpm --eval command, introduced previously:
+ </div><div class="para">
+ $ rpm --eval %_builddir/%_target
+ </div><div class="para">
+ /usr/src/redhat/BUILD/i386-linux
+ </div></div></div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id677086" class="title">The Power of popt</h1></div></div></div><div class="para">
+ Popt provides a powerful command-line processing library, allowing the rpm command to handle a variety of options in a very flexible way. You can use popt alone as a library in its own right, or use it combined with the rpm library to handle command-line options like those of the rpm command.
+ </div><div class="para">
+ At its most basic, popt processes the command-line arguments to a C program, traditionally called argc and argv, into an option table that describes and contains all the option values.
+ </div><div class="para">
+ The main advantage popt has over simpler libraries such as getopt lies in the ability to handle complex arguments and to define aliases. The rpm command supports three different behaviors for the –i option, depending on the context (install a package, get information on a package as part of a query, and perform the install stage of a source RPM, as part of rpmbuild).
+ </div><div class="para">
+ The popt library supports both traditional UNIX short options such as –U and the longer options common for GNU programs, especially on Linux, such as --upgrade. For the popt library, you can define both short and long variants for each option. In addition, command-line options may be individual flags, such as –v for verbose, or options that expect one or more data values as arguments, such as –f, which requires a file name.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id573466" class="title">Popt aliases</h1></div></div></div><div class="para">
+ One of the most powerful features of popt is the ability to define aliases. A popt alias allows you to define one command-line option as an alias for a set of options. As its simplest, the rpm command-line options --upgrade and –U refer to the same action. You could define one as an alias for the other.
+ </div><div class="para">
+ With rpm, the file /usr/lib/rpm/rpmpopt-4.1 (for RPM version 4.1) defines over 400 lines of popt aliases to configure the rpm command-line options. For example:
+ </div><div class="para">
+ Rpm alias –requires --qf \
+ </div><div class="para">
+ "[%{REQUIRENAME} %{REQUIREFLAGS:depflags} %{REQUIREVERSION}\n]" \
+ </div><div class="para">
+ --POPTdesc=$"list capabilities required by package(s)"
+ </div><div class="para">
+ This example defines rpm --requires as really a query using the --qf or --queryformat options covered in <a class="xref" href="#ch-using-rpm-db">Cap. 4, <em>Using the RPM Database</em></a> .
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ See <a class="xref" href="#ch-customizing-rpm">Cap. 20, <em>Customizing RPM Behavior</em></a> for more on defining popt aliases.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id854018" class="title">Programming with popt</h1></div></div></div><div class="para">
+ To use popt in your programs, you need to fill in a table of options and then call poptGetContext. The poptGetContext function parses the command-line options and returns a poptContext, an opaque data type that you need to pass as a parameter to a number of popt functions. The poptContext holds the state of your command-line processing. This allows you to call the popt library with multiple sets of arguments. Each set will have an associate poptContext to keep all the data separate.
+ </div><div class="para">
+ The basic poptGetContext function signature follows:
+ </div><div class="para">
+ poptContext poptGetContext (const char * name,
+ </div><div class="para">
+ int argc,
+ </div><div class="para">
+ const char ** argv,
+ </div><div class="para">
+ const struct poptOption * options,
+ </div><div class="para">
+ int flags );
+ </div><div class="para">
+ All the popt functions require the popt.h include file:
+ </div><div class="para">
+ #include <popt.h>
+ </div><div class="para">
+ The flags should be a bitmask of any options you require, including those listed in Table 16-5.
+ </div><div class="para">
+ Table 16-5 Flags for poptGetContext
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Flag
+ </div>
+
+ </td><td>
+ <div class="para">
+ Meaning
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ POPT_CONTEXT_NO_EXEC
+ </div>
+
+ </td><td>
+ <div class="para">
+ Ignore executable expansions
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ POPT_CONTEXT_KEEP_FIRST
+ </div>
+
+ </td><td>
+ <div class="para">
+ Treat argv[0], the command name, as an option
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ POPT_CONTEXT_POSIXMEHARDER
+ </div>
+
+ </td><td>
+ <div class="para">
+ Do not allow options to follow arguments
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ When done with a poptContext, you should free it by calling poptFreeContext:
+ </div><div class="para">
+ poptContext poptFreeContext(poptContext context);
+ </div><div class="para">
+ The call to poptFreeContext frees up the memory allocated for the context.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ You can also fill in a poptContext from settings in a file with poptReadConfigFile:
+ </div><div class="para">
+ int poptReadConfigFile(poptContext context,
+ </div><div class="para">
+ const char * file_name);
+ </div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id725140" class="title">Filling in the Options Table</h1></div></div></div><div class="para">
+ You need to pass in a table that defines all the possible options. This table is an array of structures, where each structure defines one option. The format for a single option follows:
+ </div><div class="para">
+ struct poptOption {
+ </div><div class="para">
+ const char * longName;
+ </div><div class="para">
+ char shortName;
+ </div><div class="para">
+ int argInfo;
+ </div><div class="para">
+ void * arg;
+ </div><div class="para">
+ int val;
+ </div><div class="para">
+ const char * descrip;
+ </div><div class="para">
+ const char * argDescrip;
+ </div><div class="para">
+ };
+ </div><div class="para">
+ Going through this structure, the longName defines the long version of the option, such as "upgrade" for --upgrade. The shortName defines the short, one-character option, such as 'U' for an option of -U. You can place a null character, '\0', to specify no short option. With the rpm command, the --rebuilddb option has only a long name and not a short name, for example.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ The longName is not preceded by the double minus sign. Similarly, the shortName is not preceded by the single minus sign.
+ </div><div class="para">
+ The descrip field holds a short description of the option and the argDescrip field holds a description of the types of values it expects, or NULL if this option expects no values.
+ </div><div class="para">
+ The argInfo field holds a flag that tells the popt library how to treat the option. At the very least, you need to define the type of the option. You can also define special processing flags. Table 16-6 lists the argument types in the options table.
+ </div><div class="para">
+ Table 16-6 Popt option table argInfo argument types
+ </div><div class="informaltable"><table border="1"><colgroup><col width="33%" /><col width="33%" /><col width="33%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Type
+ </div>
+
+ </td><td>
+ <div class="para">
+ Value
+ </div>
+
+ </td><td>
+ <div class="para">
+ Meaning
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ POPT_ARG_NONE
+ </div>
+
+ </td><td>
+ <div class="para">
+ 0
+ </div>
+
+ </td><td>
+ <div class="para">
+ No argument data, just the option such as -v
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ POPT_ARG_STRING
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1
+ </div>
+
+ </td><td>
+ <div class="para">
+ arg treated as string
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ POPT_ARG_INT
+ </div>
+
+ </td><td>
+ <div class="para">
+ 2
+ </div>
+
+ </td><td>
+ <div class="para">
+ arg treated as int
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ POPT_ARG_LONG
+ </div>
+
+ </td><td>
+ <div class="para">
+ 3
+ </div>
+
+ </td><td>
+ <div class="para">
+ arg treated as long
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ POPT_ARG_INCLUDE_TABLE
+ </div>
+
+ </td><td>
+ <div class="para">
+ 4
+ </div>
+
+ </td><td>
+ <div class="para">
+ arg points to a table
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ POPT_ARG_CALLBACK
+ </div>
+
+ </td><td>
+ <div class="para">
+ 5
+ </div>
+
+ </td><td>
+ <div class="para">
+ arg points to a callback function
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ POPT_ARG_INTL_DOMAIN
+ </div>
+
+ </td><td>
+ <div class="para">
+ 6
+ </div>
+
+ </td><td>
+ <div class="para">
+ sets translation domain
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ POPT_ARG_VAL
+ </div>
+
+ </td><td>
+ <div class="para">
+ 7
+ </div>
+
+ </td><td>
+ <div class="para">
+ use value of val field for arg
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ POPT_ARG_FLOAT
+ </div>
+
+ </td><td>
+ <div class="para">
+ 8
+ </div>
+
+ </td><td>
+ <div class="para">
+ arg treated as float
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ POPT_ARG_DOUBLE
+ </div>
+
+ </td><td>
+ <div class="para">
+ 9
+ </div>
+
+ </td><td>
+ <div class="para">
+ arg treated as double
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ Use these constants, from the include file popt.h, in place of the actual numbers.
+ </div><div class="para">
+ Depending on the type you define in the argInfo field, popt will interpret the generic pointer field, arg, in different ways. Using a pointer allows the popt library to automatically update your program variables based on the command-line option settings.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ You can pass NULL for the arg field. In this case, the popt library will not set any values for you.
+ </div><div class="para">
+ The POPT_ARG_NONE type indicates that this option has no argument. For example, the -v verbose option has no data. On the other hand, the POPT_ARG_STRING type indicates that the user should provide a string. For example, the -f option to the rpm command is expected to include a string argument, the name of the file to look up.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ If the argInfo argument type is POPT_ARG_NONE, the popt library will set arg to 1 if the option is present on the command line. You should pass a pointer to an int if you want this set for you.
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id496362" class="title">Popt Callbacks</h1></div></div></div><div class="para">
+ The POPT_ARG_CALLBACK type indicates that the arg field holds a function pointer to a callback function of the following type:
+ </div><div class="para">
+ typedef void (*poptCallbackType) (poptContext con,
+ </div><div class="para">
+ enum poptCallbackReason reason,
+ </div><div class="para">
+ const struct poptOption * opt,
+ </div><div class="para">
+ const char * arg,
+ </div><div class="para">
+ const void * data);
+ </div><div class="para">
+ The callback reason will be one of the following enum values:
+ </div><div class="para">
+ enum poptCallbackReason {
+ </div><div class="para">
+ POPT_CALLBACK_REASON_PRE = 0,
+ </div><div class="para">
+ POPT_CALLBACK_REASON_POST = 1,
+ </div><div class="para">
+ POPT_CALLBACK_REASON_OPTION = 2
+ </div><div class="para">
+ };
+ </div><div class="para">
+ The data field holds the value of the descrip field in the poptOption entry. You can cheat and stuff a pointer to arbitrary data into this field.
+ </div><div class="para">
+ The callback function is most useful if you are using nested option tables. You can place your processing code for the nested options into a callback.
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id617350" class="title">Special Option Table Flags</h1></div></div></div><div class="para">
+ In addition to the types in Table 16-6, you can also define special bit flags that define extra processing information for each option. Combine these bit flags with the type values using a logical OR operation:
+ </div><div class="para">
+ *The POPT_ARGFLAG_ONEDASH flag allows the longName to be used with one or two dashes, such as -upgrade or --upgrade.
+ </div><div class="para">
+ *For bitmask options, the POPT_ARGFLAG_OR, POPT_ARGFLAG_NOR, POPT_ARGFLAG_AND, POPT_ARGFLAG_NAND, and POPT_ARGFLAG_XOR type flags tell the popt library to apply the given operation, OR, NOR, AND, NAND, or XOR, to the value if set. The POPT_ARGFLAG_NOT flag tells the popt library to negate the value first.
+ </div><div class="para">
+ *You can also use the macros POPT_BIT_SET to set a bit and POPT_BIT_CLR to clear a bit.
+ </div><div class="para">
+ *The POPT_ARGFLAG_OPTIONAL flag indicates that the argument value is optional.
+ </div><div class="para">
+ *The POPT_ARGFLAG_DOC_HIDDEN flag tells popt to hide this option when displaying the help documentation. In other words, this is an internal option.
+ </div><div class="para">
+ *The rarely used POPT_ARGFLAG_STRIP flag tells popt to consume an option and ignore it. This option is rarely used.
+ </div><div class="para">
+ *The POPT_ARGFLAG_SHOW_DEFAULT flag tells popt to show the initial value of the argument for this option as a default when displaying a help message.
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id702120" class="title">Magic Options</h1></div></div></div><div class="para">
+ With RPM programs, developers usually round out the option table with three special options: POPT_AUTOALIAS, POPT_AUTOHELP, and POPT_TABLEEND. The POPT_AUTOALIAS option sets up a table of aliases:
+ </div><div class="para">
+ #define POPT_AUTOALIAS { NULL, '\0', POPT_ARG_INCLUDE_TABLE, poptAliasOptions, \
+ </div><div class="para">
+ 0, "Options implemented via popt alias/exec:", NULL },
+ </div><div class="para">
+ This option refers to the table, poptAliasOptions. You can use the POPT_ARG_INCLUDE_TABLE argInfo type to include another table of options. These options get filled in from popt aliases. In addition, within RPM programs, another table, rpmcliAllPoptTable, holds a set of options common to all RPM programs.
+ </div><div class="para">
+ The POPT_AUTOHELP option supports standard help options. The POPT_AUTOHELP macro adds in automatic support for -?, --help, and --usage options.
+ </div><div class="para">
+ #define POPT_AUTOHELP { NULL, '\0', POPT_ARG_INCLUDE_TABLE, poptHelpOptions, \
+ </div><div class="para">
+ 0, "Help options:", NULL },
+ </div><div class="para">
+ The POPT_TABLEEND option defines an empty option to mark the end of the table. You must include an empty option to end the table, and POPT_TABLEEND makes this easy.
+ </div><div class="para">
+ #define POPT_TABLEEND { NULL, '\0', 0, 0, 0, NULL, NULL }
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ The code in Listing 16-3, in the "Running a Popt Example" section later in this chapter, shows a full option table.
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id723305" class="title">Parsing the Command-Line Options</h1></div></div></div><div class="para">
+ Once you have set up a poptGetContext, you need to iterate over all the command-line parameters. To do this, call poptGetNextOpt:
+ </div><div class="para">
+ int poptGetNextOpt(poptContext context);
+ </div><div class="para">
+ If an error occurs, poptGetNextOpt returns a negative error code. If the context is at the end of the options, poptGetNextOpt returns –1. Table 16-7 lists the error codes:
+ </div><div class="para">
+ Table 16-7 Error codes from poptGetNextOpt
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Code
+ </div>
+
+ </td><td>
+ <div class="para">
+ Meaning
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ POPT_ERROR_NOARG
+ </div>
+
+ </td><td>
+ <div class="para">
+ Option requires an argument, but it is missing
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ POPT_ERROR_BADOPT
+ </div>
+
+ </td><td>
+ <div class="para">
+ Argument could not be parsed
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ POPT_ERROR_OPTSTOODEEP
+ </div>
+
+ </td><td>
+ <div class="para">
+ Aliases are nested too deeply
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ POPT_ERROR_BADQUOTE
+ </div>
+
+ </td><td>
+ <div class="para">
+ Start and end quotation marks don't match
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ POPT_ERROR_BADNUMBER
+ </div>
+
+ </td><td>
+ <div class="para">
+ Argument could not be converted to a number
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ POPT_ERROR_OVERFLOW
+ </div>
+
+ </td><td>
+ <div class="para">
+ Argument number was too big or too small
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ POPT_ERROR_ERRNO
+ </div>
+
+ </td><td>
+ <div class="para">
+ A system call returned an error in errno
+ </div>
+
+ </td></tr></tbody></table></div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id839778" class="title">Walking Through the Command-Line Options</h1></div></div></div><div class="para">
+ In normal circumstances, poptGetNextOpt parses all the options and returns –1. If your needs are simple, you can use the pointers to the variables passed in the options table, described previously. If you need some special processing for options not handled by popt, that is, options of type POPT_ARG_NONE, then poptGetNextOpt returns the single-character option.
+ </div><div class="para">
+ In this case, you can call poptGetNextOpt in a while loop. For example:
+ </div><div class="para">
+ while ((option = poptGetNextOpt(context) ) {
+ </div><div class="para">
+ /* Do something... */
+ </div><div class="para">
+ }
+ </div><div class="para">
+ Inside your while loop, you can call poptGetOptArg to get the value of the argument:
+ </div><div class="para">
+ char * poptGetOptArg(poptContext context);
+ </div><div class="para">
+ You can restart the processing of the options by calling poptResetContext:
+ </div><div class="para">
+ void poptResetContext(poptContext context);
+ </div><div class="para">
+ The popt system is just looking for arguments that start with a dash, -. In most command-line applications, you may have a number of extra arguments at the end, such as a list of file names. The popt library doesn’t process these, but can provide them to you.
+ </div><div class="para">
+ Call poptGetArg to return the next extra argument:
+ </div><div class="para">
+ char * poptGetArg(poptContext context);
+ </div><div class="para">
+ Keep calling this function until it returns NULL.
+ </div><div class="para">
+ Call poptPeekArg to look at the next argument but not mark it as being processed:
+ </div><div class="para">
+ char * poptPeekArg(poptContext context);
+ </div><div class="para">
+ Or, you can get the whole list of extra arguments by calling poptGetArgs:
+ </div><div class="para">
+ char ** poptGetArgs(poptContext context);
+ </div></div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id785286" class="title">Handling Errors</h1></div></div></div><div class="para">
+ Inside your while loop processing the command-line arguments, you can call poptBadOption to get the option that was bad, and poptStrerror to look up the error message associated with the error.
+ </div><div class="para">
+ For poptBadOption, you need to pass in the context, and a bitmask of flags. Normally, pass 0 for no flags or POPT_BADOPTION_NOALIAS, which tells popt to return the actual option, not a value defined in an alias. This makes poptBadOption return the option closest to, if not exactly the same as, what the user entered, which makes for better error reporting.
+ </div><div class="para">
+ The poptBadOption function signature follows:
+ </div><div class="para">
+ char * poptBadOption(poptContext context, int flags);
+ </div><div class="para">
+ Pass the error number returned by poptGetOptArg to poptStrerror to get the standard error message for that option:
+ </div><div class="para">
+ const char * poptStrerror(const int error_code);
+ </div><div class="para">
+ You can combine these and print out an error with code like the following:
+ </div><div class="para">
+ fprintf( stderr, "Error with option [%s]\n %s",
+ </div><div class="para">
+ poptBadOption(context, POPT_BADOPTION_NOALIAS),
+ </div><div class="para">
+ poptStrerror(error_code);
+ </div><div class="para">
+ To print out a usage message, call poptPrintUsage:
+ </div><div class="para">
+ void poptPrintUsage(poptContext context,
+ </div><div class="para">
+ FILE *output,
+ </div><div class="para">
+ int flags);
+ </div><div class="para">
+ This function prints out the usage help information, which is a useful function when the user has called a program with incomplete or wrong options.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id870911" class="title">Running a popt example</h1></div></div></div><div class="para">
+ Pulling this all together, you can use the popt1.c program, in Listing 16-3, as an example for using popt to process command-line options.
+ </div><div class="para">
+ Listing 16-3: popt1.c
+ </div><div class="para">
+ /* Processes command-line options. */
+ </div><div class="para">
+ </div><div class="para">
+ #include <stdio.h>
+ </div><div class="para">
+ #include <stdlib.h>
+ </div><div class="para">
+ </div><div class="para">
+ #include <popt.h>
+ </div><div class="para">
+ </div><div class="para">
+ /* Data values for the options. */
+ </div><div class="para">
+ static int intVal = 55;
+ </div><div class="para">
+ static int print = 0;
+ </div><div class="para">
+ </div><div class="para">
+ static char* stringVal;
+ </div><div class="para">
+ </div><div class="para">
+ </div><div class="para">
+ void callback(poptContext context,
+ </div><div class="para">
+ enum poptCallbackReason reason,
+ </div><div class="para">
+ const struct poptOption * option,
+ </div><div class="para">
+ const char * arg,
+ </div><div class="para">
+ const void * data)
+ </div><div class="para">
+ {
+ </div><div class="para">
+ switch(reason)
+ </div><div class="para">
+ {
+ </div><div class="para">
+ case POPT_CALLBACK_REASON_PRE:
+ </div><div class="para">
+ printf("\t Callback in pre setting\n"); break;
+ </div><div class="para">
+ case POPT_CALLBACK_REASON_POST:
+ </div><div class="para">
+ printf("\t Callback in post setting\n"); break;
+ </div><div class="para">
+ case POPT_CALLBACK_REASON_OPTION:
+ </div><div class="para">
+ printf("\t Callback in option setting\n"); break;
+ </div><div class="para">
+ }
+ </div><div class="para">
+ }
+ </div><div class="para">
+ </div><div class="para">
+ </div><div class="para">
+ </div><div class="para">
+ /* Set up a table of options. */
+ </div><div class="para">
+ static struct poptOption optionsTable[] = {
+ </div><div class="para">
+ { (const) "int", (char) 'i', POPT_ARG_INT, (void*) &intVal, 0,
+ </div><div class="para">
+ (const) "follow with an integer value", (const) "2, 4, 8, or 16" },
+ </div><div class="para">
+ </div><div class="para">
+ { "callback", '\0', POPT_ARG_CALLBACK|POPT_ARGFLAG_DOC_HIDDEN,
+ </div><div class="para">
+ &callback, 0, NULL, NULL },
+ </div><div class="para">
+ </div><div class="para">
+ { (const) "file", (char) 'f', POPT_ARG_STRING, (void*) &stringVal, 0,
+ </div><div class="para">
+ (const) "follow with a file name", NULL },
+ </div><div class="para">
+ </div><div class="para">
+ { (const) "print", (char) 'p', POPT_ARG_NONE, &print, 0,
+ </div><div class="para">
+ (const) "send output to the printer", NULL },
+ </div><div class="para">
+ </div><div class="para">
+ POPT_AUTOALIAS
+ </div><div class="para">
+ POPT_AUTOHELP
+ </div><div class="para">
+ POPT_TABLEEND
+ </div><div class="para">
+ };
+ </div><div class="para">
+ </div><div class="para">
+ int main(int argc, char *argv[]) {
+ </div><div class="para">
+ </div><div class="para">
+ poptContext context = poptGetContext(
+ </div><div class="para">
+ (const char*) "popt1",
+ </div><div class="para">
+ argc,
+ </div><div class="para">
+ argv,
+ </div><div class="para">
+ (const struct poptOption* ) &optionsTable,
+ </div><div class="para">
+ 0);
+ </div><div class="para">
+ </div><div class="para">
+ </div><div class="para">
+ int option = poptGetNextOpt(context);
+ </div><div class="para">
+ printf("option = %d\n", option);
+ </div><div class="para">
+ </div><div class="para">
+ /* Print out option values. */
+ </div><div class="para">
+ printf("After processing, options have values:\n");
+ </div><div class="para">
+ </div><div class="para">
+ printf("\t intVal holds %d\n", intVal);
+ </div><div class="para">
+ printf("\t print flag holds %d\n", print);
+ </div><div class="para">
+ printf("\t stringVal holds [%s]\n", stringVal);
+ </div><div class="para">
+ </div><div class="para">
+ poptFreeContext(context);
+ </div><div class="para">
+ </div><div class="para">
+ exit(0);
+ </div><div class="para">
+ }
+ </div><div class="para">
+ This example defines a callback but otherwise uses the simplest case for processing the command-line options. This program lets the popt library simply set the values into the option table. In most cases, you should avoid more complex command-line processing.
+ </div><div class="para">
+ To compile popt programs, you just need the popt library. For example:
+ </div><div class="para">
+ gcc -I/usr/include/rpm -o popt1 popt1.c -lpopt
+ </div><div class="para">
+ When you run this program, try out the different options. For example, when you set all the options, you’ll see output like the following:
+ </div><div class="para">
+ $ ./popt1 -i 42 --print -f filename1
+ </div><div class="para">
+ Callback in option setting
+ </div><div class="para">
+ Callback in option setting
+ </div><div class="para">
+ Callback in post setting
+ </div><div class="para">
+ option = -1
+ </div><div class="para">
+ After processing, options have values:
+ </div><div class="para">
+ intVal holds 42
+ </div><div class="para">
+ print flag holds 1
+ </div><div class="para">
+ stringVal holds [filename1]
+ </div><div class="para">
+ This command used two short options and one long. You can mix and match short and long options, as shown following:
+ </div><div class="para">
+ $ ./popt1 --int 42 -p --file filename1
+ </div><div class="para">
+ Callback in option setting
+ </div><div class="para">
+ Callback in option setting
+ </div><div class="para">
+ Callback in post setting
+ </div><div class="para">
+ option = -1
+ </div><div class="para">
+ After processing, options have values:
+ </div><div class="para">
+ intVal holds 42
+ </div><div class="para">
+ print flag holds 1
+ </div><div class="para">
+ stringVal holds [filename1]
+ </div><div class="para">
+ This example used a short option for print, -p, and long options for the other two options. The popt library also provides handy help and usage messages, using the option table macro POPT_AUTOALIAS. To get a help message, use --help or -?:
+ </div><div class="para">
+ $ ./popt1 --help
+ </div><div class="para">
+ Usage: popt1 [OPTION...]
+ </div><div class="para">
+ -i, --int=2, 4, 8, or 16 follow with an integer value
+ </div><div class="para">
+ -f, --file=STRING follow with a file name
+ </div><div class="para">
+ -p, --print send output to the printer
+ </div><div class="para">
+ </div><div class="para">
+ Options implemented via popt alias/exec:
+ </div><div class="para">
+ </div><div class="para">
+ Help options:
+ </div><div class="para">
+ -?, --help Show this help message
+ </div><div class="para">
+ --usage Display brief usage message
+ </div><div class="para">
+ Notice how the help descriptions from the options table are used.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ With some shells, especially the tcsh shell, you need to wrap a -? In single quotes. For example:
+ </div><div class="para">
+ $ ./popt1 '-?'
+ </div><div class="para">
+ The usage message is shorter, and you also get it for free:
+ </div><div class="para">
+ $ ./popt1 --usage
+ </div><div class="para">
+ Usage: popt1 [-i|--int 2, 4, 8, or 16] [-f|--file STRING] [-p|--print]
+ </div><div class="para">
+ [-?|--help] [--usage]
+ </div><div class="para">
+ All in all, the popt library provides a handy library for processing command-line options and aliases, covered in <a class="xref" href="#ch-customizing-rpm">Cap. 20, <em>Customizing RPM Behavior</em></a>.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id853423" class="title">Handling rpm command-line options</h1></div></div></div><div class="para">
+ The RPM C library makes extensive use of popt for processing command-line arguments. Functions that set up the RPM library, such as rpmcliInit, which sets up the RPM command-line environment, require a table of poptOption entries that define the command-line options for your program.
+ </div><div class="para">
+ To create a simple program that handles the standard rpm command-line options, set up the following options table:
+ </div><div class="para">
+ static struct poptOption optionsTable[] = {
+ </div><div class="para">
+ </div><div class="para">
+ { NULL, '\0', POPT_ARG_INCLUDE_TABLE, rpmcliAllPoptTable, 0,
+ </div><div class="para">
+ "Common options for all rpm modes and executables:",
+ </div><div class="para">
+ NULL },
+ </div><div class="para">
+ </div><div class="para">
+ POPT_AUTOALIAS
+ </div><div class="para">
+ POPT_AUTOHELP
+ </div><div class="para">
+ POPT_TABLEEND
+ </div><div class="para">
+ };
+ </div><div class="para">
+ Then, initialize your program with a call to rpmcliInit:
+ </div><div class="para">
+ poptContext rpmcliInit(int argc, char *const argv[],
+ </div><div class="para">
+ struct poptOption * optionsTable);
+ </div><div class="para">
+ When you call rpmcliInit, it will set up all the variables for the standard rpm command-line options.
+ </div><div class="para">
+ For example, to see if the verbose flag is turned on, call rpmIsVerbose:
+ </div><div class="para">
+ int rpmIsVerbose();
+ </div><div class="para">
+ When you are done with a program that called rpmcliInit, call rpmcliFini to clean up the global data:
+ </div><div class="para">
+ poptContext rpmcliFini(poptContext context);
+ </div><div class="para">
+ The call to rpmcliFini returns NULL.
+ </div></div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id784404" class="title">Working with RPM Files</h1></div></div></div><div class="para">
+ The RPM C library provides functions to read RPM files as well as query the RPM database. Going beyond querying, you can perform all the tasks that the rpm and rpmbuild commands do, since both these commands are written in C using the RPM library. That said, some tasks are much easier than other tasks. If you are writing a complex package installation program, or a program that keeps various systems up to date with regards to package versions, you may want to look at the Python RPM API instead of the C RPM library.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ <a class="xref" href="#ch-rpm-programming-python">Cap. 16, <em>Programming RPM with Python</em></a> covers the Python RPM API.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id791650" class="title">Opening RPM files</h1></div></div></div><div class="para">
+ When working with an RPM file from within a program, the first thing you need to do is open the file. Use Fopen:
+ </div><div class="para">
+ FD_t Fopen(const char * path,
+ </div><div class="para">
+ const char * fmode);
+ </div><div class="para">
+ Fopen works like the standard C function fopen(3).
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ The reason the RPM library wraps the input/output C library functions is to ensure portability to other operating systems. This is a fairly common technique.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id673138" class="title">Reading the RPM lead and signature</h1></div></div></div><div class="para">
+ Once you have opened an RPM file, you can start to read header information, which is the most interesting information to most RPM programs. (You may also want to read the files in the RPM payload, for example.) Before you can start reading the header, though, you must read forward in the RPM file past the lead and signature.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ <a class="xref" href="#ch-rpm-overview">Cap. 2, <em>RPM Overview</em></a> introduces the lead and signature.
+ </div><div class="para">
+ Even if your programs don’t want to examine the lead or signature, you must read past to position the file offset properly for reading the header information. To read past the lead, call readLead:
+ </div><div class="para">
+ int readLead(FD_t fd, struct rpmlead *lead);
+ </div><div class="para">
+ The readLead function returns 0 on success or 1 on an error. It fills in an rpmlead struct:
+ </div><div class="para">
+ struct rpmlead {
+ </div><div class="para">
+ unsigned char magic[4];
+ </div><div class="para">
+ unsigned char major;
+ </div><div class="para">
+ unsigned char minor;
+ </div><div class="para">
+ short type;
+ </div><div class="para">
+ short archnum;
+ </div><div class="para">
+ char name[66];
+ </div><div class="para">
+ short osnum;
+ </div><div class="para">
+ short signature_type;
+ </div><div class="para">
+ char reserved[16];
+ </div><div class="para">
+ };
+ </div><div class="para">
+ To read past the signature, call rpmReadSignature:
+ </div><div class="para">
+ rpmRC rpmReadSignature(FD_t fd,
+ </div><div class="para">
+ Header * header,
+ </div><div class="para">
+ sigType sig_type);
+ </div><div class="para">
+ The return code is one of the values listed in Table 16-8.
+ </div><div class="para">
+ Table 16-8 Return codes from rpmReadSignature
+ </div><div class="informaltable"><table border="1"><colgroup><col width="100%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Code
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMRC_OK
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMRC_BADMAGIC
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMRC_FAIL
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMRC_BADSIZE
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMRC_SHORTREAD
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ You can do more with the signature than merely reading past it, of course. Look in the online RPM documentation for more on verifying signatures.
+ </div><div class="para">
+ After reading the signature, you can start to read the general header entries.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id865045" class="title">Reading header information</h1></div></div></div><div class="para">
+ The header information includes the package name, version, pre- and post-installation scripts, and so on. To read in the RPM header, call headerRead. If successful, headerRead returns a Header object. You can then read data values from the Header.
+ </div><div class="para">
+ Header headerRead(FD_t fd,
+ </div><div class="para">
+ enum hMagic magicp);
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ When working with the RPM database, you will also use Header objects.
+ </div><div class="para">
+ The trickiest thing about calling headerRead is that you must pass a special magic number flag. This value must be HEADER_MAGIC_YES if the header has a set of magic numbers, and HEADER_MAGIC_NO if not. If you guess incorrectly, headerRead will return an error. To get around, this, you can compare the major number in the lead. For example:
+ </div><div class="para">
+ Header header = headerRead(fd, (lead.major >= 3) ?
+ </div><div class="para">
+ HEADER_MAGIC_YES : HEADER_MAGIC_NO);
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ This snippet is one of the gems you'll find when you browse the RPM source code. Use the source.
+ </div><div class="para">
+ To read values from the Header, call headerGetEntry. To call headerGetEntry, you pass in a Header and a tag ID. You get back the type of the tag, a pointer to the tag values, and a count of the number of values stored under this tag.
+ </div><div class="para">
+ int headerGetEntry(Header header,
+ </div><div class="para">
+ int_32 tag,
+ </div><div class="para">
+ hTYP_t type,
+ </div><div class="para">
+ void **pointer,
+ </div><div class="para">
+ hCNT_t data_size);
+ </div><div class="para">
+ The call to headerGetEntry returns a 1 on success, or a 0 on failure. On success, the pointer will point at the retrieved data, with the type parameter set to one of the following enum values:
+ </div><div class="para">
+ enum rpmTagType_e {
+ </div><div class="para">
+ RPM_NULL_TYPE = 0,
+ </div><div class="para">
+ RPM_CHAR_TYPE = 1,
+ </div><div class="para">
+ RPM_INT8_TYPE = 2,
+ </div><div class="para">
+ RPM_INT16_TYPE = 3,
+ </div><div class="para">
+ RPM_INT32_TYPE = 4,
+ </div><div class="para">
+ RPM_STRING_TYPE = 6,
+ </div><div class="para">
+ RPM_BIN_TYPE = 7,
+ </div><div class="para">
+ RPM_STRING_ARRAY_TYPE = 8,
+ </div><div class="para">
+ RPM_I18NSTRING_TYPE
+ </div><div class="para">
+ }
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ If the type is RPM_STRING_ARRAY_TYPE or RPM_BIN_TYPE, you must free the pointer. Call headerFreeData to free the data:
+ </div><div class="para">
+ void* headerFreeData(const void *pointer,
+ </div><div class="para">
+ rpmTagType type);
+ </div><div class="para">
+ You need to pass in the data pointer and the type flag. You can safely call headerFreeData for all types. The function will do nothing if the type is not set up to require freeing.
+ </div><div class="para">
+ When you call headerGetEntry, you must identify the tag you want from the header. This tag is an identifier for the --queryformat tags introduced in <a class="xref" href="#ch-using-rpm-db">Cap. 4, <em>Using the RPM Database</em></a> . The file rpmlib.h lists the various tags, such as RPMTAG_NAME, RPMTAG_VERSION, and RPMTAG_RELEASE.
+ </div><div class="para">
+ The following function shows how to read a string entry from a Header:
+ </div><div class="para">
+ /* Function to read a string header entry. */
+ </div><div class="para">
+ char* readHeaderString(Header header, int_32 tag_id) {
+ </div><div class="para">
+ </div><div class="para">
+ int_32 type;
+ </div><div class="para">
+ void* pointer;
+ </div><div class="para">
+ int_32 data_size;
+ </div><div class="para">
+ </div><div class="para">
+ int header_status = headerGetEntry(header,
+ </div><div class="para">
+ tag_id,
+ </div><div class="para">
+ &type,
+ </div><div class="para">
+ &pointer,
+ </div><div class="para">
+ &data_size);
+ </div><div class="para">
+ </div><div class="para">
+ if (header_status) {
+ </div><div class="para">
+ </div><div class="para">
+ if (type == RPM_STRING_TYPE) {
+ </div><div class="para">
+ return pointer;
+ </div><div class="para">
+ }
+ </div><div class="para">
+ }
+ </div><div class="para">
+ </div><div class="para">
+ return NULL;
+ </div><div class="para">
+ }
+ </div><div class="para">
+ Pass the Header object and the ID of the tag to read. For example:
+ </div><div class="para">
+ char* name = readHeaderString(header, RPMTAG_NAME);
+ </div><div class="para">
+ char* version = readHeaderString(header, RPMTAG_VERSION);
+ </div><div class="para">
+ char* release = readHeaderString(header, RPMTAG_RELEASE);
+ </div><div class="para">
+ To just get the name, version, and release number, you can call the utility function headerNVR, which has the following function signature:
+ </div><div class="para">
+ int headerNVR(Header header,
+ </div><div class="para">
+ const char **nameptr,
+ </div><div class="para">
+ const char **versionptr,
+ </div><div class="para">
+ const char **releaseptr);
+ </div><div class="para">
+ When you are through with a header, free it by calling headerFree:
+ </div><div class="para">
+ Header headerFree(Header header);
+ </div><div class="para">
+ The call to headerFree returns NULL, so you can use the call to set the original pointer to to NULL to prevent accidental reuse. For example:
+ </div><div class="para">
+ header = headerFree(header);
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id678698" class="title">A shortcut to header information</h1></div></div></div><div class="para">
+ You can read in a Header using the shortcut utility method rpmReadPackageFile:
+ </div><div class="para">
+ int rpmReadPackageFile(rpmts ts,
+ </div><div class="para">
+ FD_t fd,
+ </div><div class="para">
+ const char *filename,
+ </div><div class="para">
+ Header *header);
+ </div><div class="para">
+ You need to pass a transaction set to rpmReadPackageFile and an open file. The filename is just used for reporting errors. On success, rpmReadPackageFile fills in a Header object from the package file. The return value is 0 for success.
+ </div><div class="para">
+ To get the necessary transaction set, you need to create one with rpmtsCreate, covered in the "Programming with the RPM Database" section, following.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ In most cases, you should call rpmReadPackageFile in place of readLead, rpmReadSignature, and headerRead, since rpmReadPackageFile also verifies the package integrity.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id676439" class="title">Closing RPM files</h1></div></div></div><div class="para">
+ When you’re done with an RPM file, close it with Fclose:
+ </div><div class="para">
+ int Fclose(FD_t fd);
+ </div><div class="para">
+ Fclose acts much like the standard C function fclose(3). The FD_t is an RPM data type that is very similar to a FILE pointer.
+ </div><div class="para">
+ The RPM I/O subsystem, defined with rpmio.h, includes functions that mimic (and in most cases wrap) the ANSI C stdio functions. These include: Fopen, Fclose, Fread, Fwrite, Ferror, Fflush, Fileno, and Fseek.
+ </div><div class="para">
+ These functions wrap the ANSI C stdio functions to add new features. The Fopen function, for example, supports HTTP or FTP URLs in the place of a file name, so long as you append ".ufdio" to the mode.
+ </div></div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id569976" class="title">Programming with the RPM Database</h1></div></div></div><div class="para">
+ Many functions in rpmlib require a transaction set. In particular, accessing the rpm database is quite easy using a transaction set.
+ </div><div class="para">
+ Create a transaction set by calling rpmtsCreate:
+ </div><div class="para">
+ rpmts rpmtsCreate(void);
+ </div><div class="para">
+ RPM uses transaction sets to bracket operations on the RPM database. As the RPM API evolves, transaction sets will become more and more important. Transaction sets also help in that the RPM library will automatically open the RPM database as needed.
+ </div><div class="para">
+ When you are done with a transaction set, call rpmtsFree:
+ </div><div class="para">
+ rpmts rpmtsFree(rpmts ts);
+ </div><div class="para">
+ The call to rpmtsFree returns NULL.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id808107" class="title">Database iterators</h1></div></div></div><div class="para">
+ Once you have a transaction set, you can iterate over the installed packages in the RPM database by creating an iterator. To do this, call rpmtsInitIterator:
+ </div><div class="para">
+ rpmdbMatchIterator rpmtsInitIterator(const rpmts ts,
+ </div><div class="para">
+ rpmTag rpmtag,
+ </div><div class="para">
+ const void *keypointer,
+ </div><div class="para">
+ size_t keylen);
+ </div><div class="para">
+ You need to specify which tag to iterate by, which in most cases will be the package name, RPMTAG_NAME, introduced previously With the RPMTAG_NAME tag, you need to pass the name of a package to look for in the keypointer parameter. (The keypointer varies based on the tag you pass.)
+ </div><div class="para">
+ For string data, you can pass 0 for the keylen parameter. For example, this call to rpmtsInitIterator looks for all packages named sendmail.
+ </div><div class="para">
+ rpmdbMatchIterator iter;
+ </div><div class="para">
+ iter = rpmtsInitIterator(ts, RPMTAG_NAME, "sendmail", 0);
+ </div><div class="para">
+ The rpmdbMatchIterator allows you to iterate through a number of packages, in this case, all the packages that match a given name. After calling rpmtsInitIterator, the next step is to call rpmdbNextIterator:
+ </div><div class="para">
+ Header rpmdbNextIterator(rpmdbMatchIterator iter);
+ </div><div class="para">
+ This function returns the next package Header object in the iterator. The Header will be NULL if there are no more packages in the iterator.
+ </div><div class="para">
+ If the Header is not NULL, you can get entries from it, as shown previously. You can use a while loop to go through all the matching packages. For example:
+ </div><div class="para">
+ while ( (installed_header = rpmdbNextIterator(iter) ) != NULL) {
+ </div><div class="para">
+ /* Do something... */
+ </div><div class="para">
+ }
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ In future versions of the RPM library, rpmtsNextIterator, will replace rpmdbNextIterator.
+ </div><div class="para">
+ You do not need to free the Header returned by rpmdbNextIterator. Also, the next call to rpmdbNextIterator will reset the Header.
+ </div><div class="para">
+ You can customize how an iterator works by adding a pattern to the iterator with rpmdbSetIteratorRE:
+ </div><div class="para">
+ int rpmdbSetIteratorRE(rpmdbMatchIterator iter,
+ </div><div class="para">
+ rpmTag tag,
+ </div><div class="para">
+ rpmMireMode mode,
+ </div><div class="para">
+ const char * pattern);
+ </div><div class="para">
+ Calling rpmdbSetIteratorRE modifies the passed-in iterator to use the given pattern as a further test on the given tag. The mode parameter names the type of pattern used, which can be one of those listed in Table 16-9.
+ </div><div class="para">
+ Table 16-9 Types of patterns for rpmdbSetIteratorRE
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Type
+ </div>
+
+ </td><td>
+ <div class="para">
+ Meaning
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMMIRE_DEFAULT
+ </div>
+
+ </td><td>
+ <div class="para">
+ Same as regular expressions but with \., .*, and ^..$ added.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMMIRE_GLOB
+ </div>
+
+ </td><td>
+ <div class="para">
+ Glob-style patterns using fnmatch.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMMIRE_REGEX
+ </div>
+
+ </td><td>
+ <div class="para">
+ Regular expressions using regcomp.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMMIRE_STRCMP
+ </div>
+
+ </td><td>
+ <div class="para">
+ String comparisons using strcmp.
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ For more on these patterns, see the online manual pages for fnmatch(3), glob(7), regcomp(3), regex(7), and strcmp(3).
+ </div><div class="para">
+ Free the iterator when done with rpmdbFreeIterator:
+ </div><div class="para">
+ rpmdbMatchIterator rpmdbFreeIterator(rpmdbMatchIterator iter);
+ </div><div class="para">
+ The call to rpmdbFreeIterator returns NULL.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id749729" class="title">Dependency Sets</h1></div></div></div><div class="para">
+ To compare package versions, create a dependency set. The rpm command, for example, uses dependency sets to compare package versions.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ You could compare the version numbers directly, calling headerGetEntry to get the version and release tags, converting these strings to numbers and then comparing, but this would cause problems. The custom comparison is not as exact as the code in this section, especially since many packages have version numbers that are not true numbers, such as 1.12.4, with one too many decimal points. This makes the comparisons harder. In addition, there is more than just the version number to take into account. You need to deal with the Epoch value, as well as the release, too.
+ </div><div class="para">
+ To handle all the complicated logic of comparing versions, you can use the code in this section, or call rpmvercmp. Do not try to compare version numbers with custom code.
+ </div><div class="para">
+ To create a dependency set for a given package Header, call rpmdsThis. Calling rpmdsThis creates a dependency set that holds a triple of the package name, the Epoch/Version/Release information, and the flags.
+ </div><div class="para">
+ rpmds rpmdsThis(Header header,
+ </div><div class="para">
+ rpmTag tagID,
+ </div><div class="para">
+ int_32 Flags);
+ </div><div class="para">
+ For comparing packages, you can pass RPMTAG_REQUIRENAME for the tagID. The actual tagID here is ignored for the version check. What you do need, though, are flags to check whether another package is less than or equal to the Epoch/Version/Release information in this dependency set. For this task, pass the following bit flags:
+ </div><div class="para">
+ (RPMSENSE_EQUAL|RPMSENSE_LESS)
+ </div><div class="para">
+ Once you have a dependency set, you can use the handy function rpmdsNVRMatchesDep to compare the NVR, or Name, Version, Release entries in the header of one package against the data in the dependency set.
+ </div><div class="para">
+ int rpmdsNVRMatchesDep(const Header header,
+ </div><div class="para">
+ const rpmds dependency_set,
+ </div><div class="para">
+ int nopromote);
+ </div><div class="para">
+ After checking the dependencies, rpmdsNVRMatchesDep returns 1 if the dependency overlaps, or 0 otherwise. In terms of comparing packages, 1 means that the package file is as old or older than the installed package, and 0 means that the package already installed is newer. Pass 1 to prevent promoting the Epoch value in the packages during the comparison.
+ </div><div class="para">
+ The actual comparison is controlled by the call that creates the dependency set, especially the flags. Thus, passing flags of (RPMSENSE_EQUAL|RPMSENSE_LESS) to rpmdsThis set up the test as a less than or equal test.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ The RPM C API documentation marks rpmdsNVRMatchesDep as deprecated, to be replaced in the future.
+ </div><div class="para">
+ You can also call rpmVersionCompare to compare the versions of two packages:
+ </div><div class="para">
+ int rpmVersionCompare(Header header1, Header header2);
+ </div><div class="para">
+ The return value is -1 if the header1 represents an older version than header2, 0 if the two headers represent the same version, and 1 if header1 represents a newer version than header2.
+ </div><div class="para">
+ To get the name of the package from a dependency set, call rpmdsN:
+ </div><div class="para">
+ const char* rpmdsN(const rpmds dependency_set);
+ </div><div class="para">
+ You can use rpmdsN to get the name when calling rpmtsInitIterator if you are working with dependency sets when searching the RPM database.
+ </div><div class="para">
+ Free a dependency set when done by calling rpmdsFree:
+ </div><div class="para">
+ rpmds rpmdsFree(rpmds dependency_set);
+ </div><div class="para">
+ As with other free functions, rpmdsFree returns NULL.
+ </div></div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id659876" class="title">Comparing an RPM File to an Installed Package</h1></div></div></div><div class="para">
+ You can pull together the RPM file and database discussions, shown previously, to create a number of RPM programs. A useful utility that shows the RPM C library compares a package file against installed packages, reporting whether the package in the RPM file represents a newer or older package than what was already installed.
+ </div><div class="para">
+ Listing 16-4 shows such a program.
+ </div><div class="para">
+ Listing 16-4: vercompare.c
+ </div><div class="para">
+ /* Compares a package file with an installed package,
+ </div><div class="para">
+ telling which one is newer.
+ </div><div class="para">
+ </div><div class="para">
+ Usage:
+ </div><div class="para">
+ vercompare pkg_files+
+ </div><div class="para">
+ </div><div class="para">
+ Compile as
+ </div><div class="para">
+ cc -I/usr/include/rpm -o vercompare vercompare.c -lrpm -lrpmdb -lrpmio -lpopt
+ </div><div class="para">
+ </div><div class="para">
+ */
+ </div><div class="para">
+ #include <stdlib.h>
+ </div><div class="para">
+ </div><div class="para">
+ #include <rpmcli.h>
+ </div><div class="para">
+ #include <rpmdb.h>
+ </div><div class="para">
+ #include <rpmds.h>
+ </div><div class="para">
+ #include <rpmts.h>
+ </div><div class="para">
+ </div><div class="para">
+ /* Set up a table of options using standard RPM options. */
+ </div><div class="para">
+ static struct poptOption optionsTable[] = {
+ </div><div class="para">
+ </div><div class="para">
+ { NULL, '\0', POPT_ARG_INCLUDE_TABLE, rpmcliAllPoptTable, 0,
+ </div><div class="para">
+ "Common options for all rpm modes and executables:",
+ </div><div class="para">
+ NULL },
+ </div><div class="para">
+ </div><div class="para">
+ POPT_AUTOALIAS
+ </div><div class="para">
+ POPT_AUTOHELP
+ </div><div class="para">
+ POPT_TABLEEND
+ </div><div class="para">
+ };
+ </div><div class="para">
+ </div><div class="para">
+ int main(int argc, char * argv[])
+ </div><div class="para">
+ {
+ </div><div class="para">
+ poptContext context;
+ </div><div class="para">
+ const char ** fnp;
+ </div><div class="para">
+ rpmdbMatchIterator iter;
+ </div><div class="para">
+ Header file_header, installed_header;
+ </div><div class="para">
+ rpmts ts;
+ </div><div class="para">
+ rpmds dependency_set;
+ </div><div class="para">
+ FD_t fd;
+ </div><div class="para">
+ rpmRC rpmrc;
+ </div><div class="para">
+ int rc;
+ </div><div class="para">
+ </div><div class="para">
+ context = rpmcliInit(argc, argv, optionsTable);
+ </div><div class="para">
+ if (context == NULL) {
+ </div><div class="para">
+ exit(EXIT_FAILURE);
+ </div><div class="para">
+ }
+ </div><div class="para">
+ </div><div class="para">
+ ts = rpmtsCreate();
+ </div><div class="para">
+ </div><div class="para">
+ </div><div class="para">
+ for (fnp = poptGetArgs(context); fnp && *fnp; fnp++) {
+ </div><div class="para">
+ </div><div class="para">
+ /* Read package header, continuing to next arg on failure. */
+ </div><div class="para">
+ fd = Fopen(*fnp, "r.ufdio");
+ </div><div class="para">
+ </div><div class="para">
+ if (fd == NULL || Ferror(fd)) {
+ </div><div class="para">
+ rpmError(RPMERR_OPEN, "open of %s failed: %s\n", *fnp,
+ </div><div class="para">
+ Fstrerror(fd));
+ </div><div class="para">
+ if (fd) {
+ </div><div class="para">
+ Fclose(fd);
+ </div><div class="para">
+ }
+ </div><div class="para">
+ </div><div class="para">
+ continue;
+ </div><div class="para">
+ }
+ </div><div class="para">
+ </div><div class="para">
+ rpmrc = rpmReadPackageFile(ts, fd, *fnp, &file_header);
+ </div><div class="para">
+ Fclose(fd);
+ </div><div class="para">
+ </div><div class="para">
+ if (rpmrc != RPMRC_OK) {
+ </div><div class="para">
+ rpmError(RPMERR_OPEN, "%s cannot be read\n", *fnp);
+ </div><div class="para">
+ continue;
+ </div><div class="para">
+ }
+ </div><div class="para">
+ </div><div class="para">
+ /* Generate "name <= epoch:version-release" depset for package */
+ </div><div class="para">
+ dependency_set = rpmdsThis(file_header, RPMTAG_REQUIRENAME,
+ </div><div class="para">
+ (RPMSENSE_EQUAL|RPMSENSE_LESS));
+ </div><div class="para">
+ </div><div class="para">
+ rc = -1; /* assume no package is installed. */
+ </div><div class="para">
+ </div><div class="para">
+ /* Search all installed packages with same name. */
+ </div><div class="para">
+ iter = rpmtsInitIterator(ts, RPMTAG_NAME, rpmdsN(dependency_set), 0);
+ </div><div class="para">
+ </div><div class="para">
+ while ((installed_header = rpmdbNextIterator(iter)) != NULL) {
+ </div><div class="para">
+ </div><div class="para">
+ /* Is the installed package newer than the file? */
+ </div><div class="para">
+ rc = rpmdsNVRMatchesDep(installed_header, dependency_set, 1);
+ </div><div class="para">
+ </div><div class="para">
+ switch (rc) {
+ </div><div class="para">
+ case 1:
+ </div><div class="para">
+ if ( rpmIsVerbose() )
+ </div><div class="para">
+ fprintf(stderr, "installed package is older (or same) as %s\n",
+ </div><div class="para">
+ *fnp);
+ </div><div class="para">
+ break;
+ </div><div class="para">
+ case 0:
+ </div><div class="para">
+ if ( rpmIsVerbose() )
+ </div><div class="para">
+ fprintf(stderr, "installed package is newer than %s\n",
+ </div><div class="para">
+ *fnp);
+ </div><div class="para">
+ break;
+ </div><div class="para">
+ }
+ </div><div class="para">
+ }
+ </div><div class="para">
+ </div><div class="para">
+ </div><div class="para">
+ /* Clean up. */
+ </div><div class="para">
+ iter = rpmdbFreeIterator(iter);
+ </div><div class="para">
+ </div><div class="para">
+ dependency_set = rpmdsFree(dependency_set);
+ </div><div class="para">
+ </div><div class="para">
+ if (rc < 0 && rpmIsVerbose() )
+ </div><div class="para">
+ fprintf(stderr, "no package is installed %s\n", *fnp);
+ </div><div class="para">
+ }
+ </div><div class="para">
+ </div><div class="para">
+ ts = rpmtsFree(ts);
+ </div><div class="para">
+ context = rpmcliFini(context);
+ </div><div class="para">
+ </div><div class="para">
+ return rc;
+ </div><div class="para">
+ </div><div class="para">
+ }
+ </div><div class="para">
+ The vercompare.c program shows reading in RPM package files as well as querying the RPM database. It introduces transaction sets, used extensively in the RPM API, and also dependency sets. You can use this program as a guide for making your own RPM programs.
+ </div><div class="para">
+ When you run the vercompare.c program, pass the names of one or more RPM files. The vercompare.c program will extract the package name from the files, and then query the RPM database for matching packages. For each matching package, vercompare.c checks whether the installed package is newer than the RPM file, or at the same version or older. For example, if you have installed version 1.17-1 of the jikes package (a Java compiler), you can compare the installed version against RPM files. If you have a package that has a newer version, you should see output like the following:
+ </div><div class="para">
+ $ ./vercompare -v jikes-1.18-1.i386.rpm
+ </div><div class="para">
+ installed package is older (or same) as jikes-1.18-1.i386.rpm
+ </div><div class="para">
+ Note that the output is relative to the installed package.
+ </div><div class="para">
+ If you compare against a file that has an older version of the package, you will see results like the following:
+ </div><div class="para">
+ $ ./vercompare -v jikes-1.14-1-glibc-2.2.i386.rpm
+ </div><div class="para">
+ installed package is newer than jikes-1.14-1-glibc-2.2.i386.rpm
+ </div><div class="para">
+ And, if you compare to an RPM file that holds the same package, you will see output as follows:
+ </div><div class="para">
+ $ ./vercompare -v jikes-1.17-glibc2.2-1.i386.rpm
+ </div><div class="para">
+ installed package is older (or same) as jikes-1.17-glibc2.2-1.i386.rpm
+ </div><div class="para">
+ You can change this aspect of the test by changing the flags passed to rpmdsThis.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ The vercompare.c program prints out nothing unless there is an error. Instead, it sets the program exit status based on the package version comparison. You can use this with automated tools, such as make, that check the exit status.
+ </div><div class="para">
+ If you want output from the program, pass the –v, verbose, option to the command, as shown in the previous examples.
+ </div><div class="para">
+ The RPM cli or command-line interface functions, such as rpmcliInit, are based on the command-line options expected by the rpm and rpmbuild commands. You can use these functions to provide a high level of abstraction onto the RPM system. For example, to run the query options just like the rpm command, call rpmcliQuery.
+ </div><div class="para">
+ int rpmcliQuery(rpmts transaction_set,
+ </div><div class="para">
+ QVA_t qva,
+ </div><div class="para">
+ const char **argv);
+ </div><div class="para">
+ Set the QVA_t variable to point at the global variable rpmQVKArgs, which is set up from the global option table for the query mode, rpmQueryPoptTable. Pass rpmcliQuery a set of file names or package names. You can get these names in the given format by calling poptGetArgs, introduced previously.
+ </div><div class="para">
+ To support the query options, you need the rpm query entries in your poptOption table. To get these options, add the following entry:
+ </div><div class="para">
+ { NULL, '\0', POPT_ARG_INCLUDE_TABLE, rpmQueryPoptTable, 0,
+ </div><div class="para">
+ "Query options (with -q or --query):",
+ </div><div class="para">
+ NULL },
+ </div><div class="para">
+ With the rpmQueryPoptTable options, you can make a program that works like the rpm --query command using just the following code:
+ </div><div class="para">
+ poptContext context;
+ </div><div class="para">
+ QVA_t qva = &rpmQVKArgs;
+ </div><div class="para">
+ rpmts ts;
+ </div><div class="para">
+ int ec;
+ </div><div class="para">
+ </div><div class="para">
+ </div><div class="para">
+ context = rpmcliInit(argc, argv, optionsTable);
+ </div><div class="para">
+ if (context == NULL) {
+ </div><div class="para">
+ /* Display error and exit... */
+ </div><div class="para">
+ }
+ </div><div class="para">
+ </div><div class="para">
+ ts = rpmtsCreate();
+ </div><div class="para">
+ </div><div class="para">
+ if (qva->qva_mode == 'q') {
+ </div><div class="para">
+ /* Make sure there's something to do. */
+ </div><div class="para">
+ if (qva->qva_source != RPMQV_ALL && !poptPeekArg(context)) {
+ </div><div class="para">
+ fprintf(stderr, "no arguments given for --query");
+ </div><div class="para">
+ exit(EXIT_FAILURE);
+ </div><div class="para">
+ }
+ </div><div class="para">
+ </div><div class="para">
+ ec = rpmcliQuery(ts, qva, (const char **) poptGetArgs(context));
+ </div><div class="para">
+ }
+ </div><div class="para">
+ </div><div class="para">
+ ts = rpmtsFree(ts);
+ </div><div class="para">
+ </div><div class="para">
+ context = rpmcliFini(context);
+ </div><div class="para">
+ This code supports all the query options just like the rpm command. That's both good and bad. If you wanted everything exactly like the rpm command, chances are you could use the rpm command as is. But if you need to add RPM query support into your programs, this is probably the easiest way to do it.
+ </div><div class="para">
+ With a small additional set of code, you can add support for all the --verify options to your program. You need to include the --verify command-line option definitions, which come from the global rpmVerifyPoptTable table:
+ </div><div class="para">
+ /* Add in --verify options. */
+ </div><div class="para">
+ { NULL, '\0', POPT_ARG_INCLUDE_TABLE, rpmVerifyPoptTable, 0,
+ </div><div class="para">
+ "Verify options (with -V or --verify):",
+ </div><div class="para">
+ NULL },
+ </div><div class="para">
+ You can then check for the verify mode, and support the options, with code like the following:
+ </div><div class="para">
+ if (qva->qva_mode == 'V') {
+ </div><div class="para">
+ rpmVerifyFlags verifyFlags = VERIFY_ALL;
+ </div><div class="para">
+ </div><div class="para">
+ /* Verify flags are negated from query flags. */
+ </div><div class="para">
+ verifyFlags &= ~qva->qva_flags;
+ </div><div class="para">
+ qva->qva_flags = (rpmQueryFlags) verifyFlags;
+ </div><div class="para">
+ </div><div class="para">
+ /* Make sure there's something to do. */
+ </div><div class="para">
+ if (qva->qva_source != RPMQV_ALL && !poptPeekArg(context)) {
+ </div><div class="para">
+ fprintf(stderr, "no arguments given for --verify");
+ </div><div class="para">
+ exit(EXIT_FAILURE);
+ </div><div class="para">
+ }
+ </div><div class="para">
+ </div><div class="para">
+ ec = rpmcliVerify(ts, qva, (const char **)
+ </div><div class="para">
+ poptGetArgs(context));
+ </div><div class="para">
+ }
+ </div><div class="para">
+ The workhorse function in this code is rpmcliVerify, a high-level function that performs all the --verify work done by the rpm command.
+ </div><div class="para">
+ int rpmcliVerify(rpmts transaction_set,
+ </div><div class="para">
+ QVA_t qva,
+ </div><div class="para">
+ const char **argv);
+ </div><div class="para">
+ Again, set the QVA_t variable to point at the global variable rpmQVKArgs, which is set up from the global option table for the query mode, rpmQueryPoptTable.
+ </div><div class="para">
+ Putting this all together, Listing 16-5 shows a program that performs the same as the rpm command for the --query and --verify options.
+ </div><div class="para">
+ Listing 16-5: rpmq.c
+ </div><div class="para">
+ /*
+ </div><div class="para">
+ rpm --query and --verify modes in standalone program.
+ </div><div class="para">
+ </div><div class="para">
+ Compile as
+ </div><div class="para">
+ cc -I/usr/include/rpm -o rpmq rpmq.c -lrpm -lrpmdb -lrpmio -lpopt
+ </div><div class="para">
+ </div><div class="para">
+ See option usage by invoking
+ </div><div class="para">
+ ./rpmq --help
+ </div><div class="para">
+ */
+ </div><div class="para">
+ #include <stdlib.h>
+ </div><div class="para">
+ </div><div class="para">
+ #include <rpmcli.h>
+ </div><div class="para">
+ #include <rpmdb.h>
+ </div><div class="para">
+ #include <rpmds.h>
+ </div><div class="para">
+ #include <rpmts.h>
+ </div><div class="para">
+ </div><div class="para">
+ /* Set up a table of options. */
+ </div><div class="para">
+ static struct poptOption optionsTable[] = {
+ </div><div class="para">
+ </div><div class="para">
+ { NULL, '\0', POPT_ARG_INCLUDE_TABLE, rpmcliAllPoptTable, 0,
+ </div><div class="para">
+ "Common options for all rpm modes and executables:",
+ </div><div class="para">
+ NULL },
+ </div><div class="para">
+ </div><div class="para">
+ { NULL, '\0', POPT_ARG_INCLUDE_TABLE, rpmQueryPoptTable, 0,
+ </div><div class="para">
+ "Query options (with -q or --query):",
+ </div><div class="para">
+ NULL },
+ </div><div class="para">
+ </div><div class="para">
+ /* Add in --verify options. */
+ </div><div class="para">
+ { NULL, '\0', POPT_ARG_INCLUDE_TABLE, rpmVerifyPoptTable, 0,
+ </div><div class="para">
+ "Verify options (with -V or --verify):",
+ </div><div class="para">
+ NULL },
+ </div><div class="para">
+ </div><div class="para">
+ POPT_AUTOALIAS
+ </div><div class="para">
+ POPT_AUTOHELP
+ </div><div class="para">
+ POPT_TABLEEND
+ </div><div class="para">
+ };
+ </div><div class="para">
+ </div><div class="para">
+ </div><div class="para">
+ int main(int argc, char * argv[])
+ </div><div class="para">
+ {
+ </div><div class="para">
+ poptContext context;
+ </div><div class="para">
+ QVA_t qva = &rpmQVKArgs;
+ </div><div class="para">
+ rpmts ts;
+ </div><div class="para">
+ int ec;
+ </div><div class="para">
+ </div><div class="para">
+ </div><div class="para">
+ context = rpmcliInit(argc, argv, optionsTable);
+ </div><div class="para">
+ if (context == NULL) {
+ </div><div class="para">
+ poptPrintUsage(context, stderr, 0);
+ </div><div class="para">
+ exit(EXIT_FAILURE);
+ </div><div class="para">
+ }
+ </div><div class="para">
+ </div><div class="para">
+ ts = rpmtsCreate();
+ </div><div class="para">
+ </div><div class="para">
+ /* Check for query mode. */
+ </div><div class="para">
+ if (qva->qva_mode == 'q') {
+ </div><div class="para">
+ /* Make sure there's something to do. */
+ </div><div class="para">
+ if (qva->qva_source != RPMQV_ALL && !poptPeekArg(context)) {
+ </div><div class="para">
+ fprintf(stderr, "no arguments given for --query");
+ </div><div class="para">
+ exit(EXIT_FAILURE);
+ </div><div class="para">
+ }
+ </div><div class="para">
+ </div><div class="para">
+ ec = rpmcliQuery(ts, qva, (const char **) poptGetArgs(context));
+ </div><div class="para">
+ }
+ </div><div class="para">
+ /* Check for verify mode. */
+ </div><div class="para">
+ else if (qva->qva_mode == 'V') {
+ </div><div class="para">
+ rpmVerifyFlags verifyFlags = VERIFY_ALL;
+ </div><div class="para">
+ </div><div class="para">
+ /* Verify flags are negated from query flags. */
+ </div><div class="para">
+ verifyFlags &= ~qva->qva_flags;
+ </div><div class="para">
+ qva->qva_flags = (rpmQueryFlags) verifyFlags;
+ </div><div class="para">
+ </div><div class="para">
+ /* Make sure there's something to do. */
+ </div><div class="para">
+ if (qva->qva_source != RPMQV_ALL && !poptPeekArg(context)) {
+ </div><div class="para">
+ fprintf(stderr, "no arguments given for --verify");
+ </div><div class="para">
+ exit(EXIT_FAILURE);
+ </div><div class="para">
+ }
+ </div><div class="para">
+ </div><div class="para">
+ ec = rpmcliVerify(ts, qva, (const char **) poptGetArgs(context));
+ </div><div class="para">
+ }
+ </div><div class="para">
+ else {
+ </div><div class="para">
+ poptPrintUsage(context, stderr, 0);
+ </div><div class="para">
+ exit(EXIT_FAILURE);
+ </div><div class="para">
+ }
+ </div><div class="para">
+ </div><div class="para">
+ ts = rpmtsFree(ts);
+ </div><div class="para">
+ </div><div class="para">
+ context = rpmcliFini(context);
+ </div><div class="para">
+ </div><div class="para">
+ return ec;
+ </div><div class="para">
+ }
+ </div><div class="para">
+ There is not a lot of code in rpmq.c, as this program is mostly calling the high-level functions for the rpm command-line interface.
+ </div><div class="para">
+ When you run the rpmq program, it performs the same tasks as the rpm command with the --query (or -q) and --verify (or -V) command-line options.
+ </div><div class="para">
+ For example, rpmq supports query formats:
+ </div><div class="para">
+ $ ./rpmq -q --qf "%{NAME} %{INSTALLTID:date}\n" jikes
+ </div><div class="para">
+ jikes Fri 25 Oct 2002 06:49:38 PM CDT
+ </div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id582358" class="title">Where to Go from Here</h1></div></div></div><div class="para">
+ There is a lot more you can do with the RPM library; you're limited only by your imagination. The best way to get started is to follow the examples in this chapter and then try out some RPM programs on your own. After working with the RPM library for a while, you can delve into other RPM topics.
+ </div><div class="para">
+ The RPM Web site, at www.rpm.org, has most of the available documentation on the RPM system. This site also includes official RPM released software.
+ </div><div class="para">
+ One of the best ways to help find out about how to perform RPM tasks is to look at the source code for the rpm program itself. For this, download the rpm-src source RPM, too. To see the rpm command-line interface functions in action, look especially at tools/rpmcache.c and tools/rpmgraph.c, two relatively short RPM files that show how to take advantage of a number of short cuts. The source code for the Python and Perl bindings can also provide extra hints about the purposes of the RPM API calls.
+ </div><div class="para">
+ The RPM Web site also has a cross-referenced set of HTML pages on the RPM programming API. The pages for version 4.1 of RPM are available at www.rpm.org/rpmapi-4.1/. A good starting page is www.rpm.org/rpmapi-4.1/modules.html, which lists a number of modules within the overall RPM library. This extra level of organization can help you locate the functions you need.
+ </div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id577217" class="title">Summary</h1></div></div></div><div class="para">
+ Everything you can do with RPM you can program in C. That’s because the source code for the entire RPM system is available. In addition, the rpm and rpmbuild programs make use of a published API, called rpmlib, to access RPM functionality. You can use this library yourself.
+ </div><div class="para">
+ The popt library, short for parse options, provides a lot of handy utilities for parsing very complex command-line options. You can use popt inside your own programs, even if you don’t use the rest of the RPM functionality.
+ </div><div class="para">
+ Most RPM programs start up by calling rpmcliInit, which sets up RPM variables for the large set of command-line options supported by most RPM commands.
+ </div><div class="para">
+ Call rpmReadPackageFile to read in the Header object from a package file. You can also get Header objects for the packages installed in a system by initializing an iterator to iterate over a set of packages that meet a certain criteria.
+ </div><div class="para">
+ This chapter covers a fairly low level of access to RPM functionality. The next chapter, on Python programming, shows a higher level of abstraction for working with RPM.
+ </div></div></div><div xml:lang="ro" class="chapter" id="ch-rpm-programming-python" lang="ro"><div class="titlepage"><div><div><h2 class="title">Cap. 16. Programming RPM with Python</h2></div></div></div><div class="toc"><dl><dt><span class="sect1"><a href="#id556037">16.1. Setting Up a Python Development Environment</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id870764">16.1.1. Installing the base Python packages</a></span></dt><dt><span class="sect2"><a href="#id590825">16.1.2. Using Python for graphics</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id713551">16.2. The Python API Hierarchy</a></span></dt><dt><span class="sect1"><a href="#id605418">16.3. Programming with the RPM Database</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id938108">16.3.1. Accessing the RPM database</a></span></dt><dt><span class="sect2"><a href="#id1298510">16.3.2. Querying the RPM database</a></span></dt><dt><span class="sect2"><a href="#id752269">16.3.3. Exa
mining the package header</a></span></dt><dt><span class="sect2"><a href="#id668577">16.3.4. Querying for specific packages</a></span></dt><dt><span class="sect2"><a href="#id498480">16.3.5. Printing information on packages</a></span></dt><dt><span class="sect2"><a href="#id652749">16.3.6. Refining queries</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id759668">16.4. Reading Package Files</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id759681">16.4.1. Reading headers from package files</a></span></dt><dt><span class="sect2"><a href="#id859682">16.4.2. Setting the verification flags</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id791873">16.5. Dependency Comparisons</a></span></dt><dt><span class="sect1"><a href="#id772730">16.6. Installing and Upgrading Packages</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id582317">16.6.1. Building up the transaction set</a></span></dt><dt><span class="sect2"><a href="#id773876">16.6.2. Trans
action elements</a></span></dt><dt><span class="sect2"><a href="#id641465">16.6.3. Checking and reordering the transaction elements</a></span></dt><dt><span class="sect2"><a href="#id693782">16.6.4. Running the transaction</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id639900">16.7. Where to Go from Here</a></span></dt><dt><span class="sect1"><a href="#id587324">16.8. Summary</a></span></dt></dl></div><div class="para">
+ This chapter covers:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Using the RPM with Python
+ </div></li><li class="listitem"><div class="para">
+ Installing the necessary modules
+ </div></li><li class="listitem"><div class="para">
+ Programming with the RPM database
+ </div></li><li class="listitem"><div class="para">
+ Programming with RPM files
+ </div></li><li class="listitem"><div class="para">
+ Installing packages programmatically
+ </div></li></ul></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id556037" class="title">Setting Up a Python Development Environment</h1></div></div></div><div class="para">
+ Setting up a Python development environment is much the same as setting up a C programming environment. You need to install a set of packages for general Python development, install a package that provides the Python API to the RPM system, and choose a program for editing your Python scripts.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ <a class="xref" href="#ch-development-tools">Cap. 26, <em>Linux Text Editors and Development Tools</em></a> covers Linux text editors and development tools.
+ </div><div class="para">
+ If you want to make a graphical user interface in your Python programs, you need to install a separate Python package.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id870764" class="title">Installing the base Python packages</h1></div></div></div><div class="para">
+ The base Python package needed for developing applications is python. For RPM usage, you should install Python 2.2, not Python 1.5. That’s because the RPM bindings for Python are moving to support only 2.2 and higher releases.
+ </div><div class="para">
+ The Python package for RPM access is rpm-python. Install these as you would any other packages.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ <a class="xref" href="#ch-using-rpm">Cap. 3, <em>Using RPM</em></a> covers installing packages.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id590825" class="title">Using Python for graphics</h1></div></div></div><div class="para">
+ Python supports a number of different toolkits for creating graphical user interfaces. You need one of these toolkits if you want to create Python applications that sport a user interface instead of command-line tools. Among the most popular toolkits are PyGKT, PyQt, and Tkinter.
+ </div><div class="para">
+ *PyGTK is a binding between Python and the GTK+ toolkit used by the GNOME desktop, one of two main desktop environments for Linux. (KDE is the other main desktop environment.) The Red Hat redhat-config-packages program uses PyGTK and sports a very good-looking user interface.
+ </div><div class="para">
+ PyGTK provides full access to the GTK+ widgets such as menus, dialog windows, and buttons. Install the pygtk2 module for PyGTK. For more on PyGTK, see www.daa.com.au/~james/pygtk/.
+ </div><div class="para">
+ *PyQt connects Python scripts to the Qt C++ user interface toolkit. Qt forms the base library used by the KDE desktop environment and KDE applications. As with PyGTK, PyQt allows you to access the rich widget set provided by the library.
+ </div><div class="para">
+ Install the PyQt package for PyQt. For more on PyQt, see www.riverbankcomputing.co.uk/pyqt/.
+ </div><div class="para">
+ *Tkinter is considered a standard part of Python and is based on the Tk (pronounced teekay) toolkit from the Tcl scripting language. The main advantages of Tkinter are that it is considered part of Python, meaning users are more likely to have it, and Tkinter works on multiple platforms, including Windows.
+ </div><div class="para">
+ The main drawback of Tkinter is that the widget sets are not as rich as PyQt or PyGTK. For more on Tkinter, see www.python.org/topics/tkinter/.
+ </div><div class="para">
+ After you’ve set up your environment and installed all the necessary packages, the next step is to start working with the Python API for RPM.
+ </div></div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id713551" class="title">The Python API Hierarchy</h1></div></div></div><div class="para">
+ The RPM Python API provides a high-level abstraction into RPM functionality divided into logical areas. Table 17-1 lists the main RPM types. In most cases, you need to begin with rpm and create a transaction set.
+ </div><div class="para">
+ Table 17-1 Python types for RPM usage
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Class
+ </div>
+
+ </td><td>
+ <div class="para">
+ Covers
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpm
+ </div>
+
+ </td><td>
+ <div class="para">
+ RPM base module into RPM API
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpmts
+ </div>
+
+ </td><td>
+ <div class="para">
+ Transaction sets
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpmte
+ </div>
+
+ </td><td>
+ <div class="para">
+ Transaction elements, a package in a transaction set
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpmmi
+ </div>
+
+ </td><td>
+ <div class="para">
+ Match iterators, used for querying the RPM database
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Rpmds
+ </div>
+
+ </td><td>
+ <div class="para">
+ Dependency set
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Rpmfi
+ </div>
+
+ </td><td>
+ <div class="para">
+ File into set
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Header
+ </div>
+
+ </td><td>
+ <div class="para">
+ A package header
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ In general, the RPM Python API is well-integrated into the standard Python API. For example, you use the Python os class to read in RPM package files.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ The examples in this chapter use the RPM 4.1 Python API. The API in previous versions is significantly different from the 4.1 version.
+ </div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id605418" class="title">Programming with the RPM Database</h1></div></div></div><div class="para">
+ Compared to the RPM C API, discussed in <a class="xref" href="#ch-programming-c">Cap. 15, <em>Programming RPM with C</em></a> , the Python API is much simpler and requires many fewer programming statements to get your job done.
+ </div><div class="para">
+ Just about every Python RPM script needs a transaction set. Create a transaction set with rpm.TransactionSet:
+ </div><div class="para">
+ import rpm
+ </div><div class="para">
+ </div><div class="para">
+ ts = rpm.TransactionSet()
+ </div><div class="para">
+ The transaction set will automatically open the RPM database if needed.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ The code examples in this chapter follow the Red Hat conventions for naming variables, such as ts for a transaction set. This is to make it easier to read the Python examples in the RPM sources, along with Red Hat installer programs written in Python.
+ </div><div class="para">
+ You will need a transaction set in just about every Python script that accesses RPM functionality.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id938108" class="title">Accessing the RPM database</h1></div></div></div><div class="para">
+ Transaction sets provide a number of methods for working with the RPM database at the database level. Use these methods if you need to interact with the database as a whole, as opposed to accessing individual packages in the database. For example, you can initialize or rebuild the RPM database with these methods. You can also use a handy trick for accessing another RPM database instead of the default system database.
+ </div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id553489" class="title">Setting the Database Location</h1></div></div></div><div class="para">
+ A transaction set will open the RPM database assuming the default location. To specify a different RPM database location, call addMacro, as shown following:
+ </div><div class="para">
+ rpm.addMacro("_dbpath", path_to_rpm_database)
+ </div><div class="para">
+ You can work with more than one RPM database by setting the _dbpath macro, creating a transaction set, and then removing the macro. After doing this, you can create another transaction set for the default RPM database, allowing your script to work with more than one database. For example:
+ </div><div class="para">
+ # Open the rpmdb-redhat database
+ </div><div class="para">
+ rpm.addMacro("_dbpath", "/usr/lib/rpmdb/i386-redhat-linux/redhat")
+ </div><div class="para">
+ solvets = rpm.TransactionSet()
+ </div><div class="para">
+ solvets.openDB()
+ </div><div class="para">
+ rpm.delMacro("_dbpath")
+ </div><div class="para">
+ </div><div class="para">
+ # Open default database
+ </div><div class="para">
+ ts = rpm.TransactionSet()
+ </div><div class="para">
+ This example uses the rpmdb-redhat package, which holds a database of all Red Hat Linux packages. The explicit call to openDB opens the RPM database. In most Python scripts, though, you do not want to call openDB. Instead, a transaction set will open the database as needed.
+ </div><div class="para">
+ The call to delMacro removes the _dbpath macro, allowing the next call to TransactionSet to use the default RPM database.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ Do not call closeDB on a transaction set. This method does indeed close the RPM database, but it also disables the ability to automatically open the RPM database as needed.
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id669254" class="title">Initializing, Rebuilding, and Verifying the Database</h1></div></div></div><div class="para">
+ The transaction set provides an initDB method to initialize a new RPM database. This acts like the rpm --initdb command.
+ </div><div class="para">
+ ts.initDB()
+ </div><div class="para">
+ The rebuildDB method regenerates the RPM database indices, like the rpm --rebuilddb command:
+ </div><div class="para">
+ ts.rebuildDB()
+ </div><div class="para">
+ The rebuildDB method regenerates the RPM database indices, like the rpm --rebuilddb command.
+ </div><div class="para">
+ The verifyDB method checks that the RPM database and indices are readable by the Berkeley DB library:
+ </div><div class="para">
+ ts.verifyDB()
+ </div><div class="para">
+ Calling this method is the same as running the db_verify command on each of the database files in /var/lib/rpm.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ See <a class="xref" href="#ch-using-rpm-db">Cap. 4, <em>Using the RPM Database</em></a> for more on initializing, rebuilding, and verifying RPM databases.
+ </div><div class="para">
+ Once you have a transaction set, you can start querying the RPM database.
+ </div></div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id1298510" class="title">Querying the RPM database</h1></div></div></div><div class="para">
+ Call dbMatch on a transaction set to create a match iterator. As with the C API, a match iterator allows your code to iterate over the packages that match a given criteria.
+ </div><div class="para">
+ A call to dbMatch with no parameters means to set up a match iterator to go over the entire set of installed packages. The basic format follows:
+ </div><div class="para">
+ import rpm
+ </div><div class="para">
+ </div><div class="para">
+ ts = rpm.TransactionSet()
+ </div><div class="para">
+ </div><div class="para">
+ mi = ts.dbMatch()
+ </div><div class="para">
+ for h in mi:
+ </div><div class="para">
+ # Do something with header object...
+ </div><div class="para">
+ In this example, the call to dbMatch returns a match iterator. The for loop iterates over the match iterator, returning one header each time.
+ </div><div class="para">
+ In addition to this syntax, you can call next on the match iterator to get the next entry, a header object that represents one package. For example:
+ </div><div class="para">
+ import rpm
+ </div><div class="para">
+ </div><div class="para">
+ ts = rpm.TransactionSet()
+ </div><div class="para">
+ </div><div class="para">
+ mi = ts.dbMatch()
+ </div><div class="para">
+ while mi:
+ </div><div class="para">
+ h = mi.next()
+ </div><div class="para">
+ # Do something with the header object
+ </div><div class="para">
+ The explicit call to next on the match iterator will likely no longer be supported in a future version of the RPM Python API, since the PEP-234 (Python Enhancement Proposal) calls for one means or the other for iterating, but not both.
+ </div><div class="para">
+ For example, Listing 17-1 shows a Python script to print out the name, version, and release information for all installed packages.
+ </div><div class="para">
+ Listing 17-1: rpmqa.py
+ </div><div class="para">
+ #!/usr/bin/python
+ </div><div class="para">
+ </div><div class="para">
+ # Acts like rpm -qa and lists the names of all the installed packages.
+ </div><div class="para">
+ # Usage:
+ </div><div class="para">
+ # python rpmqa.py
+ </div><div class="para">
+ </div><div class="para">
+ import rpm
+ </div><div class="para">
+ </div><div class="para">
+ ts = rpm.TransactionSet()
+ </div><div class="para">
+ </div><div class="para">
+ mi = ts.dbMatch()
+ </div><div class="para">
+ for h in mi:
+ </div><div class="para">
+ </div><div class="para">
+ print "%s-%s-%s" % (h['name'], h['version'], h['release'])
+ </div><div class="para">
+ When you call this script, you should see output like the following, truncated for space:
+ </div><div class="para">
+ $ python rpmqa.py
+ </div><div class="para">
+ libbonoboui-2.0.1-2
+ </div><div class="para">
+ attr-2.0.8-3
+ </div><div class="para">
+ dhclient-3.0pl1-9
+ </div><div class="para">
+ file-3.37-8
+ </div><div class="para">
+ hdparm-5.2-1
+ </div><div class="para">
+ ksymoops-2.4.5-1
+ </div><div class="para">
+ imlib-1.9.13-9
+ </div><div class="para">
+ logwatch-2.6-8
+ </div><div class="para">
+ mtr-0.49-7
+ </div><div class="para">
+ openssh-clients-3.4p1-2
+ </div><div class="para">
+ pax-3.0-4
+ </div><div class="para">
+ python-optik-1.3-2
+ </div><div class="para">
+ dump-0.4b28-4
+ </div><div class="para">
+ sendmail-8.12.5-7
+ </div><div class="para">
+ sudo-1.6.6-1
+ </div><div class="para">
+ mkbootdisk-1.4.8-1
+ </div><div class="para">
+ telnet-0.17-23
+ </div><div class="para">
+ usbutils-0.9-7
+ </div><div class="para">
+ wvdial-1.53-7
+ </div><div class="para">
+ docbook-dtds-1.0-14
+ </div><div class="para">
+ urw-fonts-2.0-26
+ </div><div class="para">
+ db4-utils-4.0.14-14
+ </div><div class="para">
+ libogg-devel-1.0-1
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ If you set the execute permission on this script, you can skip the explicit call to the python command. For example:
+ </div><div class="para">
+ $ ./rpmqa.pyr
+ </div><div class="para">
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id752269" class="title">Examining the package header</h1></div></div></div><div class="para">
+ The code in Listing 17-1 introduces the package header object, an object of the hdr class. This represents a package header, and contains entries such as the name, version, pre- and post-installation scripts, and triggers.
+ </div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id752281" class="title">The hdr Class</h1></div></div></div><div class="para">
+ You can access each entry in the header using Python's dictionary syntax. This is much more convenient than calling headerGetEntry in C programs. The basic syntax to access header entries follows:
+ </div><div class="para">
+ value = h['tag_name']
+ </div><div class="para">
+ For example, to get the package name, use the following code:
+ </div><div class="para">
+ name = h['name']
+ </div><div class="para">
+ You can also use a set of predefined RPMTAG_ constants that match the C API. These constants are defined in the rpm module. For example:
+ </div><div class="para">
+ name = h[rpm.RPMTAG_NAME]
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ Using the rpm constants such as rpm.RPMTAG_NAME is faster than using the strings such as 'name'.
+ </div><div class="para">
+ For header entries that hold an array of strings, such as the list of files in the package, the data returned is a Python list. For example:
+ </div><div class="para">
+ print "Files:"
+ </div><div class="para">
+ files = h['FILENAMES']
+ </div><div class="para">
+ for name in files:
+ </div><div class="para">
+ print name
+ </div><div class="para">
+ You can use file info sets to achieve more compact code. For example:
+ </div><div class="para">
+ print "Files:"
+ </div><div class="para">
+ fi = h.fiFromHeader()
+ </div><div class="para">
+ print fi
+ </div><div class="para">
+ The requires, provides, obsoletes, and conflicts information each appear as three separate but related lists for each set of information, with three lists for the requires information, three for the provides information, and so on. You can extract this information using Python dependency sets using the simple code following:
+ </div><div class="para">
+ print h.dsFromHeader('providename')
+ </div><div class="para">
+ print h.dsFromHeader('requirename')
+ </div><div class="para">
+ print h.dsFromHeader('obsoletename')
+ </div><div class="para">
+ print h.dsFromHeader('conflictname')
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ The rpminfo.py script in Listing 17-3 shows how to print out this information.
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id735543" class="title">Printing Header Information with sprintf</h1></div></div></div><div class="para">
+ In addition to using the Python dictionary syntax, you can use the sprintf method on a header to format data using a syntax exactly the same as the query format tags supported by the rpm command.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ <a class="xref" href="#ch-using-rpm-db">Cap. 4, <em>Using the RPM Database</em></a> covers query formats.
+ </div><div class="para">
+ The basic syntax is as follows:
+ </div><div class="para">
+ h.sprintf("%{tag_name}")
+ </div><div class="para">
+ You can also use special formatting additions to the tag name. For example:
+ </div><div class="para">
+ print "Header signature: ", h.sprintf("%{DSAHEADER:pgpsig}")
+ </div><div class="para">
+ print "%-20s: %s" % ('Installed on', h.sprintf("%{INSTALLTID:date}") )
+ </div><div class="para">
+ You can combine this information into functions that print out header entries with specific formatting. For example:
+ </div><div class="para">
+ def nvr(h):
+ </div><div class="para">
+ return h.sprintf("%{NAME}-%{VERSION}-%{RELEASE}")
+ </div><div class="para">
+ Note that you only really need to use sprintf when you need the format modifiers, such as date on %{INSTALLTID:date}. In most other cases, Python’s string-handling functions will work better.
+ </div></div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id668577" class="title">Querying for specific packages</h1></div></div></div><div class="para">
+ When you call dbMatch on a transaction set object, passing no parameters means to iterate over the entire set of installed packages in the RPM database. You can also query for specific packages using dbMatch. To do so, you need to pass the name of a tag in the header, as well as the value for that tag that you are looking for. The basic syntax follows:
+ </div><div class="para">
+ mi = ts.dbMatch(tag_name, value)
+ </div><div class="para">
+ For example, to query for all packages named sendmail, use code like the following:
+ </div><div class="para">
+ mi = ts.dbMatch('name', 'sendmail')
+ </div><div class="para">
+ The call to dbMatch returns an rpmdbMatchIterator. You can query on any of the tags in the header, but by far the most common query is by name.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ Some matches are fast and some are much slower. If you try to match on a tag that is indexed in the RPM database, the matches will perform much faster than for those tags that are not indexes. To determine which tags are indexed, look at the files in /var/lib/rpm. For example, Name and Requirename are files in /var/lib/rpm. These tags are indexed and will therefore match quickly.
+ </div><div class="para">
+ Listing 17-2 shows an example Python script which queries for a particular package name and then prints out the name, version, and release for all matching packages.
+ </div><div class="para">
+ Listing 17-2: rpmq.py
+ </div><div class="para">
+ #!/usr/bin/python
+ </div><div class="para">
+ </div><div class="para">
+ # Acts like rpm -q and lists the N-V-R for installed
+ </div><div class="para">
+ # packages that match a given name.
+ </div><div class="para">
+ # Usage:
+ </div><div class="para">
+ # python rpmq.py package_name
+ </div><div class="para">
+ </div><div class="para">
+ import rpm, sys
+ </div><div class="para">
+ </div><div class="para">
+ ts = rpm.TransactionSet()
+ </div><div class="para">
+ </div><div class="para">
+ mi = ts.dbMatch( 'name', sys.argv[1] )
+ </div><div class="para">
+ for h in mi:
+ </div><div class="para">
+ </div><div class="para">
+ print "%s-%s-%s" % (h['name'], h['version'], h['release'])
+ </div><div class="para">
+ When you call this script, you need to pass the name of a package to query, which the python interpreter will store in sys,argv[1] in the call to dbMatch. For example:
+ </div><div class="para">
+ $ python rpmq.py sendmail
+ </div><div class="para">
+ sendmail-8.12.5-7
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id498480" class="title">Printing information on packages</h1></div></div></div><div class="para">
+ You can create the equivalent of the rpm –qi command with a small number of Python commands. Listing 17-3 shows an example. This script queries for a particular package name, as shown previously in Listing 17-2. Once a package is found, though, rpminfo.py prints out a lot more information, similar to the output from the rpm –qi command.
+ </div><div class="para">
+ Listing 17-3: rpminfo.py
+ </div><div class="para">
+ #!/usr/bin/python
+ </div><div class="para">
+ </div><div class="para">
+ # Lists information on installed package listed on command line.
+ </div><div class="para">
+ # Usage:
+ </div><div class="para">
+ # python rpminfo.py package_name
+ </div><div class="para">
+ </div><div class="para">
+ import rpm, sys
+ </div><div class="para">
+ </div><div class="para">
+ def printEntry(header, label, format, extra):
+ </div><div class="para">
+ value = header.sprintf(format).strip()
+ </div><div class="para">
+ </div><div class="para">
+ print "%-20s: %s %s" % (label, value, extra)
+ </div><div class="para">
+ </div><div class="para">
+ </div><div class="para">
+ def printHeader(h):
+ </div><div class="para">
+ </div><div class="para">
+ if h[rpm.RPMTAG_SOURCEPACKAGE]:
+ </div><div class="para">
+ extra = " source package"
+ </div><div class="para">
+ else:
+ </div><div class="para">
+ extra = " binary package"
+ </div><div class="para">
+ </div><div class="para">
+ printEntry(h, 'Package', "%{NAME}-%{VERSION}-%{RELEASE}", extra)
+ </div><div class="para">
+ </div><div class="para">
+ printEntry(h, 'Group', "%{GROUP}", '')
+ </div><div class="para">
+ printEntry(h, 'Summary', "%{Summary}", '')
+ </div><div class="para">
+ printEntry(h, 'Arch-OS-Platform', "%{ARCH}-%{OS}-%{PLATFORM}", '')
+ </div><div class="para">
+ </div><div class="para">
+ printEntry(h, 'Vendor', "%{Vendor}", '')
+ </div><div class="para">
+ printEntry(h, 'URL', "%{URL}", '')
+ </div><div class="para">
+ printEntry(h, 'Size', "%{Size}", '')
+ </div><div class="para">
+ printEntry(h, 'Installed on', "%{INSTALLTID:date}", '')
+ </div><div class="para">
+ </div><div class="para">
+ print h['description']
+ </div><div class="para">
+ </div><div class="para">
+ print "Files:"
+ </div><div class="para">
+ fi = h.fiFromHeader()
+ </div><div class="para">
+ print fi
+ </div><div class="para">
+ </div><div class="para">
+ # Dependencies
+ </div><div class="para">
+ print "Provides:"
+ </div><div class="para">
+ print h.dsFromHeader('providename')
+ </div><div class="para">
+ print "Requires:"
+ </div><div class="para">
+ print h.dsFromHeader('requirename')
+ </div><div class="para">
+ </div><div class="para">
+ if h.dsFromHeader('obsoletename'):
+ </div><div class="para">
+ print "Obsoletes:"
+ </div><div class="para">
+ print h.dsFromHeader('obsoletename')
+ </div><div class="para">
+ </div><div class="para">
+ if h.dsFromHeader('conflictname'):
+ </div><div class="para">
+ print "Conflicts:"
+ </div><div class="para">
+ print h.dsFromHeader('conflictname')
+ </div><div class="para">
+ </div><div class="para">
+ </div><div class="para">
+ ts = rpm.TransactionSet()
+ </div><div class="para">
+ </div><div class="para">
+ mi = ts.dbMatch( 'name', sys.argv[1] )
+ </div><div class="para">
+ for h in mi:
+ </div><div class="para">
+ </div><div class="para">
+ printHeader(h)
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ You should be able to simplify this script. The extensive use of the sprintf method is for illustration more than efficiency. You generally only need to call sprintf when you need a format modifier for a tag. In the rpminfo.py script, sprintf was also used to ensure that all entries are text, which allows for calling strip.
+ </div><div class="para">
+ The printEntry function takes in a header sprintf tag value in the format of "%{NAME}". You can also pass in more complex values with multiple header entries, such as "%{NAME}-%{VERSION}".
+ </div><div class="para">
+ When you run this script, you need to pass the name of a package. You'll see output like the following:
+ </div><div class="para">
+ $ python rpminfo.py jikes
+ </div><div class="para">
+ Package : jikes-1.18-1 binary package
+ </div><div class="para">
+ Group : Development/Languages
+ </div><div class="para">
+ Summary : java source to bytecode compiler
+ </div><div class="para">
+ Arch-OS-Platform : i386-Linux-(none)
+ </div><div class="para">
+ Vendor : (none)
+ </div><div class="para">
+ URL : http://ibm.com/developerworks/opensource/jikes
+ </div><div class="para">
+ Size : 2853672
+ </div><div class="para">
+ Installed on : Mon Dec 2 20:10:13 2002
+ </div><div class="para">
+ The IBM Jikes compiler translates Java source files to bytecode. It
+ </div><div class="para">
+ also supports incremental compilation and automatic makefile
+ </div><div class="para">
+ generation,and is maintained by the Jikes Project:
+ </div><div class="para">
+ http://ibm.com/developerworks/opensource/jikes/
+ </div><div class="para">
+ </div><div class="para">
+ Files:
+ </div><div class="para">
+ /usr/bin/jikes
+ </div><div class="para">
+ /usr/doc/jikes-1.18/license.htm
+ </div><div class="para">
+ /usr/man/man1/jikes.1.gz
+ </div><div class="para">
+ </div><div class="para">
+ Provides:
+ </div><div class="para">
+ P jikes
+ </div><div class="para">
+ P jikes = 1.18-1
+ </div><div class="para">
+ </div><div class="para">
+ Requires:
+ </div><div class="para">
+ R ld-linux.so.2
+ </div><div class="para">
+ R libc.so.6
+ </div><div class="para">
+ R libc.so.6(GLIBC_2.0)
+ </div><div class="para">
+ R libc.so.6(GLIBC_2.1)
+ </div><div class="para">
+ R libc.so.6(GLIBC_2.1.3)
+ </div><div class="para">
+ R libm.so.6
+ </div><div class="para">
+ R libstdc++-libc6.2-2.so.3
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id652749" class="title">Refining queries</h1></div></div></div><div class="para">
+ The pattern method on a match iterator allows you to refine a query. This narrows an existing iterator to only show the packages you desire. The basic syntax follows:
+ </div><div class="para">
+ mi.pattern(tag_name, mode, pattern)
+ </div><div class="para">
+ The two main uses of the pattern method are to query on more than one tag, such as the version and name, or to narrow the results of a query, using the rich set of pattern modes. The mode parameter names the type of pattern used, which can be one of those listed in Table 17-2.
+ </div><div class="para">
+ Table 17-2 Pattern modes for the pattern method
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Type
+ </div>
+
+ </td><td>
+ <div class="para">
+ Meaning
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpm.RPMMIRE_DEFAULT
+ </div>
+
+ </td><td>
+ <div class="para">
+ Same as regular expressions, but with \., .*, and ^..$ added
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpm.RPMMIRE_GLOB
+ </div>
+
+ </td><td>
+ <div class="para">
+ Glob-style patterns using fnmatch
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpm.RPMMIRE_REGEX
+ </div>
+
+ </td><td>
+ <div class="para">
+ Regular expressions using regcomp
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpm.RPMMIRE_STRCMP
+ </div>
+
+ </td><td>
+ <div class="para">
+ String comparisons using strcmp
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ For more on these patterns, see the online manual pages for fnmatch(3), glob(7), regcomp(3), regex(7), and strcmp(3). The pattern method calls rpmdbSetIteratorRE from the C API, covered in the “Database Iterators†section in <a class="xref" href="#ch-programming-c">Cap. 15, <em>Programming RPM with C</em></a> .
+ </div><div class="para">
+ To query for all packages starting with py, for example, you can use code like the following:
+ </div><div class="para">
+ import rpm
+ </div><div class="para">
+ </div><div class="para">
+ ts = rpm.TransactionSet()
+ </div><div class="para">
+ </div><div class="para">
+ mi = ts.dbMatch()
+ </div><div class="para">
+ </div><div class="para">
+ mi.pattern('name', rpm.RPMMIRE_GLOB, 'py*' )
+ </div><div class="para">
+ </div><div class="para">
+ for h in mi:
+ </div><div class="para">
+ # Do something with the header...
+ </div><div class="para">
+ Listing 17-4 shows an example for glob-based querying.
+ </div><div class="para">
+ Listing 17-4: rpmglob.py
+ </div><div class="para">
+ #!/usr/bin/python
+ </div><div class="para">
+ </div><div class="para">
+ # Acts like rpm -q and lists the N-V-R for installed packages
+ </div><div class="para">
+ # that match a given name using a glob-like syntax
+ </div><div class="para">
+ #
+ </div><div class="para">
+ # Usage:
+ </div><div class="para">
+ # python rpmglob.py "package_fragment*"
+ </div><div class="para">
+ </div><div class="para">
+ import rpm, sys
+ </div><div class="para">
+ </div><div class="para">
+ ts = rpm.TransactionSet()
+ </div><div class="para">
+ </div><div class="para">
+ mi = ts.dbMatch()
+ </div><div class="para">
+ </div><div class="para">
+ if not mi:
+ </div><div class="para">
+ print "No packages found."
+ </div><div class="para">
+ else:
+ </div><div class="para">
+ mi.pattern('name', rpm.RPMMIRE_GLOB, sys.argv[1] )
+ </div><div class="para">
+ </div><div class="para">
+ for h in mi:
+ </div><div class="para">
+ </div><div class="para">
+ print "%s-%s-%s" % (h['name'], h['version'], h['release'])
+ </div><div class="para">
+ When you run this script, you’ll see output like the following:
+ </div><div class="para">
+ $ python rpmglob.py "py*"
+ </div><div class="para">
+ pyxf86config-0.3.1-2
+ </div><div class="para">
+ python-devel-2.2.1-17
+ </div><div class="para">
+ pygtk2-devel-1.99.12-7
+ </div><div class="para">
+ pygtk2-libglade-1.99.12-7
+ </div><div class="para">
+ pygtk2-1.99.12-7
+ </div><div class="para">
+ pyOpenSSL-0.5.0.91-1
+ </div><div class="para">
+ python-optik-1.3-2
+ </div><div class="para">
+ python-docs-2.2.1-17
+ </div><div class="para">
+ python-2.2.1-17
+ </div><div class="para">
+ python-tools-2.2.1-17
+ </div><div class="para">
+ In addition to working with the RPM database, the Python API also provides access to RPM files.
+ </div></div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id759668" class="title">Reading Package Files</h1></div></div></div><div class="para">
+ As you would expect, the Python API includes methods for working with RPM package files in addition to installed RPM packages. Most of these methods require a header object, which you can read from an RPM package file.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id759681" class="title">Reading headers from package files</h1></div></div></div><div class="para">
+ Like the C function rpmReadPackageFile, the Python API provides a convenient way to read in a header object from an RPM package file. The hdrFromFdno method reads an RPM header from an open file descriptor. The basic syntax is:
+ </div><div class="para">
+ h = ts.hdrFromFdno(fdno)
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ The hdrFromFdno method uses Python’s low-level file descriptors instead of the higher-level Python file objects. In the RPM C library, an FD_t is a FILE**. This could be bound to a Python class, but that is outside the scope of this chapter.
+ </div><div class="para">
+ The following example shows a function that opens a file, reads in the RPM header, and then closes the file:
+ </div><div class="para">
+ def readRpmHeader(ts, filename):
+ </div><div class="para">
+ """ Read an rpm header. """
+ </div><div class="para">
+ fd = os.open(filename, os.O_RDONLY)
+ </div><div class="para">
+ </div><div class="para">
+ h = ts.hdrFromFdno(fd)
+ </div><div class="para">
+ </div><div class="para">
+ os.close(fd)
+ </div><div class="para">
+ return h
+ </div><div class="para">
+ </div><div class="para">
+ ts = rpm.TransactionSet()
+ </div><div class="para">
+ </div><div class="para">
+ h = readRpmHeader( ts, 'n-r-v.rpm' )
+ </div><div class="para">
+ The hdrFromFdno method raises a number of exceptions based on issues detected with the package files. The following example shows these exceptions:
+ </div><div class="para">
+ def readRpmHeader(ts, filename):
+ </div><div class="para">
+ """ Read an rpm header. """
+ </div><div class="para">
+ fd = os.open(filename, os.O_RDONLY)
+ </div><div class="para">
+ </div><div class="para">
+ h = None
+ </div><div class="para">
+ tryL
+ </div><div class="para">
+ h = ts.hdrFromFdno(fd)
+ </div><div class="para">
+ except rpm.error, e:
+ </div><div class="para">
+ if str(e) == "public key not available":
+ </div><div class="para">
+ print str(e)
+ </div><div class="para">
+ if str(e) == "public key not trusted":
+ </div><div class="para">
+ print str(e)
+ </div><div class="para">
+ if str(e) == "error reading package header":
+ </div><div class="para">
+ print str(e)
+ </div><div class="para">
+ h = None
+ </div><div class="para">
+ </div><div class="para">
+ </div><div class="para">
+ os.close(fd)
+ </div><div class="para">
+ return h
+ </div><div class="para">
+ </div><div class="para">
+ ts = rpm.TransactionSet()
+ </div><div class="para">
+ </div><div class="para">
+ h = readRpmHeader( ts, 'n-r-v.rpm' )
+ </div><div class="para">
+ You can decide in your code whether the exceptions should stop processing or not.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id859682" class="title">Setting the verification flags</h1></div></div></div><div class="para">
+ Starting with rpm 4.1, package files are verified automatically, which can cause problems, especially if you are working with older packages, or packages without proper digital signatures.
+ </div><div class="para">
+ In most cases, the automatic verification is an advantage, since you can have greater confidence in the package files. However, you can call setVSFlags on a transaction set to change the default behavior.
+ </div><div class="para">
+ ts.setVSFlags(flags)
+ </div><div class="para">
+ For example, if you have problems with old packages that do not have proper signatures, you can use code like the following to ignore such checks:
+ </div><div class="para">
+ # Set to not verify DSA signatures.
+ </div><div class="para">
+ ts.setVSFlags(rpm.RPMVSF_NODSA)
+ </div><div class="para">
+ Table 17-3 lists the flags you can pass to setVSFlags on a transaction set. These flags are bitmasks. You can or them together for more than one setting. You must do a binary or. Do not use the Python or keyword. Use | instead, for a binary or operation.
+ </div><div class="para">
+ Table 17-3 Flags for setVSFlags
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Flag
+ </div>
+
+ </td><td>
+ <div class="para">
+ Meaning
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpm.RPMVSF_NEEDPAYLOAD
+ </div>
+
+ </td><td>
+ <div class="para">
+ Leave the file handle positions at the beginning of the payload.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpm.RPMVSF_NOHDRCHK
+ </div>
+
+ </td><td>
+ <div class="para">
+ Don’t check the RPM database header.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpm.RPMVSF_ NODSA
+ </div>
+
+ </td><td>
+ <div class="para">
+ Don’t check the header and payload DSA signatures.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpm.RPMVSF_ NODSAHEADER
+ </div>
+
+ </td><td>
+ <div class="para">
+ Don’t check the header DSA signature.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpm.RPMVSF_ NOMD5
+ </div>
+
+ </td><td>
+ <div class="para">
+ Don’t check the header and payload MD5 digests.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpm.RPMVSF_ NORSA
+ </div>
+
+ </td><td>
+ <div class="para">
+ Don’t check the header and payload RSA signatures.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpm.RPMVSF_ NOSHA1HEADER
+ </div>
+
+ </td><td>
+ <div class="para">
+ Don’t check the header SHA1 digest.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpm._RPMVSF_NODIGESTS
+ </div>
+
+ </td><td>
+ <div class="para">
+ Convenience to not check digests.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpm._RPMVSF_NOSIGNATURES
+ </div>
+
+ </td><td>
+ <div class="para">
+ Convenience to not check signatures.
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ To turn off all checks, you can pass –1 to setVSFlags:
+ </div><div class="para">
+ ts.setVSFlasgs(-1)
+ </div></div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id791873" class="title">Dependency Comparisons</h1></div></div></div><div class="para">
+ Dependency sets, first introduced in <a class="xref" href="#ch-programming-c">Cap. 15, <em>Programming RPM with C</em></a> on C programming, allow you to compare the dependencies between two packages. One of the most common uses for this is to compare a package file against a version on disk to see if the package file holds a newer version of a package than the one installed.
+ </div><div class="para">
+ You can call dsOfHeader on a header object to get the default dependency set for the header. Armed with dependency sets from two headers, you can compare the sets to see which package is newer using simple code like the following:
+ </div><div class="para">
+ file_h = ts.hdrFromFdno(fd)
+ </div><div class="para">
+ file_ds = file_h.dsOfHeader()
+ </div><div class="para">
+ inst_ds = inst_h.dsOfHeader()
+ </div><div class="para">
+ if file_ds.EVR() >= inst_ds.EVR():
+ </div><div class="para">
+ print "Package file is same or newer, OK to upgrade."
+ </div><div class="para">
+ else:
+ </div><div class="para">
+ print "Package file is older than installed version."
+ </div><div class="para">
+ Pulling this all together, Listing 17-5 provides a Python script that compares a package file against an installed package, reporting on which is newer.
+ </div><div class="para">
+ Listing 17-5: vercompare.py
+ </div><div class="para">
+ #!/usr/bin/python
+ </div><div class="para">
+ </div><div class="para">
+ # Reads in package header, compares to installed package.
+ </div><div class="para">
+ # Usage:
+ </div><div class="para">
+ # python vercompare.py rpm_file.rpm
+ </div><div class="para">
+ #
+ </div><div class="para">
+ </div><div class="para">
+ import rpm, os, sys
+ </div><div class="para">
+ </div><div class="para">
+ def readRpmHeader(ts, filename):
+ </div><div class="para">
+ """ Read an rpm header. """
+ </div><div class="para">
+ fd = os.open(filename, os.O_RDONLY)
+ </div><div class="para">
+ </div><div class="para">
+ h = ts.hdrFromFdno(fd)
+ </div><div class="para">
+ </div><div class="para">
+ os.close(fd)
+ </div><div class="para">
+ return h
+ </div><div class="para">
+ </div><div class="para">
+ </div><div class="para">
+ ts = rpm.TransactionSet()
+ </div><div class="para">
+ h = readRpmHeader( ts, sys.argv[1] )
+ </div><div class="para">
+ </div><div class="para">
+ pkg_ds = h.dsOfHeader()
+ </div><div class="para">
+ </div><div class="para">
+ for inst_h in ts.dbMatch('name', h['name']):
+ </div><div class="para">
+ inst_ds = inst_h.dsOfHeader()
+ </div><div class="para">
+ </div><div class="para">
+ if pkg_ds.EVR() >= inst_ds.EVR():
+ </div><div class="para">
+ print "Package file is same or newer, OK to upgrade."
+ </div><div class="para">
+ else:
+ </div><div class="para">
+ print "Package file is older than installed version."
+ </div><div class="para">
+ Cross-Reference
+ </div><div class="para">
+ The Python script in Listing 17-5 is essentially the same as the longer C program vercompare.c in Listing 16-4 in <a class="xref" href="#ch-programming-c">Cap. 15, <em>Programming RPM with C</em></a> .
+ </div><div class="para">
+ This script takes in a package file name on the command line, loads in the header for that package, and looks up all packages of the same name installed in the RPM database. For each match, this script compares the packages to see which is newer.
+ </div><div class="para">
+ You can modify this script, for example, to print out a message if a package isn't installed.
+ </div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id772730" class="title">Installing and Upgrading Packages</h1></div></div></div><div class="para">
+ With the RPM system, you have a lot of choices. You can install or upgrade packages with the rpm command. You can install or upgrade packages with special programs you write using the C API. And you can install or upgrade packages using the Python API. If you are writing a special program to install or upgrade packages, the Python API makes this task much easier. As with the C API, most of your work needs to be part of a transaction set.
+ </div><div class="para">
+ To install or upgrade a package, you need to create a transaction set, build up the transaction with packages, which are stored as transaction elements within the transaction set, check for unresolved dependencies, reorder the transaction set based on the dependencies, and then run the transaction set. Running the transaction set installs or upgrades the packages. The following sections cover these steps.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id582317" class="title">Building up the transaction set</h1></div></div></div><div class="para">
+ Package installs and upgrades need to be performed within the context of a transaction set. To install or upgrade a set of packages, you need to call addInstall with the package headers to install or upgrade. The basic syntax follows:
+ </div><div class="para">
+ ts.addInstall(header, key_data, mode)
+ </div><div class="para">
+ When you call addInstall, you pass the header object along with arbitrary callback key data and a mode flag. The mode flag should be 'i' to install a package, 'u' to upgrade a package, or 'a' as a special code to make a package available for transaction checks but not install or upgrade the package. The 'a' flag is rarely used. In most cases, you should use 'u', just as in most cases, you should install packages with rpm –U instead of rpm –i.
+ </div><div class="para">
+ The key_data parameter will get passed to the transaction set run callback, covered in the “Running the Transaction†section later in this chapter.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ To remove packages instead of install or upgrade, call addErase instead of addInstall:
+ </div><div class="para">
+ ts.addErase(package_name)
+ </div><div class="para">
+ To set up a package to be upgraded or installed, you can use code like the following:
+ </div><div class="para">
+ h = readRpmHeader( ts, sys.argv[1] )
+ </div><div class="para">
+ </div><div class="para">
+ ts.addInstall(h, sys.argv[1], 'u')
+ </div><div class="para">
+ This example expects a package file name on the command line (accessed with sys.argv[1]), and reads in the package header using the readRpmHeader function introduced previously.
+ </div><div class="para">
+ The call to addInstall adds the header object (and the associated RPM package file) for an upgrade with the 'u' mode flag. The name of the package file, from sys.argv[1], is passed as the arbitrary data for the transaction set run callback function.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id773876" class="title">Transaction elements</h1></div></div></div><div class="para">
+ Transaction sets are made up of transaction elements. A transaction element makes up one part of a transaction and holds one package per operation (install or remove) in each transaction set. That is, there is one transaction element per package per operation in the transaction set. You can iterate over a transaction set to get each transaction element. Once you have a transaction element, you can call methods on each element to check entries in the header as well as get dependency sets for the package.
+ </div><div class="para">
+ Table 17-4 lists the informational methods you can call on a transaction element. Most of the methods listed in Table 17-4 return a single value.
+ </div><div class="para">
+ Table 17-4 Informational methods on transaction sets
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Method
+ </div>
+
+ </td><td>
+ <div class="para">
+ Returns
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ A
+ </div>
+
+ </td><td>
+ <div class="para">
+ Returns package architecture
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ E
+ </div>
+
+ </td><td>
+ <div class="para">
+ Returns package epoch
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ O
+ </div>
+
+ </td><td>
+ <div class="para">
+ Returns package operating system
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ R
+ </div>
+
+ </td><td>
+ <div class="para">
+ Returns package release number
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ V
+ </div>
+
+ </td><td>
+ <div class="para">
+ Returns package version
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ N
+ </div>
+
+ </td><td>
+ <div class="para">
+ Returns package name
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ NEVR
+ </div>
+
+ </td><td>
+ <div class="para">
+ Returns package name-epoch-version-release
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ DS
+ </div>
+
+ </td><td>
+ <div class="para">
+ Returns the package dependency set for a given tag
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ FI
+ </div>
+
+ </td><td>
+ <div class="para">
+ Returns the file info set for the package
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ For more complex checking, the DS method returns the package dependency set for a given tag:
+ </div><div class="para">
+ ds = te.DS(tag_name)
+ </div><div class="para">
+ Pass one of 'Providename', 'Requirename', 'Obsoletename', or 'Conflictname' for the tag name. For example:
+ </div><div class="para">
+ ds = te.DS('Requirename')
+ </div><div class="para">
+ The FI method returns the file info set for the package:
+ </div><div class="para">
+ fi = te.FI(tag_name)
+ </div><div class="para">
+ For the FI method, you must pass a tag name of 'Basenames'.
+ </div><div class="para">
+ As an example, Listing 17-6 shows how to iterate through a transaction set to get transaction elements.
+ </div><div class="para">
+ Listing 17-6: te.py
+ </div><div class="para">
+ #!/usr/bin/python
+ </div><div class="para">
+ </div><div class="para">
+ # Adds all package files on command line to a transaction
+ </div><div class="para">
+ # and prints out the transaction elements.
+ </div><div class="para">
+ # Usage:
+ </div><div class="para">
+ # python te.py rpm_file1.rpm rpm_file2.rpm ...
+ </div><div class="para">
+ #
+ </div><div class="para">
+ import rpm, os, sys
+ </div><div class="para">
+ </div><div class="para">
+ def readRpmHeader(ts, filename):
+ </div><div class="para">
+ """ Read an rpm header. """
+ </div><div class="para">
+ fd = os.open(filename, os.O_RDONLY)
+ </div><div class="para">
+ </div><div class="para">
+ h = ts.hdrFromFdno(fd)
+ </div><div class="para">
+ </div><div class="para">
+ os.close(fd)
+ </div><div class="para">
+ return h
+ </div><div class="para">
+ </div><div class="para">
+ </div><div class="para">
+ ts = rpm.TransactionSet()
+ </div><div class="para">
+ </div><div class="para">
+ # Set to not verify DSA signatures.
+ </div><div class="para">
+ ts.setVSFlags(rpm._RPMVSF_NOSIGNATURES)
+ </div><div class="para">
+ </div><div class="para">
+ for filename in sys.argv[1:]:
+ </div><div class="para">
+ h = readRpmHeader(ts, filename)
+ </div><div class="para">
+ print "Installing %s-%s-%s" % (h['name'], h['version'], h['release'])
+ </div><div class="para">
+ ts.addInstall(h, filename, 'i')
+ </div><div class="para">
+ </div><div class="para">
+ print "This will install:"
+ </div><div class="para">
+ for te in ts:
+ </div><div class="para">
+ print "%s-%s-%s" % (te.N(), te.V(), te.R() )
+ </div><div class="para">
+ </div><div class="para">
+ ts.check()
+ </div><div class="para">
+ ts.order()
+ </div><div class="para">
+ </div><div class="para">
+ print "This will install:"
+ </div><div class="para">
+ for te in ts:
+ </div><div class="para">
+ print "%s-%s-%s" % (te.N(), te.V(), te.R() )
+ </div><div class="para">
+ The te.py script sets up a transaction and then prints out the elements, never completing the transaction. The purpose here is just to show what is in the transaction. The second set of printed output shows the results of the check and order methods, covered in the following section.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id641465" class="title">Checking and reordering the transaction elements</h1></div></div></div><div class="para">
+ After you have called addInstall or addErase for each of the packages you want to install, upgrade, or remove, you need to call two methods to verify the transaction set and order all the elements properly. These two methods are check and order.
+ </div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id641477" class="title">Checking the Dependencies</h1></div></div></div><div class="para">
+ The check method checks the dependencies in a transaction set.
+ </div><div class="para">
+ unresolved_dependencies = ts.check()
+ </div><div class="para">
+ It returns None if all dependencies are resolved, or a complex tuple for each unresolved dependency. In general, if the check method returns anything but None, you cannot perform the transaction.
+ </div><div class="para">
+ On a dependency failure, check returns a complex tuple of the dependency information in the following format:
+ </div><div class="para">
+ ((N,V,R), (reqN, reqV), needsFlags, suggestedPackage, sense)
+ </div><div class="para">
+ The first element is a tuple of the name, version, and release of the package you are trying to install. The next tuple holds the required name and required version or conflicting name and version. The version will be None if the dependency is a shared library or other file.
+ </div><div class="para">
+ The needs flags tell you about the requirement or conflict. The value is a bitmask that can contain the following bit settings: rpm.RPMSENSE_EQUAL, rpm.RPMSENSE_GREATER, and rpm.RPMSENSE_LESS. This tells you if the dependency is for a version of a package greater than 4.1, for example.
+ </div><div class="para">
+ The suggested package names a package that solves the dependency. The packages considered are those for which you call addInstall with a flag of 'a'. This value will be None if there is no known package to solve this dependency.
+ </div><div class="para">
+ You can tell whether the dependency is a conflict or a requirement based on the sense value, one of rpm.RPMSENSE_CONFLICTS or rpm.RPMSENSE_REQUIRES.
+ </div><div class="para">
+ For example, the following tuple shows a required package:
+ </div><div class="para">
+ (('eruby-devel', '0.9.8', '2'), ('eruby-libs', '0.9.8'), 8, None, 0)
+ </div><div class="para">
+ The following tuple shows a required shared library:
+ </div><div class="para">
+ (('jpilot', '0.97', '1'), ('libpisock.so.3', None), 0, None, 0)
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ This tuple format will likely change in future versions of RPM. This example shows the format in RPM 4.1. With each RPM release, check the online documentation on the Python API to look for changes.
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id830289" class="title">Transaction Check Method Callbacks</h1></div></div></div><div class="para">
+ You can pass an optional callback function to the call to check. This callback gets called for each unresolved dependency in the transaction set. You can use this callback to try to automatically bring in required packages, for example.
+ </div><div class="para">
+ The basic syntax for the transaction check callback is:
+ </div><div class="para">
+ def checkCallback(ts, TagN, N, EVR, Flags):
+ </div><div class="para">
+ # Do something…
+ </div><div class="para">
+ You can use a check callback to automatically bring in packages that are required into a transaction set. You can bring in packages from the Red Hat RPM database package, which contains a database of all Red Hat packages, the rpmdb-redhat package. You can open the database from this package by using the trick described previously for opening transactions to more than one RPM database at a time. Simply set the _dbpath macro to "/usr/lib/rpmdb/i386-redhat-linux/redhat", or the location of your rpmdb-redhat database, and create a transaction set. Your check callback can then search this extra database and add packages from that database into the current, real RPM database.
+ </div><div class="para">
+ Your check callback can also attempt to find package files to resolve dependencies, from a disk directory or network archive for example. The following code shows a stub check callback that you can fill in to try to resolve dependencies. This callback sets up a format for finding unresolved packages in another RPM database, or elsewhere. You need to fill in the skeleton with the algorithm you want to actually resolve the dependencies.
+ </div><div class="para">
+ def checkCallback(ts, TagN, N, EVR, Flags):
+ </div><div class="para">
+ </div><div class="para">
+ if TagN == rpm.RPMTAG_REQUIRENAME:
+ </div><div class="para">
+ prev = ""
+ </div><div class="para">
+ Nh = None
+ </div><div class="para">
+ </div><div class="para">
+ if N[0] == '/':
+ </div><div class="para">
+ dbitag = 'basenames'
+ </div><div class="para">
+ else:
+ </div><div class="para">
+ dbitag = 'providename'
+ </div><div class="para">
+ </div><div class="para">
+ # What do you need to do.
+ </div><div class="para">
+ if EVR:
+ </div><div class="para">
+ print "Must find package [", N, "-", EVR, "]"
+ </div><div class="para">
+ else:
+ </div><div class="para">
+ print "Must find file [", N, "]"
+ </div><div class="para">
+ </div><div class="para">
+ if resolved:
+ </div><div class="para">
+ # ts.addIntall(h, h, 'i')
+ </div><div class="para">
+ </div><div class="para">
+ return -1
+ </div><div class="para">
+ </div><div class="para">
+ return 1
+ </div><div class="para">
+ Depending on the values passed to the callback, your code must either find a package itself or a package that provides a given file or capability to resolve the dependency. If you have another RPM database to look at, such as the rpmdb-redhat database, you can use dbMatch to find the necessary packages in that database. If, however, you are working with a directory of RPM files, you need to build up file names from the package name, version, and release.
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id565712" class="title">Reordering the Transaction Set</h1></div></div></div><div class="para">
+ You can add packages to a transaction set in any order. The order method reorders the transaction set to ensure that packages get installed or removed in the right order. The order method orders by a topological sort using the dependencies relations between objects with dependency comparisons.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ You must call check prior to order.
+ </div></div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id693782" class="title">Running the transaction</h1></div></div></div><div class="para">
+ After setting up the transaction set, perform the transaction by calling run. You need to provide two parameters:
+ </div><div class="para">
+ ts.run(callback, client_data)
+ </div><div class="para">
+ The callback parameter must be a Python function. The client_data is any data you want to pass to the callback. There may be more than one package in the transaction set, so this data should not be specific to a particular package.
+ </div><div class="para">
+ Warning
+ </div><div class="para">
+ You must not pass None as the client_data or you will get a Python error.
+ </div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id693811" class="title">Transaction run Method Callbacks</h1></div></div></div><div class="para">
+ The callback you pass to the run method on a transaction set is essential. Your callback must work properly, or the transaction will fail. You must provide a callback.
+ </div><div class="para">
+ Your callback will get called a number of times, mostly as a means to report progress. If you are writing a graphical user interface, for example, you can use the progress callbacks to update a visual progress meter.
+ </div><div class="para">
+ The basic syntax for the transaction set run callback is:
+ </div><div class="para">
+ def runCallback(reason, amount, total, key, client_data):
+ </div><div class="para">
+ # Do your stuff...
+ </div><div class="para">
+ The key is the data you provided in the call to the addInstall method. The client_data is the data you passed to the run method.
+ </div><div class="para">
+ Each time your callback is called, the transaction set will provide a reason flag. Table 17-5 lists the values for the reason parameter.
+ </div><div class="para">
+ Table 17-5 Transaction set run callback reason values
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Value
+ </div>
+
+ </td><td>
+ <div class="para">
+ Reason
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpm.RPMCALLBACK_UNKNOWN
+ </div>
+
+ </td><td>
+ <div class="para">
+ Unknown problem
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpm.RPMCALLBACK_INST_PROGRESS
+ </div>
+
+ </td><td>
+ <div class="para">
+ Progress for installation
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpm.RPMCALLBACK_INST_START
+ </div>
+
+ </td><td>
+ <div class="para">
+ Start of installation
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpm.RPMCALLBACK_INST_OPEN_FILE
+ </div>
+
+ </td><td>
+ <div class="para">
+ Callback should open package file
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpm.RPMCALLBACK_INST_CLOSE_FILE
+ </div>
+
+ </td><td>
+ <div class="para">
+ Callback should close package file
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpm.RPMCALLBACK_TRANS_PROGRESS
+ </div>
+
+ </td><td>
+ <div class="para">
+ Transaction progress
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpm.RPMCALLBACK_TRANS_START
+ </div>
+
+ </td><td>
+ <div class="para">
+ Transaction start
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpm.RPMCALLBACK_TRANS_STOP
+ </div>
+
+ </td><td>
+ <div class="para">
+ Transaction stop
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpm.RPMCALLBACK_UNINST_PROGRESS
+ </div>
+
+ </td><td>
+ <div class="para">
+ Uninstallation progress
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpm.RPMCALLBACK_UNINST_START
+ </div>
+
+ </td><td>
+ <div class="para">
+ Uninstallation start
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpm.RPMCALLBACK_UNINST_STOP
+ </div>
+
+ </td><td>
+ <div class="para">
+ Uninstallation stop
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpm.RPMCALLBACK_REPACKAGE_PROGRESS
+ </div>
+
+ </td><td>
+ <div class="para">
+ Repackaging progress
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpm.RPMCALLBACK_REPACKAGE_START
+ </div>
+
+ </td><td>
+ <div class="para">
+ Repackaging start
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpm.RPMCALLBACK_REPACKAGE_STOP
+ </div>
+
+ </td><td>
+ <div class="para">
+ Repackaging stop
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpm.RPMCALLBACK_UNPACK_ERROR
+ </div>
+
+ </td><td>
+ <div class="para">
+ Error unpacking package file
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpm.RPMCALLBACK_CPIO_ERROR
+ </div>
+
+ </td><td>
+ <div class="para">
+ cpio error getting package payload
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ Your callback must handle at least two cases: a reason value of rpm.RPMCALLBACK_INST_OPEN_FILE and rpm.RPMCALLBACK_INST_CLOSE_FILE.
+ </div><div class="para">
+ With the reason of rpm.RPMCALLBACK_INST_OPEN_FILE, you must open the RPM package file and return a file descriptor for the file. You need to keep this file descriptor in a global-scope or otherwise-accessible variable, because with the reason of rpm.RPMCALLBACK_INST_CLOSE_FILE, you must close this file.
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id760076" class="title">Coding A Sample Callback</h1></div></div></div><div class="para">
+ The following code shows a valid sample callback for upgrading and installing packages.
+ </div><div class="para">
+ # Global file descriptor for the callback.
+ </div><div class="para">
+ rpmtsCallback_fd = None
+ </div><div class="para">
+ </div><div class="para">
+ </div><div class="para">
+ def runCallback(reason, amount, total, key, client_data):
+ </div><div class="para">
+ </div><div class="para">
+ global rpmtsCallback_fd
+ </div><div class="para">
+ </div><div class="para">
+ if reason == rpm.RPMCALLBACK_INST_OPEN_FILE:
+ </div><div class="para">
+ print "Opening file. ", reason, amount, total, key, client_data
+ </div><div class="para">
+ rpmtsCallback_fd = os.open(client_data, os.O_RDONLY)
+ </div><div class="para">
+ return rpmtsCallback_fd
+ </div><div class="para">
+ elif reason == rpm.RPMCALLBACK_INST_START:
+ </div><div class="para">
+ print "Closing file. ", reason, amount, total, key, client_data
+ </div><div class="para">
+ os.close(rpmtsCallback_fd)
+ </div><div class="para">
+ This callback assumes that the call to addInstall passed client data of the package file name. This callback ignores the client_data passed to the run method, but this is a perfect slot for passing an object. You can use this, for example, to avoid having a global variable for the file descriptor.
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id722614" class="title">Upgrading A Package</h1></div></div></div><div class="para">
+ Listing 17-7 shows a simple Python script to upgrade or install a package.
+ </div><div class="para">
+ Listing 17-7: rpmupgrade.py
+ </div><div class="para">
+ #!/usr/bin/python
+ </div><div class="para">
+ </div><div class="para">
+ # Upgrades packages passed on the command line.
+ </div><div class="para">
+ # Usage:
+ </div><div class="para">
+ # python rpmupgrade.py rpm_file1.rpm rpm_file2.rpm ...
+ </div><div class="para">
+ #
+ </div><div class="para">
+ import rpm, os, sys
+ </div><div class="para">
+ </div><div class="para">
+ # Global file descriptor for the callback.
+ </div><div class="para">
+ rpmtsCallback_fd = None
+ </div><div class="para">
+ </div><div class="para">
+ </div><div class="para">
+ def runCallback(reason, amount, total, key, client_data):
+ </div><div class="para">
+ </div><div class="para">
+ global rpmtsCallback_fd
+ </div><div class="para">
+ </div><div class="para">
+ if reason == rpm.RPMCALLBACK_INST_OPEN_FILE:
+ </div><div class="para">
+ print "Opening file. ", reason, amount, total, key, client_data
+ </div><div class="para">
+ rpmtsCallback_fd = os.open(key, os.O_RDONLY)
+ </div><div class="para">
+ return rpmtsCallback_fd
+ </div><div class="para">
+ elif reason == rpm.RPMCALLBACK_INST_START:
+ </div><div class="para">
+ print "Closing file. ", reason, amount, total, key, client_data
+ </div><div class="para">
+ os.close(rpmtsCallback_fd)
+ </div><div class="para">
+ </div><div class="para">
+ </div><div class="para">
+ def checkCallback(ts, TagN, N, EVR, Flags):
+ </div><div class="para">
+ </div><div class="para">
+ if TagN == rpm.RPMTAG_REQUIRENAME:
+ </div><div class="para">
+ prev = ""
+ </div><div class="para">
+ Nh = None
+ </div><div class="para">
+ </div><div class="para">
+ if N[0] == '/':
+ </div><div class="para">
+ dbitag = 'basenames'
+ </div><div class="para">
+ else:
+ </div><div class="para">
+ dbitag = 'providename'
+ </div><div class="para">
+ </div><div class="para">
+ # What do you need to do.
+ </div><div class="para">
+ if EVR:
+ </div><div class="para">
+ print "Must find package [", N, "-", EVR, "]"
+ </div><div class="para">
+ else:
+ </div><div class="para">
+ print "Must find file [", N, "]"
+ </div><div class="para">
+ </div><div class="para">
+ if resolved:
+ </div><div class="para">
+ # ts.addIntall(h, h, 'i')
+ </div><div class="para">
+ </div><div class="para">
+ return -1
+ </div><div class="para">
+ </div><div class="para">
+ return 1
+ </div><div class="para">
+ </div><div class="para">
+ </div><div class="para">
+ </div><div class="para">
+ def readRpmHeader(ts, filename):
+ </div><div class="para">
+ """ Read an rpm header. """
+ </div><div class="para">
+ fd = os.open(filename, os.O_RDONLY)
+ </div><div class="para">
+ </div><div class="para">
+ h = ts.hdrFromFdno(fd)
+ </div><div class="para">
+ </div><div class="para">
+ os.close(fd)
+ </div><div class="para">
+ return h
+ </div><div class="para">
+ </div><div class="para">
+ </div><div class="para">
+ ts = rpm.TransactionSet()
+ </div><div class="para">
+ </div><div class="para">
+ # Set to not verify DSA signatures.
+ </div><div class="para">
+ ts.setVSFlags(-1)
+ </div><div class="para">
+ </div><div class="para">
+ for filename in sys.argv[1:]:
+ </div><div class="para">
+ h = readRpmHeader(ts, filename)
+ </div><div class="para">
+ print "Upgrading %s-%s-%s" % (h['name'], h['version'], h['release'])
+ </div><div class="para">
+ ts.addInstall(h, filename, 'u')
+ </div><div class="para">
+ </div><div class="para">
+ </div><div class="para">
+ unresolved_dependencies = ts.check(checkCallback)
+ </div><div class="para">
+ </div><div class="para">
+ if not unresolved_dependencies:
+ </div><div class="para">
+ ts.order()
+ </div><div class="para">
+ </div><div class="para">
+ print "This upgrade will install:"
+ </div><div class="para">
+ for te in ts:
+ </div><div class="para">
+ print "%s-%s-%s" % (te.N(), te.V(), te.R())
+ </div><div class="para">
+ </div><div class="para">
+ print "Running transaction (final step)..."
+ </div><div class="para">
+ ts.run(runCallback, 1)
+ </div><div class="para">
+ else:
+ </div><div class="para">
+ print "Error: Unresolved dependencies, transaction failed."
+ </div><div class="para">
+ print unresolved_dependencies
+ </div><div class="para">
+ This script expects the name of an RPM package file on the command line, and attempts to upgrade the package. (This will also install new packages.)
+ </div><div class="para">
+ When you run the rpmupgrade.py script, you should see output like the following:
+ </div><div class="para">
+ # rpm -q jikes
+ </div><div class="para">
+ jikes-1.17-1
+ </div><div class="para">
+ </div><div class="para">
+ # python rpmupgrade.py jikes-1.18-1.i386.rpm
+ </div><div class="para">
+ Upgrading jikes-1.18-1
+ </div><div class="para">
+ This upgrade will install:
+ </div><div class="para">
+ jikes-1.18-1
+ </div><div class="para">
+ jikes-1.17-1
+ </div><div class="para">
+ Running transaction (final step)...
+ </div><div class="para">
+ Opening file. 4 0 0 jikes-1.18-1.i386.rpm 1
+ </div><div class="para">
+ Closing file. 2 0 2854204 jikes-1.18-1.i386.rpm 1
+ </div><div class="para">
+ </div><div class="para">
+ # rpm -q jikes
+ </div><div class="para">
+ jikes-1.18-1
+ </div><div class="para">
+ This example shows that the package was upgraded after running the rpmupgrade.py script. Note that with an upgrade, the original package, jikes-1.17-1 in this case, is also added to the transaction set. With an install, this is not the case. That’s because the original package is removed as part of the transaction.
+ </div><div class="para">
+ If you run this script as a non-root user, you will likely see an error like the following:
+ </div><div class="para">
+ $ python rpmupgrade.py jikes-1.18-1.i386.rpm
+ </div><div class="para">
+ Upgrading jikes-1.18-1
+ </div><div class="para">
+ This upgrade will install:
+ </div><div class="para">
+ jikes-1.18-1
+ </div><div class="para">
+ jikes-1.17-1
+ </div><div class="para">
+ Running transaction (final step)...
+ </div><div class="para">
+ error: cannot get exclusive lock on /var/lib/rpm/Packages
+ </div><div class="para">
+ error: cannot open Packages index using db3 - Operation not permitted (1)
+ </div><div class="para">
+ error: cannot open Packages database in /var/lib/rpm
+ </div><div class="para">
+ If a package has a dependency on a file such as a shared library, you will see output like the following:
+ </div><div class="para">
+ # python rpmupgrade.py jikes-1.17-glibc2.2-1.i386.rpm jpilot-0_97-1_i386.rpm
+ </div><div class="para">
+ Upgrading jikes-1.17-1
+ </div><div class="para">
+ Upgrading jpilot-0.97-1
+ </div><div class="para">
+ Must find file [ libpisock.so.3 ]
+ </div><div class="para">
+ Error: Unresolved dependencies, transaction failed.
+ </div><div class="para">
+ (('jpilot', '0.97', '1'), ('libpisock.so.3', None), 0, None, 0)
+ </div><div class="para">
+ If a package has a dependency on another package, you will see output like the following:
+ </div><div class="para">
+ # python rpmupgrade.py eruby-devel-0.9.8-2.i386.rpm
+ </div><div class="para">
+ Upgrading eruby-devel-0.9.8-2
+ </div><div class="para">
+ Must find package [ eruby-libs - 0.9.8 ]
+ </div><div class="para">
+ Error: Unresolved dependencies, transaction failed.
+ </div><div class="para">
+ (('eruby-devel', '0.9.8', '2'), ('eruby-libs', '0.9.8'), 8, None, 0)
+ </div></div></div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id639900" class="title">Where to Go from Here</h1></div></div></div><div class="para">
+ The RPM bindings for Python are documented along with the C programming API. On a Red Hat Linux system, look in the file /usr/share/doc/rpm-devel-4.1/apidocs/html/group__python.html to see the start of the Python-specific documentation.
+ </div><div class="para">
+ Note that much of this online documentation covers the C functions that provide the Python bindings, not the Python API itself. But, if you examine the online information on objects listed as classes, such as rpmts, you can find the Python-specific documentation.
+ </div><div class="para">
+ Furthermore, if you look into the .c files that make up the Python bindings, you can find PyMethodDef structure tables. These tables provide useful glimpses into the Python API.
+ </div><div class="para">
+ To learn more about programming in Python, install the python-docs package. The python-docs package has a large set of online documentation for Python, including the official Python Tutorial. With Red Hat Linux, start at /usr/share/doc/python-docs-2.2.1/html/tut/tut.html.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ Other tutorials are available at http://diveintopython.org for the Dive Into Python tutorial for experienced programmers, and at http://py.vaults.ca/parnassus/apyllo.py/935043691.636055170 for the Vaults of Parnassus listing of tutorials.
+ </div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id587324" class="title">Summary</h1></div></div></div><div class="para">
+ This chapter introduces the high-level RPM API for Python programming. You can use this API from Python scripts to perform RPM functionality, just as you can write C programs using the RPM C API covered in <a class="xref" href="#ch-programming-c">Cap. 15, <em>Programming RPM with C</em></a> .
+ </div><div class="para">
+ In general, the Python API is simpler and requires fewer code statements than the corresponding functionality in the C API.
+ </div><div class="para">
+ Just about all of your work with the Python API requires a transaction set, which you can get by calling rpm.TransactionSet.
+ </div><div class="para">
+ To query the RPM database, call dbMatch on the transaction set object. To install or upgrade packages, call addInstall, check, order, and run on the transaction set.
+ </div><div class="para">
+ The next chapter switches to another language for accessing the RPM system: Perl. With the rich set of APIs, you can write your RPM programs in C, Python, Perl, or any language that can call on code written in one of these languages.
+ </div></div></div><div xml:lang="ro" class="chapter" id="ch-programming-perl" lang="ro"><div class="titlepage"><div><div><h2 class="title">Cap. 17. Programming RPM with Perl</h2></div></div></div><div class="toc"><dl><dt><span class="sect1"><a href="#id623163">17.1. Getting and Using the Perl RPM Modules</a></span></dt><dt><span class="sect1"><a href="#id699498">17.2. Working with RPM Files</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id725917">17.2.1. Opening package files</a></span></dt><dt><span class="sect2"><a href="#id690852">17.2.2. Listing tags from the package</a></span></dt><dt><span class="sect2"><a href="#id542112">17.2.3. Convenience methods</a></span></dt><dt><span class="sect2"><a href="#id764123">17.2.4. Listing the name and version</a></span></dt><dt><span class="sect2"><a href="#id803926">17.2.5. Checking whether the package is a source package</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id507880">17.3. Programming with the RPM D
atabase</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id668033">17.3.1. Opening the database</a></span></dt><dt><span class="sect2"><a href="#id578109">17.3.2. Finding packages</a></span></dt><dt><span class="sect2"><a href="#id578128">17.3.3. Iterating over packages</a></span></dt><dt><span class="sect2"><a href="#id639329">17.3.4. Additional query subroutines</a></span></dt><dt><span class="sect2"><a href="#id880328">17.3.5. Getting information on packages</a></span></dt><dt><span class="sect2"><a href="#id717333">17.3.6. Comparing versions</a></span></dt><dt><span class="sect2"><a href="#id591364">17.3.7. Closing the database</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id604517">17.4. Where to Go from Here</a></span></dt><dt><span class="sect1"><a href="#id798437">17.5. Summary</a></span></dt></dl></div><div class="para">
+ This chapter covers:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Using the RPM2 module to access information on package files
+ </div></li><li class="listitem"><div class="para">
+ Querying the RPM database from Perl
+ </div></li><li class="listitem"><div class="para">
+ Cross-referencing capabilities by the packages that provide and require capabilities
+ </div></li><li class="listitem"><div class="para">
+ Extracting information on packages
+ </div></li></ul></div><div class="para">
+ Perl is one of the most popular scripting languages. Used by system administrators, software developers, and a host of other users, Perl runs on many operating systems including Linux, UNIX, and Windows. Perl stands for Practical Extraction and Report Language, or sometimes Pathologically Eclectic Rubbish Lister.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ In the same vein, LISP stands for Lots of Irritating Single Parenthesis and COBOL for Completely Obnoxious Business Oriented Language.
+ </div><div class="para">
+ I began my book Cross-Platform Perl (John Wiley & Sons, 2000) by mentioning that when I first started learning Perl, I thought it was an evil plot. I still do. But it is a very practical evil plot. You can get a lot of work done with Perl, and quickly.
+ </div><div class="para">
+ Because of a long history of text processing, Perl is especially popular among system administrators. Perl also supports add-on packages, called modules. You can find thousands of add-on modules for text processing, networking, and a plethora of other tasks. There are so many modules available that some people who don’t like the Perl syntax script with Perl anyway, because the available modules save a lot of time.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ See search.cpan.org, the Comprehensive Perl Archive Network, for a listing of many Perl modules.
+ </div><div class="para">
+ This chapter covers working with RPM files and the RPM database using Perl. You can combine RPM usage with other Perl usage, such as generating HTML files or downloading RPMs over a network link.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ Many of the RPM tools covered in <a class="xref" href="#ch-management-software">Cap. 7, <em>RPM Management Software</em></a> are written in Perl.
+ </div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id623163" class="title">Getting and Using the Perl RPM Modules</h1></div></div></div><div class="para">
+ A number of Perl RPM modules are available. No one module provides all the features you need, although with time, the Perl modules will consolidate into a few modules that most everyone uses. As of this writing, the RPM2 module, by Chip Turner of Red Hat, provides the most recent approach to working with the RPM system from Perl. This chapter covers the RPM2 module.
+ </div><div class="para">
+ Red Hat Linux 8.0 comes with a perl-RPM2 package, which you need to install to use this module. Otherwise, you can download the module from www.cpan.org. Install this module, as well as the perl module, which provides the Perl language interpreter. Once you have this module installed and the perl package installed, you are ready to go.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ The version of the perl-RPM2 package that ships with Red Hat Linux 8.0 has a bug in that it will not open package files that were created with the version of rpm that ships with Red Hat Linux 8.0. That is, the Perl module cannot read package files that ship with Red Hat Linux. You can read older package files, though. This problem only affects attempts to read .rpm files, not installed packages. The bug is related to reading signed packages but not having the GPG keys in the keyring. The latest version on search.cpan.org fixes this problem.
+ </div><div class="para">
+ The RPM2 module contains Perl methods to work on two types of RPM objects: RPM files and installed packages.
+ </div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id699498" class="title">Working with RPM Files</h1></div></div></div><div class="para">
+ The RPM2 module provides a top-level object, RPM2, that acts as an entry point into the module. From the RPM2 object, you either open the RPM database, covered in the "Programming with the RPM Database" section, or open an RPM package file, covered here.
+ </div><div class="para">
+ The first step in working with an RPM file is to open the file inside a Perl script.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id725917" class="title">Opening package files</h1></div></div></div><div class="para">
+ The open_package subroutine opens an RPM package file and returns a header object (an RPM2::Header). The basic syntax follows:
+ </div><div class="para">
+ my $header = RPM2->open_package( $filename );
+ </div><div class="para">
+ For example:
+ </div><div class="para">
+ my $header = RPM2->open_package("jikes-1.14-1-glibc-2.2.i386.rpm");
+ </div><div class="para">
+ After you’ve opened a package, you can perform a number of query operations on the header object returned by the open_package subroutine.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id690852" class="title">Listing tags from the package</h1></div></div></div><div class="para">
+ Each RPM package has information stored under a variety of tags, such as the package name under the NAME tag and the package long description under the DESCRIPTION tag.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ These are the same tags introduced with the --queryformat option to the rpm command discussed in <a class="xref" href="#ch-using-rpm-db">Cap. 4, <em>Using the RPM Database</em></a> .
+ </div><div class="para">
+ The tag subroutine returns the value of a given tag. For example, to get the name of the package, use the NAME tag:
+ </div><div class="para">
+ use RPM2;
+ </div><div class="para">
+ </div><div class="para">
+ my $header = RPM2->open_package("jikes-1.14-1-glibc-2.2.i386.rpm" );
+ </div><div class="para">
+ </div><div class="para">
+ print $header->tag("NAME"), "\n";
+ </div><div class="para">
+ Pulling this together, Listing 18-1 shows example script that lists the name and one-line short summary of a package file.
+ </div><div class="para">
+ Listing 18-1: rpmsum.pl
+ </div><div class="para">
+ #!/usr/bin/perl
+ </div><div class="para">
+ </div><div class="para">
+ #
+ </div><div class="para">
+ # Lists summary from an RPM package file
+ </div><div class="para">
+ # Usage:
+ </div><div class="para">
+ # rpmsum.pl package_name.rpm
+ </div><div class="para">
+ #
+ </div><div class="para">
+ use strict;
+ </div><div class="para">
+ use RPM2;
+ </div><div class="para">
+ </div><div class="para">
+ my $header = RPM2->open_package( $ARGV[0] );
+ </div><div class="para">
+ </div><div class="para">
+ print $header->tag("NAME"), ": ", $header->tag("SUMMARY"), "\n";
+ </div><div class="para">
+ Enter this script and name the file rpmsum.pl.
+ </div><div class="para">
+ When you run this script, you need to pass the name of a package file on the command line. For example:
+ </div><div class="para">
+ $ ./rpmsum.pl jikes-1.14-1-glibc-2.2.i386.rpm
+ </div><div class="para">
+ jikes: java source to bytecode compiler
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id542112" class="title">Convenience methods</h1></div></div></div><div class="para">
+ The RPM2 module includes convenience methods for all RPM tags. This means you can use the method name in place of tag("NAME"). For example:
+ </div><div class="para">
+ print $header->name(), ": ", $header->summary(), "\n";
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id764123" class="title">Listing the name and version</h1></div></div></div><div class="para">
+ The RPM2 module provides a handy subroutine for getting the NAME, VERSION, RELEASE, and EPOCH tags, often abbreviated as NVRE. The subroutine, as_nvre, returns a single string with these values in the standard format, with the values separated by minus signs.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ Usually, the EPOCH tag has no value. If there is an EPOCH value, you will see it output first, and then a colon, and then the name, version, and release values. For example:
+ </div><div class="para">
+ 5:redhat-config-httpd-1.0.1-13
+ </div><div class="para">
+ In this case, the EPOCH value is 5.
+ </div><div class="para">
+ You can call this subroutine on any header object, or any package object to get the full name of the package. For example:
+ </div><div class="para">
+ print $header->as_nvre(), "\n";
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id803926" class="title">Checking whether the package is a source package</h1></div></div></div><div class="para">
+ Another handy subroutine tells you if an RPM file represents a source RPM or a binary RPM. The is_source_package subroutine returns a true value if the package is a source package, and a false value otherwise.
+ </div><div class="para">
+ The rpmpkg.pl script, shown in Listing 18-2, shows how to use the as_nvre and is_source_package subroutines.
+ </div><div class="para">
+ Listing 18-2: rpmpkg.pl
+ </div><div class="para">
+ #!/usr/bin/perl
+ </div><div class="para">
+ </div><div class="para">
+ #
+ </div><div class="para">
+ # Queries RPM package file and prints
+ </div><div class="para">
+ # out name and whether this is a source pkg.
+ </div><div class="para">
+ # Usage:
+ </div><div class="para">
+ # rpmpkg.pl package_name
+ </div><div class="para">
+ #
+ </div><div class="para">
+ use strict;
+ </div><div class="para">
+ use RPM2;
+ </div><div class="para">
+ </div><div class="para">
+ my $header = RPM2->open_package( $ARGV[0] );
+ </div><div class="para">
+ </div><div class="para">
+ if ( $header->is_source_package() ) {
+ </div><div class="para">
+ print "Source package ", $header->as_nvre(), "\n";
+ </div><div class="para">
+ } else {
+ </div><div class="para">
+ print $header->as_nvre(), "\n";
+ </div><div class="para">
+ }
+ </div></div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id507880" class="title">Programming with the RPM Database</h1></div></div></div><div class="para">
+ In addition to providing query routines for RPM files, you can also access the RPM database with the RPM2 package.
+ </div><div class="para">
+ To access the RPM database, your Perl script must first open the database.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id668033" class="title">Opening the database</h1></div></div></div><div class="para">
+ Open the RPM database with a call to open_rpm_db on the RPM2 object. For example:
+ </div><div class="para">
+ my $rpm_db = RPM2->open_rpm_db();
+ </div><div class="para">
+ You can also specify the directory where the RPM database resides. This is most useful for accessing a database in a non-standard location. For example:
+ </div><div class="para">
+ my $rpm_db = RPM2->open_rpm_db( "-path" => "/var/lib/rpm" );
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ The -path is normally used as a Perl bareword but is shown here as a string.
+ </div><div class="para">
+ Once you have an RPM database object, you can call one of the find subroutines to find packages in most of the same ways as supported by the rpm –q command.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id578109" class="title">Finding packages</h1></div></div></div><div class="para">
+ The find_by_name subroutine finds a package or packages by name. It returns a Perl list of the entries found. For example, if you installed more than one version of a package, find_by_name would return a list of all the packages at the different versions.
+ </div><div class="para">
+ Similar to find_by_name, find_by_name_iter returns an iterator to iterate over the packages that match the query. The iterator approach is usually more efficient.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id578128" class="title">Iterating over packages</h1></div></div></div><div class="para">
+ Iterators are important in the RPM2 package because they provide a more efficient interface to potentially large sets of packages, and because iterators more closely match the underlying C API. Furthermore, iterators are very easy to use. Simply call the next subroutine to move ahead to the next element, that is, the next package.
+ </div><div class="para">
+ For example:
+ </div><div class="para">
+ my $pkg_iter = $rpm_db->find_by_name_iter( "kernel" );
+ </div><div class="para">
+ </div><div class="para">
+ while (my $pkg = $pkg_iter->next() ) {
+ </div><div class="para">
+ </div><div class="para">
+ # Do something ...
+ </div><div class="para">
+ }
+ </div><div class="para">
+ Listing 18-3 shows a script that acts much like the rpm –q command, without any other command-line options.
+ </div><div class="para">
+ Listing 18-3: rpmname.pl
+ </div><div class="para">
+ #!/usr/bin/perl
+ </div><div class="para">
+ </div><div class="para">
+ #
+ </div><div class="para">
+ # Queries RPM database for given package.
+ </div><div class="para">
+ # Usage:
+ </div><div class="para">
+ # rpmname.pl package_name
+ </div><div class="para">
+ #
+ </div><div class="para">
+ use strict;
+ </div><div class="para">
+ use RPM2;
+ </div><div class="para">
+ </div><div class="para">
+ my $rpm_db = RPM2->open_rpm_db( "−path" => "/var/lib/rpm" );
+ </div><div class="para">
+ </div><div class="para">
+ my $pkg_iter = $rpm_db->find_by_name_iter( $ARGV[0] );
+ </div><div class="para">
+ </div><div class="para">
+ while (my $pkg = $pkg_iter->next() ) {
+ </div><div class="para">
+ </div><div class="para">
+ print $pkg->tag("NAME"), "-", $pkg->tag("VERSION"), "\n";
+ </div><div class="para">
+ }
+ </div><div class="para">
+ </div><div class="para">
+ $rpm_db->close_rpm_db();
+ </div><div class="para">
+ When you run this script, you need to pass the name of a package to query. For example:
+ </div><div class="para">
+ $ ./rpmname.pl kernel
+ </div><div class="para">
+ kernel-2.4.18
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id639329" class="title">Additional query subroutines</h1></div></div></div><div class="para">
+ The find_by_name_iter subroutine finds a package by its name. The RPM2 module also supports a number of other query routines, listed in Table 18-1.
+ </div><div class="para">
+ Table 18-1 RPM2 module query routines
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Routine
+ </div>
+
+ </td><td>
+ <div class="para">
+ Usage
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ find_all()
+ </div>
+
+ </td><td>
+ <div class="para">
+ Returns a list with all the packages in the database
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ find_all_iter()
+ </div>
+
+ </td><td>
+ <div class="para">
+ Returns an iterator over all the packages in the database
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ find_by_file($filename)
+ </div>
+
+ </td><td>
+ <div class="para">
+ Finds all packages that own the given file, returning a list
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ find_by_file_iter($filename)
+ </div>
+
+ </td><td>
+ <div class="para">
+ Finds all packages that own the given file, returning an iterator
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ find_by_name($package_name)
+ </div>
+
+ </td><td>
+ <div class="para">
+ Finds all packages with the given name, returning a list
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ find_by_name_iter($package_name)
+ </div>
+
+ </td><td>
+ <div class="para">
+ Finds all packages with the given name, returning an iterator
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ find_by_provides($capability)
+ </div>
+
+ </td><td>
+ <div class="para">
+ Finds all packages that provide the given capability, returning a list
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ find_by_provides_iter($capability)
+ </div>
+
+ </td><td>
+ <div class="para">
+ Finds all packages that provide the given capability, returning an iterator
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ find_by_requires($capability)
+ </div>
+
+ </td><td>
+ <div class="para">
+ Finds all packages that require the given capability, returning a list
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ find_by_requires_iter($capability)
+ </div>
+
+ </td><td>
+ <div class="para">
+ Finds all packages that require the given capability, returning an iterator
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ To verify the find routines, you can try the following script and compare the results with the rpm command. Listing 18-4 shows the script that finds what package provides a capability and also which packages require the capability.
+ </div><div class="para">
+ Listing 18-4: rpmprovides.pl
+ </div><div class="para">
+ #!/usr/bin/perl
+ </div><div class="para">
+ </div><div class="para">
+ #
+ </div><div class="para">
+ # Queries RPM database for given package,
+ </div><div class="para">
+ # listing what it provides and what other
+ </div><div class="para">
+ # packages require the capability.
+ </div><div class="para">
+ #
+ </div><div class="para">
+ # Usage:
+ </div><div class="para">
+ # rpmprovides.pl package_name
+ </div><div class="para">
+ #
+ </div><div class="para">
+ use strict;
+ </div><div class="para">
+ use RPM2;
+ </div><div class="para">
+ </div><div class="para">
+ my $rpm_db = RPM2->open_rpm_db();
+ </div><div class="para">
+ </div><div class="para">
+ my $pkg_iter = $rpm_db->find_by_provides_iter( $ARGV[0] );
+ </div><div class="para">
+ </div><div class="para">
+ print "Provides: ", $ARGV[0], "\n";
+ </div><div class="para">
+ </div><div class="para">
+ while (my $pkg = $pkg_iter->next() ) {
+ </div><div class="para">
+ print "\t", $pkg->as_nvre(), "\n";
+ </div><div class="para">
+ }
+ </div><div class="para">
+ </div><div class="para">
+ </div><div class="para">
+ # Now, what packages require this capability.
+ </div><div class="para">
+ </div><div class="para">
+ my $pkg_iter2 = $rpm_db->find_by_requires_iter( $ARGV[0] );
+ </div><div class="para">
+ </div><div class="para">
+ print "Requires: ", $ARGV[0], "\n";
+ </div><div class="para">
+ while (my $pkg2 = $pkg_iter2->next() ) {
+ </div><div class="para">
+ print "\t", $pkg2->as_nvre(), "\n";
+ </div><div class="para">
+ }
+ </div><div class="para">
+ </div><div class="para">
+ $rpm_db->close_rpm_db();
+ </div><div class="para">
+ When you run this script with the name of a capability, you'll see output like the following:
+ </div><div class="para">
+ $ ./rpmprovides.pl httpd
+ </div><div class="para">
+ Provides: httpd
+ </div><div class="para">
+ httpd-2.0.40-8
+ </div><div class="para">
+ Requires: httpd
+ </div><div class="para">
+ mod_perl-1.99_05-3
+ </div><div class="para">
+ 5:redhat-config-httpd-1.0.1-13
+ </div><div class="para">
+ mod_python-3.0.0-10
+ </div><div class="para">
+ 1:mod_ssl-2.0.40-8
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ The 5: in 5:redhat-config-httpd-1.0.1-13 and 1: in 1:mod_ssl-2.0.40-8 represent the EPOCH tag value.
+ </div><div class="para">
+ To verify this script, run the rpm -q command to see if you get the same packages listed. For example:
+ </div><div class="para">
+ $ rpm -q --whatprovides httpd
+ </div><div class="para">
+ httpd-2.0.40-8
+ </div><div class="para">
+ </div><div class="para">
+ $ rpm -q --whatrequires httpd
+ </div><div class="para">
+ mod_perl-1.99_05-3
+ </div><div class="para">
+ redhat-config-httpd-1.0.1-13
+ </div><div class="para">
+ mod_python-3.0.0-10
+ </div><div class="para">
+ mod_ssl-2.0.40-8
+ </div><div class="para">
+ In both cases, you see the same packages listed. You can use this technique to verify your scripts.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ The find_by_provides_iter subroutine requires the name of a package, such as bash. You cannot pass a file name, such as /bin/bash, to get the name of the package that provides this capability (a file, really).
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id880328" class="title">Getting information on packages</h1></div></div></div><div class="para">
+ The tag, as_nvre, and is_source_package subroutines that worked on header objects read from RPM files, shown previously, also work with package entries returned from the RPM database.
+ </div><div class="para">
+ For example, Listing 18-5 shows a script, rpminfo.pl, that prints out descriptive information about a given package.
+ </div><div class="para">
+ Listing 18-5: rpminfo.pl
+ </div><div class="para">
+ #!/usr/bin/perl
+ </div><div class="para">
+ </div><div class="para">
+ #
+ </div><div class="para">
+ # Queries RPM database for given package and prints info.
+ </div><div class="para">
+ # Usage:
+ </div><div class="para">
+ # rpminfo.pl package_name
+ </div><div class="para">
+ #
+ </div><div class="para">
+ use strict;
+ </div><div class="para">
+ use RPM2;
+ </div><div class="para">
+ </div><div class="para">
+ my $rpm_db = RPM2->open_rpm_db( "-path" => "/var/lib/rpm" );
+ </div><div class="para">
+ </div><div class="para">
+ my $pkg_iter = $rpm_db->find_by_name_iter( $ARGV[0] );
+ </div><div class="para">
+ </div><div class="para">
+ while (my $pkg = $pkg_iter->next() ) {
+ </div><div class="para">
+ </div><div class="para">
+ printInfo( $pkg );
+ </div><div class="para">
+ }
+ </div><div class="para">
+ </div><div class="para">
+ $rpm_db->close_rpm_db();
+ </div><div class="para">
+ </div><div class="para">
+ </div><div class="para">
+ # Prints info on one package.
+ </div><div class="para">
+ sub printInfo {
+ </div><div class="para">
+ my($pkg) = shift;
+ </div><div class="para">
+ </div><div class="para">
+ print $pkg->as_nvre(), ", ", $pkg->tag("ARCH"), ", ",
+ </div><div class="para">
+ $pkg->tag("OS"), ", ", $pkg->tag("PLATFORM"), "\n";
+ </div><div class="para">
+ </div><div class="para">
+ print $pkg->tag("SUMMARY"), "\n";
+ </div><div class="para">
+ print "Group: ", $pkg->tag("GROUP"), "\n";
+ </div><div class="para">
+ print $pkg->tag("DESCRIPTION"), "\n";
+ </div><div class="para">
+ print "Vendor: ", $pkg->tag("VENDOR"), ", ", $pkg->tag("URL"), "\n";
+ </div><div class="para">
+ print "Size: ", $pkg->tag("SIZE"), "\n";
+ </div><div class="para">
+ }
+ </div><div class="para">
+ When you run this script, you’ll see output like the following:
+ </div><div class="para">
+ $ ./rpminfo.pl XFree86
+ </div><div class="para">
+ XFree86-4.2.0-72, i386, linux, i386-redhat-linux-gnu
+ </div><div class="para">
+ The basic fonts, programs and docs for an X workstation.
+ </div><div class="para">
+ Group: User Interface/X
+ </div><div class="para">
+ XFree86 is an open source implementation of the X Window System. It
+ </div><div class="para">
+ provides the basic low level functionality which full fledged
+ </div><div class="para">
+ graphical user interfaces (GUIs) such as GNOME and KDE are designed
+ </div><div class="para">
+ upon.
+ </div><div class="para">
+ Vendor: Red Hat, Inc., http://www.xfree86.org
+ </div><div class="para">
+ Size: 30552239
+ </div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id637715" class="title">Listing the Installed Date</h1></div></div></div><div class="para">
+ The installed date is a number value representing the number of seconds since the start of the UNIX epoch, January 1, 1970, which predates the start of the Linux epoch by about 20 years. So, when you get the value of the INSTALLTIME tag, you’ll see a meaningless number.
+ </div><div class="para">
+ To make sense of this number, pass the value to the Perl localtime function. Listing 18-6 shows an example of this.
+ </div><div class="para">
+ Listing 18-6: rpmdate.pl
+ </div><div class="para">
+ #!/usr/bin/perl
+ </div><div class="para">
+ </div><div class="para">
+ #
+ </div><div class="para">
+ # Queries RPM database for given package,
+ </div><div class="para">
+ # prints out name, vendor, and date installed.
+ </div><div class="para">
+ # Usage:
+ </div><div class="para">
+ # rpmdate.pl package_name
+ </div><div class="para">
+ #
+ </div><div class="para">
+ use strict;
+ </div><div class="para">
+ use RPM2;
+ </div><div class="para">
+ </div><div class="para">
+ my $rpm_db = RPM2->open_rpm_db();
+ </div><div class="para">
+ </div><div class="para">
+ my $pkg_iter = $rpm_db->find_by_name_iter( $ARGV[0] );
+ </div><div class="para">
+ </div><div class="para">
+ while (my $pkg = $pkg_iter->next() ) {
+ </div><div class="para">
+ </div><div class="para">
+ printDate( $pkg );
+ </div><div class="para">
+ }
+ </div><div class="para">
+ </div><div class="para">
+ $rpm_db->close_rpm_db();
+ </div><div class="para">
+ </div><div class="para">
+ </div><div class="para">
+ </div><div class="para">
+ # Prints installation data for one package.
+ </div><div class="para">
+ sub printDate {
+ </div><div class="para">
+ my($pkg) = shift;
+ </div><div class="para">
+ </div><div class="para">
+ my $date = localtime( $pkg->tag("INSTALLTIME") );
+ </div><div class="para">
+ </div><div class="para">
+ printf("%-20s %-17s %s\n", $pkg->as_nvre(), $pkg->tag("VENDOR"), $date);
+ </div><div class="para">
+ }
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ The printf function in this script can do something the rpm command cannot do. Even with the --queryformat option, you cannot group multiple items and then set the size; with Perl, you can. Simply assign the multiple values to a string, or use the handy as_nvre subroutine, which gathers up to four tags together into one string.
+ </div><div class="para">
+ When you pass the name of a package to this script, you’ll see the date the package was installed. For example:
+ </div><div class="para">
+ $ ./rpmdate.pl kernel
+ </div><div class="para">
+ kernel-2.4.18-14 Red Hat, Inc. Sat Oct 5 12:29:58 2002
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id771826" class="title">Handling String Array Tags</h1></div></div></div><div class="para">
+ Not only is the date stored in a format that adds complication to your script. A number of tags are string arrays, not scalar strings. This means you may see output that is all mashed together.
+ </div><div class="para">
+ To help deal with this, the following subroutine takes in an array of strings and returns a string that is built using a passed-in delimiter:
+ </div><div class="para">
+ sub arrayToString {
+ </div><div class="para">
+ my($sep) = shift;
+ </div><div class="para">
+ my(@array) = @_;
+ </div><div class="para">
+ my($str);
+ </div><div class="para">
+ </div><div class="para">
+ $str = $array[0];
+ </div><div class="para">
+ </div><div class="para">
+ for ( $i = 1; $i < $#array; $i++ )
+ </div><div class="para">
+ {
+ </div><div class="para">
+ $str = $str . $sep . $array[$i];
+ </div><div class="para">
+ }
+ </div><div class="para">
+ </div><div class="para">
+ return $str;
+ </div><div class="para">
+ }
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ Show your Perl expertise and earn extra points by implementing the arrayToString subroutine as a single Perl statement that uses the join function.
+ </div><div class="para">
+ The following list shows the tags that are an array of strings:
+ </div><div class="para">
+ *BASENAMES
+ </div><div class="para">
+ *CHANGELOGNAME
+ </div><div class="para">
+ *CHANGELOGTEXT
+ </div><div class="para">
+ *DIRNAMES
+ </div><div class="para">
+ *FILEGROUPNAME
+ </div><div class="para">
+ *FILELANGS
+ </div><div class="para">
+ *FILELINKTOS
+ </div><div class="para">
+ *FILEMD5S
+ </div><div class="para">
+ *FILEUSERNAME
+ </div><div class="para">
+ *OLDFILENAMES
+ </div><div class="para">
+ *PROVIDENAME
+ </div><div class="para">
+ *PROVIDEVERSION
+ </div><div class="para">
+ *REQUIRENAME
+ </div><div class="para">
+ *REQUIREVERSION
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ <a class="xref" href="#ch-using-rpm-db">Cap. 4, <em>Using the RPM Database</em></a> covers more on these tags.
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id872976" class="title">Listing the Files In A Package</h1></div></div></div><div class="para">
+ The files subroutine provides a list of all the files in a package. Listing 18-7 shows how to access this list.
+ </div><div class="para">
+ Listing 18-7: rpmfiles.pl
+ </div><div class="para">
+ #!/usr/bin/perl
+ </div><div class="para">
+ </div><div class="para">
+ #
+ </div><div class="para">
+ # Queries RPM database for given package,
+ </div><div class="para">
+ # prints out the files in the package.
+ </div><div class="para">
+ # Usage:
+ </div><div class="para">
+ # rpmfiles.pl package_name
+ </div><div class="para">
+ #
+ </div><div class="para">
+ use strict;
+ </div><div class="para">
+ use RPM2;
+ </div><div class="para">
+ </div><div class="para">
+ my $rpm_db = RPM2->open_rpm_db();
+ </div><div class="para">
+ </div><div class="para">
+ my $pkg_iter = $rpm_db->find_by_name_iter( $ARGV[0] );
+ </div><div class="para">
+ </div><div class="para">
+ while (my $pkg = $pkg_iter->next() ) {
+ </div><div class="para">
+ </div><div class="para">
+ printFiles( $pkg );
+ </div><div class="para">
+ }
+ </div><div class="para">
+ </div><div class="para">
+ $rpm_db->close_rpm_db();
+ </div><div class="para">
+ </div><div class="para">
+ </div><div class="para">
+ </div><div class="para">
+ # Prints installation data for one package.
+ </div><div class="para">
+ sub printFiles {
+ </div><div class="para">
+ my($pkg) = shift;
+ </div><div class="para">
+ </div><div class="para">
+ my $files = arrayToString("\n", $pkg->files() );
+ </div><div class="para">
+ </div><div class="para">
+ print "Files:\n", $files, "\n";
+ </div><div class="para">
+ }
+ </div><div class="para">
+ </div><div class="para">
+ sub arrayToString {
+ </div><div class="para">
+ my($sep) = shift;
+ </div><div class="para">
+ my(@array) = @_;
+ </div><div class="para">
+ my($str);
+ </div><div class="para">
+ </div><div class="para">
+ $str = $array[0];
+ </div><div class="para">
+ </div><div class="para">
+ for ( my $i = 1; $i < $#array; $i++ )
+ </div><div class="para">
+ {
+ </div><div class="para">
+ $str = $str . $sep . $array[$i];
+ </div><div class="para">
+ }
+ </div><div class="para">
+ </div><div class="para">
+ return $str;
+ </div><div class="para">
+ }
+ </div><div class="para">
+ When you run this script, you’ll see output like the following:
+ </div><div class="para">
+ $ ./rpmfiles.pl jikes
+ </div><div class="para">
+ Files:
+ </div><div class="para">
+ /usr/bin/jikes
+ </div><div class="para">
+ /usr/doc/jikes-1.17/license.htm
+ </div></div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id717333" class="title">Comparing versions</h1></div></div></div><div class="para">
+ The RPM2 module overrides the spaceship operator, <=>, to perform version comparisons between packages. The script in Listing 18-8 shows how to compare all local RPM files against the newest installed version of the same package, if the package is installed.
+ </div><div class="para">
+ Listing 18-8: rpmver.pl
+ </div><div class="para">
+ #!/usr/bin/perl -w
+ </div><div class="para">
+ </div><div class="para">
+ #
+ </div><div class="para">
+ # Compare versions of all *.rpm files against the
+ </div><div class="para">
+ # latest packages installed (if installed)
+ </div><div class="para">
+ #
+ </div><div class="para">
+ # Usage:
+ </div><div class="para">
+ # rpmver.pl
+ </div><div class="para">
+ # This script looks for all *.rpm files.
+ </div><div class="para">
+ #
+ </div><div class="para">
+ use strict;
+ </div><div class="para">
+ use RPM2;
+ </div><div class="para">
+ </div><div class="para">
+ my $rpm_db = RPM2->open_rpm_db();
+ </div><div class="para">
+ </div><div class="para">
+ for my $filename (<*.rpm>) {
+ </div><div class="para">
+ my $h = RPM2->open_package( $filename );
+ </div><div class="para">
+ </div><div class="para">
+ # Ensure we compare against the newest
+ </div><div class="para">
+ # package of the given name.
+ </div><div class="para">
+ my ($installed) =
+ </div><div class="para">
+ sort { $b <=> $a } $rpm_db->find_by_name($h->name);
+ </div><div class="para">
+ </div><div class="para">
+ if (not $installed) {
+ </div><div class="para">
+ printf "Package %s not installed.\n", $h->as_nvre;
+ </div><div class="para">
+ } else {
+ </div><div class="para">
+ my ($result) = ($h <=> $installed);
+ </div><div class="para">
+ </div><div class="para">
+ if ($result < 0) {
+ </div><div class="para">
+ printf "Installed package %s newer than file %s\n",
+ </div><div class="para">
+ $installed->as_nvre,
+ </div><div class="para">
+ $h->as_nvre;
+ </div><div class="para">
+ } else {
+ </div><div class="para">
+ printf "File %s newer than installed package %s\n",
+ </div><div class="para">
+ $h->as_nvre,
+ </div><div class="para">
+ $installed->as_nvre;
+ </div><div class="para">
+ }
+ </div><div class="para">
+ }
+ </div><div class="para">
+ }
+ </div><div class="para">
+ The sort { $a <=> $b } in front of the find_by_name call sorts all the packages of that name by the version number, so that the comparison is performed against the newest installed version of the package. The ($h <=> $installed) compares the header from the RPM file on disk against the newest installed version of the package.
+ </div><div class="para">
+ When you run this script, you’ll see output like the following, depending on which RPM files you have in the local directory:
+ </div><div class="para">
+ $ perl rpmver.pl
+ </div><div class="para">
+ Package acroread-4.0-0 not installed.
+ </div><div class="para">
+ Package canvas-7.0b2.0-1 not installed.
+ </div><div class="para">
+ Installed package jikes-1.18-1 newer than file jikes-1.14-1
+ </div><div class="para">
+ Installed package SDL-1.2.4-5 newer than file SDL-0.9.9-4
+ </div><div class="para">
+ Package ted-2.8-1 not installed.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id591364" class="title">Closing the database</h1></div></div></div><div class="para">
+ When you are done with the RPM database, call close_rpm_db, as shown following:
+ </div><div class="para">
+ $rpm_db->close_rpm_db();
+ </div><div class="para">
+ Note that this call is not necessary, as the RPM2 module will close the database when the object, in this case $rpm_db, goes out of scope.
+ </div></div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id604517" class="title">Where to Go from Here</h1></div></div></div><div class="para">
+ One of the strengths of Perl is that there are so many add-on packages available. In addition, Perl is really strong in text processing. You can combine these strengths to provide cleaner output for RPM database queries, for example, avoiding the complex syntax for the --queryformat option to the rpm command. Perl can do more than the --queryformat option allows. For example, you can combine multiple values together into a Perl string and then format the output. The --queryformat option only allows formatting on each value individually, not groups of values.
+ </div><div class="para">
+ In addition, you can combine one of the Perl templating modules, such as Text::Template or HTML::Template, to create an HTML page for a given package. You could use Perl to create formatted HTML pages for all the installed packages on your system, with HTML links to cross-reference all the dependencies.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ Download these modules from the CPAN site, www.cpan.org.
+ </div><div class="para">
+ This chapter covers the RPM2 module. Right now, the RPM2 module supports only querying packages and the RPM database. Future versions will likely add the ability to install, update, and remove packages.
+ </div><div class="para">
+ In addition to this module, you can find an RPM module with RPM::Header and RPM::Database classes. Another module, RPM::Specfile, provides the ability to turn Perl modules, such as those stored on CPAN, into RPM packages. The RPM::Specfile module helps create an RPM spec file for a Perl module.
+ </div><div class="para">
+ The Perl-RPM-Perlonly bundle provides an alternative version of the RPM::Header module written entirely in Perl with no usage of the C rpm library. This makes RPM access much easier on platforms for which you don’t have the RPM system.
+ </div><div class="para">
+ The RPM-Tools bundle includes RPM::Update, which compares the packages installed on your system (listed by calling rpm –qa) with the packages available on another system, that may be available only with a network link. This module can also update packages that are older than the designated master system. RPM::Make, also part of the RPM-Tools bundle, helps create RPM packages from a Perl script. This module does not support all the spec file options described in <a class="xref" href="#ch-specfiles">Cap. 9, <em>Working with Spec Files</em></a> , but it can help you make simple packages.
+ </div><div class="para">
+ You can download all these modules from the CPAN site.
+ </div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id798437" class="title">Summary</h1></div></div></div><div class="para">
+ This chapter introduces the RPM2 add-on module to allow Perl scripts to access information on RPM package files and in the RPM database. To access an RPM file and query information about that file, you need to call the open_package subroutine. Once you’ve opened the file, you can call the tag, as_nvre, is_source_package, and files subroutines on the header object to query data about the package.
+ </div><div class="para">
+ To access the RPM database, call open_rpm_db. Once you’ve opened the database, you can call one of the find subroutines, such as find_by_name or find_by_name_iter, to search for packages. The subroutines that have names ending with _iter, such as find_by_name_iter, return an iterator object to iterate over the packages found. The other find subroutines, such as find_by_name, return a Perl list of the packages found.
+ </div><div class="para">
+ You can then call the tag, as_nvre, and files subroutines on the package objects to query information about the packages.
+ </div><div class="para">
+ When you are done with the RPM database, call close_rpm_db.
+ </div></div></div><div xml:lang="ro" class="chapter" id="ch-other-linuxes" lang="ro"><div class="titlepage"><div><div><h2 class="title">Cap. 18. Using RPM on Non-Red Hat Linuxes</h2></div></div></div><div class="toc"><dl><dt><span class="sect1"><a href="#id811830">18.1. Troubleshooting RPM Installation Issues</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id601628">18.1.1. Dealing with RPM versions</a></span></dt><dt><span class="sect2"><a href="#id581595">18.1.2. Dealing with divisions of software into packages</a></span></dt><dt><span class="sect2"><a href="#id540699">18.1.3. Dealing with dependency issues</a></span></dt><dt><span class="sect2"><a href="#id589152">18.1.4. Dealing with install locations</a></span></dt><dt><span class="sect2"><a href="#id806921">18.1.5. When all else fails, rebuild from the source package</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id789105">18.2. Handling Problems Building RPMs</a></span></dt><dd><dl><dt><span clas
s="sect2"><a href="#id660708">18.2.1. Writing distribution-specific packages</a></span></dt><dt><span class="sect2"><a href="#id492519">18.2.2. Dealing with automatic dependency generation</a></span></dt><dt><span class="sect2"><a href="#id962201">18.2.3. Dealing with different macros</a></span></dt><dt><span class="sect2"><a href="#id649087">18.2.4. Making relocatable packages</a></span></dt><dt><span class="sect2"><a href="#id1317565">18.2.5. Creating an RPM build environment</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id571016">18.3. Dealing with Non-RPM-Based Linux Versions</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id571028">18.3.1. Handling non-RPM packages with alien</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id682499">18.4. Standardizing RPMs</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id682517">18.4.1. Filesystem Hierarchy Standard</a></span></dt><dt><span class="sect2"><a href="#id562919">18.4.2. RPM adoptio
n</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id772912">18.5. Summary</a></span></dt></dl></div><div class="para">
+ This chapter covers:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Dealing with RPM issues on other versions of Linux
+ </div></li><li class="listitem"><div class="para">
+ RPM standardization
+ </div></li><li class="listitem"><div class="para">
+ Working around RPM differences when installing RPMs
+ </div></li><li class="listitem"><div class="para">
+ Working around RPM differences when building RPMs
+ </div></li><li class="listitem"><div class="para">
+ Dealing with non-RPM-based Linux distributions
+ </div></li></ul></div><div class="para">
+ Although its name was originally the Red Hat Package Manager, RPM has been adopted by most major Linux distributions. With this adoption, RPM has moved from its Red Hat roots, and RPM now stands for the RPM Package Manager.
+ </div><div class="para">
+ In addition, the RPM package format is being adopted by the Linux Standards Base (LSB). The LSB defines a set of standards to help maintain compatibility for all Linux distributions.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ See www.linuxbase.org for more on the LSB.
+ </div><div class="para">
+ This chapter covers differences in how Linux distributions use RPM, ways to work around these differences, and also tools you can use for non-RPM distributions.
+ </div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id811830" class="title">Troubleshooting RPM Installation Issues</h1></div></div></div><div class="para">
+ The main RPM issues when dealing with installing RPMs on other versions of Linux are:
+ </div><div class="para">
+ *Different versions of RPM itself
+ </div><div class="para">
+ *Different divisions of software into packages
+ </div><div class="para">
+ *Dealing with dependency issues
+ </div><div class="para">
+ *Different install locations
+ </div><div class="para">
+ The following sections expand on these issues.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id601628" class="title">Dealing with RPM versions</h1></div></div></div><div class="para">
+ Red Hat Linux 8.0 ships with RPM version 4.1. Other distributions of Linux ship with other versions of RPM. Thus, one of the first commands you can run on another Linux distribution is the rpm --version command, to see what RPM version is in use and help identify any issues. For example:
+ </div><div class="para">
+ $ rpm --version
+ </div><div class="para">
+ RPM version 4.1
+ </div><div class="para">
+ Once you know the RPM version, you can plan for any issues that arise from installing RPMs made with a different RPM version. For example, RPM 4.0 and higher inserts dependency information automatically into RPMs. If your Linux distribution runs RPM 3.x, you may need to disable some of the dependency checks, for example, if you want to install RPMs built under RPM 4.x onto an RPM 3.x system.
+ </div><div class="para">
+ On installing RPMs, you can disable the dependency checks with the --nodeps option. If you do this, though, you should manually check that the dependencies are really met by your Linux installation.
+ </div><div class="para">
+ On the other hand, if you want to install RPMs built on an RPM 3.x system onto an RPM 4.x system, you may need to deal with package signatures. RPM 4.x versions also automatically check for signatures. When installing packages on an RPM 4.x system, you can disable this feature with the --nosignature option.
+ </div><div class="para">
+ Using these techniques, you should be able to install packages built with RPM 4.1 on systems that use RPM 3.x versions or vice versa.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id581595" class="title">Dealing with divisions of software into packages</h1></div></div></div><div class="para">
+ There is no standardization as to how large applications are divided into packages on different Linux distributions. This means that dependencies between packages may differ.
+ </div><div class="para">
+ If your dependencies are for packages provided with the Linux distribution, which includes a huge number of packages, you must address this issue. The package an RPM depends on may not exist and may not even be needed, on a particular Linux distribution.
+ </div><div class="para">
+ If instead the dependencies are for files, especially shared libraries, you should be okay for the most part, unless the files are located in different directories.
+ </div><div class="para">
+ The only real solution to this problem is to turn off dependency checks on installing, with the --nodeps option. Then you must check manually that your system really does provide all the necessary dependencies. Use the techniques shown in <a class="xref" href="#ch-dependencies">Cap. 5, <em>Package Dependencies</em></a> to verify all the dependencies are met on your system.
+ </div><div class="para">
+ Warning
+ </div><div class="para">
+ Using the --nodeps option can lead to problems with your RPM database, because you are installing packages by defeating the RPM system's safeguards for dependencies. Only use the --nodeps option if you are really sure the dependencies are met on your system, even if from a different package than expected.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id540699" class="title">Dealing with dependency issues</h1></div></div></div><div class="para">
+ One of the toughest areas to deal with is the problem of dependencies. This topic ranges from the very simple issue of installing a necessary package to complex issues of shared library versions or particular Perl modules.
+ </div><div class="para">
+ Start with the simple case and make certain that you haven’t failed to install a necessary RPM that provides the right dependency. In most cases, you can download a vendor-specific package from your Linux vendor, such as www.suse.com for SUSE Linux. Most Linux vendors provide HTTP or FTP sites with a large set of packages created for their distributions. If such a distribution-specific package solves a dependency issue, this is the easiest way around the problem.
+ </div><div class="para">
+ After you verify that you haven't simply omitted a necessary package, move on to other potential explanations. Another issue involves shared libraries and ELF, or Extended Linking Format, symbols. A package may require an older or newer version of a shared library. Applications that are tied to a particular version of a shared library can cause problems, since you may not want to install incompatible versions of a shared library.
+ </div><div class="para">
+ If the dependency is for a system-shared library, such as the shared C library, you can often recompile the package (rebuild from a source RPM) to get the package to use the newer or older version of the system library. This is possible because most Linux applications don’t call on version-specific features of system shared libraries (some do, but most don’t). If the dependency is for an application-shared library, this is more serious, since there were likely API changes that could impact the application. Install the package owning the application-shared library and again, try to rebuild the package from the source RPM.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ You can use the rpm -qf command to query which package owns a given file. You can use the rpm -q --whatprovides command to query for which package provides a given capability. <a class="xref" href="#ch-dependencies">Cap. 5, <em>Package Dependencies</em></a> covers more on dependencies.
+ </div><div class="para">
+ Some packages are considered developer packages. These usually depend on some base package. For example, the rpm-devel package depends on the rpm package. The rpm-python package depends on both the rpm package and the python package (at particular version numbers as well).
+ </div><div class="para">
+ This naming scheme of a base package and base-devel is used for Red Hat Linux packages, but may not be used for other vendor packages. In any case, you can solve this type of dependency by finding the relevant base packages that the package you are trying to install depends on. Consult the manuals that come with your Linux distribution or browse the online RPM repositories to see what naming conventions are used for your Linux distribution.
+ </div><div class="para">
+ Many packages depend on scripting language interpreters, such as Perl. Sometimes the dependency is based on scripts used in a package, such as install or trigger scripts. You can have problems arise with the locations of these scripting interpreters. Perl, for example, is usually installed in /usr/bin/perl on most Linux systems. Another common location is /usr/local/bin/perl. In addition, packages may depend on particular add-on modules, especially Perl modules. With most versions of Linux released in the last few years, you should be able to override a Perl dependency with the --nodeps option as long as you have Perl installed.
+ </div><div class="para">
+ File paths may also cause problems. For example, a file that a package depends on may be in a different location or owned by a different package. For this case, you can try to find the package that owns the file and make sure that package is installed. If your Linux vendor provides a pre-built RPM database of all packages, such as the rpmdb-redhat package, you can query this database to find out which package owns the file for that version of Linux.
+ </div><div class="para">
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id589152" class="title">Dealing with install locations</h1></div></div></div><div class="para">
+ Linux vendors can install software anywhere. For example, some distributions place a lot of software under /opt instead of the more common /usr. From an RPM perspective, this is mostly an issue with file dependencies and the install location for packages. Evolving file system standards also help limit this issue.
+ </div><div class="para">
+ You can attempt to relocate any package using the --badreloc option.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ <a class="xref" href="#ch-using-rpm">Cap. 3, <em>Using RPM</em></a> covers the --badreloc option.
+ </div><div class="para">
+ But, while the --badreloc option will relocate the files in a package, it will not modify the contents of those files. So, any file inside a package that references files and directory locations may not work properly, since it may have the old, invalid, paths.
+ </div><div class="para">
+ The only real way around this problem is to edit any script files that come with the package and contain hard-coded paths. If the paths reside inside binary executables, you need to get a source RPM for the package, patch the sources and then create a new RPM.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id806921" class="title">When all else fails, rebuild from the source package</h1></div></div></div><div class="para">
+ When all of these techniques fail to install a package, you still have a fallback option. If you have the source RPM for a package, you can install the source RPM on the new system and then edit the spec file until you can rebuild a package that will install on your version of Linux.
+ </div><div class="para">
+ For example, a set of Build Root Policy (brp) helper scripts are run at the end of the %install section in an RPM. These scripts perform tasks such as compressing man pages. The Mandrake brp scripts use bzip2 compression. Red Hat brp scripts use gzip compression. This is one case where rebuilding an RPM and then installing may work best.
+ </div></div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id789105" class="title">Handling Problems Building RPMs</h1></div></div></div><div class="para">
+ Given all these differences, how can you create RPMs while avoiding problems? With some work setting things up, you can create an RPM build environment that solves most vendor issues. This depends on taking a methodical approach to building your packages and using techniques to avoid vendor issues wherever possible.
+ </div><div class="para">
+ When building RPMs, you will face many of the same problems@@mdand solutions@@mdas when installing RPMs. For example, due to the different ways Linux vendors divide software into packages, your RPMs will likely have issues defining the proper dependencies. There are also a number of issues that apply only when building RPMs.
+ </div><div class="para">
+ The following sections cover the main issues when building RPMs.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id660708" class="title">Writing distribution-specific packages</h1></div></div></div><div class="para">
+ One of the ways around all the differences between Linux distributions in RPM usage is to define distribution-specific packages. To do this, you create a separate package on each Linux distribution you support.
+ </div><div class="para">
+ That’s a lot of work. If possible, fit the differences into macros and use a single spec file to reduce some of this work. This technique works up to a point. Sometimes, your spec file becomes too complicated and you may decide that it is easier to create multiple spec files, one per Linux distribution.
+ </div><div class="para">
+ One way to help make vendor-specific packages, or to see which RPM macros are defined on a given Linux distribution, is to look for an RPM that contains the distribution-specific RPM configuration. For example, on Red Hat Linux systems, the Red Hat RPM configuration is defined by the redhat-rpm-config package.
+ </div><div class="para">
+ You can list the files in this package to see where Red Hat defines macros specific to their Linux distribution.
+ </div><div class="para">
+ $ rpm -ql redhat-rpm-config
+ </div><div class="para">
+ /usr/lib/rpm/redhat
+ </div><div class="para">
+ /usr/lib/rpm/redhat/brp-compress
+ </div><div class="para">
+ /usr/lib/rpm/redhat/brp-redhat
+ </div><div class="para">
+ /usr/lib/rpm/redhat/brp-sparc64-linux
+ </div><div class="para">
+ /usr/lib/rpm/redhat/brp-strip
+ </div><div class="para">
+ /usr/lib/rpm/redhat/brp-strip-comment-note
+ </div><div class="para">
+ /usr/lib/rpm/redhat/brp-strip-shared
+ </div><div class="para">
+ /usr/lib/rpm/redhat/find-lang.sh
+ </div><div class="para">
+ /usr/lib/rpm/redhat/find-provides
+ </div><div class="para">
+ /usr/lib/rpm/redhat/find-requires
+ </div><div class="para">
+ /usr/lib/rpm/redhat/macros
+ </div><div class="para">
+ /usr/lib/rpm/redhat/perl.prov
+ </div><div class="para">
+ /usr/lib/rpm/redhat/perl.req
+ </div><div class="para">
+ /usr/lib/rpm/redhat/rpmrc
+ </div><div class="para">
+ These files, such as /usr/lib/rpm/redhat/macros, show you what is specific to a given Linux distribution. You can then look at the macros defined in these files to identify settings for a particular distribution, in this case, Red Hat. Armed with this knowledge, you can better create portable RPM spec files.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id492519" class="title">Dealing with automatic dependency generation</h1></div></div></div><div class="para">
+ One of the features in RPM 4.x is the automatic generation of dependencies. For a variety of reasons including different package layouts, different directory structures, or different versions of RPM, you may need to disable some or all of automatic generation of dependencies.
+ </div><div class="para">
+ You can disable the automatic generation of dependencies by placing the following directive in your spec file:
+ </div><div class="para">
+ Autoreq: 0
+ </div><div class="para">
+ If you do so, you need to use the Requires: tag to manually define all requirements. This is not a good solution to the issue of automatic dependencies however. Most likely, you will need to override the %{__find_requires} and %{__find_provides} macros in order to filter out any unwanted dependencies.
+ </div><div class="para">
+ These two macros resolve to shell scripts that perform the automated dependency checks, as you can see with the rpm --eval command:
+ </div><div class="para">
+ $ rpm --eval "%__find_provides"
+ </div><div class="para">
+ /usr/lib/rpm/find-provides
+ </div><div class="para">
+ rpm --eval "%__find_requires"
+ </div><div class="para">
+ /usr/lib/rpm/find-requires
+ </div><div class="para">
+ You can override these scripts to filter out any dependencies that cause problems for your packages.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id962201" class="title">Dealing with different macros</h1></div></div></div><div class="para">
+ Different Linux vendors define different macros in their RPM setup. This may mean not only different values for the macros, but different macro names as well. Because of this, it is best to define your own local set of macros when building RPMs.
+ </div><div class="para">
+ As much as possible, depend on your own RPM macros. You can define your macros in terms of vendor-specific macros using conditional statements in your spec files, a topic covered in <a class="xref" href="#ch-advanced-packaging">Cap. 10, <em>Creare avansată pachete RPM</em></a> . You can also read examples in the “Build Environment and Macros†section of this chapter.
+ </div><div class="para">
+ This really boils down to creating a disciplined RPM build environment.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id649087" class="title">Making relocatable packages</h1></div></div></div><div class="para">
+ You should aim to make your packages relocatable so that users can install your packages into any directory. This makes it easier to deal with the locations chosen by different Linux distributions, such as /usr, /usr/local, or /opt, for installing add-on software.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ <a class="xref" href="#ch-specfiles">Cap. 9, <em>Working with Spec Files</em></a> covers the spec file format. <a class="xref" href="#ch-advanced-packaging">Cap. 10, <em>Creare avansată pachete RPM</em></a> covers making relocatable packages.
+ </div><div class="para">
+ You can use the %{_bindir} macro in your spec files, which will help create per-distribution packages using the right settings.
+ </div><div class="para">
+ In addition, you can define macros in your spec files that define the location for dependencies. You can then use the --define option to the rpmbuild command to define values for your macros that specify the locations for the dependencies.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ This technique of setting up Linux distribution-specific macros can help solve a lot of problems with cross-platform RPMs.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id1317565" class="title">Creating an RPM build environment</h1></div></div></div><div class="para">
+ If you start with the idea that you want to build RPMs for multiple versions of Linux, you can set up an RPM build environment that cleanly separates most vendor-specific issues.
+ </div><div class="para">
+ The key issues with the build environment are:
+ </div><div class="para">
+ *Detecting the vendors
+ </div><div class="para">
+ *Using macros to define a clean build process
+ </div><div class="para">
+ *Handling different dependencies
+ </div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id795609" class="title">Detecting Vendors</h1></div></div></div><div class="para">
+ To make a clean build environment, you need to be able to detect the Linux vendor and make build settings based on this vendor. To help with this, many Linux vendors install a special file with the vendor name, or a special package with the vendor name. You can query for either of these.
+ </div><div class="para">
+ For files, the convention follows:
+ </div><div class="para">
+ /etc/vendor-release
+ </div><div class="para">
+ For example:
+ </div><div class="para">
+ $ more /etc/redhat-release
+ </div><div class="para">
+ Red Hat Linux release 8.0 (Psyche)
+ </div><div class="para">
+ For packages, the convention is vendor-release for a package name. For example:
+ </div><div class="para">
+ $ rpm -q redhat-release
+ </div><div class="para">
+ redhat-release-8.0-8
+ </div><div class="para">
+ You can use either approach or simply define a macro for the vendor and use the --define option to set the macro. For example:
+ </div><div class="para">
+ # rpmbuild –ba --define 'linuxVendor suse'
+ </div><div class="para">
+ With this definition, you can use the macro %linuxVendor inside your spec files. It is generally easier, though, if your scripts can automatically detect the Linux vendor instead of having to define it manually. The manual approach works, though, if it becomes too much effort to detect the vendor automatically.
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id703748" class="title">Build environment and macros</h1></div></div></div><div class="para">
+ Once you can detect the Linux vendor, you can create macros based on the differences between Linux distributions that affect your applications.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ <a class="xref" href="#ch-customizing-rpm">Cap. 20, <em>Customizing RPM Behavior</em></a> covers RPM macros.
+ </div><div class="para">
+ The macros that specifically help you with platform differences include the %if .. %endif conditional. You can use this in combination with special macros you define. In addition, command-line options such as --with, --without, and --target allow you to control features and the build target within an RPM.
+ </div><div class="para">
+ The %if macro allows you to specify a condition within your spec file. For example:
+ </div><div class="para">
+ %if %{old_5x} && %{old_6x}
+ </div><div class="para">
+ %{error: You cannot build for .5x and .6x at the same time}
+ </div><div class="para">
+ %quit
+ </div><div class="para">
+ %endif
+ </div><div class="para">
+ </div><div class="para">
+ %if %{old_5x}
+ </div><div class="para">
+ %define b5x 1
+ </div><div class="para">
+ %undefine b6x
+ </div><div class="para">
+ %endif
+ </div><div class="para">
+ </div><div class="para">
+ %if %{old_6x}
+ </div><div class="para">
+ %define b6x 1
+ </div><div class="para">
+ %undefine b5x
+ </div><div class="para">
+ %endif
+ </div><div class="para">
+ You can also use %if to control settings such as the Requires:, as shown in the following example:
+ </div><div class="para">
+ %if %{build6x}
+ </div><div class="para">
+ Requires: util-linux, pam >= 0.66-5
+ </div><div class="para">
+ %else
+ </div><div class="para">
+ Requires: util-linux, pam >= 0.75-37, /etc/pam.d/system-auth
+ </div><div class="para">
+ %endif
+ </div><div class="para">
+ </div><div class="para">
+ The --with command-line option defines a special macro starting with _with_. For example, the following command-line option defines a feature to use:
+ </div><div class="para">
+ $ rpmbuild –bc --with ssh filename.spec
+ </div><div class="para">
+ This example defines the macro _with_ssh to --with-ssh. This format was specially designed to work with GNU configure. You can use this for conditional builds for platform-dependent issues.
+ </div><div class="para">
+ The --without command-line option similarly defines a macro starting with _without_. The convention is that this option defines a feature the code should not use.
+ </div><div class="para">
+ You can combine --with and --without to turn on and off features referenced in your spec files. For example:
+ </div><div class="para">
+ ./configure %{?_with_ssh}
+ </div><div class="para">
+ This will pass the following command line if the _with_ssh macro is defined:
+ </div><div class="para">
+ ./configure --with-ssh
+ </div><div class="para">
+ If this option is not defined, the command will be:
+ </div><div class="para">
+ ./configure
+ </div><div class="para">
+ The --target option sets the spec file macros %_target, %_target_arch, and %_target_os . For example:
+ </div><div class="para">
+ $ rpmbuild -bc --target ppc-ibm-aix /usr/src/redhat/SPECS/jikes.spec
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id618503" class="title">Compatibility and Glue Packages</h1></div></div></div><div class="para">
+ Not all Linux distributions are the same. Macros alone won’t provide work-arounds for all the differences. You can, though, get a lot of mileage from compatibility and glue packages.
+ </div><div class="para">
+ A compatibility package provides a legacy API on newer systems that no longer support the legacy API. By convention, compatibility packages are named with a leading compat- to signify their purpose.
+ </div><div class="para">
+ For example:
+ </div><div class="para">
+ $ rpm -q --qf "%{description}" compat-libstdc++
+ </div><div class="para">
+ The compat-libstdc++ package contains compatibility Standard C++
+ </div><div class="para">
+ Using a compatibility package allows you to create programs that use a least-common-denominator approach, programming to the oldest but most common APIs. As some Linux distributions eliminate the old APIs, compatibility packages can provide the missing APIs.
+ </div><div class="para">
+ Similarly, a glue package provides a dependency that exists on some Linux distributions but not others. It glues together your package with the Linux distribution that is missing an essential capability.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ A key point in both of these approaches is to separate the compatibility and glue packages from your main application packages. The application packages should be as clean of vendor issues as possible. Instruct your users to install the compatibility or glue packages as needed (based on their Linux distribution) along with the main application package or packages.
+ </div><div class="para">
+ With all this discussion of RPM and Linux differences, you might think that Linux is one big mess. That’s not true. Linux maintains a high degree of compatibility among Linux distributions as well as among processor architectures. Most programs originally created for Linux on Intel-based architectures compile cleanly on Linux versions running on other processor architectures such as MIPS, SPARC, and ARM.
+ </div><div class="para">
+ The main differences lie in how Linux vendors split up the huge number of files associated with Linux into RPM packages as well as which versions of tools like C compilers the vendors ship.
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id753508" class="title">Dealing with Signatures</h1></div></div></div><div class="para">
+ With SUSE Linux, or any Linux based on UnitedLinux 1.0, the RPM packages are signed with OpenPGP version 4, not 3, as used in RPM 4.1. This means that you must use some other, non-RPM means to extract the signatures from an RPM package, and then verify these signatures with gpg.
+ </div><div class="para">
+ </div></div></div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id571016" class="title">Dealing with Non-RPM-Based Linux Versions</h1></div></div></div><div class="para">
+ The main Linux distributions that don’t support RPM are the Debian GNU/Linux family and Slackware Linux. To help with these distributions, you can use a package-conversion tool called alien.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id571028" class="title">Handling non-RPM packages with alien</h1></div></div></div><div class="para">
+ Alien is a package that supports conversions between RPM and so-called alien package formats such as the dpkg (Debian GNU/Linux), slp (Stampede Linux), and tgz (Slackware Linux) formats.
+ </div><div class="para">
+ You can use alien on your RPM-based Linux system to convert RPMs to some other format, such as the Debian dpkg. You can also use alien to convert other package formats into RPMs, depending on which way you need to go.
+ </div><div class="para">
+ </div><div class="para">
+ </div></div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id682499" class="title">Standardizing RPMs</h1></div></div></div><div class="para">
+ RPM is being considered as part of the Linux Standard Base, or LSB, 1.3. This will define a standard packaging format for Linux distributions, and over time reduce the RPM differences between distributions.
+ </div><div class="para">
+ In addition, other efforts are underway to help unify the diverse Linux distributions, including the Filesystem Hierarchy Standard and the adoption of RPM by many Linux vendors.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id682517" class="title">Filesystem Hierarchy Standard</h1></div></div></div><div class="para">
+ The FHS, or Filesystem Hierarchy Standard, defines the purpose of all the upper-level directories on Linux systems, such as /var and /usr/bin. This standard, along with the Linux Standard Base, or LSB, is driving Linux distributions to a greater degree of similarity.
+ </div><div class="para">
+ The FHS helps by specifying where applications should get installed and which directories should be left to local administrators to manage. The FHS also defines the purpose of all Linux directories, giving vendors and application writers a better idea of where they should install their packages.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ See www.linuxbase.org for more on the LSB. See www.pathname.com/fhs/ for more on the FHS.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id562919" class="title">RPM adoption</h1></div></div></div><div class="para">
+ RPM has been adopted by a large number of Linux distributions. In addition, standardization efforts, both for RPM and for filesystem locations, are making Linux systems less varied.
+ </div><div class="para">
+ This means that over time, many of the RPM-related differences between Linux distributions will fade away, making it easier to create cross-platform RPMs.
+ </div><div class="para">
+ </div><div class="para">
+ </div></div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id772912" class="title">Summary</h1></div></div></div><div class="para">
+ This chapter covers differences in RPM versions between various Linux distributions, and techniques you can use to get around these differences. Each Linux vendor packages software differently, even if the vendor uses RPM. This can cause problems unless you write your spec files carefully.
+ </div><div class="para">
+ Inside your RPM spec files, you can use conditional elements as well as platform-based macro definitions to help create RPMs for multiple packages.
+ </div><div class="para">
+ Some of the best conventions are to split the software in your applications from any compatibility or glue packages, separate packages that provide missing features for various flavors of Linux.
+ </div><div class="para">
+ Standardization efforts such as the Linux Standard Base and Filesystem Hierarchy Standard are bringing Linux vendors closer and closer together. Widespread adoption of RPM by most Linux distributions also helps.
+ </div><div class="para">
+ While this chapter covers RPM on other Linux distributions, the next chapter tackles RPM outside of Linux.
+ </div></div></div><div xml:lang="ro" class="chapter" id="ch-other-os" lang="ro"><div class="titlepage"><div><div><h2 class="title">Cap. 19. RPM on Other Operating Systems</h2></div></div></div><div class="toc"><dl><dt><span class="sect1"><a href="#id586148">19.1. Running RPM on Other Operating Systems</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id658642">19.1.1. Getting RPM for your system</a></span></dt><dt><span class="sect2"><a href="#id734430">19.1.2. Running RPM on Windows</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id734462">19.2. Bootstrapping RPM On Other Operating Systems</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id876773">19.2.1. Downloading the RPM software</a></span></dt><dt><span class="sect2"><a href="#id876798">19.2.2. Extracting the software</a></span></dt><dt><span class="sect2"><a href="#id573957">19.2.3. Reading the INSTALL file</a></span></dt><dt><span class="sect2"><a href="#id573981">19.2.4. Libraries required
by RPM</a></span></dt><dt><span class="sect2"><a href="#id855206">19.2.5. Tools for building RPM</a></span></dt><dt><span class="sect2"><a href="#id794537">19.2.6. Compiling RPM</a></span></dt><dt><span class="sect2"><a href="#id688202">19.2.7. Handling problems</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id561376">19.3. Setting Up the RPM System</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id561388">19.3.1. Setting up the RPM database</a></span></dt><dt><span class="sect2"><a href="#id617415">19.3.2. Creating the RPM environment</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id663021">19.4. Creating Non-Linux RPMS</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id762951">19.4.1. Setting up a build environment</a></span></dt><dt><span class="sect2"><a href="#id1109836">19.4.2. Cross-building packages</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id518158">19.5. Summary</a></span></dt></dl></div><div class="para">
+ This chapter covers:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Running RPM on other operating systems
+ </div></li><li class="listitem"><div class="para">
+ Bootstrapping RPM on other operating systems
+ </div></li><li class="listitem"><div class="para">
+ Setting up the RPM environment
+ </div></li><li class="listitem"><div class="para">
+ Creating non-Linux RPMs
+ </div></li><li class="listitem"><div class="para">
+ Setting up an RPM build environment
+ </div></li><li class="listitem"><div class="para">
+ Cross-building packages
+ </div></li></ul></div><div class="para">
+ RPM was originally designed on Linux and for most of its life has been a Linux-centric package management system. But most Linux programs are portable to most versions of Unix or Unix -like operating systems. Linux is, after all, a Unix-workalike operating system.
+ </div><div class="para">
+ The RPM system is no exception. It has been ported to a number of operating systems, including quite a few Unix variants. The source code is freely available, so you can port RPM to other systems as well.
+ </div><div class="para">
+ This chapter covers running RPM on non-Linux operating systems, including getting the RPM system in the first place, bootstrapping an RPM environment, and creating packages for other operating systems.
+ </div><div class="para">
+ The first step is to get RPM for your system, or port RPM if it isn’t already available.
+ </div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id586148" class="title">Running RPM on Other Operating Systems</h1></div></div></div><div class="para">
+ The RPM system, made up of mostly the rpm and rpmbuild commands, have been ported to a number of operating systems. There is nothing stopping you from running the RPM system on other platforms.
+ </div><div class="para">
+ Other operating systems have their own native package management software. You may prefer the way RPM works, or merely want to standardize on RPM across all platforms you manage. There will always be a few issues, however, when running RPM on other operating systems. For example, operating system patches and updates are likely to be distributed in the operating system’s native package management format, not RPM. Many applications will be updated also using the system’s native package management format.
+ </div><div class="para">
+ You will need to always keep in mind that there are two package management schemes in use: RPM and the native one. This issue has not stopped a great many people from using RPM on other systems, though, as shown by the list of platforms RPM has been ported to (see Table 20-1 for the list).
+ </div><div class="para">
+ On the plus side, package management has always been one of the main areas where versions of Linux, Unix, and other operating systems differ, sometimes quite a lot. By using RPM, you can transfer your knowledge of package management from one system to another, saving valuable time and hassles. You will be able to update systems in the same manner, a big plus if you manage a diverse set of systems.
+ </div><div class="para">
+ Another reason to use RPM on other operating systems is that in most cases, RPM provides far more capabilities than the native package management software. Following the RPM philosophy, each package can be separately verified, checked, and updated. Each package lists the other packages it depends on, and also lists the capabilities it provides. You can automate the installation and upgrade processes with RPM. You can also perform a lot of version and signature comparisons. All of this leads to a more secure, more robust system.
+ </div><div class="para">
+ Many operating systems don’t include these capabilities in the native package management software. This is why many users run RPM on other operating systems.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ See <a class="xref" href="#ch-intro-rpm">Cap. 1, <em>Introduction to RPM</em></a> for more on the philosophy behind RPM.
+ </div><div class="para">
+ If you decide to use RPM on a non-Linux system, the first step is getting RPM for your system, if it is available.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id658642" class="title">Getting RPM for your system</h1></div></div></div><div class="para">
+ The first step to using RPM on non-Linux platforms is getting the RPM system for your platform. In most cases, this is a relatively easy step, as RPM has been ported to a great many platforms, as listed on the main RPM Web site.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ Links to RPM versions for various platforms are listed at www.rpm.org/platforms/.
+ </div><div class="para">
+ Go to this site and download the versions for the platforms you need. Table 20-1 lists the platforms RPM has been ported to, as reported by the RPM site.
+ </div><div class="para">
+ Table 20-1 Available Platforms for RPM
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Platform
+ </div>
+
+ </td><td>
+ <div class="para">
+ Notes
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ AIX
+ </div>
+
+ </td><td>
+ <div class="para">
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ AmigaOS
+ </div>
+
+ </td><td>
+ <div class="para">
+ With GeekGadgets
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ BeOS
+ </div>
+
+ </td><td>
+ <div class="para">
+ With GeekGadgets
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ FreeBSD
+ </div>
+
+ </td><td>
+ <div class="para">
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ HP-UX
+ </div>
+
+ </td><td>
+ <div class="para">
+ 10.20+, 9.04
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ IRIX
+ </div>
+
+ </td><td>
+ <div class="para">
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Linux
+ </div>
+
+ </td><td>
+ <div class="para">
+ Multiple platforms including Alpha, Intel, Motorola 68000, SGI MIPS, PowerPC, and SPARC
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ LynxOS
+ </div>
+
+ </td><td>
+ <div class="para">
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ MachTen
+ </div>
+
+ </td><td>
+ <div class="para">
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ MacOS X
+ </div>
+
+ </td><td>
+ <div class="para">
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Mint
+ </div>
+
+ </td><td>
+ <div class="para">
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ NCS System V
+ </div>
+
+ </td><td>
+ <div class="para">
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ NetBSD
+ </div>
+
+ </td><td>
+ <div class="para">
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ OS/2
+ </div>
+
+ </td><td>
+ <div class="para">
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ OSF/1
+ </div>
+
+ </td><td>
+ <div class="para">
+ 3.2+
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ SCO OpenServer
+ </div>
+
+ </td><td>
+ <div class="para">
+ 5.0.2+
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Sinix
+ </div>
+
+ </td><td>
+ <div class="para">
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Solaris
+ </div>
+
+ </td><td>
+ <div class="para">
+ Solaris for SPARC 2.4 and 8+, Solaris for Intel
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ SunOS 4.1.3
+ </div>
+
+ </td><td>
+ <div class="para">
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Windows
+ </div>
+
+ </td><td>
+ <div class="para">
+ Under Cygwin
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ Note that RPM has likely been ported to even more platforms. These are just the ones reported to the rpm.org site.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ If you fix a bug in RPM on a non-Linux system, or if you port RPM to a new system, please report this to the rpm.org site maintainers, as well as make your work available for others. You never know, but someone else may fix a problem you’re facing.
+ </div><div class="para">
+ If Table 20-1 does not cover the platforms you need, you must compile and bootstrap the RPM environment for your platforms, as covered in the "Bootstrapping RPM on Other Operating Systems" section, following.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ Don’t expect to find RPMs of the RPM system for these other platforms. If you did, there would be no way to install RPM. Instead, you’ll find RPM packaged in a variety of formats, typically using a native bundling format for a given system, or at least a supported format. Compressed tar files are very common. RPM for IRIX systems come in IRIX tardist format.
+ </div><div class="para">
+ If RPM is available for your system, download the package and follow any installation instructions that come with the package. For example, RPM for Solaris 8 requires the libiconv library, as well as the Solaris packages SUNWzlib and SUNWbzip. You must install these packages prior to installing RPM.
+ </div><div class="para">
+ Each operating system will have similar requirements. Windows systems have a few extra requirements due to the fact that Windows is very different from Linux or Unix-like systems.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id734430" class="title">Running RPM on Windows</h1></div></div></div><div class="para">
+ The version of RPM for Windows requires cygwin, originally the Cygnus port of many Unix tools to Windows. Now part of Red Hat, you can download the cygwin environment from the main cygwin site.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ Download cygwin from www.cygwin.com.
+ </div><div class="para">
+ You can download a setup.exe program to install the environment on Windows. After installation, you can download the RPM system for Windows.
+ </div><div class="para">
+ After you have RPM installed, you can set up your RPM system. If RPM wasn’t already ported to your operating systems, however, you will need to bootstrap RPM on your platforms.
+ </div></div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id734462" class="title">Bootstrapping RPM On Other Operating Systems</h1></div></div></div><div class="para">
+ If you cannot find a version of RPM that has been ported to your platform, you can port it yourself. The RPM system usually isn’t that hard to port to any platform that can appear like Unix or Linux systems, such as any platform that supports POSIX system calls or something like these system calls.
+ </div><div class="para">
+ Don’t be dismayed by the sheer size of the RPM package. Much of the RPM system was carefully designed to run across multiple platforms, so file access is abstracted to special portability routines. For example, RPM has been ported to both AmigaOS and BeOS, two non-Unix operating systems.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id876773" class="title">Downloading the RPM software</h1></div></div></div><div class="para">
+ To bootstrap RPM on another operating system, download the RPM source code from the main RPM site.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ You can download the RPM source code from ftp://ftp.rpm.org/pub/rpm/dist/.
+ </div><div class="para">
+ Note that you probably do not want to download an RPM of the sources, since your platform won’t have RPM available. In most cases, you’ll want to download a tarred compressed archive, such as rpm-4.1.tar.gz for RPM version 4.1.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id876798" class="title">Extracting the software</h1></div></div></div><div class="para">
+ If the system you plan to port RPM doesn’t have the tar and gzip commands available, or something that supports these formats, then you need to find a way to extract the software.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ Programs such as WinZip on Windows support extracting .tar.gz files. Your platform may have a similar program.
+ </div><div class="para">
+ One way is to port the gzip and tar commands to your platform.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ You can download the sources for tar and gzip from www.gnu.org.
+ </div><div class="para">
+ Another way is to extract the sources on a platform with these commands available, such as a Linux platform. Then, create a file using a format supported by your operating system and transfer the files to the other system.
+ </div><div class="para">
+ Once you have the RPM source code available on your target system, and all the files are extracted, you are ready to start porting. The first step is really simple: read.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id573957" class="title">Reading the INSTALL file</h1></div></div></div><div class="para">
+ In the main RPM source directory, you will see two very important files: README and INSTALL. Read them both. (You would be surprised at how many times people need to be told this.)
+ </div><div class="para">
+ Of the two, the INSTALL file has much more detailed information on installing RPM on a new system. The INSTALL file describes the libraries required by RPM, provides tips on compiling RPM, and describes some of the set up work necessary after compiling the RPM system.
+ </div><div class="para">
+ Some of the hardest parts of the RPM system to port, though, may be in the database, compression, and encryption calls, used as libraries by the RPM system.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id573981" class="title">Libraries required by RPM</h1></div></div></div><div class="para">
+ Rather than invent everything from scratch, the RPM system makes use of a number of libraries, including those listed in Table 20-2.
+ </div><div class="para">
+ Table 20-2 Libraries used by RPM
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Library
+ </div>
+
+ </td><td>
+ <div class="para">
+ Purpose
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Berkeley DB
+ </div>
+
+ </td><td>
+ <div class="para">
+ RPM database, using db1 and db3
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ bzip2
+ </div>
+
+ </td><td>
+ <div class="para">
+ Compression
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ gettext
+ </div>
+
+ </td><td>
+ <div class="para">
+ International text lookup
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ gpg
+ </div>
+
+ </td><td>
+ <div class="para">
+ For digital signatures
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ gzip
+ </div>
+
+ </td><td>
+ <div class="para">
+ Compression
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ popt
+ </div>
+
+ </td><td>
+ <div class="para">
+ Processing command-line options
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ zlib
+ </div>
+
+ </td><td>
+ <div class="para">
+ Compression
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ Read through the INSTALL file to find out where you can download versions of these libraries. You may find that each library has its own set of dependencies, all of which you need to port to your target platform.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id855206" class="title">Tools for building RPM</h1></div></div></div><div class="para">
+ In addition to the libraries listed in Table 20-2, RPM requires a number of GNU utilities for building RPM, including those listed in Table 20-3.
+ </div><div class="para">
+ Table 20-3 Tools used to build RPM
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Tool
+ </div>
+
+ </td><td>
+ <div class="para">
+ Usage
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Autoconf
+ </div>
+
+ </td><td>
+ <div class="para">
+ Builds configure scripts
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Automake
+ </div>
+
+ </td><td>
+ <div class="para">
+ Used with autoconf
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ GNU make
+ </div>
+
+ </td><td>
+ <div class="para">
+ Used to control building the sources
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Libtool
+ </div>
+
+ </td><td>
+ <div class="para">
+ Used by the autogen.sh script
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ In addition to all this, RPM works best with the GNU C compiler, GCC, and the GNU make program, gnumake, or simply gmake.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ The source code for all the GNU tools is available at www.gnu.org.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id794537" class="title">Compiling RPM</h1></div></div></div><div class="para">
+ After downloading the RPM sources, extracting all the files and installing all the prerequisite libraries, you are ready to start compiling RPM.
+ </div><div class="para">
+ RPM includes quite a few subsystems, such as popt for parsing command-line options. Each of these subsystems requires some configuration. Most of this configuration is automated through the use of the autogen.sh script and the autoconf/automake tool used to create configure scripts.
+ </div><div class="para">
+ The autogen.sh script is a Bourne shell script that checks for specific versions of necessary tools and libraries. After checking dependencies, the autogen.sh script calls different autogen.sh scripts in the beecrypt, libelf, popt, and zlib directories. When done with that task, the autogen.sh script calls configure.
+ </div><div class="para">
+ Pass a command-line option of --noconfigure to disable the call to configure.
+ </div><div class="para">
+ Edit the autogen.sh script if you are using different versions of the necessary tools. The autogen.sh script is coded to require the specific versions of these tools as were used originally to build the RPM package. In addition, your system may have libraries stored in different locations than those expected by the autogen.sh, so it's a good idea to edit this script and verify all the assumptions.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ One really big assumption in this script is that you have a Unix-like operating system. If not, you will need to determine how to set up the Makefiles manually. This requires a lot of trial and error while you edit the Makefiles and then see if you can build the software. Fix each problem that arises and try again.
+ </div><div class="para">
+ When you are done with the autogen.sh script, you can use the following basic commands to create system-specific Makefiles, compile RPM and install the commands:
+ </div><div class="para">
+ $ ./configure
+ </div><div class="para">
+ $ make
+ </div><div class="para">
+ $ make install
+ </div><div class="para">
+ The configure script takes the Makefile.in files and uses these files as templates to create custom versions of Makefile.in files, tuned to your system. (The automake system starts with a Makefile.am file, creates an expanded Makefile.in file, and finally results in a Makefile tuned to your system.) If all else fails, you can copy each Makefile.in file to Makefile and then edit the Makefile to make one that will work on your system.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ See the GNU site, at www.gnu.org, for more on the autoconf and automake tools.
+ </div><div class="para">
+ If the make install step fails, you can manually copy the RPM executables and scripts to a directory for system commands.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id688202" class="title">Handling problems</h1></div></div></div><div class="para">
+ If RPM fails to compile or install, you can still work around many issues. The key is to find out what went wrong, fix the problem, and try again. You may go through this loop many times before RPM successfully compiles and installs.
+ </div><div class="para">
+ Most problems can be solved by changing the configuration settings. If possible, change the inputs to the configure command to specify C compiler options, and so on, that you discover you need. You can then run the basic commands to build RPM again, but with any special options you discovered are necessary:
+ </div><div class="para">
+ $ ./configure –any_options_set_here
+ </div><div class="para">
+ $ make
+ </div><div class="para">
+ $ make install
+ </div><div class="para">
+ If you take this approach, you avoid having to edit a number of Makefiles (one in each source code subdirectory) by hand. You also have an easier time of switching to different command-line options as you determine more solutions to the compilation problems.
+ </div><div class="para">
+ If this won’t work, though, you can edit the Makefile.am file or the generated Makefile directly to add whatever settings are needed. For example, you may need to specify additional directories for libraries, or some C compiler compatibility option.
+ </div><div class="para">
+ As you discover problems, remember you are not alone in porting RPM. Check the RPM mailing list, where the question of getting RPM going on other platforms comes up frequently.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ For details on viewing the RPM mailing list archives and signing up for the list, see www.rpm.org/mailing_list/.
+ </div></div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id561376" class="title">Setting Up the RPM System</h1></div></div></div><div class="para">
+ Once you have RPM available on your platform, you need to set up the RPM system. This includes setting up the RPM database and creating an RPM environment.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id561388" class="title">Setting up the RPM database</h1></div></div></div><div class="para">
+ After you have the RPM system available on your platform, you need to set up the RPM database. This usually involves two steps:
+ </div><div class="para">
+ *Initializing an empty RPM database
+ </div><div class="para">
+ *Populating the database with packages, especially for dependencies
+ </div><div class="para">
+ Both steps are necessary.
+ </div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id776058" class="title">Initializing an Empty RPM Database</h1></div></div></div><div class="para">
+ After you have the RPM system installed on your platform, the next big step is to create an RPM database for your platform. You can make an empty database with the rpm --initdb command, as shown following:
+ </div><div class="para">
+ # mkdir /var/lib/rpm
+ </div><div class="para">
+ # rpm --initdb
+ </div><div class="para">
+ The first command creates the default directory for the RPM database.
+ </div><div class="para">
+ You may need to pass command-line options to specify a non-default location of the RPM database, such as the following:
+ </div><div class="para">
+ # rpm --dbpath /location/of/your/rpm/database --initdb
+ </div><div class="para">
+ Use a command like this one if you don’t want to place the RPM database in its default location.
+ </div><div class="para">
+ In addition, use the –v option to add more verbose output. This is very useful if errors occur. Use the --root option to specify a different root directory for RPM operations. Use the --rcfile option to specify a non-default set of rc files and the --macros option to specify a non-default set of macros.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ <a class="xref" href="#ch-customizing-rpm">Cap. 20, <em>Customizing RPM Behavior</em></a> covers RPM customization.
+ </div><div class="para">
+ Initializing the RPM database creates the necessary structure for an empty database. You can then fill, or populate, the database with packages. In most cases, all you need to do is install packages to populate the RPM database, as each installed package gets added to the database.
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id683586" class="title">Handling Dependencies for Packages Installed Without RPM</h1></div></div></div><div class="para">
+ Each time you install a package, you populate the RPM database. This works well, as long as you have already installed all the dependencies for the packages you want to install.
+ </div><div class="para">
+ On an operating system that is based on RPM, such as Red Hat Linux, all packages (except for some bootstrapping code) are installed with RPM. That means nearly everything on the system is defined in the RPM database. The RPM database then has a full knowledge of what you have installed and can properly handle dependencies. Thus, a failure to find a dependency means that you have not installed the requisite package that provides the needed capability.
+ </div><div class="para">
+ On an operating system that is not based on RPM, however, such as Solaris or IRIX, most packages have already been installed by some means other than RPM.. That’s because these operating systems use different native package-management techniques and different package formats.
+ </div><div class="para">
+ It is very likely that RPM packages you want to install have dependencies that come from non-RPM packages. For example, the rpm program on Windows depends on the cygwin environment, yet this environment needs to be installed with a Windows setup.exe program, not with the rpm command.
+ </div><div class="para">
+ To get around this problem, you need to populate the new RPM database with a package or packages that reflect the current system in order to properly handle dependencies. The main way to do this is to set up a virtual package.
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id588972" class="title">Setting Up A Virtual Package</h1></div></div></div><div class="para">
+ You can get around the problem of pre-existing software by building a virtual package that lists the system libraries at mdinstalled without RPM at mdin an RPM package. This way, the rpm command will find that the dependencies are installed, even if they were not really installed with RPM. You need to do this for all capabilities and system libraries installed outside of RPM control.
+ </div><div class="para">
+ To help create such a virtual package, use the vpkg-provides.sh script from the scripts directory. The vpkg-provides.sh script searches a list of directories for shared libraries and interpreters (such as shells). The vpkg-provides.sh script then creates a spec file that lists all the files found, files that are managed outside of RPM. You can use this spec file to create an RPM and install the RPM using the rpm command to populate the RPM database.
+ </div><div class="para">
+ The RPM spec file created by the vpkg-provides.sh doesn’t really install any files, as all the files are already installed. Instead it makes a package that claims ownership for all these files so that RPM dependencies can function properly.
+ </div><div class="para">
+ The vpkg-provides.sh script accepts three main command-line options: --spec_header, --ignore_dirs, and --no_verify.
+ </div><div class="para">
+ The --spec_header option tells the script the name of the RPM spec file it should use as a header for the spec file it will produce. You need to provide the path to the file. For example:
+ </div><div class="para">
+ # sh vpkg-provides.sh --spec_header /path/to/spec/file
+ </div><div class="para">
+ You need to provide a spec file header to make a complete spec file. This header should contain the Summary, Name, Version, and Release settings, at least. <a class="xref" href="#ch-specfiles">Cap. 9, <em>Working with Spec Files</em></a> covers these spec file tags.
+ </div><div class="para">
+ The --ignore_dirs option tells the vpkg-provides.sh script to ignore certain directories. You need to pass a list of egrep search patterns that identify the directories to ignore. Separate each pattern with a pipe character, |.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ The egrep command may not be available on your system. It may be easier to edit the vpkg-provides.sh script and manually specify the directories to ignore.
+ </div><div class="para">
+ The --no_verify option tells the vpkg-provides.sh script to skip the step of creating a script to verify checksums of all files in the package.
+ </div><div class="para">
+ In addition to these main command-line options, you can also pass the following options to the vpkg-provides.sh script.
+ </div><div class="para">
+ The --shlib_dirs option tells the vpkg-provides.sh script the directories to look for shared libraries. Pass a colon-delimited list of directories. For example:
+ </div><div class="para">
+ # sh vpkg-provides.sh --spec_header /path/to/spec/file \
+ </div><div class="para">
+ --shlib_dirs "/bin:/usr/bin:/sbin:/usr/sbin:/usr/ucb:/usr/bsd"
+ </div><div class="para">
+ The --interp_dirs option tells the vpkg-provides.sh script which directories to look in to find interpreters such as sh, bash, perl, wish (Tcl/Tk), and awk. The --interps option tells the vpkg-provides.sh script the names of the interpreter commands. Both these options expect a colon-delimited list.
+ </div><div class="para">
+ The --find_provides option tells the vpkg-provides.sh script the name of the find-provides script to use, defaulting to /usr/lib/rpm/find-provides.
+ </div><div class="para">
+ The vpkg-provides.sh script defines specific directories to look in for shared libraries and interpreters under various operating systems. You will most likely need to edit this section.
+ </div><div class="para">
+ In fact, if you are working with a non-Unix system, or if you experience problems running the vpkg-provides.sh script, you can edit the file to remove the problematic commands. You can also create a new script in a scripting language supported on your system. The vpkg-provides.sh script is a Linux shell script. Linux and Unix systems should be able to run the script, but non-Unix systems likely won’t have the commands and may also not support shell scripts at all. In an effort to be generic, the vpkg-provides.sh script does a lot of work. You can limit this by explicitly specifying directories and commands, for example. And, if all else fails, you can create a virtual package manually (covered in the following section).
+ </div><div class="para">
+ When complete, the vpkg-provides.sh script outputs a spec file, using the header you provided, and outputs a set of Provides: lines to specify what the package provides. It then outputs some empty definitions for the prep, build, install, and clean sections of the spec file.
+ </div><div class="para">
+ For example, you can run the vpkg-provides.sh script with a command like the following:
+ </div><div class="para">
+ $ sh ./vpkg-provides.sh --spec_header my_header.spec --find_provides ./find-provides --no_verify
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ If you run this script as a non-root user, you may get a number of permission errors as the vpkg-provides.sh script searches through system directories.
+ </div><div class="para">
+ The script will then output your spec file header along with output like that shown in Listing 20-1.
+ </div><div class="para">
+ Listing 20-1: Output from the vpkg-provides.sh script
+ </div><div class="para">
+ Provides: /bin/sh
+ </div><div class="para">
+ Provides: /bin/csh
+ </div><div class="para">
+ Provides: /bin/ksh
+ </div><div class="para">
+ Provides: /bin/perl
+ </div><div class="para">
+ Provides: /bin/awk
+ </div><div class="para">
+ Provides: /bin/nawk
+ </div><div class="para">
+ Provides: /bin/oawk
+ </div><div class="para">
+ Provides: /usr/bin/sh
+ </div><div class="para">
+ Provides: /usr/bin/csh
+ </div><div class="para">
+ Provides: /usr/bin/ksh
+ </div><div class="para">
+ Provides: /usr/bin/perl
+ </div><div class="para">
+ Provides: /usr/bin/awk
+ </div><div class="para">
+ Provides: /usr/bin/nawk
+ </div><div class="para">
+ Provides: /usr/bin/oawk
+ </div><div class="para">
+ Provides: /sbin/sh
+ </div><div class="para">
+ Provides: /usr/dt/bin/dtksh
+ </div><div class="para">
+ Provides: /usr/xpg4/bin/sh
+ </div><div class="para">
+ Provides: /usr/xpg4/bin/awk
+ </div><div class="para">
+ %prep
+ </div><div class="para">
+ # nothing to do
+ </div><div class="para">
+ %build
+ </div><div class="para">
+ # nothing to do
+ </div><div class="para">
+ %install
+ </div><div class="para">
+ # nothing to do
+ </div><div class="para">
+ %clean
+ </div><div class="para">
+ # nothing to do
+ </div><div class="para">
+ %files
+ </div><div class="para">
+ # no files in a virtual package
+ </div><div class="para">
+ The vpkg-provides.sh script also outputs a package description that explains how the package was created. This is important so that you know this is a virtual package.
+ </div><div class="para">
+ When done, use the rpmbuild command to create an RPM from the generated spec file.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ <a class="xref" href="#ch-creating-rpms">Cap. 8, <em>Creating RPMs: An Overview</em></a> covers how to run the rpmbuild command, and <a class="xref" href="#ch-specfiles">Cap. 9, <em>Working with Spec Files</em></a> covers spec files in detail.
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id828336" class="title">Creating a Virtual Package Manually</h1></div></div></div><div class="para">
+ Even on Unix-like systems you may experience troubles with the vpkg-provides.sh script. That’s simply because the vpkg-provides.sh script assumes a number of Unix and GNU utilities are available. In most cases, it will work best if you can fix what went wrong and run the vpkg-provides.sh script again.
+ </div><div class="para">
+ If all else fails, though, you can create a virtual package spec file manually. Create a spec file starting with the Summary, Name, Version, and Release settings.
+ </div><div class="para">
+ Looking at the output shown in Listing 20-1, you can create a Provides: statement for each shared library on your system, and each interpreter, such as shells. Add each statement to your spec file. For example:
+ </div><div class="para">
+ Provides: libgen.so
+ </div><div class="para">
+ Copy the prep, build, install, and clean sections exactly as they are in Listing 20-1. You can now run the rpmbuild command to create a virtual package. Install this package.
+ </div></div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id617415" class="title">Creating the RPM environment</h1></div></div></div><div class="para">
+ The RPM environment is made up of a large number of RPM settings and macro definitions. Run the rpm --showrc command to see the current environment settings on Linux:
+ </div><div class="para">
+ $ rpm –showrc
+ </div><div class="para">
+ ARCHITECTURE AND OS:
+ </div><div class="para">
+ build arch : i386
+ </div><div class="para">
+ compatible build archs: i686 i586 i486 i386 noarch
+ </div><div class="para">
+ build os : Linux
+ </div><div class="para">
+ compatible build os's : Linux
+ </div><div class="para">
+ install arch : i686
+ </div><div class="para">
+ install os : Linux
+ </div><div class="para">
+ compatible archs : i686 i586 i486 i386 noarch
+ </div><div class="para">
+ compatible os's : Linux
+ </div><div class="para">
+ </div><div class="para">
+ RPMRC VALUES:
+ </div><div class="para">
+ macrofiles : /usr/lib/rpm/macros:/usr/lib/rpm/i686-linux/macros:/etc/
+ </div><div class="para">
+ rpm/macros.specspo:/etc/rpm/macros.db1:/etc/rpm/macros.cdb:/etc/rpm/macros:/etc/
+ </div><div class="para">
+ rpm/i686-linux/macros:~/.rpmmacros
+ </div><div class="para">
+ optflags : -O2 -march=i686
+ </div><div class="para">
+ This output was truncated for space. As you can see, there are a lot of expected settings. You need to set up these same settings and macros, but with the proper values for the new system on which you are running RPM.
+ </div><div class="para">
+ The files rpmrc.in and macros.in serve as the default templates used to create the rc and macro settings, respectively. These files are modified by the configure script to include values specific to the local operating system. You can edit these files as needed for your system, prior to installing RPM. That is, edit these files between calling the make command and the make install command.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ <a class="xref" href="#ch-customizing-rpm">Cap. 20, <em>Customizing RPM Behavior</em></a> covers how to customize the RPM settings and macros, along with the popt aliases.
+ </div><div class="para">
+ The INSTALL file in the RPM sources also describes some modifications you may want to make to the macros.
+ </div></div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id663021" class="title">Creating Non-Linux RPMS</h1></div></div></div><div class="para">
+ Once you have RPM set up on a system, you should be able to create RPMs using the rpmbuild command on that system.
+ </div><div class="para">
+ Warning
+ </div><div class="para">
+ Do not build RPM packages logged in as a root or Administrator user. If something goes wrong, rpmbuild could destroy files in your system. Remember that spec files can define a number of commands and shell scripts. Any of these could have an error that could cause major damage when run as a root user.
+ </div><div class="para">
+ Before building RPMs with the rpmbuild command, though, you may want to customize the build environment to better reflect your system. You may also find it is too difficult to build most RPMs on the non-Linux system and instead focus on cross-building packages, should the rpmbuild command not work on the target systems.
+ </div><div class="para">
+ This section covers topics related to building RPMs on or for non-Linux systems.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id762951" class="title">Setting up a build environment</h1></div></div></div><div class="para">
+ In RPM terms, your build environment consists of the directories where you build RPMs, as well as the rc and macro settings that define all of the variables in an RPM-based system. To set up your build environment, you need to ensure that all the rc and macro settings reflect the true environment on your non-Linux system.
+ </div><div class="para">
+ The rpm --showrc command, discussed previously in the "Creating the RPM Environment" section, lists the settings for your system. You can use this command to verify all the settings.
+ </div><div class="para">
+ You may want to change some settings, such as the top directory where RPMs are built. By default, this setting is something like the following:
+ </div><div class="para">
+ _topdir %{_usrsrc}/redhat
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ See <a class="xref" href="#ch-customizing-rpm">Cap. 20, <em>Customizing RPM Behavior</em></a> for more on how to customize the rc and macro settings.
+ </div><div class="para">
+ In most cases the _topdir setting on Red Hat Linux systems map to the /usr/src/redhat directory. Your system may not even have a /usr/src directory. Also you may not want to build RPMs in a redhat directory, which may cause confusion if you are building on a non-Red Hat Linux system.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ See <a class="xref" href="#ch-other-linuxes">Cap. 18, <em>Using RPM on Non-Red Hat Linuxes</em></a> for more information on setting up a build environment for RPMs. <a class="xref" href="#ch-other-linuxes">Cap. 18, <em>Using RPM on Non-Red Hat Linuxes</em></a> focuses on other Linux systems, but many of the same techniques apply.
+ </div><div class="para">
+ With a build environment set up, you should be able to create RPMs with the rpmbuild command. If this doesn’t work, or is too difficult, then you can try cross-building packages.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id1109836" class="title">Cross-building packages</h1></div></div></div><div class="para">
+ You may find that it is too difficult to create RPMs on a given platform. It may be easier to build the RPMs on another platform, such as a Linux system, as if it were on the target platform. This is called cross-building packages, since you are building a package on one system specifically designed for another.
+ </div><div class="para">
+ In most cases, the target platform is quite different from the system where you cross-build packages. Otherwise, you would likely just build the RPMs on the target platform.
+ </div><div class="para">
+ The key issues with cross-building are the following:
+ </div><div class="para">
+ *You must compile any executables with a cross compiler for the proper target platform.
+ </div><div class="para">
+ *You must set the target platform in the RPMs you build.
+ </div><div class="para">
+ *You must manage dependencies, and likely need to turn off the automatic generation of dependencies.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ Setting up a cross-building environment is oftentimes more work than it is worth. If you can compile applications and build packages on the target system, do that. The cross-building option should be used only if you really cannot build packages on the target system. For example, many handheld or small-format computers lack the processor performance or memory to compile applications. These are good candidates for cross-building.
+ </div><div class="para">
+ To compile executables for another platform, especially a platform with a different processor architecture, you need a cross compiler. A cross compiler runs on one system and produces executables for another.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ Cross compilers are heavily used when working with embedded and small device systems. The embedded system may not have the processor power to compile applications, or it may simply be inconvenient to compile applications on the embedded system.
+ </div><div class="para">
+ The Linux gcc compiler can act as a cross compiler if you install the right gcc add-on packages. See the GNU site for more on the gcc compiler.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ You can download GCC and other GNU software from www.gnu.org.
+ </div><div class="para">
+ In addition to compiling for the target platform, you need to ensure that the RPM is marked as being for the target architecture. If not, the rpm command will fail when trying to install the RPM on the target system.
+ </div><div class="para">
+ You can set the target architecture with the --target option to the rpmbuild command. For example:
+ </div><div class="para">
+ rpmbuild –bi --target arm-sharp-linux
+ </div><div class="para">
+ This specifies a target CPU architecture of ARM, the vendor Sharp (which just happens to make an ARM-based Linux device) and the operating system of Linux. The basic format is:
+ </div><div class="para">
+ cpu-vendor-os
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ See <a class="xref" href="#ch-rpmbuild">Cap. 11, <em>Controlling the Build with <code class="command">rpmbuild</code></em></a> for more on using the --target option to the rpmbuild command.
+ </div><div class="para">
+ You must also turn off or correct any automatically generated dependencies in RPMs you build for other platforms. That is, any dependencies based on the operating system or architecture of the system you are cross-building on will likely not be found, or be found in a different location or format, on the target platform.
+ </div><div class="para">
+ This is where the handy RPM feature of automatically building the dependencies does not work to your advantage. You can turn off this feature, however.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ See <a class="xref" href="#ch-other-linuxes">Cap. 18, <em>Using RPM on Non-Red Hat Linuxes</em></a> for information on how to turn off the automatic generation of dependencies.
+ </div><div class="para">
+ You should turn off the automatically building of dependencies for any packages you cross build.
+ </div><div class="para">
+ Using these techniques, you can build packages on one system for use on another, very different system. Due to the difficulties, you should only go this route if it becomes too difficult to use the rpmbuild command on the target systems.
+ </div></div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id518158" class="title">Summary</h1></div></div></div><div class="para">
+ With its superior package-management capabilities, especially for automated installations and upgrades, you may want to use RPM on non-Linux platforms. As the experience of many developers has shown, you can indeed use RPM on non-Linux platforms.
+ </div><div class="para">
+ The rpm.org site maintains a listing of operating systems where developers have ported RPM. If you are lucky, you can download RPM for your operating system and start working right away. If you are not lucky, you will need to port RPM to your target system.
+ </div><div class="para">
+ If RPM has been ported to your architecture, download the package and follow the installation instructions. If RPM has not been ported to your architecture, download the RPM sources and all prerequisite libraries. You may need to port each library to your architecture before you can even begin to port RPM.
+ </div><div class="para">
+ The RPM sources use a configured build process that also requires some prerequisite tools. You need to get or port these to your architecture as well. Whew.
+ </div><div class="para">
+ Once everything is in place, you can start the port of RPM. In many cases, you just need to figure out how to get RPM to compile and everything will fall into place. In other cases, you will need to work on each RPM subsystem to get it to build and run.
+ </div><div class="para">
+ After you have RPM for your system, you need to initialize the RPM database with the rpm --initdb command. You can then start to populate your RPM database. Because a large number of libraries have already been installed on your system, you may need to create a virtual package that claims to provide these files. Installing such a virtual package will allow you to install other RPMs that may be dependent on system libraries.
+ </div><div class="para">
+ Much of porting RPM to another platform depends on the RPM environment and how you need to customize that environment. The next chapter shows how to customize your RPM environment, on Linux or on other operating systems.
+ </div></div></div><div xml:lang="ro" class="chapter" id="ch-customizing-rpm" lang="ro"><div class="titlepage"><div><div><h2 class="title">Cap. 20. Customizing RPM Behavior</h2></div></div></div><div class="toc"><dl><dt><span class="sect1"><a href="#id732671">20.1. Customizing with RPM Macros</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id599573">20.1.1. Defining macros</a></span></dt><dt><span class="sect2"><a href="#id624350">20.1.2. Customizing Macros</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id870277">20.2. Configuring RPM Settings</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id870293">20.2.1. Viewing the current settings</a></span></dt><dt><span class="sect2"><a href="#id579200">20.2.2. Locating the rpmrc files</a></span></dt><dt><span class="sect2"><a href="#id750695">20.2.3. Changing settings</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id559842">20.3. Adding Popt Aliases</a></span></dt><dd><dl><dt><span class="se
ct2"><a href="#id700319">20.3.1. Defining aliases</a></span></dt><dt><span class="sect2"><a href="#id835474">20.3.2. Customizing popt aliases</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id743957">20.4. Summary</a></span></dt></dl></div><div class="para">
+ This chapter covers:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Defining RPM macros
+ </div></li><li class="listitem"><div class="para">
+ Configuring RPM settings
+ </div></li><li class="listitem"><div class="para">
+ Adding popt aliases
+ </div></li></ul></div><div class="para">
+ RPM provides a high degree of customization in the form of basic settings, such as where your RPM database is located and the path to common commands like setup or make, to the ability to define new macros and command-line aliases. This chapter covers the three main ways to customize RPM behavior: RPM macros, RPM rc settings, and popt aliases.
+ </div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id732671" class="title">Customizing with RPM Macros</h1></div></div></div><div class="para">
+ Starting with RPM 3.0, RPM macros have replaced most RPM settings from the rpmrc files.
+ </div><div class="para">
+ An RPM macro defines a setting to the RPM system. A macro can be defined as a static value, such as the directory where the RPM database is installed. A macro can also be defined in terms of other macros. Furthermore, a macro can be defined with parameters.
+ </div><div class="para">
+ For example, the following defines two macros in a macro file:
+ </div><div class="para">
+ %_usr /usr
+ </div><div class="para">
+ %_usrsrc %{_usr}/src
+ </div><div class="para">
+ In this case, the macro %_usr names the /usr directory. The macro %_usrsrc names the /usr/src directory, showing how to set a macro in terms of another macro.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ The macro syntax is used in the query formats introduced in <a class="xref" href="#ch-using-rpm-db">Cap. 4, <em>Using the RPM Database</em></a> .
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id599573" class="title">Defining macros</h1></div></div></div><div class="para">
+ RPM provides a number of places you can define macros, including inside spec files (probably the most common usage), in special macro initialization files, and on the command line.
+ </div><div class="para">
+ In each case, the syntax is slightly different.
+ </div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id616798" class="title">Defining Macros in Spec Files</h1></div></div></div><div class="para">
+ You can define macros in most places in a spec file. With spec files, use the %define syntax to define a macro, which uses the following syntax:
+ </div><div class="para">
+ %define name(options) body
+ </div><div class="para">
+ The options are optional and can include the special values defined in Table 21-1.
+ </div><div class="para">
+ Table 21-1 Special options for macros
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Option
+ </div>
+
+ </td><td>
+ <div class="para">
+ Holds
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ %0
+ </div>
+
+ </td><td>
+ <div class="para">
+ The name of the macro
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ %1
+ </div>
+
+ </td><td>
+ <div class="para">
+ The first argument, after processing with getopt
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ %2-%9
+ </div>
+
+ </td><td>
+ <div class="para">
+ Additional arguments
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ %*
+ </div>
+
+ </td><td>
+ <div class="para">
+ All arguments, except for flags that have been processed
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ %#
+ </div>
+
+ </td><td>
+ <div class="para">
+ Number of arguments
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ These options are similar to those for shell scripting.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ <a class="xref" href="#ch-specfiles">Cap. 9, <em>Working with Spec Files</em></a> covers spec files.
+ </div><div class="para">
+ In addition to these options, you can use a syntax of %{-a} to hold –a if an option of –a was passed. The syntax of %{-a*} indicates the value passed after the –a option.
+ </div><div class="para">
+ You can assign a macro to the value returned by a shell command by using syntax like the following:
+ </div><div class="para">
+ %(shell_command)
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ This is similar to the $(shell_command) syntax supported by bash.
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id503532" class="title">Defining Macros in Macro Initialization Files</h1></div></div></div><div class="para">
+ Inside a macro file, define macros with the following syntax:
+ </div><div class="para">
+ %macro_name value
+ </div><div class="para">
+ Macros defined for the RPM system start with an underscore. Some older macros are left without the leading underscore.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ The macros defined with an underscore are not exported into rpm headers.
+ </div><div class="para">
+ The %expand built-in macro will expand the value of something else, including executing a shell command. For example, the following sets the user’s home directory to the %home macro:
+ </div><div class="para">
+ %home %{expand:%%(cd; pwd)}
+ </div><div class="para">
+ Note that it is probably easier to simply set the %home macro in your per-user $HOME/.rpmmacros file to the name of your home directory rather than try to figure this out programmatically.
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id624315" class="title">Defining Macros on the Command Line</h1></div></div></div><div class="para">
+ The rpm command also lets you define macros with the --define option. The basic syntax is:
+ </div><div class="para">
+ $ rpm --define 'macro_name value'
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ Do not place the leading percent sign, %, on the macro you define with --define.
+ </div><div class="para">
+ You can evaluate a macro or a macro expression with --eval. For example:
+ </div><div class="para">
+ $ rpm --eval %_usrsrc
+ </div><div class="para">
+ /usr/src
+ </div></div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id624350" class="title">Customizing Macros</h1></div></div></div><div class="para">
+ You can add your own macro definitions, using the syntax shown in the “Defining Macros in Macro Initialization Files†section. These macros are read on each invocation of the rpm or rpmbuild commands.
+ </div><div class="para">
+ To add your custom macros, you must edit one of the macro definition files. Table 21-2 lists the macro definition files and their usage.
+ </div><div class="para">
+ Table 21-2 RPM macro files
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ File
+ </div>
+
+ </td><td>
+ <div class="para">
+ Usage
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ /usr/lib/rpm/macros
+ </div>
+
+ </td><td>
+ <div class="para">
+ Official RPM macros
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ /etc/rpm/macros
+ </div>
+
+ </td><td>
+ <div class="para">
+ Per-system customizations
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ $HOME/.rpmmacros
+ </div>
+
+ </td><td>
+ <div class="para">
+ Per-user customizations
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ Note
+ </div><div class="para">
+ Do not edit the /usr/lib/rpm/macros file, as this file gets overwritten when you upgrade to a new version of rpm.
+ </div></div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id870277" class="title">Configuring RPM Settings</h1></div></div></div><div class="para">
+ RPM includes hundreds of settings based on your current system architecture, environment, and which version of the RPM system you have installed. The old settings, called rc or rpmrc settings, are gradually being phased out by the newer, more consistent and more powerful macros.
+ </div><div class="para">
+ You can still edit the rc settings, but in most cases you should edit macros instead.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id870293" class="title">Viewing the current settings</h1></div></div></div><div class="para">
+ To view the current settings, use the --showrc command-line option:
+ </div><div class="para">
+ $ rpm –showrc
+ </div><div class="para">
+ ARCHITECTURE AND OS:
+ </div><div class="para">
+ build arch : i386
+ </div><div class="para">
+ compatible build archs: i686 i586 i486 i386 noarch
+ </div><div class="para">
+ build os : Linux
+ </div><div class="para">
+ compatible build os's : Linux
+ </div><div class="para">
+ install arch : i686
+ </div><div class="para">
+ install os : Linux
+ </div><div class="para">
+ compatible archs : i686 i586 i486 i386 noarch
+ </div><div class="para">
+ compatible os's : Linux
+ </div><div class="para">
+ </div><div class="para">
+ RPMRC VALUES:
+ </div><div class="para">
+ macrofiles : /usr/lib/rpm/macros:/usr/lib/rpm/i686-linux/macros:/etc/
+ </div><div class="para">
+ rpm/macros.specspo:/etc/rpm/macros.db1:/etc/rpm/macros.cdb:/etc/rpm/macros:/etc/
+ </div><div class="para">
+ rpm/i686-linux/macros:~/.rpmmacros
+ </div><div class="para">
+ optflags : -O2 -march=i686
+ </div><div class="para">
+ This command displays the architecture and operating system information first, and then lists all the rpmrc values, shown here truncated for space.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id579200" class="title">Locating the rpmrc files</h1></div></div></div><div class="para">
+ The --showrc option reads in all the rpmrc files from the various locations. By default, this is /usr/lib/rpm/rpmrc, /etc/rpm/rpmrc, and a file named .rpmrc (with a leading period) in your home directory.
+ </div><div class="para">
+ These files are read in the order given, so that the later files can override settings in the earlier files.
+ </div><div class="para">
+ The uses for these files are listed in Table 21-3.
+ </div><div class="para">
+ Table 21-3 Uses for the rpmrc files
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ File
+ </div>
+
+ </td><td>
+ <div class="para">
+ Holds
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ /usr/lib/rpm/rpmrc
+ </div>
+
+ </td><td>
+ <div class="para">
+ RPM standard settings
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ /etc/rpm/rpmrc
+ </div>
+
+ </td><td>
+ <div class="para">
+ Per-system configuration
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ $HOME/.rpmrc
+ </div>
+
+ </td><td>
+ <div class="para">
+ Per-user configuration
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ Note
+ </div><div class="para">
+ The file /usr/lib/rpm/rpmrc gets overwritten each time you upgrade RPM. Do not customize this file.
+ </div><div class="para">
+ You can override this list of files by calling the rpm or rpmbuild commands with the --rcfile option. This option expects a semicolon at nddelimited list of files to read in, in order. For example, if you are working on a 686-architecture Intel platform, you can create a file with the following setting:
+ </div><div class="para">
+ optflags: i686 -g
+ </div><div class="para">
+ Note that this disables optimization, so it is not a good setting. (The use of this value will make the result more visible.)
+ </div><div class="para">
+ If you name this file .rpmnew and place it in your home directory, you can configure an alternate set of files with the --rcfile option and then evaluate the new optflags setting. For example:
+ </div><div class="para">
+ $ rpm --eval "%{optflags}"
+ </div><div class="para">
+ -O2 -march=i386 -mcpu=i686
+ </div><div class="para">
+ $ rpm --rcfile $HOME/.rpmnew --eval "%{optflags}"
+ </div><div class="para">
+ -g
+ </div><div class="para">
+ This example shows the value before and after changing the configuration files.
+ </div><div class="para">
+ When you use the --rcfile option, only the first file listed must exist. The rest of the files are optional. When you use the --rcfile option, however, the file /usr/lib/rpm/rpmrc is read first, and then the list of files you provide with the --rcfile option. The file /usr/lib/rpm/rpmrc is always used.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id750695" class="title">Changing settings</h1></div></div></div><div class="para">
+ You can edit the per-user or per-system rc files to change the settings. The format of the rpmrc files is fairly simple but contains a few exceptions. The most basic format is:
+ </div><div class="para">
+ setting: value
+ </div><div class="para">
+ The settings get more complicated as the rpmrc syntax supports defining settings for multiple architectures at once. In that case, the typical format is:
+ </div><div class="para">
+ setting: uname: value
+ </div><div class="para">
+ The uname portion is replaced by a value that comes from the uname(2) system call, for example, i686 on a 686-class Intel architecture machine.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ In most cases, your best bet is to copy an existing setting and modify it, rather than remembering all the exceptions.
+ </div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id620942" class="title">Setting the optflags</h1></div></div></div><div class="para">
+ One exception to the rule is the optflags setting, which controls C compiler options for optimization. The format for the optflags setting is:
+ </div><div class="para">
+ setting: arch value
+ </div><div class="para">
+ There is no colon after the architecture. For example:
+ </div><div class="para">
+ optflags: i686 -O2 -march=i686
+ </div><div class="para">
+ optflags: alphaev5 -O2 -mieee -mcpu=ev5
+ </div><div class="para">
+ This example sets the optimization flags for an i686 system to -O2 -march=i686 and an alphaev5 system to -O2 -mieee -mcpu=ev5. If your system is running on a 686-class processor, you will get one set of optimization flags. If your system is running on a V5 Alpha processor, you will get a different set.
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id1416245" class="title">Setting the Architecture Values</h1></div></div></div><div class="para">
+ The arch_canon setting builds up a table of mappings between architecture names and the numbers used internally. The following example shows the Intel and SPARC architecture settings to 1 and 3 internally.
+ </div><div class="para">
+ arch_canon: athlon: athlon 1
+ </div><div class="para">
+ arch_canon: i686: i686 1
+ </div><div class="para">
+ arch_canon: i586: i586 1
+ </div><div class="para">
+ arch_canon: i486: i486 1
+ </div><div class="para">
+ arch_canon: i386: i386 1
+ </div><div class="para">
+ </div><div class="para">
+ arch_canon: sparc: sparc 3
+ </div><div class="para">
+ arch_canon: sun4: sparc 3
+ </div><div class="para">
+ arch_canon: sun4m: sparc 3
+ </div><div class="para">
+ arch_canon: sun4c: sparc 3
+ </div><div class="para">
+ arch_canon: sun4d: sparc 3
+ </div><div class="para">
+ arch_canon: sparcv9: sparcv9 3
+ </div><div class="para">
+ The arch_compat setting builds a table of compatible architectures. The format is:
+ </div><div class="para">
+ arch_compat: arch: compatible_with
+ </div><div class="para">
+ This sets the given architecture arch as being compatible with another architecture.
+ </div><div class="para">
+ For example:
+ </div><div class="para">
+ arch_compat: athlon: i686
+ </div><div class="para">
+ This setting indicates that an athlon architecture is compatible with an i686. The table gets built up further with the following Intel-architecture compatibilities:
+ </div><div class="para">
+ arch_compat: i686: i586
+ </div><div class="para">
+ arch_compat: i586: i486
+ </div><div class="para">
+ arch_compat: i486: i386
+ </div><div class="para">
+ arch_compat: i386: noarch
+ </div><div class="para">
+ The os_canon setting defines a table of operating system labels and internal numeric values. The basic syntax is:
+ </div><div class="para">
+ os_canon: arch: name value
+ </div><div class="para">
+ The arch comes from the uname(2) call. The name provides an RPM name for that operating system, and the value defines an internal numeric ID for that OS, for example:
+ </div><div class="para">
+ os_canon: Linux: Linux 1
+ </div><div class="para">
+ os_canon: HP-UX: hpux10 6
+ </div><div class="para">
+ The buildarchtranslate setting defines the operating system settings to use as the build architecture. This value translates information from the uname(2) call to a value used by the arch_canon setting. For example:
+ </div><div class="para">
+ buildarchtranslate: athlon: i386
+ </div><div class="para">
+ buildarchtranslate: i686: i386
+ </div><div class="para">
+ buildarchtranslate: i586: i386
+ </div><div class="para">
+ buildarchtranslate: i486: i386
+ </div><div class="para">
+ buildarchtranslate: i386: i386
+ </div><div class="para">
+ </div><div class="para">
+ buildarchtranslate: sun4c: sparc
+ </div><div class="para">
+ buildarchtranslate: sun4d: sparc
+ </div><div class="para">
+ buildarchtranslate: sun4m: sparc
+ </div><div class="para">
+ buildarchtranslate: sparcv9: sparc
+ </div><div class="para">
+ buildarchtranslate: sun4u: sparc64
+ </div></div></div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id559842" class="title">Adding Popt Aliases</h1></div></div></div><div class="para">
+ Popt provides a powerful library and RPM subsystem for handling the very complex RPM command-line options. You can customize your RPM usage by defining popt aliases for complex command-line arguments to the rpm or rpmbuild commands. A popt alias is a command-line option that expands to other command-line options.
+ </div><div class="para">
+ This technique is used internally to define quite a few command-line options to the rpm and rpmbuild commands in terms of other, more complex options. Many of these aliases define simple command-line options in place of more complex query format options.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ <a class="xref" href="#ch-using-rpm-db">Cap. 4, <em>Using the RPM Database</em></a> covers the query format.
+ </div><div class="para">
+ For example, the following entry defines the --requires and –R command-line options to the rpm command:
+ </div><div class="para">
+ rpm alias --requires --qf \
+ </div><div class="para">
+ "[%{REQUIRENAME} %{REQUIREFLAGS:depflags} %{REQUIREVERSION}\n]" \
+ </div><div class="para">
+ --POPTdesc=$"list capabilities required by package(s)"
+ </div><div class="para">
+ rpm alias -R --requires
+ </div><div class="para">
+ These options are set in the file /usr/lib/rpm/rpmpopt-4.1.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ This is specific to RPM 4.1. Other releases of RPM use the same naming format but with the current RPM version number, such as 4.2 and so on.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id700319" class="title">Defining aliases</h1></div></div></div><div class="para">
+ Defining aliases is pretty easy. The basic syntax is:
+ </div><div class="para">
+ command_name alias option expansion
+ </div><div class="para">
+ To create an alias for the rpm command, you use rpm for the command_name.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ The command_name must be the name passed to the C poptGetContext function, covered in <a class="xref" href="#ch-programming-c">Cap. 15, <em>Programming RPM with C</em></a> .
+ </div><div class="para">
+ Follow this with alias and then the option. You will need separate aliases for the long and short options. The expansion defines the alias in terms of other already-defined command-line parameters.
+ </div><div class="para">
+ You can define some complex aliases, such as the following one to display information about a package:
+ </div><div class="para">
+ rpm alias --info --qf 'Name : %-27{NAME} Relocations: %|PREFIXES?{[%{PREFIXES} ]}:{(not relocateable)}|\n\
+ </div><div class="para">
+ Version : %-27{VERSION} Vendor: %{VENDOR}\n\
+ </div><div class="para">
+ Release : %-27{RELEASE} Build Date: %{BUILDTIME:date}\n\
+ </div><div class="para">
+ Install date: %|INSTALLTIME?{%-27{INSTALLTIME:date}}:{(not installed) }| Build Host: %{BUILDHOST}\n\
+ </div><div class="para">
+ Group : %-27{GROUP} Source RPM: %{SOURCERPM}\n\
+ </div><div class="para">
+ Size : %-27{SIZE}%|LICENSE?{ License: %{LICENSE}}|\n\
+ </div><div class="para">
+ Signature : %|DSAHEADER?{%{DSAHEADER:pgpsig}}:{%|RSAHEADER?{%{RSAHEADER:pgpsig}}:{%|SIGGPG?{%{SIGGPG:pgpsig}}:{%|SIGPGP?{%{SIGPGP:pgpsig}}:{(none)}|}|}|}|\n\
+ </div><div class="para">
+ %|PACKAGER?{Packager : %{PACKAGER}\n}|\
+ </div><div class="para">
+ %|URL?{URL : %{URL}\n}|\
+ </div><div class="para">
+ Summary : %{SUMMARY}\n\
+ </div><div class="para">
+ Description :\n%{DESCRIPTION}\n' \
+ </div><div class="para">
+ --POPTdesc=$"list descriptive information from package(s)"
+ </div><div class="para">
+ Popt aliases get evaluated into Linux commands, so you can use pipes and other aspects of Linux shells in your aliases.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ Look closely at the examples in the /usr/lib/rpm/rpmpopt-4.1 file. This is the most complete set of popt alias examples for RPM commands.
+ </div><div class="para">
+ You can also define aliases that can set RPM macros, such as the following alias for setting the path to the RPM database:
+ </div><div class="para">
+ rpm alias --dbpath --define '_dbpath !#:+'
+ </div><div class="para">
+ In this example, !#:+ was defined to behave like a shell history-editing command. With popt, this means to grab the next command-line parameter and place it into the command defined for the alias.
+ </div><div class="para">
+ To support the --help and --usage options, you can define the --POPTdesc and --POPTargs options to the alias as shown in the previous examples. These options also support internationalization.
+ </div><div class="para">
+ All together, the popt alias setting is very close to the popt option table entries used with the C programming API.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ <a class="xref" href="#ch-programming-c">Cap. 15, <em>Programming RPM with C</em></a> shows how to program with the popt library.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id835474" class="title">Customizing popt aliases</h1></div></div></div><div class="para">
+ Like RPM macros and settings, popt aliases are defined in a cascading set of files. The official RPM aliases are defined in /usr/lib/rpm/rpmpopt-4.1 for rpm 4.1.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ Do not modify this file! The RPM system depends on this file for proper functioning. Incorrect changes might disable many options to the rpm command.
+ </div><div class="para">
+ Store per-system popt aliases in /etc/popt. Store per-user aliases in $HOME/.popt (with a leading period).
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ These files are shared by all applications that use popt.
+ </div><div class="para">
+ For example, you can define an alias for rpm -qa that executes faster than the normal query all packages command, by turning off the tests for digest signature verification. To do so, add the following line to a file named .popt in your home directory:
+ </div><div class="para">
+ rpm alias --qall -qa --nodigest --nosignature
+ </div><div class="para">
+ Once you set up this alias, you can run the following command in place of rpm -qa:
+ </div><div class="para">
+ $ rpm --qall
+ </div><div class="para">
+ This should execute about one-third to one-half faster than the normal rpm -qa command.
+ </div><div class="para">
+ Warning
+ </div><div class="para">
+ Turning off the signature and digest tests means you are ignoring important information that pertains to the integrity of your system. That is why the alias shown here does not override the normal -qa option, and instead defines a new --qall option
+ </div></div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id743957" class="title">Summary</h1></div></div></div><div class="para">
+ This chapter shows the many ways you can customize RPM usage for your system or your own personal environment. You can define RPM macros, which is the preferred way to make RPM settings. Or you can set RPM values in the older rpmrc files, which are now mostly replaced by RPM macros.
+ </div><div class="para">
+ Using popt, the powerful command-line option parser, you can define aliases to add simple options that popt expands into whatever you define. Many of the rpm command-line options are defined this way.
+ </div></div></div><div xml:lang="ro" class="chapter" id="ch-command-reference" lang="ro"><div class="titlepage"><div><div><h2 class="title">Cap. 21. RPM Command Reference</h2></div></div></div><div class="toc"><dl><dt><span class="sect1"><a href="#id886624">21.1. The rpm Command</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id576688">21.1.1. Upgrade, freshen, and install options</a></span></dt><dt><span class="sect2"><a href="#id582449">21.1.2. Erase options</a></span></dt><dt><span class="sect2"><a href="#id640206">21.1.3. Signature options</a></span></dt><dt><span class="sect2"><a href="#id745360">21.1.4. Verify options</a></span></dt><dt><span class="sect2"><a href="#id620160">21.1.5. Database options</a></span></dt><dt><span class="sect2"><a href="#id665079">21.1.6. Miscellaneous options</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id650496">21.2. The rpmbuild Command</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id650509">21.2.1. Bui
lding from a spec file</a></span></dt><dt><span class="sect2"><a href="#id784858">21.2.2. Building from a compressed tar archive</a></span></dt><dt><span class="sect2"><a href="#id703405">21.2.3. Rebuilding RPMs from source RPMs</a></span></dt><dt><span class="sect2"><a href="#id563539">21.2.4. Customizing the build</a></span></dt></dl></dd></dl></div><div class="para">
+ This appendix covers:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ rpm command
+ </div></li><li class="listitem"><div class="para">
+ rpmbuild command
+ </div></li></ul></div><div class="para">
+ This appendix covers the syntax of the command-line options for the rpm and rpmbuild commands.
+ </div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id886624" class="title">The rpm Command</h1></div></div></div><div class="para">
+ The rpm command is the workhorse of the RPM system. The following sections cover options for the major operations with the rpm command.
+ </div><div class="para">
+ Table A-1 lists the query options for the rpm command.
+ </div><div class="para">
+ Table A-1 rpm query options with –q or --query
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Option
+ </div>
+
+ </td><td>
+ <div class="para">
+ Usage
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -a, --all
+ </div>
+
+ </td><td>
+ <div class="para">
+ Query all packages
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -c, --configfiles
+ </div>
+
+ </td><td>
+ <div class="para">
+ List configuration files
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --changelog
+ </div>
+
+ </td><td>
+ <div class="para">
+ List changelog entries
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --conflicts
+ </div>
+
+ </td><td>
+ <div class="para">
+ List capabilities this package conflicts with
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -d, --docfiles
+ </div>
+
+ </td><td>
+ <div class="para">
+ List documentation files
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --dump
+ </div>
+
+ </td><td>
+ <div class="para">
+ Dump out extra information on files.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -f, --file filename
+ </div>
+
+ </td><td>
+ <div class="para">
+ Query for packages owning given file
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --filesbypapkg
+ </div>
+
+ </td><td>
+ <div class="para">
+ List all files in each selected package
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --fileid md5_id
+ </div>
+
+ </td><td>
+ <div class="para">
+ Query for the package with the given MD5 digest
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -g, --group group_name
+ </div>
+
+ </td><td>
+ <div class="para">
+ Query packages in the given group
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --hdrid sha1_header_id
+ </div>
+
+ </td><td>
+ <div class="para">
+ Query for the package with the given header identifier number, in SHA1 format
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -i, --info
+ </div>
+
+ </td><td>
+ <div class="para">
+ Display a lot of package information including description
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --last
+ </div>
+
+ </td><td>
+ <div class="para">
+ Reorder the output of the rpm command to show the most recently installed packages first
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --obsoletes
+ </div>
+
+ </td><td>
+ <div class="para">
+ List capabilities this package obsoletes
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -p, --package rpm_file
+ </div>
+
+ </td><td>
+ <div class="para">
+ Query the given package file or files
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --pkgid md5_id
+ </div>
+
+ </td><td>
+ <div class="para">
+ Query for the package with the given MD5 package ID
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --provides
+ </div>
+
+ </td><td>
+ <div class="para">
+ List capabilities provided by package
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --querybynumber number
+ </div>
+
+ </td><td>
+ <div class="para">
+ Query for the given entry, by number, in the RPM database
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --qf, --queryformat format
+ </div>
+
+ </td><td>
+ <div class="para">
+ Use the given query format for displaying the output
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --redhatprovides capability
+ </div>
+
+ </td><td>
+ <div class="para">
+ Look in rpmdb-redhat database for packages that provide the given capability
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --redhatrequires capability
+ </div>
+
+ </td><td>
+ <div class="para">
+ Look in rpmdb-redhat database for packages that require the given capability
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -R, --requires
+ </div>
+
+ </td><td>
+ <div class="para">
+ Lists packages and capabilities that this package depends on
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --specfile specfile
+ </div>
+
+ </td><td>
+ <div class="para">
+ Query the given spec file
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -s, --state
+ </div>
+
+ </td><td>
+ <div class="para">
+ Display the state of the listed files
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --scripts
+ </div>
+
+ </td><td>
+ <div class="para">
+ List scripts in the package
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --tid transaction_id
+ </div>
+
+ </td><td>
+ <div class="para">
+ Query for the package or packages with the given transaction ID
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --triggeredby package
+ </div>
+
+ </td><td>
+ <div class="para">
+ Query packages triggered by the given package
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --triggers, --triggerscripts
+ </div>
+
+ </td><td>
+ <div class="para">
+ List trigger scripts
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --whatrequires capability
+ </div>
+
+ </td><td>
+ <div class="para">
+ Query packages that require the given capability
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --whatprovides capability
+ </div>
+
+ </td><td>
+ <div class="para">
+ List packages that provide the given capability
+ </div>
+
+ </td></tr></tbody></table></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id576688" class="title">Upgrade, freshen, and install options</h1></div></div></div><div class="para">
+ Table A-2 lists the upgrade, freshen, and installation options for the rpm command.
+ </div><div class="para">
+ Table A-2 rpm upgrade, freshen, and install options
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Option
+ </div>
+
+ </td><td>
+ <div class="para">
+ Usage
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --aid
+ </div>
+
+ </td><td>
+ <div class="para">
+ Add any suggested packages to the list to install or upgrade
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --allfiles
+ </div>
+
+ </td><td>
+ <div class="para">
+ Install all the files, even if some might otherwise be skipped
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --badreloc
+ </div>
+
+ </td><td>
+ <div class="para">
+ Relocate files even if the package is not relocatable
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --excludedocs
+ </div>
+
+ </td><td>
+ <div class="para">
+ Skip the files marked as documentation
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --excludepath path
+ </div>
+
+ </td><td>
+ <div class="para">
+ Skip files that begin with path
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --force
+ </div>
+
+ </td><td>
+ <div class="para">
+ A short hand for --replacepkgs and --replacefiles
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -h, --hash
+ </div>
+
+ </td><td>
+ <div class="para">
+ Print hash marks, #, periodically while performing operation to provide some feedback
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --ignorearch
+ </div>
+
+ </td><td>
+ <div class="para">
+ Ignore the architecture listed in the package
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --ignoreos
+ </div>
+
+ </td><td>
+ <div class="para">
+ Ignore the operating system listed in the package
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --ignoresize
+ </div>
+
+ </td><td>
+ <div class="para">
+ Skip the check to see if there is enough disk space to install the package
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --includedocs
+ </div>
+
+ </td><td>
+ <div class="para">
+ Install files marked as documentation, turned on by default
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --justdb
+ </div>
+
+ </td><td>
+ <div class="para">
+ Just update the RPM database, do not modify any files
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nodeps
+ </div>
+
+ </td><td>
+ <div class="para">
+ Skip verification of package dependencies
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nodigest
+ </div>
+
+ </td><td>
+ <div class="para">
+ Skip verification of package and header digests
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nomd5
+ </div>
+
+ </td><td>
+ <div class="para">
+ Skip verification of file MD5 checksums
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --noorder
+ </div>
+
+ </td><td>
+ <div class="para">
+ Do not reorder the list of packages to be installed based on dependencies
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nopost
+ </div>
+
+ </td><td>
+ <div class="para">
+ Do not run post-install scripts
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nopostun
+ </div>
+
+ </td><td>
+ <div class="para">
+ Do not run post-uninstall scripts
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nopre
+ </div>
+
+ </td><td>
+ <div class="para">
+ Do not run pre-install scripts
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nopreun
+ </div>
+
+ </td><td>
+ <div class="para">
+ Do not run pre-uninstall scripts
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nosuggest
+ </div>
+
+ </td><td>
+ <div class="para">
+ Do not suggest packages for missing dependencies
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --noscripts
+ </div>
+
+ </td><td>
+ <div class="para">
+ Do not execute scripts
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nosignature
+ </div>
+
+ </td><td>
+ <div class="para">
+ Skip verification of package and header signatures
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --notriggers
+ </div>
+
+ </td><td>
+ <div class="para">
+ Do not execute trigger scripts
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --notriggerin
+ </div>
+
+ </td><td>
+ <div class="para">
+ Do not run trigger install scripts
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --notriggerpostun
+ </div>
+
+ </td><td>
+ <div class="para">
+ Do not run trigger post uninstall scripts
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --notriggerun
+ </div>
+
+ </td><td>
+ <div class="para">
+ Do not run trigger uninstall scripts
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --oldpackage
+ </div>
+
+ </td><td>
+ <div class="para">
+ Allow an upgrade to an older version of a package
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --percent
+ </div>
+
+ </td><td>
+ <div class="para">
+ Print out percentage of work completed as command executes
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --prefix directory
+ </div>
+
+ </td><td>
+ <div class="para">
+ Relocate package to directory, if package is relocatable
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --relocate old=new
+ </div>
+
+ </td><td>
+ <div class="para">
+ Relocate all paths that start with old to new, if relocatable
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --repackage
+ </div>
+
+ </td><td>
+ <div class="para">
+ Create a package from any files that would be erased
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --replacefiles
+ </div>
+
+ </td><td>
+ <div class="para">
+ Install package even if it replaces files from other packages
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --replacepkgs
+ </div>
+
+ </td><td>
+ <div class="para">
+ Install packages even if they are already installed
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --test
+ </div>
+
+ </td><td>
+ <div class="para">
+ Do not install or remove packages, just see if the command would work
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ Use rpm –U or --upgrade to upgrade, rpm –i or --install to install, and –F or --freshen to freshen a package.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id582449" class="title">Erase options</h1></div></div></div><div class="para">
+ Table A-3 lists the erase, or package removal, options for the rpm command.
+ </div><div class="para">
+ Table A-3 rpm erase (removal) options with –e or --erase
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Option
+ </div>
+
+ </td><td>
+ <div class="para">
+ Usage
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --allmatches
+ </div>
+
+ </td><td>
+ <div class="para">
+ Remove all versions of the packages; normally an error would occur if there is more than one package of the same name and you try to erase the package
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nodeps
+ </div>
+
+ </td><td>
+ <div class="para">
+ Skip verification of package dependencies
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --noscripts
+ </div>
+
+ </td><td>
+ <div class="para">
+ Do not execute scripts
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nopostun
+ </div>
+
+ </td><td>
+ <div class="para">
+ Do not run post-uninstall scripts
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nopreun
+ </div>
+
+ </td><td>
+ <div class="para">
+ Do not run pre-uninstall scripts
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --notriggers
+ </div>
+
+ </td><td>
+ <div class="para">
+ Do not execute trigger scripts
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --notriggerpostun
+ </div>
+
+ </td><td>
+ <div class="para">
+ Do not run trigger post uninstall scripts
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --notriggerun
+ </div>
+
+ </td><td>
+ <div class="para">
+ Do not run trigger uninstall scripts
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --repackage
+ </div>
+
+ </td><td>
+ <div class="para">
+ Create a package from any files that would be erased
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --test
+ </div>
+
+ </td><td>
+ <div class="para">
+ Do not install or remove packages, just see if the command would work
+ </div>
+
+ </td></tr></tbody></table></div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id640206" class="title">Signature options</h1></div></div></div><div class="para">
+ Table A-4 lists the signature-related options to the rpm command.
+ </div><div class="para">
+ Table A-4 rpm signature options with –K, --checksig, or --import
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Option
+ </div>
+
+ </td><td>
+ <div class="para">
+ Usage
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --addsign
+ </div>
+
+ </td><td>
+ <div class="para">
+ Sign packages, same as --resign
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --import public_key
+ </div>
+
+ </td><td>
+ <div class="para">
+ Add given public key to the RPM database
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nodigest
+ </div>
+
+ </td><td>
+ <div class="para">
+ Skip verification of package and header digests
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nosignature
+ </div>
+
+ </td><td>
+ <div class="para">
+ Skip verification of package and header signatures
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --resign
+ </div>
+
+ </td><td>
+ <div class="para">
+ Sign packages
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ The --import option works on its own. The rest of the options work with one or more RPM packages.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id745360" class="title">Verify options</h1></div></div></div><div class="para">
+ The rpm command can verify packages. This involves comparing all files installed by the package with the information in the RPM database, and looking for differences or missing files.
+ </div><div class="para">
+ Table A-5 lists the verify options to the rpm command.
+ </div><div class="para">
+ Table A-5 rpm verify options with –V or --verify
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Option
+ </div>
+
+ </td><td>
+ <div class="para">
+ Usage
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -a, --all
+ </div>
+
+ </td><td>
+ <div class="para">
+ Verify all packages
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -f, --file filename
+ </div>
+
+ </td><td>
+ <div class="para">
+ Verify packages owning given file
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -g, --group group_name
+ </div>
+
+ </td><td>
+ <div class="para">
+ Verify packages in the given group
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nodeps
+ </div>
+
+ </td><td>
+ <div class="para">
+ Skip verification of package dependencies
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nodigest
+ </div>
+
+ </td><td>
+ <div class="para">
+ Skip verification of package and header digests
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nofiles
+ </div>
+
+ </td><td>
+ <div class="para">
+ Do not verify the files in the package
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nogroup
+ </div>
+
+ </td><td>
+ <div class="para">
+ Do not verify the group owner
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nolinkto
+ </div>
+
+ </td><td>
+ <div class="para">
+ Do not verify the link file attribute
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nomd5
+ </div>
+
+ </td><td>
+ <div class="para">
+ Skip verification of file MD5 checksums
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nomtime
+ </div>
+
+ </td><td>
+ <div class="para">
+ Do not verify the mtime attribute
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nomode
+ </div>
+
+ </td><td>
+ <div class="para">
+ Do not verify the file mode (permissions)
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nordev
+ </div>
+
+ </td><td>
+ <div class="para">
+ Do not verify the rdev attribute
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --noscripts
+ </div>
+
+ </td><td>
+ <div class="para">
+ Do not execute the verify scripts
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nosignature
+ </div>
+
+ </td><td>
+ <div class="para">
+ Skip verification of package and header signatures
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nosize
+ </div>
+
+ </td><td>
+ <div class="para">
+ Do not verify the file size
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nouser
+ </div>
+
+ </td><td>
+ <div class="para">
+ Do not verify the owner of the file
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -p, --package rpm_file
+ </div>
+
+ </td><td>
+ <div class="para">
+ Verify the given package file or files
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --specfile specfile
+ </div>
+
+ </td><td>
+ <div class="para">
+ Verify the given spec file
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --whatrequires capability
+ </div>
+
+ </td><td>
+ <div class="para">
+ Verify packages that require the given capability
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --whatprovides capability
+ </div>
+
+ </td><td>
+ <div class="para">
+ Verify packages that provide the given capability
+ </div>
+
+ </td></tr></tbody></table></div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id620160" class="title">Database options</h1></div></div></div><div class="para">
+ You can create a new, empty, RPM database as well as rebuild all the inverted lists used for quick access using the database options listed in Table A-6.
+ </div><div class="para">
+ Table A-6 rpm database options
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Option
+ </div>
+
+ </td><td>
+ <div class="para">
+ Usage
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --initdb
+ </div>
+
+ </td><td>
+ <div class="para">
+ Initialize database
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --rebuilddb
+ </div>
+
+ </td><td>
+ <div class="para">
+ Rebuild all the inverted lists from the Packages file
+ </div>
+
+ </td></tr></tbody></table></div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id665079" class="title">Miscellaneous options</h1></div></div></div><div class="para">
+ These options can be used with any rpm command. Three of the options, --querytags, --version, and --showrc, run on their own. The rest can be used with the other rpm options. Table A-7 lists these miscellaneous options.
+ </div><div class="para">
+ Table A-7 Miscellaneous rpm options
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Option
+ </div>
+
+ </td><td>
+ <div class="para">
+ Usage
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -?, --help
+ </div>
+
+ </td><td>
+ <div class="para">
+ Print the popt help information for all the command-line options
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --dbpath path_to_rpm_db
+ </div>
+
+ </td><td>
+ <div class="para">
+ Use the given directory for the RPM database, instead of the default
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -D, --define 'macro value'
+ </div>
+
+ </td><td>
+ <div class="para">
+ Define the given macro to hold the given value
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -E, --eval expression
+ </div>
+
+ </td><td>
+ <div class="para">
+ Print the evaluation of the given expression
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --ftpport port
+ </div>
+
+ </td><td>
+ <div class="para">
+ Use the given port number for FTP access
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --ftpproxy host
+ </div>
+
+ </td><td>
+ <div class="para">
+ Use the given host name as a proxy for FTP access
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --httpport port
+ </div>
+
+ </td><td>
+ <div class="para">
+ Use the given port number for HTTP access
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --httpproxy host
+ </div>
+
+ </td><td>
+ <div class="para">
+ Use the given host name as a proxy for HTTP access
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --macros file:file:file
+ </div>
+
+ </td><td>
+ <div class="para">
+ Read the given colon-separated files as the macro files to define RPM macros; only the first file must exist
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --pipe command
+ </div>
+
+ </td><td>
+ <div class="para">
+ Pipe the output of the rpm command to the given command
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --querytags
+ </div>
+
+ </td><td>
+ <div class="para">
+ Print the query tag names and exit
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --quiet
+ </div>
+
+ </td><td>
+ <div class="para">
+ Provide less output, normally show only errors
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --rcfile file:file:file
+ </div>
+
+ </td><td>
+ <div class="para">
+ Read the given colon-separated files as the rc files to define RPM settings; only the first file must exist
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --root directory
+ </div>
+
+ </td><td>
+ <div class="para">
+ Use directory as the top-level directory instead of /.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --showrc
+ </div>
+
+ </td><td>
+ <div class="para">
+ Print the rpmrc and macro configuration and exit
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -v, --verbose
+ </div>
+
+ </td><td>
+ <div class="para">
+ Provide more verbose output
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -vv
+ </div>
+
+ </td><td>
+ <div class="para">
+ Provide even more verbose output, including debugging information
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --version
+ </div>
+
+ </td><td>
+ <div class="para">
+ Print the RPM version and exit
+ </div>
+
+ </td></tr></tbody></table></div></div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id650496" class="title">The rpmbuild Command</h1></div></div></div><div class="para">
+ The rpmbuild command builds RPMs. Most of the options are duplicated. The options that begin with –b build from a spec file, and the options that begin with –t build from a compressed tar archive, commonly called a tarball.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id650509" class="title">Building from a spec file</h1></div></div></div><div class="para">
+ Table A-8 lists the rpmbuild options for building RPMs from a spec file.
+ </div><div class="para">
+ Table A-8 Options for building RPMs from a spec file
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Option
+ </div>
+
+ </td><td>
+ <div class="para">
+ Usage
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -ba
+ </div>
+
+ </td><td>
+ <div class="para">
+ Build all, both a binary and source RPM
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -bb
+ </div>
+
+ </td><td>
+ <div class="para">
+ Build a binary RPM
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -bc
+ </div>
+
+ </td><td>
+ <div class="para">
+ Build (compile) the program but do not make the full RPM, by executing the build commands through the %build section and stopping
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -bp
+ </div>
+
+ </td><td>
+ <div class="para">
+ Prepare for building a binary RPM, by executing the build commands through the %prep section and stopping
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -bi
+ </div>
+
+ </td><td>
+ <div class="para">
+ Execute the build commands through the %install section and stop
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -bl
+ </div>
+
+ </td><td>
+ <div class="para">
+ Check the listing of files for the RPM
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -bs
+ </div>
+
+ </td><td>
+ <div class="para">
+ Build a source RPM only
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ Each of these options requires the name of a spec file at the end of the command line.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id784858" class="title">Building from a compressed tar archive</h1></div></div></div><div class="para">
+ Table A-9 lists the rpmbuild options for working with a compressed tar archive.
+ </div><div class="para">
+ Table A-9 Options for building RPMs from a compressed tar archive
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Option
+ </div>
+
+ </td><td>
+ <div class="para">
+ Usage
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -ta
+ </div>
+
+ </td><td>
+ <div class="para">
+ Build all, both a binary and source RPM
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -tb
+ </div>
+
+ </td><td>
+ <div class="para">
+ Build a binary RPM
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -tc
+ </div>
+
+ </td><td>
+ <div class="para">
+ Build (compile) the program but do not make the full RPM, by executing the build commands through the %build section and stopping
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -tp
+ </div>
+
+ </td><td>
+ <div class="para">
+ Prepare for building a binary RPM, by executing the build commands through the %prep section and stopping
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -ti
+ </div>
+
+ </td><td>
+ <div class="para">
+ Execute the build commands through the %install section and stop
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -tl
+ </div>
+
+ </td><td>
+ <div class="para">
+ Check the listing of files for the RPM
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -ts
+ </div>
+
+ </td><td>
+ <div class="para">
+ Build a source RPM only
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ Each of these options requires the name of a compressed tar archive at the end of the command line. The tar archive must contain a valid spec file inside the archive.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id703405" class="title">Rebuilding RPMs from source RPMs</h1></div></div></div><div class="para">
+ You can use the rpmbuild command to rebuild an RPM from a source RPM with the options listed in Table A-10.
+ </div><div class="para">
+ Table A-10 Options for rebuilding RPMs from source RPMs
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Option
+ </div>
+
+ </td><td>
+ <div class="para">
+ Usage
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --rebuild
+ </div>
+
+ </td><td>
+ <div class="para">
+ Rebuild binary RPM from source RPM
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --recompile
+ </div>
+
+ </td><td>
+ <div class="para">
+ Recompile binary RPM from source RPM
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ Each of these options requires the name of a source RPM file on the end of the command line.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id563539" class="title">Customizing the build</h1></div></div></div><div class="para">
+ You can customize the rpmbuild command with the options listed in Table A-11.
+ </div><div class="para">
+ Table A-11 Extra build options for the rpmbuild command
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Option
+ </div>
+
+ </td><td>
+ <div class="para">
+ Usage
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -?, --help
+ </div>
+
+ </td><td>
+ <div class="para">
+ Print the popt help information for all the command-line options
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --buildroot directory
+ </div>
+
+ </td><td>
+ <div class="para">
+ Override the default root directory for building with directory.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --clean
+ </div>
+
+ </td><td>
+ <div class="para">
+ Remove the build tree after building
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -D, --define 'macro value'
+ </div>
+
+ </td><td>
+ <div class="para">
+ Define the given macro to hold the given value
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --dbpath path_to_rpm_db
+ </div>
+
+ </td><td>
+ <div class="para">
+ Use the given directory for the RPM database instead of the default
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -E, --eval expression
+ </div>
+
+ </td><td>
+ <div class="para">
+ Print the evaluation of the given expression
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --macros file:file:file
+ </div>
+
+ </td><td>
+ <div class="para">
+ Read the given colon-separated files as the macro files to define RPM macros; only the first file must exist
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nobuild
+ </div>
+
+ </td><td>
+ <div class="para">
+ Don't really build anything, which really tests the spec file
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --pipe command
+ </div>
+
+ </td><td>
+ <div class="para">
+ Pipe the output of the rpm command to the given command
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --quiet
+ </div>
+
+ </td><td>
+ <div class="para">
+ Provide less output, normally show only errors
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --rcfile file:file:file
+ </div>
+
+ </td><td>
+ <div class="para">
+ Read the given colon-separated files as the rc files to define RPM settings; only the first file must exist
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --rmsource
+ </div>
+
+ </td><td>
+ <div class="para">
+ Remove the sources after the build
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --rmspec
+ </div>
+
+ </td><td>
+ <div class="para">
+ Remove the spec file after the build
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --root directory
+ </div>
+
+ </td><td>
+ <div class="para">
+ Use directory as the top-level directory instead of /
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --short-circuit
+ </div>
+
+ </td><td>
+ <div class="para">
+ With the -bc or -bi options, jumps directly to the given stage and just executes that stage
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --showrc
+ </div>
+
+ </td><td>
+ <div class="para">
+ Print the rpmrc and macro configuration and exit
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --sign
+ </div>
+
+ </td><td>
+ <div class="para">
+ Sign the package with a GPG signature
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --target platform
+ </div>
+
+ </td><td>
+ <div class="para">
+ Build for the given platform. May not work if you don't have the other platform build commands, such as cross compilers, set up. Can work for Intel platforms with i386, i686, and so on.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -v, --verbose
+ </div>
+
+ </td><td>
+ <div class="para">
+ Provide more verbose output
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -vv
+ </div>
+
+ </td><td>
+ <div class="para">
+ Provide even more verbose output, including debugging information
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --version
+ </div>
+
+ </td><td>
+ <div class="para">
+ Print the RPM version and exit
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ </div></div></div></div><div xml:lang="ro" class="chapter" id="ch-specfile-syntax" lang="ro"><div class="titlepage"><div><div><h2 class="title">Cap. 22. Spec File Syntax</h2></div></div></div><div class="toc"><dl><dt><span class="sect1"><a href="#id764656">22.1. Package Information Tags</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id690830">22.1.1. Comments</a></span></dt><dt><span class="sect2"><a href="#id843939">22.1.2. Build settings</a></span></dt><dt><span class="sect2"><a href="#id1283550">22.1.3. Dependency tags</a></span></dt><dt><span class="sect2"><a href="#id642245">22.1.4. Source files</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id662269">22.2. Macros</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id662281">22.2.1. Variable definition macros</a></span></dt><dt><span class="sect2"><a href="#id622855">22.2.2. Conditional macros</a></span></dt><dt><span class="sect2"><a href="#id571162">22.2.3. Built-in macros</a></span></dt></
dl></dd><dt><span class="sect1"><a href="#id853518">22.3. Build Sections</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id1363142">22.3.1. Build preparation</a></span></dt><dt><span class="sect2"><a href="#id1363163">22.3.2. Build</a></span></dt><dt><span class="sect2"><a href="#id860560">22.3.3. Installation</a></span></dt><dt><span class="sect2"><a href="#id613014">22.3.4. Clean up</a></span></dt><dt><span class="sect2"><a href="#id613035">22.3.5. Install and uninstall scripts</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id731001">22.4. File Tags</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id887593">22.4.1. Making relocatable packages</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id887623">22.5. The Change Log</a></span></dt></dl></div><div class="para">
+ This appendix covers:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ The package information tags
+ </div></li><li class="listitem"><div class="para">
+ Build sections
+ </div></li></ul></div><div class="para">
+ The RPM spec file is divided into two main parts: the package information tags, such as the name of the package, and the build sections, such as the commands to compile the software.
+ </div><div class="para">
+ The following sections summarize the spec file syntax.
+ </div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id764656" class="title">Package Information Tags</h1></div></div></div><div class="para">
+ The package information tags contain most of the header tags that you can query with the rpm command. First and foremost, this includes a name.
+ </div><div class="para">
+ The name-epoch-version-release tags, which form the NEVR used to identify packages, should all appear in your spec file, although you can skip the Epoch tag.
+ </div><div class="para">
+ Name: name
+ </div><div class="para">
+ # Epoch: 1
+ </div><div class="para">
+ Version: version_number
+ </div><div class="para">
+ Release: package_release_number
+ </div><div class="para">
+ The optional Epoch tag provides an ordering for the version numbers (replacing the deprecated Serial tag). Use this tag if RPM cannot figure out the ordering of which release comes after another.
+ </div><div class="para">
+ Epoch: 42
+ </div><div class="para">
+ A number of tags allow you to define who made the package and under what conditions has the package been released:
+ </div><div class="para">
+ Vendor: name_of_vendor
+ </div><div class="para">
+ URL: URL_to_package_home
+ </div><div class="para">
+ Copyright: package_copyright_message
+ </div><div class="para">
+ Distribution: Linux_or_product_distribution
+ </div><div class="para">
+ Packager: John Q. Smith <john.smith at somecompany.yow>
+ </div><div class="para">
+ Group: group_for_categorizing_package
+ </div><div class="para">
+ Use the Group tag to help users categorize your package.
+ </div><div class="para">
+ The Icon tag allows you to provide a desktop icon for the package:
+ </div><div class="para">
+ Icon: filename.xpm
+ </div><div class="para">
+ A one-line summary is essential to tell users what your package is for:
+ </div><div class="para">
+ Summary: one_line_description_of_package
+ </div><div class="para">
+ You should also include a longer description section, marked by %description:
+ </div><div class="para">
+ %description
+ </div><div class="para">
+ Tcsh is an enhanced but completely compatible version of csh, the C
+ </div><div class="para">
+ shell. Tcsh is a command language interpreter which can be used both
+ </div><div class="para">
+ as an interactive login shell and as a shell script command processor.
+ </div><div class="para">
+ Tcsh includes a command line editor, programmable word completion,
+ </div><div class="para">
+ spelling correction, a history mechanism, job control and a C language
+ </div><div class="para">
+ like syntax.
+ </div><div class="para">
+ In the description section, blank lines indicate paragraphs. Lines that start with a space are not formatted.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id690830" class="title">Comments</h1></div></div></div><div class="para">
+ To help document your work, you can include comments (to yourself and others reading the spec file). Any line starting with a hash character, #, holds a comment. RPM will ignore comments.
+ </div><div class="para">
+ # This is a comment.
+ </div><div class="para">
+ In spec files, comments are used mostly to help explain your syntax choices to yourself should you view the spec file later.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ Avoid percent signs, %, in comments, which may get interpreted as RPM macros. See <a class="xref" href="#ch-specfiles">Cap. 9, <em>Working with Spec Files</em></a> for details.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id843939" class="title">Build settings</h1></div></div></div><div class="para">
+ The BuildArchitectures tag names the architectures that a binary RPM will run on. See <a class="xref" href="#ch-customizing-rpm">Cap. 20, <em>Customizing RPM Behavior</em></a> for a description of the architecture settings. A special value of noarch indicates a package that is not dependent on a particular architecture, such as a Perl or Python script.
+ </div><div class="para">
+ The BuildPreReq tag lists any prerequisites for building. For example:
+ </div><div class="para">
+ BuildPreReq: ncurses-devel
+ </div><div class="para">
+ The Buildroot tag names the temporary directory in which to build the package. For example:
+ </div><div class="para">
+ Buildroot: %{_tmppath}/%{name}-root
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id1283550" class="title">Dependency tags</h1></div></div></div><div class="para">
+ Dependency tags define all the dependencies for the package, as described in <a class="xref" href="#ch-dependencies">Cap. 5, <em>Package Dependencies</em></a> .
+ </div><div class="para">
+ For each dependency, you can specify a capability name alone. For example:
+ </div><div class="para">
+ Provides: capability_name
+ </div><div class="para">
+ You can also provide a particular version number or indicate that your package has a dependency on a version larger or smaller than a given number. For example:
+ </div><div class="para">
+ Requires: capability_name >= version_number
+ </div><div class="para">
+ Requires: capability_name <= version_number
+ </div><div class="para">
+ Requires: capability_name > version_number
+ </div><div class="para">
+ Requires: capability_name < version_number
+ </div><div class="para">
+ Requires: capability_name == version_number
+ </div><div class="para">
+ Requires: capability_name = version_number
+ </div><div class="para">
+ The == and = act the same for dependencies. Both check for a version equal to the given number. You can provide multiple items, separated by commas. For example:
+ </div><div class="para">
+ Requires: python >= 1.3, perl
+ </div><div class="para">
+ For add-on modules for interpreters, especially Perl, you can use the following syntax to define capabilities:
+ </div><div class="para">
+ Provides: perl(MIME-Base64)
+ </div><div class="para">
+ This example provides the MIME-Base64 add-on Perl module.
+ </div><div class="para">
+ You can also use or to specify more than one possibility. For example:
+ </div><div class="para">
+ perl(IO-Wrap) == 4.5 or perl(IO-Wrap)-4.5
+ </div><div class="para">
+ The Provides, Requires, Obsoletes, and Conflicts dependency tags all work the same for capability names and version numbers.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ You can also specify BuildRequires tags for capabilities necessary to build the package, not to install it. A BuildConflicts tag names capabilities that conflict for building, such as a particular version of the gcc C compiler.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id642245" class="title">Source files</h1></div></div></div><div class="para">
+ The source and patch tags identify the source files used to build the binary package. The patch tags identify any patches used to modify the sources.
+ </div><div class="para">
+ If you have more than one of a particular kind of tag, append a number. For example:
+ </div><div class="para">
+ Source0: ftp://ftp.uk.linux.org/pub/linux/telnet-%{telnet_version}.tar.gz
+ </div><div class="para">
+ Source2: telnet-client.tar.gz
+ </div><div class="para">
+ Source3: telnet-xinetd
+ </div><div class="para">
+ Source4: telnet.wmconfig
+ </div><div class="para">
+ Patch1: telnet-client-cvs.patch
+ </div><div class="para">
+ Patch5: telnetd-0.17.diff
+ </div><div class="para">
+ Patch6: telnet-0.17-env.patch
+ </div><div class="para">
+ Patch7: telnet-0.17-issue.patch
+ </div><div class="para">
+ Patch8: telnet-0.17-sa-01-49.patch
+ </div><div class="para">
+ Patch9: telnet-0.17-env-5x.patch
+ </div><div class="para">
+ Patch10: telnet-0.17-pek.patch
+ </div></div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id662269" class="title">Macros</h1></div></div></div><div class="para">
+ You can define macros in your spec files to help control how the package gets built. The following section describes these macros.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id662281" class="title">Variable definition macros</h1></div></div></div><div class="para">
+ The %define macro allows you to define new macros from within your spec file. A common usage is to define top-level directories with %define macros at the top of a spec file and then reference these directories throughout the file. For example:
+ </div><div class="para">
+ %define_bindir/bin
+ </div><div class="para">
+ This allows you to change the setting in one place, which is very handy for directory paths used throughout your spec files.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ See the section on Defining Macros in Spec Files in <a class="xref" href="#ch-specfile-syntax">Cap. 22, <em>Spec File Syntax</em></a> for more on this subject.
+ </div><div class="para">
+ You can use this syntax for other things that may commonly change, such as version numbers. For example:
+ </div><div class="para">
+ %define major 2
+ </div><div class="para">
+ %define minor 2
+ </div><div class="para">
+ %define patchlevel 7
+ </div><div class="para">
+ Version: %{major}.%{minor}.%{patchlevel}
+ </div><div class="para">
+ Table B-1 lists more special macros used within spec files.
+ </div><div class="para">
+ Table B-1 Special spec file macros
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Macro
+ </div>
+
+ </td><td>
+ <div class="para">
+ Usage
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ %dump
+ </div>
+
+ </td><td>
+ <div class="para">
+ Prints out macro values
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ %{echo:message}
+ </div>
+
+ </td><td>
+ <div class="para">
+ Prints message to stderr
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ %{error:message}
+ </div>
+
+ </td><td>
+ <div class="para">
+ Prints message to stderr and returns BADSPEC
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ %{expand:expression}
+ </div>
+
+ </td><td>
+ <div class="para">
+ Like eval, expands expression
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ %{F:file_exp}
+ </div>
+
+ </td><td>
+ <div class="para">
+ Expands file_exp to a file name
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ %global name value
+ </div>
+
+ </td><td>
+ <div class="para">
+ Defines a global macro
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ %{P:patch_exp}
+ </div>
+
+ </td><td>
+ <div class="para">
+ Expands patch_exp to a patch file name
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ %{S:source_exp}
+ </div>
+
+ </td><td>
+ <div class="para">
+ Expands source_exp to a source file name
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ %trace
+ </div>
+
+ </td><td>
+ <div class="para">
+ Toggles the printing of debugging information
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ %{uncompress:filename}
+ </div>
+
+ </td><td>
+ <div class="para">
+ Tests if file filename is compressed. If so, uncompresses and includes in the given context. If not compressed, calls cat to include file in given context.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ %undefine macro
+ </div>
+
+ </td><td>
+ <div class="para">
+ Undefines the given macro
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ %{warn:message}
+ </div>
+
+ </td><td>
+ <div class="para">
+ Prints message to stderr
+ </div>
+
+ </td></tr></tbody></table></div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id622855" class="title">Conditional macros</h1></div></div></div><div class="para">
+ You can use a special syntax to test for the existence of macros. For example:
+ </div><div class="para">
+ %{?macro_to_test: expression}
+ </div><div class="para">
+ This syntax tells RPM to expand the expression if macro_to_test exists, otherwise ignore. A leading exclamation point, !, tests for the non-existence of a macro:
+ </div><div class="para">
+ %{!?macro_to_test: expression}
+ </div><div class="para">
+ In this example, if the macro_to_test macro does not exist, then expand the expression.
+ </div><div class="para">
+ The %if macro performs an if test much like scripting languages. For example:
+ </div><div class="para">
+ %if %{old_5x}
+ </div><div class="para">
+ %define b5x 1
+ </div><div class="para">
+ %undefine b6x
+ </div><div class="para">
+ %endif
+ </div><div class="para">
+ A %else allows you to specify what to do if the test is not successful. For example:
+ </div><div class="para">
+ %if %{old_5x}
+ </div><div class="para">
+ %define b5x 1
+ </div><div class="para">
+ %undefine b6x
+ </div><div class="para">
+ %else
+ </div><div class="para">
+ %define b6x 1
+ </div><div class="para">
+ %undefine b5x
+ </div><div class="para">
+ %endif
+ </div><div class="para">
+ Again, use an exclamation point to negate the test. For example:
+ </div><div class="para">
+ %if ! %{old_5x}
+ </div><div class="para">
+ %define b5x 1
+ </div><div class="para">
+ %undefine b6x
+ </div><div class="para">
+ %endif
+ </div><div class="para">
+ You can use a && for an and test. For example:
+ </div><div class="para">
+ %if %{old_5x} && %{old_6x}
+ </div><div class="para">
+ %{error: You cannot build for .5x and .6x at the same time}
+ </div><div class="para">
+ %quit
+ </div><div class="para">
+ %endif
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id571162" class="title">Built-in macros</h1></div></div></div><div class="para">
+ The following macros are built into RPM and can help allow you to place your files in the right locations:
+ </div><div class="para">
+ %_prefix /usr
+ </div><div class="para">
+ %_exec_prefix %{_prefix}
+ </div><div class="para">
+ %_bindir %{_exec_prefix}/bin
+ </div><div class="para">
+ %_sbindir %{_exec_prefix}/sbin
+ </div><div class="para">
+ %_libexecdir %{_exec_prefix}/libexec
+ </div><div class="para">
+ %_datadir %{_prefix}/share
+ </div><div class="para">
+ %_sysconfdir %{_prefix}/etc
+ </div><div class="para">
+ %_sharedstatedir %{_prefix}/com
+ </div><div class="para">
+ %_localstatedir %{_prefix}/var
+ </div><div class="para">
+ %_libdir %{_exec_prefix}/lib
+ </div><div class="para">
+ %_includedir %{_prefix}/include
+ </div><div class="para">
+ %_oldincludedir /usr/include
+ </div><div class="para">
+ %_infodir %{_prefix}/info
+ </div><div class="para">
+ %_mandir %{_prefix}/man
+ </div></div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id853518" class="title">Build Sections</h1></div></div></div><div class="para">
+ After providing information about the package, you need to define the build stages, as described in <a class="xref" href="#ch-specfiles">Cap. 9, <em>Working with Spec Files</em></a> and <a class="xref" href="#ch-rpmbuild">Cap. 11, <em>Controlling the Build with <code class="command">rpmbuild</code></em></a>.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id1363142" class="title">Build preparation</h1></div></div></div><div class="para">
+ The build preparation section sets the stage for the build. Usually this section has a %setup command. For example:
+ </div><div class="para">
+ %prep
+ </div><div class="para">
+ %setup -q
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id1363163" class="title">Build</h1></div></div></div><div class="para">
+ The build section describes how to build the library or application. In most cases, the majority of the instructions are in the Makefile created by the prep section, leaving a build section something like the following:
+ </div><div class="para">
+ %build
+ </div><div class="para">
+ %configure
+ </div><div class="para">
+ make
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id860560" class="title">Installation</h1></div></div></div><div class="para">
+ After building, the installation section holds the commands to install the library or application. For example:
+ </div><div class="para">
+ %install
+ </div><div class="para">
+ rm -rf %{buildroot}
+ </div><div class="para">
+ %makeinstall
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id613014" class="title">Clean up</h1></div></div></div><div class="para">
+ The clean up section usually calls the make clean command to clean up the built files. For example:
+ </div><div class="para">
+ %clean
+ </div><div class="para">
+ rm -rf %{buildroot}
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id613035" class="title">Install and uninstall scripts</h1></div></div></div><div class="para">
+ RPM packages can run scripts prior to installation with %pre, and after installation with %post. You can also run scripts prior to an uninstall with %preun and after an uninstall with %postun. For example:
+ </div><div class="para">
+ %post
+ </div><div class="para">
+ /sbin/chkconfig --add ypbind
+ </div><div class="para">
+ </div><div class="para">
+ %preun
+ </div><div class="para">
+ if [ "$1" = 0 ] ; then
+ </div><div class="para">
+ /sbin/service ypbind stop > /dev/null 2>&1
+ </div><div class="para">
+ /sbin/chkconfig --del ypbind
+ </div><div class="para">
+ fi
+ </div><div class="para">
+ exit 0
+ </div><div class="para">
+ </div><div class="para">
+ %postun
+ </div><div class="para">
+ if [ "$1" -ge 1 ]; then
+ </div><div class="para">
+ /sbin/service ypbind condrestart > /dev/null 2>&1
+ </div><div class="para">
+ fi
+ </div><div class="para">
+ exit 0
+ </div></div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id731001" class="title">File Tags</h1></div></div></div><div class="para">
+ The %files tag lists the files your package should install. For example:
+ </div><div class="para">
+ %files
+ </div><div class="para">
+ %defattr(-,root,root)
+ </div><div class="para">
+ /usr/X11R6/bin/xtoolwait
+ </div><div class="para">
+ /usr/X11R6/man/man1/xtoolwait.*
+ </div><div class="para">
+ You should mark configuration and documentation files with %config and %doc, respectively. For example:
+ </div><div class="para">
+ %files
+ </div><div class="para">
+ %defattr(-,root,root)
+ </div><div class="para">
+ /sbin/ypbind
+ </div><div class="para">
+ %{_mandir}/*/*
+ </div><div class="para">
+ %config /etc/rc.d/init.d/*
+ </div><div class="para">
+ %config /etc/yp.conf
+ </div><div class="para">
+ %dir /var/yp
+ </div><div class="para">
+ %dir /var/yp/binding
+ </div><div class="para">
+ %doc README NEWS
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id887593" class="title">Making relocatable packages</h1></div></div></div><div class="para">
+ You can make a relocatable package by setting up one or more Prefix tags. For example:
+ </div><div class="para">
+ Prefix: /usr
+ </div><div class="para">
+ Prefix: /etc
+ </div><div class="para">
+ Each file in the %files section must then start with one of the prefixes you provided. With this, installers can easily relocate the package with a command like the following:
+ </div><div class="para">
+ # rpm --relocate /etc=/usr/etc file_name.rpm
+ </div></div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id887623" class="title">The Change Log</h1></div></div></div><div class="para">
+ The change log usually appears at the end of a spec file. It holds messages for each significant change. For example:
+ </div><div class="para">
+ %changelog
+ </div><div class="para">
+ * Fri Jun 21 2002 Bob Marley <marley at redhat.com>
+ </div><div class="para">
+ - automated rebuild
+ </div><div class="para">
+ </div><div class="para">
+ * Tue May 08 2001 Peter Tosh <tosh at redhat.com> 1.3-1
+ </div><div class="para">
+ - updated to 1.3
+ </div></div></div><div xml:lang="ro" class="chapter" id="ch-rpm-evolution" lang="ro"><div class="titlepage"><div><div><h2 class="title">Cap. 23. RPM Feature Evolution</h2></div></div></div><div class="para">
+ Although RPM implementations are largely compatible from version to version, RPM packagers must remember that RPM is a still-evolving program and that its developers are adding features to it with each new version. When producing RPM package files, packagers must keep in mind the audience that will be using the final RPM package files. They must decide which versions of RPM they intend the package to be used with and must use only the lowest common denominator set of features implemented in the oldest of the RPM versions they are targeting. As a quick reference, keep in mind the RPM features noted here and the RPM version in which they are introduced. In considering these revisions of RPM, the main releases of interest are RPM 2.5, RPM 3.0.5, RPM 4.0.4, and RPM 4.1.
+ </div><div class="para">
+ RPM 2.5 is not widely used anymore; packages should target RPM 2.5 only if the intention is for the RPM package to install using absolutely all RPM versions.
+ </div><div class="para">
+ RPM 3.0.5 is the final release of the 3.x series of RPM. It was the release of RPM shipped with Red Hat Linux 6.2 and older releases. It is still in wide use by other vendors as well. Cobalt’s Linux distributions use an RPM implementation version based on RPM 3.0.5, for example. (Red Hat Linux was upgraded to RPM 4 via an errata.)
+ </div><div class="para">
+ RPM 4.0.4 was used with the 7.x releases of Red Hat Linux, and RPM 4.1 first shipped with Red Hat Linux 8.0. Packages produced targeting RPM 3.0.5 should work with nearly all implementations of RPM still in use today. Packages produced targeting RPM 4.0.4 or RPM 4.1 will work only with recent RPM implementations.
+ </div><div class="para">
+ RPM 2.5 is the oldest version of RPM that can, by any stretch of the imagination, still be considered in use. With RPM 2.5, most of the basic RPM features were in place, as well as more advanced functions such as triggers and support for internationalization of Summary:, Description:, and Group: tags in the RPM file header. RPM 2.5 was also the first version of RPM to use the RPM version 3 RPM file format.
+ </div><div class="para">
+ RPM 2.5.3 added support for Epochs to the RPM header, implementing RPMTAG_EPOCH.
+ </div><div class="para">
+ RPM 2.5.4 introduced the %license and %readme file types, which can be used in the RPM spec file to indicate license and README files.
+ </div><div class="para">
+ RPM 2.5.6 added support for usage of the Epoch: keyword in the RPM spec file, allowing you to force an Epoch for your package. The Epoch: keyword replaced the older Serial: keyword, which semantically behaved similarly.
+ </div><div class="para">
+ RPM 2.5.7 enforced the previously implied standard that the "-" character should not be used within the Version or Release fields in the RPM spec file.
+ </div><div class="para">
+ RPM 2.90 introduced support for signing and verifying RPM package files using GPG, the GNU Privacy Guard.
+ </div><div class="para">
+ RPM 2.91 allowed the usage of Provides: directives that defined absolute paths to provided files. Prior to RPM 2.91, Provides: could be used only for listing provided capabilities, not for using statements like Provides: /path/to/file to indicate provided files.
+ </div><div class="para">
+ RPM 3.0.2 permitted usage of multiple Provides: lines for the first time, eliminating the need to combine all provided capabilities and files on the same line in the spec file.
+ </div><div class="para">
+ RPM 3.0.3 added support for versioned dependencies. Prior to RPM 3.0.3, spec files could indicate that a package required another package or provided a specific capability, but they could not indicate the acceptable versions of the required package or which version of the capability the package provided.
+ </div><div class="para">
+ RPM 3.0.4 introduced CompressedFileNames support to RPM. Prior to RPM 3.0.4, RPM packaged the absolute paths of all archived files within the package file. Package file headers contained statements such as
+ </div><div class="para">
+ fileName #0: /usr/bin/ar
+ </div><div class="para">
+ fileName #1: /usr/bin/as
+ </div><div class="para">
+ fileName #2: /usr/bin/gasp
+ </div><div class="para">
+ fileName #3: /usr/bin/gprof
+ </div><div class="para">
+ With CompressedFileNames support, the RPM package file header instead stores the directory name, then just the base name of files within that directory. Package file headers now contain statements such as the following for a given directory with a number of files within that directory:
+ </div><div class="para">
+ dirName #0: /usr/bin
+ </div><div class="para">
+ baseName dirIndex
+ </div><div class="para">
+ #0 ar 0
+ </div><div class="para">
+ #1 as 0
+ </div><div class="para">
+ #2 gasp 0
+ </div><div class="para">
+ #3 gprof 0
+ </div><div class="para">
+ Each file entry now holds the file's base name within the directory, as well as an index number that refers to the directory entry. Since packages typically contain lots of files within the same directory, CompressedFileNames support results in significant memory savings when processing packages for installation.
+ </div><div class="para">
+ RPM 3.0.5 added PayloadIsBzip2 support to RPM, allowing the data payload of RPM package files to be compressed using bzip2 instead of gzip. Even though RPM now supports bzip2 compression of package files, this feature is rarely used in practice, since significantly more memory and time is required to install bzip2-compressed RPM package files than to install gzip-compressed RPM package files. RPM 3.0.5 also added support to RPM for manipulating existing RPM version 4 file format packages; packages produced with RPM 3.0.5 can only be RPM version 3 file format, however.
+ </div><div class="para">
+ RPM 4.0 implemented several significant changes to RPM. RPM 4.0 created package files using RPM version 4 package file format. RPM 4.0 also switched from Berkeley db 1.85 to Berkeley db 3.1 as the database program used for creation and manipulation of the RPM database. The RPM package database file was renamed as well. The db3 package database file is /var/lib/rpm/Packages, and the older db1 package database file was /var/lib/rpm/packages.rpm. Changing the package database file name allowed old and new versions to co-exist if necessary, simplifying upgrades from older RPM releases to the new RPM 4.0 release. RPM 4.0 also introduced the PayloadFilesHavePrefix feature, changing the way archived files are named within the RPM package file. RPM package files contain a cpio archive of files. Prior to RPM 4.0, file names in the cpio archive were stored without a root prefix. With PayloadFilesHavePrefix, all file names within the cpio archive files now have a root prefix, such as
./usr/bin/ar. This modification made it possible for RPM package files to contain the root directory, “./â€. Additional sanity-checking was added to the RPM 4.0 spec file parser; beginning with 4.0, RPM no longer allows dangling symbolic links that contain the BuildRoot. This change eliminates a class of common mistakes made when producing RPMs. Finally, RPM 4.0 implicitly generates Provides: directives; whenever a package header is read, the Provides: directive Provides: %{name} = %{epoch}:%{version}-%{release} is automatically generated, ensuring that all packages explicitly provide themselves as a capability and removing the need to provide self-capabilities within the package spec file.
+ </div><div class="para">
+ RPM 4.0.2 introduced the use of SHA-1 message digests to validate RPM header regions.
+ </div><div class="para">
+ RPM 4.0.3 added the %dev(type,major,minor) spec file directive, allowing creation of device nodes. In addition, the %configure spec file directive now supported --target and –host, simplifying cross compilation when using RPM. The %files directive was extended by adding the %exclude subdirective that could be used to exclude files from inclusion. Finally, RPM 4.0.3 switched back to creating package files in RPM version 3 package file format by default, although it still supports RPM version 4 package file format as well.
+ </div><div class="para">
+ RPM 4.0.4 provided PartialHardlinkSets support. RPM package files are sometimes created which contain multiple copies of the same file, stored as hard links to save space. Prior to RPM 4.0.4, RPM has always treated collections of hard links as an all-or-nothing proposition; all hard links were created, or else none were created. This behavior posed problems when some hard links in a set were tagged with attributes such as %doc or %lang, since rpm commands make it possible to install an RPM package file without installing any files with %doc attributes. Prior to RPM 4.0.4, doing so would break the hard link set, preventing creation of all hard links in the set. PartialHardlinkSet corrects this problem by allowing successful creation of subsets of the hard link set. RPM 4.0.4 also provided automatic generation of Perl module Requires: directives. find-requires now parses all packaged Perl scripts, generating any determined dependencies. In addition, RPM 4.0.4 provides transa
ction support for RPM.
+ </div><div class="para">
+ RPM 4.1 adds separate header DSA and RSA signatures, allowing verification of RPM package headers.
+ </div><div class="para">
+ Finally, when considering the RPM features required by your prepared package, remember that some required RPM features are specified manually within the package spec file, while others are automatically added by RPM during the RPM package file build process. For example, usage of versioned Requires: directives in a spec file will make the resulting RPM package file correctly installable only by RPM release 3.0.3 or later. Similarly, the preparation of any package using RPM release 4.0 or later will automatically produce RPM package files that can only be manipulated by releases of RPM that support the PayloadFilesHavePrefix feature. In the first case, you chose to produce packages that worked with RPM release 3.0.5 or later but not with RPM release 2.5 by including a new directive in the package spec file. In the second case, however, you did not explicitly produce packages that work only with recent RPM releases. The simple fact that you built your RPM package using RPM r
elease 4.0 means that you automatically used features that only RPM 4.0 and later releases understand. These automatic internal requirements are quite common in the later versions; as a result, the best practice is to decide the oldest version of RPM that you wish to support, then to build all packages using that version of RPM, keeping its feature set in mind as you prepare and build the packages.
+ </div></div><div xml:lang="ro" class="chapter" id="ch-package-structure" lang="ro"><div class="titlepage"><div><div><h2 class="title">Cap. 24. RPM Package File Structure</h2></div></div></div><div class="toc"><dl><dt><span class="sect1"><a href="#id680686">24.1. The Package File</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id829652">24.1.1. The file identifier</a></span></dt><dt><span class="sect2"><a href="#id530474">24.1.2. The signature</a></span></dt><dt><span class="sect2"><a href="#id946419">24.1.3. The header</a></span></dt><dt><span class="sect2"><a href="#id588134">24.1.4. The payload</a></span></dt></dl></dd></dl></div><div class="para">
+ This appendix covers:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ RPM package file structure
+ </div></li><li class="listitem"><div class="para">
+ RPM header entry formats
+ </div></li><li class="listitem"><div class="para">
+ Payload format
+ </div></li></ul></div><div class="para">
+ This appendix describes the format of RPM package files. You can combine this information with C, Perl, or Python data structures to access the information. In all cases, you should access elements in an RPM file using one of the available programming libraries. Do not attempt to access the files directly, as you may inadvertently damage the RPM file.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ <a class="xref" href="#ch-programming-c">Cap. 15, <em>Programming RPM with C</em></a>, <a class="xref" href="#ch-rpm-programming-python">Cap. 16, <em>Programming RPM with Python</em></a>, and <a class="xref" href="#ch-programming-perl">Cap. 17, <em>Programming RPM with Perl</em></a> cover programming with C, Python, and Perl, respectively.
+ </div><div class="para">
+ The RPM package format described here has been standardized as part of the Linux Standards Base, or LSB, version 1.3.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ The LSB 1.3 section on package file formats is available at www.linuxbase.org/spec/refspecs/LSB_1.3.0/gLSB/gLSB.html#PACKAGEFMT.
+ </div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id680686" class="title">The Package File</h1></div></div></div><div class="para">
+ RPM packages are delivered with one file per package. All RPM files have the following basic format of four sections:
+ </div><div class="para">
+ *A lead or file identifier
+ </div><div class="para">
+ *A signature
+ </div><div class="para">
+ *Header information
+ </div><div class="para">
+ *Archive of the payload, the files to install
+ </div><div class="para">
+ All values are encoded in network byte order, for portability to multiple processor architectures.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id829652" class="title">The file identifier</h1></div></div></div><div class="para">
+ Also called the lead or the rpmlead, the identifier marks that this file is an RPM file. It contains a magic number that the file command uses to detect RPM files. It also contains version and architecture information.
+ </div><div class="para">
+ The start of the identifier is the so-called magic number. The file command reads the first few bytes of a file and compares the values found with the contents of /usr/share/magic (/etc/magic on many UNIX systems), a database of magic numbers. This allows the file command to quickly identify files.
+ </div><div class="para">
+ The identifier includes the RPM version number, that is, the version of the RPM file format used for the package. The identifier also has a flag that tells the type of the RPM file, whether the file contains a binary or source package. An architecture flag allows RPM software to double-check that you are not trying to install a package for a non-compatible architecture.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id530474" class="title">The signature</h1></div></div></div><div class="para">
+ The signature appears after the lead or identifier section. The RPM signature helps verify the integrity of the package, and optionally the authenticity.
+ </div><div class="para">
+ The signature works by performing a mathematical function on the header and archive section of the file. The mathematical function can be an encryption process, such as PGP (Pretty Good Privacy), or a message digest in MD5 format.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id946419" class="title">The header</h1></div></div></div><div class="para">
+ The identifier section no longer contains enough information to describe modern RPMs. Furthermore, the identifier section is nowhere near as flexible as today’s packages require. To counter these deficiencies, the header section was introduced to include more information about the package.
+ </div><div class="para">
+ The header structure contains three parts:
+ </div><div class="para">
+ *Header record
+ </div><div class="para">
+ *One or more header index record structures
+ </div><div class="para">
+ *Data for the index record structures
+ </div><div class="para">
+ The header record identifies this as the RPM header. It also contains a count of the number of index records and the size of the index record data.
+ </div><div class="para">
+ Each index record uses a structure that contains a tag number for the data it contains. This includes tag IDs for the copyright message, name of the package, version number, and so on. A type number identifies the type of the item. An offset indicates where in the data section the data for this header item begins. A count indicates how many items of the given type are in this header entry. You can multiply the count by the size of the type to get the number of bytes used for the header entry.
+ </div><div class="para">
+ Table D-1 lists the type identifiers.
+ </div><div class="para">
+ Table D-1 Header type identifiers
+ </div><div class="informaltable"><table border="1"><colgroup><col width="33%" /><col width="33%" /><col width="33%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Constant
+ </div>
+
+ </td><td>
+ <div class="para">
+ Value
+ </div>
+
+ </td><td>
+ <div class="para">
+ Size in Bytes
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPM_NULL_TYPE
+ </div>
+
+ </td><td>
+ <div class="para">
+ 0
+ </div>
+
+ </td><td>
+ <div class="para">
+ No size
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPM_CHAR_TYPE
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPM_INT8_TYPE
+ </div>
+
+ </td><td>
+ <div class="para">
+ 2
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPM_INT16_TYPE
+ </div>
+
+ </td><td>
+ <div class="para">
+ 3
+ </div>
+
+ </td><td>
+ <div class="para">
+ 2
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPM_INT32_TYPE
+ </div>
+
+ </td><td>
+ <div class="para">
+ 4
+ </div>
+
+ </td><td>
+ <div class="para">
+ 4
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPM_INT64_TYPE
+ </div>
+
+ </td><td>
+ <div class="para">
+ 5
+ </div>
+
+ </td><td>
+ <div class="para">
+ Not supported yet
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPM_STRING_TYPE
+ </div>
+
+ </td><td>
+ <div class="para">
+ 6
+ </div>
+
+ </td><td>
+ <div class="para">
+ Variable number of bytes, terminated by a NULL
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPM_BIN_TYPE
+ </div>
+
+ </td><td>
+ <div class="para">
+ 7
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPM_STRING_ARRAY_TYPE
+ </div>
+
+ </td><td>
+ <div class="para">
+ 8
+ </div>
+
+ </td><td>
+ <div class="para">
+ Variable, vector of NULL-terminated strings
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPM_I18NSTRING_TYPE
+ </div>
+
+ </td><td>
+ <div class="para">
+ 9
+ </div>
+
+ </td><td>
+ <div class="para">
+ Variable, vector of NULL-terminated strings
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ Note
+ </div><div class="para">
+ Integer values are aligned on 2-byte (16-bit integers) or 4-byte (32-bit integers) boundaries.
+ </div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id624435" class="title">Header Tags</h1></div></div></div><div class="para">
+ Table D-2 lists the tag identifiers.
+ </div><div class="para">
+ Table D-2 Header entry tag identifiers
+ </div><div class="informaltable"><table border="1"><colgroup><col width="25%" /><col width="25%" /><col width="25%" /><col width="25%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Constant
+ </div>
+
+ </td><td>
+ <div class="para">
+ Value
+ </div>
+
+ </td><td>
+ <div class="para">
+ Type
+ </div>
+
+ </td><td>
+ <div class="para">
+ Required?
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_NAME
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1000
+ </div>
+
+ </td><td>
+ <div class="para">
+ STRING
+ </div>
+
+ </td><td>
+ <div class="para">
+ Yes
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_VERSION
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1001
+ </div>
+
+ </td><td>
+ <div class="para">
+ STRING
+ </div>
+
+ </td><td>
+ <div class="para">
+ Yes
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_RELEASE
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1002
+ </div>
+
+ </td><td>
+ <div class="para">
+ STRING
+ </div>
+
+ </td><td>
+ <div class="para">
+ Yes
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_SUMMARY
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1004
+ </div>
+
+ </td><td>
+ <div class="para">
+ I18NSTRING
+ </div>
+
+ </td><td>
+ <div class="para">
+ Yes
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_DESCRIPTION
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1005
+ </div>
+
+ </td><td>
+ <div class="para">
+ I18NSTRING
+ </div>
+
+ </td><td>
+ <div class="para">
+ Yes
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_BUILDTIME
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1006
+ </div>
+
+ </td><td>
+ <div class="para">
+ INT32
+ </div>
+
+ </td><td>
+ <div class="para">
+ Optional
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_BUILDHOST
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1007
+ </div>
+
+ </td><td>
+ <div class="para">
+ STRING
+ </div>
+
+ </td><td>
+ <div class="para">
+ Optional
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_SIZE
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1009
+ </div>
+
+ </td><td>
+ <div class="para">
+ INT32
+ </div>
+
+ </td><td>
+ <div class="para">
+ Yes
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_LICENSE
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1014
+ </div>
+
+ </td><td>
+ <div class="para">
+ STRING
+ </div>
+
+ </td><td>
+ <div class="para">
+ Yes
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_GROUP
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1016
+ </div>
+
+ </td><td>
+ <div class="para">
+ I18NSTRING
+ </div>
+
+ </td><td>
+ <div class="para">
+ Yes
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_OS
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1021
+ </div>
+
+ </td><td>
+ <div class="para">
+ STRING
+ </div>
+
+ </td><td>
+ <div class="para">
+ Yes
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_ARCH
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1022
+ </div>
+
+ </td><td>
+ <div class="para">
+ STRING
+ </div>
+
+ </td><td>
+ <div class="para">
+ Yes
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_SOURCERPM
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1044
+ </div>
+
+ </td><td>
+ <div class="para">
+ STRING
+ </div>
+
+ </td><td>
+ <div class="para">
+ Optional
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_FILEVERIFYFLAGS
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1045
+ </div>
+
+ </td><td>
+ <div class="para">
+ INT32
+ </div>
+
+ </td><td>
+ <div class="para">
+ Optional
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_ARCHIVESIZE
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1046
+ </div>
+
+ </td><td>
+ <div class="para">
+ INT32
+ </div>
+
+ </td><td>
+ <div class="para">
+ Optional
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_RPMVERSION
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1064
+ </div>
+
+ </td><td>
+ <div class="para">
+ STRING
+ </div>
+
+ </td><td>
+ <div class="para">
+ Optional
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_CHANGELOGTIME
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1080
+ </div>
+
+ </td><td>
+ <div class="para">
+ INT32
+ </div>
+
+ </td><td>
+ <div class="para">
+ Optional
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_CHANGELOGNAME
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1081
+ </div>
+
+ </td><td>
+ <div class="para">
+ STRING_ARRAY
+ </div>
+
+ </td><td>
+ <div class="para">
+ Optional
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_CHANGELOGTEXT
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1082
+ </div>
+
+ </td><td>
+ <div class="para">
+ STRING_ARRAY
+ </div>
+
+ </td><td>
+ <div class="para">
+ Optional
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_COOKIE
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1094
+ </div>
+
+ </td><td>
+ <div class="para">
+ STRING
+ </div>
+
+ </td><td>
+ <div class="para">
+ Optional
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_OPTFLAGS
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1122
+ </div>
+
+ </td><td>
+ <div class="para">
+ STRING
+ </div>
+
+ </td><td>
+ <div class="para">
+ Optional
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_PAYLOADFORMAT
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1124
+ </div>
+
+ </td><td>
+ <div class="para">
+ STRING
+ </div>
+
+ </td><td>
+ <div class="para">
+ Yes
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_PAYLOADCOMPRESSOR
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1125
+ </div>
+
+ </td><td>
+ <div class="para">
+ STRING
+ </div>
+
+ </td><td>
+ <div class="para">
+ Yes
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_PAYLOADFLAGS
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1126
+ </div>
+
+ </td><td>
+ <div class="para">
+ STRING
+ </div>
+
+ </td><td>
+ <div class="para">
+ Yes
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_RHNPLATFORM
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1131
+ </div>
+
+ </td><td>
+ <div class="para">
+ STRING
+ </div>
+
+ </td><td>
+ <div class="para">
+ Deprecated
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_PLATFORM
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1132
+ </div>
+
+ </td><td>
+ <div class="para">
+ STRING
+ </div>
+
+ </td><td>
+ <div class="para">
+ Optional
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ Most of these tags are self-explanatory; however, a few tags hold special meaning. The RPMTAG_SIZE tag holds the size of all the regular files in the payload. The RPMTAG_ARCHIVESIZE tag holds the uncompressed size of the payload section, including the necessary cpio headers. The RPMTAG_COOKIE tag holds an opaque string.
+ </div><div class="para">
+ According to the LSB standards, the RPMTAG_PAYLOADFORMAT must always be cpio. The RPMTAG_PAYLOADCOMPRESSOR must be gzip. The RPMTAG_PAYLOADFLAGS must always be 9.
+ </div><div class="para">
+ The RPMTAG_OPTFLAGS tag holds special compiler flags used to build the package. The RPMTAG_PLATFORM and RPMTAG_RHNPLATFORM tags hold opaque strings.
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id1374275" class="title">Private Header Tags</h1></div></div></div><div class="para">
+ Table D-3 lists header tags that are considered private.
+ </div><div class="para">
+ Table D-3 Private header tags
+ </div><div class="informaltable"><table border="1"><colgroup><col width="25%" /><col width="25%" /><col width="25%" /><col width="25%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Constant
+ </div>
+
+ </td><td>
+ <div class="para">
+ Value
+ </div>
+
+ </td><td>
+ <div class="para">
+ Type
+ </div>
+
+ </td><td>
+ <div class="para">
+ Required?
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_HEADERSIGNATURES
+ </div>
+
+ </td><td>
+ <div class="para">
+ 62
+ </div>
+
+ </td><td>
+ <div class="para">
+ BIN
+ </div>
+
+ </td><td>
+ <div class="para">
+ Optional
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_HEADERIMMUTABLE
+ </div>
+
+ </td><td>
+ <div class="para">
+ 63
+ </div>
+
+ </td><td>
+ <div class="para">
+ BIN
+ </div>
+
+ </td><td>
+ <div class="para">
+ Optional
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_HEADERI18NTABLE
+ </div>
+
+ </td><td>
+ <div class="para">
+ 100
+ </div>
+
+ </td><td>
+ <div class="para">
+ STRING_ARRAY
+ </div>
+
+ </td><td>
+ <div class="para">
+ Yes
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ The RPMTAG_HEADERSIGNATURES tag indicates that this is a signature entry. The RPMTAG_HEADERIMMUTABLE tag indicates a header item that is used in the calculation of signatures. This data should be preserved.
+ </div><div class="para">
+ The RPMTAG_HEADERI18NTABLE tag holds a table of locales used for international text lookup.
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id868672" class="title">Signature Tags</h1></div></div></div><div class="para">
+ The signature section is implemented as a header structure, but it is not considered part of the RPM header. Table D-4 lists special signature-related tags.
+ </div><div class="para">
+ Table D-4 Signature-related tags
+ </div><div class="informaltable"><table border="1"><colgroup><col width="25%" /><col width="25%" /><col width="25%" /><col width="25%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Constant
+ </div>
+
+ </td><td>
+ <div class="para">
+ Value
+ </div>
+
+ </td><td>
+ <div class="para">
+ Type
+ </div>
+
+ </td><td>
+ <div class="para">
+ Required?
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ SIGTAG_SIGSIZE
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1000
+ </div>
+
+ </td><td>
+ <div class="para">
+ INT32
+ </div>
+
+ </td><td>
+ <div class="para">
+ Yes
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ SIGTAG_PGP
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1002
+ </div>
+
+ </td><td>
+ <div class="para">
+ BIN
+ </div>
+
+ </td><td>
+ <div class="para">
+ Optional
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ SIGTAG_MD5
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1004
+ </div>
+
+ </td><td>
+ <div class="para">
+ BIN
+ </div>
+
+ </td><td>
+ <div class="para">
+ Yes
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ SIGTAG_GPG
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1005
+ </div>
+
+ </td><td>
+ <div class="para">
+ BIN
+ </div>
+
+ </td><td>
+ <div class="para">
+ Optional
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ SIGTAG_PAYLOADSIZE
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1007
+ </div>
+
+ </td><td>
+ <div class="para">
+ INT32
+ </div>
+
+ </td><td>
+ <div class="para">
+ Optional
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ SIGTAG_SHA1HEADER
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1010
+ </div>
+
+ </td><td>
+ <div class="para">
+ STRING
+ </div>
+
+ </td><td>
+ <div class="para">
+ Optional
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ SIGTAG_DSAHEADER
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1011
+ </div>
+
+ </td><td>
+ <div class="para">
+ BIN
+ </div>
+
+ </td><td>
+ <div class="para">
+ Optional
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ SIGTAG_RSAHEADER
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1012
+ </div>
+
+ </td><td>
+ <div class="para">
+ BIN
+ </div>
+
+ </td><td>
+ <div class="para">
+ Optional
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ The SIGTAG_SIGSIZE tag specifies the size of the header and payload sections, while the SIGTAG_PAYLOADSIZE holds the uncompressed size of the payload.
+ </div><div class="para">
+ To verify the integrity of the package, the SIGTAG_MD5 tag holds a 128-bit MD5 checksum of the header and payload sections. The SIGTAG_SHA1HEADER holds an SHA1 checksum of the entire header section.
+ </div><div class="para">
+ To verify the authenticity of the package, the SIGTAG_PGP tag holds a Version 3 OpenPGP Signature Packet RSA signature of the header and payload areas. The SIGTAG_GPG tag holds a Version 3 OpenPGP Signature Packet DSA signature of the header and payload areas. The SIGTAG_DSAHEADER holds a DSA signature of just the header section. If the SIGTAG_DSAHEADER tag is included, the SIGTAG_GPG tag must also be present. The SIGTAG_ RSAHEADER holds an RSA signature of just the header section. If the SIGTAG_ RSAHEADER tag is included, the SIGTAG_PGP tag must also be present.
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id592036" class="title">Installation Tags</h1></div></div></div><div class="para">
+ A set of installation-specific tags tells the rpm program how to run the pre- and post-installation scripts. Table D-5 lists these tags.
+ </div><div class="para">
+ Table D-5 Installation tags
+ </div><div class="informaltable"><table border="1"><colgroup><col width="25%" /><col width="25%" /><col width="25%" /><col width="25%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Constant
+ </div>
+
+ </td><td>
+ <div class="para">
+ Value
+ </div>
+
+ </td><td>
+ <div class="para">
+ Type
+ </div>
+
+ </td><td>
+ <div class="para">
+ Required?
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_PREINPROG
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1085
+ </div>
+
+ </td><td>
+ <div class="para">
+ STRING
+ </div>
+
+ </td><td>
+ <div class="para">
+ Optional
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_POSTINPROG
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1086
+ </div>
+
+ </td><td>
+ <div class="para">
+ STRING
+ </div>
+
+ </td><td>
+ <div class="para">
+ Optional
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_PREUNPROG
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1087
+ </div>
+
+ </td><td>
+ <div class="para">
+ STRING
+ </div>
+
+ </td><td>
+ <div class="para">
+ Optional
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_POSTUNPROG
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1088
+ </div>
+
+ </td><td>
+ <div class="para">
+ STRING
+ </div>
+
+ </td><td>
+ <div class="para">
+ Optional
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ The RPMTAG_PREINPROG tag holds the name of the interpreter, such as sh, to run the pre-install script. Similarly, the RPMTAG_POSTINPROG tag holds the name of the interpreter to run the post-install script. RPMTAG_PREUNPROG and RPMTAG_POSTUNPROG are the same for the uninstall scripts.
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id879598" class="title">File Information Tags</h1></div></div></div><div class="para">
+ File information tags are placed in the header for convenient access. These tags describe the files in the payload. Table D-6 lists these tags.
+ </div><div class="para">
+ Table D-6 File information tags
+ </div><div class="informaltable"><table border="1"><colgroup><col width="25%" /><col width="25%" /><col width="25%" /><col width="25%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Constant
+ </div>
+
+ </td><td>
+ <div class="para">
+ Value
+ </div>
+
+ </td><td>
+ <div class="para">
+ Type
+ </div>
+
+ </td><td>
+ <div class="para">
+ Required?
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_OLDFILENAMES
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1027
+ </div>
+
+ </td><td>
+ <div class="para">
+ STRING_ARRAY
+ </div>
+
+ </td><td>
+ <div class="para">
+ Optional
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_FILESIZES
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1028
+ </div>
+
+ </td><td>
+ <div class="para">
+ INT32
+ </div>
+
+ </td><td>
+ <div class="para">
+ Yes
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_FILEMODES
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1030
+ </div>
+
+ </td><td>
+ <div class="para">
+ INT16
+ </div>
+
+ </td><td>
+ <div class="para">
+ Yes
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_FILERDEVS
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1033
+ </div>
+
+ </td><td>
+ <div class="para">
+ INT16
+ </div>
+
+ </td><td>
+ <div class="para">
+ Yes
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_FILEMTIMES
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1034
+ </div>
+
+ </td><td>
+ <div class="para">
+ INT32
+ </div>
+
+ </td><td>
+ <div class="para">
+ Yes
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_FILEMD5S
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1035
+ </div>
+
+ </td><td>
+ <div class="para">
+ STRING_ARRAY
+ </div>
+
+ </td><td>
+ <div class="para">
+ Yes
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_FILELINKTOS
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1036
+ </div>
+
+ </td><td>
+ <div class="para">
+ STRING_ARRAY
+ </div>
+
+ </td><td>
+ <div class="para">
+ Yes
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_FILEFLAGS
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1037
+ </div>
+
+ </td><td>
+ <div class="para">
+ INT32
+ </div>
+
+ </td><td>
+ <div class="para">
+ Yes
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_FILEUSERNAME
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1039
+ </div>
+
+ </td><td>
+ <div class="para">
+ STRING_ARRAY
+ </div>
+
+ </td><td>
+ <div class="para">
+ Yes
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_FILEGROUPNAME
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1040
+ </div>
+
+ </td><td>
+ <div class="para">
+ STRING_ARRAY
+ </div>
+
+ </td><td>
+ <div class="para">
+ Yes
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_FILEDEVICES
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1095
+ </div>
+
+ </td><td>
+ <div class="para">
+ INT32
+ </div>
+
+ </td><td>
+ <div class="para">
+ Yes
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_FILEINODES
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1096
+ </div>
+
+ </td><td>
+ <div class="para">
+ INT32
+ </div>
+
+ </td><td>
+ <div class="para">
+ Yes
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_FILELANGS
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1097
+ </div>
+
+ </td><td>
+ <div class="para">
+ STRING_ARRAY
+ </div>
+
+ </td><td>
+ <div class="para">
+ Yes
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_DIRINDEXES
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1116
+ </div>
+
+ </td><td>
+ <div class="para">
+ INT32
+ </div>
+
+ </td><td>
+ <div class="para">
+ Optional
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_BASENAMES
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1117
+ </div>
+
+ </td><td>
+ <div class="para">
+ STRING_ARRAY
+ </div>
+
+ </td><td>
+ <div class="para">
+ Optional
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_DIRNAMES
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1118
+ </div>
+
+ </td><td>
+ <div class="para">
+ STRING_ARRAY
+ </div>
+
+ </td><td>
+ <div class="para">
+ Optional
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ The RPMTAG_OLDFILENAMES tag is used when the files are not compressed, when the RPMTAG_REQUIRENAME tag does not indicate rpmlib(CompressedFileNames). The RPMTAG_FILESIZES tag specifies the size of each file in the payload, while the RPMTAG_FILEMODES tag specifies the file modes (permissions) and the RPMTAG_FILEMTIMES tag holds the last modification time for each file.
+ </div><div class="para">
+ The RPMTAG_BASENAMES tag holds an array of the base file names for the files in the payload. The RPMTAG_DIRNAMES tag holds an array of the directories for the files. The RPMTAG_DIRINDEXES tag contains an index into the RPMTAG_DIRNAMES for the directory. Each RPM must have either RPMTAG_OLDFILENAMES or the triple of RPMTAG_BASENAMES, RPMTAG_DIRNAMES, and RPMTAG_DIRINDEXES, but not both.
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id759754" class="title">Dependency Tags</h1></div></div></div><div class="para">
+ The dependency tags provide one of the most useful features of the RPM system by allowing for automated dependency checks between packages. Table D-7 lists these tags.
+ </div><div class="para">
+ Table D-7 Dependency tags
+ </div><div class="informaltable"><table border="1"><colgroup><col width="25%" /><col width="25%" /><col width="25%" /><col width="25%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Constant
+ </div>
+
+ </td><td>
+ <div class="para">
+ Value
+ </div>
+
+ </td><td>
+ <div class="para">
+ Type
+ </div>
+
+ </td><td>
+ <div class="para">
+ Required?
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_PROVIDENAME
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1047
+ </div>
+
+ </td><td>
+ <div class="para">
+ STRING_ARRAY
+ </div>
+
+ </td><td>
+ <div class="para">
+ Yes
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_REQUIREFLAGS
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1048
+ </div>
+
+ </td><td>
+ <div class="para">
+ INT32
+ </div>
+
+ </td><td>
+ <div class="para">
+ Yes
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_REQUIRENAME
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1049
+ </div>
+
+ </td><td>
+ <div class="para">
+ STRING_ARRAY
+ </div>
+
+ </td><td>
+ <div class="para">
+ Yes
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_REQUIREVERSION
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1050
+ </div>
+
+ </td><td>
+ <div class="para">
+ STRING_ARRAY
+ </div>
+
+ </td><td>
+ <div class="para">
+ Yes
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_CONFLICTFLAGS
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1053
+ </div>
+
+ </td><td>
+ <div class="para">
+ INT32
+ </div>
+
+ </td><td>
+ <div class="para">
+ Optional
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_CONFLICTNAME
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1054
+ </div>
+
+ </td><td>
+ <div class="para">
+ STRING_ARRAY
+ </div>
+
+ </td><td>
+ <div class="para">
+ Optional
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_CONFLICTVERSION
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1055
+ </div>
+
+ </td><td>
+ <div class="para">
+ STRING_ARRAY
+ </div>
+
+ </td><td>
+ <div class="para">
+ Optional
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_OBSOLETENAME
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1090
+ </div>
+
+ </td><td>
+ <div class="para">
+ STRING_ARRAY
+ </div>
+
+ </td><td>
+ <div class="para">
+ Optional
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_PROVIDEFLAGS
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1112
+ </div>
+
+ </td><td>
+ <div class="para">
+ INT32
+ </div>
+
+ </td><td>
+ <div class="para">
+ Yes
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_PROVIDEVERSION
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1113
+ </div>
+
+ </td><td>
+ <div class="para">
+ STRING_ARRAY
+ </div>
+
+ </td><td>
+ <div class="para">
+ Yes
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_OBSOLETEFLAGS
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1114
+ </div>
+
+ </td><td>
+ <div class="para">
+ INT32
+ </div>
+
+ </td><td>
+ <div class="para">
+ Optional
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_OBSOLETEVERSION
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1115
+ </div>
+
+ </td><td>
+ <div class="para">
+ INT32
+ </div>
+
+ </td><td>
+ <div class="para">
+ Optional
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ Each of these tags comes in triples, which are formatted similarly. The RPMTAG_REQUIRENAME tag holds an array of required capabilities. The RPMTAG_REQUIREVERSION tag holds an array of the versions of the required capabilities. The RPMTAG_REQUIREFLAGS tag ties the two together with a set of bit flags that specify whether the requirement is for a version less than the given number, equal to the given number, greater than or equal to the given number, and so on. Table D-8 lists these flags.
+ </div><div class="para">
+ Table D-8 Bit flags for dependencies
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Flag
+ </div>
+
+ </td><td>
+ <div class="para">
+ Value
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMSENSE_LESS
+ </div>
+
+ </td><td>
+ <div class="para">
+ 0x02
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMSENSE_GREATER
+ </div>
+
+ </td><td>
+ <div class="para">
+ 0x04
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMSENSE_EQUAL
+ </div>
+
+ </td><td>
+ <div class="para">
+ 0x08
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMSENSE_PREREQ
+ </div>
+
+ </td><td>
+ <div class="para">
+ 0x40
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMSENSE_INTERP
+ </div>
+
+ </td><td>
+ <div class="para">
+ 0x100
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMSENSE_SCRIPT_PRE
+ </div>
+
+ </td><td>
+ <div class="para">
+ 0x200
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMSENSE_SCRIPT_POST
+ </div>
+
+ </td><td>
+ <div class="para">
+ 0x400
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMSENSE_SCRIPT_PREUN
+ </div>
+
+ </td><td>
+ <div class="para">
+ 0x800
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMSENSE_SCRIPT_POSTUN
+ </div>
+
+ </td><td>
+ <div class="para">
+ 0x1000
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ The RPMTAG_PROVIDENAME, RPMTAG_PROVIDEVERSION, and RPMTAG_PROVIDEFLAGS tags work similarly for the capabilities this package provides. The RPMTAG_CONFLICTNAME, RPMTAG_CONFLICTVERSION, and RPMTAG_CONFLICTFLAGS tags specify the conflicts. The RPMTAG_OBSOLETENAME, RPMTAG_OBSOLETEVERSION, and RPMTAG_OBSOLETEFLAGS tags specify the obsoleted dependencies.
+ </div><div class="para">
+ In addition, an RPM package can define some special requirements in the RPMTAG_REQUIRENAME and RPMTAG_REQUIREVERSION tags. Table D-9 lists these requirements.
+ </div><div class="para">
+ Table D-9 Special package requirement names and versions
+ </div><div class="informaltable"><table border="1"><colgroup><col width="33%" /><col width="33%" /><col width="33%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Name
+ </div>
+
+ </td><td>
+ <div class="para">
+ Version
+ </div>
+
+ </td><td>
+ <div class="para">
+ Specifies
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Lsb
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1.3
+ </div>
+
+ </td><td>
+ <div class="para">
+ The package conforms to the Linux Standards Base RPM format.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpmlib(VersionedDependencies)
+ </div>
+
+ </td><td>
+ <div class="para">
+ 3.0.3-1
+ </div>
+
+ </td><td>
+ <div class="para">
+ The package holds dependencies or prerequisites that have versions associated with them.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpmlib(PayloadFilesHavePrefix)
+ </div>
+
+ </td><td>
+ <div class="para">
+ 4.0-1
+ </div>
+
+ </td><td>
+ <div class="para">
+ File names in the archive have a “.†prepended on the names.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpmlib(CompressedFileNames)
+ </div>
+
+ </td><td>
+ <div class="para">
+ 3.0.4-1
+ </div>
+
+ </td><td>
+ <div class="para">
+ The package uses the RPMTAG_DIRINDEXES, RPMTAG_DIRNAME and RPMTAG_BASENAMES tags for specifying file names.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ /bin/sh
+ </div>
+
+ </td><td>
+ <div class="para">
+ NA
+ </div>
+
+ </td><td>
+ <div class="para">
+ Indicates a requirement for the Bourne shell to run the installation scripts.
+ </div>
+
+ </td></tr></tbody></table></div></div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id588134" class="title">The payload</h1></div></div></div><div class="para">
+ The payload, or archive, section contains the actual files used in the package. These are the files that the rpm command installs when you install the package. To save space, data in the archive section is compressed in GNU gzip format.
+ </div><div class="para">
+ Once uncompressed, the data is in cpio format, which is how the rpm2cpio command can do its work. In cpio format, the payload is made up of records, one per file. Table D-10 lists the record structure.
+ </div><div class="para">
+ Table D-10 cpio file record structure
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Element
+ </div>
+
+ </td><td>
+ <div class="para">
+ Holds
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ cpio header
+ </div>
+
+ </td><td>
+ <div class="para">
+ Information on the file, such as the file mode (permissions)
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ File name
+ </div>
+
+ </td><td>
+ <div class="para">
+ NULL-terminated string
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Padding
+ </div>
+
+ </td><td>
+ <div class="para">
+ 0 to 3 bytes, as needed, to align the next element on a 4-byte boundary
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ File data
+ </div>
+
+ </td><td>
+ <div class="para">
+ The contents of the file
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Padding
+ </div>
+
+ </td><td>
+ <div class="para">
+ 0 to 3 bytes, as needed, to align the next file record on a 4-byte boundary
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ The information in the cpio header duplicates that of the RPM file-information header elements.
+ </div></div></div></div><div xml:lang="ro" class="chapter" id="ch-online-resources" lang="ro"><div class="titlepage"><div><div><h2 class="title">Cap. 25. RPM Resources</h2></div></div></div><div class="toc"><dl><dt><span class="sect1"><a href="#id847900">25.1. Finding RPM Sites</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id529167">25.1.1. The main rpm.org site</a></span></dt><dt><span class="sect2"><a href="#id745432">25.1.2. RPM locator sites</a></span></dt><dt><span class="sect2"><a href="#id626826">25.1.3. RPM tools sites</a></span></dt><dt><span class="sect2"><a href="#id823415">25.1.4. Programming sites</a></span></dt><dt><span class="sect2"><a href="#id574081">25.1.5. Sites related to RPM</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id652975">25.2. Accessing RPM Mailing Lists and Newsgroups</a></span></dt></dl></div><div class="para">
+ This appendix covers:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Finding RPM sites on the Internet
+ </div></li><li class="listitem"><div class="para">
+ Accessing RPM newsgroups and mailing lists
+ </div></li></ul></div><div class="para">
+ This appendix covers the material available on the Internet for working with RPM.
+ </div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id847900" class="title">Finding RPM Sites</h1></div></div></div><div class="para">
+ There is a wealth of RPM material online, although some of it is hard to find. The following sections list a number of RPM-related sites, divided by category. Note that as with any Internet sites, the sites listed my change or disappear.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id529167" class="title">The main rpm.org site</h1></div></div></div><div class="para">
+ The main RPM site is www.rpm.org. This site provides the official distributions of the RPM software, as well as a lot of documentation online.
+ </div><div class="para">
+ Table F-1 lists a number of useful links on this site.
+ </div><div class="para">
+ Table F-1 Links on the rpm.org site
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Link
+ </div>
+
+ </td><td>
+ <div class="para">
+ Holds
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ ftp://ftp.rpm.org/pub/rpm/dist/
+ </div>
+
+ </td><td>
+ <div class="para">
+ RPM software downloads
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ ftp://ftp.rpm.org/pub/
+ </div>
+
+ </td><td>
+ <div class="para">
+ rpm.org download site
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ www.rpm.org/cvs_help/
+ </div>
+
+ </td><td>
+ <div class="para">
+ Instructions for accessing the RPM CVS repository
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ www.rpm.org/hintskinks/
+ </div>
+
+ </td><td>
+ <div class="para">
+ Tips for working with RPM
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ www.rpm.org/hintskinks/bootstrap/
+ </div>
+
+ </td><td>
+ <div class="para">
+ Good tips on bootstrapping RPM to new platforms
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ www.rpm.org/howto/
+ </div>
+
+ </td><td>
+ <div class="para">
+ How-to documents for working with RPM
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ www.rpm.org/max-rpm/
+ </div>
+
+ </td><td>
+ <div class="para">
+ Maximum RPM by Edward C. Bailey
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ www.rpm.org/RPM-HOWTO/
+ </div>
+
+ </td><td>
+ <div class="para">
+ Good introductory tutorial
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ www.rpm.org/rpmapi-4.1/
+ </div>
+
+ </td><td>
+ <div class="para">
+ API documentation
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ The main RPM FTP site, at ftp://ftp.rpm.org/pub/, includes the RPM distributions, as well as the Berkeley DB version 3 library, and the text of the book Maximum RPM. Download RPM software from ftp://ftp.rpm.org/pub/rpm/dist/.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id745432" class="title">RPM locator sites</h1></div></div></div><div class="para">
+ A number of sites help you find RPMs for various applications. On the main sites, you can find specially built RPMs for a variety of Linux distributions. You can then download the RPMs made especially for your systems.
+ </div><div class="para">
+ The main RPM-finding site is rpmfind.net, which offers a search engine as well as software you can run on your site.
+ </div><div class="para">
+ The RPM PBone Search, at http://rpm.pbone.net/, is also very useful.
+ </div><div class="para">
+ The www.rpm.org/packagers/ site lists a number of places that package RPMs and provide them for downloading.
+ </div><div class="para">
+ Many Java libraries and packages are available in RPM format from www.jpackage.org/.
+ </div><div class="para">
+ Table F-2 lists a number of other RPM download sites.
+ </div><div class="para">
+ Table F-2 RPM download sites
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Site
+ </div>
+
+ </td><td>
+ <div class="para">
+ Holds
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpmfind.net
+ </div>
+
+ </td><td>
+ <div class="para">
+ Links to a huge number of RPMs, many specific to various Linux distributions
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ http://rpm.pbone.net/
+ </div>
+
+ </td><td>
+ <div class="para">
+ RPM PBone search, useful for finding RPMs
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ www.rpm.org/packagers/
+ </div>
+
+ </td><td>
+ <div class="para">
+ Lists a number of sites that provide RPMs for download
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ www.javapackage.org
+ </div>
+
+ </td><td>
+ <div class="para">
+ Many Java packages in RPM format
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ http://plf.zarb.org/
+ </div>
+
+ </td><td>
+ <div class="para">
+ The Penguin Liberation Front has RPMs that for legal reasons cannot be included in the Mandrake Linux distribution.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ www.math.unl.edu/~rdieter/Projects
+ </div>
+
+ </td><td>
+ <div class="para">
+ Rex Dieter’s RPM site
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ www.rpmhelp.net
+ </div>
+
+ </td><td>
+ <div class="para">
+ Mandrake Linux RPMs
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ www.aucs.org/rpmcenter/
+ </div>
+
+ </td><td>
+ <div class="para">
+ Edwin Chan's Red Hat RPMs
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ www.owlriver.com/projects/links/
+ </div>
+
+ </td><td>
+ <div class="para">
+ Owl River Company RPMs
+ </div>
+
+ </td></tr></tbody></table></div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id626826" class="title">RPM tools sites</h1></div></div></div><div class="para">
+ A large number of tools exist to help you work with RPMs. The following sites list some of the main tools:
+ </div><div class="para">
+ *For the vim text editor, you can download a spec.vim syntax file from http://pegasus.rutgers.edu/~elflord/vim/syntax/spec.vim.
+ </div><div class="para">
+ *For emacs, you can download an Emacs mode for spec files from http://tihlde.org/~stigb/rpm-spec-mode.el.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ <a class="xref" href="#ch-development-tools">Cap. 26, <em>Linux Text Editors and Development Tools</em></a> lists links for a number of text editors.
+ </div><div class="para">
+ *The rpmlint tool mentioned in <a class="xref" href="#ch-extra-packaging-tools">Cap. 12, <em>Supplemental Packaging Software</em></a> is available at http://people.mandrakesoft.com/~flepied/projects/rpmlint/.
+ </div><div class="para">
+ Table F-3 lists a number of RPM-related tools and the sites you can find more information on the tools.
+ </div><div class="para">
+ Table F-3 RPM-related tools
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Tool
+ </div>
+
+ </td><td>
+ <div class="para">
+ Site
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ apt-rpm
+ </div>
+
+ </td><td>
+ <div class="para">
+ ftp://ftp.conectiva.com/pub/conectiva/EXPERIMENTAL/apt/
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ apt4rpm
+ </div>
+
+ </td><td>
+ <div class="para">
+ http://apt4rpm.sourceforge.net/
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ AutoRPM
+ </div>
+
+ </td><td>
+ <div class="para">
+ www.autorpm.org
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ AutoUpdate
+ </div>
+
+ </td><td>
+ <div class="para">
+ www.mat.univie.ac.at/~gerald/ftp/autoupdate
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ current
+ </div>
+
+ </td><td>
+ <div class="para">
+ www.biology.duke.edu/computer/unix/current/
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ kpackage
+ </div>
+
+ </td><td>
+ <div class="para">
+ www.kde.org
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ MakeRPM.pl
+ </div>
+
+ </td><td>
+ <div class="para">
+ www.perl.com/CPAN/modules/by-authors/id/JWIED
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ poldek
+ </div>
+
+ </td><td>
+ <div class="para">
+ http://poldek.pld.org.pl/
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpm2html
+ </div>
+
+ </td><td>
+ <div class="para">
+ rpmfind.net/linux/rpm2html/
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpmfind
+ </div>
+
+ </td><td>
+ <div class="para">
+ rpmfind.net
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RUST
+ </div>
+
+ </td><td>
+ <div class="para">
+ www.rusthq.com
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ setup.sh
+ </div>
+
+ </td><td>
+ <div class="para">
+ www.mmedia.is/~bre/programs/setup.sh
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ urpmi
+ </div>
+
+ </td><td>
+ <div class="para">
+ www.linux-mandrake.com/cooker/urpmi.html
+ </div>
+
+ </td></tr></tbody></table></div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id823415" class="title">Programming sites</h1></div></div></div><div class="para">
+ Only a few sites exist to help developers with programming for RPM. I maintain some quick links to RPM sites at www.pconline.com/~erc/rpm.htm. Most of these links are focused for programming with RPM.
+ </div><div class="para">
+ The best sites for programming RPM are the online API documentation at www.rpm.org/rpmapi-4.1/ for the RPM 4.1 release, and the ftp.rpm.org/pub/rpm/dist/ site for downloading the RPM sources. There is a lot of documentation bundled with the source code.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ <a class="xref" href="#ch-development-tools">Cap. 26, <em>Linux Text Editors and Development Tools</em></a> lists links for a number of Integrated Development Environments, or IDEs, aimed at programmers.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id574081" class="title">Sites related to RPM</h1></div></div></div><div class="para">
+ If you try to make cross-platform RPMs, especially RPMs that should work for multiple versions of Linux, it is very important to follow the Linux standards for things like file placement and package formats.
+ </div><div class="para">
+ The Filesystem Hierarchy Standard, or FHS, covers Linux directory layout at www.pathname.com/fhs/.
+ </div><div class="para">
+ The Linux Standards Base is working on standardizing on the RPM package file format. See www.linuxbase.org for details.
+ </div></div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id652975" class="title">Accessing RPM Mailing Lists and Newsgroups</h1></div></div></div><div class="para">
+ The RPM mailing list provides the best source of technical RPM information. You can post questions and get quick, useful responses. If you are working with RPM, you should subscribe to this mailing list. For details on viewing the RPM mailing list archives and signing up for the list, see www.rpm.org/mailing_list/.
+ </div><div class="para">
+ To help avoid unwanted commercial e-mail (in other words, spam), you need to register with a user name and password to subscribe to the mailing list or view the archives.
+ </div><div class="para">
+ A Usenet newsgroup, named linux.redhat.rpm, also provides a forum for asking RPM-related questions. You can read this newsgroup with any newsreading program.
+ </div></div></div><div xml:lang="ro" class="chapter" id="ch-development-tools" lang="ro"><div class="titlepage"><div><div><h2 class="title">Cap. 26. Linux Text Editors and Development Tools</h2></div></div></div><div class="toc"><dl><dt><span class="sect1"><a href="#id928395">26.1. General Text Editors</a></span></dt><dt><span class="sect1"><a href="#id788731">26.2. Programming Text Editors</a></span></dt><dt><span class="sect1"><a href="#id773190">26.3. Integrated Development Environments for C Programming</a></span></dt><dt><span class="sect1"><a href="#id737936">26.4. Integrated Development Environments for Python Programming</a></span></dt></dl></div><div class="para">
+ This appendix covers:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ General text editors
+ </div></li><li class="listitem"><div class="para">
+ C-specific tools and integrated development environments
+ </div></li><li class="listitem"><div class="para">
+ Python-specific development tools
+ </div></li></ul></div><div class="para">
+ Linux includes a number of text editors and integrated development environments (IDEs), going from plain old text editors all the way up to sophisticated tools. These tools are suitable for shell scripting, C, Python, and Perl programming, along with a plethora of other uses. Linux makes extensive use of text files, especially for configuration data, so Linux has always included a number of text editors.
+ </div><div class="para">
+ This appendix lists a number of tools for those who have not yet set up an RPM development environment on Linux. Note that choosing an editor or IDE is mostly a matter of personal taste. Programmers will often engage in raging battles over the superiority of text editors and other programming tools. Before searching around too far, try out what you have installed on your system and see if that works for you.
+ </div><div class="para">
+ Note that Internet sites may change or disappear, so you may have to search to find these tools.
+ </div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id928395" class="title">General Text Editors</h1></div></div></div><div class="para">
+ Linux distributions include a number of text editors with varying sets of features. The two most common editors are vi and emacs, which come with virtually all Linux distributions. These editors are good for UNIX- or Linux-savvy developers, but generally have a steep learning curve for developers used only to Windows.
+ </div><div class="para">
+ If you come from Windows, try gedit, kedit, or kate. These text editors open a graphical window on your desktop, making them appear more or less like the Windows Notepad.exe. All three offer more features than Notepad.exe, however.
+ </div><div class="para">
+ You may not have installed any of these editors, but all are available as part of Red Hat Linux. You can install vi, emacs, gedit, kedit, or kate from the packages that come with your Linux distribution.
+ </div><div class="para">
+ To start one of the editors, enter a command like the following:
+ </div><div class="para">
+ $ gedit listrpmpkgs &
+ </div><div class="para">
+ The ampersand, &, launches the program in the background. Replace gedit with the editor you choose.
+ </div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id788731" class="title">Programming Text Editors</h1></div></div></div><div class="para">
+ In addition to general-purpose text editors, Linux sports a large number of text editors with special features for programming, such as syntax highlighting. The extended version of vi, called vim, includes a number of add-ons that can help you with C programming tasks. Emacs also includes a wide array of features to help programming. Both of these editors can act as development environments with a bit of configuration. As mentioned previously, both come with most Linux distributions.
+ </div><div class="para">
+ I also like an editor called nedit and another one called jedit. The jedit editor is written in Java, so that it runs the same on Windows and Linux, a big win if you must work on multiple platforms. (Emacs and vim have versions that work on Windows, too, along with Linux.) If you use jedit, you must have a Java runtime environment installed.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ Download nedit from www.nedit.org. Download jedit from www.jedit.org. Download Java runtime environments from Sun at http://java.sun.com/j2se/downloads.html or IBM at www.ibm.com/java/jdk/ and select the IBM Developer Kit for Linux.
+ </div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id773190" class="title">Integrated Development Environments for C Programming</h1></div></div></div><div class="para">
+ If you want more of a graphical environment, Red Hat Linux ships with KDevelop, an IDE for C and C++ programming.
+ </div><div class="para">
+ Anjuta provides a GTK/GNOME-based IDE, an alternative to the KDE-based KDevelop. KDevelop, however, supports KDE, GNOME, Qt, and text-mode C and C++ applications.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ Download Anjuta from www.anjuta.org.
+ </div><div class="para">
+ The Eclipse IDE, while mostly used for Java development, has a C and C++ mode called CDT, for C/C++ Development Tools. Eclipse is important because Red Hat provides an RPM-building plug-in to Eclipse.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ Download Anjuta from www.anjuta.org. Download Eclipse from www.eclipse.org and the Eclipse CDT from www.eclipse.org/tools/downloads.html.
+ </div></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id737936" class="title">Integrated Development Environments for Python Programming</h1></div></div></div><div class="para">
+ As with C programs, Python scripts are made up of text files holding Python commands, so you need a text editor or some sort of development environment for creating Python programs. Any of the tools listed so far will work fine for developing Python applications. The key requirement is the ability to control tabs and indenting, since this is crucial to Python syntax.
+ </div><div class="para">
+ IDLE, a graphical console and editor, supports creating Python applications. This is considered part of Python. IDLE requires the Python-tools package.
+ </div><div class="para">
+ In addition, you can choose from Python-focused tools such as Bicycle Repair Man, a refactoring tool, or Boa Constructor and Black Adder, two Python IDEs.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ Boa Constructor is available from http://boa-constructor.sourceforge.net. Black Adder is a commercial tool available at www.thekompany.com.
+ </div><div class="para">
+ The Eclipse IDE, mentioned previously, supports a number of Python add-ons. Combined with the C and C++ tools, and plug-ins for building RPMs, Eclipse brings together most everything you need for Python development on Linux.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ Eclipse is available at www.eclipse.org, and Python add-ons at http://sourceforge.net/projects/pyeclipse, http://sourceforge.net/projects/pe4eclipse, or http://www.kalab.com/freeware/pythoneclipse/pythoneclipse.htm.
+ </div><div class="para">
+ This is really just the tip of the iceberg when it comes to Python tools. You can find many more available on the Internet.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ A large listing of Python editing tools appears at http://www.python.org/cgi-bin/moinmoin/PythonEditors.
+ </div></div></div><div xml:lang="ro" class="chapter" id="ch-licensing" lang="ro"><div class="titlepage"><div><div><h2 class="title">Cap. 27. Licensing RPM</h2></div></div></div><div class="toc"><dl><dt><span class="sect1"><a href="#id699117">27.1. The GNU General Public License</a></span></dt></dl></div><div class="para">
+ When incorporating someone else's existing code into your software project, you should always examine the license of the code carefully, make sure you understand its implications, and make sure you are willing to abide by them. You also need to make sure you have the legal right to incorporate the other code in your project. This is true for commercial code and commercial projects, and it is equally true for freely licensed code and free software projects.
+ </div><div class="para">
+ RPM itself and most discussed helper applications (rpmlint, rpm-spec-mode, and so forth) are free software, meaning that the programs themselves are available without cost. In addition, most of these tools are considered open source software, which means the source code for the applications are also available.
+ </div><div class="para">
+ These facts do not mean that they are unlicensed software, or that their source code can be used in any desired fashion. RPM and these helper applications are made freely available in both source and binary formats under the terms of the GNU Project's General Public License (GPL). Parts of RPM are licensed under the LGPL, the Lesser General Public License. The terms of the GPL are reproduced here, and should be consulted before incorporating any source code or binaries licensed under the GPL into your projects. Essentially, the GPL states that you can use GPL'ed source code or binaries for any purpose, so long as you always give those same rights (including access to your program’s source code) to any users to whom you give software derived from GPL'ed source code (though a lawyer should be consulted to obtain an analysis of the implications of the GPL on your project, should you decide to use GPL'ed code in any commercially licensed project you might undertake).
+ </div><div class="para">
+ </div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id699117" class="title">The GNU General Public License</h1></div></div></div><div class="para">
+ Version 2, June 1991
+ </div><div class="para">
+ </div><div class="para">
+ Copyright (C) 1989, 1991 Free Software Foundation, Inc.
+ </div><div class="para">
+ 675 Mass Ave, Cambridge, MA 02139, USA
+ </div><div class="para">
+ Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.
+ </div><div class="para">
+ </div><div class="para">
+ Preamble
+ </div><div class="para">
+ The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users. This General Public License applies to most of the Free Software Foundation's software and to any other program whose authors commit to using it. (Some other Free Software Foundation software is covered by the GNU Library General Public License instead.) You can apply it to your programs, too.
+ </div><div class="para">
+ </div><div class="para">
+ When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs; and that you know you can do these things.
+ </div><div class="para">
+ </div><div class="para">
+ To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to surrender the rights. These restrictions translate to certain responsibilities for you if you distribute copies of the software, or if you modify it.
+ </div><div class="para">
+ </div><div class="para">
+ For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the rights that you have. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights.
+ </div><div class="para">
+ </div><div class="para">
+ We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which gives you legal permission to copy, distribute and/or modify the software.
+ </div><div class="para">
+ </div><div class="para">
+ Also, for each author's protection and ours, we want to make certain that everyone understands that there is no warranty for this free software. If the software is modified by someone else and passed on, we want its recipients to know that what they have is not the original, so that any problems introduced by others will not reflect on the original authors' reputations.
+ </div><div class="para">
+ </div><div class="para">
+ Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that redistributors of a free program will individually obtain patent licenses, in effect making the program proprietary. To prevent this, we have made it clear that any patent must be licensed for everyone's free use or not licensed at all.
+ </div><div class="para">
+ </div><div class="para">
+ The precise terms and conditions for copying, distribution and modification follow.
+ </div><div class="para">
+ </div><div class="para">
+ TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+ </div><div class="para">
+ 0.This License applies to any program or other work which contains a notice placed by the copyright holder saying it may be distributed under the terms of this General Public License. The "Program", below, refers to any such program or work, and a "work based on the Program" means either the Program or any derivative work under copyright law: that is to say, a work containing the Program or a portion of it, either verbatim or with modifications and/or translated into another language. (Hereinafter, translation is included without limitation in the term "modification".) Each licensee is addressed as "you".
+ </div><div class="para">
+ Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program). Whether that is true depends on what the Program does.
+ </div><div class="para">
+ 1.You may copy and distribute verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and give any other recipients of the Program a copy of this License along with the Program.
+ </div><div class="para">
+ You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee.
+ </div><div class="para">
+ 2.You may modify your copy or copies of the Program or any portion of it, thus forming a work based on the Program, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions:
+ </div><div class="para">
+ a)You must cause the modified files to carry prominent notice stating that you changed the files and the date of any change.
+ </div><div class="para">
+ b)You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License.
+ </div><div class="para">
+ c)If the modified program normally reads commands interactively when run, you must cause it, when started running for such interactive use in the most ordinary way, to print or display an announcement including an appropriate copyright notice and a notice that there is no warranty (or else, saying that you provide a warranty) and that users may redistribute the program under these conditions, and telling the user how to view a copy of this License. (Exception: if the Program itself is interactive but does not normally print such an announcement, your work based on the Program is not required to print an announcement.)
+ </div><div class="para">
+ These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Program, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it.
+ </div><div class="para">
+ Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Program.
+ </div><div class="para">
+ In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on the Program) on a volume of a storage or distribution medium does not bring the other work under the scope of this License.
+ </div><div class="para">
+ 3.You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following:
+ </div><div class="para">
+ a)Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,
+ </div><div class="para">
+ b)Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,
+ </div><div class="para">
+ c)Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for noncommercial distribution and only if you received the program in object code or executable form with such an offer, in accord with Subsection b above.)
+ </div><div class="para">
+ The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable. However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable.
+ </div><div class="para">
+ If distribution of executable or object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place counts as distribution of the source code, even though third parties are not compelled to copy the source along with the object code.
+ </div><div class="para">
+ 4.You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense or distribute the Program is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance.
+ </div><div class="para">
+ 5.You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Program (or any work based on the Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Program or works based on it.
+ </div><div class="para">
+ 6.Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties to this License.
+ </div><div class="para">
+ 7.If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Program at all. For example, if a patent license would not permit royalty-free redistribution of the Program by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Program.
+ </div><div class="para">
+ If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply and the section as a whole is intended to apply in other circumstances.
+ </div><div class="para">
+ It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system, which is implemented by public license practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice.
+ </div><div class="para">
+ This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License.
+ </div><div class="para">
+ 8.If the distribution and/or use of the Program is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Program under this License may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this License.
+ </div><div class="para">
+ 9.The Free Software Foundation may publish revised and/or new versions of the General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.
+ </div><div class="para">
+ Each version is given a distinguishing version number. If the Program specifies a version number of this License which applies to it and "any later version", you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation.
+ </div><div class="para">
+ 10.If you wish to incorporate parts of the Program into other free programs whose distribution conditions are different, write to the author to ask for permission. For software which is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally.
+ </div><div class="para">
+ NO WARRANTY
+ </div><div class="para">
+ 11.BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+ </div><div class="para">
+ 12.IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
+ </div><div class="para">
+ END OF TERMS AND CONDITIONS
+ </div><div class="para">
+ </div><div class="para">
+ Appendix: How to Apply These Terms to Your New Programs
+ </div><div class="para">
+ </div><div class="para">
+ If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms.
+ </div><div class="para">
+ </div><div class="para">
+ To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively convey the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found.
+ </div><div class="para">
+ <one line to give the program's name and a brief idea of what it does.> Copyright (C) 19yy <name of author>
+ </div><div class="para">
+ This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.
+ </div><div class="para">
+ This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
+ </div><div class="para">
+ You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
+ </div><div class="para">
+ Also add information on how to contact you by electronic and paper mail.
+ </div><div class="para">
+ </div><div class="para">
+ If the program is interactive, make it output a short notice like this when it starts in an interactive mode:
+ </div><div class="para">
+ Gnomovision version 69, Copyright (C) 19yy name of author Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'. This is free software, and you are welcome to redistribute it under certain conditions; type `show c' for details.
+ </div><div class="para">
+ </div><div class="para">
+ The hypothetical commands `show w' and `show c' should show the appropriate parts of the General Public License. Of course, the commands you use may be called something other than `show w' and `show c'; they could even be mouse-clicks or menu items--whatever suits your program.
+ </div><div class="para">
+ </div><div class="para">
+ You should also get your employer (if you work as a programmer) or your school, if any, to sign a "copyright disclaimer" for the program, if necessary. Here is a sample; alter the names:
+ </div><div class="para">
+ Yoyodyne, Inc., hereby disclaims all copyright interest in the program `Gnomovision' (which makes passes at compilers) written by James Hacker.
+ </div><div class="para">
+ <signature of Ty Coon>, 1 April 1989Ty Coon, President of Vice
+ </div><div class="para">
+ This General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Library General Public License instead of this License.
+ </div></div></div><div xml:lang="ro" class="appendix" id="appe-Publican-Revision_History" lang="ro"><div class="titlepage"><div><div><h1 class="title">Istoria reviziilor</h1></div></div></div><div class="para">
+ <div class="revhistory"><table border="0" width="100%" summary="Revision history"><tr><th align="left" valign="top" colspan="3"><strong>Istoricul versiunilor</strong></th></tr><tr><td align="left">Versiune 1.0</td><td align="left"></td><td align="left"><span class="author"><span class="firstname"></span> <span class="surname"></span></span></td></tr><tr><td align="left" colspan="3">
+ <table border="0" summary="Simple list" class="simplelist"><tr><td></td></tr></table>
+
+ </td></tr></table></div>
+
+ </div></div><div class="index" id="id634964"><div class="titlepage"><div><div><h2 class="title">Index</h2></div></div></div><div class="index"></div></div></div></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/css/common.css b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/css/common.css
new file mode 100644
index 0000000..f9603b7
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/css/common.css
@@ -0,0 +1,1495 @@
+body, h1, h2, h3, h4, h5, h6, pre, li, div {
+ line-height: 1.29em;
+}
+
+body {
+ background-color: white;
+ margin:0 auto;
+ font-family: "liberation sans", "Myriad ", "Bitstream Vera Sans", "Lucida Grande", "Luxi Sans", "Trebuchet MS", helvetica, verdana, arial, sans-serif;
+ font-size:12px;
+ max-width:55em;
+ color:black;
+}
+
+body.toc_embeded {
+ /*for web hosting system only*/
+ margin-left: 300px;
+}
+
+object.toc, iframe.toc {
+ /*for web hosting system only*/
+ border-style:none;
+ position:fixed;
+ width:290px;
+ height:99.99%;
+ top:0;
+ left:0;
+ z-index: 100;
+ border-style:none;
+ border-right:1px solid #999;
+}
+
+/* Hide web menu */
+
+body.notoc {
+ margin-left: 3em;
+}
+
+iframe.notoc {
+ border-style:none;
+ border: none;
+ padding: 0em;
+ position:fixed;
+ width: 21px;
+ height: 29px;
+ top: 0px;
+ left:0;
+ overflow: hidden;
+ margin: 0em;
+ margin-left: -3px;
+}
+/* End hide web menu */
+
+/* desktop styles */
+body.desktop {
+ margin-left: 26em;
+}
+
+body.desktop .book > .toc {
+ display:block;
+ width:24em;
+ height:99%;
+ position:fixed;
+ overflow:auto;
+ top:0px;
+ left:0px;
+ padding-left:1em;
+ background-color:#EEEEEE;
+}
+
+.toc {
+ line-height:1.35em;
+}
+
+.toc .glossary,
+.toc .chapter, .toc .appendix {
+ margin-top:1em;
+}
+
+.toc .part {
+ margin-top:1em;
+ display:block;
+}
+
+span.glossary,
+span.appendix {
+ display:block;
+ margin-top:0.5em;
+}
+
+div {
+ padding-top:0px;
+}
+
+div.section {
+ padding-top:1em;
+}
+
+p, div.para, div.formalpara {
+ padding-top:0px;
+ margin-top:0.3em;
+ padding-bottom:0px;
+ margin-bottom:1em;
+}
+
+/*Links*/
+a {
+ outline: none;
+}
+
+a:link {
+ text-decoration:none;
+ border-bottom: 1px dotted ;
+ color:#3366cc;
+}
+
+a:visited {
+ text-decoration:none;
+ border-bottom: 1px dotted ;
+ color:#003366;
+}
+
+div.longdesc-link {
+ float:right;
+ color:#999;
+}
+
+.toc a, .qandaset a {
+ font-weight:normal;
+}
+
+/*headings*/
+h1, h2, h3, h4, h5, h6 {
+ color: #336699;
+ margin-top: 0em;
+ margin-bottom: 0em;
+ background-color: transparent;
+}
+
+h1 {
+ font-size:2.0em;
+}
+
+.titlepage h1.title {
+ font-size: 3.0em;
+ padding-top: 1em;
+ text-align:left;
+}
+
+.book > .titlepage h1.title {
+ text-align:center;
+}
+
+.article > .titlepage h1.title {
+ text-align:center;
+}
+
+.set .titlepage > div > div > h1.title {
+ text-align:center;
+}
+
+.producttitle {
+ margin-top: 0em;
+ margin-bottom: 0em;
+ font-size: 3.0em;
+ font-weight: bold;
+ background: #003d6e url(../images/h1-bg.png) top left repeat-x;
+ color: white;
+ text-align: center;
+ padding: 0.7em;
+}
+
+.titlepage .corpauthor {
+ margin-top: 1em;
+ text-align: center;
+}
+
+.section h1.title {
+ font-size: 1.6em;
+ padding: 0em;
+ color: #336699;
+ text-align: left;
+ background: white;
+}
+
+h2 {
+ font-size:1.6em;
+}
+
+
+h2.subtitle, h3.subtitle {
+ margin-top: 1em;
+ margin-bottom: 1em;
+ font-size: 1.4em;
+ text-align: center;
+}
+
+.preface > div > div > div > h2.title {
+ margin-top: 1em;
+ font-size: 2.0em;
+}
+
+.appendix h2 {
+ margin-top: 1em;
+ font-size: 2.0em;
+}
+
+
+
+h3 {
+ font-size:1.3em;
+ padding-top:0em;
+ padding-bottom:0em;
+}
+h4 {
+ font-size:1.1em;
+ padding-top:0em;
+ padding-bottom:0em;
+}
+
+h5 {
+ font-size:1em;
+}
+
+h6 {
+ font-size:1em;
+}
+
+h5.formalpara {
+ font-size:1em;
+ margin-top:2em;
+ margin-bottom:.8em;
+}
+
+.abstract h6 {
+ margin-top:1em;
+ margin-bottom:.5em;
+ font-size:2em;
+}
+
+/*element rules*/
+hr {
+ border-collapse: collapse;
+ border-style:none;
+ border-top: 1px dotted #ccc;
+ width:100%;
+ margin-top: 3em;
+}
+
+/* web site rules */
+ul.languages, .languages li {
+ display:inline;
+ padding:0em;
+}
+
+.languages li a {
+ padding:0em .5em;
+ text-decoration: none;
+}
+
+.languages li p, .languages li div.para {
+ display:inline;
+}
+
+.languages li a:link, .languages li a:visited {
+ color:#444;
+}
+
+.languages li a:hover, .languages li a:focus, .languages li a:active {
+ color:black;
+}
+
+ul.languages {
+ display:block;
+ background-color:#eee;
+ padding:.5em;
+}
+
+/*supporting stylesheets*/
+
+/*unique to the webpage only*/
+.books {
+ position:relative;
+}
+
+.versions li {
+ width:100%;
+ clear:both;
+ display:block;
+}
+
+a.version {
+ font-size:2em;
+ text-decoration:none;
+ width:100%;
+ display:block;
+ padding:1em 0em .2em 0em;
+ clear:both;
+}
+
+a.version:before {
+ content:"Version";
+ font-size:smaller;
+}
+
+a.version:visited, a.version:link {
+ color:#666;
+}
+
+a.version:focus, a.version:hover {
+ color:black;
+}
+
+.books {
+ display:block;
+ position:relative;
+ clear:both;
+ width:100%;
+}
+
+.books li {
+ display:block;
+ width:200px;
+ float:left;
+ position:relative;
+ clear: none ;
+}
+
+.books .html {
+ width:170px;
+ display:block;
+}
+
+.books .pdf {
+ position:absolute;
+ left:170px;
+ top:0px;
+ font-size:smaller;
+}
+
+.books .pdf:link, .books .pdf:visited {
+ color:#555;
+}
+
+.books .pdf:hover, .books .pdf:focus {
+ color:#000;
+}
+
+.books li a {
+ text-decoration:none;
+}
+
+.books li a:hover {
+ color:black;
+}
+
+/*products*/
+.products li {
+ display: block;
+ width:300px;
+ float:left;
+}
+
+.products li a {
+ width:300px;
+ padding:.5em 0em;
+}
+
+.products ul {
+ clear:both;
+}
+
+/*revision history*/
+.revhistory {
+ display:block;
+}
+
+.revhistory table {
+ background-color:transparent;
+ border-color:#fff;
+ padding:0em;
+ margin: 0;
+ border-collapse:collapse;
+ border-style:none;
+}
+
+.revhistory td {
+ text-align :left;
+ padding:0em;
+ border: none;
+ border-top: 1px solid #fff;
+ font-weight: bold;
+}
+
+.revhistory .simplelist td {
+ font-weight: normal;
+}
+
+.revhistory .simplelist {
+ margin-bottom: 1.5em;
+ margin-left: 1em;
+}
+
+.revhistory table th {
+ display: none;
+}
+
+
+/*credits*/
+.authorgroup div {
+ clear:both;
+ text-align: center;
+}
+
+h3.author {
+ margin: 0em;
+ padding: 0em;
+ padding-top: 1em;
+}
+
+.authorgroup h4 {
+ padding: 0em;
+ margin: 0em;
+ padding-top: 1em;
+ margin-top: 1em;
+}
+
+.author,
+.editor,
+.translator,
+.othercredit,
+.contrib {
+ display: block;
+}
+
+.revhistory .author {
+ display: inline;
+}
+
+.othercredit h3 {
+ padding-top: 1em;
+}
+
+
+.othercredit {
+ margin:0em;
+ padding:0em;
+}
+
+.releaseinfo {
+ clear: both;
+}
+
+.copyright {
+ margin-top: 1em;
+}
+
+/* qanda sets */
+.answer {
+ margin-bottom:1em;
+ border-bottom:1px dotted #ccc;
+}
+
+.qandaset .toc {
+ border-bottom:1px dotted #ccc;
+}
+
+.question {
+ font-weight:bold;
+}
+
+.answer .data, .question .data {
+ padding-left: 2.6em;
+}
+
+.answer label, .question label {
+ float:left;
+ font-weight:bold;
+}
+
+/* inline syntax highlighting */
+.perl_Alert {
+ color: #0000ff;
+}
+
+.perl_BaseN {
+ color: #007f00;
+}
+
+.perl_BString {
+ color: #5C3566;
+}
+
+.perl_Char {
+ color: #ff00ff;
+}
+
+.perl_Comment {
+ color: #FF00FF;
+}
+
+
+.perl_DataType {
+ color: #0000ff;
+}
+
+
+.perl_DecVal {
+ color: #00007f;
+}
+
+
+.perl_Error {
+ color: #ff0000;
+}
+
+
+.perl_Float {
+ color: #00007f;
+}
+
+
+.perl_Function {
+ color: #007f00;
+}
+
+
+.perl_IString {
+ color: #5C3566;
+}
+
+
+.perl_Keyword {
+ color: #002F5D;
+}
+
+
+.perl_Operator {
+ color: #ffa500;
+}
+
+
+.perl_Others {
+ color: #b03060;
+}
+
+
+.perl_RegionMarker {
+ color: #96b9ff;
+}
+
+
+.perl_Reserved {
+ color: #9b30ff;
+}
+
+
+.perl_String {
+ color: #5C3566;
+}
+
+
+.perl_Variable {
+ color: #0000ff;
+}
+
+
+.perl_Warning {
+ color: #0000ff;
+}
+
+/*Lists*/
+ul {
+ padding-left:1.6em;
+ list-style-image:url(../images/dot.png);
+ list-style-type: circle;
+}
+
+ul ul {
+ list-style-image:url(../images/dot2.png);
+ list-style-type: circle;
+}
+
+ol {
+ list-style-image:none;
+ list-style-type: decimal;
+}
+
+ol ol {
+ list-style-type: lower-alpha;
+}
+
+ol.arabic {
+ list-style-type: decimal;
+}
+
+ol.loweralpha {
+ list-style-type: lower-alpha;
+}
+
+ol.lowerroman {
+ list-style-type: lower-roman;
+}
+
+ol.upperalpha {
+ list-style-type: upper-alpha;
+}
+
+ol.upperroman {
+ list-style-type: upper-roman;
+}
+
+dt {
+ font-weight:bold;
+ margin-bottom:0em;
+ padding-bottom:0em;
+}
+
+dd {
+ margin:0em;
+ margin-left:2em;
+ padding-top:0em;
+ padding-bottom: 1em;
+}
+
+li {
+ padding-top:0px;
+ margin-top:0em;
+ padding-bottom:0px;
+ margin-bottom:0.4em;
+}
+
+li p, li div.para {
+ padding-top:0px;
+ margin-top:0em;
+ padding-bottom:0px;
+ margin-bottom:0.3em;
+}
+
+/*images*/
+img {
+ display:block;
+ margin: 2em 0;
+}
+
+.inlinemediaobject, .inlinemediaobject img {
+ display:inline;
+ margin:0em;
+}
+
+.figure img {
+ display:block;
+ margin:0;
+}
+
+.figure .title {
+ margin:0em;
+ margin-bottom:2em;
+ padding:0px;
+}
+
+/*document modes*/
+.confidential {
+ background-color:#900;
+ color:White;
+ padding:.5em .5em;
+ text-transform:uppercase;
+ text-align:center;
+}
+
+.longdesc-link {
+ display:none;
+}
+
+.longdesc {
+ display:none;
+}
+
+.prompt {
+ padding:0em .3em;
+}
+
+/*user interface styles*/
+.screen .replaceable {
+}
+
+.guibutton, .guilabel {
+ font-family: "liberation mono", "bitstream vera mono", "dejavu mono", monospace;
+ font-weight: bold;
+ white-space: nowrap;
+}
+
+.example {
+ background-color: #ffffff;
+ border-left: 3px solid #aaaaaa;
+ padding-top: 1em;
+ padding-bottom: 0.1em;
+}
+
+.example h6 {
+ padding-left: 10px;
+}
+
+.example-contents {
+ padding-left: 10px;
+ background-color: #ffffff;
+}
+
+.example-contents .para {
+/* padding: 10px;*/
+}
+
+/*terminal/console text*/
+.computeroutput,
+.option {
+ font-family:"liberation mono", "bitstream vera mono", "dejavu mono", monospace;
+ font-weight:bold;
+}
+
+.replaceable {
+ font-family:"liberation mono", "bitstream vera mono", "dejavu mono", monospace;
+ font-style: italic;
+}
+
+.command, .filename, .keycap, .classname, .literal {
+ font-family:"liberation mono", "bitstream vera mono", "dejavu mono", monospace;
+ font-weight:bold;
+}
+
+/* no bold in toc */
+.toc * {
+ font-weight: inherit;
+}
+
+pre {
+ font-family:"liberation mono", "bitstream vera mono", "dejavu mono", monospace;
+ display:block;
+ background-color: #f5f5f5;
+ color: #000000;
+ border: 1px solid #aaaaaa;
+ margin-bottom: 0.3em;
+ padding:.5em 1em;
+ white-space: pre-wrap; /* css-3 */
+ white-space: -moz-pre-wrap !important; /* Mozilla, since 1999 */
+ white-space: -pre-wrap; /* Opera 4-6 */
+ white-space: -o-pre-wrap; /* Opera 7 */
+ word-wrap: break-word; /* Internet Explorer 5.5+ */
+ font-size: 0.9em;
+}
+
+pre .replaceable,
+pre .keycap {
+}
+
+code {
+ font-family:"liberation mono", "bitstream vera mono", "dejavu mono", monospace;
+ white-space: nowrap;
+ font-weight:bold;
+}
+
+.parameter code {
+ display: inline;
+ white-space: pre-wrap; /* css-3 */
+ white-space: -moz-pre-wrap !important; /* Mozilla, since 1999 */
+ white-space: -pre-wrap; /* Opera 4-6 */
+ white-space: -o-pre-wrap; /* Opera 7 */
+ word-wrap: break-word; /* Internet Explorer 5.5+ */
+}
+
+/*Notifications*/
+div.warning:before {
+ content:url(../images/warning.png);
+ padding-left: 5px;
+}
+
+div.note:before {
+ content:url(../images/note.png);
+ padding-left: 5px;
+}
+
+div.important:before {
+ content:url(../images/important.png);
+ padding-left: 5px;
+}
+
+div.warning, div.note, div.important {
+ color: black;
+ margin: 0em;
+ padding: 0em;
+ background: none;
+ background-color: white;
+ margin-bottom: 1em;
+ border-bottom: 1px solid #aaaaaa;
+}
+
+div.warning h2, div.note h2,div.important h2 {
+ margin: 0em;
+ padding: 0em;
+ color: #eeeeec;
+ padding-top: 0px;
+ padding-bottom: 0px;
+ height: 1.4em;
+ line-height: 1.4em;
+ font-size: 1.4em;
+ display:inline;
+}
+
+div.admonition_header {
+ clear: both;
+ margin: 0em;
+ padding: 0em;
+ margin-top: -3.3em;
+ padding-left: 58px;
+ line-height: 1.0em;
+ font-size: 1.0em;
+}
+
+div.warning div.admonition_header {
+ background: url(../images/red.png) top left repeat-x;
+ background-color: #590000;
+}
+
+div.note div.admonition_header {
+ background: url(../images/green.png) top right repeat-x;
+ background-color: #597800;
+}
+
+div.important div.admonition_header {
+ background: url(../images/yellow.png) top right repeat-x;
+ background-color: #a6710f;
+}
+
+div.warning p, div.warning div.para,
+div.note p, div.note div.para,
+div.important p, div.important div.para {
+ padding: 0em;
+ margin: 0em;
+}
+
+div.admonition {
+ border: none;
+ border-left: 1px solid #aaaaaa;
+ border-right: 1px solid #aaaaaa;
+ padding:0em;
+ margin:0em;
+ padding-top: 1.5em;
+ padding-bottom: 1em;
+ padding-left: 2em;
+ padding-right: 1em;
+ background-color: #eeeeec;
+ -moz-border-radius: 0px;
+ -webkit-border-radius: 0px;
+ border-radius: 0px;
+}
+
+/*Page Title*/
+#title {
+ display:block;
+ height:45px;
+ padding-bottom:1em;
+ margin:0em;
+}
+
+#title a.left{
+ display:inline;
+ border:none;
+}
+
+#title a.left img{
+ border:none;
+ float:left;
+ margin:0em;
+ margin-top:.7em;
+}
+
+#title a.right {
+ padding-bottom:1em;
+}
+
+#title a.right img {
+ border:none;
+ float:right;
+ margin:0em;
+ margin-top:.7em;
+}
+
+/*Table*/
+table {
+ border:1px solid #6c614b;
+ width:100%;
+ border-collapse:collapse;
+}
+
+table.simplelist, .calloutlist table {
+ border-style: none;
+}
+
+table th {
+ text-align:left;
+ background-color:#6699cc;
+ padding:.3em .5em;
+ color:white;
+}
+
+table td {
+ padding:.15em .5em;
+}
+
+table tr.even td {
+ background-color:#f5f5f5;
+}
+
+table th p:first-child, table td p:first-child, table li p:first-child,
+table th div.para:first-child, table td div.para:first-child, table li div.para:first-child {
+ margin-top:0em;
+ padding-top:0em;
+ display:inline;
+}
+
+th, td {
+ border-style:none;
+ vertical-align: top;
+ border: 1px solid #000;
+}
+
+.simplelist th, .simplelist td {
+ border: none;
+}
+
+table table td {
+ border-bottom:1px dotted #aaa;
+ background-color:white;
+ padding:.6em 0em;
+}
+
+table table {
+ border:1px solid white;
+}
+
+td.remarkval {
+ color:#444;
+}
+
+td.fieldval {
+ font-weight:bold;
+}
+
+.lbname, .lbtype, .lbdescr, .lbdriver, .lbhost {
+ color:white;
+ font-weight:bold;
+ background-color:#999;
+ width:120px;
+}
+
+td.remarkval {
+ width:230px;
+}
+
+td.tname {
+ font-weight:bold;
+}
+
+th.dbfield {
+ width:120px;
+}
+
+th.dbtype {
+ width:70px;
+}
+
+th.dbdefault {
+ width:70px;
+}
+
+th.dbnul {
+ width:70px;
+}
+
+th.dbkey {
+ width:70px;
+}
+
+span.book {
+ margin-top:4em;
+ display:block;
+}
+
+span.chapter {
+ display:block;
+ margin-top:0.5em;
+}
+
+table.simplelist td, .calloutlist table td {
+ border-style: none;
+}
+
+/*Breadcrumbs*/
+#breadcrumbs ul li.first:before {
+ content:" ";
+}
+
+#breadcrumbs {
+ color:#900;
+ padding:3px;
+ margin-bottom:25px;
+}
+
+#breadcrumbs ul {
+ margin-left:0;
+ padding-left:0;
+ display:inline;
+ border:none;
+}
+
+#breadcrumbs ul li {
+ margin-left:0;
+ padding-left:2px;
+ border:none;
+ list-style:none;
+ display:inline;
+}
+
+#breadcrumbs ul li:before {
+ content:"\0020 \0020 \0020 \00BB \0020";
+ color:#333;
+}
+
+/*index*/
+.glossary h3,
+.index h3 {
+ font-size: 2em;
+ color:#aaa;
+ margin:0em;
+}
+
+.indexdiv {
+ margin-bottom:1em;
+}
+
+.glossary dt,
+.index dt {
+ color:#444;
+ padding-top:.5em;
+}
+
+.glossary dl dl dt,
+.index dl dl dt {
+ color:#777;
+ font-weight:normal;
+ padding-top:0em;
+}
+
+.index dl dl dt:before {
+ content:"- ";
+ color:#ccc;
+}
+
+/*changes*/
+.footnote {
+ font-size: .7em;
+ margin:0em;
+ color:#222;
+}
+
+table .footnote {
+}
+
+sup {
+ color:#999;
+ margin:0em;
+ padding:0em;
+ line-height: .4em;
+ font-size: 1em;
+ padding-left:0em;
+}
+
+.footnote {
+ position:relative;
+}
+
+.footnote sup {
+ color:#e3dcc0;
+ position:absolute;
+ left: .4em;
+}
+
+.footnote sup a:link,
+.footnote sup a:visited {
+ color:#92917d;
+ text-decoration:none;
+}
+
+.footnote:hover sup a {
+ text-decoration:none;
+}
+
+.footnote p,.footnote div.para {
+ padding-left:2em;
+}
+
+.footnote a:link,
+.footnote a:visited {
+ color:#00537c;
+}
+
+.footnote a:hover {
+}
+
+/**/
+div.chapter {
+ margin-top:3em;
+}
+
+div.section {
+ margin-top:1em;
+}
+
+div.note .replaceable,
+div.important .replaceable,
+div.warning .replaceable,
+div.note .keycap,
+div.important .keycap,
+div.warning .keycap
+{
+}
+
+ul li p:last-child, ul li div.para:last-child {
+ margin-bottom:0em;
+ padding-bottom:0em;
+}
+
+/*document navigation*/
+.docnav a, .docnav strong {
+ border:none;
+ text-decoration:none;
+ font-weight:normal;
+}
+
+.docnav {
+ list-style:none;
+ margin:0em;
+ padding:0em;
+ position:relative;
+ width:100%;
+ padding-bottom:2em;
+ padding-top:1em;
+ border-top:1px dotted #ccc;
+}
+
+.docnav li {
+ list-style:none;
+ margin:0em;
+ padding:0em;
+ display:inline;
+ font-size:.8em;
+}
+
+.docnav li:before {
+ content:" ";
+}
+
+.docnav li.previous, .docnav li.next {
+ position:absolute;
+ top:1em;
+}
+
+.docnav li.up, .docnav li.home {
+ margin:0em 1.5em;
+}
+
+.docnav li.previous {
+ left:0px;
+ text-align:left;
+}
+
+.docnav li.next {
+ right:0px;
+ text-align:right;
+}
+
+.docnav li.previous strong, .docnav li.next strong {
+ height:22px;
+ display:block;
+}
+
+.docnav {
+ margin:0 auto;
+ text-align:center;
+}
+
+.docnav li.next a strong {
+ background: url(../images/stock-go-forward.png) top right no-repeat;
+ padding-top:3px;
+ padding-bottom:4px;
+ padding-right:28px;
+ font-size:1.2em;
+}
+
+.docnav li.previous a strong {
+ background: url(../images/stock-go-back.png) top left no-repeat;
+ padding-top:3px;
+ padding-bottom:4px;
+ padding-left:28px;
+ padding-right:0.5em;
+ font-size:1.2em;
+}
+
+.docnav li.home a strong {
+ background: url(../images/stock-home.png) top left no-repeat;
+ padding:5px;
+ padding-left:28px;
+ font-size:1.2em;
+}
+
+.docnav li.up a strong {
+ background: url(../images/stock-go-up.png) top left no-repeat;
+ padding:5px;
+ padding-left:28px;
+ font-size:1.2em;
+}
+
+.docnav a:link, .docnav a:visited {
+ color:#666;
+}
+
+.docnav a:hover, .docnav a:focus, .docnav a:active {
+ color:black;
+}
+
+.docnav a {
+ max-width: 10em;
+ overflow:hidden;
+}
+
+.docnav a:link strong {
+ text-decoration:none;
+}
+
+.docnav {
+ margin:0 auto;
+ text-align:center;
+}
+
+ul.docnav {
+ margin-bottom: 1em;
+}
+/* Reports */
+.reports ul {
+ list-style:none;
+ margin:0em;
+ padding:0em;
+}
+
+.reports li{
+ margin:0em;
+ padding:0em;
+}
+
+.reports li.odd {
+ background-color: #eeeeee;
+ margin:0em;
+ padding:0em;
+}
+
+.reports dl {
+ display:inline;
+ margin:0em;
+ padding:0em;
+ float:right;
+ margin-right: 17em;
+ margin-top:-1.3em;
+}
+
+.reports dt {
+ display:inline;
+ margin:0em;
+ padding:0em;
+}
+
+.reports dd {
+ display:inline;
+ margin:0em;
+ padding:0em;
+ padding-right:.5em;
+}
+
+.reports h2, .reports h3{
+ display:inline;
+ padding-right:.5em;
+ font-size:10pt;
+ font-weight:normal;
+}
+
+.reports div.progress {
+ display:inline;
+ float:right;
+ width:16em;
+ background:#c00 url(../images/shine.png) top left repeat-x;
+ margin:0em;
+ margin-top:-1.3em;
+ padding:0em;
+ border:none;
+}
+
+/*uniform*/
+body.results, body.reports {
+ max-width:57em ;
+ padding:0em;
+}
+
+/*Progress Bar*/
+div.progress {
+ display:block;
+ float:left;
+ width:16em;
+ background:#c00 url(../images/shine.png) top left repeat-x;
+ height:1em;
+}
+
+div.progress span {
+ height:1em;
+ float:left;
+}
+
+div.progress span.translated {
+ background:#6c3 url(../images/shine.png) top left repeat-x;
+}
+
+div.progress span.fuzzy {
+ background:#ff9f00 url(../images/shine.png) top left repeat-x;
+}
+
+
+/*Results*/
+
+.results ul {
+ list-style:none;
+ margin:0em;
+ padding:0em;
+}
+
+.results li{
+ margin:0em;
+ padding:0em;
+}
+
+.results li.odd {
+ background-color: #eeeeee;
+ margin:0em;
+ padding:0em;
+}
+
+.results dl {
+ display:inline;
+ margin:0em;
+ padding:0em;
+ float:right;
+ margin-right: 17em;
+ margin-top:-1.3em;
+}
+
+.results dt {
+ display:inline;
+ margin:0em;
+ padding:0em;
+}
+
+.results dd {
+ display:inline;
+ margin:0em;
+ padding:0em;
+ padding-right:.5em;
+}
+
+.results h2, .results h3 {
+ display:inline;
+ padding-right:.5em;
+ font-size:10pt;
+ font-weight:normal;
+}
+
+.results div.progress {
+ display:inline;
+ float:right;
+ width:16em;
+ background:#c00 url(../images/shine.png) top left repeat-x;
+ margin:0em;
+ margin-top:-1.3em;
+ padding:0em;
+ border:none;
+}
+
+/* Dirty EVIL Mozilla hack for round corners */
+pre {
+ -moz-border-radius:11px;
+ -webkit-border-radius:11px;
+ border-radius: 11px;
+}
+
+.example {
+ -moz-border-radius:0px;
+ -webkit-border-radius:0px;
+ border-radius: 0px;
+}
+
+.package, .citetitle {
+ font-style: italic;
+}
+
+.titlepage .edition {
+ color: #336699;
+ background-color: transparent;
+ margin-top: 1em;
+ margin-bottom: 1em;
+ font-size: 1.4em;
+ font-weight: bold;
+ text-align: center;
+}
+
+span.remark {
+ background-color: #ff00ff;
+}
+
+.draft {
+ background-image: url(../images/watermark-draft.png);
+ background-repeat: repeat-y;
+ background-position: center;
+}
+
+.foreignphrase {
+ font-style: inherit;
+}
+
+dt {
+ clear:both;
+}
+
+dt img {
+ border-style: none;
+ max-width: 112px;
+}
+
+dt object {
+ max-width: 112px;
+}
+
+dt .inlinemediaobject, dt object {
+ display: inline;
+ float: left;
+ margin-bottom: 1em;
+ padding-right: 1em;
+ width: 112px;
+}
+
+dl:after {
+ display: block;
+ clear: both;
+ content: "";
+}
+
+.toc dd {
+ padding-bottom: 0em;
+ margin-bottom: 1em;
+ padding-left: 1.3em;
+ margin-left: 0em;
+}
+
+div.toc > dl > dt {
+ padding-bottom: 0em;
+ margin-bottom: 0em;
+ margin-top: 1em;
+}
+
+
+.strikethrough {
+ text-decoration: line-through;
+}
+
+.underline {
+ text-decoration: underline;
+}
+
+.calloutlist img, .callout {
+ padding: 0em;
+ margin: 0em;
+ width: 12pt;
+ display: inline;
+ vertical-align: middle;
+}
+
+.stepalternatives {
+ list-style-image: none;
+ list-style-type: none;
+}
+
+
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/css/default.css b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/css/default.css
new file mode 100644
index 0000000..bf38ebb
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/css/default.css
@@ -0,0 +1,3 @@
+ at import url("common.css");
+ at import url("overrides.css");
+ at import url("lang.css");
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/css/lang.css b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/css/lang.css
new file mode 100644
index 0000000..81c3115
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/css/lang.css
@@ -0,0 +1,2 @@
+/* place holder */
+
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/css/overrides.css b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/css/overrides.css
new file mode 100644
index 0000000..057be29
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/css/overrides.css
@@ -0,0 +1,51 @@
+a:link {
+ color:#0066cc;
+}
+
+a:hover, a:active {
+ color:#003366;
+}
+
+a:visited {
+ color:#6699cc;
+}
+
+
+h1 {
+ color:#3c6eb4
+}
+
+.producttitle {
+ background: #3c6eb4 url(../images/h1-bg.png) top left repeat;
+}
+
+.section h1.title {
+ color:#3c6eb4;
+}
+
+
+h2,h3,h4,h5,h6 {
+ color:#3c6eb4;
+}
+
+table {
+ border:1px solid #3c6eb4;
+}
+
+table th {
+ background-color:#3c6eb4;
+}
+
+
+table tr.even td {
+ background-color:#f5f5f5;
+}
+
+.revhistory table th {
+ color:#3c6eb4;
+}
+
+.titlepage .edition {
+ color: #3c6eb4;
+}
+
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/css/print.css b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/css/print.css
new file mode 100644
index 0000000..773d8ae
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/css/print.css
@@ -0,0 +1,16 @@
+ at import url("common.css");
+ at import url("overrides.css");
+ at import url("lang.css");
+
+#tocframe {
+ display: none;
+}
+
+body.toc_embeded {
+ margin-left: 30px;
+}
+
+.producttitle {
+ color: #336699;
+}
+
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/1.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/1.png
new file mode 100644
index 0000000..c21d7a3
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/1.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/1.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/1.svg
new file mode 100644
index 0000000..a2b3903
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/1.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;fill:#000000;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 17.853468,22.008438 -2.564941,0 0,-7.022461 c -5e-6,-0.143873 -5e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224122,0.224121 -0.08301,0.07748 -0.168786,0.157724 -0.257324,0.240723 -0.08854,0.08302 -0.17432,0.157723 -0.257324,0.224121 l -1.394531,1.120605 -1.245117,-1.543945 3.909668,-3.1127931 2.108398,0 0,12.1357421"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/10.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/10.png
new file mode 100644
index 0000000..15b81da
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/10.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/10.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/10.svg
new file mode 100644
index 0000000..af015ab
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/10.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724 -0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L 8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0 0,12.1357421"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.6378,15.940567 c -9e-6,0.979497 -0.07748,1.853845 -0.232422,2.623047 -0.149422,0.769208 -0.392912,1.422202 -0.730468,1.958984 -0.332039,0.536785 -0.763679,0.94629 -1.294922,1.228516 -0.525722,0.282226 -1.162115,0.42334 -1.90918,0.42334 -0.702803,0 -1.314294,-0.141114 -1.834473,-0.42334 -0.520184,-0.282226 -0.951824,-0.691731 -1.294922,-1.228516 -0.3431,-0.536782 -0.600424,-1.189776 -0.771972,-1.958984 -0.166016,-0.769202 -0.249024,-1.64355 -0.249024,-2.623047 0,-0.979485 0.07471,-1.8566 0.224121,-2.631348 0.154948,-0.77473 0.398437,-1.430491 0.730469,-1.967285 0.33203,-0.536772 0.760903,-0.946277 1.286621,-1.228515 0.525713,-0.2877487 1.162106,-0.4316287 1.90918,-0.431641 0.69726,1.23e-5 1.305984,0.1411254 1.826172,0.42334 0.520175,0.282238 0.954582,0.691743 1.303223,1.228515 0.348624,0.536794 0.608715,1.192555 0.780273,1.967286 0.171541,0.774747 0.257315,1.654629 0.257324,2.639648 m -5.760742,0 c -3e-6,1.383468 0.118975,2.423832 0.356934,3.121094 0.237952,0.6
97268 0.650223,1.0459 1.236816,1.045898 0.575516,2e-6 0.987787,-0.345863 1.236816,-1.037597 0.254552,-0.691729 0.38183,-1.734859 0.381836,-3.129395 -6e-6,-1.38899 -0.127284,-2.43212 -0.381836,-3.129395 -0.249029,-0.702789 -0.6613,-1.054188 -1.236816,-1.054199 -0.293299,1.1e-5 -0.542322,0.08855 -0.74707,0.265625 -0.199223,0.177093 -0.362471,0.439951 -0.489746,0.788574 -0.127282,0.348642 -0.218591,0.785816 -0.273926,1.311524 -0.05534,0.52019 -0.08301,1.126146 -0.08301,1.817871"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/11.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/11.png
new file mode 100644
index 0000000..2fcc2dd
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/11.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/11.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/11.svg
new file mode 100644
index 0000000..cb82b70
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/11.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724 -0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L 8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0 0,12.1357421"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 22.579206,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141117,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168786,0.157724 -0.257324,0.240723 -0.08855,0.08302 -0.17432,0.157723 -0.257325,0.224121 l -1.394531,1.120605 -1.245117,-1.543945 3.909668,-3.1127931 2.108398,0 0,12.1357421"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/12.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/12.png
new file mode 100644
index 0000000..edebe20
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/12.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/12.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/12.svg
new file mode 100644
index 0000000..3b6d822
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/12.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724 -0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L 8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0 0,12.1357421"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.621199,22.008438 -8.143067,0 0,-1.784668 2.855469,-3.07959 c 0.359697,-0.387364 0.686194,-0.744297 0.979492,-1.0708 0.29329,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373535,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437179,10e-6 -0.857751,0.10792 -1.261719,0.323731 -0.403974,0.215829 -0.827314,0.522958 -1.27002,0.921386 l -1.394531,-1.651855 c 0.249023,-0.226877 0.509114,-0.442698 0.780274,-0.647461 0.271157,-0.210275 0.569985,-0.395659 0.896484,-0.556152 0.326495,-0.16047 0.686195,-0.2877488 1.079101,-0.3818364 0.3929,-0.099597 0.832841,-0.1494018 1.319825,-0.1494141 0.581049,1.23e-5 1.101231,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860507,0.3901488 1.187011,0.6889648 0.32649,0.293305 0.575513,0.650239 0.747071,1.070801 0.177075,0.420583 0.265616,0.893727 0.265625,1.419
433 -9e-6,0.47592 -0.08302,0.932463 -0.249024,1.369629 -0.166024,0.431648 -0.392911,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622565,0.830083 -1.004394,1.245117 -0.376309,0.40951 -0.78028,0.827315 -1.211914,1.253418 l -1.460938,1.469238 0,0.116211 4.947266,0 0,2.158203"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/13.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/13.png
new file mode 100644
index 0000000..ec48cef
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/13.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/13.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/13.svg
new file mode 100644
index 0000000..226e461
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/13.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724 -0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L 8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0 0,12.1357421"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.148054,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.207519,1.137207 -0.132821,0.33204 -0.318205,0.625334 -0.556153,0.879883 -0.232429,0.249031 -0.509121,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979486,0.121751 1.721021,0.420579 2.22461,0.896485 0.503572,0.470382 0.755362,1.106775 0.755371,1.909179 -9e-6,0.531253 -0.09685,1.023766 -0.290528,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879882,1.170411 -0.392911,0.332031 -0.890958,0.592122 -1.494141,0.780273 -0.597662,0.182617 -1.303227,0.273926 -2.116699,0.273926 -0.652998,0 -1.267256,-0.05534 -1.842774,-0.166016 -0.575522,-0.105143 -1.112305,-0.268392 -1.610351,-0.489746 l 0,-2.183105 c 0.249022,0.132815 0.51188,0.249025 0.788574,0.348632 0.276691,0.09961 0.553384,0.185387 0.830078,0.257325 0.27669,0.06641 0.547849,0.116212 0.813477,0.149414 0.271155,0.0332 0.525712,0.04981 0.763671,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132812 0.315425,
-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188146,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124512,-0.73877 -7e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.20474 -0.265631,-0.376289 -0.498047,-0.51464 -0.226893,-0.143876 -0.525721,-0.254553 -0.896485,-0.332032 -0.370772,-0.07747 -0.827315,-0.116205 -1.369628,-0.116211 l -0.863282,0 0,-1.801269 0.84668,0 c 0.509111,7e-6 0.93245,-0.04426 1.270019,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124512,-0.672363 -6e-6,-0.431632 -0.135585,-0.769197 -0.406739,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,1e-5 -0.514652,0.02768 -0.747071,0.08301 -0.226891,0.04981 -0.439944,0.116221 -0.63916,0.199218 -0.193687,0.07748 -0.373537,0.166026 -0.53955,0.265625 -0.160484,0.09409 -0.307131,0.188161 -0.439942,0.282227 l -1.294922,-1.7
09961 c 0.232421,-0.171538 0.484212,-0.329253 0.755371,-0.473145 0.276692,-0.143868 0.575519,-0.26838 0.896485,-0.373535 0.320961,-0.1106647 0.666826,-0.1964393 1.037597,-0.2573239 0.370765,-0.06086 0.766435,-0.091296 1.187012,-0.091309 0.597651,1.23e-5 1.139969,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/14.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/14.png
new file mode 100644
index 0000000..33d5637
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/14.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/14.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/14.svg
new file mode 100644
index 0000000..5aaa3a3
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/14.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724 -0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L 8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0 0,12.1357421"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.803816,19.493301 -1.460938,0 0,2.515137 -2.498535,0 0,-2.515137 -5.013672,0 0,-1.784668 5.154785,-7.8359371 2.357422,0 0,7.6284181 1.460938,0 0,1.992187 m -3.959473,-1.992187 0,-2.058594 c -5e-6,-0.07193 -5e-6,-0.17431 0,-0.307129 0.0055,-0.138339 0.01106,-0.293287 0.0166,-0.464844 0.0055,-0.171541 0.01106,-0.348625 0.0166,-0.53125 0.01106,-0.182609 0.01936,-0.356925 0.0249,-0.522949 0.01106,-0.166007 0.01936,-0.309887 0.0249,-0.43164 0.01106,-0.12727 0.01936,-0.218579 0.0249,-0.273926 l -0.07471,0 c -0.09961,0.232431 -0.213058,0.478687 -0.340332,0.738769 -0.121749,0.2601 -0.262862,0.520191 -0.42334,0.780274 l -2.02539,3.071289 2.755859,0"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/15.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/15.png
new file mode 100644
index 0000000..f1a4eb2
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/15.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/15.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/15.svg
new file mode 100644
index 0000000..f51dd96
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/15.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724 -0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L 8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0 0,12.1357421"
+ id="path2839"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 20.761335,14.255508 c 0.520177,8e-6 1.004389,0.08025 1.452637,0.240723 0.448235,0.160489 0.838372,0.395678 1.17041,0.705566 0.332024,0.309903 0.592114,0.697272 0.780274,1.16211 0.188142,0.459315 0.282218,0.987797 0.282226,1.585449 -8e-6,0.658532 -0.102385,1.250654 -0.307129,1.776367 -0.20476,0.520184 -0.506355,0.962892 -0.904785,1.328125 -0.398444,0.359701 -0.893724,0.636394 -1.48584,0.830078 -0.586594,0.193685 -1.261723,0.290528 -2.02539,0.290528 -0.304366,0 -0.605961,-0.01384 -0.904785,-0.0415 -0.298831,-0.02767 -0.586591,-0.06917 -0.863282,-0.124512 -0.27116,-0.04981 -0.531251,-0.116211 -0.780273,-0.199219 -0.243491,-0.08301 -0.464845,-0.17985 -0.664063,-0.290527 l 0,-2.216309 c 0.193684,0.11068 0.417805,0.215823 0.672364,0.31543 0.254555,0.09408 0.517413,0.177086 0.788574,0.249024 0.27669,0.06641 0.553383,0.121746 0.830078,0.166015 0.276689,0.03874 0.539547,0.05811 0.788574,0.05811 0.741532,2e-6 1.305985,-0.152179 1.69336,-0.456543 0.387364,-0.309893 0.581048
,-0.799639 0.581054,-1.469239 -6e-6,-0.597651 -0.190924,-1.051427 -0.572754,-1.361328 -0.376307,-0.315424 -0.960128,-0.473139 -1.751464,-0.473144 -0.143884,5e-6 -0.298832,0.0083 -0.464844,0.0249 -0.160485,0.01661 -0.320967,0.03874 -0.481446,0.06641 -0.15495,0.02768 -0.304364,0.05811 -0.448242,0.09131 -0.143882,0.02767 -0.268394,0.05811 -0.373535,0.09131 l -1.020996,-0.547852 0.456543,-6.1840821 6.408203,0 0,2.1748051 -4.183594,0 -0.199218,2.382324 c 0.177079,-0.03873 0.381832,-0.07747 0.614257,-0.116211 0.237952,-0.03873 0.542314,-0.0581 0.913086,-0.05811"
+ id="path2841"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/16.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/16.png
new file mode 100644
index 0000000..d38a155
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/16.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/16.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/16.svg
new file mode 100644
index 0000000..cb7e2f5
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/16.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724 -0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L 8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0 0,12.1357421"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 16.428328,16.853653 c -1e-6,-0.581049 0.03044,-1.159336 0.09131,-1.734863 0.06641,-0.575514 0.17985,-1.126132 0.340332,-1.651856 0.166015,-0.531241 0.387369,-1.023753 0.664063,-1.477539 0.282224,-0.453765 0.636391,-0.846669 1.0625,-1.178711 0.431637,-0.337553 0.946285,-0.600411 1.543945,-0.788574 0.603185,-0.1936727 1.305984,-0.2905151 2.108398,-0.2905274 0.116205,1.23e-5 0.243483,0.00278 0.381836,0.0083 0.13834,0.00555 0.276686,0.013847 0.415039,0.024902 0.143873,0.00555 0.282219,0.016614 0.415039,0.033203 0.132805,0.016614 0.251783,0.035982 0.356934,0.058105 l 0,2.0502924 c -0.210294,-0.04979 -0.434415,-0.08853 -0.672363,-0.116211 -0.232429,-0.03319 -0.467618,-0.04979 -0.705567,-0.0498 -0.747076,1e-5 -1.361333,0.09408 -1.842773,0.282226 -0.48145,0.182627 -0.863285,0.439951 -1.145508,0.771973 -0.28223,0.33204 -0.484215,0.730477 -0.605957,1.195312 -0.116214,0.464852 -0.188154,0.9795 -0.21582,1.543946 l 0.09961,0 c 0.110674,-0.199212 0.243487,-0.384596 0.398438,-0
.556153 0.160478,-0.177076 0.345862,-0.32649 0.556152,-0.448242 0.210282,-0.127271 0.445471,-0.22688 0.705566,-0.298828 0.265621,-0.07193 0.561681,-0.107902 0.888184,-0.10791 0.52571,8e-6 0.998854,0.08578 1.419434,0.257324 0.420565,0.171557 0.774732,0.42058 1.0625,0.74707 0.293286,0.326504 0.517407,0.727708 0.672363,1.203614 0.154939,0.475916 0.232413,1.021 0.232422,1.635254 -9e-6,0.658532 -0.09408,1.247887 -0.282227,1.768066 -0.182625,0.520184 -0.445483,0.962892 -0.788574,1.328125 -0.343106,0.359701 -0.758145,0.636394 -1.245117,0.830078 -0.486985,0.188151 -1.034836,0.282227 -1.643555,0.282227 -0.59766,0 -1.156579,-0.105144 -1.676758,-0.31543 -0.520185,-0.21582 -0.97396,-0.542317 -1.361328,-0.979492 -0.381837,-0.437173 -0.683432,-0.987791 -0.904785,-1.651856 -0.215821,-0.669593 -0.323731,-1.460933 -0.32373,-2.374023 m 4.216796,3.270508 c 0.226883,2e-6 0.431636,-0.0415 0.614258,-0.124512 0.188146,-0.08854 0.348627,-0.218585 0.481446,-0.390137 0.13834,-0.17708 0.243483,-0.3984
34 0.315429,-0.664062 0.07747,-0.265622 0.116205,-0.581051 0.116211,-0.946289 -6e-6,-0.592118 -0.124518,-1.056961 -0.373535,-1.394531 -0.243495,-0.343094 -0.61703,-0.514643 -1.120605,-0.514649 -0.254562,6e-6 -0.486984,0.04981 -0.697266,0.149414 -0.21029,0.09962 -0.390141,0.229661 -0.539551,0.390137 -0.149417,0.160487 -0.265628,0.340337 -0.348633,0.539551 -0.07748,0.199223 -0.116214,0.401209 -0.116211,0.605957 -3e-6,0.28223 0.0332,0.564456 0.09961,0.846679 0.07194,0.276696 0.17708,0.528486 0.315429,0.755371 0.143877,0.221357 0.318193,0.401207 0.52295,0.539551 0.210282,0.138349 0.453771,0.207522 0.730468,0.20752"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/17.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/17.png
new file mode 100644
index 0000000..d83e898
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/17.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/17.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/17.svg
new file mode 100644
index 0000000..5d6f0ad
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/17.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724 -0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L 8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0 0,12.1357421"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 17.51573,22.008438 4.316406,-9.960937 -5.578125,0 0,-2.1582035 8.367188,0 0,1.6103515 -4.424317,10.508789 -2.681152,0"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/18.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/18.png
new file mode 100644
index 0000000..9e39de4
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/18.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/18.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/18.svg
new file mode 100644
index 0000000..9ea672c
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/18.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724 -0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L 8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0 0,12.1357421"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 20.48741,9.7149811 c 0.503575,1.23e-5 0.979486,0.060885 1.427734,0.1826172 0.448236,0.1217567 0.841139,0.3043737 1.178711,0.5478517 0.337557,0.243501 0.605949,0.547862 0.805176,0.913086 0.19921,0.365244 0.298819,0.794118 0.298828,1.286621 -9e-6,0.365243 -0.05535,0.697274 -0.166016,0.996094 -0.110685,0.293302 -0.262866,0.561694 -0.456543,0.805175 -0.193692,0.237963 -0.423347,0.451017 -0.688965,0.639161 -0.265631,0.188157 -0.553392,0.359707 -0.863281,0.514648 0.320957,0.171556 0.63362,0.362473 0.937988,0.572754 0.309889,0.210292 0.583814,0.448247 0.821778,0.713867 0.237947,0.260096 0.428865,0.55339 0.572754,0.879883 0.143871,0.326501 0.215811,0.691735 0.21582,1.095703 -9e-6,0.503583 -0.09962,0.960126 -0.298828,1.369629 -0.199227,0.409506 -0.478687,0.758139 -0.838379,1.045898 -0.359708,0.287761 -0.791348,0.509115 -1.294922,0.664063 -0.498053,0.154948 -1.048671,0.232422 -1.651855,0.232422 -0.652999,0 -1.234053,-0.07471 -1.743164,-0.224121 -0.509117,-0.149414 -0.93799
1,-0.362467 -1.286622,-0.639161 -0.348634,-0.276691 -0.614258,-0.617023 -0.796875,-1.020996 -0.177084,-0.403969 -0.265625,-0.857744 -0.265625,-1.361328 0,-0.415035 0.06087,-0.78857 0.182618,-1.120605 0.121744,-0.332027 0.287759,-0.630855 0.498046,-0.896485 0.210285,-0.265619 0.456542,-0.500808 0.73877,-0.705566 0.282224,-0.204747 0.583819,-0.384597 0.904785,-0.539551 -0.271161,-0.171543 -0.525718,-0.356927 -0.763672,-0.556152 -0.237957,-0.204746 -0.445477,-0.428866 -0.622558,-0.672363 -0.171551,-0.249016 -0.309897,-0.522942 -0.415039,-0.821778 -0.09961,-0.298819 -0.149415,-0.628083 -0.149414,-0.987793 -1e-6,-0.481435 0.09961,-0.902008 0.298828,-1.261718 0.204751,-0.365224 0.478676,-0.669585 0.821777,-0.913086 0.343097,-0.249012 0.738767,-0.434396 1.187012,-0.5561527 0.448238,-0.1217326 0.918615,-0.1826049 1.411133,-0.1826172 m -1.718262,9.0644529 c -3e-6,0.221357 0.03597,0.42611 0.10791,0.614258 0.07194,0.18262 0.17708,0.340334 0.31543,0.473145 0.143876,0.132814 0.32096,0.23
7957 0.53125,0.315429 0.210282,0.07194 0.453771,0.107912 0.730468,0.10791 0.58105,2e-6 1.015457,-0.135577 1.303223,-0.406738 0.287754,-0.27669 0.431634,-0.639157 0.431641,-1.087402 -7e-6,-0.232419 -0.04981,-0.439938 -0.149414,-0.622559 -0.09408,-0.188147 -0.218594,-0.359696 -0.373535,-0.514648 -0.14942,-0.160478 -0.32097,-0.307125 -0.514649,-0.439942 -0.19369,-0.132807 -0.387375,-0.260086 -0.581055,-0.381836 L 20.3878,16.72084 c -0.243494,0.12175 -0.464848,0.254563 -0.664062,0.398438 -0.199223,0.138351 -0.370772,0.293299 -0.514649,0.464844 -0.138349,0.16602 -0.246259,0.348637 -0.32373,0.547851 -0.07748,0.199223 -0.116214,0.415043 -0.116211,0.647461 m 1.70166,-7.188476 c -0.182622,10e-6 -0.354171,0.02768 -0.514648,0.08301 -0.154952,0.05535 -0.290532,0.13559 -0.406739,0.240723 -0.11068,0.105153 -0.199222,0.235199 -0.265625,0.390137 -0.06641,0.154957 -0.09961,0.329274 -0.09961,0.522949 -3e-6,0.232431 0.0332,0.434416 0.09961,0.605957 0.07194,0.166024 0.166012,0.315438 0.282227,0
.448242 0.121741,0.127287 0.260087,0.243498 0.415039,0.348633 0.160477,0.09962 0.32926,0.199226 0.506348,0.298828 0.171544,-0.08853 0.334793,-0.185376 0.489746,-0.290527 0.154942,-0.105135 0.290522,-0.224113 0.406738,-0.356934 0.121739,-0.138338 0.218581,-0.293286 0.290527,-0.464843 0.07193,-0.171541 0.107904,-0.367993 0.10791,-0.589356 -6e-6,-0.193675 -0.03321,-0.367992 -0.09961,-0.522949 -0.06641,-0.154938 -0.15772,-0.284984 -0.273926,-0.390137 -0.116216,-0.105133 -0.254562,-0.185374 -0.415039,-0.240723 -0.160487,-0.05533 -0.334803,-0.083 -0.522949,-0.08301"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/19.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/19.png
new file mode 100644
index 0000000..9eeedfb
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/19.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/19.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/19.svg
new file mode 100644
index 0000000..80d1d09
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/19.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724 -0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L 8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0 0,12.1357421"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.554792,15.052383 c -8e-6,0.581061 -0.03321,1.162116 -0.09961,1.743164 -0.06088,0.575526 -0.174325,1.126144 -0.340332,1.651856 -0.16049,0.525719 -0.381844,1.018232 -0.664063,1.477539 -0.2767,0.453778 -0.630866,0.846681 -1.0625,1.178711 -0.426112,0.332032 -0.94076,0.59489 -1.543945,0.788574 -0.597661,0.188151 -1.300459,0.282227 -2.108398,0.282227 -0.116214,0 -0.243493,-0.0028 -0.381836,-0.0083 -0.138349,-0.0055 -0.279462,-0.01384 -0.42334,-0.0249 -0.138348,-0.0055 -0.273928,-0.0166 -0.406738,-0.0332 -0.132814,-0.01107 -0.249025,-0.02767 -0.348633,-0.0498 l 0,-2.058594 c 0.204751,0.05534 0.423338,0.09961 0.655762,0.132813 0.237953,0.02767 0.478675,0.04151 0.722168,0.0415 0.747066,2e-6 1.361324,-0.09131 1.842773,-0.273925 0.48144,-0.188149 0.863276,-0.44824 1.145508,-0.780274 0.28222,-0.337562 0.481439,-0.738766 0.597656,-1.203613 0.121738,-0.464839 0.196445,-0.97672 0.224121,-1.535645 l -0.10791,0 c -0.110683,0.199225 -0.243496,0.384609 -0.398438,0.556153 -0.1549
53,0.171554 -0.33757,0.320968 -0.547851,0.448242 -0.210292,0.127283 -0.448247,0.226892 -0.713867,0.298828 -0.26563,0.07194 -0.561691,0.107914 -0.888184,0.10791 -0.525719,4e-6 -0.998863,-0.08577 -1.419433,-0.257324 -0.420575,-0.171545 -0.777509,-0.420568 -1.070801,-0.74707 -0.287762,-0.326492 -0.509116,-0.727696 -0.664063,-1.203614 -0.154948,-0.475904 -0.232422,-1.020988 -0.232422,-1.635253 0,-0.65852 0.09131,-1.247875 0.273926,-1.768067 0.18815,-0.520172 0.453775,-0.960113 0.796875,-1.319824 0.343097,-0.365223 0.758136,-0.644682 1.245117,-0.838379 0.49251,-0.1936727 1.043128,-0.2905151 1.651856,-0.2905274 0.597651,1.23e-5 1.15657,0.1079224 1.676758,0.3237304 0.520175,0.210298 0.971184,0.534028 1.353027,0.971192 0.381828,0.437185 0.683423,0.990569 0.904785,1.660156 0.221346,0.669605 0.332023,1.458178 0.332031,2.365722 m -4.216796,-3.262207 c -0.226893,1.1e-5 -0.434412,0.04151 -0.622559,0.124512 -0.188155,0.08302 -0.351403,0.213063 -0.489746,0.390137 -0.132816,0.171559 -0.2379
59,0.392913 -0.31543,0.664062 -0.07194,0.265634 -0.107913,0.581063 -0.10791,0.946289 -3e-6,0.586596 0.124509,1.05144 0.373535,1.394532 0.24902,0.343105 0.625322,0.514654 1.128906,0.514648 0.254553,6e-6 0.486975,-0.0498 0.697266,-0.149414 0.210281,-0.0996 0.390131,-0.229648 0.539551,-0.390137 0.149408,-0.160475 0.262852,-0.340325 0.340332,-0.53955 0.083,-0.199212 0.124505,-0.401197 0.124512,-0.605958 -7e-6,-0.282218 -0.03598,-0.561677 -0.107911,-0.838378 -0.06641,-0.282218 -0.171555,-0.534008 -0.315429,-0.755372 -0.138352,-0.226878 -0.312669,-0.409495 -0.52295,-0.547851 -0.204757,-0.138336 -0.44548,-0.207509 -0.722167,-0.20752"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/2.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/2.png
new file mode 100644
index 0000000..ff9cc57
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/2.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/2.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/2.svg
new file mode 100644
index 0000000..8e94260
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/2.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 19.89546,22.008438 -8.143066,0 0,-1.784668 2.855468,-3.07959 c 0.359697,-0.387364 0.686194,-0.744297 0.979493,-1.0708 0.293289,-0.326492 0.545079,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.373529,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.17431,-0.666821 0.174316,-1.037598 -6e-6,-0.409496 -0.124517,-0.727692 -0.373535,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.261719,0.323731 -0.403974,0.215829 -0.827313,0.522958 -1.270019,0.921386 l -1.394531,-1.651855 c 0.249022,-0.226877 0.509113,-0.442698 0.780273,-0.647461 0.271157,-0.210275 0.569985,-0.395659 0.896484,-0.556152 0.326495,-0.16047 0.686195,-0.2877488 1.079102,-0.3818364 0.3929,-0.099597 0.832841,-0.1494018 1.319824,-0.1494141 0.58105,1.23e-5 1.101231,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860507,0.3901488 1.187012,0.6889648 0.326489,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.893727 0.265625,1.41
9433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/20.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/20.png
new file mode 100644
index 0000000..b28b4aa
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/20.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/20.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/20.svg
new file mode 100644
index 0000000..409ac6e
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/20.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.6378,15.940567 c -9e-6,0.979497 -0.07748,1.853845 -0.232422,2.623047 -0.149422,0.769208 -0.392912,1.422202 -0.730468,1.958984 -0.332039,0.536785 -0.763679,0.94629 -1.294922,1.228516 -0.525722,0.282226 -1.162115,0.42334 -1.90918,0.42334 -0.702803,0 -1.314294,-0.141114 -1.834473,-0.42334 -0.520184,-0.282226 -0.951824,-0.691731 -1.294922,-1.228516 -0.3431,-0.536782 -0.600424,-1.189776 -0.771972,-1.958984 -0.166016,-0.769202 -0.249024,-1.64355 -0.249024,-2.623047 0,-0.979485 0.07471,-1.8566 0.224121,-2.631348 0.154948,-0.77473 0.398437,-1.430491 0.730469,-1.967285 0.33203,-0.536772 0.760903,-0.946277 1.286621,-1.228515 0.525713,-0.2877487 1.162106,-0.4316287 1.90918,-0.431641 0.69726,1.23e-5 1.305984,0.1411254 1.826172,0.42334 0.520175,0.282238 0.954582,0.691743 1.303223,1.228515 0.348624,0.536794 0.608715,1.192555 0.780273,1.967286 0.171541,0.774747 0.257315,1.654629 0.257324,2.639648 m -5.760742,0 c -3e-6,1.383468 0.118975,2.423832 0.356934,3.121094 0.237952,0.6
97268 0.650223,1.0459 1.236816,1.045898 0.575516,2e-6 0.987787,-0.345863 1.236816,-1.037597 0.254552,-0.691729 0.38183,-1.734859 0.381836,-3.129395 -6e-6,-1.38899 -0.127284,-2.43212 -0.381836,-3.129395 -0.249029,-0.702789 -0.6613,-1.054188 -1.236816,-1.054199 -0.293299,1.1e-5 -0.542322,0.08855 -0.74707,0.265625 -0.199223,0.177093 -0.362471,0.439951 -0.489746,0.788574 -0.127282,0.348642 -0.218591,0.785816 -0.273926,1.311524 -0.05534,0.52019 -0.08301,1.126146 -0.08301,1.817871"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/21.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/21.png
new file mode 100644
index 0000000..eda952c
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/21.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/21.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/21.svg
new file mode 100644
index 0000000..7bc03af
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/21.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 22.579206,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141117,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168786,0.157724 -0.257324,0.240723 -0.08855,0.08302 -0.17432,0.157723 -0.257325,0.224121 l -1.394531,1.120605 -1.245117,-1.543945 3.909668,-3.1127931 2.108398,0 0,12.1357421"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/22.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/22.png
new file mode 100644
index 0000000..90b14b0
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/22.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/22.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/22.svg
new file mode 100644
index 0000000..fe086f6
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/22.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.621199,22.008438 -8.143067,0 0,-1.784668 2.855469,-3.07959 c 0.359697,-0.387364 0.686194,-0.744297 0.979492,-1.0708 0.29329,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373535,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437179,10e-6 -0.857751,0.10792 -1.261719,0.323731 -0.403974,0.215829 -0.827314,0.522958 -1.27002,0.921386 l -1.394531,-1.651855 c 0.249023,-0.226877 0.509114,-0.442698 0.780274,-0.647461 0.271157,-0.210275 0.569985,-0.395659 0.896484,-0.556152 0.326495,-0.16047 0.686195,-0.2877488 1.079101,-0.3818364 0.3929,-0.099597 0.832841,-0.1494018 1.319825,-0.1494141 0.581049,1.23e-5 1.101231,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860507,0.3901488 1.187011,0.6889648 0.32649,0.293305 0.575513,0.650239 0.747071,1.070801 0.177075,0.420583 0.265616,0.893727 0.265625,1.419
433 -9e-6,0.47592 -0.08302,0.932463 -0.249024,1.369629 -0.166024,0.431648 -0.392911,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622565,0.830083 -1.004394,1.245117 -0.376309,0.40951 -0.78028,0.827315 -1.211914,1.253418 l -1.460938,1.469238 0,0.116211 4.947266,0 0,2.158203"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/23.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/23.png
new file mode 100644
index 0000000..8b35a74
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/23.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/23.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/23.svg
new file mode 100644
index 0000000..f17ec29
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/23.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.148054,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.207519,1.137207 -0.132821,0.33204 -0.318205,0.625334 -0.556153,0.879883 -0.232429,0.249031 -0.509121,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979486,0.121751 1.721021,0.420579 2.22461,0.896485 0.503572,0.470382 0.755362,1.106775 0.755371,1.909179 -9e-6,0.531253 -0.09685,1.023766 -0.290528,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879882,1.170411 -0.392911,0.332031 -0.890958,0.592122 -1.494141,0.780273 -0.597662,0.182617 -1.303227,0.273926 -2.116699,0.273926 -0.652998,0 -1.267256,-0.05534 -1.842774,-0.166016 -0.575522,-0.105143 -1.112305,-0.268392 -1.610351,-0.489746 l 0,-2.183105 c 0.249022,0.132815 0.51188,0.249025 0.788574,0.348632 0.276691,0.09961 0.553384,0.185387 0.830078,0.257325 0.27669,0.06641 0.547849,0.116212 0.813477,0.149414 0.271155,0.0332 0.525712,0.04981 0.763671,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132812 0.315425,
-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188146,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124512,-0.73877 -7e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.20474 -0.265631,-0.376289 -0.498047,-0.51464 -0.226893,-0.143876 -0.525721,-0.254553 -0.896485,-0.332032 -0.370772,-0.07747 -0.827315,-0.116205 -1.369628,-0.116211 l -0.863282,0 0,-1.801269 0.84668,0 c 0.509111,7e-6 0.93245,-0.04426 1.270019,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124512,-0.672363 -6e-6,-0.431632 -0.135585,-0.769197 -0.406739,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,1e-5 -0.514652,0.02768 -0.747071,0.08301 -0.226891,0.04981 -0.439944,0.116221 -0.63916,0.199218 -0.193687,0.07748 -0.373537,0.166026 -0.53955,0.265625 -0.160484,0.09409 -0.307131,0.188161 -0.439942,0.282227 l -1.294922,-1.7
09961 c 0.232421,-0.171538 0.484212,-0.329253 0.755371,-0.473145 0.276692,-0.143868 0.575519,-0.26838 0.896485,-0.373535 0.320961,-0.1106647 0.666826,-0.1964393 1.037597,-0.2573239 0.370765,-0.06086 0.766435,-0.091296 1.187012,-0.091309 0.597651,1.23e-5 1.139969,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/24.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/24.png
new file mode 100644
index 0000000..6041b02
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/24.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/24.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/24.svg
new file mode 100644
index 0000000..42a5333
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/24.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.803816,19.493301 -1.460938,0 0,2.515137 -2.498535,0 0,-2.515137 -5.013672,0 0,-1.784668 5.154785,-7.8359371 2.357422,0 0,7.6284181 1.460938,0 0,1.992187 m -3.959473,-1.992187 0,-2.058594 c -5e-6,-0.07193 -5e-6,-0.17431 0,-0.307129 0.0055,-0.138339 0.01106,-0.293287 0.0166,-0.464844 0.0055,-0.171541 0.01106,-0.348625 0.0166,-0.53125 0.01106,-0.182609 0.01936,-0.356925 0.0249,-0.522949 0.01106,-0.166007 0.01936,-0.309887 0.0249,-0.43164 0.01106,-0.12727 0.01936,-0.218579 0.0249,-0.273926 l -0.07471,0 c -0.09961,0.232431 -0.213058,0.478687 -0.340332,0.738769 -0.121749,0.2601 -0.262862,0.520191 -0.42334,0.780274 l -2.02539,3.071289 2.755859,0"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/25.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/25.png
new file mode 100644
index 0000000..ecb15e6
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/25.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/25.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/25.svg
new file mode 100644
index 0000000..a8d4672
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/25.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 20.761335,14.255508 c 0.520177,8e-6 1.004389,0.08025 1.452637,0.240723 0.448235,0.160489 0.838372,0.395678 1.17041,0.705566 0.332024,0.309903 0.592114,0.697272 0.780274,1.16211 0.188142,0.459315 0.282218,0.987797 0.282226,1.585449 -8e-6,0.658532 -0.102385,1.250654 -0.307129,1.776367 -0.20476,0.520184 -0.506355,0.962892 -0.904785,1.328125 -0.398444,0.359701 -0.893724,0.636394 -1.48584,0.830078 -0.586594,0.193685 -1.261723,0.290528 -2.02539,0.290528 -0.304366,0 -0.605961,-0.01384 -0.904785,-0.0415 -0.298831,-0.02767 -0.586591,-0.06917 -0.863282,-0.124512 -0.27116,-0.04981 -0.531251,-0.116211 -0.780273,-0.199219 -0.243491,-0.08301 -0.464845,-0.17985 -0.664063,-0.290527 l 0,-2.216309 c 0.193684,0.11068 0.417805,0.215823 0.672364,0.31543 0.254555,0.09408 0.517413,0.177086 0.788574,0.249024 0.27669,0.06641 0.553383,0.121746 0.830078,0.166015 0.276689,0.03874 0.539547,0.05811 0.788574,0.05811 0.741532,2e-6 1.305985,-0.152179 1.69336,-0.456543 0.387364,-0.309893 0.581048
,-0.799639 0.581054,-1.469239 -6e-6,-0.597651 -0.190924,-1.051427 -0.572754,-1.361328 -0.376307,-0.315424 -0.960128,-0.473139 -1.751464,-0.473144 -0.143884,5e-6 -0.298832,0.0083 -0.464844,0.0249 -0.160485,0.01661 -0.320967,0.03874 -0.481446,0.06641 -0.15495,0.02768 -0.304364,0.05811 -0.448242,0.09131 -0.143882,0.02767 -0.268394,0.05811 -0.373535,0.09131 l -1.020996,-0.547852 0.456543,-6.1840821 6.408203,0 0,2.1748051 -4.183594,0 -0.199218,2.382324 c 0.177079,-0.03873 0.381832,-0.07747 0.614257,-0.116211 0.237952,-0.03873 0.542314,-0.0581 0.913086,-0.05811"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/26.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/26.png
new file mode 100644
index 0000000..4b2f560
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/26.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/26.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/26.svg
new file mode 100644
index 0000000..3cf00ec
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/26.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 16.428328,16.853653 c -1e-6,-0.581049 0.03044,-1.159336 0.09131,-1.734863 0.06641,-0.575514 0.17985,-1.126132 0.340332,-1.651856 0.166015,-0.531241 0.387369,-1.023753 0.664063,-1.477539 0.282224,-0.453765 0.636391,-0.846669 1.0625,-1.178711 0.431637,-0.337553 0.946285,-0.600411 1.543945,-0.788574 0.603185,-0.1936727 1.305984,-0.2905151 2.108398,-0.2905274 0.116205,1.23e-5 0.243483,0.00278 0.381836,0.0083 0.13834,0.00555 0.276686,0.013847 0.415039,0.024902 0.143873,0.00555 0.282219,0.016614 0.415039,0.033203 0.132805,0.016614 0.251783,0.035982 0.356934,0.058105 l 0,2.0502924 c -0.210294,-0.04979 -0.434415,-0.08853 -0.672363,-0.116211 -0.232429,-0.03319 -0.467618,-0.04979 -0.705567,-0.0498 -0.747076,1e-5 -1.361333,0.09408 -1.842773,0.282226 -0.48145,0.182627 -0.863285,0.439951 -1.145508,0.771973 -0.28223,0.33204 -0.484215,0.730477 -0.605957,1.195312 -0.116214,0.464852 -0.188154,0.9795 -0.21582,1.543946 l 0.09961,0 c 0.110674,-0.199212 0.243487,-0.384596 0.398438,-0
.556153 0.160478,-0.177076 0.345862,-0.32649 0.556152,-0.448242 0.210282,-0.127271 0.445471,-0.22688 0.705566,-0.298828 0.265621,-0.07193 0.561681,-0.107902 0.888184,-0.10791 0.52571,8e-6 0.998854,0.08578 1.419434,0.257324 0.420565,0.171557 0.774732,0.42058 1.0625,0.74707 0.293286,0.326504 0.517407,0.727708 0.672363,1.203614 0.154939,0.475916 0.232413,1.021 0.232422,1.635254 -9e-6,0.658532 -0.09408,1.247887 -0.282227,1.768066 -0.182625,0.520184 -0.445483,0.962892 -0.788574,1.328125 -0.343106,0.359701 -0.758145,0.636394 -1.245117,0.830078 -0.486985,0.188151 -1.034836,0.282227 -1.643555,0.282227 -0.59766,0 -1.156579,-0.105144 -1.676758,-0.31543 -0.520185,-0.21582 -0.97396,-0.542317 -1.361328,-0.979492 -0.381837,-0.437173 -0.683432,-0.987791 -0.904785,-1.651856 -0.215821,-0.669593 -0.323731,-1.460933 -0.32373,-2.374023 m 4.216796,3.270508 c 0.226883,2e-6 0.431636,-0.0415 0.614258,-0.124512 0.188146,-0.08854 0.348627,-0.218585 0.481446,-0.390137 0.13834,-0.17708 0.243483,-0.3984
34 0.315429,-0.664062 0.07747,-0.265622 0.116205,-0.581051 0.116211,-0.946289 -6e-6,-0.592118 -0.124518,-1.056961 -0.373535,-1.394531 -0.243495,-0.343094 -0.61703,-0.514643 -1.120605,-0.514649 -0.254562,6e-6 -0.486984,0.04981 -0.697266,0.149414 -0.21029,0.09962 -0.390141,0.229661 -0.539551,0.390137 -0.149417,0.160487 -0.265628,0.340337 -0.348633,0.539551 -0.07748,0.199223 -0.116214,0.401209 -0.116211,0.605957 -3e-6,0.28223 0.0332,0.564456 0.09961,0.846679 0.07194,0.276696 0.17708,0.528486 0.315429,0.755371 0.143877,0.221357 0.318193,0.401207 0.52295,0.539551 0.210282,0.138349 0.453771,0.207522 0.730468,0.20752"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/27.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/27.png
new file mode 100644
index 0000000..ecf058e
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/27.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/27.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/27.svg
new file mode 100644
index 0000000..c8d6440
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/27.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 17.51573,22.008438 4.316406,-9.960937 -5.578125,0 0,-2.1582035 8.367188,0 0,1.6103515 -4.424317,10.508789 -2.681152,0"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/28.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/28.png
new file mode 100644
index 0000000..e64efb2
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/28.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/28.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/28.svg
new file mode 100644
index 0000000..5acce93
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/28.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 20.48741,9.7149811 c 0.503575,1.23e-5 0.979486,0.060885 1.427734,0.1826172 0.448236,0.1217567 0.841139,0.3043737 1.178711,0.5478517 0.337557,0.243501 0.605949,0.547862 0.805176,0.913086 0.19921,0.365244 0.298819,0.794118 0.298828,1.286621 -9e-6,0.365243 -0.05535,0.697274 -0.166016,0.996094 -0.110685,0.293302 -0.262866,0.561694 -0.456543,0.805175 -0.193692,0.237963 -0.423347,0.451017 -0.688965,0.639161 -0.265631,0.188157 -0.553392,0.359707 -0.863281,0.514648 0.320957,0.171556 0.63362,0.362473 0.937988,0.572754 0.309889,0.210292 0.583814,0.448247 0.821778,0.713867 0.237947,0.260096 0.428865,0.55339 0.572754,0.879883 0.143871,0.326501 0.215811,0.691735 0.21582,1.095703 -9e-6,0.503583 -0.09962,0.960126 -0.298828,1.369629 -0.199227,0.409506 -0.478687,0.758139 -0.838379,1.045898 -0.359708,0.287761 -0.791348,0.509115 -1.294922,0.664063 -0.498053,0.154948 -1.048671,0.232422 -1.651855,0.232422 -0.652999,0 -1.234053,-0.07471 -1.743164,-0.224121 -0.509117,-0.149414 -0.93799
1,-0.362467 -1.286622,-0.639161 -0.348634,-0.276691 -0.614258,-0.617023 -0.796875,-1.020996 -0.177084,-0.403969 -0.265625,-0.857744 -0.265625,-1.361328 0,-0.415035 0.06087,-0.78857 0.182618,-1.120605 0.121744,-0.332027 0.287759,-0.630855 0.498046,-0.896485 0.210285,-0.265619 0.456542,-0.500808 0.73877,-0.705566 0.282224,-0.204747 0.583819,-0.384597 0.904785,-0.539551 -0.271161,-0.171543 -0.525718,-0.356927 -0.763672,-0.556152 -0.237957,-0.204746 -0.445477,-0.428866 -0.622558,-0.672363 -0.171551,-0.249016 -0.309897,-0.522942 -0.415039,-0.821778 -0.09961,-0.298819 -0.149415,-0.628083 -0.149414,-0.987793 -1e-6,-0.481435 0.09961,-0.902008 0.298828,-1.261718 0.204751,-0.365224 0.478676,-0.669585 0.821777,-0.913086 0.343097,-0.249012 0.738767,-0.434396 1.187012,-0.5561527 0.448238,-0.1217326 0.918615,-0.1826049 1.411133,-0.1826172 m -1.718262,9.0644529 c -3e-6,0.221357 0.03597,0.42611 0.10791,0.614258 0.07194,0.18262 0.17708,0.340334 0.31543,0.473145 0.143876,0.132814 0.32096,0.23
7957 0.53125,0.315429 0.210282,0.07194 0.453771,0.107912 0.730468,0.10791 0.58105,2e-6 1.015457,-0.135577 1.303223,-0.406738 0.287754,-0.27669 0.431634,-0.639157 0.431641,-1.087402 -7e-6,-0.232419 -0.04981,-0.439938 -0.149414,-0.622559 -0.09408,-0.188147 -0.218594,-0.359696 -0.373535,-0.514648 -0.14942,-0.160478 -0.32097,-0.307125 -0.514649,-0.439942 -0.19369,-0.132807 -0.387375,-0.260086 -0.581055,-0.381836 L 20.3878,16.72084 c -0.243494,0.12175 -0.464848,0.254563 -0.664062,0.398438 -0.199223,0.138351 -0.370772,0.293299 -0.514649,0.464844 -0.138349,0.16602 -0.246259,0.348637 -0.32373,0.547851 -0.07748,0.199223 -0.116214,0.415043 -0.116211,0.647461 m 1.70166,-7.188476 c -0.182622,10e-6 -0.354171,0.02768 -0.514648,0.08301 -0.154952,0.05535 -0.290532,0.13559 -0.406739,0.240723 -0.11068,0.105153 -0.199222,0.235199 -0.265625,0.390137 -0.06641,0.154957 -0.09961,0.329274 -0.09961,0.522949 -3e-6,0.232431 0.0332,0.434416 0.09961,0.605957 0.07194,0.166024 0.166012,0.315438 0.282227,0
.448242 0.121741,0.127287 0.260087,0.243498 0.415039,0.348633 0.160477,0.09962 0.32926,0.199226 0.506348,0.298828 0.171544,-0.08853 0.334793,-0.185376 0.489746,-0.290527 0.154942,-0.105135 0.290522,-0.224113 0.406738,-0.356934 0.121739,-0.138338 0.218581,-0.293286 0.290527,-0.464843 0.07193,-0.171541 0.107904,-0.367993 0.10791,-0.589356 -6e-6,-0.193675 -0.03321,-0.367992 -0.09961,-0.522949 -0.06641,-0.154938 -0.15772,-0.284984 -0.273926,-0.390137 -0.116216,-0.105133 -0.254562,-0.185374 -0.415039,-0.240723 -0.160487,-0.05533 -0.334803,-0.083 -0.522949,-0.08301"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/29.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/29.png
new file mode 100644
index 0000000..dbbca1b
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/29.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/29.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/29.svg
new file mode 100644
index 0000000..507dd44
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/29.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.554792,15.052383 c -8e-6,0.581061 -0.03321,1.162116 -0.09961,1.743164 -0.06088,0.575526 -0.174325,1.126144 -0.340332,1.651856 -0.16049,0.525719 -0.381844,1.018232 -0.664063,1.477539 -0.2767,0.453778 -0.630866,0.846681 -1.0625,1.178711 -0.426112,0.332032 -0.94076,0.59489 -1.543945,0.788574 -0.597661,0.188151 -1.300459,0.282227 -2.108398,0.282227 -0.116214,0 -0.243493,-0.0028 -0.381836,-0.0083 -0.138349,-0.0055 -0.279462,-0.01384 -0.42334,-0.0249 -0.138348,-0.0055 -0.273928,-0.0166 -0.406738,-0.0332 -0.132814,-0.01107 -0.249025,-0.02767 -0.348633,-0.0498 l 0,-2.058594 c 0.204751,0.05534 0.423338,0.09961 0.655762,0.132813 0.237953,0.02767 0.478675,0.04151 0.722168,0.0415 0.747066,2e-6 1.361324,-0.09131 1.842773,-0.273925 0.48144,-0.188149 0.863276,-0.44824 1.145508,-0.780274 0.28222,-0.337562 0.481439,-0.738766 0.597656,-1.203613 0.121738,-0.464839 0.196445,-0.97672 0.224121,-1.535645 l -0.10791,0 c -0.110683,0.199225 -0.243496,0.384609 -0.398438,0.556153 -0.1549
53,0.171554 -0.33757,0.320968 -0.547851,0.448242 -0.210292,0.127283 -0.448247,0.226892 -0.713867,0.298828 -0.26563,0.07194 -0.561691,0.107914 -0.888184,0.10791 -0.525719,4e-6 -0.998863,-0.08577 -1.419433,-0.257324 -0.420575,-0.171545 -0.777509,-0.420568 -1.070801,-0.74707 -0.287762,-0.326492 -0.509116,-0.727696 -0.664063,-1.203614 -0.154948,-0.475904 -0.232422,-1.020988 -0.232422,-1.635253 0,-0.65852 0.09131,-1.247875 0.273926,-1.768067 0.18815,-0.520172 0.453775,-0.960113 0.796875,-1.319824 0.343097,-0.365223 0.758136,-0.644682 1.245117,-0.838379 0.49251,-0.1936727 1.043128,-0.2905151 1.651856,-0.2905274 0.597651,1.23e-5 1.15657,0.1079224 1.676758,0.3237304 0.520175,0.210298 0.971184,0.534028 1.353027,0.971192 0.381828,0.437185 0.683423,0.990569 0.904785,1.660156 0.221346,0.669605 0.332023,1.458178 0.332031,2.365722 m -4.216796,-3.262207 c -0.226893,1.1e-5 -0.434412,0.04151 -0.622559,0.124512 -0.188155,0.08302 -0.351403,0.213063 -0.489746,0.390137 -0.132816,0.171559 -0.2379
59,0.392913 -0.31543,0.664062 -0.07194,0.265634 -0.107913,0.581063 -0.10791,0.946289 -3e-6,0.586596 0.124509,1.05144 0.373535,1.394532 0.24902,0.343105 0.625322,0.514654 1.128906,0.514648 0.254553,6e-6 0.486975,-0.0498 0.697266,-0.149414 0.210281,-0.0996 0.390131,-0.229648 0.539551,-0.390137 0.149408,-0.160475 0.262852,-0.340325 0.340332,-0.53955 0.083,-0.199212 0.124505,-0.401197 0.124512,-0.605958 -7e-6,-0.282218 -0.03598,-0.561677 -0.107911,-0.838378 -0.06641,-0.282218 -0.171555,-0.534008 -0.315429,-0.755372 -0.138352,-0.226878 -0.312669,-0.409495 -0.52295,-0.547851 -0.204757,-0.138336 -0.44548,-0.207509 -0.722167,-0.20752"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/3.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/3.png
new file mode 100644
index 0000000..4febe43
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/3.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/3.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/3.svg
new file mode 100644
index 0000000..5e87e1f
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/3.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;text-anchor:start;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 19.422316,12.587051 c -9e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.23243,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315437,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503572,0.470382 0.755362,1.106775 0.755371,1.909179 -9e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.392911,0.332031 -0.890957,0.592122 -1.494141,0.780273 -0.597661,0.182617 -1.303227,0.273926 -2.116699,0.273926 -0.652998,0 -1.267255,-0.05534 -1.842773,-0.166016 -0.575523,-0.105143 -1.112306,-0.268392 -1.610352,-0.489746 l 0,-2.183105 c 0.249023,0.132815 0.511881,0.249025 0.788574,0.348632 0.276692,0.09961 0.553384,0.185387 0.830079,0.257325 0.27669,0.06641 0.547848,0.116212 0.813476,0.149414 0.271156,0.0332 0.525713,0.04981 0.763672,0.0498 0.475907,2e-6 0.871577,-0.04427 1.187012,-0.132812 0.315424,-
0.08854 0.567214,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320957,-0.351397 0.398437,-0.572754 0.083,-0.226885 0.124506,-0.473141 0.124512,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.265631,-0.376297 -0.498047,-0.514648 -0.226893,-0.143876 -0.525721,-0.254553 -0.896484,-0.332032 -0.370773,-0.07747 -0.827315,-0.116205 -1.369629,-0.116211 l -0.863281,0 0,-1.801269 0.846679,0 c 0.509111,7e-6 0.932451,-0.04426 1.27002,-0.132813 0.33756,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.43164,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124512,-0.672363 -6e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.68897,-0.365224 -1.27002,-0.365234 -0.265629,10e-6 -0.514652,0.02768 -0.74707,0.08301 -0.226891,0.04981 -0.439944,0.116221 -0.63916,0.199218 -0.193688,0.07748 -0.373538,0.166026 -0.539551,0.265625 -0.160484,0.09409 -0.307131,0.188161 -0.439941,0.282227 l -1.294922,-1.70
9961 c 0.232421,-0.171538 0.484211,-0.329253 0.755371,-0.473145 0.276691,-0.143868 0.575519,-0.26838 0.896484,-0.373535 0.320961,-0.1106647 0.666827,-0.1964393 1.037598,-0.2573239 0.370765,-0.06086 0.766435,-0.091296 1.187012,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492506,0.1272911 0.913079,0.3154421 1.261718,0.5644531 0.348626,0.243501 0.617017,0.545096 0.805176,0.904786 0.193677,0.354177 0.290519,0.760914 0.290528,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/30.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/30.png
new file mode 100644
index 0000000..f4ffb14
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/30.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/30.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/30.svg
new file mode 100644
index 0000000..434e663
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/30.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.6378,15.940567 c -9e-6,0.979497 -0.07748,1.853845 -0.232422,2.623047 -0.149422,0.769208 -0.392912,1.422202 -0.730468,1.958984 -0.332039,0.536785 -0.763679,0.94629 -1.294922,1.228516 -0.525722,0.282226 -1.162115,0.42334 -1.90918,0.42334 -0.702803,0 -1.314294,-0.141114 -1.834473,-0.42334 -0.520184,-0.282226 -0.951824,-0.691731 -1.294922,-1.228516 -0.3431,-0.536782 -0.600424,-1.189776 -0.771972,-1.958984 -0.166016,-0.769202 -0.249024,-1.64355 -0.249024,-2.623047 0,-0.979485 0.07471,-1.8566 0.224121,-2.631348 0.154948,-0.77473 0.398437,-1.430491 0.730469,-1.967285 0.33203,-0.536772 0.760903,-0.946277 1.286621,-1.228515 0.525713,-0.2877487 1.162106,-0.4316287 1.90918,-0.431641 0.69726,1.23e-5 1.305984,0.1411254 1.826172,0.42334 0.520175,0.282238 0.954582,0.691743 1.303223,1.228515 0.348624,0.536794 0.608715,1.192555 0.780273,1.967286 0.171541,0.774747 0.257315,1.654629 0.257324,2.639648 m -5.760742,0 c -3e-6,1.383468 0.118975,2.423832 0.356934,3.121094 0.237952,0.6
97268 0.650223,1.0459 1.236816,1.045898 0.575516,2e-6 0.987787,-0.345863 1.236816,-1.037597 0.254552,-0.691729 0.38183,-1.734859 0.381836,-3.129395 -6e-6,-1.38899 -0.127284,-2.43212 -0.381836,-3.129395 -0.249029,-0.702789 -0.6613,-1.054188 -1.236816,-1.054199 -0.293299,1.1e-5 -0.542322,0.08855 -0.74707,0.265625 -0.199223,0.177093 -0.362471,0.439951 -0.489746,0.788574 -0.127282,0.348642 -0.218591,0.785816 -0.273926,1.311524 -0.05534,0.52019 -0.08301,1.126146 -0.08301,1.817871"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/31.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/31.png
new file mode 100644
index 0000000..0b29e87
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/31.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/31.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/31.svg
new file mode 100644
index 0000000..08c3f2d
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/31.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 22.579206,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141117,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168786,0.157724 -0.257324,0.240723 -0.08855,0.08302 -0.17432,0.157723 -0.257325,0.224121 l -1.394531,1.120605 -1.245117,-1.543945 3.909668,-3.1127931 2.108398,0 0,12.1357421"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/32.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/32.png
new file mode 100644
index 0000000..a4740a3
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/32.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/32.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/32.svg
new file mode 100644
index 0000000..aa099c3
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/32.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.621199,22.008438 -8.143067,0 0,-1.784668 2.855469,-3.07959 c 0.359697,-0.387364 0.686194,-0.744297 0.979492,-1.0708 0.29329,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373535,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437179,10e-6 -0.857751,0.10792 -1.261719,0.323731 -0.403974,0.215829 -0.827314,0.522958 -1.27002,0.921386 l -1.394531,-1.651855 c 0.249023,-0.226877 0.509114,-0.442698 0.780274,-0.647461 0.271157,-0.210275 0.569985,-0.395659 0.896484,-0.556152 0.326495,-0.16047 0.686195,-0.2877488 1.079101,-0.3818364 0.3929,-0.099597 0.832841,-0.1494018 1.319825,-0.1494141 0.581049,1.23e-5 1.101231,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860507,0.3901488 1.187011,0.6889648 0.32649,0.293305 0.575513,0.650239 0.747071,1.070801 0.177075,0.420583 0.265616,0.893727 0.265625,1.419
433 -9e-6,0.47592 -0.08302,0.932463 -0.249024,1.369629 -0.166024,0.431648 -0.392911,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622565,0.830083 -1.004394,1.245117 -0.376309,0.40951 -0.78028,0.827315 -1.211914,1.253418 l -1.460938,1.469238 0,0.116211 4.947266,0 0,2.158203"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/33.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/33.png
new file mode 100644
index 0000000..f23ccea
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/33.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/33.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/33.svg
new file mode 100644
index 0000000..fce979c
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/33.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.148054,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.207519,1.137207 -0.132821,0.33204 -0.318205,0.625334 -0.556153,0.879883 -0.232429,0.249031 -0.509121,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979486,0.121751 1.721021,0.420579 2.22461,0.896485 0.503572,0.470382 0.755362,1.106775 0.755371,1.909179 -9e-6,0.531253 -0.09685,1.023766 -0.290528,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879882,1.170411 -0.392911,0.332031 -0.890958,0.592122 -1.494141,0.780273 -0.597662,0.182617 -1.303227,0.273926 -2.116699,0.273926 -0.652998,0 -1.267256,-0.05534 -1.842774,-0.166016 -0.575522,-0.105143 -1.112305,-0.268392 -1.610351,-0.489746 l 0,-2.183105 c 0.249022,0.132815 0.51188,0.249025 0.788574,0.348632 0.276691,0.09961 0.553384,0.185387 0.830078,0.257325 0.27669,0.06641 0.547849,0.116212 0.813477,0.149414 0.271155,0.0332 0.525712,0.04981 0.763671,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132812 0.315425,
-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188146,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124512,-0.73877 -7e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.20474 -0.265631,-0.376289 -0.498047,-0.51464 -0.226893,-0.143876 -0.525721,-0.254553 -0.896485,-0.332032 -0.370772,-0.07747 -0.827315,-0.116205 -1.369628,-0.116211 l -0.863282,0 0,-1.801269 0.84668,0 c 0.509111,7e-6 0.93245,-0.04426 1.270019,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124512,-0.672363 -6e-6,-0.431632 -0.135585,-0.769197 -0.406739,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,1e-5 -0.514652,0.02768 -0.747071,0.08301 -0.226891,0.04981 -0.439944,0.116221 -0.63916,0.199218 -0.193687,0.07748 -0.373537,0.166026 -0.53955,0.265625 -0.160484,0.09409 -0.307131,0.188161 -0.439942,0.282227 l -1.294922,-1.7
09961 c 0.232421,-0.171538 0.484212,-0.329253 0.755371,-0.473145 0.276692,-0.143868 0.575519,-0.26838 0.896485,-0.373535 0.320961,-0.1106647 0.666826,-0.1964393 1.037597,-0.2573239 0.370765,-0.06086 0.766435,-0.091296 1.187012,-0.091309 0.597651,1.23e-5 1.139969,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/34.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/34.png
new file mode 100644
index 0000000..7e2ab31
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/34.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/34.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/34.svg
new file mode 100644
index 0000000..c67f8ec
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/34.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.803816,19.493301 -1.460938,0 0,2.515137 -2.498535,0 0,-2.515137 -5.013672,0 0,-1.784668 5.154785,-7.8359371 2.357422,0 0,7.6284181 1.460938,0 0,1.992187 m -3.959473,-1.992187 0,-2.058594 c -5e-6,-0.07193 -5e-6,-0.17431 0,-0.307129 0.0055,-0.138339 0.01106,-0.293287 0.0166,-0.464844 0.0055,-0.171541 0.01106,-0.348625 0.0166,-0.53125 0.01106,-0.182609 0.01936,-0.356925 0.0249,-0.522949 0.01106,-0.166007 0.01936,-0.309887 0.0249,-0.43164 0.01106,-0.12727 0.01936,-0.218579 0.0249,-0.273926 l -0.07471,0 c -0.09961,0.232431 -0.213058,0.478687 -0.340332,0.738769 -0.121749,0.2601 -0.262862,0.520191 -0.42334,0.780274 l -2.02539,3.071289 2.755859,0"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/35.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/35.png
new file mode 100644
index 0000000..02118e3
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/35.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/35.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/35.svg
new file mode 100644
index 0000000..da7780a
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/35.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 20.761335,14.255508 c 0.520177,8e-6 1.004389,0.08025 1.452637,0.240723 0.448235,0.160489 0.838372,0.395678 1.17041,0.705566 0.332024,0.309903 0.592114,0.697272 0.780274,1.16211 0.188142,0.459315 0.282218,0.987797 0.282226,1.585449 -8e-6,0.658532 -0.102385,1.250654 -0.307129,1.776367 -0.20476,0.520184 -0.506355,0.962892 -0.904785,1.328125 -0.398444,0.359701 -0.893724,0.636394 -1.48584,0.830078 -0.586594,0.193685 -1.261723,0.290528 -2.02539,0.290528 -0.304366,0 -0.605961,-0.01384 -0.904785,-0.0415 -0.298831,-0.02767 -0.586591,-0.06917 -0.863282,-0.124512 -0.27116,-0.04981 -0.531251,-0.116211 -0.780273,-0.199219 -0.243491,-0.08301 -0.464845,-0.17985 -0.664063,-0.290527 l 0,-2.216309 c 0.193684,0.11068 0.417805,0.215823 0.672364,0.31543 0.254555,0.09408 0.517413,0.177086 0.788574,0.249024 0.27669,0.06641 0.553383,0.121746 0.830078,0.166015 0.276689,0.03874 0.539547,0.05811 0.788574,0.05811 0.741532,2e-6 1.305985,-0.152179 1.69336,-0.456543 0.387364,-0.309893 0.581048
,-0.799639 0.581054,-1.469239 -6e-6,-0.597651 -0.190924,-1.051427 -0.572754,-1.361328 -0.376307,-0.315424 -0.960128,-0.473139 -1.751464,-0.473144 -0.143884,5e-6 -0.298832,0.0083 -0.464844,0.0249 -0.160485,0.01661 -0.320967,0.03874 -0.481446,0.06641 -0.15495,0.02768 -0.304364,0.05811 -0.448242,0.09131 -0.143882,0.02767 -0.268394,0.05811 -0.373535,0.09131 l -1.020996,-0.547852 0.456543,-6.1840821 6.408203,0 0,2.1748051 -4.183594,0 -0.199218,2.382324 c 0.177079,-0.03873 0.381832,-0.07747 0.614257,-0.116211 0.237952,-0.03873 0.542314,-0.0581 0.913086,-0.05811"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/36.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/36.png
new file mode 100644
index 0000000..30f4fdf
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/36.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/36.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/36.svg
new file mode 100644
index 0000000..348549a
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/36.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 16.428328,16.853653 c -1e-6,-0.581049 0.03044,-1.159336 0.09131,-1.734863 0.06641,-0.575514 0.17985,-1.126132 0.340332,-1.651856 0.166015,-0.531241 0.387369,-1.023753 0.664063,-1.477539 0.282224,-0.453765 0.636391,-0.846669 1.0625,-1.178711 0.431637,-0.337553 0.946285,-0.600411 1.543945,-0.788574 0.603185,-0.1936727 1.305984,-0.2905151 2.108398,-0.2905274 0.116205,1.23e-5 0.243483,0.00278 0.381836,0.0083 0.13834,0.00555 0.276686,0.013847 0.415039,0.024902 0.143873,0.00555 0.282219,0.016614 0.415039,0.033203 0.132805,0.016614 0.251783,0.035982 0.356934,0.058105 l 0,2.0502924 c -0.210294,-0.04979 -0.434415,-0.08853 -0.672363,-0.116211 -0.232429,-0.03319 -0.467618,-0.04979 -0.705567,-0.0498 -0.747076,1e-5 -1.361333,0.09408 -1.842773,0.282226 -0.48145,0.182627 -0.863285,0.439951 -1.145508,0.771973 -0.28223,0.33204 -0.484215,0.730477 -0.605957,1.195312 -0.116214,0.464852 -0.188154,0.9795 -0.21582,1.543946 l 0.09961,0 c 0.110674,-0.199212 0.243487,-0.384596 0.398438,-0
.556153 0.160478,-0.177076 0.345862,-0.32649 0.556152,-0.448242 0.210282,-0.127271 0.445471,-0.22688 0.705566,-0.298828 0.265621,-0.07193 0.561681,-0.107902 0.888184,-0.10791 0.52571,8e-6 0.998854,0.08578 1.419434,0.257324 0.420565,0.171557 0.774732,0.42058 1.0625,0.74707 0.293286,0.326504 0.517407,0.727708 0.672363,1.203614 0.154939,0.475916 0.232413,1.021 0.232422,1.635254 -9e-6,0.658532 -0.09408,1.247887 -0.282227,1.768066 -0.182625,0.520184 -0.445483,0.962892 -0.788574,1.328125 -0.343106,0.359701 -0.758145,0.636394 -1.245117,0.830078 -0.486985,0.188151 -1.034836,0.282227 -1.643555,0.282227 -0.59766,0 -1.156579,-0.105144 -1.676758,-0.31543 -0.520185,-0.21582 -0.97396,-0.542317 -1.361328,-0.979492 -0.381837,-0.437173 -0.683432,-0.987791 -0.904785,-1.651856 -0.215821,-0.669593 -0.323731,-1.460933 -0.32373,-2.374023 m 4.216796,3.270508 c 0.226883,2e-6 0.431636,-0.0415 0.614258,-0.124512 0.188146,-0.08854 0.348627,-0.218585 0.481446,-0.390137 0.13834,-0.17708 0.243483,-0.3984
34 0.315429,-0.664062 0.07747,-0.265622 0.116205,-0.581051 0.116211,-0.946289 -6e-6,-0.592118 -0.124518,-1.056961 -0.373535,-1.394531 -0.243495,-0.343094 -0.61703,-0.514643 -1.120605,-0.514649 -0.254562,6e-6 -0.486984,0.04981 -0.697266,0.149414 -0.21029,0.09962 -0.390141,0.229661 -0.539551,0.390137 -0.149417,0.160487 -0.265628,0.340337 -0.348633,0.539551 -0.07748,0.199223 -0.116214,0.401209 -0.116211,0.605957 -3e-6,0.28223 0.0332,0.564456 0.09961,0.846679 0.07194,0.276696 0.17708,0.528486 0.315429,0.755371 0.143877,0.221357 0.318193,0.401207 0.52295,0.539551 0.210282,0.138349 0.453771,0.207522 0.730468,0.20752"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/37.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/37.png
new file mode 100644
index 0000000..6174706
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/37.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/37.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/37.svg
new file mode 100644
index 0000000..7bc04d9
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/37.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 17.51573,22.008438 4.316406,-9.960937 -5.578125,0 0,-2.1582035 8.367188,0 0,1.6103515 -4.424317,10.508789 -2.681152,0"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/38.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/38.png
new file mode 100644
index 0000000..161661d
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/38.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/38.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/38.svg
new file mode 100644
index 0000000..ec2ad98
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/38.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 20.48741,9.7149811 c 0.503575,1.23e-5 0.979486,0.060885 1.427734,0.1826172 0.448236,0.1217567 0.841139,0.3043737 1.178711,0.5478517 0.337557,0.243501 0.605949,0.547862 0.805176,0.913086 0.19921,0.365244 0.298819,0.794118 0.298828,1.286621 -9e-6,0.365243 -0.05535,0.697274 -0.166016,0.996094 -0.110685,0.293302 -0.262866,0.561694 -0.456543,0.805175 -0.193692,0.237963 -0.423347,0.451017 -0.688965,0.639161 -0.265631,0.188157 -0.553392,0.359707 -0.863281,0.514648 0.320957,0.171556 0.63362,0.362473 0.937988,0.572754 0.309889,0.210292 0.583814,0.448247 0.821778,0.713867 0.237947,0.260096 0.428865,0.55339 0.572754,0.879883 0.143871,0.326501 0.215811,0.691735 0.21582,1.095703 -9e-6,0.503583 -0.09962,0.960126 -0.298828,1.369629 -0.199227,0.409506 -0.478687,0.758139 -0.838379,1.045898 -0.359708,0.287761 -0.791348,0.509115 -1.294922,0.664063 -0.498053,0.154948 -1.048671,0.232422 -1.651855,0.232422 -0.652999,0 -1.234053,-0.07471 -1.743164,-0.224121 -0.509117,-0.149414 -0.93799
1,-0.362467 -1.286622,-0.639161 -0.348634,-0.276691 -0.614258,-0.617023 -0.796875,-1.020996 -0.177084,-0.403969 -0.265625,-0.857744 -0.265625,-1.361328 0,-0.415035 0.06087,-0.78857 0.182618,-1.120605 0.121744,-0.332027 0.287759,-0.630855 0.498046,-0.896485 0.210285,-0.265619 0.456542,-0.500808 0.73877,-0.705566 0.282224,-0.204747 0.583819,-0.384597 0.904785,-0.539551 -0.271161,-0.171543 -0.525718,-0.356927 -0.763672,-0.556152 -0.237957,-0.204746 -0.445477,-0.428866 -0.622558,-0.672363 -0.171551,-0.249016 -0.309897,-0.522942 -0.415039,-0.821778 -0.09961,-0.298819 -0.149415,-0.628083 -0.149414,-0.987793 -1e-6,-0.481435 0.09961,-0.902008 0.298828,-1.261718 0.204751,-0.365224 0.478676,-0.669585 0.821777,-0.913086 0.343097,-0.249012 0.738767,-0.434396 1.187012,-0.5561527 0.448238,-0.1217326 0.918615,-0.1826049 1.411133,-0.1826172 m -1.718262,9.0644529 c -3e-6,0.221357 0.03597,0.42611 0.10791,0.614258 0.07194,0.18262 0.17708,0.340334 0.31543,0.473145 0.143876,0.132814 0.32096,0.23
7957 0.53125,0.315429 0.210282,0.07194 0.453771,0.107912 0.730468,0.10791 0.58105,2e-6 1.015457,-0.135577 1.303223,-0.406738 0.287754,-0.27669 0.431634,-0.639157 0.431641,-1.087402 -7e-6,-0.232419 -0.04981,-0.439938 -0.149414,-0.622559 -0.09408,-0.188147 -0.218594,-0.359696 -0.373535,-0.514648 -0.14942,-0.160478 -0.32097,-0.307125 -0.514649,-0.439942 -0.19369,-0.132807 -0.387375,-0.260086 -0.581055,-0.381836 L 20.3878,16.72084 c -0.243494,0.12175 -0.464848,0.254563 -0.664062,0.398438 -0.199223,0.138351 -0.370772,0.293299 -0.514649,0.464844 -0.138349,0.16602 -0.246259,0.348637 -0.32373,0.547851 -0.07748,0.199223 -0.116214,0.415043 -0.116211,0.647461 m 1.70166,-7.188476 c -0.182622,10e-6 -0.354171,0.02768 -0.514648,0.08301 -0.154952,0.05535 -0.290532,0.13559 -0.406739,0.240723 -0.11068,0.105153 -0.199222,0.235199 -0.265625,0.390137 -0.06641,0.154957 -0.09961,0.329274 -0.09961,0.522949 -3e-6,0.232431 0.0332,0.434416 0.09961,0.605957 0.07194,0.166024 0.166012,0.315438 0.282227,0
.448242 0.121741,0.127287 0.260087,0.243498 0.415039,0.348633 0.160477,0.09962 0.32926,0.199226 0.506348,0.298828 0.171544,-0.08853 0.334793,-0.185376 0.489746,-0.290527 0.154942,-0.105135 0.290522,-0.224113 0.406738,-0.356934 0.121739,-0.138338 0.218581,-0.293286 0.290527,-0.464843 0.07193,-0.171541 0.107904,-0.367993 0.10791,-0.589356 -6e-6,-0.193675 -0.03321,-0.367992 -0.09961,-0.522949 -0.06641,-0.154938 -0.15772,-0.284984 -0.273926,-0.390137 -0.116216,-0.105133 -0.254562,-0.185374 -0.415039,-0.240723 -0.160487,-0.05533 -0.334803,-0.083 -0.522949,-0.08301"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/39.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/39.png
new file mode 100644
index 0000000..2d46b24
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/39.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/39.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/39.svg
new file mode 100644
index 0000000..664ffdd
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/39.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.554792,15.052383 c -8e-6,0.581061 -0.03321,1.162116 -0.09961,1.743164 -0.06088,0.575526 -0.174325,1.126144 -0.340332,1.651856 -0.16049,0.525719 -0.381844,1.018232 -0.664063,1.477539 -0.2767,0.453778 -0.630866,0.846681 -1.0625,1.178711 -0.426112,0.332032 -0.94076,0.59489 -1.543945,0.788574 -0.597661,0.188151 -1.300459,0.282227 -2.108398,0.282227 -0.116214,0 -0.243493,-0.0028 -0.381836,-0.0083 -0.138349,-0.0055 -0.279462,-0.01384 -0.42334,-0.0249 -0.138348,-0.0055 -0.273928,-0.0166 -0.406738,-0.0332 -0.132814,-0.01107 -0.249025,-0.02767 -0.348633,-0.0498 l 0,-2.058594 c 0.204751,0.05534 0.423338,0.09961 0.655762,0.132813 0.237953,0.02767 0.478675,0.04151 0.722168,0.0415 0.747066,2e-6 1.361324,-0.09131 1.842773,-0.273925 0.48144,-0.188149 0.863276,-0.44824 1.145508,-0.780274 0.28222,-0.337562 0.481439,-0.738766 0.597656,-1.203613 0.121738,-0.464839 0.196445,-0.97672 0.224121,-1.535645 l -0.10791,0 c -0.110683,0.199225 -0.243496,0.384609 -0.398438,0.556153 -0.1549
53,0.171554 -0.33757,0.320968 -0.547851,0.448242 -0.210292,0.127283 -0.448247,0.226892 -0.713867,0.298828 -0.26563,0.07194 -0.561691,0.107914 -0.888184,0.10791 -0.525719,4e-6 -0.998863,-0.08577 -1.419433,-0.257324 -0.420575,-0.171545 -0.777509,-0.420568 -1.070801,-0.74707 -0.287762,-0.326492 -0.509116,-0.727696 -0.664063,-1.203614 -0.154948,-0.475904 -0.232422,-1.020988 -0.232422,-1.635253 0,-0.65852 0.09131,-1.247875 0.273926,-1.768067 0.18815,-0.520172 0.453775,-0.960113 0.796875,-1.319824 0.343097,-0.365223 0.758136,-0.644682 1.245117,-0.838379 0.49251,-0.1936727 1.043128,-0.2905151 1.651856,-0.2905274 0.597651,1.23e-5 1.15657,0.1079224 1.676758,0.3237304 0.520175,0.210298 0.971184,0.534028 1.353027,0.971192 0.381828,0.437185 0.683423,0.990569 0.904785,1.660156 0.221346,0.669605 0.332023,1.458178 0.332031,2.365722 m -4.216796,-3.262207 c -0.226893,1.1e-5 -0.434412,0.04151 -0.622559,0.124512 -0.188155,0.08302 -0.351403,0.213063 -0.489746,0.390137 -0.132816,0.171559 -0.2379
59,0.392913 -0.31543,0.664062 -0.07194,0.265634 -0.107913,0.581063 -0.10791,0.946289 -3e-6,0.586596 0.124509,1.05144 0.373535,1.394532 0.24902,0.343105 0.625322,0.514654 1.128906,0.514648 0.254553,6e-6 0.486975,-0.0498 0.697266,-0.149414 0.210281,-0.0996 0.390131,-0.229648 0.539551,-0.390137 0.149408,-0.160475 0.262852,-0.340325 0.340332,-0.53955 0.083,-0.199212 0.124505,-0.401197 0.124512,-0.605958 -7e-6,-0.282218 -0.03598,-0.561677 -0.107911,-0.838378 -0.06641,-0.282218 -0.171555,-0.534008 -0.315429,-0.755372 -0.138352,-0.226878 -0.312669,-0.409495 -0.52295,-0.547851 -0.204757,-0.138336 -0.44548,-0.207509 -0.722167,-0.20752"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/4.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/4.png
new file mode 100644
index 0000000..9b9dd88
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/4.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/4.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/4.svg
new file mode 100644
index 0000000..bc06c73
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/4.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;text-anchor:start;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 20.078077,19.493301 -1.460937,0 0,2.515137 -2.498535,0 0,-2.515137 -5.013672,0 0,-1.784668 5.154785,-7.8359371 2.357422,0 0,7.6284181 1.460937,0 0,1.992187 m -3.959472,-1.992187 0,-2.058594 c -5e-6,-0.07193 -5e-6,-0.17431 0,-0.307129 0.0055,-0.138339 0.01106,-0.293287 0.0166,-0.464844 0.0055,-0.171541 0.01106,-0.348625 0.0166,-0.53125 0.01106,-0.182609 0.01936,-0.356925 0.0249,-0.522949 0.01106,-0.166007 0.01936,-0.309887 0.0249,-0.43164 0.01106,-0.12727 0.01936,-0.218579 0.0249,-0.273926 l -0.07471,0 c -0.09962,0.232431 -0.213058,0.478687 -0.340332,0.738769 -0.12175,0.2601 -0.262863,0.520191 -0.42334,0.780274 l -2.025391,3.071289 2.75586,0"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/40.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/40.png
new file mode 100644
index 0000000..fe2a68f
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/40.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/40.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/40.svg
new file mode 100644
index 0000000..5a94d1b
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/40.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.440535,19.493301 -1.460938,0 0,2.515137 -2.498535,0 0,-2.515137 -5.0136719,0 0,-1.784668 5.1547849,-7.8359371 2.357422,0 0,7.6284181 1.460938,0 0,1.992187 m -3.959473,-1.992187 0,-2.058594 c -5e-6,-0.07193 -5e-6,-0.17431 0,-0.307129 0.0055,-0.138339 0.01106,-0.293287 0.0166,-0.464844 0.0055,-0.171541 0.01106,-0.348625 0.0166,-0.53125 0.01106,-0.182609 0.01936,-0.356925 0.0249,-0.522949 0.01106,-0.166007 0.01936,-0.309887 0.0249,-0.43164 0.01106,-0.12727 0.01936,-0.218579 0.0249,-0.273926 l -0.07471,0 c -0.09961,0.232431 -0.213058,0.478687 -0.340332,0.738769 -0.121749,0.2601 -0.262863,0.520191 -0.42334,0.780274 l -2.0253904,3.071289 2.7558594,0"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.6378,15.940567 c -9e-6,0.979497 -0.07748,1.853845 -0.232422,2.623047 -0.149422,0.769208 -0.392912,1.422202 -0.730468,1.958984 -0.332039,0.536785 -0.763679,0.94629 -1.294922,1.228516 -0.525722,0.282226 -1.162115,0.42334 -1.90918,0.42334 -0.702803,0 -1.314294,-0.141114 -1.834473,-0.42334 -0.520184,-0.282226 -0.951824,-0.691731 -1.294922,-1.228516 -0.3431,-0.536782 -0.600424,-1.189776 -0.771972,-1.958984 -0.166016,-0.769202 -0.249024,-1.64355 -0.249024,-2.623047 0,-0.979485 0.07471,-1.8566 0.224121,-2.631348 0.154948,-0.77473 0.398437,-1.430491 0.730469,-1.967285 0.33203,-0.536772 0.760903,-0.946277 1.286621,-1.228515 0.525713,-0.2877487 1.162106,-0.4316287 1.90918,-0.431641 0.69726,1.23e-5 1.305984,0.1411254 1.826172,0.42334 0.520175,0.282238 0.954582,0.691743 1.303223,1.228515 0.348624,0.536794 0.608715,1.192555 0.780273,1.967286 0.171541,0.774747 0.257315,1.654629 0.257324,2.639648 m -5.760742,0 c -3e-6,1.383468 0.118975,2.423832 0.356934,3.121094 0.237952,0.6
97268 0.650223,1.0459 1.236816,1.045898 0.575516,2e-6 0.987787,-0.345863 1.236816,-1.037597 0.254552,-0.691729 0.38183,-1.734859 0.381836,-3.129395 -6e-6,-1.38899 -0.127284,-2.43212 -0.381836,-3.129395 -0.249029,-0.702789 -0.6613,-1.054188 -1.236816,-1.054199 -0.293299,1.1e-5 -0.542322,0.08855 -0.74707,0.265625 -0.199223,0.177093 -0.362471,0.439951 -0.489746,0.788574 -0.127282,0.348642 -0.218591,0.785816 -0.273926,1.311524 -0.05534,0.52019 -0.08301,1.126146 -0.08301,1.817871"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/5.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/5.png
new file mode 100644
index 0000000..f239fb6
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/5.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/5.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/5.svg
new file mode 100644
index 0000000..82fb03d
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/5.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;text-anchor:start;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 16.035597,14.255508 c 0.520177,8e-6 1.004388,0.08025 1.452637,0.240723 0.448235,0.160489 0.838371,0.395678 1.17041,0.705566 0.332023,0.309903 0.592114,0.697272 0.780273,1.16211 0.188143,0.459315 0.282218,0.987797 0.282227,1.585449 -9e-6,0.658532 -0.102385,1.250654 -0.307129,1.776367 -0.204761,0.520184 -0.506356,0.962892 -0.904785,1.328125 -0.398445,0.359701 -0.893724,0.636394 -1.48584,0.830078 -0.586594,0.193685 -1.261724,0.290528 -2.025391,0.290528 -0.304365,0 -0.60596,-0.01384 -0.904785,-0.0415 -0.298831,-0.02767 -0.586591,-0.06917 -0.863281,-0.124512 -0.271161,-0.04981 -0.531252,-0.116211 -0.780274,-0.199219 -0.24349,-0.08301 -0.464844,-0.17985 -0.664062,-0.290527 l 0,-2.216309 c 0.193684,0.11068 0.417805,0.215823 0.672363,0.31543 0.254556,0.09408 0.517414,0.177086 0.788574,0.249024 0.276691,0.06641 0.553383,0.121746 0.830078,0.166015 0.27669,0.03874 0.539548,0.05811 0.788575,0.05811 0.741532,2e-6 1.305984,-0.152179 1.693359,-0.456543 0.387364,-0.309893 0.5810
49,-0.799639 0.581055,-1.469239 -6e-6,-0.597651 -0.190924,-1.051427 -0.572754,-1.361328 -0.376307,-0.315424 -0.960128,-0.473139 -1.751465,-0.473144 -0.143884,5e-6 -0.298832,0.0083 -0.464844,0.0249 -0.160485,0.01661 -0.320966,0.03874 -0.481445,0.06641 -0.154951,0.02768 -0.304365,0.05811 -0.448242,0.09131 -0.143883,0.02767 -0.268394,0.05811 -0.373535,0.09131 l -1.020996,-0.547852 0.456542,-6.1840821 6.408204,0 0,2.1748051 -4.183594,0 -0.199219,2.382324 c 0.17708,-0.03873 0.381832,-0.07747 0.614258,-0.116211 0.237951,-0.03873 0.542313,-0.0581 0.913086,-0.05811"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/6.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/6.png
new file mode 100644
index 0000000..18866e6
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/6.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/6.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/6.svg
new file mode 100644
index 0000000..e2f62af
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/6.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;text-anchor:start;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 11.702589,16.853653 c -10e-7,-0.581049 0.03044,-1.159336 0.09131,-1.734863 0.0664,-0.575514 0.179849,-1.126132 0.340332,-1.651856 0.166014,-0.531241 0.387368,-1.023753 0.664062,-1.477539 0.282225,-0.453765 0.636391,-0.846669 1.0625,-1.178711 0.431638,-0.337553 0.946285,-0.600411 1.543945,-0.788574 0.603186,-0.1936727 1.305984,-0.2905151 2.108399,-0.2905274 0.116204,1.23e-5 0.243483,0.00278 0.381836,0.0083 0.138339,0.00555 0.276685,0.013847 0.415039,0.024902 0.143873,0.00555 0.282219,0.016614 0.415039,0.033203 0.132805,0.016614 0.251782,0.035982 0.356934,0.058105 l 0,2.0502924 c -0.210295,-0.04979 -0.434416,-0.08853 -0.672364,-0.116211 -0.232429,-0.03319 -0.467617,-0.04979 -0.705566,-0.0498 -0.747076,1e-5 -1.361334,0.09408 -1.842774,0.282226 -0.481449,0.182627 -0.863285,0.439951 -1.145507,0.771973 -0.28223,0.33204 -0.484216,0.730477 -0.605957,1.195312 -0.116214,0.464852 -0.188154,0.9795 -0.215821,1.543946 l 0.09961,0 c 0.110674,-0.199212 0.243486,-0.384596 0.39843
7,-0.556153 0.160478,-0.177076 0.345862,-0.32649 0.556153,-0.448242 0.210282,-0.127271 0.44547,-0.22688 0.705566,-0.298828 0.26562,-0.07193 0.561681,-0.107902 0.888184,-0.10791 0.52571,8e-6 0.998854,0.08578 1.419433,0.257324 0.420566,0.171557 0.774732,0.42058 1.0625,0.74707 0.293286,0.326504 0.517407,0.727708 0.672363,1.203614 0.15494,0.475916 0.232413,1.021 0.232422,1.635254 -9e-6,0.658532 -0.09408,1.247887 -0.282226,1.768066 -0.182626,0.520184 -0.445484,0.962892 -0.788575,1.328125 -0.343106,0.359701 -0.758145,0.636394 -1.245117,0.830078 -0.486985,0.188151 -1.034836,0.282227 -1.643554,0.282227 -0.597661,0 -1.15658,-0.105144 -1.676758,-0.31543 -0.520185,-0.21582 -0.973961,-0.542317 -1.361328,-0.979492 -0.381838,-0.437173 -0.683433,-0.987791 -0.904785,-1.651856 -0.215822,-0.669593 -0.323732,-1.460933 -0.323731,-2.374023 m 4.216797,3.270508 c 0.226883,2e-6 0.431635,-0.0415 0.614258,-0.124512 0.188145,-0.08854 0.348627,-0.218585 0.481445,-0.390137 0.13834,-0.17708 0.243483,-0.3
98434 0.31543,-0.664062 0.07747,-0.265622 0.116204,-0.581051 0.116211,-0.946289 -7e-6,-0.592118 -0.124518,-1.056961 -0.373535,-1.394531 -0.243496,-0.343094 -0.617031,-0.514643 -1.120606,-0.514649 -0.254562,6e-6 -0.486984,0.04981 -0.697266,0.149414 -0.21029,0.09962 -0.39014,0.229661 -0.53955,0.390137 -0.149418,0.160487 -0.265629,0.340337 -0.348633,0.539551 -0.07748,0.199223 -0.116214,0.401209 -0.116211,0.605957 -3e-6,0.28223 0.0332,0.564456 0.09961,0.846679 0.07194,0.276696 0.17708,0.528486 0.31543,0.755371 0.143876,0.221357 0.318193,0.401207 0.522949,0.539551 0.210282,0.138349 0.453772,0.207522 0.730469,0.20752"
+ id="path2846"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/7.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/7.png
new file mode 100644
index 0000000..52c3a18
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/7.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/7.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/7.svg
new file mode 100644
index 0000000..a43460f
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/7.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;text-anchor:start;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 12.789991,22.008438 4.316407,-9.960937 -5.578125,0 0,-2.1582035 8.367187,0 0,1.6103515 -4.424316,10.508789 -2.681153,0"
+ id="path2832"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/8.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/8.png
new file mode 100644
index 0000000..8a8cb21
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/8.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/8.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/8.svg
new file mode 100644
index 0000000..2c82d3f
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/8.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;text-anchor:start;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.761671,9.7149811 c 0.503576,1.23e-5 0.979487,0.060885 1.427734,0.1826172 0.448236,0.1217567 0.841139,0.3043737 1.178711,0.5478517 0.337558,0.243501 0.60595,0.547862 0.805176,0.913086 0.199211,0.365244 0.29882,0.794118 0.298828,1.286621 -8e-6,0.365243 -0.05535,0.697274 -0.166015,0.996094 -0.110686,0.293302 -0.262866,0.561694 -0.456543,0.805175 -0.193693,0.237963 -0.423348,0.451017 -0.688965,0.639161 -0.265632,0.188157 -0.553392,0.359707 -0.863281,0.514648 0.320957,0.171556 0.633619,0.362473 0.937988,0.572754 0.309888,0.210292 0.583814,0.448247 0.821777,0.713867 0.237948,0.260096 0.428866,0.55339 0.572754,0.879883 0.143872,0.326501 0.215812,0.691735 0.21582,1.095703 -8e-6,0.503583 -0.09962,0.960126 -0.298828,1.369629 -0.199227,0.409506 -0.478686,0.758139 -0.838379,1.045898 -0.359707,0.287761 -0.791348,0.509115 -1.294921,0.664063 -0.498053,0.154948 -1.048671,0.232422 -1.651856,0.232422 -0.652999,0 -1.234053,-0.07471 -1.743164,-0.224121 -0.509117,-0.149414 -0.9379
9,-0.362467 -1.286621,-0.639161 -0.348634,-0.276691 -0.614259,-0.617023 -0.796875,-1.020996 -0.177084,-0.403969 -0.265626,-0.857744 -0.265625,-1.361328 -10e-7,-0.415035 0.06087,-0.78857 0.182617,-1.120605 0.121744,-0.332027 0.287759,-0.630855 0.498047,-0.896485 0.210285,-0.265619 0.456541,-0.500808 0.73877,-0.705566 0.282224,-0.204747 0.583819,-0.384597 0.904785,-0.539551 -0.271162,-0.171543 -0.525719,-0.356927 -0.763672,-0.556152 -0.237958,-0.204746 -0.445477,-0.428866 -0.622559,-0.672363 -0.171551,-0.249016 -0.309897,-0.522942 -0.415039,-0.821778 -0.09961,-0.298819 -0.149415,-0.628083 -0.149414,-0.987793 -10e-7,-0.481435 0.09961,-0.902008 0.298828,-1.261718 0.204751,-0.365224 0.478677,-0.669585 0.821778,-0.913086 0.343096,-0.249012 0.738766,-0.434396 1.187011,-0.5561527 0.448239,-0.1217326 0.918616,-0.1826049 1.411133,-0.1826172 m -1.718262,9.0644529 c -3e-6,0.221357 0.03597,0.42611 0.107911,0.614258 0.07194,0.18262 0.17708,0.340334 0.315429,0.473145 0.143877,0.132814 0.32
096,0.237957 0.53125,0.315429 0.210283,0.07194 0.453772,0.107912 0.730469,0.10791 0.581049,2e-6 1.015457,-0.135577 1.303223,-0.406738 0.287754,-0.27669 0.431634,-0.639157 0.43164,-1.087402 -6e-6,-0.232419 -0.04981,-0.439938 -0.149414,-0.622559 -0.09408,-0.188147 -0.218593,-0.359696 -0.373535,-0.514648 -0.14942,-0.160478 -0.320969,-0.307125 -0.514648,-0.439942 -0.19369,-0.132807 -0.387375,-0.260086 -0.581055,-0.381836 L 15.662062,16.72084 c -0.243494,0.12175 -0.464848,0.254563 -0.664063,0.398438 -0.199222,0.138351 -0.370772,0.293299 -0.514648,0.464844 -0.13835,0.16602 -0.24626,0.348637 -0.323731,0.547851 -0.07748,0.199223 -0.116214,0.415043 -0.116211,0.647461 m 1.701661,-7.188476 c -0.182622,10e-6 -0.354171,0.02768 -0.514649,0.08301 -0.154952,0.05535 -0.290531,0.13559 -0.406738,0.240723 -0.110681,0.105153 -0.199223,0.235199 -0.265625,0.390137 -0.06641,0.154957 -0.09961,0.329274 -0.09961,0.522949 -3e-6,0.232431 0.0332,0.434416 0.09961,0.605957 0.07194,0.166024 0.166012,0.31543
8 0.282226,0.448242 0.121741,0.127287 0.260087,0.243498 0.415039,0.348633 0.160478,0.09962 0.32926,0.199226 0.506348,0.298828 0.171545,-0.08853 0.334793,-0.185376 0.489746,-0.290527 0.154943,-0.105135 0.290522,-0.224113 0.406738,-0.356934 0.12174,-0.138338 0.218582,-0.293286 0.290528,-0.464843 0.07193,-0.171541 0.107904,-0.367993 0.10791,-0.589356 -6e-6,-0.193675 -0.03321,-0.367992 -0.09961,-0.522949 -0.06641,-0.154938 -0.157721,-0.284984 -0.273926,-0.390137 -0.116217,-0.105133 -0.254563,-0.185374 -0.415039,-0.240723 -0.160487,-0.05533 -0.334803,-0.083 -0.522949,-0.08301"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/9.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/9.png
new file mode 100644
index 0000000..0ae412f
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/9.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/9.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/9.svg
new file mode 100644
index 0000000..b0f04c4
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/9.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;text-anchor:start;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 19.829054,15.052383 c -9e-6,0.581061 -0.03321,1.162116 -0.09961,1.743164 -0.06088,0.575526 -0.174325,1.126144 -0.340333,1.651856 -0.160489,0.525719 -0.381843,1.018232 -0.664062,1.477539 -0.2767,0.453778 -0.630866,0.846681 -1.0625,1.178711 -0.426113,0.332032 -0.940761,0.59489 -1.543945,0.788574 -0.597661,0.188151 -1.30046,0.282227 -2.108399,0.282227 -0.116214,0 -0.243492,-0.0028 -0.381836,-0.0083 -0.138348,-0.0055 -0.279462,-0.01384 -0.42334,-0.0249 -0.138348,-0.0055 -0.273927,-0.0166 -0.406738,-0.0332 -0.132814,-0.01107 -0.249025,-0.02767 -0.348633,-0.0498 l 0,-2.058594 c 0.204751,0.05534 0.423338,0.09961 0.655762,0.132813 0.237954,0.02767 0.478676,0.04151 0.722168,0.0415 0.747067,2e-6 1.361324,-0.09131 1.842773,-0.273925 0.481441,-0.188149 0.863276,-0.44824 1.145508,-0.780274 0.282221,-0.337562 0.481439,-0.738766 0.597657,-1.203613 0.121738,-0.464839 0.196445,-0.97672 0.224121,-1.535645 l -0.107911,0 c -0.110683,0.199225 -0.243495,0.384609 -0.398437,0.556153 -0.
154954,0.171554 -0.337571,0.320968 -0.547852,0.448242 -0.210291,0.127283 -0.448247,0.226892 -0.713867,0.298828 -0.265629,0.07194 -0.56169,0.107914 -0.888183,0.10791 -0.52572,4e-6 -0.998864,-0.08577 -1.419434,-0.257324 -0.420575,-0.171545 -0.777508,-0.420568 -1.070801,-0.74707 -0.287761,-0.326492 -0.509115,-0.727696 -0.664062,-1.203614 -0.154949,-0.475904 -0.232423,-1.020988 -0.232422,-1.635253 -10e-7,-0.65852 0.09131,-1.247875 0.273926,-1.768067 0.18815,-0.520172 0.453774,-0.960113 0.796875,-1.319824 0.343097,-0.365223 0.758135,-0.644682 1.245117,-0.838379 0.49251,-0.1936727 1.043127,-0.2905151 1.651855,-0.2905274 0.597651,1.23e-5 1.15657,0.1079224 1.676758,0.3237304 0.520176,0.210298 0.971184,0.534028 1.353027,0.971192 0.381829,0.437185 0.683423,0.990569 0.904786,1.660156 0.221345,0.669605 0.332022,1.458178 0.332031,2.365722 m -4.216797,-3.262207 c -0.226892,1.1e-5 -0.434412,0.04151 -0.622559,0.124512 -0.188154,0.08302 -0.351403,0.213063 -0.489746,0.390137 -0.132815,0.17155
9 -0.237959,0.392913 -0.315429,0.664062 -0.07194,0.265634 -0.107914,0.581063 -0.107911,0.946289 -3e-6,0.586596 0.124509,1.05144 0.373536,1.394532 0.249019,0.343105 0.625321,0.514654 1.128906,0.514648 0.254552,6e-6 0.486974,-0.0498 0.697266,-0.149414 0.210281,-0.0996 0.390131,-0.229648 0.53955,-0.390137 0.149408,-0.160475 0.262852,-0.340325 0.340332,-0.53955 0.083,-0.199212 0.124506,-0.401197 0.124512,-0.605958 -6e-6,-0.282218 -0.03598,-0.561677 -0.10791,-0.838378 -0.06641,-0.282218 -0.171556,-0.534008 -0.31543,-0.755372 -0.138352,-0.226878 -0.312668,-0.409495 -0.522949,-0.547851 -0.204758,-0.138336 -0.44548,-0.207509 -0.722168,-0.20752"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/bkgrnd_greydots.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/bkgrnd_greydots.png
new file mode 100644
index 0000000..2333a6d
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/bkgrnd_greydots.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/bullet_arrowblue.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/bullet_arrowblue.png
new file mode 100644
index 0000000..c235534
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/bullet_arrowblue.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/documentation.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/documentation.png
new file mode 100644
index 0000000..79d0a80
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/documentation.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/dot.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/dot.png
new file mode 100644
index 0000000..36a6859
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/dot.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/dot2.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/dot2.png
new file mode 100644
index 0000000..40aff92
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/dot2.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/green.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/green.png
new file mode 100644
index 0000000..ebb3c24
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/green.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/h1-bg.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/h1-bg.png
new file mode 100644
index 0000000..a2aad24
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/h1-bg.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/image_left.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/image_left.png
new file mode 100644
index 0000000..e8fe7a4
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/image_left.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/image_right.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/image_right.png
new file mode 100644
index 0000000..5b67443
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/image_right.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/important.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/important.png
new file mode 100644
index 0000000..f7594a3
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/important.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/important.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/important.svg
new file mode 100644
index 0000000..2d33045
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/important.svg
@@ -0,0 +1,106 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:dc="http://purl.org/dc/elements/1.1/"
+ xmlns:cc="http://creativecommons.org/ns#"
+ xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd"
+ xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
+ version="1.0"
+ width="48"
+ height="48"
+ id="svg5921"
+ sodipodi:version="0.32"
+ inkscape:version="0.46"
+ sodipodi:docname="important.svg"
+ inkscape:output_extension="org.inkscape.output.svg.inkscape"
+ inkscape:export-filename="/home/jfearn/Build/src/fedora/publican/trunk/publican-fedora/en-US/images/important.png"
+ inkscape:export-xdpi="111.32"
+ inkscape:export-ydpi="111.32">
+ <metadata
+ id="metadata2611">
+ <rdf:RDF>
+ <cc:Work
+ rdf:about="">
+ <dc:format>image/svg+xml</dc:format>
+ <dc:type
+ rdf:resource="http://purl.org/dc/dcmitype/StillImage" />
+ </cc:Work>
+ </rdf:RDF>
+ </metadata>
+ <sodipodi:namedview
+ inkscape:window-height="681"
+ inkscape:window-width="738"
+ inkscape:pageshadow="2"
+ inkscape:pageopacity="0.0"
+ guidetolerance="10.0"
+ gridtolerance="10.0"
+ objecttolerance="10.0"
+ borderopacity="1.0"
+ bordercolor="#666666"
+ pagecolor="#ffffff"
+ id="base"
+ showgrid="false"
+ inkscape:zoom="11.5"
+ inkscape:cx="20"
+ inkscape:cy="20"
+ inkscape:window-x="0"
+ inkscape:window-y="51"
+ inkscape:current-layer="svg5921" />
+ <defs
+ id="defs5923">
+ <inkscape:perspective
+ sodipodi:type="inkscape:persp3d"
+ inkscape:vp_x="0 : 20 : 1"
+ inkscape:vp_y="0 : 1000 : 0"
+ inkscape:vp_z="40 : 20 : 1"
+ inkscape:persp3d-origin="20 : 13.333333 : 1"
+ id="perspective2613" />
+ </defs>
+ <g
+ transform="matrix(0.4626799,0,0,0.4626799,-5.2934127,-3.3160376)"
+ id="g5485">
+ <path
+ d="M 29.97756,91.885882 L 55.586992,80.409826 L 81.231619,91.807015 L 78.230933,63.90468 L 96.995009,43.037218 L 69.531053,37.26873 L 55.483259,12.974592 L 41.510292,37.311767 L 14.064204,43.164717 L 32.892392,63.97442 L 29.97756,91.885882 z"
+ id="path6799"
+ style="fill:#f3de82;fill-opacity:1;enable-background:new" />
+ <path
+ d="M 55.536215,56.538729 L 55.48324,12.974601 L 41.51028,37.311813 L 55.536215,56.538729 z"
+ id="path6824"
+ style="opacity:0.91005291;fill:#f9f2cb;fill-opacity:1;enable-background:new" />
+ <path
+ d="M 55.57947,56.614318 L 78.241135,63.937979 L 96.976198,43.044318 L 55.57947,56.614318 z"
+ id="use6833"
+ style="opacity:1;fill:#d0bc64;fill-opacity:1;enable-background:new" />
+ <path
+ d="M 55.523838,56.869126 L 55.667994,80.684281 L 81.379011,91.931065 L 55.523838,56.869126 z"
+ id="use6835"
+ style="opacity:1;fill:#e0c656;fill-opacity:1;enable-background:new" />
+ <path
+ d="M 55.283346,56.742618 L 13.877363,43.200977 L 32.640089,64.069652 L 55.283346,56.742618 z"
+ id="use6831"
+ style="opacity:1;fill:#d1ba59;fill-opacity:1;enable-background:new" />
+ <path
+ d="M 55.472076,56.869126 L 55.32792,80.684281 L 29.616903,91.931065 L 55.472076,56.869126 z"
+ id="use6837"
+ style="opacity:1;fill:#d2b951;fill-opacity:1;enable-background:new" />
+ <path
+ d="M 55.57947,56.614318 L 96.976198,43.044318 L 69.504294,37.314027 L 55.57947,56.614318 z"
+ id="path7073"
+ style="opacity:1;fill:#f6e7a3;fill-opacity:1;enable-background:new" />
+ <path
+ d="M 55.523838,56.869126 L 81.379011,91.931065 L 78.214821,64.046881 L 55.523838,56.869126 z"
+ id="path7075"
+ style="opacity:1;fill:#f6e7a3;fill-opacity:1;enable-background:new" />
+ <path
+ d="M 55.283346,56.742618 L 41.341708,37.434209 L 13.877363,43.200977 L 55.283346,56.742618 z"
+ id="path7077"
+ style="opacity:1;fill:#f6e59d;fill-opacity:1;enable-background:new" />
+ <path
+ d="M 55.472076,56.869126 L 29.616903,91.931065 L 32.781093,64.046881 L 55.472076,56.869126 z"
+ id="path7079"
+ style="opacity:1;fill:#f3df8b;fill-opacity:1;enable-background:new" />
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/logo.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/logo.png
new file mode 100644
index 0000000..66a3104
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/logo.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/note.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/note.png
new file mode 100644
index 0000000..d6c4518
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/note.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/note.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/note.svg
new file mode 100644
index 0000000..70e43b6
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/note.svg
@@ -0,0 +1,111 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:dc="http://purl.org/dc/elements/1.1/"
+ xmlns:cc="http://creativecommons.org/ns#"
+ xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd"
+ xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
+ version="1.0"
+ width="48"
+ height="48"
+ id="svg5921"
+ sodipodi:version="0.32"
+ inkscape:version="0.46"
+ sodipodi:docname="note.svg"
+ inkscape:output_extension="org.inkscape.output.svg.inkscape"
+ inkscape:export-filename="/home/jfearn/Build/src/fedora/publican/trunk/publican-fedora/en-US/images/note.png"
+ inkscape:export-xdpi="111.32"
+ inkscape:export-ydpi="111.32">
+ <metadata
+ id="metadata16">
+ <rdf:RDF>
+ <cc:Work
+ rdf:about="">
+ <dc:format>image/svg+xml</dc:format>
+ <dc:type
+ rdf:resource="http://purl.org/dc/dcmitype/StillImage" />
+ </cc:Work>
+ </rdf:RDF>
+ </metadata>
+ <sodipodi:namedview
+ inkscape:window-height="1024"
+ inkscape:window-width="1205"
+ inkscape:pageshadow="2"
+ inkscape:pageopacity="0.0"
+ guidetolerance="10.0"
+ gridtolerance="10.0"
+ objecttolerance="10.0"
+ borderopacity="1.0"
+ bordercolor="#666666"
+ pagecolor="#ffffff"
+ id="base"
+ showgrid="false"
+ inkscape:zoom="11.5"
+ inkscape:cx="22.217181"
+ inkscape:cy="20"
+ inkscape:window-x="334"
+ inkscape:window-y="51"
+ inkscape:current-layer="svg5921" />
+ <defs
+ id="defs5923">
+ <inkscape:perspective
+ sodipodi:type="inkscape:persp3d"
+ inkscape:vp_x="0 : 20 : 1"
+ inkscape:vp_y="0 : 1000 : 0"
+ inkscape:vp_z="40 : 20 : 1"
+ inkscape:persp3d-origin="20 : 13.333333 : 1"
+ id="perspective18" />
+ </defs>
+ <g
+ transform="matrix(0.468275,0,0,0.468275,-5.7626904,-7.4142703)"
+ id="layer1">
+ <g
+ transform="matrix(0.115136,0,0,0.115136,9.7283,21.77356)"
+ id="g8014"
+ style="enable-background:new">
+ <g
+ id="g8518"
+ style="opacity:1">
+ <path
+ d="M -2512.4524,56.33197 L 3090.4719,56.33197 L 3090.4719,4607.3813 L -2512.4524,4607.3813 L -2512.4524,56.33197 z"
+ transform="matrix(0.1104659,-2.3734892e-2,2.2163258e-2,0.1031513,308.46782,74.820675)"
+ id="rect8018"
+ style="fill:#ffe680;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.1;stroke-linecap:butt;stroke-miterlimit:4;stroke-dashoffset:0;stroke-opacity:1" />
+ </g>
+ <g
+ transform="matrix(0.5141653,-7.1944682e-2,7.1944682e-2,0.5141653,146.04015,-82.639785)"
+ id="g8020">
+ <path
+ d="M 511.14114,441.25315 C 527.3248,533.52772 464.31248,622.82928 370.39916,640.71378 C 276.48584,658.59828 187.23462,598.29322 171.05095,506.01865 C 154.86728,413.74408 217.8796,324.44253 311.79292,306.55803 C 405.70624,288.67353 494.95747,348.97858 511.14114,441.25315 z"
+ id="path8022"
+ style="opacity:1;fill:#e0c96f;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.0804934;stroke-linecap:butt;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1" />
+ <path
+ d="M 527.8214,393.1416 C 527.8214,461.31268 472.55783,516.57625 404.38675,516.57625 C 336.21567,516.57625 280.9521,461.31268 280.9521,393.1416 C 280.9521,324.97052 336.21567,269.70695 404.38675,269.70695 C 472.55783,269.70695 527.8214,324.97052 527.8214,393.1416 z"
+ transform="matrix(1.2585415,-0.2300055,0.2168789,1.1867072,-248.76141,68.254424)"
+ id="path8024"
+ style="opacity:1;fill:#c00000;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.0804934;stroke-linecap:butt;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1" />
+ <path
+ d="M 358.5625,281.15625 C 348.09597,281.05155 337.43773,281.94729 326.71875,283.90625 C 240.96686,299.57789 183.37901,377.92385 198.15625,458.78125 C 209.70749,521.98673 262.12957,567.92122 325.40625,577.5625 L 357.25,433.6875 L 509.34375,405.875 C 509.14405,404.58166 509.0804,403.29487 508.84375,402 C 495.91366,331.24978 431.82821,281.88918 358.5625,281.15625 z"
+ id="path8026"
+ style="opacity:1;fill:#b60000;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.1;stroke-linecap:butt;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1" />
+ <path
+ d="M 294.2107,361.9442 L 282.79367,370.38482 L 261.73414,386.13346 C 253.13706,404.40842 254.3359,423.7989 259.7176,444.39774 C 273.6797,497.83861 313.42636,523.96124 369.50989,517.58957 C 398.21848,514.32797 424.51832,504.67345 440.64696,484.15958 L 469.89512,447.48298 L 294.2107,361.9442 z"
+ id="path8028"
+ style="fill:#750000;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.09999999;stroke-linecap:butt;stroke-miterlimit:4;stroke-dashoffset:0;stroke-opacity:1" />
+ <path
+ d="M 527.8214,393.1416 C 527.8214,461.31268 472.55783,516.57625 404.38675,516.57625 C 336.21567,516.57625 280.9521,461.31268 280.9521,393.1416 C 280.9521,324.97052 336.21567,269.70695 404.38675,269.70695 C 472.55783,269.70695 527.8214,324.97052 527.8214,393.1416 z"
+ transform="matrix(0.9837071,-0.1797787,0.1695165,0.9275553,-78.013985,79.234385)"
+ id="path8030"
+ style="opacity:1;fill:#d40000;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.10298239;stroke-linecap:butt;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1" />
+ <path
+ d="M 527.8214,393.1416 C 527.8214,461.31268 472.55783,516.57625 404.38675,516.57625 C 336.21567,516.57625 280.9521,461.31268 280.9521,393.1416 C 280.9521,324.97052 336.21567,269.70695 404.38675,269.70695 C 472.55783,269.70695 527.8214,324.97052 527.8214,393.1416 z"
+ transform="matrix(0.9837071,-0.1797787,0.1695165,0.9275553,-69.306684,71.273294)"
+ id="path8032"
+ style="opacity:1;fill:#e11212;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.10298239;stroke-linecap:butt;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1" />
+ </g>
+ </g>
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/red.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/red.png
new file mode 100644
index 0000000..d32d5e2
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/red.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/shade.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/shade.png
new file mode 100644
index 0000000..a73afdf
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/shade.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/shine.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/shine.png
new file mode 100644
index 0000000..a18f7c4
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/shine.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/stock-go-back.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/stock-go-back.png
new file mode 100644
index 0000000..d320f26
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/stock-go-back.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/stock-go-forward.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/stock-go-forward.png
new file mode 100644
index 0000000..1ee5a29
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/stock-go-forward.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/stock-go-up.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/stock-go-up.png
new file mode 100644
index 0000000..1cd7332
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/stock-go-up.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/stock-home.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/stock-home.png
new file mode 100644
index 0000000..122536d
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/stock-home.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/title_logo.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/title_logo.png
new file mode 100644
index 0000000..d5182b4
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/title_logo.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/title_logo.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/title_logo.svg
new file mode 100644
index 0000000..e8fd52b
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/title_logo.svg
@@ -0,0 +1,61 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="220"
+ height="70"
+ id="svg6180">
+ <defs
+ id="defs6182" />
+ <g
+ transform="translate(-266.55899,-345.34488)"
+ id="layer1">
+ <path
+ d="m 316.7736,397.581 c 0,0 0,0 -20.53889,0 0.3327,4.45245 3.92157,7.77609 8.70715,7.77609 3.38983,0 6.31456,-1.39616 8.64094,-3.65507 0.46553,-0.46679 0.99726,-0.59962 1.59519,-0.59962 0.79781,0 1.59561,0.39932 2.12692,1.06388 0.3327,0.46553 0.53216,0.99726 0.53216,1.52857 0,0.73118 -0.3327,1.52857 -0.93106,2.12734 -2.7919,2.99052 -7.51086,4.98503 -12.16403,4.98503 -8.44149,0 -15.22074,-6.77967 -15.22074,-15.22158 0,-8.44149 6.58022,-15.22074 15.02171,-15.22074 8.37529,0 14.62323,6.51317 14.62323,15.08749 0,1.26418 -1.12924,2.12861 -2.39258,2.12861 z m -12.23065,-11.76512 c -4.45329,0 -7.51085,2.92473 -8.17499,7.17731 10.03626,0 16.35083,0 16.35083,0 -0.59836,-4.05355 -3.78874,-7.17731 -8.17584,-7.17731 z"
+ id="path11"
+ style="fill:#3c6eb4" />
+ <path
+ d="m 375.46344,410.80807 c -8.44106,0 -15.22074,-6.77968 -15.22074,-15.22159 0,-8.44149 6.77968,-15.22074 15.22074,-15.22074 8.44234,0 15.22159,6.77925 15.22159,15.22074 -4.2e-4,8.44149 -6.77968,15.22159 -15.22159,15.22159 z m 0,-24.65992 c -5.31688,0 -8.77377,4.25427 -8.77377,9.43833 0,5.18364 3.45689,9.43833 8.77377,9.43833 5.31731,0 8.77504,-4.25469 8.77504,-9.43833 -4.2e-4,-5.18406 -3.45773,-9.43833 -8.77504,-9.43833 z"
+ id="path13"
+ style="fill:#3c6eb4" />
+ <path
+ d="m 412.66183,380.36574 c -4.45963,0 -7.40966,1.319 -10.01391,4.62956 l -0.24036,-1.53995 0,0 c -0.20198,-1.60743 -1.57326,-2.84926 -3.23382,-2.84926 -1.80139,0 -3.26206,1.459 -3.26206,3.26081 0,0.003 0,0.005 0,0.008 l 0,0 0,0.003 0,0 0,23.40712 c 0,1.79464 1.46194,3.25743 3.257,3.25743 1.79465,0 3.25744,-1.46279 3.25744,-3.25743 l 0,-12.56209 c 0,-5.71621 4.98502,-8.57432 10.23613,-8.57432 1.59519,0 2.85726,-1.32953 2.85726,-2.92515 0,-1.59561 -1.26207,-2.85726 -2.85768,-2.85726 z"
+ id="path15"
+ style="fill:#3c6eb4" />
+ <path
+ d="m 447.02614,395.58648 c 0.0666,-8.17541 -5.78326,-15.22074 -15.222,-15.22074 -8.44192,0 -15.28779,6.77925 -15.28779,15.22074 0,8.44191 6.64684,15.22159 14.68985,15.22159 4.01434,0 7.62682,-2.06621 9.23846,-4.22518 l 0.79359,2.01434 0,0 c 0.42589,1.13177 1.5176,1.93717 2.7978,1.93717 1.65001,0 2.98756,-1.33671 2.99009,-2.98545 l 0,0 0,-7.80687 0,0 0,-4.1556 z m -15.222,9.43833 c -5.31773,0 -8.77419,-4.25469 -8.77419,-9.43833 0,-5.18406 3.45604,-9.43833 8.77419,-9.43833 5.3173,0 8.77419,4.25427 8.77419,9.43833 0,5.18364 -3.45689,9.43833 -8.77419,9.43833 z"
+ id="path17"
+ style="fill:#3c6eb4" />
+ <path
+ d="m 355.01479,368.3337 c 0,-1.7938 -1.46194,-3.18997 -3.25659,-3.18997 -1.79422,0 -3.25743,1.39659 -3.25743,3.18997 l 0,17.1499 c -1.66097,-3.05756 -5.25026,-5.11786 -9.50495,-5.11786 -8.64052,0 -14.42336,6.51318 -14.42336,15.22074 0,8.70757 5.98229,15.22159 14.42336,15.22159 3.76555,0 7.03057,-1.55429 8.98587,-4.25554 l 0.72317,1.83428 c 0.44782,1.25912 1.64917,2.16024 3.06051,2.16024 1.78621,0 3.24984,-1.45435 3.24984,-3.24815 0,-0.005 0,-0.009 0,-0.0139 l 0,0 0,-38.95128 -4.2e-4,0 z m -15.22116,36.69111 c -5.31731,0 -8.70715,-4.25469 -8.70715,-9.43833 0,-5.18406 3.38984,-9.43833 8.70715,-9.43833 5.31773,0 8.70714,4.0544 8.70714,9.43833 0,5.38309 -3.38941,9.43833 -8.70714,9.43833 z"
+ id="path19"
+ style="fill:#3c6eb4" />
+ <path
+ d="m 287.21553,365.34023 c -0.59414,-0.0877 -1.19966,-0.13198 -1.80097,-0.13198 -6.73118,0 -12.20746,5.4767 -12.20746,12.20788 l 0,3.8132 -3.98903,0 c -1.46237,0 -2.65908,1.19671 -2.65908,2.65781 0,1.46321 1.19671,2.93738 2.65908,2.93738 l 3.98819,0 0,20.46004 c 0,1.79464 1.46236,3.25743 3.25658,3.25743 1.79507,0 3.25744,-1.46279 3.25744,-3.25743 l 0,-20.46004 4.40986,0 c 1.46194,0 2.65823,-1.47417 2.65823,-2.93738 0,-1.46152 -1.19629,-2.65823 -2.65823,-2.65823 l -4.40733,0 0,-3.8132 c 0,-3.13852 2.55323,-6.11469 5.69175,-6.11469 0.28294,0 0.56757,0.0211 0.84672,0.062 1.78031,0.26355 3.4358,-0.54269 3.70019,-2.32342 0.2627,-1.77904 -0.96606,-3.43538 -2.74594,-3.69935 z"
+ id="path21"
+ style="fill:#3c6eb4" />
+ <path
+ d="m 482.01243,363.57426 c 0,-10.06788 -8.16108,-18.22938 -18.22897,-18.22938 -10.06282,0 -18.22179,8.15475 -18.22854,18.21631 l -4.2e-4,-4.2e-4 0,14.1071 4.2e-4,4.2e-4 c 0.005,2.28463 1.85832,4.13409 4.14463,4.13409 0.007,0 0.0127,-8.4e-4 0.0194,-8.4e-4 l 0.001,8.4e-4 14.07083,0 0,0 c 10.06409,-0.004 18.22138,-8.16276 18.22138,-18.22812 z"
+ id="path25"
+ style="fill:#294172" />
+ <path
+ d="m 469.13577,349.66577 c -4.72528,0 -8.55576,3.83049 -8.55576,8.55577 0,0.002 0,0.004 0,0.006 l 0,4.52836 -4.51444,0 c -8.5e-4,0 -8.5e-4,0 -0.001,0 -4.72528,0 -8.55576,3.81193 -8.55576,8.53678 0,4.72528 3.83048,8.55577 8.55576,8.55577 4.72486,0 8.55534,-3.83049 8.55534,-8.55577 0,-0.002 0,-0.004 0,-0.006 l 0,-4.54733 4.51444,0 c 8.5e-4,0 0.001,0 0.002,0 4.72486,0 8.55534,-3.79296 8.55534,-8.51781 0,-4.72528 -3.83048,-8.55577 -8.55534,-8.55577 z m -8.55576,21.63483 c -0.004,2.48998 -2.02446,4.50811 -4.51571,4.50811 -2.49378,0 -4.53426,-2.02193 -4.53426,-4.5157 0,-2.49421 2.04048,-4.55366 4.53426,-4.55366 0.002,0 0.004,4.2e-4 0.006,4.2e-4 l 3.86971,0 c 0.001,0 0.002,-4.2e-4 0.003,-4.2e-4 0.35209,0 0.63799,0.28505 0.63799,0.63715 0,4.2e-4 -4.2e-4,8.4e-4 -4.2e-4,0.001 l 0,3.92284 -4.2e-4,0 z m 8.55534,-8.5448 c -0.001,0 -0.003,0 -0.004,0 l -3.87223,0 c -8.4e-4,0 -0.002,0 -0.002,0 -0.35252,0 -0.63757,-0.28506 -0.63757,-0.63758 l 0,-4.2e-4 0,-3.90343 c 0.004,-2.49083 2.02
446,-4.50854 4.51571,-4.50854 2.49378,0 4.53468,2.02193 4.53468,4.51613 4.2e-4,2.49336 -2.04048,4.53384 -4.53426,4.53384 z"
+ id="path29"
+ style="fill:#3c6eb4" />
+ <path
+ d="m 460.58001,362.7558 0,-4.52836 c 0,-0.002 0,-0.004 0,-0.006 0,-4.72528 3.83048,-8.55577 8.55576,-8.55577 0.71685,0 1.22623,0.0805 1.88952,0.25469 0.96774,0.25385 1.75796,1.04618 1.75838,1.96922 4.2e-4,1.11575 -0.80919,1.92621 -2.0194,1.92621 -0.57642,0 -0.78473,-0.11048 -1.62892,-0.11048 -2.49125,0 -4.51149,2.01771 -4.51571,4.50854 l 0,3.90385 0,4.2e-4 c 0,0.35252 0.28505,0.63758 0.63757,0.63758 4.3e-4,0 0.001,0 0.002,0 l 2.96521,0 c 1.10521,0 1.99747,0.88467 1.99832,1.99283 0,1.10816 -0.89353,1.99114 -1.99832,1.99114 l -3.60489,0 0,4.54733 c 0,0.002 0,0.004 0,0.006 0,4.72485 -3.83048,8.55534 -8.55534,8.55534 -0.71684,0 -1.22623,-0.0805 -1.88952,-0.25469 -0.96774,-0.25343 -1.75838,-1.04618 -1.7588,-1.9688 0,-1.11575 0.80919,-1.92663 2.01982,-1.92663 0.576,0 0.78473,0.11048 1.6285,0.11048 2.49125,0 4.51191,-2.01771 4.51613,-4.50811 0,0 0,-3.92368 0,-3.9241 0,-0.35168 -0.2859,-0.63673 -0.63799,-0.63673 -4.3e-4,0 -8.5e-4,0 -0.002,0 l -2.96521,-4.2e-4 c -1.10521,0 -1.
99831,-0.88214 -1.99831,-1.9903 -4.3e-4,-1.11533 0.90238,-1.99367 2.01939,-1.99367 l 3.58339,0 0,0 z"
+ id="path31"
+ style="fill:#ffffff" />
+ <path
+ d="m 477.41661,378.55292 2.81558,0 0,0.37898 -1.18152,0 0,2.94935 -0.45254,0 0,-2.94935 -1.18152,0 0,-0.37898 m 3.26144,0 0.67101,0 0.84937,2.26496 0.85381,-2.26496 0.67102,0 0,3.32833 -0.43917,0 0,-2.9226 -0.85828,2.28279 -0.45255,0 -0.85827,-2.28279 0,2.9226 -0.43694,0 0,-3.32833"
+ id="text6223"
+ style="fill:#294172;enable-background:new" />
+ </g>
+ <path
+ d="m 181.98344,61.675273 2.81558,0 0,0.37898 -1.18152,0 0,2.94935 -0.45254,0 0,-2.94935 -1.18152,0 0,-0.37898 m 3.26144,0 0.67101,0 0.84937,2.26496 0.85381,-2.26496 0.67102,0 0,3.32833 -0.43917,0 0,-2.9226 -0.85828,2.28279 -0.45255,0 -0.85827,-2.28279 0,2.9226 -0.43694,0 0,-3.32833"
+ id="path2391"
+ style="fill:#294172;enable-background:new" />
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/warning.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/warning.png
new file mode 100644
index 0000000..ce09951
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/warning.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/warning.svg b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/warning.svg
new file mode 100644
index 0000000..5f2612c
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/warning.svg
@@ -0,0 +1,89 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:dc="http://purl.org/dc/elements/1.1/"
+ xmlns:cc="http://creativecommons.org/ns#"
+ xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd"
+ xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
+ version="1.0"
+ width="48"
+ height="48"
+ id="svg5921"
+ sodipodi:version="0.32"
+ inkscape:version="0.46"
+ sodipodi:docname="warning.svg"
+ inkscape:output_extension="org.inkscape.output.svg.inkscape"
+ inkscape:export-filename="/home/jfearn/Build/src/fedora/publican/trunk/publican-fedora/en-US/images/warning.png"
+ inkscape:export-xdpi="111.32"
+ inkscape:export-ydpi="111.32">
+ <metadata
+ id="metadata2482">
+ <rdf:RDF>
+ <cc:Work
+ rdf:about="">
+ <dc:format>image/svg+xml</dc:format>
+ <dc:type
+ rdf:resource="http://purl.org/dc/dcmitype/StillImage" />
+ </cc:Work>
+ </rdf:RDF>
+ </metadata>
+ <sodipodi:namedview
+ inkscape:window-height="910"
+ inkscape:window-width="1284"
+ inkscape:pageshadow="2"
+ inkscape:pageopacity="0.0"
+ guidetolerance="10.0"
+ gridtolerance="10.0"
+ objecttolerance="10.0"
+ borderopacity="1.0"
+ bordercolor="#666666"
+ pagecolor="#ffffff"
+ id="base"
+ showgrid="false"
+ inkscape:zoom="11.5"
+ inkscape:cx="20"
+ inkscape:cy="20"
+ inkscape:window-x="0"
+ inkscape:window-y="51"
+ inkscape:current-layer="svg5921" />
+ <defs
+ id="defs5923">
+ <inkscape:perspective
+ sodipodi:type="inkscape:persp3d"
+ inkscape:vp_x="0 : 20 : 1"
+ inkscape:vp_y="0 : 1000 : 0"
+ inkscape:vp_z="40 : 20 : 1"
+ inkscape:persp3d-origin="20 : 13.333333 : 1"
+ id="perspective2484" />
+ </defs>
+ <g
+ transform="matrix(0.4536635,0,0,0.4536635,-5.1836431,-4.6889387)"
+ id="layer1">
+ <g
+ transform="translate(2745.6887,-1555.5977)"
+ id="g8304"
+ style="enable-background:new">
+ <path
+ d="M -1603,1054.4387 L -1577.0919,1027.891 L -1540,1027.4387 L -1513.4523,1053.3468 L -1513,1090.4387 L -1538.9081,1116.9864 L -1576,1117.4387 L -1602.5477,1091.5306 L -1603,1054.4387 z"
+ transform="matrix(0.8233528,8.9983906e-3,-8.9983906e-3,0.8233528,-1398.5561,740.7914)"
+ id="path8034"
+ style="opacity:1;fill:#efd259;fill-opacity:1;stroke:#efd259;stroke-opacity:1" />
+ <path
+ d="M -1603,1054.4387 L -1577.0919,1027.891 L -1540,1027.4387 L -1513.4523,1053.3468 L -1513,1090.4387 L -1538.9081,1116.9864 L -1576,1117.4387 L -1602.5477,1091.5306 L -1603,1054.4387 z"
+ transform="matrix(0.6467652,7.0684723e-3,-7.0684723e-3,0.6467652,-1675.7492,927.16391)"
+ id="path8036"
+ style="opacity:1;fill:#a42324;fill-opacity:1;stroke:#a42324;stroke-opacity:1" />
+ <path
+ d="M -2686.7886,1597.753 C -2686.627,1596.5292 -2686.5462,1595.6987 -2686.5462,1595.218 C -2686.5462,1593.1637 -2688.0814,1592.0711 -2690.9899,1592.0711 C -2693.8985,1592.0711 -2695.4336,1593.12 -2695.4336,1595.218 C -2695.4336,1595.961 -2695.3528,1596.7914 -2695.1912,1597.753 L -2692.929,1614.4491 L -2689.0508,1614.4491 L -2686.7886,1597.753"
+ id="path8038"
+ style="font-size:107.13574219px;font-style:normal;font-weight:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;stroke-width:1px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1;font-family:Bitstream Charter" />
+ <path
+ d="M -2690.9899,1617.8197 C -2693.6124,1617.8197 -2695.8118,1619.9346 -2695.8118,1622.6416 C -2695.8118,1625.3486 -2693.6124,1627.4635 -2690.9899,1627.4635 C -2688.2829,1627.4635 -2686.168,1625.264 -2686.168,1622.6416 C -2686.168,1619.9346 -2688.2829,1617.8197 -2690.9899,1617.8197"
+ id="path8040"
+ style="font-size:107.13574219px;font-style:normal;font-weight:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;stroke-width:1px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1;font-family:Bitstream Charter" />
+ </g>
+ </g>
+</svg>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/watermark-draft.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/watermark-draft.png
new file mode 100644
index 0000000..0ead5af
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/watermark-draft.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/yellow.png b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/yellow.png
new file mode 100644
index 0000000..223865d
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/Common_Content/images/yellow.png differ
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/RPM-Guide-Using_RPM-DB-verifying_packages.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/RPM-Guide-Using_RPM-DB-verifying_packages.html
new file mode 100644
index 0000000..0746bd4
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/RPM-Guide-Using_RPM-DB-verifying_packages.html
@@ -0,0 +1,141 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>4.4.2. Verifying Installed RPM Packages</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="RPM_Guide-Using_RPM_DB-Getting_information_on_package_files.html" title="4.4. Getting Information on Package Files" /><link rel="prev" href="RPM_Guide-Using_RPM_DB-Getting_information_on_package_files.html" title="4.4. Getting Information on Package Files" /><link rel="next" href="RPM_Guide-Using_RPM_DB-controlling_verification.html" title="4.4.2.2. Controlling the verification" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docn
av"><li class="previous"><a accesskey="p" href="RPM_Guide-Using_RPM_DB-Getting_information_on_package_files.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="RPM_Guide-Using_RPM_DB-controlling_verification.html"><strong>ÃŽnainte</strong></a></li></ul><div class="section" id="RPM-Guide-Using_RPM-DB-verifying_packages"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="RPM-Guide-Using_RPM-DB-verifying_packages">4.4.2. Verifying Installed RPM Packages</h3></div></div></div><div class="para">
+ You can do a lot more than just query packages in the RPM database. You can ask the rpm command to verify packages with the <code class="option">-V</code> (or <code class="option">--verify</code>) option. The rpm -V command will also report missing dependencies.
+ </div><div class="para">
+ The basic syntax is:
+ </div><div class="para">
+ <code class="command">rpm -V <em class="replaceable"><code>verify_options</code></em> <em class="replaceable"><code>package_name</code></em></code>
+ </div><div class="para">
+ For example:
+ </div><pre class="screen">
+ rpm -V telnet
+ #
+</pre><div class="para">
+ If everything checks out, you'll get no response. The rpm command reports problems only. For example, if you have an installation of the telnet-server package that is missing some files, the rpm -V command will let you know, as shown following:
+ </div><pre class="screen">
+ $ rpm -V telnet-server
+ missing c /etc/xinetd.d/telnet
+ missing /usr/sbin/in.telnetd
+ missing d /usr/share/man/man5/issue.net.5.gz
+</pre><div class="para">
+ In this example, the c and d stand for configuration and documentation files, respectively.
+ </div><div class="para">
+ Note
+ </div><div class="section" id="RPM_Guide-Using_RPM_DB-verifying_system"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="RPM_Guide-Using_RPM_DB-verifying_system">4.4.2.1. Verifying your entire system</h4></div></div></div><div class="para">
+ To verify your entire system, use the <code class="option">-a</code> option.
+ </div><div class="para">
+ For example:
+ </div><pre class="screen">
+ # rpm -Va
+ SM5....T c /usr/share/info/dir
+ .......T c /etc/krb5.conf
+ .......T /usr/share/pixmaps/gnome-default-dlg.png
+ .......T /usr/share/pixmaps/gnome-error.png
+ .......T /usr/share/pixmaps/gnome-info.png
+ .......T /usr/share/pixmaps/gnome-question.png
+ .......T /usr/share/pixmaps/gnome-warning.png
+ S.5....T c /etc/sysconfig/pcmcia
+ .....U.. /dev/winradio0
+</pre><div class="para">
+ Each line that the rpm command outputs indicates a problem with the given file. The rpm command uses letter codes to show the type of the problem. Table 5-8 lists the letter codes with their meanings.
+ </div><div class="para">
+ Table 5-8 RPM verify output codes
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Code
+ </div>
+
+ </td><td>
+ <div class="para">
+ Meaning
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ S
+ </div>
+
+ </td><td>
+ <div class="para">
+ File size differs.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ M
+ </div>
+
+ </td><td>
+ <div class="para">
+ File mode differs.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ 5
+ </div>
+
+ </td><td>
+ <div class="para">
+ The MD5 checksum differs.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ D
+ </div>
+
+ </td><td>
+ <div class="para">
+ The major and minor version numbers differ on a device file.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ L
+ </div>
+
+ </td><td>
+ <div class="para">
+ A mismatch occurs in a link.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ U
+ </div>
+
+ </td><td>
+ <div class="para">
+ The file ownership differs.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ G
+ </div>
+
+ </td><td>
+ <div class="para">
+ The file group owner differs.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ T
+ </div>
+
+ </td><td>
+ <div class="para">
+ The file time (mtime) differs.
+ </div>
+
+ </td></tr></tbody></table></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="RPM_Guide-Using_RPM_DB-Getting_information_on_package_files.html"><strong>Înapoi</strong>4.4. Getting Information on Package Files</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="RPM_Guide-Using_RPM_DB-controlling_verification.html"><strong>Înainte</strong>4.4.2.2. Controlling the verification</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/RPM-Guide-Using_RPM_DB-Querying_file_information.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/RPM-Guide-Using_RPM_DB-Querying_file_information.html
new file mode 100644
index 0000000..771eb1e
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/RPM-Guide-Using_RPM_DB-Querying_file_information.html
@@ -0,0 +1,230 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>4.2.16. Querying for File Information</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="RPM_Guide-Using_RPM_DB-getting_information.html" title="4.2. Getting Information on Packages" /><link rel="prev" href="RPM_Guide-Using_RPM_DB-querying_pacakge_dependencies.html" title="4.2.15. Querying for Package Dependencies" /><link rel="next" href="RPM_Guide-Using_RPM_DB-Other_Query_Format_Tags.html" title="4.2.17. Other Query Format Tags" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesske
y="p" href="RPM_Guide-Using_RPM_DB-querying_pacakge_dependencies.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="RPM_Guide-Using_RPM_DB-Other_Query_Format_Tags.html"><strong>ÃŽnainte</strong></a></li></ul><div class="section" id="RPM-Guide-Using_RPM_DB-Querying_file_information"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="RPM-Guide-Using_RPM_DB-Querying_file_information">4.2.16. Querying for File Information</h3></div></div></div><div class="para">
+ The file-information tags hold data on the files within the package payload, that is, the files the rpm command installs when you install the package. These tags are arrays, with one value per file.
+ </div><div class="para">
+ Table 5-5 lists the file-information tags.
+ </div><div class="para">
+ Table 5-5 File-information query tags
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Tag
+ </div>
+
+ </td><td>
+ <div class="para">
+ Holds
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ OLDFILENAMES
+ </div>
+
+ </td><td>
+ <div class="para">
+ Array of full file names, used in older packages
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ FILESIZES
+ </div>
+
+ </td><td>
+ <div class="para">
+ Array of sizes for each file
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ FILEMODES
+ </div>
+
+ </td><td>
+ <div class="para">
+ Array of permissions for each file
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ FILERDEVS
+ </div>
+
+ </td><td>
+ <div class="para">
+ Array of rdev values for each file
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ FILEMTIMES
+ </div>
+
+ </td><td>
+ <div class="para">
+ Array of modified times for each file
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ FILEMD5S
+ </div>
+
+ </td><td>
+ <div class="para">
+ MD5 checksum for each file
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ FILELINKTOS
+ </div>
+
+ </td><td>
+ <div class="para">
+ Array of link information for each file
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ FILEFLAGS
+ </div>
+
+ </td><td>
+ <div class="para">
+ Array of flags for each file
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ FILEUSERNAME
+ </div>
+
+ </td><td>
+ <div class="para">
+ Array of user names for the file owners
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ FILEGROUPNAME
+ </div>
+
+ </td><td>
+ <div class="para">
+ Array of group names for the file owners
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ FILEDEVICES
+ </div>
+
+ </td><td>
+ <div class="para">
+ Array of devices for each file
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ FILEINODES
+ </div>
+
+ </td><td>
+ <div class="para">
+ Array of inodes for each file
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ FILELANGS
+ </div>
+
+ </td><td>
+ <div class="para">
+ Array of language flags for each file
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ DIRINDEXES
+ </div>
+
+ </td><td>
+ <div class="para">
+ Array of values that matches the DIRNAMES with the BASENBAMES
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ BASENAMES
+ </div>
+
+ </td><td>
+ <div class="para">
+ Array of file base names
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ DIRNAMES
+ </div>
+
+ </td><td>
+ <div class="para">
+ Array of directories that matches up with BASENAMES
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ The <code class="literal">OLDFILENAMES</code> tag is used when the files are not compressed, when the <code class="literal">REQUIRENAME</code> tag does not indicate rpmlib(CompressedFileNames).
+ </div><div class="para">
+ The <code class="literal">FILESIZES</code> tag specifies the size of each file in the payload, while the <code class="literal">FILEMODES</code> tag specifies the file modes (permissions) and the <code class="literal">FILEMTIMES</code> tag holds the last modification time for each file.
+ </div><div class="para">
+ The <code class="literal">BASENAMES</code> tag holds an array of the base file names for the files in the payload. The <code class="literal">DIRNAMES</code> tag holds an array of the directories for the files. The <code class="literal">DIRINDEXES</code> tag contains an index into the <code class="literal">DIRNAMES</code> for the directory. Each RPM must have either <code class="literal">OLDFILENAMES</code> or the triple of <code class="literal">BASENAMES</code>, <code class="literal">DIRNAMES</code>, and <code class="literal">DIRINDEXES</code>, but not both.
+ </div><div class="para">
+ When listing file information, use the square bracket array syntax with your query formats. You can use the perms special formatting option for the file modes. For example:
+ </div><pre class="screen">
+$ rpm -q --qf "[%-15{=NAME} %-36{FILENAMES} %{FILEMODES:perms}\n]" sudo
+sudo /etc/pam.d/sudo -rw-r--r--
+sudo /etc/pam.d/sudo-i -rw-r--r--
+sudo /etc/sudoers -r--r-----
+sudo /etc/sudoers.d drwxr-x---
+sudo /usr/bin/sudo ---s--x--x
+sudo /usr/bin/sudoedit ---s--x--x
+sudo /usr/bin/sudoreplay ---x--x--x
+sudo /usr/libexec/sesh -rwxr-xr-x
+sudo /usr/libexec/sudo_noexec.so -rwxr-xr-x
+sudo /usr/sbin/visudo -rwxr-xr-x
+sudo /usr/share/doc/sudo-1.7.4p4 drwxr-xr-x
+sudo /usr/share/doc/sudo-1.7.4p4/ChangeLog -rw-r--r--
+sudo /usr/share/doc/sudo-1.7.4p4/HISTORY -rw-r--r--
+sudo /usr/share/doc/sudo-1.7.4p4/LICENSE -rw-r--r--
+sudo /usr/share/doc/sudo-1.7.4p4/NEWS -rw-r--r--
+sudo /usr/share/doc/sudo-1.7.4p4/README -rw-r--r--
+sudo /usr/share/doc/sudo-1.7.4p4/README.LDAP -rw-r--r--
+sudo /usr/share/doc/sudo-1.7.4p4/TROUBLESHOOTING -rw-r--r--
+sudo /usr/share/doc/sudo-1.7.4p4/UPGRADE -rw-r--r--
+sudo /usr/share/doc/sudo-1.7.4p4/sample.pam -rw-r--r--
+sudo /usr/share/doc/sudo-1.7.4p4/sample.sudoers -rw-r--r--
+sudo /usr/share/doc/sudo-1.7.4p4/sample.syslog.conf -rw-r--r--
+sudo /usr/share/doc/sudo-1.7.4p4/schema.ActiveDirectory -rw-r--r--
+sudo /usr/share/doc/sudo-1.7.4p4/schema.OpenLDAP -rw-r--r--
+sudo /usr/share/doc/sudo-1.7.4p4/schema.iPlanet -rw-r--r--
+sudo /usr/share/doc/sudo-1.7.4p4/sudoers.ldap.pod -rw-r--r--
+sudo /usr/share/doc/sudo-1.7.4p4/sudoers2ldif -rw-r--r--
+sudo /usr/share/man/man5/sudoers.5.gz -rw-r--r--
+sudo /usr/share/man/man5/sudoers.ldap.5.gz -rw-r--r--
+sudo /usr/share/man/man8/sudo.8.gz -rw-r--r--
+sudo /usr/share/man/man8/sudoedit.8.gz -rw-r--r--
+sudo /usr/share/man/man8/sudoreplay.8.gz -rw-r--r--
+sudo /usr/share/man/man8/visudo.8.gz -rw-r--r--
+sudo /var/db/sudo drwx------
+</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="RPM_Guide-Using_RPM_DB-querying_pacakge_dependencies.html"><strong>Înapoi</strong>4.2.15. Querying for Package Dependencies</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="RPM_Guide-Using_RPM_DB-Other_Query_Format_Tags.html"><strong>Înainte</strong>4.2.17. Other Query Format Tags</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/RPM_GUide-Using_RPM_DB-working_with_RPM_db.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/RPM_GUide-Using_RPM_DB-working_with_RPM_db.html
new file mode 100644
index 0000000..2fda36c
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/RPM_GUide-Using_RPM_DB-working_with_RPM_db.html
@@ -0,0 +1,44 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>4.4.3. Working With the RPM Database</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="RPM_Guide-Using_RPM_DB-Getting_information_on_package_files.html" title="4.4. Getting Information on Package Files" /><link rel="prev" href="RPM_Guide-Using_RPM_DB-controlling_verification.html" title="4.4.2.2. Controlling the verification" /><link rel="next" href="RPM_Guide-Using_RPM_DB-rebuilding_RPM-db.html" title="4.4.3.2. Rebuilding the RPM database" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"
><a accesskey="p" href="RPM_Guide-Using_RPM_DB-controlling_verification.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="RPM_Guide-Using_RPM_DB-rebuilding_RPM-db.html"><strong>ÃŽnainte</strong></a></li></ul><div class="section" id="RPM_GUide-Using_RPM_DB-working_with_RPM_db"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="RPM_GUide-Using_RPM_DB-working_with_RPM_db">4.4.3. Working With the RPM Database</h3></div></div></div><div class="para">
+ As mentioned in <a class="xref" href="ch-rpm-overview.html">Cap. 2, <em>RPM Overview</em></a> , the RPM database is stored in /var/lib/rpm. The files in that directory are Berkeley DB files, as shown by the file command:
+ </div><pre class="screen">
+ # file /var/lib/rpm/*
+ /var/lib/rpm/Basenames: Berkeley DB (Hash, version 7, native byte-order)
+ /var/lib/rpm/Conflictname: Berkeley DB (Hash, version 7, native byte-order)
+ /var/lib/rpm/__db.001: data
+ /var/lib/rpm/__db.002: X11 SNF font data, LSB first
+ /var/lib/rpm/__db.003: X11 SNF font data, LSB first
+ /var/lib/rpm/Dirnames: Berkeley DB (Btree, version 8, native byte-order)
+ /var/lib/rpm/Filemd5s: Berkeley DB (Btree, version 8, native byte-order)
+ /var/lib/rpm/Group: Berkeley DB (Hash, version 7, native byte-order)
+ /var/lib/rpm/Installtid: Berkeley DB (Btree, version 8, native byte-order)
+ /var/lib/rpm/Name: Berkeley DB (Hash, version 7, native byte-order)
+ /var/lib/rpm/Packages: Berkeley DB (Hash, version 7, native byte-order)
+ /var/lib/rpm/Providename: Berkeley DB (Hash, version 7, native byte-order)
+ /var/lib/rpm/Provideversion: Berkeley DB (Btree, version 8, native byte-order)
+ /var/lib/rpm/Requirename: Berkeley DB (Hash, version 7, native byte-order)
+ /var/lib/rpm/Requireversion: Berkeley DB (Btree, version 8, native byte-order)
+ /var/lib/rpm/Sha1header: Berkeley DB (Btree, version 8, native byte-order)
+ /var/lib/rpm/Sigmd5: Berkeley DB (Btree, version 8, native byte-order)
+ /var/lib/rpm/Triggername: Berkeley DB (Hash, version 7, native byte-order)
+</pre><div class="para">
+ Each file is a separate database in Berkeley DB format, except for a few __db data files. (These are not really X11 font files, just plain data files. The file command is confused by the data in the files.)
+ </div><div class="note"><div class="admonition_header"><h2>The Berkeley DB Library</h2></div><div class="admonition"><div class="para">
+ Available from Oracle at http://www.oracle.com/technetwork/database/berkeleydb/overview/, the Berkeley DB library provides a simple database API. This is not a traditional relational database. Instead, data values are stored in what amounts to a persistent hash table of name/value pairs. This type of database is very quick to look up a named entry (such as a package name) but is not so quick for iterating over all the entries.
+ </div></div></div><div class="para">
+ The RPM database is really a number of Berkeley DB databases, each designed for a different type of query.
+ </div><div class="para">
+ If something goes wrong with your RPM database, you can first try to rebuild it. If that fails, you may need to initialize a new database, although that is generally not needed. First and foremost, however, you should back up this database.
+ </div><div class="section" id="RPM_Guide-Using_RPM_DB-Backing_up_RPM_db"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="RPM_Guide-Using_RPM_DB-Backing_up_RPM_db">4.4.3.1. Backing up the RPM database</h4></div></div></div><div class="para">
+ As mentioned before, the RPM database resides in the /var/lib/rpm. You can back up the RPM database by using a command such as the following:
+ </div><div class="para">
+ <code class="command">tar cf <em class="replaceable"><code>rpmdb.tar</code></em> /var/lib/rpm</code>
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="RPM_Guide-Using_RPM_DB-controlling_verification.html"><strong>Înapoi</strong>4.4.2.2. Controlling the verification</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="RPM_Guide-Using_RPM_DB-rebuilding_RPM-db.html"><strong>Înainte</strong>4.4.3.2. Rebuilding the RPM database</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/RPM_Guide-Using_RPM_DB-Combining_queries-Recently_installed.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/RPM_Guide-Using_RPM_DB-Combining_queries-Recently_installed.html
new file mode 100644
index 0000000..26ac093
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/RPM_Guide-Using_RPM_DB-Combining_queries-Recently_installed.html
@@ -0,0 +1,29 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>4.2.9.3. Listing the Most Recently Installed Packages</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="RPM_Guide-Using_RPM_DB-Combining_queries.html" title="4.2.9. Combining queries" /><link rel="prev" href="RPM_Guide-Using_RPM_DB-Combining_queries-State_of_config_files.html" title="4.2.9.2. Listing the State of Configuration Files" /><link rel="next" href="RPM_Guide-Using_RPM_DB-Cusomt_queries.html" title="4.2.10. Creating custom queries" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p"
href="RPM_Guide-Using_RPM_DB-Combining_queries-State_of_config_files.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="RPM_Guide-Using_RPM_DB-Cusomt_queries.html"><strong>ÃŽnainte</strong></a></li></ul><div class="section" id="RPM_Guide-Using_RPM_DB-Combining_queries-Recently_installed"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="RPM_Guide-Using_RPM_DB-Combining_queries-Recently_installed">4.2.9.3. Listing the Most Recently Installed Packages</h4></div></div></div><div class="para">
+ To list the most recently installed packages, use the following command with the <code class="option">--last</code> option. This is very useful if you recently installed or upgraded a number of packages and something unexpected happens. If you cannot remember the package names, you can use the <code class="option">--last</code> option to list out packages in reverse order of installation.
+ </div><div class="para">
+ You can pipe the output of a query to the head command to show only the last ten packages that were installed or upgraded, as shown following:
+ </div><div class="para">
+ <code class="command">rpm -qa --last | head</code>
+ </div><pre class="screen">
+kmod-nvidia-2.6.34.6-47.fc13.x86_64-256.53-1.fc13 Sat 18 Sep 2010 09:54:48 AM EDT
+xorg-x11-drv-nvidia-256.53-1.fc13 Sat 18 Sep 2010 09:51:00 AM EDT
+kmod-nvidia-2.6.34.6-54.fc13.x86_64-256.53-1.fc13.3 Sat 18 Sep 2010 09:50:59 AM EDT
+xorg-x11-drv-nvidia-libs-256.53-1.fc13 Sat 18 Sep 2010 09:50:57 AM EDT
+google-talkplugin-1.5.1.0-1 Wed 15 Sep 2010 07:38:46 PM EDT
+mythplugins-0.23.1-2.fc13 Sun 12 Sep 2010 09:35:42 PM EDT
+mythweather-0.23.1-2.fc13 Sun 12 Sep 2010 09:35:40 PM EDT
+perl-DateTime-Format-ISO8601-0.07-1.fc13 Sun 12 Sep 2010 09:35:39 PM EDT
+perl-DateTime-Format-Builder-0.7901-5.fc13 Sun 12 Sep 2010 09:35:38 PM EDT
+perl-Class-Factory-Util-1.7-6.fc13 Sun 12 Sep 2010 09:35:37 PM EDT
+</pre><div class="para">
+ You can pass options to the head command to show more or fewer than ten lines. In general, starting with the last ten packages can help you track down something you installed the day before.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="RPM_Guide-Using_RPM_DB-Combining_queries-State_of_config_files.html"><strong>Înapoi</strong>4.2.9.2. Listing the State of Configuration Files</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="RPM_Guide-Using_RPM_DB-Cusomt_queries.html"><strong>Înainte</strong>4.2.10. Creating custom queries</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/RPM_Guide-Using_RPM_DB-Combining_queries-State_of_config_files.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/RPM_Guide-Using_RPM_DB-Combining_queries-State_of_config_files.html
new file mode 100644
index 0000000..0a0db60
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/RPM_Guide-Using_RPM_DB-Combining_queries-State_of_config_files.html
@@ -0,0 +1,20 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>4.2.9.2. Listing the State of Configuration Files</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="RPM_Guide-Using_RPM_DB-Combining_queries.html" title="4.2.9. Combining queries" /><link rel="prev" href="RPM_Guide-Using_RPM_DB-Combining_queries.html" title="4.2.9. Combining queries" /><link rel="next" href="RPM_Guide-Using_RPM_DB-Combining_queries-Recently_installed.html" title="4.2.9.3. Listing the Most Recently Installed Packages" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" hr
ef="RPM_Guide-Using_RPM_DB-Combining_queries.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="RPM_Guide-Using_RPM_DB-Combining_queries-Recently_installed.html"><strong>ÃŽnainte</strong></a></li></ul><div class="section" id="RPM_Guide-Using_RPM_DB-Combining_queries-State_of_config_files"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="RPM_Guide-Using_RPM_DB-Combining_queries-State_of_config_files">4.2.9.2. Listing the State of Configuration Files</h4></div></div></div><div class="para">
+ To find the state of all the configuration files for a given Linux command, use a command with the <code class="option">–qcsf</code> option with the name of the file, as shown here, or the <code class="option">-qcs</code> option with the name of a package.
+ </div><div class="para">
+ For example:
+ </div><div class="para">
+ <code class="command">rpm -qcsf /bin/bash</code>
+ </div><pre class="screen">
+normal /etc/skel/.bash_logout
+normal /etc/skel/.bash_profile
+normal /etc/skel/.bashrc
+</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="RPM_Guide-Using_RPM_DB-Combining_queries.html"><strong>Înapoi</strong>4.2.9. Combining queries</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="RPM_Guide-Using_RPM_DB-Combining_queries-Recently_installed.html"><strong>Înainte</strong>4.2.9.3. Listing the Most Recently Installed Pack...</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/RPM_Guide-Using_RPM_DB-Combining_queries.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/RPM_Guide-Using_RPM_DB-Combining_queries.html
new file mode 100644
index 0000000..faeb6d4
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/RPM_Guide-Using_RPM_DB-Combining_queries.html
@@ -0,0 +1,49 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>4.2.9. Combining queries</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="RPM_Guide-Using_RPM_DB-getting_information.html" title="4.2. Getting Information on Packages" /><link rel="prev" href="RPM_Guide-Using_RPM_DB-Listing_changed.html" title="4.2.8. Listing what has changed" /><link rel="next" href="RPM_Guide-Using_RPM_DB-Combining_queries-State_of_config_files.html" title="4.2.9.2. Listing the State of Configuration Files" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><
a accesskey="p" href="RPM_Guide-Using_RPM_DB-Listing_changed.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="RPM_Guide-Using_RPM_DB-Combining_queries-State_of_config_files.html"><strong>ÃŽnainte</strong></a></li></ul><div class="section" id="RPM_Guide-Using_RPM_DB-Combining_queries"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="RPM_Guide-Using_RPM_DB-Combining_queries">4.2.9. Combining queries</h3></div></div></div><div class="para">
+ The rpm command is very flexible in allowing you to combine queries. Just start the command with <code class="command">rpm –q</code> and add the various options either on their own, such as <code class="option">–q</code> with <code class="option">–s</code> and <code class="option">–f</code>, or together, such as <code class="option">–qsf</code>.
+ </div><div class="para">
+ The following sections show a few handy combinations of the options you can use for real-world package-management tasks.
+ </div><div class="section" id="RPM_Guide-Using_RPM_DB-Combining_queries-Decription_documentation"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="RPM_Guide-Using_RPM_DB-Combining_queries-Decription_documentation">4.2.9.1. Listing Package Description and Documentation Files</h4></div></div></div><div class="para">
+ To find information on a package and where it is documented, use the <code class="option">–qdi</code> option to rpm (a combination of the <code class="option">–q</code>, <code class="option">–d</code>, and <code class="option">–i</code> options):
+ </div><div class="para">
+ <code class="command">rpm -qdi grep</code>
+ </div><pre class="screen">
+Name : grep Relocations: (not relocatable)
+Version : 2.6.3 Vendor: Fedora Project
+Release : 1.fc13 Build Date: Wed 07 Apr 2010 05:58:58 PM EDT
+Install Date: Fri 27 Aug 2010 07:03:07 PM EDT Build Host: x86-06.phx2.fedoraproject.org
+Group : Applications/Text Source RPM: grep-2.6.3-1.fc13.src.rpm
+Size : 800493 License: GPLv3+
+Signature : RSA/SHA256, Wed 07 Apr 2010 06:48:20 PM EDT, Key ID 7edc6ad6e8e40fde
+Packager : Fedora Project
+URL : http://www.gnu.org/software/grep/
+Summary : Pattern matching utilities
+Description :
+The GNU versions of commonly used grep utilities. Grep searches through
+textual input for lines which contain a match to a specified pattern and then
+prints the matching lines. GNU's grep utilities include grep, egrep and fgrep.
+
+GNU grep is needed by many scripts, so it shall be installed on every system.
+/usr/share/doc/grep-2.6.3/ABOUT-NLS
+/usr/share/doc/grep-2.6.3/AUTHORS
+/usr/share/doc/grep-2.6.3/COPYING
+/usr/share/doc/grep-2.6.3/ChangeLog
+/usr/share/doc/grep-2.6.3/NEWS
+/usr/share/doc/grep-2.6.3/README
+/usr/share/doc/grep-2.6.3/THANKS
+/usr/share/doc/grep-2.6.3/TODO
+/usr/share/info/grep.info.gz
+/usr/share/man/man1/egrep.1.gz
+/usr/share/man/man1/fgrep.1.gz
+/usr/share/man/man1/grep.1.gz
+</pre><div class="para">
+ It can sometimes be difficult to track down the documentation for a given package. Some packages use Unix manual pages; others use info files, and still others provide HTML for other formatted manuals. Some have no real documentation at all.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="RPM_Guide-Using_RPM_DB-Listing_changed.html"><strong>Înapoi</strong>4.2.8. Listing what has changed</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="RPM_Guide-Using_RPM_DB-Combining_queries-State_of_config_files.html"><strong>Înainte</strong>4.2.9.2. Listing the State of Configuration Files</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/RPM_Guide-Using_RPM_DB-Cusomt_queries.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/RPM_Guide-Using_RPM_DB-Cusomt_queries.html
new file mode 100644
index 0000000..c9bb0ac
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/RPM_Guide-Using_RPM_DB-Cusomt_queries.html
@@ -0,0 +1,56 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>4.2.10. Creating custom queries</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="RPM_Guide-Using_RPM_DB-getting_information.html" title="4.2. Getting Information on Packages" /><link rel="prev" href="RPM_Guide-Using_RPM_DB-Combining_queries-Recently_installed.html" title="4.2.9.3. Listing the Most Recently Installed Packages" /><link rel="next" href="RPM_Guide-Using_RPM_DB-Query_format_tags.html" title="4.2.11. Working With Query Format Tags" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="p
revious"><a accesskey="p" href="RPM_Guide-Using_RPM_DB-Combining_queries-Recently_installed.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="RPM_Guide-Using_RPM_DB-Query_format_tags.html"><strong>ÃŽnainte</strong></a></li></ul><div class="section" id="RPM_Guide-Using_RPM_DB-Cusomt_queries"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="RPM_Guide-Using_RPM_DB-Cusomt_queries">4.2.10. Creating custom queries</h3></div></div></div><div class="para">
+ The <code class="option">--qf</code> or <code class="option">--queryformat</code> option allows you to create custom queries with the rpm command, although in a rather difficult manner. You need to pass a query format string, the syntax of which originates with the C printf function and requires precision.
+ </div><div class="para">
+ The basic syntax of the query format is <code class="option">%{tag_name}</code>. (The percent sign is about the only part that comes from the C printf function.) You can combine tag names to display more than one item per package. You can also add formatting options following C language conventions.
+ </div><div class="para">
+ For example, to list all package names, use a command like the following (the output is abbreviated):
+ </div><div class="para">
+ <code class="command">rpm -qa --qf "%{NAME}"</code>
+ </div><pre class="screen">
+libxml2tcp_wrappers-libstracerouteperl-Config-Tinylibsampleratefedora-icon-themefftw2dvb-appsreport-plugin-localsaveglib2-develqwtintltoolperl-Locale-Maketext-Gettextliblastfmxorg-x11-fonts-ISO8859-1-100dpilibpng-devellibgeotifffontconfigPackageKit-glibshared-mime-infoxorg-x11-drv-sisusbxmlgraphics-commonsopenoffice.org-graphicfilterm17n-db-oriyadejavu-sans-fontslibselinux-pythonapr-utilxorg-x11-drv-cirruslibsilcmysql-serverpnm2ppanssmythmusicdbus-glibcyrus-sasl-libfedora-release-notesekigaperl-Net-SSLeayperl-HTML-Parsermingettyphp-clixorg-x11-drv-nvidia-libspatchgnome-games-extra
+</pre><div class="para">
+ This command used the simplest format, which is just the value of the tag in the package headers, in this case the package names. Because we used no other formatting, this command outputs all the package names smashed together. To deal with this problem in the output, you can place a \n, the C language convention for a newline character, at the end of the format string. This fixes the output considerably.
+ </div><div class="para">
+ For example (showing just the first few entries):
+ </div><div class="para">
+ <code class="command">rpm -qa --qf "%{NAME}\n"</code>
+ </div><pre class="screen">
+libxml2
+tcp_wrappers-libs
+traceroute
+perl-Config-Tiny
+libsamplerate
+fedora-icon-theme
+fftw2
+dvb-apps
+report-plugin-localsave
+glib2-devel
+</pre><div class="para">
+ This command provides a custom query that is essentially the same as <code class="command">rpm -qa</code>. You’ll likely not use this command in favor of the simpler rpm option, but you can use this example as a guide for creating your own custom queries.
+ </div><div class="note"><div class="admonition_header"><h2>popt aliases</h2></div><div class="admonition"><div class="para">
+ A great many of the command-line options to the rpm command are defined as popt aliases. These popt aliases define the rpm command-line options in terms of longer query format strings. See <a class="xref" href="ch-customizing-rpm.html">Cap. 20, <em>Customizing RPM Behavior</em></a> for more information on popt.
+ </div></div></div><div class="para">
+ You can add items to the query string and use C language conventions for formatting and controlling the amount of space provided for each item output. For example, the following command prints the name and platform for all packages, showing the first few entries, formatted with 20 characters for each item:
+ </div><div class="para">
+ <code class="command">rpm -qa --qf "%-20{NAME} %-20{PLATFORM}\n"</code>
+ </div><pre class="screen">
+libxml2 x86_64-redhat-linux-gnu
+tcp_wrappers-libs i686-redhat-linux-gnu
+traceroute x86_64-redhat-linux-gnu
+perl-Config-Tiny noarch-redhat-linux-gnu
+libsamplerate x86_64-redhat-linux-gnu
+fedora-icon-theme noarch-redhat-linux-gnu
+fftw2 x86_64-redhat-linux-gnu
+dvb-apps x86_64-redhat-linux-gnu
+report-plugin-localsave x86_64-redhat-linux-gnu
+glib2-devel x86_64-redhat-linux-gnu
+</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="RPM_Guide-Using_RPM_DB-Combining_queries-Recently_installed.html"><strong>Înapoi</strong>4.2.9.3. Listing the Most Recently Installed Pack...</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="RPM_Guide-Using_RPM_DB-Query_format_tags.html"><strong>Înainte</strong>4.2.11. Working With Query Format Tags</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/RPM_Guide-Using_RPM_DB-Formatting_arrays.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/RPM_Guide-Using_RPM_DB-Formatting_arrays.html
new file mode 100644
index 0000000..eca8054
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/RPM_Guide-Using_RPM_DB-Formatting_arrays.html
@@ -0,0 +1,46 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>4.2.13. Formatting Arrays</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="RPM_Guide-Using_RPM_DB-getting_information.html" title="4.2. Getting Information on Packages" /><link rel="prev" href="RPM_Guide-Using_RPM_DB-Querying_for_package_information.html" title="4.2.12. Querying for Package Information" /><link rel="next" href="RPM_Guide-Using_RPM_DB-Special_formatting.html" title="4.2.14. Special Formatting" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" hr
ef="RPM_Guide-Using_RPM_DB-Querying_for_package_information.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="RPM_Guide-Using_RPM_DB-Special_formatting.html"><strong>ÃŽnainte</strong></a></li></ul><div class="section" id="RPM_Guide-Using_RPM_DB-Formatting_arrays"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="RPM_Guide-Using_RPM_DB-Formatting_arrays">4.2.13. Formatting Arrays</h3></div></div></div><div class="para">
+ Many of the header entries are arrays, so the header tags can hold more than one item. For example, RPM packages can have more than one file in the payload.
+ </div><div class="para">
+ To specify a format for each item in an array, use square brackets. For example:
+ </div><div class="para">
+ <code class="command">rpm -q --queryformat "[%-50{FILENAMES} %{FILESIZES}\n]" sendmail</code>
+ </div><pre class="screen">
+/etc/NetworkManager/dispatcher.d/10-sendmail 96
+/etc/mail 4096
+/etc/mail/Makefile 92
+/etc/mail/access 469
+/etc/mail/access.db 0
+/etc/mail/aliasesdb-stamp 0
+/etc/mail/domaintable 233
+/etc/mail/domaintable.db 0
+/etc/mail/helpfile 5584
+/etc/mail/local-host-names 64
+</pre><div class="para">
+ This example lists the files and file sizes within a package, with the listing of files truncated for size.
+ </div><div class="para">
+ If you want to mix array tags with non-array tags, you can use an equals sign, <code class="literal">=</code>, in front of the tag name to specify that the given tag should be repeated for each item in the array. For example:
+ </div><div class="para">
+ <code class="command">rpm -q --queryformat "[%-15{=NAME} %-50{FILENAMES}\n]" sendmail bash</code>
+ </div><pre class="screen">
+sendmail /etc/NetworkManager/dispatcher.d/10-sendmail
+sendmail /etc/mail
+sendmail /etc/mail/Makefile
+sendmail /etc/mail/access
+sendmail /etc/mail/access.db
+bash /bin/bash
+bash /bin/sh
+bash /etc/skel/.bash_logout
+bash /etc/skel/.bash_profile
+bash /etc/skel/.bashrc
+</pre><div class="para">
+ This example, also truncated for size, lists the package name along with the file name for the files contained in these two packages.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="RPM_Guide-Using_RPM_DB-Querying_for_package_information.html"><strong>Înapoi</strong>4.2.12. Querying for Package Information</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="RPM_Guide-Using_RPM_DB-Special_formatting.html"><strong>Înainte</strong>4.2.14. Special Formatting</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/RPM_Guide-Using_RPM_DB-Getting_information_on_package_files.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/RPM_Guide-Using_RPM_DB-Getting_information_on_package_files.html
new file mode 100644
index 0000000..412e171
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/RPM_Guide-Using_RPM_DB-Getting_information_on_package_files.html
@@ -0,0 +1,96 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>4.4. Getting Information on Package Files</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-using-rpm-db.html" title="Cap. 4. Using the RPM Database" /><link rel="prev" href="ch04s03.html" title="4.3. Other queries" /><link rel="next" href="RPM-Guide-Using_RPM-DB-verifying_packages.html" title="4.4.2. Verifying Installed RPM Packages" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch04s03.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href=
"RPM-Guide-Using_RPM-DB-verifying_packages.html"><strong>ÃŽnainte</strong></a></li></ul><div class="section" id="RPM_Guide-Using_RPM_DB-Getting_information_on_package_files"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="RPM_Guide-Using_RPM_DB-Getting_information_on_package_files">4.4. Getting Information on Package Files</h2></div></div></div><div class="para">
+ In addition to querying the RPM database about installed packages, the rpm command provides the handy ability to extract information from RPM files. This is very useful for determining whether you want to install a given package or not. It also helps with the simple task of figuring out what a package’s purpose, especially if names like kudzu, anaconda, or dia don’t immediately tell you what the corresponding packages provide.
+ </div><div class="para">
+ The <code class="literal">–p</code> option tells the rpm command to provide information on the given package file. The basic syntax is:
+ </div><div class="para">
+ <code class="command">rpm –qp <em class="replaceable"><code>query_options</code></em> <em class="replaceable"><code>filename</code></em></code>
+ </div><div class="para">
+ You can use the longer option, <code class="literal">--package</code>, in place of <code class="literal">–p</code>. You can also pass more than one RPM file to the command.
+ </div><div class="para">
+ The query information options shown previously for installed packages also work for RPM files. For example, to list the configuration files for a package, combine the <code class="literal">-q</code>, <code class="literal">-p</code>, and <code class="literal">-c</code> options with the name of a package file, as shown following:
+ </div><pre class="screen">
+$ rpm -qpc qt-4.6.2-17.fc12.x86_64.rpm
+/etc/Trolltech.conf
+</pre><div class="para">
+ To list all the files in an RPM package, combine the <code class="literal">-q</code>, <code class="literal">-p</code>, and <code class="literal">-l</code> options (example output truncated):
+ </div><pre class="screen">
+$ rpm -qpl qt-4.6.2-17.fc12.x86_64.rpm
+/etc/Trolltech.conf
+/usr/bin/qdbus
+/usr/lib64/libQtCore.so.4
+/usr/lib64/libQtCore.so.4.6
+/usr/lib64/libQtCore.so.4.6.2
+/usr/lib64/libQtDBus.so.4
+/usr/lib64/libQtDBus.so.4.6
+/usr/lib64/libQtDBus.so.4.6.2
+/usr/lib64/libQtNetwork.so.4
+/usr/lib64/libQtNetwork.so.4.6
+</pre><div class="section" id="RPM_Guide_Using_RPM_DB-Querying_package_files_remotely"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="RPM_Guide_Using_RPM_DB-Querying_package_files_remotely">4.4.1. Querying Package Files Remotely</h3></div></div></div><div class="para">
+ As shown in <a class="xref" href="ch-using-rpm.html">Cap. 3, <em>Using RPM</em></a> , you can access RPM package files over a network using FTP or HTTP connections. To query remote files, use the same rules as shown in <a class="xref" href="ch-using-rpm.html">Cap. 3, <em>Using RPM</em></a> , with the following syntax:
+ </div><div class="para">
+ <code class="command">rpm -qp ftp://<em class="replaceable"><code>username</code></em>:<em class="replaceable"><code>password</code></em>@<em class="replaceable"><code>hostname</code></em>:<em class="replaceable"><code>port</code></em>/<em class="replaceable"><code>path/to/rpm/file</code></em></code>
+ </div><div class="para">
+ <code class="command">rpm -qp http://<em class="replaceable"><code>hostname</code></em>:<em class="replaceable"><code>port</code></em>/<em class="replaceable"><code>path/to/rpm/file</code></em></code>
+ </div><div class="para">
+ If your system resides behind a firewall with a proxy server, use the options in the following table to name the proxy. Note that these proxy options only work with the TIS Firewall toolkit.
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Network Proxy Option
+ </div>
+
+ </td><td>
+ <div class="para">
+ Meaning
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --ftpproxy proxy_hostname
+ </div>
+
+ </td><td>
+ <div class="para">
+ Names the proxy system
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --ftpport proxy_port_number
+ </div>
+
+ </td><td>
+ <div class="para">
+ Network port number on the proxy system
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --httpproxy proxy_hostname
+ </div>
+
+ </td><td>
+ <div class="para">
+ Names the proxy system
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --httpport proxy_port_number
+ </div>
+
+ </td><td>
+ <div class="para">
+ Network port number on the proxy system
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch04s03.html"><strong>Înapoi</strong>4.3. Other queries</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="RPM-Guide-Using_RPM-DB-verifying_packages.html"><strong>Înainte</strong>4.4.2. Verifying Installed RPM Packages</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/RPM_Guide-Using_RPM_DB-Listing_changed.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/RPM_Guide-Using_RPM_DB-Listing_changed.html
new file mode 100644
index 0000000..07956ef
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/RPM_Guide-Using_RPM_DB-Listing_changed.html
@@ -0,0 +1,59 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>4.2.8. Listing what has changed</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="RPM_Guide-Using_RPM_DB-getting_information.html" title="4.2. Getting Information on Packages" /><link rel="prev" href="RPM_Guide-Using_RPM_DB-listing_scripts.html" title="4.2.7. Listing the scripts in a package" /><link rel="next" href="RPM_Guide-Using_RPM_DB-Combining_queries.html" title="4.2.9. Combining queries" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="RPM_Guide-Using_R
PM_DB-listing_scripts.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="RPM_Guide-Using_RPM_DB-Combining_queries.html"><strong>ÃŽnainte</strong></a></li></ul><div class="section" id="RPM_Guide-Using_RPM_DB-Listing_changed"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="RPM_Guide-Using_RPM_DB-Listing_changed">4.2.8. Listing what has changed</h3></div></div></div><div class="para">
+ The <code class="option">--changelog</code> option lists what has changed, as described in a file that logs changes, from previous versions of a given package. The change log is just a convention, so not all packages will sport this nifty feature. In addition, the change log for many packages documents the changes in the RPM packaging, not the changes in the underlying application. If a change log is available, however, this can prove a very good way to help determine whether you want to upgrade to a new version of a package.
+ </div><div class="para">
+ For example, a network server application may have been updated to fix some security problems. In that case, you likely want to upgrade. Other changes may not affect your site, leading you to decide not to upgrade.
+ </div><div class="para">
+ The basic format of the command is:
+ </div><div class="para">
+ <code class="command">rpm –q --changelog <em class="replaceable"><code>package_name</code></em></code>
+ </div><div class="para">
+ For example, the following shows the beginning of the changelog for the bash package:
+ </div><div class="para">
+ <code class="command">rpm -q --changelog bash</code>
+ </div><pre class="screen">
+* Fri May 21 2010 Roman Rakus rrakus at redhat.com - 4.1.7-1
+- Patch level 7
+
+* Wed Mar 31 2010 Roman Rakus rrakus at redhat.com - 4.1.2-4
+- Corrected requires patch (#563301)
+
+* Fri Jan 22 2010 rrakus at redhat.com 4.1.2-3
+- Don't use cond-rmatch patch
+- Use manso patch
+- Include COPYING in base bash rpm
+
+* Fri Jan 22 2010 rrakus at redhat.com 4.1.2-2
+- Correct patchlevel 2
+
+* Fri Jan 22 2010 Roman Rakus rrakus at redhat.com 4.1.2-1
+- Patchlevel 4.2
+- Removed old patch
+- Returned back manso patch
+
+* Fri Jan 08 2010 Roman Rakus rrakus at redhat.com 4.1.0-2
+- Include COPYING in doc dir
+
+* Mon Jan 04 2010 Roman Rakus rrakus at redhat.com - 4.1.0-1
+- Upstream 4.1
+
+* Sun Dec 27 2009 Roman Rakus rrakus at redhat.com - 4.1-0.2.rc1
+- Fixed patch for fuzz=0
+
+* Sun Dec 27 2009 Roman Rakus rrakus at redhat.com - 4.1-0.1.rc1
+- Upstream 4.1.rc1
+
+* Fri Dec 11 2009 Roman Rakus rrakus at redhat.com - 4.0.35-2
+- Don't segfault when TERM=eterm* and EMACS is unset (#530911)
+
+* Thu Oct 29 2009 Roman Rakus rrakus at redhat.com - 4.0.35-1
+- Patch level 35
+</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="RPM_Guide-Using_RPM_DB-listing_scripts.html"><strong>Înapoi</strong>4.2.7. Listing the scripts in a package</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="RPM_Guide-Using_RPM_DB-Combining_queries.html"><strong>Înainte</strong>4.2.9. Combining queries</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/RPM_Guide-Using_RPM_DB-Other_Query_Format_Tags.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/RPM_Guide-Using_RPM_DB-Other_Query_Format_Tags.html
new file mode 100644
index 0000000..99849ce
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/RPM_Guide-Using_RPM_DB-Other_Query_Format_Tags.html
@@ -0,0 +1,128 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>4.2.17. Other Query Format Tags</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="RPM_Guide-Using_RPM_DB-getting_information.html" title="4.2. Getting Information on Packages" /><link rel="prev" href="RPM-Guide-Using_RPM_DB-Querying_file_information.html" title="4.2.16. Querying for File Information" /><link rel="next" href="ch04s03.html" title="4.3. Other queries" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="RPM-Guide-Using_RPM_DB-Querying_file_information
.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch04s03.html"><strong>ÃŽnainte</strong></a></li></ul><div class="section" id="RPM_Guide-Using_RPM_DB-Other_Query_Format_Tags"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="RPM_Guide-Using_RPM_DB-Other_Query_Format_Tags">4.2.17. Other Query Format Tags</h3></div></div></div><div class="para">
+ In addition to all these tags, there are a number of other miscellaneous tags, many of which are listed in Table 5-6.
+ </div><div class="para">
+ Table 5-6 Other query tags
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Tag
+ </div>
+
+ </td><td>
+ <div class="para">
+ Holds
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ ARCHIVESIZE
+ </div>
+
+ </td><td>
+ <div class="para">
+ Uncompressed size of the payload section
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ COOKIE
+ </div>
+
+ </td><td>
+ <div class="para">
+ Holds an opaque string
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMVERSION
+ </div>
+
+ </td><td>
+ <div class="para">
+ Holds the version of the RPM tool used to create the package
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ OPTFLAGS
+ </div>
+
+ </td><td>
+ <div class="para">
+ Compiler optimization flags used to build the package
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ PAYLOADFORMAT
+ </div>
+
+ </td><td>
+ <div class="para">
+ Must be cpio for LSB-compliant packages
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ PAYLOADCOMPRESSOR
+ </div>
+
+ </td><td>
+ <div class="para">
+ Must be gzip for LSB-compliant packages
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ PAYLOADFLAGS
+ </div>
+
+ </td><td>
+ <div class="para">
+ Must be 9 for LSB-compliant packages
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RHNPLATFORM
+ </div>
+
+ </td><td>
+ <div class="para">
+ Holds an opaque string
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ FILEVERIFYFLAGS
+ </div>
+
+ </td><td>
+ <div class="para">
+ Bitmask that specifies which tests to perform to verify the files after an install
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ For example, you can list the version of RPM that created a package with a command like the following:
+ </div><pre class="screen">
+$ rpm -qp --qf "%{name} - rpm %{rpmversion}\n" *.rpm
+qt - rpm 4.7.2
+qt - rpm 4.7.2
+qt-devel - rpm 4.7.2
+qt-mysql - rpm 4.7.2
+qt-sqlite - rpm 4.7.2
+qt-sqlite - rpm 4.7.2
+qt-x11 - rpm 4.7.2
+qt-x11 - rpm 4.7.2
+</pre><div class="note"><div class="admonition_header"><h2>Cross Reference</h2></div><div class="admonition"><div class="para">
+ See <a class="xref" href="ch-package-structure.html">Cap. 24, <em>RPM Package File Structure</em></a> for a listing of all the tags in an RPM file.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="RPM-Guide-Using_RPM_DB-Querying_file_information.html"><strong>Înapoi</strong>4.2.16. Querying for File Information</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch04s03.html"><strong>Înainte</strong>4.3. Other queries</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/RPM_Guide-Using_RPM_DB-Query_format_tags.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/RPM_Guide-Using_RPM_DB-Query_format_tags.html
new file mode 100644
index 0000000..a9396d6
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/RPM_Guide-Using_RPM_DB-Query_format_tags.html
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>4.2.11. Working With Query Format Tags</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="RPM_Guide-Using_RPM_DB-getting_information.html" title="4.2. Getting Information on Packages" /><link rel="prev" href="RPM_Guide-Using_RPM_DB-Cusomt_queries.html" title="4.2.10. Creating custom queries" /><link rel="next" href="RPM_Guide-Using_RPM_DB-Querying_for_package_information.html" title="4.2.12. Querying for Package Information" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" h
ref="RPM_Guide-Using_RPM_DB-Cusomt_queries.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="RPM_Guide-Using_RPM_DB-Querying_for_package_information.html"><strong>ÃŽnainte</strong></a></li></ul><div class="section" id="RPM_Guide-Using_RPM_DB-Query_format_tags"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="RPM_Guide-Using_RPM_DB-Query_format_tags">4.2.11. Working With Query Format Tags</h3></div></div></div><div class="para">
+ To build queries with the <code class="option">--queryformat</code> option, you need to know what tags you can use. To list the names of the available query format tags, use the <code class="option">--querytags</code> option, which returns a large set of tags, truncated here for space:
+ </div><div class="para">
+ <code class="command">rpm --querytags</code>
+ </div><pre class="screen">
+ NAME
+ VERSION
+ RELEASE
+ SUMMARY
+ DESCRIPTION
+ BUILDTIME
+</pre><div class="para">
+ Each of these tags also has a version with a <code class="literal">RPMTAG_</code> prefix, such as <code class="literal">RPMTAG_NAME</code>. You can use this tags with or without the <code class="literal">RPMTAG_</code> prefix. For example:
+ </div><div class="para">
+ <code class="command">rpm -q --qf "%{RPMTAG_NAME}\n" sendmail</code>
+ </div><pre class="screen">
+ sendmail
+</pre><div class="para">
+ Note how this command uses the <code class="option">–q</code> option to query for one package, instead of <code class="option">–qa</code> to query for all packages. You can use query formats with any of the rpm queries.
+ </div><div class="para">
+ The next sections cover the available tags based on the type of the information stored in the tag.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="RPM_Guide-Using_RPM_DB-Cusomt_queries.html"><strong>Înapoi</strong>4.2.10. Creating custom queries</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="RPM_Guide-Using_RPM_DB-Querying_for_package_information.html"><strong>Înainte</strong>4.2.12. Querying for Package Information</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/RPM_Guide-Using_RPM_DB-Querying_for_package_information.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/RPM_Guide-Using_RPM_DB-Querying_for_package_information.html
new file mode 100644
index 0000000..089b718
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/RPM_Guide-Using_RPM_DB-Querying_for_package_information.html
@@ -0,0 +1,236 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>4.2.12. Querying for Package Information</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="RPM_Guide-Using_RPM_DB-getting_information.html" title="4.2. Getting Information on Packages" /><link rel="prev" href="RPM_Guide-Using_RPM_DB-Query_format_tags.html" title="4.2.11. Working With Query Format Tags" /><link rel="next" href="RPM_Guide-Using_RPM_DB-Formatting_arrays.html" title="4.2.13. Formatting Arrays" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="RPM_Guide-Using
_RPM_DB-Query_format_tags.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="RPM_Guide-Using_RPM_DB-Formatting_arrays.html"><strong>ÃŽnainte</strong></a></li></ul><div class="section" id="RPM_Guide-Using_RPM_DB-Querying_for_package_information"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="RPM_Guide-Using_RPM_DB-Querying_for_package_information">4.2.12. Querying for Package Information</h3></div></div></div><div class="para">
+ Many of the query format tags refer to package-information data stored in the RPM header, introduced in <a class="xref" href="ch-rpm-overview.html">Cap. 2, <em>RPM Overview</em></a> . Table 5-3 lists the package-information tags.
+ </div><div class="para">
+ Table 5-3 Package-information query tags
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Tag
+ </div>
+
+ </td><td>
+ <div class="para">
+ Holds
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ NAME
+ </div>
+
+ </td><td>
+ <div class="para">
+ Package name
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ VERSION
+ </div>
+
+ </td><td>
+ <div class="para">
+ Version number
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RELEASE
+ </div>
+
+ </td><td>
+ <div class="para">
+ Release number
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ SUMMARY
+ </div>
+
+ </td><td>
+ <div class="para">
+ One-line summary of the package contents
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ DESCRIPTION
+ </div>
+
+ </td><td>
+ <div class="para">
+ Descriptive text about the package
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ BUILDTIME
+ </div>
+
+ </td><td>
+ <div class="para">
+ Time package was built
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ BUILDHOST
+ </div>
+
+ </td><td>
+ <div class="para">
+ Host package was built on
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ SIZE
+ </div>
+
+ </td><td>
+ <div class="para">
+ Size of all the regular files in the payload
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ LICENSE
+ </div>
+
+ </td><td>
+ <div class="para">
+ License package was released under
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ GROUP
+ </div>
+
+ </td><td>
+ <div class="para">
+ Descriptive group or category name for the package
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ OS
+ </div>
+
+ </td><td>
+ <div class="para">
+ Operating system package was built for
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ ARCH
+ </div>
+
+ </td><td>
+ <div class="para">
+ Architecture, such as i386
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ SOURCERPM
+ </div>
+
+ </td><td>
+ <div class="para">
+ The associated source RPM
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ CHANGELOGTIME
+ </div>
+
+ </td><td>
+ <div class="para">
+ Array of changelog times
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ CHANGELOGNAME
+ </div>
+
+ </td><td>
+ <div class="para">
+ Array of changelog names
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ CHANGELOGTEXT
+ </div>
+
+ </td><td>
+ <div class="para">
+ Array of changelog text entries
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ PREIN
+ </div>
+
+ </td><td>
+ <div class="para">
+ Pre-install script
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ POSTIN
+ </div>
+
+ </td><td>
+ <div class="para">
+ Post-install script
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ PREUN
+ </div>
+
+ </td><td>
+ <div class="para">
+ Pre-uninstall script
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ POSTUN
+ </div>
+
+ </td><td>
+ <div class="para">
+ Post uninstall script
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ PLATFORM
+ </div>
+
+ </td><td>
+ <div class="para">
+ Platform
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ All of these tags, except for the <code class="literal">CHANGELOGTIME</code>, <code class="literal">CHANGELOGTEXT</code> and <code class="literal">CHANGELOGNAME</code> tags, are single-value tags.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="RPM_Guide-Using_RPM_DB-Query_format_tags.html"><strong>Înapoi</strong>4.2.11. Working With Query Format Tags</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="RPM_Guide-Using_RPM_DB-Formatting_arrays.html"><strong>Înainte</strong>4.2.13. Formatting Arrays</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/RPM_Guide-Using_RPM_DB-Special_formatting.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/RPM_Guide-Using_RPM_DB-Special_formatting.html
new file mode 100644
index 0000000..dc43cac
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/RPM_Guide-Using_RPM_DB-Special_formatting.html
@@ -0,0 +1,42 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>4.2.14. Special Formatting</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="RPM_Guide-Using_RPM_DB-getting_information.html" title="4.2. Getting Information on Packages" /><link rel="prev" href="RPM_Guide-Using_RPM_DB-Formatting_arrays.html" title="4.2.13. Formatting Arrays" /><link rel="next" href="RPM_Guide-Using_RPM_DB-querying_pacakge_dependencies.html" title="4.2.15. Querying for Package Dependencies" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="
RPM_Guide-Using_RPM_DB-Formatting_arrays.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="RPM_Guide-Using_RPM_DB-querying_pacakge_dependencies.html"><strong>ÃŽnainte</strong></a></li></ul><div class="section" id="RPM_Guide-Using_RPM_DB-Special_formatting"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="RPM_Guide-Using_RPM_DB-Special_formatting">4.2.14. Special Formatting</h3></div></div></div><div class="para">
+ Some of the tags within an RPM package header contain special binary information that usually makes no sense when printed out. To help with these header tags, you can use special RPM formatting options, using a syntax like the following:
+ </div><div class="para">
+ <code class="literal">%{tag:special_format}</code>
+ </div><div class="para">
+ For example, to print the <code class="literal">INSTALLTIME</code> tag, use <code class="literal">%{INSTALLTIME:date}</code>, which specifies to print the <code class="literal">INSTALLTIME</code> tag in date format. For example:
+ </div><div class="para">
+ <code class="command">rpm -q --qf "%{NAME}-%{VERSION}-%{RELEASE} %{INSTALLTIME:date}\n" bash</code>
+ </div><pre class="screen">
+bash-4.1.7-1.fc13 Fri 27 Aug 2010 07:02:33 PM EDT
+</pre><div class="para">
+ This example prints the <code class="literal">NAME-VERSION-RELEASE</code> of the package, along with the <code class="literal">INSTALLTIME</code> in date format.
+ </div><div class="para">
+ Most tags in a header are optional. You can print the value of these tags, but you may get nothing. To help deal with this, you can use a conditional operator based loosely on the C language ternary operator. The basic syntax is:
+ </div><div class="para">
+ <code class="literal">%|tag?{print_if_present}:{print_if_absent}|</code>
+ </div><div class="para">
+ With the normal %{tag} syntax, this conditional syntax gets complicated really fast. You need to break the elements down. For example:
+ </div><div class="para">
+ <code class="command">rpm -q --qf "%{NAME} %|EPOCH?{%{EPOCH}}:{(no Epoch)}|\n" perl</code>
+ </div><pre class="screen">
+ perl 4
+</pre><div class="para">
+ If the package has a value for the <code class="literal">EPOCH</code> tag, you will see output as shown in this example. Most packages do not have an <code class="literal">EPOCH</code> defined, in which case, you will \ see output like the following:
+ </div><div class="para">
+ RPM files likely hold packages that are not installed. If you query one of these packages, you will get the alternative text, as shown following:
+ </div><div class="para">
+ <code class="command">rpm -q --qf "%{NAME} %|EPOCH?{%{EPOCH}}:{(no Epoch)}|\n" sendmail</code>
+ </div><pre class="screen">
+sendmail (no Epoch)
+</pre><div class="para">
+ See the "Getting Information on Package Files" section in this chapter for more on querying RPM package files. Other special-formatting options are described in the following sections on the dependency and file information tags.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="RPM_Guide-Using_RPM_DB-Formatting_arrays.html"><strong>Înapoi</strong>4.2.13. Formatting Arrays</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="RPM_Guide-Using_RPM_DB-querying_pacakge_dependencies.html"><strong>Înainte</strong>4.2.15. Querying for Package Dependencies</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/RPM_Guide-Using_RPM_DB-controlling_verification.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/RPM_Guide-Using_RPM_DB-controlling_verification.html
new file mode 100644
index 0000000..5653450
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/RPM_Guide-Using_RPM_DB-controlling_verification.html
@@ -0,0 +1,188 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>4.4.2.2. Controlling the verification</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="RPM-Guide-Using_RPM-DB-verifying_packages.html" title="4.4.2. Verifying Installed RPM Packages" /><link rel="prev" href="RPM-Guide-Using_RPM-DB-verifying_packages.html" title="4.4.2. Verifying Installed RPM Packages" /><link rel="next" href="RPM_GUide-Using_RPM_DB-working_with_RPM_db.html" title="4.4.3. Working With the RPM Database" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href
="RPM-Guide-Using_RPM-DB-verifying_packages.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="RPM_GUide-Using_RPM_DB-working_with_RPM_db.html"><strong>ÃŽnainte</strong></a></li></ul><div class="section" id="RPM_Guide-Using_RPM_DB-controlling_verification"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="RPM_Guide-Using_RPM_DB-controlling_verification">4.4.2.2. Controlling the verification</h4></div></div></div><div class="para">
+ You can use a number of options to tell the verification command specifically what to check for or not check for. Table 5-9 lists these options.
+ </div><div class="para">
+ Table 5-9 Controlling the verification
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Option
+ </div>
+
+ </td><td>
+ <div class="para">
+ Usage
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nodeps
+ </div>
+
+ </td><td>
+ <div class="para">
+ Don't verify dependencies.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nodigest
+ </div>
+
+ </td><td>
+ <div class="para">
+ Don't verify the package or header digests.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nofiles
+ </div>
+
+ </td><td>
+ <div class="para">
+ Don't verify the file attributes.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --noscripts
+ </div>
+
+ </td><td>
+ <div class="para">
+ Don't try to verify the scripts.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nosignature
+ </div>
+
+ </td><td>
+ <div class="para">
+ Don't verify the package or header signatures.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nolinkto
+ </div>
+
+ </td><td>
+ <div class="para">
+ Don't verify the link file attribute.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nomd5
+ </div>
+
+ </td><td>
+ <div class="para">
+ Don't verify the MD5 digest file attribute.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nosize
+ </div>
+
+ </td><td>
+ <div class="para">
+ Don't verify the file size attribute.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nouser
+ </div>
+
+ </td><td>
+ <div class="para">
+ Don't verify the file owner attribute.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nogroup
+ </div>
+
+ </td><td>
+ <div class="para">
+ Don't verify the file group owner attribute.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nomtime
+ </div>
+
+ </td><td>
+ <div class="para">
+ Don't verify the file mtime attribute.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nomode
+ </div>
+
+ </td><td>
+ <div class="para">
+ Don't verify the file mode attribute.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nordev
+ </div>
+
+ </td><td>
+ <div class="para">
+ Don't verify the file rdev attribute.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -a
+ </div>
+
+ </td><td>
+ <div class="para">
+ Verify all packages in a given group.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -g group
+ </div>
+
+ </td><td>
+ <div class="para">
+ Verify all packages in a given group.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -p file
+ </div>
+
+ </td><td>
+ <div class="para">
+ Verify the given RPM file.
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ The <code class="option">--nofiles</code> option is often used with <code class="option"> –Va</code> to verify the whole system but skip tests of file attributes. This command is used so often it has become an idiom for RPM usage, especially for debugging RPM problems. Run a command like the following:
+ </div><div class="para">
+ <code class="command">rpm -Va --nofiles</code>
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="RPM-Guide-Using_RPM-DB-verifying_packages.html"><strong>Înapoi</strong>4.4.2. Verifying Installed RPM Packages</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="RPM_GUide-Using_RPM_DB-working_with_RPM_db.html"><strong>Înainte</strong>4.4.3. Working With the RPM Database</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/RPM_Guide-Using_RPM_DB-file_state.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/RPM_Guide-Using_RPM_DB-file_state.html
new file mode 100644
index 0000000..c529b54
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/RPM_Guide-Using_RPM_DB-file_state.html
@@ -0,0 +1,91 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>4.2.6. Listing the state of the files in a package</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="RPM_Guide-Using_RPM_DB-getting_information.html" title="4.2. Getting Information on Packages" /><link rel="prev" href="ch04s02s05.html" title="4.2.5. Listing the documentation files for a package" /><link rel="next" href="RPM_Guide-Using_RPM_DB-listing_scripts.html" title="4.2.7. Listing the scripts in a package" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch04s02s05.html"><s
trong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="RPM_Guide-Using_RPM_DB-listing_scripts.html"><strong>ÃŽnainte</strong></a></li></ul><div class="section" id="RPM_Guide-Using_RPM_DB-file_state"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="RPM_Guide-Using_RPM_DB-file_state">4.2.6. Listing the state of the files in a package</h3></div></div></div><div class="para">
+ The <code class="option">–s</code> option to the <code class="command">rpm –q</code> command lists the state of each file in a package. The basic syntax is:
+ </div><div class="para">
+ <code class="command">rpm –qs <em class="replaceable"><code>package_name</code></em></code>
+ </div><div class="para">
+ For example:
+ </div><div class="para">
+ <code class="command">rpm -qs tcsh</code>
+ </div><pre class="screen">
+ normal /bin/csh
+ normal /bin/tcsh
+ normal /usr/share/doc/tcsh-6.10
+ normal /usr/share/doc/tcsh-6.10/FAQ
+ normal /usr/share/doc/tcsh-6.10/Fixes
+ normal /usr/share/doc/tcsh-6.10/NewThings
+ normal /usr/share/doc/tcsh-6.10/complete.tcsh
+ normal /usr/share/doc/tcsh-6.10/eight-bit.txt
+ normal /usr/share/doc/tcsh-6.10/tcsh.html
+ normal /usr/share/doc/tcsh-6.10/tcsh.html/header.html
+ normal /usr/share/doc/tcsh-6.10/tcsh.html/index.html
+ normal /usr/share/doc/tcsh-6.10/tcsh.html/lists.html
+ normal /usr/share/doc/tcsh-6.10/tcsh.html/tcsh.man
+ normal /usr/share/doc/tcsh-6.10/tcsh.html/tcsh.man2html
+ normal /usr/share/doc/tcsh-6.10/tcsh.html/top.html
+ not installed /usr/share/locale/de/LC_MESSAGES/tcsh
+ not installed /usr/share/locale/el/LC_MESSAGES/tcsh
+ not installed /usr/share/locale/es/LC_MESSAGES/tcsh
+ not installed /usr/share/locale/fr/LC_MESSAGES/tcsh
+ not installed /usr/share/locale/it/LC_MESSAGES/tcsh
+ not installed /usr/share/locale/ja/LC_MESSAGES/tcsh
+ normal /usr/share/man/man1/tcsh.1.gz
+</pre><div class="para">
+ You can also use the long option, <code class="option">--state</code>, in place of <code class="option">–s</code>.
+ </div><div class="para">
+ You can combine the <code class="option">–s</code> option with other file filters, such as <code class="option">–d</code>, for listing only the documentation files for a package.
+ </div><div class="para">
+ Table 5-2 lists the states that RPM supports.
+ </div><div class="para">
+ Table 5-2 RPM File States
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ State
+ </div>
+
+ </td><td>
+ <div class="para">
+ Usage
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ normal
+ </div>
+
+ </td><td>
+ <div class="para">
+ The file has been installed.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ not installed
+ </div>
+
+ </td><td>
+ <div class="para">
+ The file from the package is not installed.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ replaced
+ </div>
+
+ </td><td>
+ <div class="para">
+ The file has been replaced.
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ Sometimes files in a package may have been skipped during installation with options such as <code class="option">--excludedocs</code>. This can lead to non-normal states. You may have also modified files installed from a given package.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch04s02s05.html"><strong>Înapoi</strong>4.2.5. Listing the documentation files for a pack...</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="RPM_Guide-Using_RPM_DB-listing_scripts.html"><strong>Înainte</strong>4.2.7. Listing the scripts in a package</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/RPM_Guide-Using_RPM_DB-getting_information.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/RPM_Guide-Using_RPM_DB-getting_information.html
new file mode 100644
index 0000000..c51d9f0
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/RPM_Guide-Using_RPM_DB-getting_information.html
@@ -0,0 +1,45 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>4.2. Getting Information on Packages</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-using-rpm-db.html" title="Cap. 4. Using the RPM Database" /><link rel="prev" href="ch-using-rpm-db.html" title="Cap. 4. Using the RPM Database" /><link rel="next" href="RPM_Guide-Using_RPM_DB-package_groups.html" title="4.2.2. Package groups" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-using-rpm-db.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n"
href="RPM_Guide-Using_RPM_DB-package_groups.html"><strong>ÃŽnainte</strong></a></li></ul><div class="section" id="RPM_Guide-Using_RPM_DB-getting_information"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="RPM_Guide-Using_RPM_DB-getting_information">4.2. Getting Information on Packages</h2></div></div></div><div class="para">
+ The query options for the rpm command include a whole set of options that return information about the files that make up a package, the scripts, and other parts of the original package. The following sections cover these options.
+ </div><div class="section" id="RPM_Guide-USing_RPM_DB-getting_information-describing_packages"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="RPM_Guide-USing_RPM_DB-getting_information-describing_packages">4.2.1. Describing packages</h3></div></div></div><div class="para">
+ The <code class="option">–i</code> option with an rpm query command tells the rpm command to output descriptive information about the package. You can also use the longer option, <code class="option">--info</code>, in place of <code class="option">–i</code>. The basic syntax is:
+ </div><div class="para">
+ <code class="command">rpm -qi <em class="replaceable"><code>package</code></em></code>
+ </div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ The order of the command-line options is very important. Remember that the rpm command has the following general syntax:
+ </div><div class="para">
+ <code class="command">rpm <em class="replaceable"><code>–MajorOperation</code></em> <em class="replaceable"><code>–extra_options packages_or_files</code></em></code>
+ </div><div class="para">
+ <code class="command">rpm –i</code> installs packages and <code class="command">rpm –q</code> queries packages. The <code class="command">rpm –qi</code> command outputs the descriptive information on packages. If you make a mistake and place the <code class="literal">i</code> in front of the <code class="literal">q</code>, you are telling the rpm command to perform a different operation.
+ </div></div></div><div class="para">
+ When you run this command, being very careful with the order of the options, you’ll see output like the following, which describes the tcsh shell package.
+ </div><div class="para">
+ <code class="command">rpm -qi tcsh-6.17-6</code>
+ </div><pre class="screen">Name : tcsh Relocations: (not relocateable)
+Version : 6.17 Vendor: Fedora Project
+Release : 6 Build Date: Tue 15 Dec 2009 11:28:11 AM EST
+Install Date: Fri 27 Aug 2010 07:41:03 PM EDT Build Host: localhost
+Group : System Environment/Shells Source RPM: tcsh-6.17-6.fc13.src.rpm
+Size : 1191282 License: BSD
+Signature : RSA/SHA256, Fri 05 Feb 2010 09:30:43 AM EST, Key ID 7edc6ad6e8e40fde
+Packager : Fedora Project
+URL : http://www.tcsh.org/
+Summary : An enhanced version of csh, the C shell
+Description :
+Tcsh is an enhanced but completely compatible version of csh, the C
+shell. Tcsh is a command language interpreter which can be used both
+as an interactive login shell and as a shell script command processor.
+Tcsh includes a command line editor, programmable word completion,
+spelling correction, a history mechanism, job control and a C language
+like syntax.
+</pre><div class="para">
+ The sections on custom queries following in this chapter show how you can query for any information stored in a package header, including all of the information shown with <code class="command">rpm –qi</code>, as well as any other header tag.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-using-rpm-db.html"><strong>Înapoi</strong>Cap. 4. Using the RPM Database</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="RPM_Guide-Using_RPM_DB-package_groups.html"><strong>Înainte</strong>4.2.2. Package groups</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/RPM_Guide-Using_RPM_DB-listing_conf_files.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/RPM_Guide-Using_RPM_DB-listing_conf_files.html
new file mode 100644
index 0000000..1a249b7
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/RPM_Guide-Using_RPM_DB-listing_conf_files.html
@@ -0,0 +1,58 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>4.2.4. Listing the configuration files for a package</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="RPM_Guide-Using_RPM_DB-getting_information.html" title="4.2. Getting Information on Packages" /><link rel="prev" href="ch04s02s03.html" title="4.2.3. Listing the files in a package" /><link rel="next" href="ch04s02s05.html" title="4.2.5. Listing the documentation files for a package" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch04s02s03.html"><strong>ÃŽnapoi</strong></a></li
><li class="next"><a accesskey="n" href="ch04s02s05.html"><strong>ÃŽnainte</strong></a></li></ul><div class="section" id="RPM_Guide-Using_RPM_DB-listing_conf_files"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="RPM_Guide-Using_RPM_DB-listing_conf_files">4.2.4. Listing the configuration files for a package</h3></div></div></div><div class="para">
+ The <code class="option">–c</code> option tells <code class="command">rpm –q</code> to list the configuration files for a package. You can also use the longer option, <code class="option">--configfiles</code>, in place of <code class="option">–c</code>. The basic syntax is:
+ </div><div class="para">
+ <code class="command">rpm –qc <em class="replaceable"><code>package_name</code></em></code>
+ </div><div class="para">
+ For example:
+ </div><div class="para">
+ <code class="command">rpm -qc bash</code>
+ </div><pre class="screen">
+ /etc/skel/.bash_logout
+ /etc/skel/.bash_profile
+ /etc/skel/.bashrc
+</pre><div class="para">
+ This command lists the configuration files for the bash package.
+ </div><div class="para">
+ Some packages don’t have configuration files, as shown following:
+ </div><div class="para">
+ <code class="command">rpm -qc python</code>
+ </div><pre class="screen">
+
+</pre><div class="para">
+ In this case, the rpm command provides no output. Other packages have a lot of configuration files, such as the sendmail mail transfer agent, as shown following:
+ </div><div class="para">
+ <code class="command">rpm -qc sendmail</code>
+ </div><pre class="screen">
+ /etc/aliases
+ /etc/mail/Makefile
+ /etc/mail/access
+ /etc/mail/domaintable
+ /etc/mail/helpfile
+ /etc/mail/local-host-names
+ /etc/mail/mailertable
+ /etc/mail/sendmail.mc
+ /etc/mail/statistics
+ /etc/mail/trusted-users
+ /etc/mail/virtusertable
+ /etc/rc.d/init.d/sendmail
+ /etc/sendmail.cf
+ /etc/sysconfig/sendmail
+ /usr/lib/sasl/Sendmail.conf
+</pre><div class="para">
+ As with the <code class="option">–l</code> option, the <code class="option">–v</code> option provides more information on each file, as shown following:
+ </div><div class="para">
+ <code class="command">rpm -qcv bash</code>
+ </div><pre class="screen">
+-rw-r--r-- 1 root root 18 May 21 13:32 /etc/skel/.bash_logout
+-rw-r--r-- 1 root root 176 May 21 13:32 /etc/skel/.bash_profile
+-rw-r--r-- 1 root root 124 May 21 13:32 /etc/skel/.bashrc
+</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch04s02s03.html"><strong>Înapoi</strong>4.2.3. Listing the files in a package</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch04s02s05.html"><strong>Înainte</strong>4.2.5. Listing the documentation files for a pack...</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/RPM_Guide-Using_RPM_DB-listing_scripts.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/RPM_Guide-Using_RPM_DB-listing_scripts.html
new file mode 100644
index 0000000..bb23ad6
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/RPM_Guide-Using_RPM_DB-listing_scripts.html
@@ -0,0 +1,89 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>4.2.7. Listing the scripts in a package</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="RPM_Guide-Using_RPM_DB-getting_information.html" title="4.2. Getting Information on Packages" /><link rel="prev" href="RPM_Guide-Using_RPM_DB-file_state.html" title="4.2.6. Listing the state of the files in a package" /><link rel="next" href="RPM_Guide-Using_RPM_DB-Listing_changed.html" title="4.2.8. Listing what has changed" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="RPM_Gu
ide-Using_RPM_DB-file_state.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="RPM_Guide-Using_RPM_DB-Listing_changed.html"><strong>ÃŽnainte</strong></a></li></ul><div class="section" id="RPM_Guide-Using_RPM_DB-listing_scripts"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="RPM_Guide-Using_RPM_DB-listing_scripts">4.2.7. Listing the scripts in a package</h3></div></div></div><div class="para">
+ RPM packages can have preinstallation, postinstallation, preuninstallation, and postuninstallation scripts. These are scripts that the rpm command will execute before and after installing a package, as well as before and after removing the package. The <code class="option">--scripts</code> option to the <code class="command">rpm –q</code> command lists the scripts associated with a package. The basic syntax follows:
+ </div><div class="para">
+ <code class="command">rpm -q --scripts <em class="replaceable"><code>package_name</code></em></code>
+ </div><div class="para">
+ For example:
+ </div><div class="para">
+ <code class="command">rpm -q --scripts tcsh</code>
+ </div><pre class="screen">
+if [ ! -f /etc/shells ]; then
+ echo "/bin/tcsh" >> /etc/shells
+ echo "/bin/csh" >> /etc/shells
+else
+ grep -q '^/bin/tcsh$' /etc/shells || \
+ echo "/bin/tcsh" >> /etc/shells
+ grep -q '^/bin/csh$' /etc/shells || \
+ echo "/bin/csh" >> /etc/shells
+fi
+postuninstall scriptlet (using /bin/sh):
+if [ ! -x /bin/tcsh ]; then
+ grep -v '^/bin/tcsh$' /etc/shells | \
+ grep -v '^/bin/csh$' > /etc/shells.rpm && \
+ mv /etc/shells.rpm /etc/shells
+fi
+</pre><div class="para">
+ The simple scripts shown here add an entry to the /etc/shells file and clean up the entry when uninstalled.
+ </div><div class="important"><div class="admonition_header"><h2>Cleaning up</h2></div><div class="admonition"><div class="para">
+ Cleaning up any changes your package makes on uninstallation is a very good idea. See the chapters in Part II, Creating RPMs, for details on making your own well-behaved packages.
+ </div></div></div><div class="para">
+ Other packages have more complex scripts, as shown following:
+ </div><div class="para">
+ <code class="command">rpm -q --scripts sendmail</code>
+ </div><pre class="screen">
+preinstall scriptlet (using /bin/sh):
+/usr/sbin/useradd -u 47 -d /var/spool/mqueue -r -s /sbin/nologin mailnull >/dev/null 2>&1
+/usr/sbin/useradd -u 51 -d /var/spool/mqueue -r -s /sbin/nologin smmsp >/dev/null 2>&1
+exit 0
+postinstall scriptlet (using /bin/sh):
+/sbin/chkconfig --add sendmail
+# Set up the alternatives files for MTAs.
+/usr/sbin/alternatives --install /usr/sbin/sendmail mta /usr/sbin/sendmail.sendmail 90 \
+ --slave /usr/bin/mailq mta-mailq /usr/bin/mailq.sendmail \
+ --slave /usr/bin/newaliases mta-newaliases /usr/bin/newaliases.sendmail \
+ --slave /usr/bin/rmail mta-rmail /usr/bin/rmail.sendmail \
+ --slave /usr/lib/sendmail mta-sendmail /usr/lib/sendmail.sendmail \
+ --slave /etc/pam.d/smtp mta-pam /etc/pam.d/smtp.sendmail \
+ --slave /usr/share/man/man8/sendmail.8.gz mta-sendmailman /usr/share/man/man8/sendmail.sendmail.8.gz \
+ --slave /usr/share/man/man1/mailq.1.gz mta-mailqman /usr/share/man/man1/mailq.sendmail.1.gz \
+ --slave /usr/share/man/man1/newaliases.1.gz mta-newaliasesman /usr/share/man/man1/newaliases.sendmail.1.gz \
+ --slave /usr/share/man/man5/aliases.5.gz mta-aliasesman /usr/share/man/man5/aliases.sendmail.5.gz \
+ --initscript sendmail
+
+# Rebuild maps
+{
+ chown root /etc/aliases.db /etc/mail/access.db \
+ /etc/mail/mailertable.db /etc/mail/domaintable.db \
+ /etc/mail/virtusertable.db
+ SM_FORCE_DBREBUILD=1 /etc/mail/make
+ SM_FORCE_DBREBUILD=1 /etc/mail/make aliases
+} > /dev/null 2>&1
+exit 0
+preuninstall scriptlet (using /bin/sh):
+if [ $1 = 0 ]; then
+ /etc/rc.d/init.d/sendmail stop >/dev/null 2>&1
+ /sbin/chkconfig --del sendmail
+ /usr/sbin/alternatives --remove mta /usr/sbin/sendmail.sendmail
+fi
+exit 0
+postuninstall scriptlet (using /bin/sh):
+if [ "$1" -ge "1" ]; then
+ /etc/rc.d/init.d/sendmail condrestart >/dev/null 2>&1
+ mta=`readlink /etc/alternatives/mta`
+ if [ "$mta" == "/usr/sbin/sendmail.sendmail" ]; then
+ /usr/sbin/alternatives --set mta /usr/sbin/sendmail.sendmail
+ fi
+fi
+exit 0
+</pre><div class="para">
+ In this case, the main script is the post-install script, which tries to convert old-format data into the new format, thereby helping users upgrade to the newer release.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="RPM_Guide-Using_RPM_DB-file_state.html"><strong>Înapoi</strong>4.2.6. Listing the state of the files in a package</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="RPM_Guide-Using_RPM_DB-Listing_changed.html"><strong>Înainte</strong>4.2.8. Listing what has changed</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/RPM_Guide-Using_RPM_DB-new_db.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/RPM_Guide-Using_RPM_DB-new_db.html
new file mode 100644
index 0000000..ee518d8
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/RPM_Guide-Using_RPM_DB-new_db.html
@@ -0,0 +1,29 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>4.4.3.3. Creating a new RPM database</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="RPM_GUide-Using_RPM_DB-working_with_RPM_db.html" title="4.4.3. Working With the RPM Database" /><link rel="prev" href="RPM_Guide-Using_RPM_DB-rebuilding_RPM-db.html" title="4.4.3.2. Rebuilding the RPM database" /><link rel="next" href="RPM_Guide-Using_RPM_DB-summary.html" title="4.4.4. Summary" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="RPM_Guide-Using_RPM_DB-rebuilding_RPM-
db.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="RPM_Guide-Using_RPM_DB-summary.html"><strong>ÃŽnainte</strong></a></li></ul><div class="section" id="RPM_Guide-Using_RPM_DB-new_db"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="RPM_Guide-Using_RPM_DB-new_db">4.4.3.3. Creating a new RPM database</h4></div></div></div><div class="para">
+ If all else fails, use the <code class="option">--initdb</code> option to tell the rpm command to create a new empty RPM database. In almost all cases, you do not want to create a new RPM database, since this database will be empty. It will not have any knowledge about the packages you have already installed on your system. That could lead to a lot of problems, since you have the files installed, but the RPM system just doesn’t know about them.
+ </div><div class="para">
+ The basic syntax follows.
+ </div><div class="para">
+ <code class="command">rpm --initdb</code>
+ </div><div class="para">
+ If the RPM system cannot be rebuilt, you may have to reinstall the operating system to recreate a clean system. In general, if things are this far gone, reinstalling may be your best answer instead of wiping the RPM database and creating an empty database.
+ </div><div class="para">
+ You can also use the <code class="option">--dbpath</code> option to tell the rpm command to create an RPM database in a different directory.
+ </div><div class="para">
+ For example:
+ </div><pre class="screen">
+ mkdir /tmp/rpm
+ rpm --initdb --dbpath /tmp/rpm
+</pre><div class="para">
+ These commands create a temporary directory and an RPM database in the /tmp/rpm directory.
+ </div><div class="para">
+ After running this command, you can examine the files created.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="RPM_Guide-Using_RPM_DB-rebuilding_RPM-db.html"><strong>Înapoi</strong>4.4.3.2. Rebuilding the RPM database</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="RPM_Guide-Using_RPM_DB-summary.html"><strong>Înainte</strong>4.4.4. Summary</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/RPM_Guide-Using_RPM_DB-package_groups.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/RPM_Guide-Using_RPM_DB-package_groups.html
new file mode 100644
index 0000000..a6cd867
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/RPM_Guide-Using_RPM_DB-package_groups.html
@@ -0,0 +1,24 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>4.2.2. Package groups</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="RPM_Guide-Using_RPM_DB-getting_information.html" title="4.2. Getting Information on Packages" /><link rel="prev" href="RPM_Guide-Using_RPM_DB-getting_information.html" title="4.2. Getting Information on Packages" /><link rel="next" href="ch04s02s03.html" title="4.2.3. Listing the files in a package" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="RPM_Guide-Using_RPM_DB-getting_in
formation.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch04s02s03.html"><strong>ÃŽnainte</strong></a></li></ul><div class="section" id="RPM_Guide-Using_RPM_DB-package_groups"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="RPM_Guide-Using_RPM_DB-package_groups">4.2.2. Package groups</h3></div></div></div><div class="para">
+ RPM packages can be placed into groups, merely arbitrary names for a set of packages. The <code class="command">rpm –qi</code> command, shown previously, lists the group for a package, if there is one. For the tcsh package shown in the previous example, the package is <code class="literal">System Environment/Shells</code>.
+ </div><div class="para">
+ The <code class="option">–g</code> option to <code class="command">rpm –q</code> tells rpm to list all the packages in a given group. You can also use the longer option, <code class="option">--group</code>, in place of <code class="option">–g</code>. The basic syntax follows:
+ </div><div class="para">
+ <code class="command">rpm –qg <em class="replaceable"><code>group_name</code></em></code>
+ </div><div class="para">
+ For example:
+ </div><div class="para">
+ <code class="command">rpm -qg "System Environment/Shells"</code>
+ </div><pre class="screen">dash-0.5.5.1-3.x86_64
+bash-4.1.7-1.x86_64
+tcsh-6.17-6.x86_64</pre><div class="note"><div class="admonition_header"><h2>Spaces in group names</h2></div><div class="admonition"><div class="para">
+ This group has a space in its name, so you need quotation marks to pass the group name as one parameter to the rpm command.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="RPM_Guide-Using_RPM_DB-getting_information.html"><strong>Înapoi</strong>4.2. Getting Information on Packages</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch04s02s03.html"><strong>Înainte</strong>4.2.3. Listing the files in a package</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/RPM_Guide-Using_RPM_DB-querying_pacakge_dependencies.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/RPM_Guide-Using_RPM_DB-querying_pacakge_dependencies.html
new file mode 100644
index 0000000..98773d5
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/RPM_Guide-Using_RPM_DB-querying_pacakge_dependencies.html
@@ -0,0 +1,190 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>4.2.15. Querying for Package Dependencies</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="RPM_Guide-Using_RPM_DB-getting_information.html" title="4.2. Getting Information on Packages" /><link rel="prev" href="RPM_Guide-Using_RPM_DB-Special_formatting.html" title="4.2.14. Special Formatting" /><link rel="next" href="RPM-Guide-Using_RPM_DB-Querying_file_information.html" title="4.2.16. Querying for File Information" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="RPM_Gu
ide-Using_RPM_DB-Special_formatting.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="RPM-Guide-Using_RPM_DB-Querying_file_information.html"><strong>ÃŽnainte</strong></a></li></ul><div class="section" id="RPM_Guide-Using_RPM_DB-querying_pacakge_dependencies"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="RPM_Guide-Using_RPM_DB-querying_pacakge_dependencies">4.2.15. Querying for Package Dependencies</h3></div></div></div><div class="para">
+ A number of tags provide package dependency information. Each of these tags comes in triples, which are formatted similarly. For example, for the capabilities a package requires, you have the REQUIRENAME, REQUIREVERSION, and REQUIREFLAGS tags.
+ </div><div class="para">
+ The REQUIRENAME tag holds an array of required capability names. The REQUIREVERSION tag holds an array of the versions of the required capabilities. The REQUIREFLAGS tag ties the two together with a set of bit flags that specify whether the requirement is for a version less than the given number, equal to the given number, greater than or equal to the given number, and so on.
+ </div><div class="para">
+ Table 5-4 lists the dependency tags.
+ </div><div class="para">
+ Table 5-4 Dependency query tags
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Tag
+ </div>
+
+ </td><td>
+ <div class="para">
+ Holds
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ CONFLICTFLAGS
+ </div>
+
+ </td><td>
+ <div class="para">
+ Array of flags for the capabilities this package conflicts
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ CONFLICTNAME
+ </div>
+
+ </td><td>
+ <div class="para">
+ Array of capabilities that this package conflicts
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ CONFLICTVERSION
+ </div>
+
+ </td><td>
+ <div class="para">
+ Array of version numbers that this package conflicts
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ REQUIREFLAGS
+ </div>
+
+ </td><td>
+ <div class="para">
+ Array of flags for the capabilities this package requires
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ REQUIRENAME
+ </div>
+
+ </td><td>
+ <div class="para">
+ Array of capabilities that this package requires
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ REQUIREVERSION
+ </div>
+
+ </td><td>
+ <div class="para">
+ Array of version numbers that this package requires
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ OBSOLETENAME
+ </div>
+
+ </td><td>
+ <div class="para">
+ Array of capabilities that this package obsoletes
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ OBSOLETEFLAGS
+ </div>
+
+ </td><td>
+ <div class="para">
+ Array of flags for the capabilities this package obsoletes
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ OBSOLETEVERSION
+ </div>
+
+ </td><td>
+ <div class="para">
+ Array of version numbers that this package obsoletes
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ PROVIDENAME
+ </div>
+
+ </td><td>
+ <div class="para">
+ Array of capabilities that this package provides
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ PROVIDEFLAGS
+ </div>
+
+ </td><td>
+ <div class="para">
+ Array of flags for the capabilities this package provides
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ PROVIDEVERSION
+ </div>
+
+ </td><td>
+ <div class="para">
+ Array of version numbers that this package provides
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ Each of these tags is an array. The PROVIDENAME, PROVIDEVERSION, and PROVIDEFLAGS tags work similarly for the capabilities this package provides. The CONFLICTNAME, CONFLICTVERSION, and CONFLICTFLAGS tags specify the conflicts, and, the OBSOLETENAME, OBSOLETEVERSION, and OBSOLETEFLAGS tags specify the obsolete dependencies.
+ </div><div class="para">
+ The depflags special-formatting option prints out the flag tags, such as REQUIREFLAGS, in human-readable format. For example, the following command lists the requirements for a package:
+ </div><div class="para">
+ $ rpm -q --qf \
+ </div><div class="para">
+ "[%{REQUIRENAME} %{REQUIREFLAGS:depflags} %{REQUIREVERSION}\n]" sendmail
+ </div><div class="para">
+ rpmlib(VersionedDependencies) <= 3.0.3-1
+ </div><div class="para">
+ chkconfig >= 1.3
+ </div><div class="para">
+ /usr/sbin/useradd
+ </div><div class="para">
+ /bin/mktemp
+ </div><div class="para">
+ fileutils
+ </div><div class="para">
+ gawk
+ </div><div class="para">
+ sed
+ </div><div class="para">
+ sh-utils
+ </div><div class="para">
+ procmail
+ </div><div class="para">
+ bash >= 2.0
+ </div><div class="para">
+ /bin/sh
+ </div><div class="para">
+ rpmlib(PayloadFilesHavePrefix) <= 4.0-1
+ </div><div class="para">
+ rpmlib(CompressedFileNames) <= 3.0.4-1
+ </div><div class="para">
+ For those requirements that have specific version numbers, this command prints out the version number along with the operator, such as >= for a version greater than or equal to the given number.
+ </div><div class="para">
+ Note that for many of the requirements, there is no specific version information.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ In addition to normal capabilities, most packages will have some RPM-related requirements as well, which specify any required RPM versions, for example, rpmlib(CompressedFileNames).
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="RPM_Guide-Using_RPM_DB-Special_formatting.html"><strong>Înapoi</strong>4.2.14. Special Formatting</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="RPM-Guide-Using_RPM_DB-Querying_file_information.html"><strong>Înainte</strong>4.2.16. Querying for File Information</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/RPM_Guide-Using_RPM_DB-rebuilding_RPM-db.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/RPM_Guide-Using_RPM_DB-rebuilding_RPM-db.html
new file mode 100644
index 0000000..180560f
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/RPM_Guide-Using_RPM_DB-rebuilding_RPM-db.html
@@ -0,0 +1,20 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>4.4.3.2. Rebuilding the RPM database</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="RPM_GUide-Using_RPM_DB-working_with_RPM_db.html" title="4.4.3. Working With the RPM Database" /><link rel="prev" href="RPM_GUide-Using_RPM_DB-working_with_RPM_db.html" title="4.4.3. Working With the RPM Database" /><link rel="next" href="RPM_Guide-Using_RPM_DB-new_db.html" title="4.4.3.3. Creating a new RPM database" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="RPM_GUide-Using
_RPM_DB-working_with_RPM_db.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="RPM_Guide-Using_RPM_DB-new_db.html"><strong>ÃŽnainte</strong></a></li></ul><div class="section" id="RPM_Guide-Using_RPM_DB-rebuilding_RPM-db"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="RPM_Guide-Using_RPM_DB-rebuilding_RPM-db">4.4.3.2. Rebuilding the RPM database</h4></div></div></div><div class="para">
+ If the RPM database has been corrupted in some way, you can use the <code class="option">--rebuilddb</code> option to tell the rpm command to rebuild your database. For example:
+ </div><div class="para">
+ <code class="command">rpm --rebuilddb</code>
+ </div><div class="para">
+ This command rebuilds the RPM database from the installed packages, the file named <code class="filename">Packages</code> in the /var/lib/rpm directory. Only the <code class="filename">Packages</code> file is required. All the other files can be recreated from the <code class="filename">Packages</code> file. If your database is OK, this command won't do much, other than shrink the size of your RPM database by removing unused entries. This command will take some time to execute, though.
+ </div><div class="warning"><div class="admonition_header"><h2>Avertisment</h2></div><div class="admonition"><div class="para">
+ Before running this command, back up your RPM database.
+ </div></div></div><div class="para">
+ To check that the <code class="command">rpm --rebuilddb</code> command has not damaged the RPM database, you can check with a file listing, query all packages, and then check the results of the <code class="command">rpm –rebuilddb</code> command with another file listing when done.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="RPM_GUide-Using_RPM_DB-working_with_RPM_db.html"><strong>Înapoi</strong>4.4.3. Working With the RPM Database</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="RPM_Guide-Using_RPM_DB-new_db.html"><strong>Înainte</strong>4.4.3.3. Creating a new RPM database</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/RPM_Guide-Using_RPM_DB-summary.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/RPM_Guide-Using_RPM_DB-summary.html
new file mode 100644
index 0000000..84a274e
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/RPM_Guide-Using_RPM_DB-summary.html
@@ -0,0 +1,16 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>4.4.4. Summary</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="RPM_Guide-Using_RPM_DB-Getting_information_on_package_files.html" title="4.4. Getting Information on Package Files" /><link rel="prev" href="RPM_Guide-Using_RPM_DB-new_db.html" title="4.4.3.3. Creating a new RPM database" /><link rel="next" href="ch-dependencies.html" title="Cap. 5. Package Dependencies" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="RPM_Guide-Using_RPM_DB-new_d
b.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch-dependencies.html"><strong>ÃŽnainte</strong></a></li></ul><div class="section" id="RPM_Guide-Using_RPM_DB-summary"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="RPM_Guide-Using_RPM_DB-summary">4.4.4. Summary</h3></div></div></div><div class="para">
+ This chapter covers the rpm command options to query the RPM database and RPM package files. You can determine the packages installed on your system, as well as which packages are responsible for the files on your system.
+ </div><div class="para">
+ The RPM database maintains a lot of information about the files and packages on your system. Thus, it is crucial for managing your Linux systems. You should back up the RPM database before and after any installation, upgrade, or removal of packages.
+ </div><div class="para">
+ You can also use the <code class="option">--rebuilddb</code> option to the rpm command to rebuild a damaged RPM database.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="RPM_Guide-Using_RPM_DB-new_db.html"><strong>Înapoi</strong>4.4.3.3. Creating a new RPM database</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch-dependencies.html"><strong>Înainte</strong>Cap. 5. Package Dependencies</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/appe-Publican-Revision_History.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/appe-Publican-Revision_History.html
new file mode 100644
index 0000000..99ce8ac
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/appe-Publican-Revision_History.html
@@ -0,0 +1,16 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Anexa A. Istoria reviziilor</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="index.html" title="Ghid RPM" /><link rel="prev" href="ch-licensing.html" title="Cap. 27. Licensing RPM" /><link rel="next" href="ix01.html" title="Index" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-licensing.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ix01.html"><strong>ÃŽnainte</strong></a></li></ul><div xml:lang="ro" class="appendix" id
="appe-Publican-Revision_History" lang="ro"><div class="titlepage"><div><div><h1 class="title">Istoria reviziilor</h1></div></div></div><div class="para">
+ <div class="revhistory"><table border="0" width="100%" summary="Revision history"><tr><th align="left" valign="top" colspan="3"><strong>Istoricul versiunilor</strong></th></tr><tr><td align="left">Versiune 1.0</td><td align="left"></td><td align="left"><span class="author"><span class="firstname"></span> <span class="surname"></span></span></td></tr><tr><td align="left" colspan="3">
+ <table border="0" summary="Simple list" class="simplelist"><tr><td></td></tr></table>
+
+ </td></tr></table></div>
+
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-licensing.html"><strong>Înapoi</strong>Cap. 27. Licensing RPM</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ix01.html"><strong>Înainte</strong>Index</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-advanced-packaging.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-advanced-packaging.html
new file mode 100644
index 0000000..9f3ef01
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-advanced-packaging.html
@@ -0,0 +1,210 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Cap. 10. Creare avansată pachete RPM</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="index.html" title="Ghid RPM" /><link rel="prev" href="ch09s09.html" title="9.9. Summary" /><link rel="next" href="ch10s02.html" title="10.2. Setarea triggerelor" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch09s09.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch10s02.html"><strong>ÃŽnainte</strong></a></li></ul><div xml:lang="ro" class="chapte
r" id="ch-advanced-packaging" lang="ro"><div class="titlepage"><div><div><h2 class="title">Cap. 10. Creare avansată pachete RPM</h2></div></div></div><div class="toc"><dl><dt><span class="sect1"><a href="ch-advanced-packaging.html#id662011">10.1. Definirea dependențelor pachetelor</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch-advanced-packaging.html#id507149">10.1.1. Numirea dependențelor</a></span></dt><dt><span class="sect2"><a href="ch-advanced-packaging.html#id666574">10.1.2. Setarea premiselor</a></span></dt><dt><span class="sect2"><a href="ch-advanced-packaging.html#id666618">10.1.3. Numirea dependențelor de construcție</a></span></dt><dt><span class="sect2"><a href="ch-advanced-packaging.html#id666660">10.1.4. Generarea automată de dependențe</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch10s02.html">10.2. Setarea triggerelor</a></span></dt><dt><span class="sect1"><a href="ch10s03.html">10.3. Scrierea scripturilor de verificare</a></sp
an></dt><dt><span class="sect1"><a href="ch10s04.html">10.4. Crearea subpachetelor.</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch10s04.html#id776325">10.4.1. Furnizarea informațiilor pentru subpachete</a></span></dt><dt><span class="sect2"><a href="ch10s04s02.html">10.4.2. Definirea scripturilor pentru subpachete</a></span></dt><dt><span class="sect2"><a href="ch10s04s03.html">10.4.3. Construirea subpachetelor</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch10s05.html">10.5. Creating Relocatable Packages</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch10s05.html#id785850">10.5.1. Setting up the prefixes</a></span></dt><dt><span class="sect2"><a href="ch10s05s02.html">10.5.2. Define the files section</a></span></dt><dt><span class="sect2"><a href="ch10s05s03.html">10.5.3. Problems creating relocatable packages</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch10s06.html">10.6. Defining Conditional Builds</a></span></dt><dd><dl><dt
><span class="sect2"><a href="ch10s06.html#id763642">10.6.1. Defining conditional macros</a></span></dt><dt><span class="sect2"><a href="ch10s06s02.html">10.6.2. Using conditional blocks</a></span></dt><dt><span class="sect2"><a href="ch10s06s03.html">10.6.3. Using architecture-based conditionals</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch10s07.html">10.7. Summary</a></span></dt></dl></div><div class="para">
+ Acest capitol acoperă:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Se definește informația despre dependențele pachetelor
+ </div></li><li class="listitem"><div class="para">
+ Setare trigger-e
+ </div></li><li class="listitem"><div class="para">
+ Scriere scripturi de verificare
+ </div></li><li class="listitem"><div class="para">
+ Creare subpachete
+ </div></li><li class="listitem"><div class="para">
+ Creare pachete relocabile
+ </div></li><li class="listitem"><div class="para">
+ Definire construcții condiționale
+ </div></li></ul></div><div class="para">
+ Capitolul anterior a introdus fișierul spec RPM, care controlează cum sunt construite și instalate pachetele RPM. Acest capitol intră mai adânc în subiecte mai avansate despre fișiere spec cum ar fi utilizarea comenzilor condiționale și creare de pachete relocabile, începând cu instrucțiuni despre cum să specificați dependențele pachetelor
+ </div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id662011" class="title">Definirea dependențelor pachetelor</h1></div></div></div><div class="para">
+ Dependențele sunt una dintre cele mai importante părți ale sistemului RPM. Baza de date RPM caută dependențele între pachete pentru a vă permite să vă administrați sistemul mai bine. Dependențele apar când un pachet depinde de un altul. Sistemul RPM se asigură că dependențele sunt îndeplinite la actualizare, instalare sau la ștergerea pachetelor. Pornind de la acest concept simplu, RPM suportă patru tipuri de dependențe:
+ </div><div class="para">
+ *Requirements (cerințe), unde un pachet cere o capabilitate asigurată de către alt pachet.
+ </div><div class="para">
+ *Provides (asigură), o listă de capabilități asigurate de pachetul dvs.
+ </div><div class="para">
+ *Conflicts (conflict), unde un pachet este în conflict cu o capabilitate asigurată de alt pachet
+ </div><div class="para">
+ *Obsoletes (scos din uz), unde un pachet scoate din uz capabilitățiasigurate de un altul.
+ </div><div class="para">
+ Referință încrucișată
+ </div><div class="para">
+ <a class="xref" href="ch-dependencies.html">Cap. 5, <em>Package Dependencies</em></a> are mai multe informații despre dependențe.Dependențele tip obsoletes sunt folosite de obicei doar când un pachet este redenumit, ca de exemplu pachetul apache care a devenit httpd, începând cu Red Hat Linux 8.0. Pachetul httpd scoate din uz pachetul apache.
+ </div><div class="para">
+ Puteți enumera toate dependențele în fișierul dvs. spec. Cea mai folosită informație legată de dependențe este cea legată de cerințele unui pachet.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id507149" class="title">Numirea dependențelor</h1></div></div></div><div class="para">
+ În fișierele dvs. spec puteți numi dependențele pentru pachetul dvs. Sintaxa de bază este:
+ </div><div class="para">
+ Requires: capabilitate
+ </div><div class="para">
+ În cele mai multe cazuri, capabilitatea ar trebui să fie numele unui alt pachet. Acest exemplu setează o dependență de tip requires. Acest lucru înseamnă că pachetul cere acea capabilitate. Folosiți o sintaxă asemănătoare și la alte tipuri de dependențe:
+ </div><div class="para">
+ Provides: capabilitate
+ </div><div class="para">
+ Obsoletes: capabilitate
+ </div><div class="para">
+ Conflicts: capabilitate
+ </div><div class="para">
+ Puteți pune mai mult de o singură capabilitate pe linia cu dependențele. De exemplu:
+ </div><div class="para">
+ Requires: bash perl
+ </div><div class="para">
+ Puteți folosi spații sau virgule pentru a separa capabilitățile. De exemplu:
+ </div><div class="para">
+ Requires: bash, perl
+ </div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id752335" class="title">Specificarea versiunii dependențelor</h1></div></div></div><div class="para">
+ Puteți adăuga și informații despre versiune, de exemplu:
+ </div><div class="para">
+ Requires: bash >= 2.0
+ </div><div class="para">
+ Aceasta înseamnă că pachetul cere capabilitatea bash (un pachet) cu versiunea 2.0 sau mai sus. Aceeași logică se aplică la alte tipuri de dependențe.Spre exemplu:
+ </div><div class="para">
+ Conflicts: bash >= 2.0
+ </div><div class="para">
+ Acest exemplu arată că pachetul este în conflict cu toate versiunile bash 2.0 sau mai recente
+ </div><div class="para">
+ Tabelul 11-1 enumerează comparațiile de versiuni pe care le puteți folosi.
+ </div><div class="para">
+ Tabel 11-1 Comparații de versiuni dependențe
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Comparație
+ </div>
+
+ </td><td>
+ <div class="para">
+ Semnificație
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ pachet < versiune
+ </div>
+
+ </td><td>
+ <div class="para">
+ Un pachet de versiune mai veche
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ pachet > versiune
+ </div>
+
+ </td><td>
+ <div class="para">
+ Un pachet de versiune mai nouă
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ pachet >= versiune
+ </div>
+
+ </td><td>
+ <div class="para">
+ Un pachet de versiune mai nouă sau la fel
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ pachet <= versiune
+ </div>
+ <div class="para">
+ </div>
+
+ </td><td>
+ <div class="para">
+ Un pachet de versiune mai veche sau la fel
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ pachet = versiune
+ </div>
+
+ </td><td>
+ <div class="para">
+ Un pachet de versiune egală
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ pachet
+ </div>
+
+ </td><td>
+ <div class="para">
+ Pachet la orice versiune
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ RPM suportă o sintaxă extinsă pentru compararea versiunilor. Acesta esteformatul complet:
+ </div><div class="para">
+ Perioadă:Versiune-Lansare
+ </div><div class="para">
+ De exemplu:
+ </div><div class="para">
+ 1:5.6.0-17
+ </div><div class="para">
+ În acest caz, perioada este 1, versiunea este 5.6.0 iar lansarea este 17.În cele mai multe cazuri veți avea nevoie doar de versiune. Perioada permitemanevrarea versiunilor greu de comparat. Numărul de lansare nu este folosit aproape niciodată. Acest lucru are sens pentru că leagă o dependență de o anumităconstrucție a pachetului RPM mai degrabă decât de o versiune a programului în sine.Acest tip de dependență poate fi de folos doar dacă schimbați radical modul deconstrucție al unui pachet.
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id742516" class="title">Creare CAPABILITIES virtuale</h1></div></div></div><div class="para">
+ Dependențele sunt bazate pe capabilități, cele mai multe dintre acestea fiindpachete. Puteți crea capabilități virtuale, care sunt doar nume definite de dvs.De exemplu, pachetul sendmail asigură o capabilitate virtuală numită smtpdaemon.De exemplu:
+ </div><div class="para">
+ Provides: smtpdaemon
+ </div><div class="para">
+ Această capabilitate se referă la serviciul general SMTP pentru trimitereamesajelor e-mail. Nu există un fișier cu acest nume. Este doar o capabilitate,text arbitrar. Alte pachete cer această capabilitate, cum ar fi aplicațiafetchmail de descărcare și forwardare e-mail, și mutt, un client de mail.
+ </div><div class="para">
+ Prin folosirea unei capabilități virtuale, alte pachete pot asigura capabilitatea, și, cel mai important, aplicațiile client pot cere această capabilitate fără a trebui să știe ce pachet asigură capabilitatea de a trimite mesaje e-mail. De exemplu, pachetele exim și postfix, agenți de transport mail ca și sendmail, pot asiguraaceeași capabilitate.
+ </div><div class="para">
+ Notă
+ </div><div class="para">
+ Desigur, veți dori să vă asigurați că aceste pachete intră în conflict unelecu altele.
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id666551" class="title">Numirea dependențelor în motoare de scripting și module</h1></div></div></div><div class="para">
+ Limbaje de scripting ca Perl sau Tcl permit module adiționale. Pachetul dvs. poate avea nevoie de unele dintre aceste module. RPM folosește o sintaxă specialăcu paranteze pentru a indica dependențe de module de scripting. De exemplu:
+ </div><div class="para">
+ Requires: perl(Carp) >= 3.2
+ </div><div class="para">
+ Aceasta indică o cerere pentru modulul adițional Carp pentru Perl, cu o versiune mai recentă sau egală cu 3.2.
+ </div></div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id666574" class="title">Setarea premiselor</h1></div></div></div><div class="para">
+ O premisă este similară cu o dependență require, doar că o premisătrebuie instalată înainte de un anume pachet. Specificați o premisă după cum urmează:
+ </div><div class="para">
+ PreReq: capability
+ </div><div class="para">
+ Puteți include dependențe cu număr-versiune, cum ar fi:
+ </div><div class="para">
+ PreReq: capability >= version
+ </div><div class="para">
+ De obicei, o PreReq: se comportă ca o Requires:, de fapt, directiva PreReq:există doar pentru a permite ordonarea manuală a dependențelor. RPM garantează că pachetul PreReq: va fi instalat înainte de pachetul care numește dependențaPreReq: .
+ </div><div class="para">
+ Referință încrucișată
+ </div><div class="para">
+ <a class="xref" href="ch-packaging-guidelines.html">Cap. 13, <em>Packaging Guidelines</em></a> descrie problema comună detratare a dependențelor circulare folosind premise.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id666618" class="title">Numirea dependențelor de construcție</h1></div></div></div><div class="para">
+ Pachetul dvs., odată construit, are un set de dependențe. Aceste dependențe sunt importante pentru oricine care instalează pachetul. Dar există și probleme cu dependențele la construirea pachetelor. Dependențele de construcție vă permit să precizați de ce este nevoie pentru a construi pachetul. Chiar dacă credeți că acest lucru e același cu ce este necesar pentru a instala pachetul, în mod normal nu este așa. Distribuțiile de Linux tind să împartă software-ul în pachete necesare la rulare și pachete pentru dezvoltatori (runtime și development)De exemplu, pachetul python conține runtime-ul necesar pentru executarea scripturilorscrise în Python. Pachetul python-devel asigură abilitatea de a scrie extensii ale limbajului Python
+ </div><div class="para">
+ RPM vă permite să definiți dependențe în timpul construirii în fișierele dvs. spec folosind următoarele directive:
+ </div><div class="para">
+ BuildRequires:
+ </div><div class="para">
+ BuildConflicts:
+ </div><div class="para">
+ BuildPreReq:
+ </div><div class="para">
+ Aceste directive se comportă ca Requires:, Conflicts:, respectiv PreReq:, exceptând faptul că dependențele sunt necesare pentru construirea pachetului, nu pentru instalarea lui. De exemplu, pachetul dvs. poate avea nevoie de un compilator C pentru construcție, sau ar putea avea nevoie de un instrument special de construit sau o bibliotecă de dezvoltare
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id666660" class="title">Generarea automată de dependențe</h1></div></div></div><div class="para">
+ Pentru că multe dependențe sunt legate de bibliotecile shared, sistemul RPM va genera automat dependențe provide pentru orice fișier din pachetele dvs.care este obiect shared sau fișier .so. RPM va genera de asemenea dependențerequire pentru toate fișierele din lista %files care cer biblioteci shared.Pentru a realiza acest lucru, RPM folosește comanda ldd, care determină bibliotecile shared folosite de o aplicație.
+ </div><div class="para">
+ în plus, scripturile find-requires și find-provides din /usr/lib/rpm pot determina dependențele scripturilor Perl, Python și Tcl și alte dependențe,cum ar fi dependențele pachetelor Java, în mod automat. Scriptul find-requiresdetermină dependențele requires automat, iar scriptul find-provides determină dependențele provides
+ </div><div class="para">
+ Referință încrucișată
+ </div><div class="para">
+ <a class="xref" href="ch-packaging-guidelines.html">Cap. 13, <em>Packaging Guidelines</em></a> tratează oprirea generării automate a dependențelor.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch09s09.html"><strong>Înapoi</strong>9.9. Summary</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch10s02.html"><strong>Înainte</strong>10.2. Setarea triggerelor</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-command-reference.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-command-reference.html
new file mode 100644
index 0000000..7495466
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-command-reference.html
@@ -0,0 +1,1324 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Cap. 21. RPM Command Reference</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="index.html" title="Ghid RPM" /><link rel="prev" href="ch20s04.html" title="20.4. Summary" /><link rel="next" href="ch21s02.html" title="21.2. The rpmbuild Command" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch20s04.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch21s02.html"><strong>ÃŽnainte</strong></a></li></ul><div xml:lang="ro" class="chap
ter" id="ch-command-reference" lang="ro"><div class="titlepage"><div><div><h2 class="title">Cap. 21. RPM Command Reference</h2></div></div></div><div class="toc"><dl><dt><span class="sect1"><a href="ch-command-reference.html#id695500">21.1. The rpm Command</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch-command-reference.html#id561909">21.1.1. Upgrade, freshen, and install options</a></span></dt><dt><span class="sect2"><a href="ch-command-reference.html#id578909">21.1.2. Erase options</a></span></dt><dt><span class="sect2"><a href="ch-command-reference.html#id717458">21.1.3. Signature options</a></span></dt><dt><span class="sect2"><a href="ch-command-reference.html#id794197">21.1.4. Verify options</a></span></dt><dt><span class="sect2"><a href="ch-command-reference.html#id693385">21.1.5. Database options</a></span></dt><dt><span class="sect2"><a href="ch-command-reference.html#id558887">21.1.6. Miscellaneous options</a></span></dt></dl></dd><dt><span class="sect1"
><a href="ch21s02.html">21.2. The rpmbuild Command</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch21s02.html#id568724">21.2.1. Building from a spec file</a></span></dt><dt><span class="sect2"><a href="ch21s02s02.html">21.2.2. Building from a compressed tar archive</a></span></dt><dt><span class="sect2"><a href="ch21s02s03.html">21.2.3. Rebuilding RPMs from source RPMs</a></span></dt><dt><span class="sect2"><a href="ch21s02s04.html">21.2.4. Customizing the build</a></span></dt></dl></dd></dl></div><div class="para">
+ This appendix covers:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ rpm command
+ </div></li><li class="listitem"><div class="para">
+ rpmbuild command
+ </div></li></ul></div><div class="para">
+ This appendix covers the syntax of the command-line options for the rpm and rpmbuild commands.
+ </div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id695500" class="title">The rpm Command</h1></div></div></div><div class="para">
+ The rpm command is the workhorse of the RPM system. The following sections cover options for the major operations with the rpm command.
+ </div><div class="para">
+ Table A-1 lists the query options for the rpm command.
+ </div><div class="para">
+ Table A-1 rpm query options with –q or --query
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Option
+ </div>
+
+ </td><td>
+ <div class="para">
+ Usage
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -a, --all
+ </div>
+
+ </td><td>
+ <div class="para">
+ Query all packages
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -c, --configfiles
+ </div>
+
+ </td><td>
+ <div class="para">
+ List configuration files
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --changelog
+ </div>
+
+ </td><td>
+ <div class="para">
+ List changelog entries
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --conflicts
+ </div>
+
+ </td><td>
+ <div class="para">
+ List capabilities this package conflicts with
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -d, --docfiles
+ </div>
+
+ </td><td>
+ <div class="para">
+ List documentation files
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --dump
+ </div>
+
+ </td><td>
+ <div class="para">
+ Dump out extra information on files.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -f, --file filename
+ </div>
+
+ </td><td>
+ <div class="para">
+ Query for packages owning given file
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --filesbypapkg
+ </div>
+
+ </td><td>
+ <div class="para">
+ List all files in each selected package
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --fileid md5_id
+ </div>
+
+ </td><td>
+ <div class="para">
+ Query for the package with the given MD5 digest
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -g, --group group_name
+ </div>
+
+ </td><td>
+ <div class="para">
+ Query packages in the given group
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --hdrid sha1_header_id
+ </div>
+
+ </td><td>
+ <div class="para">
+ Query for the package with the given header identifier number, in SHA1 format
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -i, --info
+ </div>
+
+ </td><td>
+ <div class="para">
+ Display a lot of package information including description
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --last
+ </div>
+
+ </td><td>
+ <div class="para">
+ Reorder the output of the rpm command to show the most recently installed packages first
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --obsoletes
+ </div>
+
+ </td><td>
+ <div class="para">
+ List capabilities this package obsoletes
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -p, --package rpm_file
+ </div>
+
+ </td><td>
+ <div class="para">
+ Query the given package file or files
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --pkgid md5_id
+ </div>
+
+ </td><td>
+ <div class="para">
+ Query for the package with the given MD5 package ID
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --provides
+ </div>
+
+ </td><td>
+ <div class="para">
+ List capabilities provided by package
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --querybynumber number
+ </div>
+
+ </td><td>
+ <div class="para">
+ Query for the given entry, by number, in the RPM database
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --qf, --queryformat format
+ </div>
+
+ </td><td>
+ <div class="para">
+ Use the given query format for displaying the output
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --redhatprovides capability
+ </div>
+
+ </td><td>
+ <div class="para">
+ Look in rpmdb-redhat database for packages that provide the given capability
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --redhatrequires capability
+ </div>
+
+ </td><td>
+ <div class="para">
+ Look in rpmdb-redhat database for packages that require the given capability
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -R, --requires
+ </div>
+
+ </td><td>
+ <div class="para">
+ Lists packages and capabilities that this package depends on
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --specfile specfile
+ </div>
+
+ </td><td>
+ <div class="para">
+ Query the given spec file
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -s, --state
+ </div>
+
+ </td><td>
+ <div class="para">
+ Display the state of the listed files
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --scripts
+ </div>
+
+ </td><td>
+ <div class="para">
+ List scripts in the package
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --tid transaction_id
+ </div>
+
+ </td><td>
+ <div class="para">
+ Query for the package or packages with the given transaction ID
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --triggeredby package
+ </div>
+
+ </td><td>
+ <div class="para">
+ Query packages triggered by the given package
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --triggers, --triggerscripts
+ </div>
+
+ </td><td>
+ <div class="para">
+ List trigger scripts
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --whatrequires capability
+ </div>
+
+ </td><td>
+ <div class="para">
+ Query packages that require the given capability
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --whatprovides capability
+ </div>
+
+ </td><td>
+ <div class="para">
+ List packages that provide the given capability
+ </div>
+
+ </td></tr></tbody></table></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id561909" class="title">Upgrade, freshen, and install options</h1></div></div></div><div class="para">
+ Table A-2 lists the upgrade, freshen, and installation options for the rpm command.
+ </div><div class="para">
+ Table A-2 rpm upgrade, freshen, and install options
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Option
+ </div>
+
+ </td><td>
+ <div class="para">
+ Usage
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --aid
+ </div>
+
+ </td><td>
+ <div class="para">
+ Add any suggested packages to the list to install or upgrade
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --allfiles
+ </div>
+
+ </td><td>
+ <div class="para">
+ Install all the files, even if some might otherwise be skipped
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --badreloc
+ </div>
+
+ </td><td>
+ <div class="para">
+ Relocate files even if the package is not relocatable
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --excludedocs
+ </div>
+
+ </td><td>
+ <div class="para">
+ Skip the files marked as documentation
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --excludepath path
+ </div>
+
+ </td><td>
+ <div class="para">
+ Skip files that begin with path
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --force
+ </div>
+
+ </td><td>
+ <div class="para">
+ A short hand for --replacepkgs and --replacefiles
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -h, --hash
+ </div>
+
+ </td><td>
+ <div class="para">
+ Print hash marks, #, periodically while performing operation to provide some feedback
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --ignorearch
+ </div>
+
+ </td><td>
+ <div class="para">
+ Ignore the architecture listed in the package
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --ignoreos
+ </div>
+
+ </td><td>
+ <div class="para">
+ Ignore the operating system listed in the package
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --ignoresize
+ </div>
+
+ </td><td>
+ <div class="para">
+ Skip the check to see if there is enough disk space to install the package
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --includedocs
+ </div>
+
+ </td><td>
+ <div class="para">
+ Install files marked as documentation, turned on by default
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --justdb
+ </div>
+
+ </td><td>
+ <div class="para">
+ Just update the RPM database, do not modify any files
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nodeps
+ </div>
+
+ </td><td>
+ <div class="para">
+ Skip verification of package dependencies
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nodigest
+ </div>
+
+ </td><td>
+ <div class="para">
+ Skip verification of package and header digests
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nomd5
+ </div>
+
+ </td><td>
+ <div class="para">
+ Skip verification of file MD5 checksums
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --noorder
+ </div>
+
+ </td><td>
+ <div class="para">
+ Do not reorder the list of packages to be installed based on dependencies
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nopost
+ </div>
+
+ </td><td>
+ <div class="para">
+ Do not run post-install scripts
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nopostun
+ </div>
+
+ </td><td>
+ <div class="para">
+ Do not run post-uninstall scripts
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nopre
+ </div>
+
+ </td><td>
+ <div class="para">
+ Do not run pre-install scripts
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nopreun
+ </div>
+
+ </td><td>
+ <div class="para">
+ Do not run pre-uninstall scripts
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nosuggest
+ </div>
+
+ </td><td>
+ <div class="para">
+ Do not suggest packages for missing dependencies
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --noscripts
+ </div>
+
+ </td><td>
+ <div class="para">
+ Do not execute scripts
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nosignature
+ </div>
+
+ </td><td>
+ <div class="para">
+ Skip verification of package and header signatures
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --notriggers
+ </div>
+
+ </td><td>
+ <div class="para">
+ Do not execute trigger scripts
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --notriggerin
+ </div>
+
+ </td><td>
+ <div class="para">
+ Do not run trigger install scripts
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --notriggerpostun
+ </div>
+
+ </td><td>
+ <div class="para">
+ Do not run trigger post uninstall scripts
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --notriggerun
+ </div>
+
+ </td><td>
+ <div class="para">
+ Do not run trigger uninstall scripts
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --oldpackage
+ </div>
+
+ </td><td>
+ <div class="para">
+ Allow an upgrade to an older version of a package
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --percent
+ </div>
+
+ </td><td>
+ <div class="para">
+ Print out percentage of work completed as command executes
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --prefix directory
+ </div>
+
+ </td><td>
+ <div class="para">
+ Relocate package to directory, if package is relocatable
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --relocate old=new
+ </div>
+
+ </td><td>
+ <div class="para">
+ Relocate all paths that start with old to new, if relocatable
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --repackage
+ </div>
+
+ </td><td>
+ <div class="para">
+ Create a package from any files that would be erased
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --replacefiles
+ </div>
+
+ </td><td>
+ <div class="para">
+ Install package even if it replaces files from other packages
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --replacepkgs
+ </div>
+
+ </td><td>
+ <div class="para">
+ Install packages even if they are already installed
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --test
+ </div>
+
+ </td><td>
+ <div class="para">
+ Do not install or remove packages, just see if the command would work
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ Use rpm –U or --upgrade to upgrade, rpm –i or --install to install, and –F or --freshen to freshen a package.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id578909" class="title">Erase options</h1></div></div></div><div class="para">
+ Table A-3 lists the erase, or package removal, options for the rpm command.
+ </div><div class="para">
+ Table A-3 rpm erase (removal) options with –e or --erase
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Option
+ </div>
+
+ </td><td>
+ <div class="para">
+ Usage
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --allmatches
+ </div>
+
+ </td><td>
+ <div class="para">
+ Remove all versions of the packages; normally an error would occur if there is more than one package of the same name and you try to erase the package
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nodeps
+ </div>
+
+ </td><td>
+ <div class="para">
+ Skip verification of package dependencies
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --noscripts
+ </div>
+
+ </td><td>
+ <div class="para">
+ Do not execute scripts
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nopostun
+ </div>
+
+ </td><td>
+ <div class="para">
+ Do not run post-uninstall scripts
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nopreun
+ </div>
+
+ </td><td>
+ <div class="para">
+ Do not run pre-uninstall scripts
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --notriggers
+ </div>
+
+ </td><td>
+ <div class="para">
+ Do not execute trigger scripts
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --notriggerpostun
+ </div>
+
+ </td><td>
+ <div class="para">
+ Do not run trigger post uninstall scripts
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --notriggerun
+ </div>
+
+ </td><td>
+ <div class="para">
+ Do not run trigger uninstall scripts
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --repackage
+ </div>
+
+ </td><td>
+ <div class="para">
+ Create a package from any files that would be erased
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --test
+ </div>
+
+ </td><td>
+ <div class="para">
+ Do not install or remove packages, just see if the command would work
+ </div>
+
+ </td></tr></tbody></table></div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id717458" class="title">Signature options</h1></div></div></div><div class="para">
+ Table A-4 lists the signature-related options to the rpm command.
+ </div><div class="para">
+ Table A-4 rpm signature options with –K, --checksig, or --import
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Option
+ </div>
+
+ </td><td>
+ <div class="para">
+ Usage
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --addsign
+ </div>
+
+ </td><td>
+ <div class="para">
+ Sign packages, same as --resign
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --import public_key
+ </div>
+
+ </td><td>
+ <div class="para">
+ Add given public key to the RPM database
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nodigest
+ </div>
+
+ </td><td>
+ <div class="para">
+ Skip verification of package and header digests
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nosignature
+ </div>
+
+ </td><td>
+ <div class="para">
+ Skip verification of package and header signatures
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --resign
+ </div>
+
+ </td><td>
+ <div class="para">
+ Sign packages
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ The --import option works on its own. The rest of the options work with one or more RPM packages.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id794197" class="title">Verify options</h1></div></div></div><div class="para">
+ The rpm command can verify packages. This involves comparing all files installed by the package with the information in the RPM database, and looking for differences or missing files.
+ </div><div class="para">
+ Table A-5 lists the verify options to the rpm command.
+ </div><div class="para">
+ Table A-5 rpm verify options with –V or --verify
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Option
+ </div>
+
+ </td><td>
+ <div class="para">
+ Usage
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -a, --all
+ </div>
+
+ </td><td>
+ <div class="para">
+ Verify all packages
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -f, --file filename
+ </div>
+
+ </td><td>
+ <div class="para">
+ Verify packages owning given file
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -g, --group group_name
+ </div>
+
+ </td><td>
+ <div class="para">
+ Verify packages in the given group
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nodeps
+ </div>
+
+ </td><td>
+ <div class="para">
+ Skip verification of package dependencies
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nodigest
+ </div>
+
+ </td><td>
+ <div class="para">
+ Skip verification of package and header digests
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nofiles
+ </div>
+
+ </td><td>
+ <div class="para">
+ Do not verify the files in the package
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nogroup
+ </div>
+
+ </td><td>
+ <div class="para">
+ Do not verify the group owner
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nolinkto
+ </div>
+
+ </td><td>
+ <div class="para">
+ Do not verify the link file attribute
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nomd5
+ </div>
+
+ </td><td>
+ <div class="para">
+ Skip verification of file MD5 checksums
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nomtime
+ </div>
+
+ </td><td>
+ <div class="para">
+ Do not verify the mtime attribute
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nomode
+ </div>
+
+ </td><td>
+ <div class="para">
+ Do not verify the file mode (permissions)
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nordev
+ </div>
+
+ </td><td>
+ <div class="para">
+ Do not verify the rdev attribute
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --noscripts
+ </div>
+
+ </td><td>
+ <div class="para">
+ Do not execute the verify scripts
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nosignature
+ </div>
+
+ </td><td>
+ <div class="para">
+ Skip verification of package and header signatures
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nosize
+ </div>
+
+ </td><td>
+ <div class="para">
+ Do not verify the file size
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nouser
+ </div>
+
+ </td><td>
+ <div class="para">
+ Do not verify the owner of the file
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -p, --package rpm_file
+ </div>
+
+ </td><td>
+ <div class="para">
+ Verify the given package file or files
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --specfile specfile
+ </div>
+
+ </td><td>
+ <div class="para">
+ Verify the given spec file
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --whatrequires capability
+ </div>
+
+ </td><td>
+ <div class="para">
+ Verify packages that require the given capability
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --whatprovides capability
+ </div>
+
+ </td><td>
+ <div class="para">
+ Verify packages that provide the given capability
+ </div>
+
+ </td></tr></tbody></table></div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id693385" class="title">Database options</h1></div></div></div><div class="para">
+ You can create a new, empty, RPM database as well as rebuild all the inverted lists used for quick access using the database options listed in Table A-6.
+ </div><div class="para">
+ Table A-6 rpm database options
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Option
+ </div>
+
+ </td><td>
+ <div class="para">
+ Usage
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --initdb
+ </div>
+
+ </td><td>
+ <div class="para">
+ Initialize database
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --rebuilddb
+ </div>
+
+ </td><td>
+ <div class="para">
+ Rebuild all the inverted lists from the Packages file
+ </div>
+
+ </td></tr></tbody></table></div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id558887" class="title">Miscellaneous options</h1></div></div></div><div class="para">
+ These options can be used with any rpm command. Three of the options, --querytags, --version, and --showrc, run on their own. The rest can be used with the other rpm options. Table A-7 lists these miscellaneous options.
+ </div><div class="para">
+ Table A-7 Miscellaneous rpm options
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Option
+ </div>
+
+ </td><td>
+ <div class="para">
+ Usage
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -?, --help
+ </div>
+
+ </td><td>
+ <div class="para">
+ Print the popt help information for all the command-line options
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --dbpath path_to_rpm_db
+ </div>
+
+ </td><td>
+ <div class="para">
+ Use the given directory for the RPM database, instead of the default
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -D, --define 'macro value'
+ </div>
+
+ </td><td>
+ <div class="para">
+ Define the given macro to hold the given value
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -E, --eval expression
+ </div>
+
+ </td><td>
+ <div class="para">
+ Print the evaluation of the given expression
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --ftpport port
+ </div>
+
+ </td><td>
+ <div class="para">
+ Use the given port number for FTP access
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --ftpproxy host
+ </div>
+
+ </td><td>
+ <div class="para">
+ Use the given host name as a proxy for FTP access
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --httpport port
+ </div>
+
+ </td><td>
+ <div class="para">
+ Use the given port number for HTTP access
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --httpproxy host
+ </div>
+
+ </td><td>
+ <div class="para">
+ Use the given host name as a proxy for HTTP access
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --macros file:file:file
+ </div>
+
+ </td><td>
+ <div class="para">
+ Read the given colon-separated files as the macro files to define RPM macros; only the first file must exist
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --pipe command
+ </div>
+
+ </td><td>
+ <div class="para">
+ Pipe the output of the rpm command to the given command
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --querytags
+ </div>
+
+ </td><td>
+ <div class="para">
+ Print the query tag names and exit
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --quiet
+ </div>
+
+ </td><td>
+ <div class="para">
+ Provide less output, normally show only errors
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --rcfile file:file:file
+ </div>
+
+ </td><td>
+ <div class="para">
+ Read the given colon-separated files as the rc files to define RPM settings; only the first file must exist
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --root directory
+ </div>
+
+ </td><td>
+ <div class="para">
+ Use directory as the top-level directory instead of /.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --showrc
+ </div>
+
+ </td><td>
+ <div class="para">
+ Print the rpmrc and macro configuration and exit
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -v, --verbose
+ </div>
+
+ </td><td>
+ <div class="para">
+ Provide more verbose output
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -vv
+ </div>
+
+ </td><td>
+ <div class="para">
+ Provide even more verbose output, including debugging information
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --version
+ </div>
+
+ </td><td>
+ <div class="para">
+ Print the RPM version and exit
+ </div>
+
+ </td></tr></tbody></table></div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch20s04.html"><strong>Înapoi</strong>20.4. Summary</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch21s02.html"><strong>Înainte</strong>21.2. The rpmbuild Command</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-creating-rpms.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-creating-rpms.html
new file mode 100644
index 0000000..9b30072
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-creating-rpms.html
@@ -0,0 +1,232 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Cap. 8. Creating RPMs: An Overview</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="index.html" title="Ghid RPM" /><link rel="prev" href="ch07s04.html" title="7.4. Summary" /><link rel="next" href="ch08s02.html" title="8.2. Building RPMs" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch07s04.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch08s02.html"><strong>ÃŽnainte</strong></a></li></ul><div xml:lang="ro" class="chapter" id="
ch-creating-rpms" lang="ro"><div class="titlepage"><div><div><h2 class="title">Cap. 8. Creating RPMs: An Overview</h2></div></div></div><div class="toc"><dl><dt><span class="sect1"><a href="ch-creating-rpms.html#id851471">8.1. Preparing to Build RPMs</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch-creating-rpms.html#id765745">8.1.1. Planning what you want to build</a></span></dt><dt><span class="sect2"><a href="ch-creating-rpms.html#id553544">8.1.2. Gathering the software to package</a></span></dt><dt><span class="sect2"><a href="ch-creating-rpms.html#id582471">8.1.3. Creating a reproducible build of the software</a></span></dt><dt><span class="sect2"><a href="ch-creating-rpms.html#id571720">8.1.4. Planning for Upgrades</a></span></dt><dt><span class="sect2"><a href="ch-creating-rpms.html#id870930">8.1.5. Outlining Any Dependencies</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch08s02.html">8.2. Building RPMs</a></span></dt><dd><dl><dt><span class="sec
t2"><a href="ch08s02.html#id823716">8.2.1. Setting up the directory structure</a></span></dt><dt><span class="sect2"><a href="ch08s02s02.html">8.2.2. Placing your sources into the directory structure</a></span></dt><dt><span class="sect2"><a href="ch08s02s03.html">8.2.3. Creating the spec file</a></span></dt><dt><span class="sect2"><a href="ch08s02s04.html">8.2.4. Building RPMs with the rpmbuild command</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch08s03.html">8.3. Verifying Your RPMS</a></span></dt><dt><span class="sect1"><a href="ch08s04.html">8.4. Summary</a></span></dt></dl></div><div class="para">
+ This chapter covers:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Preparing to build RPMs
+ </div></li><li class="listitem"><div class="para">
+ Planning for RPMs
+ </div></li><li class="listitem"><div class="para">
+ Explaining the build process
+ </div></li><li class="listitem"><div class="para">
+ Using build files
+ </div></li><li class="listitem"><div class="para">
+ Seeing the results
+ </div></li><li class="listitem"><div class="para">
+ Verifying your RPMs
+ </div></li></ul></div><div class="para">
+ Thus far in this book, all the commands presented have been used to manage or query packages. With this chapter, though, you start creating RPMs of your own. Even if you do not produce applications on your own, you may want to create RPM packages out of software you use, if only for the ease of management that the RPM system provides.
+ </div><div class="para">
+ Creating RPMs allows you to create a consistent set of applications for use on all systems in your organization and easily manage those applications. You may create RPMs of applications developed in house or RPMs of applications developed elsewhere that you need to customize for your environment. Making RPMs of the customized applications reduces work and makes the customizations consistent.
+ </div><div class="para">
+ This chapter introduces the RPM system from the point of view of creating RPMs and demonstrates the steps and planning necessary to make your own packages. As such, this chapter introduces the RPM-building topics covered in depth in the remaining chapters in this part.
+ </div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id851471" class="title">Preparing to Build RPMs</h1></div></div></div><div class="para">
+ The RPM-building task starts with gathering all the material you want to bundle into an RPM package and then defining the RPM directives to make your package. The final steps are to build and test an RPM. This sounds easy, and for the most part it is fairly straightforward.
+ </div><div class="para">
+ The main problems arise when you try to define the many RPM directives for your package. In addition, some of the elements in an RPM can be complex, such as upgrade scripts.
+ </div><div class="para">
+ The main tasks in building RPMs are:
+ </div><div class="para">
+ 1.Planning what you want to build
+ </div><div class="para">
+ 2.Gathering the software to package
+ </div><div class="para">
+ 3.Patching the software as needed
+ </div><div class="para">
+ 4.Creating a reproducible build of the software
+ </div><div class="para">
+ 5.Planning for upgrades
+ </div><div class="para">
+ 6.Outlining any dependencies
+ </div><div class="para">
+ 7.Building the RPMs
+ </div><div class="para">
+ 8.Testing the RPMs
+ </div><div class="para">
+ The sections in this chapter cover the initial planning stages and provide an overview of the process of building RPMs. The remaining chapters in Part II go in depth into the process of building RPMs.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id765745" class="title">Planning what you want to build</h1></div></div></div><div class="para">
+ The first step in the entire RPM-building process is simply to decide exactly what you want to make into an RPM. Is this an application, a programming library, a set of system configuration files, or a documentation package? If this is an application, is it customized or patched? Think these issues over and decide what you want to package as an RPM.
+ </div><div class="para">
+ In most cases, you want to create both a source package and a binary package containing the built sources. You need a binary package because that holds the RPM you want to install on other systems. You need the source package so you can recreate the binary package at any time. And, if the sources get updated, you can quickly make a new binary RPM from the updated sources if you have already defined a source RPM.
+ </div><div class="para">
+ Most packages start with a source RPM, although you have the option to skip making a source RPM. It is a good idea to make the source RPM, however, because it makes it easier to reproduce the final binary RPM. Once of the key goals of the RPM system is to allow for reproducible builds, and making source RPMs is just one step to help towards this goal.
+ </div><div class="para">
+ Creating a source RPM also allows you to transfer the entire set of sources for a package to another system, since the source RPM is just one file and it contains all the program sources along with the instructions, called a spec file, for building the binary RPM. Furthermore, creating a source RPM makes it easier to create binary RPMs on different processor architectures or different versions of Linux.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ Not all programs are portable to multiple-processor architectures. But many Linux programs can simply be recompiled on another architecture to make a binary program for that architecture. That's because there are a lot of common APIs for Linux applications and because most programs are not processor dependent. This is not true of all programs, so your mileage may vary.
+ </div><div class="para">
+ Source packages are not that hard to make, and they provide a single package, and single file, that holds all the sources necessary to build your binary package. In addition, once you have a source RPM, it is very easy to build a binary RPM.
+ </div><div class="para">
+ Binary packages are likely the real reason you want to make an RPM. You can package an application, a programming library, or almost anything you want. Armed with a binary RPM, you can transfer one file to another machine and install the application there, taking full advantage of the RPM system.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id553544" class="title">Gathering the software to package</h1></div></div></div><div class="para">
+ Whether you are writing your own software or merely packaging software found elsewhere, the next step is to gather the software you want to bundle into an RPM. This includes the applications or libraries you want to package, as well as the program source code.
+ </div><div class="para">
+ In general, you’ll be doing one of three things:
+ </div><div class="para">
+ *Packaging your own software
+ </div><div class="para">
+ *Packaging someone else’s software
+ </div><div class="para">
+ *Packaging someone else’s stuff after first customizing or patching the software
+ </div><div class="para">
+ In all cases, you need to gather the software together and decide whether you want everything to go into one bundle or a number of bundles.
+ </div><div class="para">
+ As covered in <a class="xref" href="ch-intro-rpm.html">Cap. 1, <em>Introduction to RPM</em></a> , a major tenet of the philosophy behind RPM is to start with pristine—unmodified--sources. You may need to patch or customize the sources for your environment, but you can always go back to the original sources.
+ </div><div class="para">
+ Starting with pristine sources provides a number of advantages, including the following:
+ </div><div class="para">
+ *You clearly separate any changes you have made to the software from the original software.
+ </div><div class="para">
+ *You make it easier to get an upgrade of the original sources, since your changes are cleanly separated from the original sources. With each new release of the software, you can determine which of your changes, if any, are still needed. This is especially important if you are packaging an application created by another organization into an RPM.
+ </div><div class="para">
+ *You have a reproducible way to recreate everything in the package. Since you start with unmodified sources, you can always go back to the beginning of the process and start again. Thus, your RPMs don’t depend on any actions taken beforehand, such as patching, that you may later forget to do because the steps are not automated as part of the RPM-building process.
+ </div><div class="para">
+ Start with pristine sources; then patch as needed. A patch is an automated set of modifications to the source code. Use the diff command to build a patch and the patch command to apply the patch (that is, to modify the source code). Keep the original sources separate from any patches you need to make the software work in your environment.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ See the online manual pages for the patch and diff commands for more information on how to create and apply a patch.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id582471" class="title">Creating a reproducible build of the software</h1></div></div></div><div class="para">
+ The RPM system will automate the steps to create an application, as long as you configure the RPM with the proper steps, such as which make targets to run. Unfortunately, configuring the proper steps is not always easy. So before trying to make an RPM, you need to figure out how to build the application or library you plan to package into an RPM. Once you have figured out how to build the application or library, you can set up a reproducible build. The RPM system can then automate this build.
+ </div><div class="para">
+ To build the software, you’ll need to use a variety of Linux tools. The specific tools you need depend largely on where the original software came from. The following sections outline some of the more common techniques for preparing and building Linux software.
+ </div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id582489" class="title">Unpacking Software</h1></div></div></div><div class="para">
+ Many applications are downloaded in compressed tar format, often called a tarball. A tarball is merely an archive file built by the tar command that has been compressed, usually using the gzip command.
+ </div><div class="para">
+ In most cases, these files have a name such as the following:
+ </div><div class="para">
+ filename.tar.gz
+ </div><div class="para">
+ filename.tgz
+ </div><div class="para">
+ filename.tar.Z
+ </div><div class="para">
+ For the first two cases, use the gunzip command to unzip the file; then use the tar command to extract the file, for example:
+ </div><div class="para">
+ $ gunzip filename.tgz
+ </div><div class="para">
+ $ tar xf filename.tar
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ In the case of a file name ending in .Z, use the uncompress program instead of gunzip.
+ </div><div class="para">
+ Once you have unpacked the sources, start looking around at the files.
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id863384" class="title">Reading the README</h1></div></div></div><div class="para">
+ Many applications come with a very handy file named README, or something similar, such as README.txt. As the name implies, you should read this file. The README file answers some of the most common questions about a particular application.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ You really should read any file named README or any variant of README.
+ </div><div class="para">
+ Other useful files include those named INSTALL or some close variant. Read these files, too. Usually, the README or the INSTALL file will tell you what you need to do to build the software.
+ </div><div class="para">
+ Once you have extracted the source code files and read all the available documentation, the next step is to build, usually compile, the application or library.
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id863416" class="title">Building Programs with Linux Build Tools</h1></div></div></div><div class="para">
+ Most applications or libraries need to be built into executable programs or compiled archived libraries. This process of building can be as simple as just compiling, but is usually more involved. Most Linux applications and libraries use a build tool called make to manage the building of the source code and creation of the executable programs. The make command uses a file, normally named Makefile, that contains the rules for building the software. You will usually find a Makefile in each directory in the source code
+ </div><div class="para">
+ Each Makefile contains a set of targets that define things that make can build. Each target defines the commands to run to build a particular thing (make targets are purely arbitrary, although some conventions are usually followed). Some combination of the targets results in a built application. The make program runs the targets that you specify on the command line, or the Makefile rules indicate it needs to run based on the targets you specify on the command line.
+ </div><div class="para">
+ You need to tell make the target to build the application or library you want to package into an RPM. Each target is defined within the Makefile. The conventional make targets to build and install a program are:
+ </div><div class="para">
+ make
+ </div><div class="para">
+ make install
+ </div><div class="para">
+ When you call the make command without the name of a target, make builds the default target, named all. This target usually compiles the program or library. The install target should install the program.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ The names of these make targets are conventions shared by many but not all programs. Other common targets include clean, which should clean up any files built.
+ </div><div class="para">
+ </div><div class="para">
+ The commands in the Makefile may be specific to a given system. For example, the traditional command for compiling C programs is cc, short for C Compiler. You may have the gcc command (GNU C Compiler) instead. The options passed to the C compiler may differ depending on the architecture of the system. Other commands may exist but be located in different locations. SUSE Linux, for example, puts a lot of programs in /opt.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ These system-dependent issues mostly apply to various versions of Unix. Most modern Linux systems are fairly similar. Because many packages, such as sendmail, have a long UNIX history, you’ll find all sorts of complications in the Makefiles or many Makefiles provided with many applications. If we could just convince everyone to give up all non-Linux operating systems, this task would be much simpler.
+ </div><div class="para">
+ Because the Makefiles are platform specific, a number of tools have been developed to create the proper Makefile, usually by running a program that knows about your system's architecture. The simplest of these tools is the manual approach. You may download a program and find files such as Makefile.amiga, Makefile.solaris, and Makefile.linux. You need to copy the file for your system architecture to the name Makefile.
+ </div><div class="para">
+ The following sections discuss other tools for creating Makefiles.
+ </div><div class="para">
+ </div><div class="sect4"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id569132" class="title">imake</h1></div></div></div><div class="para">
+ A program called imake is used mostly for X Window graphical applications, and typically older X Window applications. The imake command uses a file named Imakefile that contains rules used to build a platform-specific Makefile. This allows X Window applications, which run on many architectures and operating systems, to come with fairly generic build scripts.
+ </div><div class="para">
+ When you see an Imakefile, use the following general set of commands to compileand install an application:
+ </div><div class="para">
+ $ xmkmf
+ </div><div class="para">
+ $ make
+ </div><div class="para">
+ $ make install
+ </div><div class="para">
+ These commands work for most X Window applications. The xmkmf command is a script that runs the imake command to create a Makefile. If the xmkmf command is not available or if this command does not work, you may need to run a command such as the following:
+ </div><div class="para">
+ make Makefile
+ </div><div class="para">
+ Or, if there are multiple directories of source code, try the following command:
+ </div><div class="para">
+ make Makefiles
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ For more on imake, see www.dubois.ws/software/imake-stuff/.
+ </div></div><div class="sect4"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id676815" class="title">The configure script</h1></div></div></div><div class="para">
+ Most Linux programs, especially server-side or command-line programs, use a script called configure. The configure script outputs a platform-specific Makefile.
+ </div><div class="para">
+ If you see a script named configure in the source files, try the following commands to build and install the program:
+ </div><div class="para">
+ $ ./configure
+ </div><div class="para">
+ $ make
+ </div><div class="para">
+ $ make install
+ </div><div class="para">
+ The ./configure command runs the script in the local directory, which outputs a Makefile configured for your system. The make command builds the program and the make install command installs the program.
+ </div><div class="para">
+ The configure script is created by a set of tools including automake and autoconf, which use generic files usually named configure.in and makefile.am, among other files, to create the generic configure script.
+ </div><div class="para">
+ In many cases, you’ll need to pass parameters to the configure script. One of the most common parameters is --prefix, which tells the configure script the name of the starting directory from which to base all other paths. This is the root directory for building the application.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ For more on the configure system, autoconf, and automake, see www.airs.com/ian/configure/.
+ </div></div><div class="sect4"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id571677" class="title">Building Perl modules</h1></div></div></div><div class="para">
+ Perl is a scripting language used heavily on Linux systems, especially by administrators. Most Perl modules and packages use the following set of commands to create a system-specific Makefile and to build the module:
+ </div><div class="para">
+ $ perl Makefile.PL
+ </div><div class="para">
+ $ make
+ </div><div class="para">
+ $ make test
+ </div><div class="para">
+ $ make install
+ </div><div class="para">
+ If you see a file named Makefile.PL, chances are these are the commands to run to build the application or module.
+ </div><div class="para">
+ The goal of all these steps is to figure out how to make a reproducible build of the application or library you want to package in RPM format. Once you have a build, the next step is to plan for upgrades.
+ </div></div></div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id571720" class="title">Planning for Upgrades</h1></div></div></div><div class="para">
+ Any application or library you package in RPM format is likely to get upgraded sometime. When this happens, you’ll need to make a new RPM. This new RPM must handle not only installing the package, but also handling any upgrade issues. You need to think about the following issues:
+ </div><div class="para">
+ *How to install the RPM for the new version of the software. Are there any necessary install scripts?
+ </div><div class="para">
+ *How to remove the previous RPM package. If your package has an install script, then you may need an uninstall script to cleanly remove any changes made to the system by the install script. The RPM system handles the removal of the files in the package. You need to handle the task of undoing any changes made to the system during installation.
+ </div><div class="para">
+ At this point in time, the main effort is to keep these issues in mind and plan ahead, since these issues will come up with any upgrade.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id870930" class="title">Outlining Any Dependencies</h1></div></div></div><div class="para">
+ Often, the hardest task is getting make to build a program properly. One potential problem is assuring that all the dependencies are included. As you work with make, keep track of any other libraries that the program you are trying to build requires. These libraries will become dependencies when you get to the stage of making the RPM.
+ </div><div class="para">
+ In most cases you do not want to include the dependencies in your RPM. Instead, each dependency should have its own RPM for each necessary library. In many cases, you should be able to find RPMs for these dependencies. Keep track of the packages that provide the dependencies.
+ </div><div class="para">
+ After you have built the application, planned for upgrades and outlined dependencies, you can make an RPM.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch07s04.html"><strong>Înapoi</strong>7.4. Summary</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch08s02.html"><strong>Înainte</strong>8.2. Building RPMs</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-customizing-rpm.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-customizing-rpm.html
new file mode 100644
index 0000000..e5d97db
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-customizing-rpm.html
@@ -0,0 +1,204 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Cap. 20. Customizing RPM Behavior</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="index.html" title="Ghid RPM" /><link rel="prev" href="ch19s05.html" title="19.5. Summary" /><link rel="next" href="ch20s02.html" title="20.2. Configuring RPM Settings" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch19s05.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch20s02.html"><strong>ÃŽnainte</strong></a></li></ul><div xml:lang="ro" class="
chapter" id="ch-customizing-rpm" lang="ro"><div class="titlepage"><div><div><h2 class="title">Cap. 20. Customizing RPM Behavior</h2></div></div></div><div class="toc"><dl><dt><span class="sect1"><a href="ch-customizing-rpm.html#id773884">20.1. Customizing with RPM Macros</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch-customizing-rpm.html#id820436">20.1.1. Defining macros</a></span></dt><dt><span class="sect2"><a href="ch-customizing-rpm.html#id721750">20.1.2. Customizing Macros</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch20s02.html">20.2. Configuring RPM Settings</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch20s02.html#id558168">20.2.1. Viewing the current settings</a></span></dt><dt><span class="sect2"><a href="ch20s02s02.html">20.2.2. Locating the rpmrc files</a></span></dt><dt><span class="sect2"><a href="ch20s02s03.html">20.2.3. Changing settings</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch20s03.html">20.3. Adding P
opt Aliases</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch20s03.html#id692629">20.3.1. Defining aliases</a></span></dt><dt><span class="sect2"><a href="ch20s03s02.html">20.3.2. Customizing popt aliases</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch20s04.html">20.4. Summary</a></span></dt></dl></div><div class="para">
+ This chapter covers:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Defining RPM macros
+ </div></li><li class="listitem"><div class="para">
+ Configuring RPM settings
+ </div></li><li class="listitem"><div class="para">
+ Adding popt aliases
+ </div></li></ul></div><div class="para">
+ RPM provides a high degree of customization in the form of basic settings, such as where your RPM database is located and the path to common commands like setup or make, to the ability to define new macros and command-line aliases. This chapter covers the three main ways to customize RPM behavior: RPM macros, RPM rc settings, and popt aliases.
+ </div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id773884" class="title">Customizing with RPM Macros</h1></div></div></div><div class="para">
+ Starting with RPM 3.0, RPM macros have replaced most RPM settings from the rpmrc files.
+ </div><div class="para">
+ An RPM macro defines a setting to the RPM system. A macro can be defined as a static value, such as the directory where the RPM database is installed. A macro can also be defined in terms of other macros. Furthermore, a macro can be defined with parameters.
+ </div><div class="para">
+ For example, the following defines two macros in a macro file:
+ </div><div class="para">
+ %_usr /usr
+ </div><div class="para">
+ %_usrsrc %{_usr}/src
+ </div><div class="para">
+ In this case, the macro %_usr names the /usr directory. The macro %_usrsrc names the /usr/src directory, showing how to set a macro in terms of another macro.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ The macro syntax is used in the query formats introduced in <a class="xref" href="ch-using-rpm-db.html">Cap. 4, <em>Using the RPM Database</em></a> .
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id820436" class="title">Defining macros</h1></div></div></div><div class="para">
+ RPM provides a number of places you can define macros, including inside spec files (probably the most common usage), in special macro initialization files, and on the command line.
+ </div><div class="para">
+ In each case, the syntax is slightly different.
+ </div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id620320" class="title">Defining Macros in Spec Files</h1></div></div></div><div class="para">
+ You can define macros in most places in a spec file. With spec files, use the %define syntax to define a macro, which uses the following syntax:
+ </div><div class="para">
+ %define name(options) body
+ </div><div class="para">
+ The options are optional and can include the special values defined in Table 21-1.
+ </div><div class="para">
+ Table 21-1 Special options for macros
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Option
+ </div>
+
+ </td><td>
+ <div class="para">
+ Holds
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ %0
+ </div>
+
+ </td><td>
+ <div class="para">
+ The name of the macro
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ %1
+ </div>
+
+ </td><td>
+ <div class="para">
+ The first argument, after processing with getopt
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ %2-%9
+ </div>
+
+ </td><td>
+ <div class="para">
+ Additional arguments
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ %*
+ </div>
+
+ </td><td>
+ <div class="para">
+ All arguments, except for flags that have been processed
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ %#
+ </div>
+
+ </td><td>
+ <div class="para">
+ Number of arguments
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ These options are similar to those for shell scripting.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ <a class="xref" href="ch-specfiles.html">Cap. 9, <em>Working with Spec Files</em></a> covers spec files.
+ </div><div class="para">
+ In addition to these options, you can use a syntax of %{-a} to hold –a if an option of –a was passed. The syntax of %{-a*} indicates the value passed after the –a option.
+ </div><div class="para">
+ You can assign a macro to the value returned by a shell command by using syntax like the following:
+ </div><div class="para">
+ %(shell_command)
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ This is similar to the $(shell_command) syntax supported by bash.
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id820958" class="title">Defining Macros in Macro Initialization Files</h1></div></div></div><div class="para">
+ Inside a macro file, define macros with the following syntax:
+ </div><div class="para">
+ %macro_name value
+ </div><div class="para">
+ Macros defined for the RPM system start with an underscore. Some older macros are left without the leading underscore.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ The macros defined with an underscore are not exported into rpm headers.
+ </div><div class="para">
+ The %expand built-in macro will expand the value of something else, including executing a shell command. For example, the following sets the user’s home directory to the %home macro:
+ </div><div class="para">
+ %home %{expand:%%(cd; pwd)}
+ </div><div class="para">
+ Note that it is probably easier to simply set the %home macro in your per-user $HOME/.rpmmacros file to the name of your home directory rather than try to figure this out programmatically.
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id721714" class="title">Defining Macros on the Command Line</h1></div></div></div><div class="para">
+ The rpm command also lets you define macros with the --define option. The basic syntax is:
+ </div><div class="para">
+ $ rpm --define 'macro_name value'
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ Do not place the leading percent sign, %, on the macro you define with --define.
+ </div><div class="para">
+ You can evaluate a macro or a macro expression with --eval. For example:
+ </div><div class="para">
+ $ rpm --eval %_usrsrc
+ </div><div class="para">
+ /usr/src
+ </div></div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id721750" class="title">Customizing Macros</h1></div></div></div><div class="para">
+ You can add your own macro definitions, using the syntax shown in the “Defining Macros in Macro Initialization Files†section. These macros are read on each invocation of the rpm or rpmbuild commands.
+ </div><div class="para">
+ To add your custom macros, you must edit one of the macro definition files. Table 21-2 lists the macro definition files and their usage.
+ </div><div class="para">
+ Table 21-2 RPM macro files
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ File
+ </div>
+
+ </td><td>
+ <div class="para">
+ Usage
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ /usr/lib/rpm/macros
+ </div>
+
+ </td><td>
+ <div class="para">
+ Official RPM macros
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ /etc/rpm/macros
+ </div>
+
+ </td><td>
+ <div class="para">
+ Per-system customizations
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ $HOME/.rpmmacros
+ </div>
+
+ </td><td>
+ <div class="para">
+ Per-user customizations
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ Note
+ </div><div class="para">
+ Do not edit the /usr/lib/rpm/macros file, as this file gets overwritten when you upgrade to a new version of rpm.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch19s05.html"><strong>Înapoi</strong>19.5. Summary</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch20s02.html"><strong>Înainte</strong>20.2. Configuring RPM Settings</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-dependencies.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-dependencies.html
new file mode 100644
index 0000000..9cb1ef9
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-dependencies.html
@@ -0,0 +1,121 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Cap. 5. Package Dependencies</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="index.html" title="Ghid RPM" /><link rel="prev" href="RPM_Guide-Using_RPM_DB-summary.html" title="4.4.4. Summary" /><link rel="next" href="ch05s02.html" title="5.2. Checking for Dependencies" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="RPM_Guide-Using_RPM_DB-summary.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch05s02.html"><strong>ÃŽnainte</
strong></a></li></ul><div xml:lang="ro" class="chapter" id="ch-dependencies" lang="ro"><div class="titlepage"><div><div><h2 class="title">Cap. 5. Package Dependencies</h2></div></div></div><div class="toc"><dl><dt><span class="sect1"><a href="ch-dependencies.html#id652095">5.1. Understanding the Dependency Concept</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch-dependencies.html#id662448">5.1.1. Capabilities</a></span></dt><dt><span class="sect2"><a href="ch-dependencies.html#id702044">5.1.2. Version dependencies</a></span></dt><dt><span class="sect2"><a href="ch-dependencies.html#id702074">5.1.3. Conflicts</a></span></dt><dt><span class="sect2"><a href="ch-dependencies.html#id735748">5.1.4. Obsoletes</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch05s02.html">5.2. Checking for Dependencies</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch05s02.html#id675733">5.2.1. Determining the capabilities a package requires</a></span></dt><dt><span class
="sect2"><a href="ch05s02s02.html">5.2.2. Determining the capabilities a package provides</a></span></dt><dt><span class="sect2"><a href="ch05s02s03.html">5.2.3. Checking for conflicts</a></span></dt><dt><span class="sect2"><a href="ch05s02s04.html">5.2.4. Determining which packages require a certain capability</a></span></dt><dt><span class="sect2"><a href="ch05s02s05.html">5.2.5. Determining which package provides a certain capability</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch05s03.html">5.3. Triggers</a></span></dt><dt><span class="sect1"><a href="ch05s04.html">5.4. Summary</a></span></dt></dl></div><div class="para">
+ This chapter covers:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Understanding dependencies
+ </div></li><li class="listitem"><div class="para">
+ Package capabilities
+ </div></li><li class="listitem"><div class="para">
+ Version dependencies
+ </div></li><li class="listitem"><div class="para">
+ Checking dependencies
+ </div></li><li class="listitem"><div class="para">
+ Triggers
+ </div></li></ul></div><div class="para">
+ Packages aren’t built in a vacuum. Web applications, for example, build on system networking libraries, system-encryption libraries, and system-file input and output libraries.
+ </div><div class="para">
+ This chapter covers dependencies between packages, along with ways to discover and manage those dependencies.
+ </div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id652095" class="title">Understanding the Dependency Concept</h1></div></div></div><div class="para">
+ A dependency occurs when one package depends on another. You might think it would make for an easier-to-manage system if no package depended on any others, but you’d face a few problems, not the least of which would be dramatically increased disk usage.
+ </div><div class="para">
+ Packages on your Linux system depend on other packages. Just about every package with an application, for example, depends on the system C libraries, since these libraries provide common facilities that just about every program uses. Network applications typically depend on low-level networking libraries. These dependencies really work in your favor, since a security bug fix in the network libraries can update all applications that make use of the updated libraries.
+ </div><div class="para">
+ Furthermore, sharing software means that each package has less code to maintain and thus improved quality. Code sharing has been in the computer lexicon since the 1960s.
+ </div><div class="para">
+ Although quite a few packages depend on system-level libraries, some packages depend on applications defined in other packages. The Emacs text editor package, for example, depends on the Perl scripting language, specifically, the perl command. Database client programs usually depend on the database server applications.
+ </div><div class="para">
+ The RPM database tracks dependency information, so it can, for example, stop attempts to remove packages that other packages depend on or inform users of dependent packages upon installation.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id662448" class="title">Capabilities</h1></div></div></div><div class="para">
+ In RPM terminology, each package provides capabilities. A capability is simply a text string that the package claims it provides. In most cases, a capability names a file or a package. But the capability can be any arbitrary text string.
+ </div><div class="para">
+ Other packages can then depend on certain capabilities. (You can use this concept in building your own packages.) Each package lists the capabilities it requires as well as the capabilities it provides.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ Package dependencies and capabilities are very important when creating spec files for building your own RPM packages, the subject of <a class="xref" href="ch-specfiles.html">Cap. 9, <em>Working with Spec Files</em></a> .
+ </div><div class="para">
+ When you install a package, the capability information is stored in the RPM database. When you remove a package, the rpm command checks the RPM database. If the package you are trying to remove provides a capability that another package needs, the command will generate an error. If you try to remove a package that other packages depend on, you'll see an error like the following:
+ </div><div class="para">
+ # rpm -e setup
+ </div><div class="para">
+ error: Failed dependencies:
+ </div><div class="para">
+ setup is needed by (installed) basesystem-8.0-1
+ </div><div class="para">
+ setup >= 2.0.3 is needed by (installed) initscripts-6.95-1
+ </div><div class="para">
+ setup >= 2.5.4-1 is needed by (installed) filesystem-2.1.6-5
+ </div><div class="para">
+ setup is needed by (installed) xinetd-2.3.7-2
+ </div><div class="para">
+ setup is needed by (installed) dump-0.4b28-4
+ </div><div class="para">
+ To verify that the package has not been removed, you can query for the package after trying to remove it, as shown following:
+ </div><div class="para">
+ # rpm -q setup
+ </div><div class="para">
+ setup-2.5.20-1
+ </div><div class="para">
+ This shows that the rpm command has not removed the setup package due to the errors.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ <a class="xref" href="ch-using-rpm.html">Cap. 3, <em>Using RPM</em></a> covers ways to force the rpm command to do what you want, although this can cause problems if you try to force the issue and remove a crucial package. In virtually all cases, do not use any of the force options, as this can cause problems with the RPM system, since the force options are purposely ignoring safety checks performed by the rpm command.
+ </div><div class="para">
+ Many capabilities that packages require are system libraries, especially shared libraries. Shared libraries, which usually have a .so file extension (short for shared object), provide a memory-efficient means for applications to share program code. These libraries may also have a .so.number extension, such as libc.so.6.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ Shared libraries on Windows are called DLLs, short for Dynamic Link Libraries. The implementations differ, but the Windows DLL concept is similar to Linux and Unix shared objects.
+ </div><div class="para">
+ Shared libraries have been part of Linux for a long time and have nothing to do with the RPM system. Shared libraries accessed by a program, however, represent natural dependencies. Because so many programs depend on shared libraries, the RPM system can automatically handle many shared-library dependencies.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ To list the shared libraries that a program accesses, use the ldd command, for example:
+ </div><div class="para">
+ $ ldd /bin/grep
+ </div><div class="para">
+ libc.so.6 => /lib/i686/libc.so.6 (0x42000000)
+ </div><div class="para">
+ /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
+ </div><div class="para">
+ Other dependencies include version-specific dependencies.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id702044" class="title">Version dependencies</h1></div></div></div><div class="para">
+ An application may depend on a capability provided by another package. It may also depend on the capability that a specific version of another package provides. For example, some add-ons to the Apache Web server depend on the version of Apache. The Apache 2.0 version made a number of changes that affect add-on packages. Some Apache add-on packages depend on version 1.3; others depend on version 2.0.
+ </div><div class="para">
+ Most package dependencies assume some level of compatibility and require a version at or above a given version number (for example, version 2.0 or later).
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ You’ll see more version dependencies when applications make major changes, such as the change from 1.3 to 2.0 for the Apache Web server.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id702074" class="title">Conflicts</h1></div></div></div><div class="para">
+ Some packages may provide capabilities that interfere with those in other packages. This is called a conflict. Installing conflicting packages is an error. For example, the httpd package (the Apache Web server) conflicts with the thttpd package. Both packages want to provide the primary Web server for a system.
+ </div><div class="para">
+ The RPM system will prevent you from installing packages that conflict with other packages. You can force the issue, using the techniques described in <a class="xref" href="ch-using-rpm.html">Cap. 3, <em>Using RPM</em></a> , and override the RPM system. But in most cases, you should not install packages that conflict.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id735748" class="title">Obsoletes</h1></div></div></div><div class="para">
+ The RPM system supports one more type of dependency, called obsoletes. This refers to a capability that a package provides that makes another capability obsolete. For example, a new version of the perl interpreter may make an older version obsolete. In most cases, the obsoletes dependency should be used when the name of a package changes. For example, the apache Web server package became the httpd package. You would expect the new package, httpd, to obsolete the old package name, apache.
+ </div><div class="para">
+ This brings the total to four types of dependencies that the RPM system tracks:
+ </div><div class="para">
+ *Requires, which tracks the capabilities a package requires
+ </div><div class="para">
+ *Provides, which tracks the capabilities a package provides for other packages
+ </div><div class="para">
+ *Conflicts, which describes the capabilities that if installed, conflict with capabilities in a package
+ </div><div class="para">
+ *Obsoletes, which describes the capabilities that this package will make obsolete
+ </div><div class="para">
+ Packages advertise this dependency information. Each dependency holds the type, such as requires, a capability, such as a shared library or a package name, and optionally a version number, such as requiring the python package at a version number greater than or equal to 2.2 (python >= 2.2).
+ </div><div class="para">
+ </div><div class="para">
+ You can check package dependencies by using, as you’d guess, the rpm command.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="RPM_Guide-Using_RPM_DB-summary.html"><strong>Înapoi</strong>4.4.4. Summary</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch05s02.html"><strong>Înainte</strong>5.2. Checking for Dependencies</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-development-tools.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-development-tools.html
new file mode 100644
index 0000000..527e1e7
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-development-tools.html
@@ -0,0 +1,36 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Cap. 26. Linux Text Editors and Development Tools</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="index.html" title="Ghid RPM" /><link rel="prev" href="ch25s02.html" title="25.2. Accessing RPM Mailing Lists and Newsgroups" /><link rel="next" href="ch26s02.html" title="26.2. Programming Text Editors" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch25s02.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch26s02.html"><strong>ÃŽnainte</strong></a><
/li></ul><div xml:lang="ro" class="chapter" id="ch-development-tools" lang="ro"><div class="titlepage"><div><div><h2 class="title">Cap. 26. Linux Text Editors and Development Tools</h2></div></div></div><div class="toc"><dl><dt><span class="sect1"><a href="ch-development-tools.html#id496359">26.1. General Text Editors</a></span></dt><dt><span class="sect1"><a href="ch26s02.html">26.2. Programming Text Editors</a></span></dt><dt><span class="sect1"><a href="ch26s03.html">26.3. Integrated Development Environments for C Programming</a></span></dt><dt><span class="sect1"><a href="ch26s04.html">26.4. Integrated Development Environments for Python Programming</a></span></dt></dl></div><div class="para">
+ This appendix covers:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ General text editors
+ </div></li><li class="listitem"><div class="para">
+ C-specific tools and integrated development environments
+ </div></li><li class="listitem"><div class="para">
+ Python-specific development tools
+ </div></li></ul></div><div class="para">
+ Linux includes a number of text editors and integrated development environments (IDEs), going from plain old text editors all the way up to sophisticated tools. These tools are suitable for shell scripting, C, Python, and Perl programming, along with a plethora of other uses. Linux makes extensive use of text files, especially for configuration data, so Linux has always included a number of text editors.
+ </div><div class="para">
+ This appendix lists a number of tools for those who have not yet set up an RPM development environment on Linux. Note that choosing an editor or IDE is mostly a matter of personal taste. Programmers will often engage in raging battles over the superiority of text editors and other programming tools. Before searching around too far, try out what you have installed on your system and see if that works for you.
+ </div><div class="para">
+ Note that Internet sites may change or disappear, so you may have to search to find these tools.
+ </div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id496359" class="title">General Text Editors</h1></div></div></div><div class="para">
+ Linux distributions include a number of text editors with varying sets of features. The two most common editors are vi and emacs, which come with virtually all Linux distributions. These editors are good for UNIX- or Linux-savvy developers, but generally have a steep learning curve for developers used only to Windows.
+ </div><div class="para">
+ If you come from Windows, try gedit, kedit, or kate. These text editors open a graphical window on your desktop, making them appear more or less like the Windows Notepad.exe. All three offer more features than Notepad.exe, however.
+ </div><div class="para">
+ You may not have installed any of these editors, but all are available as part of Red Hat Linux. You can install vi, emacs, gedit, kedit, or kate from the packages that come with your Linux distribution.
+ </div><div class="para">
+ To start one of the editors, enter a command like the following:
+ </div><div class="para">
+ $ gedit listrpmpkgs &
+ </div><div class="para">
+ The ampersand, &, launches the program in the background. Replace gedit with the editor you choose.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch25s02.html"><strong>Înapoi</strong>25.2. Accessing RPM Mailing Lists and Newsgroups</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch26s02.html"><strong>Înainte</strong>26.2. Programming Text Editors</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-extra-packaging-tools.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-extra-packaging-tools.html
new file mode 100644
index 0000000..556c9d8
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-extra-packaging-tools.html
@@ -0,0 +1,667 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Cap. 12. Supplemental Packaging Software</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="index.html" title="Ghid RPM" /><link rel="prev" href="ch11s05.html" title="11.5. Summary" /><link rel="next" href="ch12s02.html" title="12.2. Summary" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch11s05.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch12s02.html"><strong>ÃŽnainte</strong></a></li></ul><div xml:lang="ro" class="chapter" id="ch-e
xtra-packaging-tools" lang="ro"><div class="titlepage"><div><div><h2 class="title">Cap. 12. Supplemental Packaging Software</h2></div></div></div><div class="toc"><dl><dt><span class="sect1"><a href="ch-extra-packaging-tools.html#id804948">12.1. Packaging Aids</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch-extra-packaging-tools.html#id643503">12.1.1. Using VIM spec plugins to improve spec file editing</a></span></dt><dt><span class="sect2"><a href="ch-extra-packaging-tools.html#id622758">12.1.2. Adding functions with emacs rpm-spec-mode</a></span></dt><dt><span class="sect2"><a href="ch-extra-packaging-tools.html#id559610">12.1.3. Validating and debugging spec files with rpmlint</a></span></dt><dt><span class="sect2"><a href="ch-extra-packaging-tools.html#id820477">12.1.4. Generating the %files section with RUST</a></span></dt><dt><span class="sect2"><a href="ch-extra-packaging-tools.html#id568330">12.1.5. setup.sh and MakeRPM.pl</a></span></dt><dt><span class="s
ect2"><a href="ch-extra-packaging-tools.html#id568375">12.1.6. Manipulating Package Files with rpm2cpio</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch12s02.html">12.2. Summary</a></span></dt></dl></div><div class="para">
+ This chapter covers:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Understanding packaging aids
+ </div></li><li class="listitem"><div class="para">
+ Manipulating packages
+ </div></li></ul></div><div class="para">
+ RPM is intended to make system management easier, both for system administrators and other users who do all the day-to-day work of installing and removing applications and for developers and other users who do all the work of preparing applications for installation. For RPM packagers, the work involved in preparing an application for installation has two phases: first, the software must be compiled (if it is not written in an interpreted language such as Perl) and otherwise configured for the system on which it will be installed; then the RPM package of the software must be prepared by creating a spec file that properly packages it into an RPM. In contrast, packagers who choose to package applications in a simpler format, such as gzipped tarballs (compressed tar archives), have less work ahead of them, since they need only concern themselves with the first step.
+ </div><div class="para">
+ After a packager has prepared an RPM package once, RPM makes the first step (compilation and configuration) easier when the packager has to package an updated version of the same software; RPM does a lot of work to track compilation commands, any needed patches, and any configuration modifications discovered to be necessary to prepare the software. Similarly, once an RPM spec file has been produced for an application, updating that spec file to support a newer version of that application is usually trivial. For these reasons, using RPM instead of a simpler, less end-user-friendly package format (such as gzipped tarballs) is a bit of a tradeoff for the packager; preparing an RPM of an application requires a little more initial time and work than preparing a gzipped tarball of that same application, but once created, the RPM package takes less time and effort to keep current than the gzipped tarball requires.
+ </div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id804948" class="title">Packaging Aids</h1></div></div></div><div class="para">
+ However, several helper tools are also available for RPM packagers. These tools can be used at various stages in the process of producing a high-quality RPM package to simplify the tasks that an RPM packager must perform. These tools include syntax-highlighting modes for various text editors, making production and maintenance of spec files easier; macro packages for popular text editors, simplifying the generation and maintenance of spec files; tools that generate spec files, simplifying initial spec file creation; and debuggers that validate produced binary RPMs, helping ensure that the spec file used to create the packages is accurate and high quality.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id643503" class="title">Using VIM spec plugins to improve spec file editing</h1></div></div></div><div class="para">
+ Unix systems have traditionally shipped the legendary (or notorious, depending upon your point of view) vi editor (pronounced vee eye) as their default text editor. Vi was initially developed by Bill Joy in 1976 for BSD Unix. It eventually was incorporated in AT& T System V Unix as well and later was mandated by the POSIX 1003 standards (which define what an OS must have to be Unix-compatible), thereby conquering all facets of the Unix world.
+ </div><div class="para">
+ The original vi source code is no longer freely available, but several clones of the vi program have been created over the years. The most popular of these vi clones is probably Vi IMproved, or VIM (www.vim.org). VIM is the standard vi implementation (meaning that when you type vi at the command prompt, the program you really are running is vim) on many Linux distributions, including Red Hat Linux. It is also freely available for most other Unixes and even for non-Unix systems such as Microsoft Windows.
+ </div><div class="para">
+ VIM is a fully backwards-compatible implementation of the original vi editor, although it also offers many additional features that vi did not support. One VIM feature that can be extremely useful when preparing spec files is colorized syntax highlighting. VIM has an extensible interface through which it can be told about the syntax used for files of various types. Once it understands a filetype's syntax, it can color the various syntactic structures of that file in different ways. For example, when editing a Bourne shell script using VIM, comments are typically blue, control statements (if, for, do, and so on) are yellow, variables are purple, and so forth. Many people find this feature very useful, since a single glance reveals the entire logical structure of the file. Furthermore, errors in the file (such as a missing done statement failing to close a do loop in a Bourne shell script) are often immediately obvious when using such a colorizing editor.
+ </div><div class="para">
+ Usually, VIM does not understand the structure of RPM spec files. When preparing a spec file, VIM displays all text in the same color. A spec.vim syntax file is available for VIM that makes VIM aware of the syntax used for RPM spec files. When this file is used, the various structural components (%define, preamble statements, %build, and so forth) are all colorized, making the logic of the spec file readily apparent.
+ </div><div class="para">
+ The spec.vim file that provides VIM with an understanding of spec-file syntax is bundled with newer versions of VIM, or it can be downloaded from the Internet. Most RPM-based Linux distributions, including Red Hat Linux, ship this file with VIM as part of their distribution and even automatically configure VIM to load this syntax file any time an RPM spec file is being edited. When using VIM on a system that does not automatically load spec.vim whenever spec files are edited, you should download the spec.vim file (I tend to save such personal extensions in ~/etc/vim, but you can save it any place you prefer).
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ Download the spec.vim syntax file for VIM from <a href="http://www.panix.com/~elflord/vim/syntax/spec.vim">http://www.panix.com/~elflord/vim/syntax/spec.vim</a>
+ </div><div class="para">
+ Once downloaded, configure VIM to load your new syntax file. You can do this by putting the following in your ~/.vimrc file (assuming you have saved the file as ~/etc/vim/spec.vim; adjust the path as necessary if you saved it elsewhere):
+ </div><div class="para">
+ augroup syntax
+ </div><div class="para">
+ au! BufNewFile,BufReadPost *.spec so ~/etc/vim/spec.vim
+ </div><div class="para">
+ au BufNewFile,BufReadPost *.spec so ~/etc/vim/spec.vim
+ </div><div class="para">
+ augroup END
+ </div><div class="para">
+ This statement will instruct VIM to load the syntax file whenever a file named with a .spec extension is edited. You can now even customize the colors which VIM uses, if you like, by editing ~/etc/vim/spec.vim!
+ </div><div class="para">
+ The VIM editor has hundreds of built-in commands for formatting text. If necessary, it can even be extended with new commands. Furthermore, these commands can be defined in FileType plugins, so that different commands are loaded depending upon the type of file being edited (just as different syntax matching can be used depending upon the type of file being edited). Gustavo Niemeyer has written a spec plugin, pi_spec, which defines various commands that can be used when working with RPM spec files. Currently, this plugin can be used to automate maintenance of the %changelog section of RPM spec files.
+ </div><div class="para">
+ By default, the spec plugin provides a macro, spec_chglog, which is mapped to the <LocalLeader>-c key. Normally, the LocalLeader key in VIM is mapped to "\", a backslash character. This means you press \c to load the spec_chglog macro. If desired, you can instead map spec_chglog to a different key by putting a statement like the following in your ~/.vimrc file.
+ </div><div class="para">
+ au FileType spec map <buffer> C <Plug>SpecChangelog
+ </div><div class="para">
+ In this case, that statement would map the macro to the "C" key, but you can map it to a different key by replacing the "C" in the statement with whichever key or key combination you prefer.
+ </div><div class="para">
+ The spec_chglog macro checks the %changelog in the spec file currently being edited and makes sure that the last entry in this %changelog was written today and was written by you. If it was, the macro adds a new item to the entry. If it was not written today, or was written today, but not by you, the macro adds an entirely new entry. Optionally, the macro also checks that the name, version, and release of the package are correct and will update the release if it is incorrect. In addition, the macro maps the percent key, %, making it usable in command mode in VIM to move quickly between sections within a spec file.
+ </div><div class="para">
+ To help spec_chglog, you can define a few variables in your ~/.vimrc file to customize its behavior. The variable spec_chglog_format defines what the macro uses for new %changelog entries. If you do not define this variable, the macro will ask you for an e-mail address and construct it for you the first time you use the macro. Alternatively, you can customize it yourself by adding an entry like the following to your ~/.vimrc file.
+ </div><div class="para">
+ let spec_chglog_format = "%a %b %d %Y Your Name <your at email.address>"
+ </div><div class="para">
+ The preceding format is what Red Hat's developers use for Red Hat Linux spec files and results in a %changelog entry that looks like the following, with the user name and e-mail address changed to protect the innocent:
+ </div><div class="para">
+ * Mon Apr 15 2002 Bob Marley <bob at marley.yow>
+ </div><div class="para">
+ The variables in the spec_chglog_format control the time format that is used. If you want different time formats in your %changelog entry, you can replace the variables (using %A instead of %a would cause the full weekday name, such as "Monday", to be printed) using the documentation in the strftime(3) man page as a guideline.
+ </div><div class="para">
+ By default, the macro will insert new entry items after existing items. For example, if I already have a %changelog entry for today that reads as follows:
+ </div><div class="para">
+ * Mon May 6 2002 Bob Marley <bob at marley.yow>
+ </div><div class="para">
+ - Updated to newest release
+ </div><div class="para">
+ Then, using the macro to add a new entry for an additional patch I added will, by default, result in an entry that reads:
+ </div><div class="para">
+ * Mon May 6 2002 Bob Marley <bob at marley.yow>
+ </div><div class="para">
+ - Updated to newest release
+ </div><div class="para">
+ - Added Solaris compile patch
+ </div><div class="para">
+ If I want, I can instead have new items inserted before existing items, so that my second entry instead looks like
+ </div><div class="para">
+ * Mon May 6 2002 Bob Marley <bob at marley.yow>
+ </div><div class="para">
+ - Added Solaris compile patch
+ </div><div class="para">
+ - Updated to newest release
+ </div><div class="para">
+ To have new items inserted before existing items, simply add the following line to your ~/.vimrc file:
+ </div><div class="para">
+ let spec_chglog_prepend = 1
+ </div><div class="para">
+ Optionally, the macro can track version and release numbers in the %changelog entries automatically. Adding the line
+ </div><div class="para">
+ let spec_chglog_release_info = 1
+ </div><div class="para">
+ results in the first item in every changelog entry automatically reflecting the version and release, so that my %changelog entry might instead look like the following:
+ </div><div class="para">
+ * Mon May 6 2002 Bob Marley <bob at marley.yow>
+ </div><div class="para">
+ + httpd-2.0.36-2
+ </div><div class="para">
+ - Updated to newest release
+ </div><div class="para">
+ - Added Solaris compile patch
+ </div><div class="para">
+ If this feature is enabled, the macro automatically checks the version and release information to make sure that they have increased. If they haven't, it will offer to update them for you. Add the following line to your ~/.vimrc file to disable this feature, if necessary.
+ </div><div class="para">
+ let spec_chglog_never_increase_release = 1
+ </div><div class="para">
+ This spec plugin ships with newer versions of VIM. Both it and the VIM spec syntax highlighting extensions can be very useful for speeding spec file editing and debugging, and are well worth trying out if you are a VIM user.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ You can find out more about vim at www.vim.org.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id622758" class="title">Adding functions with emacs rpm-spec-mode</h1></div></div></div><div class="para">
+ Of course, not everyone in the world uses VIM. Another commonly used editor is the emacs editor originally developed by Richard M. Stallman. Unlike vi, emacs is not considered an essential Unix component and is not always found installed on a Unix system, although it is bundled with just about every Linux distribution.
+ </div><div class="para">
+ Over the years, two major emacs variants have emerged. GNU Emacs is produced by the Free Software Foundation and can be downloaded from www.gnu.org/software/emacs/emacs.html. XEmacs is based on GNU Emacs and is available from www.xemacs.org. Historically, the two differed in their user interfaces (XEmacs, as the name suggests, had an X Window interface, though GNU Emacs has one as well these days) and in some technical details of how they operated. Both are freely available under the terms of the GNU GPL, so you can download and try either or both if they are not already on your system.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ See <a class="xref" href="ch-licensing.html">Cap. 27, <em>Licensing RPM</em></a> for more on the GNU GPL, or General Public License.
+ </div><div class="para">
+ Red Hat Linux includes RPMs of both GNU Emacs and XEmacs as part of the distribution, and most other Linux distributions will include one or both as well.
+ </div><div class="para">
+ Like VIM, both GNU Emacs and XEmacs support syntax highlighting. They are also both extensible, having the ability to load mode files that add new commands and functions. Stig Bjørlykke has written a mode, rpm-spec-mode.el, which works with both GNU Emacs and with XEmacs to add many functions, making it easier to use when editing RPM spec files. Red Hat Linux includes and enables this mode in both GNU Emacs and XEmacs, as do many other Linux distributions.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ You can download this emacs mode from http://tihlde.org/~stigb/rpm-spec-mode.el.
+ </div><div class="para">
+ After downloading, you will need to put the following lines in your ~/.emacs init files (for GNU Emacs) or ~/.xemacs init files (for XEmacs) to instruct emacs to load rpm-spec-mode whenever a file with a .spec extension is being edited:
+ </div><div class="para">
+ (autoload 'rpm-spec-mode "rpm-spec-mode.el" "RPM spec mode." t)
+ </div><div class="para">
+ (setq auto-mode-alist (append '(("\\.spec" . rpm-spec-mode)) auto-mode-alist))
+ </div><div class="para">
+ </div><div class="para">
+ Once installed, rpm-spec-mode will provide emacs with additional support for editing RPM spec files. Figure 13-1 shows this mode in GNU Emacs.
+ </div><div class="para">
+ 54965-0 Fg1301.tiff here; needs to be cropped to just the central window
+ </div><div class="para">
+ Figure 13-1: Gnu Emacs using rpm-spec-mode
+ </div><div class="para">
+ Figure 13-2 shows this mode in XEmacs.
+ </div><div class="para">
+ 54965-0 Fg1302.tiff here; needs to be cropped to just the central window
+ </div><div class="para">
+ Figure 13-2: XEmacs using rpm-spec-mode
+ </div><div class="para">
+ With this mode, emacs can do syntax highlighting of spec files, just like VIM. The mode file rpm-spec-mode.el contains the emacs instructions that specify what should be highlighted and what colors should be used for highlighting.
+ </div><div class="para">
+ Tip
+ </div><div class="para">
+ If you do not see syntax highlighting when you edit a spec file, your emacs session may or may not be currently configured to do syntax highlighting. First, make sure that the status bar at the bottom of your emacs window says (RPM-SPEC), indicating that rpm-spec-mode is being used. If it doesn't, double-check the rpm-spec-mode installation instructions. If the status bar does indicate that you are using rpm-spec-mode, also double-check that syntax highlighting (which, in emacs, is a global configuration option) has been enabled. In both GNU Emacs and XEmacs, the Options menu has a Syntax Highlighting option that must be enabled before emacs will colorize spec file syntactic structures.
+ </div><div class="para">
+ In addition to providing syntax colorization, rpm-spec-mode adds a variety of new functions to emacs that can be used to speed the process of creating or editing RPM spec files. These new functions appear on the RPM-Spec menu that is added to emacs by rpm-spec-mode. Many of the functions are similar to the functions added to VIM by the spec_chglog macro. Navigation functions to move quickly through a spec file are provided, so that Ctrl+C, Ctrl+N (press Ctrl+C followed by Ctrl+N) will move the cursor to the next major section of the spec file, while Ctrl+C, Ctrl+P will move the cursor to the prior major section of the spec file. Similarly, macros are also defined to increment the release tag (Ctrl+C, R) and the very handy option to add new %changelog entries (Ctrl+C, E). Like the VIM macros for adding %changelog entries, the rpm-spec-mode command checks to see if an entry already exists for today. If not, it adds a new entry, but if so, it just adds a new item to the exist
ing entry. For %changelog entries to have the correct e-mail address, the emacs variable user-mail-address must be set correctly. If it is not set on your system, you can add the following line to your emacs initialization files:
+ </div><div class="para">
+ (setq user-mail-address "your at email.address")
+ </div><div class="para">
+ In addition to these basic functions, rpm-spec-mode offers more advanced spec file creation support. Opening a new buffer in emacs for a spec file that does not already exist automatically generates a skeleton spec file.
+ </div><div class="para">
+ To further speed things up, emacs offers a number of macros for the main tasks in writing an RPM spec file. Table 13-1 lists these macros.
+ </div><div class="para">
+ Table 13-1Macro commands for The RPM SPEC MODE IN EMacs
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Command
+ </div>
+
+ </td><td>
+ <div class="para">
+ Function
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Ctrl+C Tab
+ </div>
+
+ </td><td>
+ <div class="para">
+ Adds a new tag to the spec file
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Ctrl+C Ctrl+F F
+ </div>
+
+ </td><td>
+ <div class="para">
+ Adds a new file to the %files section
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Ctrl+C Ctrl+F C
+ </div>
+
+ </td><td>
+ <div class="para">
+ Adds a new configuration file to the %files section
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Ctrl+C Ctrl+F D
+ </div>
+
+ </td><td>
+ <div class="para">
+ Adds a new documentation file to the %files section
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Ctrl+C Ctrl+F G
+ </div>
+
+ </td><td>
+ <div class="para">
+ Adds a new ghost file to the %files section
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Ctrl+C Ctrl+D D
+ </div>
+
+ </td><td>
+ <div class="para">
+ Adds a new directory to the %files section
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Ctrl+C Ctrl+D O
+ </div>
+
+ </td><td>
+ <div class="para">
+ Adds a new documentation directory to the %files section
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Ctrl+C Ctrl+C U
+ </div>
+
+ </td><td>
+ <div class="para">
+ Changes the umask in %defattr entries in %files
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Ctrl+C Ctrl+C O
+ </div>
+
+ </td><td>
+ <div class="para">
+ Changes the owner in %defattr entries in %files
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Ctrl+C Ctrl+C G
+ </div>
+
+ </td><td>
+ <div class="para">
+ Changes the group in %defattr entries in %files
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ Furthermore, rpm-spec-mode even adds macros to emacs that can be used to build RPMs from spec files without even having to exit emacs! Since the process of constructing spec files is often iterative (make new spec, build RPM from spec, find mistake, edit spec, build RPM from spec, find mistake, and so on), this capability of emacs to be used as an IDE for RPM package generation is extremely useful. Basic macros exist to do complete builds (Ctrl+C B to build a binary package, Ctrl+C S to build a source package, and Ctrl+C A to build both). Macros can also be used to execute various intermediate steps, such as the %prep stage (Ctrl+C P), the %build stage (Ctrl+C C), or the %install stage (Ctrl+C I). Various options of the build process can also be controlled, such as GPG-signing of generated packages.
+ </div><div class="para">
+ If you are a user of GNU Emacs or XEmacs, you should definitely take the time to learn to use rpm-spec-mode. Being able to build packages from within the editor where you are editing the spec file that builds those packages is a great productivity gain for many people.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id559610" class="title">Validating and debugging spec files with rpmlint</h1></div></div></div><div class="para">
+ Both VIM and emacs extensions help with the process of initially creating spec files and with the maintenance of existing RPM spec files. After a spec file has been created, and RPMs have been created using that spec, the binary RPMs generated from the spec can be validated using the rpmlint command. The name rpmlint comes from lint, the traditional Unix utility that can "sanity-check" C source code, looking for certain classes of common C coding mistakes. The idea behind rpmlint is similar; it processes binary RPMs, checking for certain common mistakes made by RPM packagers.
+ </div><div class="para">
+ The rpmlint command currently ships with a wide variety of checks and is written using a modular interface so that additional checks can easily be added if needed. Currently, rpmlint can check that all binary files in the package are correct (making sure that a .noarch.rpm package does not contain binary files, that no binaries are being installed in /etc, that the binary file types in the package are appropriate for the package architecture, that shared libraries are configured correctly, and that all executables are stripped). It can also check the validity of files marked as configuration files in the RPM (ensuring that configuration files are only being installed in /etc, not in /usr) and that the package file complies with the distribution's policies for packages (checking things such as the compression of man pages and Info pages and the correctness of vendor and distribution fields in the package header).
+ </div><div class="para">
+ In addition, rpmlint performs a variety of checks to ensure that the package complies with the Filesystem Hierarchy Standard (verifying that files are installed in their standard locations on the system), the Linux Standards Base (verifying that package-file naming is LSB-compliant) and that files have correct ownerships and permissions. Init scripts are double-checked (for packages that have init scripts) to ensure that the basic structure of the init script is correct and that appropriate %post and %preun configuration directives are being run to configure the init script on the system. %post, %pre, and %preun scripts are also double-checked (ensuring that only valid interpreters are specified for scripts and that scripts are written in valid syntax). The validity of the package itself is also checked in various ways (ensuring that the package is GPG-signed, that the package's source RPM is correctly prepared, that the package spec file uses correct syntax, and that all
tags used in the package header are valid).
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ To find out more about the Filesystem Hierarchy Standard, see www.pathname.com/fhs/. To find out more about the Linux Standards Base, see www.linuxbase.org.
+ </div><div class="para">
+ Download rpmlint from www.lepied.com/rpmlint. It is written entirely in Python, so a Python interpreter is necessary to run it.
+ </div><div class="para">
+ Once installed, rpmlint can be configured on a system-wide basis, using the /etc/rpmlint/config file, or on a per-user basis, using the $HOME/.rpmlintrc file. This file can specify checks to perform, check output that should be ignored, and configuration options. Configuration options can be specified, listing what entries are valid for various fields in the RPM header, such as the Vendor and Packager fields. By default, Red Hat Linux ships with this configuration file set to validate packages to make sure they are suitable for Red Hat Linux; if packaging for a different distribution, this file might need to be modified.
+ </div><div class="para">
+ Once rpmlint has been installed and configured, it can be run against RPMs. For example, rpmlint helps with creating packages, such as tin (a popular Usenet client) for Red Hat Linux, since it is not included with the distribution. After preparing a tin spec file, then building RPMs from that file, you can typically double-check them using rpmlint.
+ </div><div class="para">
+ For example, when running rpmlint on a source RPM, you’ll see output like the following:
+ </div><div class="para">
+ $ rpmlint tin-1.5.12-1.src.rpm
+ </div><div class="para">
+ E: tin no-packager-tag
+ </div><div class="para">
+ W: tin invalid-license distributable
+ </div><div class="para">
+ W: tin no-url-tag
+ </div><div class="para">
+ W: tin strange-permission tin-1.5.12.tar.bz2 0664
+ </div><div class="para">
+ W: tin obsolete-tag Copyright
+ </div><div class="para">
+ $
+ </div><div class="para">
+ For the most part, this package looks fine according to the rpmlint output. The permissions on the tin source code can be changed (0644 is the "preferred" permissions), and you might want to change my spec file to use the License tag instead of the now-obsolete Copyright tag. Similarly, you might want to add a URL tag to the package to point to the URL for the software.
+ </div><div class="para">
+ When running rpmlint on a binary RPM, you’ll see output like the following:
+ </div><div class="para">
+ $ rpmlint tin-1.5.12-1.i386.rpm
+ </div><div class="para">
+ W: tin invalid-vendor None
+ </div><div class="para">
+ W: tin invalid-distribution None
+ </div><div class="para">
+ E: tin no-packager-tag
+ </div><div class="para">
+ W: tin invalid-license distributable
+ </div><div class="para">
+ W: tin no-url-tag
+ </div><div class="para">
+ $
+ </div><div class="para">
+ With this output, the binary package looks fine. You should set a I don’t bother setting a vendor, distribution, and packager but you can ignore those warnings. Similarly, rpmlint warns because it does not recognize the license type used, "distributable". You can fix this, you can ignore this, or you can modify /etc/rpmlint/config so that rpmlint recognizes "distributable" as a valid license.
+ </div><div class="para">
+ The sorts of validity checks that rpmlint can do make it valuable for ensuring the quality and consistency of RPMs. Most RPM-based Linux distributions validate their entire distribution using rpmlint. Using it for packages you prepare is a good idea as well.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id820477" class="title">Generating the %files section with RUST</h1></div></div></div><div class="para">
+ For the most part, maintaining RPM spec files is relatively straightforward. Creating spec files from scratch, however, can be a little bit more challenging. Tools like rpm-spec-mode for emacs can help with the process, generating skeleton spec file templates that can be filled in, but these sorts of tools do not address the step that most new RPM packagers seem to find most difficult: generating the %files section. Creating a complete, accurate list of all needed files supplied by an application can be difficult, particularly when it is an application with which you are unfamiliar. Most software supports installation to a temporary location; if the software you are packaging allows this, generation of %files is (almost) as simple as using BuildRoot to install the application to a temporary directory, then running an ls -lR command in that subdirectory to see all the installed files and directories. Even then, though, the output from ls -lR must be cleaned up and converted
into %files format for adding to the spec file. All of this takes time.
+ </div><div class="para">
+ A couple of tools exist to reduce the amount of work needed for this stage of the process, automating the generation of the %files section of spec files. The most sophisticated of these toolsets is RUST.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ Download RUST from www.rusthq.com.
+ </div><div class="para">
+ RUST consists of two tools: crust and rust. The crust command provides a command-line tool that can create a chroot() jail, in which software can be built and installed, and then automatically generate a spec file that documents the files that were installed. This not only eliminates the need to generate a %files section for a spec file manually but also removes the need to modify software to support installation to a temporary location using BuildRoot, a sometimes difficult task.
+ </div><div class="para">
+ The rust command provides a graphical front end to the crust command, as shown in Figure 13-3.
+ </div><div class="para">
+ 54965-0 Fg1303.tiff here
+ </div><div class="para">
+ Figure 13-3: rust, a drag-and-drop spec file generator
+ </div><div class="para">
+ The rust command provides a graphical interface that can be used to control crust and supports drag-and-drop creation of spec files. In the rust interface, two file trees are displayed. The left-hand tree displays the local file system, while the right-hand tree displays the file tree inside the crust chroot() jail. Files that should be packaged together can just be dragged from their current locations on the system (displayed in the left-hand tree) to their final destinations in the right-hand tree. You can then click the makeRPM choice to generate an RPM containing those files. Although not terribly useful for packages being generated from source code, this feature can greatly simplify creation of RPMs of applications that are only supplied in binary format (such as the Linux Adobe Acrobat reader).
+ </div><div class="para">
+ RUST's rust application can be useful in some circumstances (providing new developers a graphical tool that can be used to generate binary RPMs), and crust is more generally useful for packaging difficult-to-package software that needs to be built and installed in a chroot() jail. Unfortunately, development of RUST appears to have stopped, so extension of RUST to become a more generally useful IDE for RPM generation is not likely to happen. However, the project is licensed under the GNU GPL (<a class="xref" href="ch-licensing.html">Cap. 27, <em>Licensing RPM</em></a> ), so it might be resumed by another developer or team of developers.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id568330" class="title">setup.sh and MakeRPM.pl</h1></div></div></div><div class="para">
+ Other tools that have been developed to simplify the process of creating an RPM spec file take an entirely different approach. Tools such as setup.sh, available from www.mmedia.is/~bre/programs/setup.sh, are intended to function as wrappers around the existing build commands (./configure and make) for software. These types of tools take the approach of using the standard build tools for software (since those tools must always be used to build the software, whether using RPM or compiling the software from a source tarball) and capturing the output to generate an RPM spec file automatically.
+ </div><div class="para">
+ The MakeRPM.pl Perl script, available from www.perl.com/CPAN/modules/by-authors/id/JWIED, is another example of such an approach. MakeRPM.pl is a more specialized tool than setup.sh, as MakeRPM.pl is intended only for producing RPMs from Perl modules packaged in CPAN (www.cpan.org). It is implemented as a wrapper around the standard commands (perl Makefile.PL ; make ; make test ; make install) used to install Perl CPAN software.
+ </div><div class="para">
+ MakeRPM.pl actually works quite well for its intended purpose at mdproducing packages of CPAN modules. The setup.sh script is currently viewable mainly as a proof of concept, rather than being a generally universal automatic spec file generator. In the future, when spec files are likely to be representable using a formal closed-syntax grammar, it is possible that more generalized spec file generation tools will be developed. Until that time, however, some of the previously mentioned tools, particularly the VIM and emacs extensions, can provide assistance when manually generating spec files.
+ </div><div class="para">
+ Cross-reference
+ </div><div class="para">
+ For more discussion of the future of RPM, you can turn to <a class="xref" href="ch-rpm-evolution.html">Cap. 23, <em>RPM Feature Evolution</em></a> .
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id568375" class="title">Manipulating Package Files with rpm2cpio</h1></div></div></div><div class="para">
+ Normally, RPM packagers are concerned with taking source code or binary files, and producing an RPM that contains those files and can be used to install them on end-users' systems. Sometimes, packagers and end users find themselves in the opposite position, that of having a source or binary RPM package file and needing to extract its contents. An RPM can always be installed to access its contents (either source code, patches, and a spec file which get put under %_topdir for a source RPM, or software which gets put in system directories for a binary RPM), but that is often overkill. I frequently want to extract a single patch file, or the spec file, from a source RPM, but I don't really need to install the entire source RPM. Similarly, people often want to extract the contents of RPMs on systems that do not come with RPM, such as Solaris.
+ </div><div class="para">
+ Fortunately, tools are available that can process RPM package files into a format from which their content can be extracted. Structurally speaking, RPM package files are compressed cpio archives that have additional binary data added to the beginning containing various meta-data about the package (specifying its architecture and OS, for example), a GPG signature if the package is signed, and so forth. If this binary data is removed from the beginning of the RPM package file, the remainder is a System V Release 4-style cpio file that can be manipulated using any reasonably complete cpio command. Several different tools, each sporting the name rpm2cpio, are available which can do this binary data removal, converting an RPM package file into a standard cpio archive.
+ </div><div class="para">
+ RPM ships with an rpm2cpio utility that can be used to convert RPM package files to cpio files. (<a class="xref" href="ch-rpm-overview.html">Cap. 2, <em>RPM Overview</em></a> introduces the rpm2cpio utility.) For example, if you have a source RPM package file and want to extract its files without having to install it, you can process it through rpm2cpio. The rpm2cpio command takes as input an RPM package file, and produces a cpio file on standard output. For example, to redirect the output to a file, use a command like the following:
+ </div><div class="para">
+ $ rpm2cpio fluxbox-0.1.8-2.src.rpm > fluxbox-0.1.8-2.cpio
+ </div><div class="para">
+ $
+ </div><div class="para">
+ This command creates a cpio archive from the package. You can later use cpio commands on the output file. You can also pipe the output of rpm2cpio through the cpio command:
+ </div><div class="para">
+ $ rpm2cpio fluxbox-0.1.8-2.src.rpm | cpio -i -d
+ </div><div class="para">
+ 656 blocks
+ </div><div class="para">
+ $
+ </div><div class="para">
+ This command extracts the contents of the package.
+ </div><div class="para">
+ This rpm2cpio command is bundled with RPM and is installed on most RPM-based Linux distributions, including Red Hat Linux. However, it is less useful on systems that do not come with RPM, such as Solaris. This "standard" implementation of rpm2cpio is written in C, and so must be compiled before it can be used. Since most commercial Unix systems do not come with a C compiler by default (unlike Linux and other free Unixes, such as the BSD operating systems), compiling this rpm2cpio code can be a major undertaking.
+ </div><div class="para">
+ Fortunately, rpm2cpio implementations are also available in a couple of other languages, in more easy-to-install formats for other operating sytsems, including as a Bourne shell script or a Perl script. The Bourne shell syntax should work on any reasonably modern Unix system (and even a few non-Unix systems; it also works on Microsoft Windows under cygwin, for example). The script in Listing 13-1should be saved to a file named rpm2cpio.sh, marked executable, and copied to a directory in your path.
+ </div><div class="para">
+ Listing 13-1: rpm2cpio as a Bourne Shell script
+ </div><div class="para">
+ #!/bin/sh
+ </div><div class="para">
+ </div><div class="para">
+ pkg=$1
+ </div><div class="para">
+ if [ "$pkg" = "" -o ! -e "$pkg" ]; then
+ </div><div class="para">
+ echo "no package supplied" 1>&2
+ </div><div class="para">
+ exit 1
+ </div><div class="para">
+ fi
+ </div><div class="para">
+ </div><div class="para">
+ leadsize=96
+ </div><div class="para">
+ o=`expr $leadsize + 8`
+ </div><div class="para">
+ set `od -j $o -N 8 -t u1 $pkg`
+ </div><div class="para">
+ il=`expr 256 \* \( 256 \* \( 256 \* $2 + $3 \) + $4 \) + $5`
+ </div><div class="para">
+ dl=`expr 256 \* \( 256 \* \( 256 \* $6 + $7 \) + $8 \) + $9`
+ </div><div class="para">
+ # echo "sig il: $il dl: $dl"
+ </div><div class="para">
+ </div><div class="para">
+ sigsize=`expr 8 + 16 \* $il + $dl`
+ </div><div class="para">
+ o=`expr $o + $sigsize + \( 8 - \( $sigsize \% 8 \) \) \% 8 + 8`
+ </div><div class="para">
+ set `od -j $o -N 8 -t u1 $pkg`
+ </div><div class="para">
+ il=`expr 256 \* \( 256 \* \( 256 \* $2 + $3 \) + $4 \) + $5`
+ </div><div class="para">
+ dl=`expr 256 \* \( 256 \* \( 256 \* $6 + $7 \) + $8 \) + $9`
+ </div><div class="para">
+ # echo "hdr il: $il dl: $dl"
+ </div><div class="para">
+ </div><div class="para">
+ hdrsize=`expr 8 + 16 \* $il + $dl`
+ </div><div class="para">
+ o=`expr $o + $hdrsize`
+ </div><div class="para">
+ </div><div class="para">
+ dd if=$pkg ibs=$o skip=1 2>/dev/null | gunzip
+ </div><div class="para">
+ After you have marked this file as executable and placed it in your command path, you can use the script just like the C language implementation of rpm2cpio. This script also takes an RPM package file as input and produces a cpio file on standard output, and so should be used in conjunction with redirection or a pipe:
+ </div><div class="para">
+ $ rpm2cpio.sh fluxbox-0.1.8-2.src.rpm | cpio -i -d
+ </div><div class="para">
+ 656 blocks
+ </div><div class="para">
+ $
+ </div><div class="para">
+ In this case, I piped the output to cpio, directly extracting it. I could have redirected the output of rpm2cpio.sh to a file instead.
+ </div><div class="para">
+ In addition to the Bourne shell implementation of rpm2cpio, a version has been written in Perl by Roger Espel Llima. The Perl rpm2cpio implementation should work on any system that has a reasonably modern Perl interpreter. To use this version of rpm2cpio, the script in Listing 13-2 should be saved to a file named rpm2cpio.pl, marked executable, and copied to a directory in your path.
+ </div><div class="para">
+ Listing 13-2:The Perl version of rpm2cpio, rpm2cpio.pl
+ </div><div class="para">
+ #!/usr/bin/perl
+ </div><div class="para">
+ </div><div class="para">
+ # Copyright (C) 1997,1998,1999, Roger Espel Llima
+ </div><div class="para">
+ #
+ </div><div class="para">
+ # Permission is hereby granted, free of charge, to any person obtaining a copy
+ </div><div class="para">
+ # of this software and any associated documentation files (the "Software"), to
+ </div><div class="para">
+ # deal in the Software without restriction, including without limitation the
+ </div><div class="para">
+ # rights to use, copy, modify, merge, publish, distribute, sublicense,
+ </div><div class="para">
+ # and/or sell copies of the Software, and to permit persons to whom the
+ </div><div class="para">
+ # Software is furnished to do so, subject to the following conditions:
+ </div><div class="para">
+ #
+ </div><div class="para">
+ # The above copyright notice and this permission notice shall be included in
+ </div><div class="para">
+ # all copies or substantial portions of the Software.
+ </div><div class="para">
+ #
+ </div><div class="para">
+ # THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+ </div><div class="para">
+ # IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+ </div><div class="para">
+ # FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+ </div><div class="para">
+ # SOFTWARE'S COPYRIGHT HOLDER(S) BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+ </div><div class="para">
+ # LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+ </div><div class="para">
+ # OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+ </div><div class="para">
+ # THE SOFTWARE
+ </div><div class="para">
+ </div><div class="para">
+ # (whew, that's done!)
+ </div><div class="para">
+ </div><div class="para">
+ # why does the world need another rpm2cpio? because the existing one
+ </div><div class="para">
+ # won't build unless you have half a ton of things that aren't really
+ </div><div class="para">
+ # required for it, since it uses the same library used to extract RPM's.
+ </div><div class="para">
+ # in particular, it won't build on the HPsUX box i'm on.
+ </div><div class="para">
+ </div><div class="para">
+ # sw 2002-Mar-6 Don't slurp the whole file
+ </div><div class="para">
+ </div><div class="para">
+ # add a path if desired
+ </div><div class="para">
+ $gzip = "gzip";
+ </div><div class="para">
+ </div><div class="para">
+ sub printhelp {
+ </div><div class="para">
+ print <<HERE;
+ </div><div class="para">
+ rpm2cpio, perl version by orabidoo <odar\@pobox.com> +sw
+ </div><div class="para">
+ dumps the contents to stdout as a cpio archive
+ </div><div class="para">
+ </div><div class="para">
+ use: rpm2cpio [file.rpm] > file.cpio
+ </div><div class="para">
+ </div><div class="para">
+ Here's how to use cpio:
+ </div><div class="para">
+ list of contents: cpio -t -i < /file/name
+ </div><div class="para">
+ extract files: cpio -d -i < /file/name
+ </div><div class="para">
+ HERE
+ </div><div class="para">
+ </div><div class="para">
+ exit 0;
+ </div><div class="para">
+ }
+ </div><div class="para">
+ </div><div class="para">
+ if ($#ARGV == -1) {
+ </div><div class="para">
+ printhelp if -t STDIN;
+ </div><div class="para">
+ $f = "STDIN";
+ </div><div class="para">
+ } elsif ($#ARGV == 0) {
+ </div><div class="para">
+ open(F, "< $ARGV[0]") or die "Can't read file $ARGV[0]\n";
+ </div><div class="para">
+ $f = 'F';
+ </div><div class="para">
+ } else {
+ </div><div class="para">
+ printhelp;
+ </div><div class="para">
+ }
+ </div><div class="para">
+ </div><div class="para">
+ printhelp if -t STDOUT;
+ </div><div class="para">
+ </div><div class="para">
+ # gobble the file up
+ </div><div class="para">
+ ##undef $/;
+ </div><div class="para">
+ ##$|=1;
+ </div><div class="para">
+ ##$rpm = <$f>;
+ </div><div class="para">
+ ##close ($f);
+ </div><div class="para">
+ </div><div class="para">
+ read $f,$rpm,96;
+ </div><div class="para">
+ </div><div class="para">
+ ($magic, $major, $minor, $crap) = unpack("NCC C90", $rpm);
+ </div><div class="para">
+ </div><div class="para">
+ die "Not an RPM\n" if $magic != 0xedabeedb;
+ </div><div class="para">
+ die "Not a version 3 or 4 RPM\n" if $major != 3 && $major != 4;
+ </div><div class="para">
+ </div><div class="para">
+ ##$rpm = substr($rpm, 96);
+ </div><div class="para">
+ </div><div class="para">
+ while (!eof($f)) {
+ </div><div class="para">
+ $pos = tell($f);
+ </div><div class="para">
+ read $f,$rpm,16;
+ </div><div class="para">
+ $smagic = unpack("n", $rpm);
+ </div><div class="para">
+ last if $smagic eq 0x1f8b;
+ </div><div class="para">
+ # Turns out that every header except the start of the gzip one is
+ </div><div class="para">
+ # padded to an 8 bytes boundary.
+ </div><div class="para">
+ if ($pos & 0x7) {
+ </div><div class="para">
+ $pos += 7;
+ </div><div class="para">
+ $pos &= ~0x7;# Round to 8 byte boundary
+ </div><div class="para">
+ seek $f, $pos, 0;
+ </div><div class="para">
+ read $f,$rpm,16;
+ </div><div class="para">
+ }
+ </div><div class="para">
+ ($magic, $crap, $sections, $bytes) = unpack("N4", $rpm);
+ </div><div class="para">
+ die "Error: header not recognized\n" if $magic != 0x8eade801;
+ </div><div class="para">
+ $pos += 16;# for header
+ </div><div class="para">
+ $pos += 16 * $sections;
+ </div><div class="para">
+ $pos += $bytes;
+ </div><div class="para">
+ seek $f, $pos, 0;
+ </div><div class="para">
+ }
+ </div><div class="para">
+ </div><div class="para">
+ if (eof($f)) {
+ </div><div class="para">
+ die "bogus RPM\n";
+ </div><div class="para">
+ }
+ </div><div class="para">
+ </div><div class="para">
+ open(ZCAT, "|gzip -cd") || die "can't pipe to gzip\n";
+ </div><div class="para">
+ print STDERR "CPIO archive found!\n";
+ </div><div class="para">
+ </div><div class="para">
+ print ZCAT $rpm;
+ </div><div class="para">
+ </div><div class="para">
+ while (read($f, ($_=''), 16384) > 0) {
+ </div><div class="para">
+ print ZCAT;
+ </div><div class="para">
+ }
+ </div><div class="para">
+ </div><div class="para">
+ close ZCAT;
+ </div><div class="para">
+ After set up, rpm2cpio.pl works much like the C and Bourne shell versions, so the following command can be used to generate a cpio archive from an RPM package file:
+ </div><div class="para">
+ $ rpm2cpio.pl fluxbox-0.1.8-2.src.rpm | cpio -i -d
+ </div><div class="para">
+ CPIO archive found!
+ </div><div class="para">
+ 656 blocks
+ </div><div class="para">
+ $
+ </div><div class="para">
+ </div><div class="para">
+ Depending upon the system you are on, one or more of these three rpm2cpio programs should work. All three are useful any time you want to extract a file or files from an RPM package file but do not actually need to install the RPM.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch11s05.html"><strong>Înapoi</strong>11.5. Summary</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch12s02.html"><strong>Înainte</strong>12.2. Summary</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-intro-packaging.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-intro-packaging.html
new file mode 100644
index 0000000..28fe7eb
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-intro-packaging.html
@@ -0,0 +1,44 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Introducing Package Management</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="index.html" title="Ghid RPM" /><link rel="prev" href="index.html" title="Ghid RPM" /><link rel="next" href="pr01s02.html" title="2. Overcoming the Installation Obstacles" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="index.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="pr01s02.html"><strong>ÃŽnainte</strong></a></li></ul><div xml:lang="ro" class=
"preface" id="ch-intro-packaging" lang="ro"><div class="titlepage"><div><div><h1 class="title">Introducing Package Management</h1></div></div></div><div class="para">
+ This chapter covers:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Issues in software management
+ </div></li><li class="listitem"><div class="para">
+ Examining Linux management tools
+ </div></li><li class="listitem"><div class="para">
+ Introducing the package concept
+ </div></li></ul></div><div class="para">
+ In 1991, a young Finnish graduate student started a new personal hobby. He had acquired an Intel 386 computer and had spent a few weeks exploring it and playing early PC computer games. Eventually, however, he grew bored with the limitations of the MS-DOS environment that had come with his toy and decided that he wanted an operating system for it that he could use more productively. After exploring Minix, a feature-limited teaching operating system, he decided he needed a full-featured OS.
+ </div><div class="para">
+ At that time, no full-featured PC operating systems were freely available, so he decided to write his own operating system. Today, that small hobby OS that Linus Torvalds started almost as a whim has become Linux, a significant new variant of Unix that runs millions of the world's network servers and, increasingly, desktop computers and embedded processors.
+ </div><div class="para">
+ Linux has grown up, successfully making the transition from a one-man personal project to a functional, full-featured operating system used by many of the world's major corporations and deployed on millions of corporate and personal systems. Along the way, Linux has had to address many of the same issues any new operating system must face. One of these concerns is how software for Linux, and how the Linux operating system itself, should be installed. How can administrators safely remove software packages without affecting other installed packages? And how can you safely upgrade packages? Answering these questions is what this book is all about.
+ </div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id569409" class="title">Installing, Removing, and Upgrading Applications</h1></div></div></div><div class="para">
+ Applications for most operating systems consist of multiple files that must be copied to specific locations on the computer's file system before each application can be run. This is true for common PC operating systems such as MS-DOS or Microsoft Windows, as well as for Unix and Linux.
+ </div><div class="para">
+ In the case of a Unix-like operating system such as Linux, other issues must also be considered. Unix and Linux are multiple-user systems, so they must track ownership of files. Furthermore, Unix and Linux use a system of file permissions. Administrators can grant some users access to files and can control how users may access those files, for example, allowing some users the permission to read only certain files. Administrators can deny other users access to the same files. So, installation of an application on Linux requires consideration of all these details. After files are copied into their appropriate locations, they must be granted correct permissions and correct ownerships.
+ </div><div class="para">
+ Similarly, administrators occasionally need to remove installed software from the computer. Maybe the program is no longer needed; maybe it does not work correctly for the needed task, or maybe the space it is using is needed for more important programs. In addition, installed software sometimes needs to be upgraded. Perhaps a new version of the software has come out and the currently installed version needs to be replaced with the presumably improved version. In most respects, software upgrades are the same as the removal of one application (the old version), followed by installation of another application (the new version). Upgrades do, however, have additional issues. Many applications must be configured before they can be used. Ideally, the upgrade for an installed application takes the current configuration into account, preserving old configuration information and applying it to the recently installed version.
+ </div><div class="para">
+ All these considerations make installation of a new application onto Unix or Linux a labor-intensive process. To further complicate matters, Unix applications have primarily been distributed as source code. To install a new application, such as the Apache Web server, you download the source code for that application—in this case, from the Apache Project's Web page (<a href="http://httpd.apache.org">http://httpd.apache.org</a>). Typically, the source code is provided in some sort of archive (such as the Zip archival and compression format often used in the Windows world or the tar archive format typically used in the Unix world) that you must then unpack. After unpacking this source code, you have to configure it to support the options and systems you want, compiling it to produce an executable program that can run on your particular operating system (CPU combination).
+ </div><div class="para">
+ After compiling the source code, you still have to install the application by putting all of its components (executable programs, documentation, configuration files, and so forth) into the correct locations on your hard drive and setting correct permissions on all those files. You might also need to perform other steps to prepare the system for the software. In the case of Apache, for example, some space needs to be set aside for storage of Web-access logs, and a special user account needs to be created so that the Apache Web server can operate more securely. Finally, you are ready to try running the application you have spent so much time installing.
+ </div><div class="para">
+ To help with all these tasks, precompiled software is becoming increasingly prevalent in the Unix and Linux communities, so you might be able to find executable (precompiled binary) copies of the application you wish to install that are appropriate for your particular machine's CPU. In that case, download an archive of the compiled application and unpack it. Then skip the compilation step, since that has already been done for you. The other steps required to install the package (copying files into correct locations, setting file permissions, and doing any needed system or application configuration) are exactly the same as the steps performed to install that application from source code. Once those steps are finished, you are ready to test your freshly installed application.
+ </div><div class="para">
+ When you run your newly installed application, you might be thrilled, perhaps discovering that it is something you want to use regularly. On the other hand, you might discover that you have no use for the software you have just installed, deciding that you want to uninstall it.
+ </div><div class="para">
+ Uninstallation occurs by reversing the installation steps. Remember any special steps you have performed (such as adding a user account), and undo those. Then remember all the files you have installed and where you have installed them. Manually delete them. As you can see, this can become a pretty tedious exercise.
+ </div><div class="para">
+ If you like the application you have installed, you will likely find yourself wanting to upgrade it eventually. The Apache Web server, for example, like any network service, must be upgraded whenever security problems are found and fixed. If you find that you need to upgrade Apache, you need to back up your Apache configuration files and then uninstall Apache. The next step is to install a new version of Apache, applying your Apache-configuration customizations to your new installation of Apache.
+ </div><div class="para">
+ All of this is a big pain. There has to be a better way. And there is.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="index.html"><strong>Înapoi</strong>Ghid RPM</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="pr01s02.html"><strong>Înainte</strong>2. Overcoming the Installation Obstacles</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-intro-rpm.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-intro-rpm.html
new file mode 100644
index 0000000..fc29523
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-intro-rpm.html
@@ -0,0 +1,48 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Cap. 1. Introduction to RPM</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="index.html" title="Ghid RPM" /><link rel="prev" href="pr01s04.html" title="4. Summary" /><link rel="next" href="ch01s02.html" title="1.2. RPM Design Goals" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="pr01s04.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch01s02.html"><strong>ÃŽnainte</strong></a></li></ul><div xml:lang="ro" class="chapter" id=
"ch-intro-rpm" lang="ro"><div class="titlepage"><div><div><h2 class="title">Cap. 1. Introduction to RPM</h2></div></div></div><div class="toc"><dl><dt><span class="sect1"><a href="ch-intro-rpm.html#id897385">1.1. The Need for Linux Package Management Systems</a></span></dt><dt><span class="sect1"><a href="ch01s02.html">1.2. RPM Design Goals</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch01s02.html#id620200">1.2.1. Ease of use</a></span></dt><dt><span class="sect2"><a href="ch01s02s02.html">1.2.2. Package-oriented focus</a></span></dt><dt><span class="sect2"><a href="ch01s02s03.html">1.2.3. Package upgradability</a></span></dt><dt><span class="sect2"><a href="ch01s02s04.html">1.2.4. Package interdependencies</a></span></dt><dt><span class="sect2"><a href="ch01s02s05.html">1.2.5. Query capabilities</a></span></dt><dt><span class="sect2"><a href="ch01s02s06.html">1.2.6. Package verification</a></span></dt><dt><span class="sect2"><a href="ch01s02s07.html">1.2.7. Multi
ple architectures</a></span></dt><dt><span class="sect2"><a href="ch01s02s08.html">1.2.8. Pristine sources</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch01s03.html">1.3. RPM Terminology</a></span></dt><dt><span class="sect1"><a href="ch01s04.html">1.4. Summary</a></span></dt></dl></div><div class="para">
+ This chapter covers:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Examining the history of package management
+ </div></li><li class="listitem"><div class="para">
+ Introducing RPM features
+ </div></li><li class="listitem"><div class="para">
+ Getting acquainted with RPM terminology
+ </div></li></ul></div><div class="para">
+ Several package managers are available for Linux to track and manipulate the applications installed on the system. The most widely used of these Linux package managers is the RPM Package Manager (formerly the Red Hat Package Manager), or RPM for short, the subject of this book
+ </div><div class="para">
+ Although RPM was initially developed for Red Hat Linux, a combination of technical features and good timing has resulted in RPM’s becoming the de facto standard for packaging software on most Linux distributions. The fact that Red Hat released the source code to the RPM software under an open-source license also helped its adoption.
+ </div><div class="para">
+ More recently, the RPM package file format has been adopted as the official standard for Linux as part of the Linux Standards Base, or LSB. Described at <a href="http://www.linuxbase.org/">http://www.linuxbase.org/</a>, the Linux Standards Base is an attempt to set a baseline that all Linux distributions should follow. The LSB has helped system administrators by providing some commonality across distributions, as in the location of certain files. The history of Linux package managers is largely intertwined with the history of Linux distributions.
+ </div><div class="para">
+ Strictly speaking, Linux refers to a single piece of software, the Unix-like kernel that Linus Torvalds and cohorts have scattered all over the Internet and have been developing since 1991. This Linux kernel is a marvelous piece of software, currently comprising over 3.7 million lines of freely-licensed source code and accompanying documentation. Together, these factors provide a fast, full-featured, stable operating system kernel for use on more than 30 different processor architectures, ranging from embedded systems such as watches and PDAs, to desktop and server systems, all the way up to mainframes and supercomputing clusters.
+ </div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id897385" class="title">The Need for Linux Package Management Systems</h1></div></div></div><div class="para">
+ Although Linux is an excellent core component of an operating system suitable for a wide variety of real-world applications, this Linux kernel by itself is not sufficient for accomplishing most tasks. The technical definition of exactly what constitutes an operating system is a matter of debate.
+ </div><div class="para">
+ Despite this controversy, it is clear that most users of Linux require both the Linux kernel and a large suite of accompanying software (a shared C library; traditional Unix utilities such as <code class="command">grep</code>, <code class="command">awk</code>, and <code class="command">sed</code>; an editor, such as <code class="command">vi</code>; a shell, such as the Bourne-Again <code class="command">bash</code> shell; and so forth) to complete the various tasks for which they typically employ Linux.
+ </div><div class="para">
+ Users expect Linux to include server software such as the Apache Web server, desktop software such as the OpenOffice.org office productivity suite, and a host of other packages. In fact, most Linux users don’t make the distinction between the kernel (technically the only part that is Linux) and all the extra packages (technically “everything elseâ€) that comes with a Linux distribution. Most users simply refer to the whole thing as “Linux.â€
+ </div><div class="para">
+ Some Linux distributions include thousands of packages on six or more CD-ROMs. This situation alone cries out for effective package-management software. And this doesn’t include the extra packages that don’t come with Linux distributions but which organizations need to create an effective working environment.
+ </div><div class="para">
+ Furthermore, the Linux kernel and these various software applications are typically made available by their developers in source code formats only, and they can be installed manually only after compiling them from source code.
+ </div><div class="para">
+ Most people do not have the technical skills necessary to cross-compile an entire operating system. Even if they do, they usually do not want to devote the time and effort required to bootstrap and compile an operating system just to be able to run Linux.
+ </div><div class="para">
+ Fortunately, the early Linux programmers quickly realized the impracticality of source-code only releases early in Linux's development and created what they called distributions—collections of precompiled binaries of the Linux kernel and other necessary software that users often wanted. Rather than installing Minix, compiling the Linux kernel and other required software applications under Minix, and installing those compiled binaries of the Linux kernel and essential Linux applications, users could just install these distributions, immediately having a functional Linux environment in which to work.
+ </div><div class="para">
+ Early distributions, such as MCC and SLS, initially represented little more than archived snapshots of their developer's hard drive. They offered the user performing the installation little or no control over what applications were put on the system. Whatever the distribution developer had on his hard drive was what the distribution installer got on her hard drive. Even this was much better than rolling your own distribution by hand. SLS, for example, stood for Soft Landing System, and was designed to make the experience of installing Linux easier, hence providing a “soft landing.†MCC Interim Linux, from the Manchester Computing Centre, was the first distribution to sport a combined boot/root disk, another attempt to make life easier for those adopting Linux.
+ </div><div class="para">
+ Distribution developers quickly realized, however, that more flexibility was needed and began looking for ways to provide choices both during and after installation. The Slackware distribution, for example, divided applications into several functional categories. All users installed the base distribution; users could then selectively install only the additional supplemental categories they needed. If networking support was desired, for example, the networking bundle could be installed. Similarly, if a graphical user interface was desired, the X bundle could be installed, making the X Window System available. This concept offered rudimentary control over what was installed but only at a very coarse level. Installing the X bundle put several applications (multiple X terminal emulators, several different window managers, and so forth) on the system, and all users who installed the bundle got all of those applications whether they wanted them all or not.
+ </div><div class="para">
+ The next logical step in distribution evolution was the development of more advanced tools to control what was installed. Several distributions independently developed the notion of application-level installation management. The developers of these distributions realized that Slackware and similar distributions were heading in the right direction, but simply had not made software management granular enough. Slackware allowed installation and uninstallation (after a fashion) of bundles of related applications, but what was really needed was installation and uninstallation on an application-by-application basis.
+ </div><div class="para">
+ In late 1993, Rik Faith, Doug Hoffman, and Kevin Martin began releasing the first public betas of the BOGUS Linux distribution. BOGUS was notable for the package management system (<code class="command">pms</code>) software that was used with it for installation and uninstallation of all software on an application-by-application basis. Shortly thereafter, in the summer of 1994, the first public betas of Red Hat Commercial Linux were released. Red Hat initially used Red Hat Software Program Packages (RPP) as the basis of its Linux distribution. Like <code class="command">pms</code>, RPP was a system-management tool that allowed for easy installation and uninstallation of applications. In late 1993, Ian Murdock founded the Debian Gnu/Linux distribution. He began seriously developing its <code class="command">dpkg</code> application-management software by the summer of 1994. Like <code class="command">pms</code> and RPP, <code class="command">dpkg</code> made it possible to m
anage each application on the system.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="pr01s04.html"><strong>Înapoi</strong>4. Summary</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch01s02.html"><strong>Înainte</strong>1.2. RPM Design Goals</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-licensing.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-licensing.html
new file mode 100644
index 0000000..a86363c
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-licensing.html
@@ -0,0 +1,155 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Cap. 27. Licensing RPM</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="index.html" title="Ghid RPM" /><link rel="prev" href="ch26s04.html" title="26.4. Integrated Development Environments for Python Programming" /><link rel="next" href="appe-Publican-Revision_History.html" title="Anexa A. Istoria reviziilor" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch26s04.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="appe-Pub
lican-Revision_History.html"><strong>ÃŽnainte</strong></a></li></ul><div xml:lang="ro" class="chapter" id="ch-licensing" lang="ro"><div class="titlepage"><div><div><h2 class="title">Cap. 27. Licensing RPM</h2></div></div></div><div class="toc"><dl><dt><span class="sect1"><a href="ch-licensing.html#id573888">27.1. The GNU General Public License</a></span></dt></dl></div><div class="para">
+ When incorporating someone else's existing code into your software project, you should always examine the license of the code carefully, make sure you understand its implications, and make sure you are willing to abide by them. You also need to make sure you have the legal right to incorporate the other code in your project. This is true for commercial code and commercial projects, and it is equally true for freely licensed code and free software projects.
+ </div><div class="para">
+ RPM itself and most discussed helper applications (rpmlint, rpm-spec-mode, and so forth) are free software, meaning that the programs themselves are available without cost. In addition, most of these tools are considered open source software, which means the source code for the applications are also available.
+ </div><div class="para">
+ These facts do not mean that they are unlicensed software, or that their source code can be used in any desired fashion. RPM and these helper applications are made freely available in both source and binary formats under the terms of the GNU Project's General Public License (GPL). Parts of RPM are licensed under the LGPL, the Lesser General Public License. The terms of the GPL are reproduced here, and should be consulted before incorporating any source code or binaries licensed under the GPL into your projects. Essentially, the GPL states that you can use GPL'ed source code or binaries for any purpose, so long as you always give those same rights (including access to your program’s source code) to any users to whom you give software derived from GPL'ed source code (though a lawyer should be consulted to obtain an analysis of the implications of the GPL on your project, should you decide to use GPL'ed code in any commercially licensed project you might undertake).
+ </div><div class="para">
+ </div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id573888" class="title">The GNU General Public License</h1></div></div></div><div class="para">
+ Version 2, June 1991
+ </div><div class="para">
+ </div><div class="para">
+ Copyright (C) 1989, 1991 Free Software Foundation, Inc.
+ </div><div class="para">
+ 675 Mass Ave, Cambridge, MA 02139, USA
+ </div><div class="para">
+ Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.
+ </div><div class="para">
+ </div><div class="para">
+ Preamble
+ </div><div class="para">
+ The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users. This General Public License applies to most of the Free Software Foundation's software and to any other program whose authors commit to using it. (Some other Free Software Foundation software is covered by the GNU Library General Public License instead.) You can apply it to your programs, too.
+ </div><div class="para">
+ </div><div class="para">
+ When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs; and that you know you can do these things.
+ </div><div class="para">
+ </div><div class="para">
+ To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to surrender the rights. These restrictions translate to certain responsibilities for you if you distribute copies of the software, or if you modify it.
+ </div><div class="para">
+ </div><div class="para">
+ For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the rights that you have. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights.
+ </div><div class="para">
+ </div><div class="para">
+ We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which gives you legal permission to copy, distribute and/or modify the software.
+ </div><div class="para">
+ </div><div class="para">
+ Also, for each author's protection and ours, we want to make certain that everyone understands that there is no warranty for this free software. If the software is modified by someone else and passed on, we want its recipients to know that what they have is not the original, so that any problems introduced by others will not reflect on the original authors' reputations.
+ </div><div class="para">
+ </div><div class="para">
+ Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that redistributors of a free program will individually obtain patent licenses, in effect making the program proprietary. To prevent this, we have made it clear that any patent must be licensed for everyone's free use or not licensed at all.
+ </div><div class="para">
+ </div><div class="para">
+ The precise terms and conditions for copying, distribution and modification follow.
+ </div><div class="para">
+ </div><div class="para">
+ TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+ </div><div class="para">
+ 0.This License applies to any program or other work which contains a notice placed by the copyright holder saying it may be distributed under the terms of this General Public License. The "Program", below, refers to any such program or work, and a "work based on the Program" means either the Program or any derivative work under copyright law: that is to say, a work containing the Program or a portion of it, either verbatim or with modifications and/or translated into another language. (Hereinafter, translation is included without limitation in the term "modification".) Each licensee is addressed as "you".
+ </div><div class="para">
+ Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program). Whether that is true depends on what the Program does.
+ </div><div class="para">
+ 1.You may copy and distribute verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and give any other recipients of the Program a copy of this License along with the Program.
+ </div><div class="para">
+ You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee.
+ </div><div class="para">
+ 2.You may modify your copy or copies of the Program or any portion of it, thus forming a work based on the Program, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions:
+ </div><div class="para">
+ a)You must cause the modified files to carry prominent notice stating that you changed the files and the date of any change.
+ </div><div class="para">
+ b)You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License.
+ </div><div class="para">
+ c)If the modified program normally reads commands interactively when run, you must cause it, when started running for such interactive use in the most ordinary way, to print or display an announcement including an appropriate copyright notice and a notice that there is no warranty (or else, saying that you provide a warranty) and that users may redistribute the program under these conditions, and telling the user how to view a copy of this License. (Exception: if the Program itself is interactive but does not normally print such an announcement, your work based on the Program is not required to print an announcement.)
+ </div><div class="para">
+ These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Program, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it.
+ </div><div class="para">
+ Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Program.
+ </div><div class="para">
+ In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on the Program) on a volume of a storage or distribution medium does not bring the other work under the scope of this License.
+ </div><div class="para">
+ 3.You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following:
+ </div><div class="para">
+ a)Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,
+ </div><div class="para">
+ b)Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,
+ </div><div class="para">
+ c)Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for noncommercial distribution and only if you received the program in object code or executable form with such an offer, in accord with Subsection b above.)
+ </div><div class="para">
+ The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable. However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable.
+ </div><div class="para">
+ If distribution of executable or object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place counts as distribution of the source code, even though third parties are not compelled to copy the source along with the object code.
+ </div><div class="para">
+ 4.You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense or distribute the Program is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance.
+ </div><div class="para">
+ 5.You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Program (or any work based on the Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Program or works based on it.
+ </div><div class="para">
+ 6.Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties to this License.
+ </div><div class="para">
+ 7.If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Program at all. For example, if a patent license would not permit royalty-free redistribution of the Program by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Program.
+ </div><div class="para">
+ If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply and the section as a whole is intended to apply in other circumstances.
+ </div><div class="para">
+ It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system, which is implemented by public license practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice.
+ </div><div class="para">
+ This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License.
+ </div><div class="para">
+ 8.If the distribution and/or use of the Program is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Program under this License may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this License.
+ </div><div class="para">
+ 9.The Free Software Foundation may publish revised and/or new versions of the General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.
+ </div><div class="para">
+ Each version is given a distinguishing version number. If the Program specifies a version number of this License which applies to it and "any later version", you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation.
+ </div><div class="para">
+ 10.If you wish to incorporate parts of the Program into other free programs whose distribution conditions are different, write to the author to ask for permission. For software which is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally.
+ </div><div class="para">
+ NO WARRANTY
+ </div><div class="para">
+ 11.BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+ </div><div class="para">
+ 12.IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
+ </div><div class="para">
+ END OF TERMS AND CONDITIONS
+ </div><div class="para">
+ </div><div class="para">
+ Appendix: How to Apply These Terms to Your New Programs
+ </div><div class="para">
+ </div><div class="para">
+ If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms.
+ </div><div class="para">
+ </div><div class="para">
+ To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively convey the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found.
+ </div><div class="para">
+ <one line to give the program's name and a brief idea of what it does.> Copyright (C) 19yy <name of author>
+ </div><div class="para">
+ This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.
+ </div><div class="para">
+ This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
+ </div><div class="para">
+ You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
+ </div><div class="para">
+ Also add information on how to contact you by electronic and paper mail.
+ </div><div class="para">
+ </div><div class="para">
+ If the program is interactive, make it output a short notice like this when it starts in an interactive mode:
+ </div><div class="para">
+ Gnomovision version 69, Copyright (C) 19yy name of author Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'. This is free software, and you are welcome to redistribute it under certain conditions; type `show c' for details.
+ </div><div class="para">
+ </div><div class="para">
+ The hypothetical commands `show w' and `show c' should show the appropriate parts of the General Public License. Of course, the commands you use may be called something other than `show w' and `show c'; they could even be mouse-clicks or menu items--whatever suits your program.
+ </div><div class="para">
+ </div><div class="para">
+ You should also get your employer (if you work as a programmer) or your school, if any, to sign a "copyright disclaimer" for the program, if necessary. Here is a sample; alter the names:
+ </div><div class="para">
+ Yoyodyne, Inc., hereby disclaims all copyright interest in the program `Gnomovision' (which makes passes at compilers) written by James Hacker.
+ </div><div class="para">
+ <signature of Ty Coon>, 1 April 1989Ty Coon, President of Vice
+ </div><div class="para">
+ This General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Library General Public License instead of this License.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch26s04.html"><strong>Înapoi</strong>26.4. Integrated Development Environments for Pyt...</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="appe-Publican-Revision_History.html"><strong>Înainte</strong>Anexa A. Istoria reviziilor</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-management-software.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-management-software.html
new file mode 100644
index 0000000..5ea8be7
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-management-software.html
@@ -0,0 +1,346 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Cap. 7. RPM Management Software</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="index.html" title="Ghid RPM" /><link rel="prev" href="ch06s04.html" title="6.4. Summary" /><link rel="next" href="ch07s02.html" title="7.2. Graphical RPM Management" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch06s04.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch07s02.html"><strong>ÃŽnainte</strong></a></li></ul><div xml:lang="ro" class="ch
apter" id="ch-management-software" lang="ro"><div class="titlepage"><div><div><h2 class="title">Cap. 7. RPM Management Software</h2></div></div></div><div class="toc"><dl><dt><span class="sect1"><a href="ch-management-software.html#id650152">7.1. Locating RPMs</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch-management-software.html#id801673">7.1.1. rpmfind and rpm2html</a></span></dt><dt><span class="sect2"><a href="ch-management-software.html#id703003">7.1.2. RPM Sites On the Internet</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch07s02.html">7.2. Graphical RPM Management</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch07s02.html#id759907">7.2.1. Nautilus</a></span></dt><dt><span class="sect2"><a href="ch07s02s02.html">7.2.2. Red Hat Package Management</a></span></dt><dt><span class="sect2"><a href="ch07s02s03.html">7.2.3. KPackage</a></span></dt><dt><span class="sect2"><a href="ch07s02s04.html">7.2.4. Gnome-RPM</a></span></dt></dl></dd><dt
><span class="sect1"><a href="ch07s03.html">7.3. Extending RPM Management</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch07s03.html#id567232">7.3.1. AutoRPM</a></span></dt><dt><span class="sect2"><a href="ch07s03s02.html">7.3.2. AutoUpdate</a></span></dt><dt><span class="sect2"><a href="ch07s03s03.html">7.3.3. The Red Hat Network and up2date</a></span></dt><dt><span class="sect2"><a href="ch07s03s04.html">7.3.4. Current</a></span></dt><dt><span class="sect2"><a href="ch07s03s05.html">7.3.5. urpmi and RpmDrake</a></span></dt><dt><span class="sect2"><a href="ch07s03s06.html">7.3.6. apt-rpm</a></span></dt><dt><span class="sect2"><a href="ch07s03s07.html">7.3.7. The poldek</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch07s04.html">7.4. Summary</a></span></dt></dl></div><div class="para">
+ This chapter covers:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Finding packages in RPM format
+ </div></li><li class="listitem"><div class="para">
+ Graphical tools to manage RPM packages
+ </div></li><li class="listitem"><div class="para">
+ Extending RPM management with additional tools
+ </div></li></ul></div><div class="para">
+ You can find a variety of software packages to ease the work of managing RPM-based systems. These utilities can help you find a specific software application packaged using RPM or search through a collection of RPM-packaged software to locate applications with specific features. Similarly, several utilities provide features to ease long-term system-management tasks. These applications provide features such as automatic updating of existing installed software with more recent versions or simplification of software installation by automating installation of any required software dependencies.
+ </div><div class="para">
+ This chapter covers a number of tools for finding packages in RPM format, as well as tools to help manage the RPMs on your system.
+ </div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id650152" class="title">Locating RPMs</h1></div></div></div><div class="para">
+ RPM provides a powerful tool for managing software installed on a system. With a single command, an entire application can be installed on the system in a ready-to-run configuration. With a different command, the entire application can be removed without having manually to track down all of the associated files scattered throughout the hard drive. For RPM to work, however, the software being managed must be packaged in the proper RPM format. RPM packages can be easily prepared if necessary, but you can save time by using the wide variety of software already available in the RPM format. The only trick to using this RPM-packaged software is finding it.
+ </div><div class="para">
+ As you start to search for RPM packages on the Internet, you’ll find thousands of packages available. Many of these packages are built specifically for various Linux distributions, such as Conectiva, SUSE, Red Hat, or Mandrake. In many cases, the Linux distribution won’t matter, but in general it's best to download packages built for your version of Linux, such as Red Hat.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ Although the examples in this book assume Red Hat Linux as a base, just about everything applies to all versions of Linux that use the RPM system, unless noted otherwise.
+ </div><div class="para">
+ Internet search engines are popular, but they aren’t very helpful for finding RPM packages, especially because lots of Web pages have the term rpm (including those covering revolutions per minute). A more efficient approach is to use one of the RPM-specific Internet search tools such as rpmfind.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id801673" class="title">rpmfind and rpm2html</h1></div></div></div><div class="para">
+ One popular free tool for locating RPMs is rpmfind, written by Daniel Veillard. This tool provides a command-line utility that can search for packages by name or description, displaying or optionally downloading any matching packages it finds. It can even provide a list of the dependencies that those matching packages require to run and can download those required dependencies as well.
+ </div><div class="para">
+ When searching for packages, rpmfind can search both the software already installed on the local system and remote databases, including the databases located at http://rpmfind.net/.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ The databases at http://rpmfind.net/ are, in turn, created by another utility: rpm2html. Both are covered in the sections following.
+ </div><div class="para">
+ Commonly, rpmfind is used to search for packages by name, though it can be used to search package descriptions for key words. For example, I might want to find new e-mail clients to install on my system. I happen to know that one popular Linux e-mail client is Ximian’s evolution, so I search for that.
+ </div><div class="para">
+ The basic syntax for rpmfind follows:
+ </div><div class="para">
+ rpmfind package_name
+ </div><div class="para">
+ For example, to search for evolution, use a command like the following:
+ </div><div class="para">
+ $ rpmfind evolution
+ </div><div class="para">
+ Resource evolution already installed
+ </div><div class="para">
+ $
+ </div><div class="para">
+ Before accessing the Internet, rpmfind searches my local system and finds that I already have evolution installed, so it does not even bother searching for copies to download. It looks like I’m forgetful, not remembering that I already have evolution installed. At this point, I might realize that I already have the software I need, or I might decide to search for a similar application, such as exmh, another popular Unix e-mail client.
+ </div><div class="para">
+ To search for exmh (which in this example has not been installed), use a command like the following:
+ </div><div class="para">
+ $ rpmfind exmh
+ </div><div class="para">
+ Installing exmh will require 7301 KBytes
+ </div><div class="para">
+ </div><div class="para">
+ ### To Transfer:
+ </div><div class="para">
+ ftp://ftp.redhat.com/pub/redhat/linux/7.2/en/os/i386/RedHat/RPMS//nmh-1.0.4-9.i3
+ </div><div class="para">
+ 86.rpm
+ </div><div class="para">
+ ftp://ftp.redhat.com/pub/redhat/linux/7.2/en/os/i386/RedHat/RPMS//exmh-2.4-2.noarch.rpm
+ </div><div class="para">
+ Do you want to download these files to /tmp [Y/n/a/i] ? : a
+ </div><div class="para">
+ transferring
+ </div><div class="para">
+ ftp://ftp.redhat.com/pub/redhat/linux/7.2/en/os/i386/RedHat/RPMS//nmh-1.0.4-9.i386.rpm
+ </div><div class="para">
+ saving to /tmp/nmh-1.0.4-9.i386.rpm
+ </div><div class="para">
+ transferring
+ </div><div class="para">
+ ftp://ftp.redhat.com/pub/redhat/linux/7.2/en/os/i386/RedHat/RPMS//exmh-2.4-2.noarch.rpm
+ </div><div class="para">
+ saving to /tmp/exmh-2.4-2.noarch.rpm
+ </div><div class="para">
+ rpm -U /tmp/nmh-1.0.4-9.i386.rpm /tmp/exmh-2.4-2.noarch.rpm
+ </div><div class="para">
+ $
+ </div><div class="para">
+ Here, rpmfind searches my local system for exmh. Since exmh is not installed there, rpmfind searches the databases at http://rpmfind.net/ and does two things: it finds exmh, and it learns that exmh depends upon another package: nmh. After double-checking and learning that nmh is not installed on my local system, rpmfind gives me a choice regarding whether I should download both of those packages; rpmfind gives me four possible answers:
+ </div><div class="para">
+ Do you want to download these files to /tmp [Y/n/a/i] ? : a
+ </div><div class="para">
+ My possible answers were:
+ </div><div class="para">
+ YYes, do download the files.
+ </div><div class="para">
+ NNo, do not download the files.
+ </div><div class="para">
+ AGet all. By default, run in Automatic mode, trying to upgrade packages after they are downloaded
+ </div><div class="para">
+ IInstall packages after download.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ Any user can download packages, but usually only the root user can install packages. Unless you are logged in as root, rpmfind will likely fail to install the downloaded RPMs.
+ </div><div class="para">
+ Because I select the "a" answer, rpmfind downloads all necessary packages to /tmp and tries to upgrade the packages automatically by running the following command:
+ </div><div class="para">
+ rpm -U /tmp/nmh-1.0.4-9.i386.rpm /tmp/exmh-2.4-2.noarch.rpm
+ </div><div class="para">
+ In this case, the rpm -U command silently fails, since I am not running it as root and do not have permission to install software.
+ </div><div class="para">
+ If the name of a package is unknown, rpmfind also supports searching by keywords. The --apropos pattern option tells rpmfind to search through all package descriptions in the databases for the pattern. If I do not know the names of any e-mail clients, I might use this code for my search:
+ </div><div class="para">
+ $ rpmfind --apropos "mail client"
+ </div><div class="para">
+ Searching the RPM catalog for mail client ...
+ </div><div class="para">
+ 1:
+ </div><div class="para">
+ ftp://ftp.redhat.com/pub/redhat/linux/7.2/en/os/i386/RedHat/RPMS//netscape-communicator-4.78-2.i386.rpm
+ </div><div class="para">
+ netscape-communicator : A Web browser, news reader and e-mail client.
+ </div><div class="para">
+ 2:
+ </div><div class="para">
+ ftp://ftp.redhat.com/pub/redhat/linux/7.2/en/os/i386/RedHat/RPMS//sylpheed-0.5.0-3.i386.rpm
+ </div><div class="para">
+ sylpheed : A GTK+ based, lightweight, and fast email client.
+ </div><div class="para">
+ <snip>
+ </div><div class="para">
+ 364: ftp://ftp.pld.org.pl/PLD-1.0/dists/ra/PLD/SRPMS/SRPMS/sylpheed-0.7.4-1.src.rpm
+ </div><div class="para">
+ sylpheed : GTK+ based fast e-mail client
+ </div><div class="para">
+ From my search, rpmfind returns the following output (with most of the entries edited out for space):
+ </div><div class="para">
+ Found 364 packages related to mail client
+ </div><div class="para">
+ $
+ </div><div class="para">
+ With this command, rpmfind connects to the databases at http://rpmfind.net/ and returns the location of all packages whose description contains the text “mail clientâ€. Notice that 364 packages are found; there are lots of e-mail clients available for Linux! That number, however, is slightly misleading. Some of the packages found are prepared for the distribution I am running (Red Hat Linux version 7.2), but others are not. Result #364, for example, appears to be the Polish(ed) Linux Distribution 1.0 package of sylpheed, the same software offered to me packaged for my Red Hat Linux version 7.2 system in Result #2.
+ </div><div class="para">
+ Warning
+ </div><div class="para">
+ Use caution when working with rpmfind. By default, it connects to the databases on the server http://rpmfind.net/ and queries them. These databases are indexes of all RPM-based distributions, and of all versions of each RPM-based distribution, and of all architectures, and of both source and binary RPMs for all these distributions!
+ </div><div class="para">
+ To help you avoid being overwhelmed with results (such as the 364 results I obtain when I search for “mail clientâ€), options are available to fine-tune rpmfind’s searches in various ways. Common options are presented in Table 8-1.
+ </div><div class="para">
+ Table 8-1SEARCH OPTIONS FOR rpmfind
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Option
+ </div>
+
+ </td><td>
+ <div class="para">
+ Result
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -v
+ </div>
+
+ </td><td>
+ <div class="para">
+ increases verbosity of output (can be used multiple times)
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -s server
+ </div>
+
+ </td><td>
+ <div class="para">
+ connects to a specific rpmfind database server
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --sources package
+ </div>
+
+ </td><td>
+ <div class="para">
+ looks for source RPMs of the package
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --apropos key word(s)
+ </div>
+
+ </td><td>
+ <div class="para">
+ looks by keyword instead of package name
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --dist dist
+ </div>
+
+ </td><td>
+ <div class="para">
+ restricts packages to a specific distribution
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --latest package
+ </div>
+
+ </td><td>
+ <div class="para">
+ finds the most current version of package available
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --upgrade package
+ </div>
+
+ </td><td>
+ <div class="para">
+ finds the most current dependencies available for package
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ The rpmfind databases that rpmfind searches are created using the utility rpm2html. If you desire, rpm2html can be used to set up a local mirror of the databases at rpmfind.net or to make a custom database of locally available RPMs for in-house use.
+ </div><div class="para">
+ rpm2html
+ </div><div class="para">
+ The rpm2html utility generates HTML Web pages that describe RPM packages. Very simple in concept, rpm2html has proven very useful over the years.
+ </div><div class="para">
+ With rpm2html, each package is displayed as a single HTML page that describes the package using information much like that returned by the rpm -qi command, covered in <a class="xref" href="ch-using-rpm.html">Cap. 3, <em>Using RPM</em></a> . The HTML page also lists the capabilities the package requires and those it provides. This shows the needed dependency information. Finally, the page includes a download link to download the RPM file.
+ </div><div class="para">
+ All packages of the same name, such as the exmh e-mail client, are collected on summary pages. The summary page tries to list all RPMs for all Linux distributions that provide the given package. For exmh, for example, the database as of this writing includes 71 versions of the exmh package, for Conectiva Linux, Mandrake Linux, Yellow Dog PowerPC Linux, and so on. The summary page also links to the URL in the RPMs that is listed as the home page for the application.
+ </div><div class="para">
+ Used together with its database, rpm2html provides a powerful RPM-centric search engine. You can find more on rpm2html at rpmfind.net/linux/rpm2html/ or just access an RPM search site such as rpmfind.net.
+ </div><div class="para">
+ In addition to rpm2html, the program pdbv creates a set of cross-linked HTML files that list the packages on your system. Pdbv doesn’t support searching and wasn’t built as a front end for search sites, so it is simpler than rpm2html. Instead, pdbv just creates a set of HTML pages that list data that you can query with the rpm command, including the package descriptions, the capabilities required and provided, as well as all the files in the package.
+ </div><div class="para">
+ The primary advantage of pdbv is that it runs relatively quickly to provide you a snapshot of your system.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id703003" class="title">RPM Sites On the Internet</h1></div></div></div><div class="para">
+ In addition to the command-line RPM search tools, a number of Web sites provide handy front ends to databases of available packages. These Web sites make it easy to query for packages and also provide snapshots of what is happening in Linux development, especially with the sites that list recently created RPMs.
+ </div><div class="para">
+ The following sections list some of the more popular sites.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ As with anything on the Internet, sites come and go. I’ve used rpmfind.net for years, but it is always possible that any of these sites may suddenly disappear.
+ </div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id703029" class="title">rpmfind.net</h1></div></div></div><div class="para">
+ The rpmfind utility is associated with an online database available at www.rpmfind.net. You can search this site and see the results in the same format as that created by the rpm2html utility. In essence, this site acts as an HTML front end to the rpmfind query commands. By providing a search engine accessible from a Web browser, instead of the command line as used by the rpmfind utility, the rpmfind.net site is easy to search and also displays the data in an easier-to-read format.
+ </div><div class="para">
+ Use the rpmfind command when you know you want to install something. Use the rpmfind.net Web site when you want to browse through the lists of available RPMs.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ You can download the rpmfind command RPM from the rpmfind.net site.
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id703058" class="title">freshrpms.net</h1></div></div></div><div class="para">
+ The site name,freshrpms.net, is a play on the popular but oddly named Linux site freshmeat.net. The freshmeat.net site provides listings of newly-updated applications for Linux and other operating systems. The freshrpms.net site provides a similar service devoted to freshly-made RPMs.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ You don’t always want the most recently made RPMs. Sometimes it's good to wait a while and see if others have faced problems with a given RPM before downloading it.
+ </div><div class="para">
+ One of the best features of the freshrpms.net site is that it also provides links to the RPM spec files for the packages it references. This is a very useful source of examples when you try to build RPMs.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ See <a class="xref" href="ch-specfiles.html">Cap. 9, <em>Working with Spec Files</em></a> for more on RPM spec files.
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id570405" class="title">RPM PBone Search</h1></div></div></div><div class="para">
+ The site http://rpm.pbone.net/ provides a database of RPM packages you can search. This site also lists quite a few recently created RPMs. In fact, much of the focus here lies in finding the latest updates to the applications you run.
+ </div><div class="para">
+ The feature I like most about the PBone search is the ability to specify which Linux distributions to search by using a set of check boxes. Although in theory most Linux RPMs should work on most Linux distributions, I prefer to get something made for and tested on my version of Linux.
+ </div><div class="para">
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id570430" class="title">Other Sites</h1></div></div></div><div class="para">
+ Table 8-2 lists additional sites where you can find RPMs. As with all listings of Internet sites, these may come and go.
+ </div><div class="para">
+ Table 8-2MORE RPM SITES
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Site
+ </div>
+
+ </td><td>
+ <div class="para">
+ Holds
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ http://plf.zarb.org/
+ </div>
+
+ </td><td>
+ <div class="para">
+ The Penguin Liberation Front has RPMs that for legal reasons cannot be included in the Mandrake Linux distribution.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ www.math.unl.edu/~rdieter/Projects/
+ </div>
+
+ </td><td>
+ <div class="para">
+ Rex Dieter’s RPM site
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ www.rpmhelp.net/
+ </div>
+
+ </td><td>
+ <div class="para">
+ Mandrake Linux RPMs
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ www.aucs.org/rpmcenter/
+ </div>
+
+ </td><td>
+ <div class="para">
+ Edwin Chan's Red Hat RPMs
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ www.owlriver.com/projects/links/
+ </div>
+
+ </td><td>
+ <div class="para">
+ Owl River Company RPMs
+ </div>
+
+ </td></tr></tbody></table></div></div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch06s04.html"><strong>Înapoi</strong>6.4. Summary</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch07s02.html"><strong>Înainte</strong>7.2. Graphical RPM Management</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-online-resources.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-online-resources.html
new file mode 100644
index 0000000..b11f598
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-online-resources.html
@@ -0,0 +1,412 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Cap. 25. RPM Resources</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="index.html" title="Ghid RPM" /><link rel="prev" href="ch-package-structure.html" title="Cap. 24. RPM Package File Structure" /><link rel="next" href="ch25s02.html" title="25.2. Accessing RPM Mailing Lists and Newsgroups" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-package-structure.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch25s02.html"
><strong>ÃŽnainte</strong></a></li></ul><div xml:lang="ro" class="chapter" id="ch-online-resources" lang="ro"><div class="titlepage"><div><div><h2 class="title">Cap. 25. RPM Resources</h2></div></div></div><div class="toc"><dl><dt><span class="sect1"><a href="ch-online-resources.html#id701853">25.1. Finding RPM Sites</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch-online-resources.html#id667310">25.1.1. The main rpm.org site</a></span></dt><dt><span class="sect2"><a href="ch-online-resources.html#id562433">25.1.2. RPM locator sites</a></span></dt><dt><span class="sect2"><a href="ch-online-resources.html#id798080">25.1.3. RPM tools sites</a></span></dt><dt><span class="sect2"><a href="ch-online-resources.html#id626076">25.1.4. Programming sites</a></span></dt><dt><span class="sect2"><a href="ch-online-resources.html#id626107">25.1.5. Sites related to RPM</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch25s02.html">25.2. Accessing RPM Mailing Lists and Ne
wsgroups</a></span></dt></dl></div><div class="para">
+ This appendix covers:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Finding RPM sites on the Internet
+ </div></li><li class="listitem"><div class="para">
+ Accessing RPM newsgroups and mailing lists
+ </div></li></ul></div><div class="para">
+ This appendix covers the material available on the Internet for working with RPM.
+ </div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id701853" class="title">Finding RPM Sites</h1></div></div></div><div class="para">
+ There is a wealth of RPM material online, although some of it is hard to find. The following sections list a number of RPM-related sites, divided by category. Note that as with any Internet sites, the sites listed my change or disappear.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id667310" class="title">The main rpm.org site</h1></div></div></div><div class="para">
+ The main RPM site is www.rpm.org. This site provides the official distributions of the RPM software, as well as a lot of documentation online.
+ </div><div class="para">
+ Table F-1 lists a number of useful links on this site.
+ </div><div class="para">
+ Table F-1 Links on the rpm.org site
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Link
+ </div>
+
+ </td><td>
+ <div class="para">
+ Holds
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ ftp://ftp.rpm.org/pub/rpm/dist/
+ </div>
+
+ </td><td>
+ <div class="para">
+ RPM software downloads
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ ftp://ftp.rpm.org/pub/
+ </div>
+
+ </td><td>
+ <div class="para">
+ rpm.org download site
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ www.rpm.org/cvs_help/
+ </div>
+
+ </td><td>
+ <div class="para">
+ Instructions for accessing the RPM CVS repository
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ www.rpm.org/hintskinks/
+ </div>
+
+ </td><td>
+ <div class="para">
+ Tips for working with RPM
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ www.rpm.org/hintskinks/bootstrap/
+ </div>
+
+ </td><td>
+ <div class="para">
+ Good tips on bootstrapping RPM to new platforms
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ www.rpm.org/howto/
+ </div>
+
+ </td><td>
+ <div class="para">
+ How-to documents for working with RPM
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ www.rpm.org/max-rpm/
+ </div>
+
+ </td><td>
+ <div class="para">
+ Maximum RPM by Edward C. Bailey
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ www.rpm.org/RPM-HOWTO/
+ </div>
+
+ </td><td>
+ <div class="para">
+ Good introductory tutorial
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ www.rpm.org/rpmapi-4.1/
+ </div>
+
+ </td><td>
+ <div class="para">
+ API documentation
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ The main RPM FTP site, at ftp://ftp.rpm.org/pub/, includes the RPM distributions, as well as the Berkeley DB version 3 library, and the text of the book Maximum RPM. Download RPM software from ftp://ftp.rpm.org/pub/rpm/dist/.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id562433" class="title">RPM locator sites</h1></div></div></div><div class="para">
+ A number of sites help you find RPMs for various applications. On the main sites, you can find specially built RPMs for a variety of Linux distributions. You can then download the RPMs made especially for your systems.
+ </div><div class="para">
+ The main RPM-finding site is rpmfind.net, which offers a search engine as well as software you can run on your site.
+ </div><div class="para">
+ The RPM PBone Search, at http://rpm.pbone.net/, is also very useful.
+ </div><div class="para">
+ The www.rpm.org/packagers/ site lists a number of places that package RPMs and provide them for downloading.
+ </div><div class="para">
+ Many Java libraries and packages are available in RPM format from www.jpackage.org/.
+ </div><div class="para">
+ Table F-2 lists a number of other RPM download sites.
+ </div><div class="para">
+ Table F-2 RPM download sites
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Site
+ </div>
+
+ </td><td>
+ <div class="para">
+ Holds
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpmfind.net
+ </div>
+
+ </td><td>
+ <div class="para">
+ Links to a huge number of RPMs, many specific to various Linux distributions
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ http://rpm.pbone.net/
+ </div>
+
+ </td><td>
+ <div class="para">
+ RPM PBone search, useful for finding RPMs
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ www.rpm.org/packagers/
+ </div>
+
+ </td><td>
+ <div class="para">
+ Lists a number of sites that provide RPMs for download
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ www.javapackage.org
+ </div>
+
+ </td><td>
+ <div class="para">
+ Many Java packages in RPM format
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ http://plf.zarb.org/
+ </div>
+
+ </td><td>
+ <div class="para">
+ The Penguin Liberation Front has RPMs that for legal reasons cannot be included in the Mandrake Linux distribution.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ www.math.unl.edu/~rdieter/Projects
+ </div>
+
+ </td><td>
+ <div class="para">
+ Rex Dieter’s RPM site
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ www.rpmhelp.net
+ </div>
+
+ </td><td>
+ <div class="para">
+ Mandrake Linux RPMs
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ www.aucs.org/rpmcenter/
+ </div>
+
+ </td><td>
+ <div class="para">
+ Edwin Chan's Red Hat RPMs
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ www.owlriver.com/projects/links/
+ </div>
+
+ </td><td>
+ <div class="para">
+ Owl River Company RPMs
+ </div>
+
+ </td></tr></tbody></table></div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id798080" class="title">RPM tools sites</h1></div></div></div><div class="para">
+ A large number of tools exist to help you work with RPMs. The following sites list some of the main tools:
+ </div><div class="para">
+ *For the vim text editor, you can download a spec.vim syntax file from http://pegasus.rutgers.edu/~elflord/vim/syntax/spec.vim.
+ </div><div class="para">
+ *For emacs, you can download an Emacs mode for spec files from http://tihlde.org/~stigb/rpm-spec-mode.el.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ <a class="xref" href="ch-development-tools.html">Cap. 26, <em>Linux Text Editors and Development Tools</em></a> lists links for a number of text editors.
+ </div><div class="para">
+ *The rpmlint tool mentioned in <a class="xref" href="ch-extra-packaging-tools.html">Cap. 12, <em>Supplemental Packaging Software</em></a> is available at http://people.mandrakesoft.com/~flepied/projects/rpmlint/.
+ </div><div class="para">
+ Table F-3 lists a number of RPM-related tools and the sites you can find more information on the tools.
+ </div><div class="para">
+ Table F-3 RPM-related tools
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Tool
+ </div>
+
+ </td><td>
+ <div class="para">
+ Site
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ apt-rpm
+ </div>
+
+ </td><td>
+ <div class="para">
+ ftp://ftp.conectiva.com/pub/conectiva/EXPERIMENTAL/apt/
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ apt4rpm
+ </div>
+
+ </td><td>
+ <div class="para">
+ http://apt4rpm.sourceforge.net/
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ AutoRPM
+ </div>
+
+ </td><td>
+ <div class="para">
+ www.autorpm.org
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ AutoUpdate
+ </div>
+
+ </td><td>
+ <div class="para">
+ www.mat.univie.ac.at/~gerald/ftp/autoupdate
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ current
+ </div>
+
+ </td><td>
+ <div class="para">
+ www.biology.duke.edu/computer/unix/current/
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ kpackage
+ </div>
+
+ </td><td>
+ <div class="para">
+ www.kde.org
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ MakeRPM.pl
+ </div>
+
+ </td><td>
+ <div class="para">
+ www.perl.com/CPAN/modules/by-authors/id/JWIED
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ poldek
+ </div>
+
+ </td><td>
+ <div class="para">
+ http://poldek.pld.org.pl/
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpm2html
+ </div>
+
+ </td><td>
+ <div class="para">
+ rpmfind.net/linux/rpm2html/
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpmfind
+ </div>
+
+ </td><td>
+ <div class="para">
+ rpmfind.net
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RUST
+ </div>
+
+ </td><td>
+ <div class="para">
+ www.rusthq.com
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ setup.sh
+ </div>
+
+ </td><td>
+ <div class="para">
+ www.mmedia.is/~bre/programs/setup.sh
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ urpmi
+ </div>
+
+ </td><td>
+ <div class="para">
+ www.linux-mandrake.com/cooker/urpmi.html
+ </div>
+
+ </td></tr></tbody></table></div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id626076" class="title">Programming sites</h1></div></div></div><div class="para">
+ Only a few sites exist to help developers with programming for RPM. I maintain some quick links to RPM sites at www.pconline.com/~erc/rpm.htm. Most of these links are focused for programming with RPM.
+ </div><div class="para">
+ The best sites for programming RPM are the online API documentation at www.rpm.org/rpmapi-4.1/ for the RPM 4.1 release, and the ftp.rpm.org/pub/rpm/dist/ site for downloading the RPM sources. There is a lot of documentation bundled with the source code.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ <a class="xref" href="ch-development-tools.html">Cap. 26, <em>Linux Text Editors and Development Tools</em></a> lists links for a number of Integrated Development Environments, or IDEs, aimed at programmers.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id626107" class="title">Sites related to RPM</h1></div></div></div><div class="para">
+ If you try to make cross-platform RPMs, especially RPMs that should work for multiple versions of Linux, it is very important to follow the Linux standards for things like file placement and package formats.
+ </div><div class="para">
+ The Filesystem Hierarchy Standard, or FHS, covers Linux directory layout at www.pathname.com/fhs/.
+ </div><div class="para">
+ The Linux Standards Base is working on standardizing on the RPM package file format. See www.linuxbase.org for details.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-package-structure.html"><strong>Înapoi</strong>Cap. 24. RPM Package File Structure</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch25s02.html"><strong>Înainte</strong>25.2. Accessing RPM Mailing Lists and Newsgroups</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-other-linuxes.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-other-linuxes.html
new file mode 100644
index 0000000..1a392e2
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-other-linuxes.html
@@ -0,0 +1,107 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Cap. 18. Using RPM on Non-Red Hat Linuxes</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="index.html" title="Ghid RPM" /><link rel="prev" href="ch17s05.html" title="17.5. Summary" /><link rel="next" href="ch18s02.html" title="18.2. Handling Problems Building RPMs" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch17s05.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch18s02.html"><strong>ÃŽnainte</strong></a></li></ul><div xml:lang="ro"
class="chapter" id="ch-other-linuxes" lang="ro"><div class="titlepage"><div><div><h2 class="title">Cap. 18. Using RPM on Non-Red Hat Linuxes</h2></div></div></div><div class="toc"><dl><dt><span class="sect1"><a href="ch-other-linuxes.html#id492534">18.1. Troubleshooting RPM Installation Issues</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch-other-linuxes.html#id578601">18.1.1. Dealing with RPM versions</a></span></dt><dt><span class="sect2"><a href="ch-other-linuxes.html#id743717">18.1.2. Dealing with divisions of software into packages</a></span></dt><dt><span class="sect2"><a href="ch-other-linuxes.html#id841602">18.1.3. Dealing with dependency issues</a></span></dt><dt><span class="sect2"><a href="ch-other-linuxes.html#id556728">18.1.4. Dealing with install locations</a></span></dt><dt><span class="sect2"><a href="ch-other-linuxes.html#id638386">18.1.5. When all else fails, rebuild from the source package</a></span></dt></dl></dd><dt><span class="sect1"><a href
="ch18s02.html">18.2. Handling Problems Building RPMs</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch18s02.html#id638432">18.2.1. Writing distribution-specific packages</a></span></dt><dt><span class="sect2"><a href="ch18s02s02.html">18.2.2. Dealing with automatic dependency generation</a></span></dt><dt><span class="sect2"><a href="ch18s02s03.html">18.2.3. Dealing with different macros</a></span></dt><dt><span class="sect2"><a href="ch18s02s04.html">18.2.4. Making relocatable packages</a></span></dt><dt><span class="sect2"><a href="ch18s02s05.html">18.2.5. Creating an RPM build environment</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch18s03.html">18.3. Dealing with Non-RPM-Based Linux Versions</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch18s03.html#id554032">18.3.1. Handling non-RPM packages with alien</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch18s04.html">18.4. Standardizing RPMs</a></span></dt><dd><dl><dt><span class=
"sect2"><a href="ch18s04.html#id554078">18.4.1. Filesystem Hierarchy Standard</a></span></dt><dt><span class="sect2"><a href="ch18s04s02.html">18.4.2. RPM adoption</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch18s05.html">18.5. Summary</a></span></dt></dl></div><div class="para">
+ This chapter covers:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Dealing with RPM issues on other versions of Linux
+ </div></li><li class="listitem"><div class="para">
+ RPM standardization
+ </div></li><li class="listitem"><div class="para">
+ Working around RPM differences when installing RPMs
+ </div></li><li class="listitem"><div class="para">
+ Working around RPM differences when building RPMs
+ </div></li><li class="listitem"><div class="para">
+ Dealing with non-RPM-based Linux distributions
+ </div></li></ul></div><div class="para">
+ Although its name was originally the Red Hat Package Manager, RPM has been adopted by most major Linux distributions. With this adoption, RPM has moved from its Red Hat roots, and RPM now stands for the RPM Package Manager.
+ </div><div class="para">
+ In addition, the RPM package format is being adopted by the Linux Standards Base (LSB). The LSB defines a set of standards to help maintain compatibility for all Linux distributions.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ See www.linuxbase.org for more on the LSB.
+ </div><div class="para">
+ This chapter covers differences in how Linux distributions use RPM, ways to work around these differences, and also tools you can use for non-RPM distributions.
+ </div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id492534" class="title">Troubleshooting RPM Installation Issues</h1></div></div></div><div class="para">
+ The main RPM issues when dealing with installing RPMs on other versions of Linux are:
+ </div><div class="para">
+ *Different versions of RPM itself
+ </div><div class="para">
+ *Different divisions of software into packages
+ </div><div class="para">
+ *Dealing with dependency issues
+ </div><div class="para">
+ *Different install locations
+ </div><div class="para">
+ The following sections expand on these issues.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id578601" class="title">Dealing with RPM versions</h1></div></div></div><div class="para">
+ Red Hat Linux 8.0 ships with RPM version 4.1. Other distributions of Linux ship with other versions of RPM. Thus, one of the first commands you can run on another Linux distribution is the rpm --version command, to see what RPM version is in use and help identify any issues. For example:
+ </div><div class="para">
+ $ rpm --version
+ </div><div class="para">
+ RPM version 4.1
+ </div><div class="para">
+ Once you know the RPM version, you can plan for any issues that arise from installing RPMs made with a different RPM version. For example, RPM 4.0 and higher inserts dependency information automatically into RPMs. If your Linux distribution runs RPM 3.x, you may need to disable some of the dependency checks, for example, if you want to install RPMs built under RPM 4.x onto an RPM 3.x system.
+ </div><div class="para">
+ On installing RPMs, you can disable the dependency checks with the --nodeps option. If you do this, though, you should manually check that the dependencies are really met by your Linux installation.
+ </div><div class="para">
+ On the other hand, if you want to install RPMs built on an RPM 3.x system onto an RPM 4.x system, you may need to deal with package signatures. RPM 4.x versions also automatically check for signatures. When installing packages on an RPM 4.x system, you can disable this feature with the --nosignature option.
+ </div><div class="para">
+ Using these techniques, you should be able to install packages built with RPM 4.1 on systems that use RPM 3.x versions or vice versa.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id743717" class="title">Dealing with divisions of software into packages</h1></div></div></div><div class="para">
+ There is no standardization as to how large applications are divided into packages on different Linux distributions. This means that dependencies between packages may differ.
+ </div><div class="para">
+ If your dependencies are for packages provided with the Linux distribution, which includes a huge number of packages, you must address this issue. The package an RPM depends on may not exist and may not even be needed, on a particular Linux distribution.
+ </div><div class="para">
+ If instead the dependencies are for files, especially shared libraries, you should be okay for the most part, unless the files are located in different directories.
+ </div><div class="para">
+ The only real solution to this problem is to turn off dependency checks on installing, with the --nodeps option. Then you must check manually that your system really does provide all the necessary dependencies. Use the techniques shown in <a class="xref" href="ch-dependencies.html">Cap. 5, <em>Package Dependencies</em></a> to verify all the dependencies are met on your system.
+ </div><div class="para">
+ Warning
+ </div><div class="para">
+ Using the --nodeps option can lead to problems with your RPM database, because you are installing packages by defeating the RPM system's safeguards for dependencies. Only use the --nodeps option if you are really sure the dependencies are met on your system, even if from a different package than expected.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id841602" class="title">Dealing with dependency issues</h1></div></div></div><div class="para">
+ One of the toughest areas to deal with is the problem of dependencies. This topic ranges from the very simple issue of installing a necessary package to complex issues of shared library versions or particular Perl modules.
+ </div><div class="para">
+ Start with the simple case and make certain that you haven’t failed to install a necessary RPM that provides the right dependency. In most cases, you can download a vendor-specific package from your Linux vendor, such as www.suse.com for SUSE Linux. Most Linux vendors provide HTTP or FTP sites with a large set of packages created for their distributions. If such a distribution-specific package solves a dependency issue, this is the easiest way around the problem.
+ </div><div class="para">
+ After you verify that you haven't simply omitted a necessary package, move on to other potential explanations. Another issue involves shared libraries and ELF, or Extended Linking Format, symbols. A package may require an older or newer version of a shared library. Applications that are tied to a particular version of a shared library can cause problems, since you may not want to install incompatible versions of a shared library.
+ </div><div class="para">
+ If the dependency is for a system-shared library, such as the shared C library, you can often recompile the package (rebuild from a source RPM) to get the package to use the newer or older version of the system library. This is possible because most Linux applications don’t call on version-specific features of system shared libraries (some do, but most don’t). If the dependency is for an application-shared library, this is more serious, since there were likely API changes that could impact the application. Install the package owning the application-shared library and again, try to rebuild the package from the source RPM.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ You can use the rpm -qf command to query which package owns a given file. You can use the rpm -q --whatprovides command to query for which package provides a given capability. <a class="xref" href="ch-dependencies.html">Cap. 5, <em>Package Dependencies</em></a> covers more on dependencies.
+ </div><div class="para">
+ Some packages are considered developer packages. These usually depend on some base package. For example, the rpm-devel package depends on the rpm package. The rpm-python package depends on both the rpm package and the python package (at particular version numbers as well).
+ </div><div class="para">
+ This naming scheme of a base package and base-devel is used for Red Hat Linux packages, but may not be used for other vendor packages. In any case, you can solve this type of dependency by finding the relevant base packages that the package you are trying to install depends on. Consult the manuals that come with your Linux distribution or browse the online RPM repositories to see what naming conventions are used for your Linux distribution.
+ </div><div class="para">
+ Many packages depend on scripting language interpreters, such as Perl. Sometimes the dependency is based on scripts used in a package, such as install or trigger scripts. You can have problems arise with the locations of these scripting interpreters. Perl, for example, is usually installed in /usr/bin/perl on most Linux systems. Another common location is /usr/local/bin/perl. In addition, packages may depend on particular add-on modules, especially Perl modules. With most versions of Linux released in the last few years, you should be able to override a Perl dependency with the --nodeps option as long as you have Perl installed.
+ </div><div class="para">
+ File paths may also cause problems. For example, a file that a package depends on may be in a different location or owned by a different package. For this case, you can try to find the package that owns the file and make sure that package is installed. If your Linux vendor provides a pre-built RPM database of all packages, such as the rpmdb-redhat package, you can query this database to find out which package owns the file for that version of Linux.
+ </div><div class="para">
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id556728" class="title">Dealing with install locations</h1></div></div></div><div class="para">
+ Linux vendors can install software anywhere. For example, some distributions place a lot of software under /opt instead of the more common /usr. From an RPM perspective, this is mostly an issue with file dependencies and the install location for packages. Evolving file system standards also help limit this issue.
+ </div><div class="para">
+ You can attempt to relocate any package using the --badreloc option.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ <a class="xref" href="ch-using-rpm.html">Cap. 3, <em>Using RPM</em></a> covers the --badreloc option.
+ </div><div class="para">
+ But, while the --badreloc option will relocate the files in a package, it will not modify the contents of those files. So, any file inside a package that references files and directory locations may not work properly, since it may have the old, invalid, paths.
+ </div><div class="para">
+ The only real way around this problem is to edit any script files that come with the package and contain hard-coded paths. If the paths reside inside binary executables, you need to get a source RPM for the package, patch the sources and then create a new RPM.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id638386" class="title">When all else fails, rebuild from the source package</h1></div></div></div><div class="para">
+ When all of these techniques fail to install a package, you still have a fallback option. If you have the source RPM for a package, you can install the source RPM on the new system and then edit the spec file until you can rebuild a package that will install on your version of Linux.
+ </div><div class="para">
+ For example, a set of Build Root Policy (brp) helper scripts are run at the end of the %install section in an RPM. These scripts perform tasks such as compressing man pages. The Mandrake brp scripts use bzip2 compression. Red Hat brp scripts use gzip compression. This is one case where rebuilding an RPM and then installing may work best.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch17s05.html"><strong>Înapoi</strong>17.5. Summary</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch18s02.html"><strong>Înainte</strong>18.2. Handling Problems Building RPMs</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-other-os.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-other-os.html
new file mode 100644
index 0000000..0cbfaaf
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-other-os.html
@@ -0,0 +1,284 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Cap. 19. RPM on Other Operating Systems</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="index.html" title="Ghid RPM" /><link rel="prev" href="ch18s05.html" title="18.5. Summary" /><link rel="next" href="ch19s02.html" title="19.2. Bootstrapping RPM On Other Operating Systems" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch18s05.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch19s02.html"><strong>ÃŽnainte</strong></a></li></ul><div x
ml:lang="ro" class="chapter" id="ch-other-os" lang="ro"><div class="titlepage"><div><div><h2 class="title">Cap. 19. RPM on Other Operating Systems</h2></div></div></div><div class="toc"><dl><dt><span class="sect1"><a href="ch-other-os.html#id715002">19.1. Running RPM on Other Operating Systems</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch-other-os.html#id742916">19.1.1. Getting RPM for your system</a></span></dt><dt><span class="sect2"><a href="ch-other-os.html#id719450">19.1.2. Running RPM on Windows</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch19s02.html">19.2. Bootstrapping RPM On Other Operating Systems</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch19s02.html#id719502">19.2.1. Downloading the RPM software</a></span></dt><dt><span class="sect2"><a href="ch19s02s02.html">19.2.2. Extracting the software</a></span></dt><dt><span class="sect2"><a href="ch19s02s03.html">19.2.3. Reading the INSTALL file</a></span></dt><dt><span class="sec
t2"><a href="ch19s02s04.html">19.2.4. Libraries required by RPM</a></span></dt><dt><span class="sect2"><a href="ch19s02s05.html">19.2.5. Tools for building RPM</a></span></dt><dt><span class="sect2"><a href="ch19s02s06.html">19.2.6. Compiling RPM</a></span></dt><dt><span class="sect2"><a href="ch19s02s07.html">19.2.7. Handling problems</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch19s03.html">19.3. Setting Up the RPM System</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch19s03.html#id498249">19.3.1. Setting up the RPM database</a></span></dt><dt><span class="sect2"><a href="ch19s03s02.html">19.3.2. Creating the RPM environment</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch19s04.html">19.4. Creating Non-Linux RPMS</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch19s04.html#id612860">19.4.1. Setting up a build environment</a></span></dt><dt><span class="sect2"><a href="ch19s04s02.html">19.4.2. Cross-building packages</a></span></d
t></dl></dd><dt><span class="sect1"><a href="ch19s05.html">19.5. Summary</a></span></dt></dl></div><div class="para">
+ This chapter covers:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Running RPM on other operating systems
+ </div></li><li class="listitem"><div class="para">
+ Bootstrapping RPM on other operating systems
+ </div></li><li class="listitem"><div class="para">
+ Setting up the RPM environment
+ </div></li><li class="listitem"><div class="para">
+ Creating non-Linux RPMs
+ </div></li><li class="listitem"><div class="para">
+ Setting up an RPM build environment
+ </div></li><li class="listitem"><div class="para">
+ Cross-building packages
+ </div></li></ul></div><div class="para">
+ RPM was originally designed on Linux and for most of its life has been a Linux-centric package management system. But most Linux programs are portable to most versions of Unix or Unix -like operating systems. Linux is, after all, a Unix-workalike operating system.
+ </div><div class="para">
+ The RPM system is no exception. It has been ported to a number of operating systems, including quite a few Unix variants. The source code is freely available, so you can port RPM to other systems as well.
+ </div><div class="para">
+ This chapter covers running RPM on non-Linux operating systems, including getting the RPM system in the first place, bootstrapping an RPM environment, and creating packages for other operating systems.
+ </div><div class="para">
+ The first step is to get RPM for your system, or port RPM if it isn’t already available.
+ </div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id715002" class="title">Running RPM on Other Operating Systems</h1></div></div></div><div class="para">
+ The RPM system, made up of mostly the rpm and rpmbuild commands, have been ported to a number of operating systems. There is nothing stopping you from running the RPM system on other platforms.
+ </div><div class="para">
+ Other operating systems have their own native package management software. You may prefer the way RPM works, or merely want to standardize on RPM across all platforms you manage. There will always be a few issues, however, when running RPM on other operating systems. For example, operating system patches and updates are likely to be distributed in the operating system’s native package management format, not RPM. Many applications will be updated also using the system’s native package management format.
+ </div><div class="para">
+ You will need to always keep in mind that there are two package management schemes in use: RPM and the native one. This issue has not stopped a great many people from using RPM on other systems, though, as shown by the list of platforms RPM has been ported to (see Table 20-1 for the list).
+ </div><div class="para">
+ On the plus side, package management has always been one of the main areas where versions of Linux, Unix, and other operating systems differ, sometimes quite a lot. By using RPM, you can transfer your knowledge of package management from one system to another, saving valuable time and hassles. You will be able to update systems in the same manner, a big plus if you manage a diverse set of systems.
+ </div><div class="para">
+ Another reason to use RPM on other operating systems is that in most cases, RPM provides far more capabilities than the native package management software. Following the RPM philosophy, each package can be separately verified, checked, and updated. Each package lists the other packages it depends on, and also lists the capabilities it provides. You can automate the installation and upgrade processes with RPM. You can also perform a lot of version and signature comparisons. All of this leads to a more secure, more robust system.
+ </div><div class="para">
+ Many operating systems don’t include these capabilities in the native package management software. This is why many users run RPM on other operating systems.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ See <a class="xref" href="ch-intro-rpm.html">Cap. 1, <em>Introduction to RPM</em></a> for more on the philosophy behind RPM.
+ </div><div class="para">
+ If you decide to use RPM on a non-Linux system, the first step is getting RPM for your system, if it is available.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id742916" class="title">Getting RPM for your system</h1></div></div></div><div class="para">
+ The first step to using RPM on non-Linux platforms is getting the RPM system for your platform. In most cases, this is a relatively easy step, as RPM has been ported to a great many platforms, as listed on the main RPM Web site.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ Links to RPM versions for various platforms are listed at www.rpm.org/platforms/.
+ </div><div class="para">
+ Go to this site and download the versions for the platforms you need. Table 20-1 lists the platforms RPM has been ported to, as reported by the RPM site.
+ </div><div class="para">
+ Table 20-1 Available Platforms for RPM
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Platform
+ </div>
+
+ </td><td>
+ <div class="para">
+ Notes
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ AIX
+ </div>
+
+ </td><td>
+ <div class="para">
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ AmigaOS
+ </div>
+
+ </td><td>
+ <div class="para">
+ With GeekGadgets
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ BeOS
+ </div>
+
+ </td><td>
+ <div class="para">
+ With GeekGadgets
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ FreeBSD
+ </div>
+
+ </td><td>
+ <div class="para">
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ HP-UX
+ </div>
+
+ </td><td>
+ <div class="para">
+ 10.20+, 9.04
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ IRIX
+ </div>
+
+ </td><td>
+ <div class="para">
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Linux
+ </div>
+
+ </td><td>
+ <div class="para">
+ Multiple platforms including Alpha, Intel, Motorola 68000, SGI MIPS, PowerPC, and SPARC
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ LynxOS
+ </div>
+
+ </td><td>
+ <div class="para">
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ MachTen
+ </div>
+
+ </td><td>
+ <div class="para">
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ MacOS X
+ </div>
+
+ </td><td>
+ <div class="para">
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Mint
+ </div>
+
+ </td><td>
+ <div class="para">
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ NCS System V
+ </div>
+
+ </td><td>
+ <div class="para">
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ NetBSD
+ </div>
+
+ </td><td>
+ <div class="para">
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ OS/2
+ </div>
+
+ </td><td>
+ <div class="para">
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ OSF/1
+ </div>
+
+ </td><td>
+ <div class="para">
+ 3.2+
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ SCO OpenServer
+ </div>
+
+ </td><td>
+ <div class="para">
+ 5.0.2+
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Sinix
+ </div>
+
+ </td><td>
+ <div class="para">
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Solaris
+ </div>
+
+ </td><td>
+ <div class="para">
+ Solaris for SPARC 2.4 and 8+, Solaris for Intel
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ SunOS 4.1.3
+ </div>
+
+ </td><td>
+ <div class="para">
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Windows
+ </div>
+
+ </td><td>
+ <div class="para">
+ Under Cygwin
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ Note that RPM has likely been ported to even more platforms. These are just the ones reported to the rpm.org site.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ If you fix a bug in RPM on a non-Linux system, or if you port RPM to a new system, please report this to the rpm.org site maintainers, as well as make your work available for others. You never know, but someone else may fix a problem you’re facing.
+ </div><div class="para">
+ If Table 20-1 does not cover the platforms you need, you must compile and bootstrap the RPM environment for your platforms, as covered in the "Bootstrapping RPM on Other Operating Systems" section, following.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ Don’t expect to find RPMs of the RPM system for these other platforms. If you did, there would be no way to install RPM. Instead, you’ll find RPM packaged in a variety of formats, typically using a native bundling format for a given system, or at least a supported format. Compressed tar files are very common. RPM for IRIX systems come in IRIX tardist format.
+ </div><div class="para">
+ If RPM is available for your system, download the package and follow any installation instructions that come with the package. For example, RPM for Solaris 8 requires the libiconv library, as well as the Solaris packages SUNWzlib and SUNWbzip. You must install these packages prior to installing RPM.
+ </div><div class="para">
+ Each operating system will have similar requirements. Windows systems have a few extra requirements due to the fact that Windows is very different from Linux or Unix-like systems.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id719450" class="title">Running RPM on Windows</h1></div></div></div><div class="para">
+ The version of RPM for Windows requires cygwin, originally the Cygnus port of many Unix tools to Windows. Now part of Red Hat, you can download the cygwin environment from the main cygwin site.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ Download cygwin from www.cygwin.com.
+ </div><div class="para">
+ You can download a setup.exe program to install the environment on Windows. After installation, you can download the RPM system for Windows.
+ </div><div class="para">
+ After you have RPM installed, you can set up your RPM system. If RPM wasn’t already ported to your operating systems, however, you will need to bootstrap RPM on your platforms.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch18s05.html"><strong>Înapoi</strong>18.5. Summary</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch19s02.html"><strong>Înainte</strong>19.2. Bootstrapping RPM On Other Operating Systems</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-package-structure.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-package-structure.html
new file mode 100644
index 0000000..9a74d78
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-package-structure.html
@@ -0,0 +1,2053 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Cap. 24. RPM Package File Structure</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="index.html" title="Ghid RPM" /><link rel="prev" href="ch-rpm-evolution.html" title="Cap. 23. RPM Feature Evolution" /><link rel="next" href="ch-online-resources.html" title="Cap. 25. RPM Resources" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-rpm-evolution.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch-online-resources.html"><strong>ÃŽnain
te</strong></a></li></ul><div xml:lang="ro" class="chapter" id="ch-package-structure" lang="ro"><div class="titlepage"><div><div><h2 class="title">Cap. 24. RPM Package File Structure</h2></div></div></div><div class="toc"><dl><dt><span class="sect1"><a href="ch-package-structure.html#id856787">24.1. The Package File</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch-package-structure.html#id582395">24.1.1. The file identifier</a></span></dt><dt><span class="sect2"><a href="ch-package-structure.html#id843773">24.1.2. The signature</a></span></dt><dt><span class="sect2"><a href="ch-package-structure.html#id674921">24.1.3. The header</a></span></dt><dt><span class="sect2"><a href="ch-package-structure.html#id800907">24.1.4. The payload</a></span></dt></dl></dd></dl></div><div class="para">
+ This appendix covers:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ RPM package file structure
+ </div></li><li class="listitem"><div class="para">
+ RPM header entry formats
+ </div></li><li class="listitem"><div class="para">
+ Payload format
+ </div></li></ul></div><div class="para">
+ This appendix describes the format of RPM package files. You can combine this information with C, Perl, or Python data structures to access the information. In all cases, you should access elements in an RPM file using one of the available programming libraries. Do not attempt to access the files directly, as you may inadvertently damage the RPM file.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ <a class="xref" href="ch-programming-c.html">Cap. 15, <em>Programming RPM with C</em></a>, <a class="xref" href="ch-rpm-programming-python.html">Cap. 16, <em>Programming RPM with Python</em></a>, and <a class="xref" href="ch-programming-perl.html">Cap. 17, <em>Programming RPM with Perl</em></a> cover programming with C, Python, and Perl, respectively.
+ </div><div class="para">
+ The RPM package format described here has been standardized as part of the Linux Standards Base, or LSB, version 1.3.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ The LSB 1.3 section on package file formats is available at www.linuxbase.org/spec/refspecs/LSB_1.3.0/gLSB/gLSB.html#PACKAGEFMT.
+ </div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id856787" class="title">The Package File</h1></div></div></div><div class="para">
+ RPM packages are delivered with one file per package. All RPM files have the following basic format of four sections:
+ </div><div class="para">
+ *A lead or file identifier
+ </div><div class="para">
+ *A signature
+ </div><div class="para">
+ *Header information
+ </div><div class="para">
+ *Archive of the payload, the files to install
+ </div><div class="para">
+ All values are encoded in network byte order, for portability to multiple processor architectures.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id582395" class="title">The file identifier</h1></div></div></div><div class="para">
+ Also called the lead or the rpmlead, the identifier marks that this file is an RPM file. It contains a magic number that the file command uses to detect RPM files. It also contains version and architecture information.
+ </div><div class="para">
+ The start of the identifier is the so-called magic number. The file command reads the first few bytes of a file and compares the values found with the contents of /usr/share/magic (/etc/magic on many UNIX systems), a database of magic numbers. This allows the file command to quickly identify files.
+ </div><div class="para">
+ The identifier includes the RPM version number, that is, the version of the RPM file format used for the package. The identifier also has a flag that tells the type of the RPM file, whether the file contains a binary or source package. An architecture flag allows RPM software to double-check that you are not trying to install a package for a non-compatible architecture.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id843773" class="title">The signature</h1></div></div></div><div class="para">
+ The signature appears after the lead or identifier section. The RPM signature helps verify the integrity of the package, and optionally the authenticity.
+ </div><div class="para">
+ The signature works by performing a mathematical function on the header and archive section of the file. The mathematical function can be an encryption process, such as PGP (Pretty Good Privacy), or a message digest in MD5 format.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id674921" class="title">The header</h1></div></div></div><div class="para">
+ The identifier section no longer contains enough information to describe modern RPMs. Furthermore, the identifier section is nowhere near as flexible as today’s packages require. To counter these deficiencies, the header section was introduced to include more information about the package.
+ </div><div class="para">
+ The header structure contains three parts:
+ </div><div class="para">
+ *Header record
+ </div><div class="para">
+ *One or more header index record structures
+ </div><div class="para">
+ *Data for the index record structures
+ </div><div class="para">
+ The header record identifies this as the RPM header. It also contains a count of the number of index records and the size of the index record data.
+ </div><div class="para">
+ Each index record uses a structure that contains a tag number for the data it contains. This includes tag IDs for the copyright message, name of the package, version number, and so on. A type number identifies the type of the item. An offset indicates where in the data section the data for this header item begins. A count indicates how many items of the given type are in this header entry. You can multiply the count by the size of the type to get the number of bytes used for the header entry.
+ </div><div class="para">
+ Table D-1 lists the type identifiers.
+ </div><div class="para">
+ Table D-1 Header type identifiers
+ </div><div class="informaltable"><table border="1"><colgroup><col width="33%" /><col width="33%" /><col width="33%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Constant
+ </div>
+
+ </td><td>
+ <div class="para">
+ Value
+ </div>
+
+ </td><td>
+ <div class="para">
+ Size in Bytes
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPM_NULL_TYPE
+ </div>
+
+ </td><td>
+ <div class="para">
+ 0
+ </div>
+
+ </td><td>
+ <div class="para">
+ No size
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPM_CHAR_TYPE
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPM_INT8_TYPE
+ </div>
+
+ </td><td>
+ <div class="para">
+ 2
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPM_INT16_TYPE
+ </div>
+
+ </td><td>
+ <div class="para">
+ 3
+ </div>
+
+ </td><td>
+ <div class="para">
+ 2
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPM_INT32_TYPE
+ </div>
+
+ </td><td>
+ <div class="para">
+ 4
+ </div>
+
+ </td><td>
+ <div class="para">
+ 4
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPM_INT64_TYPE
+ </div>
+
+ </td><td>
+ <div class="para">
+ 5
+ </div>
+
+ </td><td>
+ <div class="para">
+ Not supported yet
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPM_STRING_TYPE
+ </div>
+
+ </td><td>
+ <div class="para">
+ 6
+ </div>
+
+ </td><td>
+ <div class="para">
+ Variable number of bytes, terminated by a NULL
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPM_BIN_TYPE
+ </div>
+
+ </td><td>
+ <div class="para">
+ 7
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPM_STRING_ARRAY_TYPE
+ </div>
+
+ </td><td>
+ <div class="para">
+ 8
+ </div>
+
+ </td><td>
+ <div class="para">
+ Variable, vector of NULL-terminated strings
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPM_I18NSTRING_TYPE
+ </div>
+
+ </td><td>
+ <div class="para">
+ 9
+ </div>
+
+ </td><td>
+ <div class="para">
+ Variable, vector of NULL-terminated strings
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ Note
+ </div><div class="para">
+ Integer values are aligned on 2-byte (16-bit integers) or 4-byte (32-bit integers) boundaries.
+ </div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id569735" class="title">Header Tags</h1></div></div></div><div class="para">
+ Table D-2 lists the tag identifiers.
+ </div><div class="para">
+ Table D-2 Header entry tag identifiers
+ </div><div class="informaltable"><table border="1"><colgroup><col width="25%" /><col width="25%" /><col width="25%" /><col width="25%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Constant
+ </div>
+
+ </td><td>
+ <div class="para">
+ Value
+ </div>
+
+ </td><td>
+ <div class="para">
+ Type
+ </div>
+
+ </td><td>
+ <div class="para">
+ Required?
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_NAME
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1000
+ </div>
+
+ </td><td>
+ <div class="para">
+ STRING
+ </div>
+
+ </td><td>
+ <div class="para">
+ Yes
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_VERSION
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1001
+ </div>
+
+ </td><td>
+ <div class="para">
+ STRING
+ </div>
+
+ </td><td>
+ <div class="para">
+ Yes
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_RELEASE
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1002
+ </div>
+
+ </td><td>
+ <div class="para">
+ STRING
+ </div>
+
+ </td><td>
+ <div class="para">
+ Yes
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_SUMMARY
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1004
+ </div>
+
+ </td><td>
+ <div class="para">
+ I18NSTRING
+ </div>
+
+ </td><td>
+ <div class="para">
+ Yes
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_DESCRIPTION
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1005
+ </div>
+
+ </td><td>
+ <div class="para">
+ I18NSTRING
+ </div>
+
+ </td><td>
+ <div class="para">
+ Yes
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_BUILDTIME
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1006
+ </div>
+
+ </td><td>
+ <div class="para">
+ INT32
+ </div>
+
+ </td><td>
+ <div class="para">
+ Optional
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_BUILDHOST
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1007
+ </div>
+
+ </td><td>
+ <div class="para">
+ STRING
+ </div>
+
+ </td><td>
+ <div class="para">
+ Optional
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_SIZE
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1009
+ </div>
+
+ </td><td>
+ <div class="para">
+ INT32
+ </div>
+
+ </td><td>
+ <div class="para">
+ Yes
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_LICENSE
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1014
+ </div>
+
+ </td><td>
+ <div class="para">
+ STRING
+ </div>
+
+ </td><td>
+ <div class="para">
+ Yes
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_GROUP
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1016
+ </div>
+
+ </td><td>
+ <div class="para">
+ I18NSTRING
+ </div>
+
+ </td><td>
+ <div class="para">
+ Yes
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_OS
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1021
+ </div>
+
+ </td><td>
+ <div class="para">
+ STRING
+ </div>
+
+ </td><td>
+ <div class="para">
+ Yes
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_ARCH
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1022
+ </div>
+
+ </td><td>
+ <div class="para">
+ STRING
+ </div>
+
+ </td><td>
+ <div class="para">
+ Yes
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_SOURCERPM
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1044
+ </div>
+
+ </td><td>
+ <div class="para">
+ STRING
+ </div>
+
+ </td><td>
+ <div class="para">
+ Optional
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_FILEVERIFYFLAGS
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1045
+ </div>
+
+ </td><td>
+ <div class="para">
+ INT32
+ </div>
+
+ </td><td>
+ <div class="para">
+ Optional
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_ARCHIVESIZE
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1046
+ </div>
+
+ </td><td>
+ <div class="para">
+ INT32
+ </div>
+
+ </td><td>
+ <div class="para">
+ Optional
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_RPMVERSION
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1064
+ </div>
+
+ </td><td>
+ <div class="para">
+ STRING
+ </div>
+
+ </td><td>
+ <div class="para">
+ Optional
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_CHANGELOGTIME
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1080
+ </div>
+
+ </td><td>
+ <div class="para">
+ INT32
+ </div>
+
+ </td><td>
+ <div class="para">
+ Optional
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_CHANGELOGNAME
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1081
+ </div>
+
+ </td><td>
+ <div class="para">
+ STRING_ARRAY
+ </div>
+
+ </td><td>
+ <div class="para">
+ Optional
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_CHANGELOGTEXT
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1082
+ </div>
+
+ </td><td>
+ <div class="para">
+ STRING_ARRAY
+ </div>
+
+ </td><td>
+ <div class="para">
+ Optional
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_COOKIE
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1094
+ </div>
+
+ </td><td>
+ <div class="para">
+ STRING
+ </div>
+
+ </td><td>
+ <div class="para">
+ Optional
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_OPTFLAGS
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1122
+ </div>
+
+ </td><td>
+ <div class="para">
+ STRING
+ </div>
+
+ </td><td>
+ <div class="para">
+ Optional
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_PAYLOADFORMAT
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1124
+ </div>
+
+ </td><td>
+ <div class="para">
+ STRING
+ </div>
+
+ </td><td>
+ <div class="para">
+ Yes
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_PAYLOADCOMPRESSOR
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1125
+ </div>
+
+ </td><td>
+ <div class="para">
+ STRING
+ </div>
+
+ </td><td>
+ <div class="para">
+ Yes
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_PAYLOADFLAGS
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1126
+ </div>
+
+ </td><td>
+ <div class="para">
+ STRING
+ </div>
+
+ </td><td>
+ <div class="para">
+ Yes
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_RHNPLATFORM
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1131
+ </div>
+
+ </td><td>
+ <div class="para">
+ STRING
+ </div>
+
+ </td><td>
+ <div class="para">
+ Deprecated
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_PLATFORM
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1132
+ </div>
+
+ </td><td>
+ <div class="para">
+ STRING
+ </div>
+
+ </td><td>
+ <div class="para">
+ Optional
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ Most of these tags are self-explanatory; however, a few tags hold special meaning. The RPMTAG_SIZE tag holds the size of all the regular files in the payload. The RPMTAG_ARCHIVESIZE tag holds the uncompressed size of the payload section, including the necessary cpio headers. The RPMTAG_COOKIE tag holds an opaque string.
+ </div><div class="para">
+ According to the LSB standards, the RPMTAG_PAYLOADFORMAT must always be cpio. The RPMTAG_PAYLOADCOMPRESSOR must be gzip. The RPMTAG_PAYLOADFLAGS must always be 9.
+ </div><div class="para">
+ The RPMTAG_OPTFLAGS tag holds special compiler flags used to build the package. The RPMTAG_PLATFORM and RPMTAG_RHNPLATFORM tags hold opaque strings.
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id565082" class="title">Private Header Tags</h1></div></div></div><div class="para">
+ Table D-3 lists header tags that are considered private.
+ </div><div class="para">
+ Table D-3 Private header tags
+ </div><div class="informaltable"><table border="1"><colgroup><col width="25%" /><col width="25%" /><col width="25%" /><col width="25%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Constant
+ </div>
+
+ </td><td>
+ <div class="para">
+ Value
+ </div>
+
+ </td><td>
+ <div class="para">
+ Type
+ </div>
+
+ </td><td>
+ <div class="para">
+ Required?
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_HEADERSIGNATURES
+ </div>
+
+ </td><td>
+ <div class="para">
+ 62
+ </div>
+
+ </td><td>
+ <div class="para">
+ BIN
+ </div>
+
+ </td><td>
+ <div class="para">
+ Optional
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_HEADERIMMUTABLE
+ </div>
+
+ </td><td>
+ <div class="para">
+ 63
+ </div>
+
+ </td><td>
+ <div class="para">
+ BIN
+ </div>
+
+ </td><td>
+ <div class="para">
+ Optional
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_HEADERI18NTABLE
+ </div>
+
+ </td><td>
+ <div class="para">
+ 100
+ </div>
+
+ </td><td>
+ <div class="para">
+ STRING_ARRAY
+ </div>
+
+ </td><td>
+ <div class="para">
+ Yes
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ The RPMTAG_HEADERSIGNATURES tag indicates that this is a signature entry. The RPMTAG_HEADERIMMUTABLE tag indicates a header item that is used in the calculation of signatures. This data should be preserved.
+ </div><div class="para">
+ The RPMTAG_HEADERI18NTABLE tag holds a table of locales used for international text lookup.
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id532356" class="title">Signature Tags</h1></div></div></div><div class="para">
+ The signature section is implemented as a header structure, but it is not considered part of the RPM header. Table D-4 lists special signature-related tags.
+ </div><div class="para">
+ Table D-4 Signature-related tags
+ </div><div class="informaltable"><table border="1"><colgroup><col width="25%" /><col width="25%" /><col width="25%" /><col width="25%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Constant
+ </div>
+
+ </td><td>
+ <div class="para">
+ Value
+ </div>
+
+ </td><td>
+ <div class="para">
+ Type
+ </div>
+
+ </td><td>
+ <div class="para">
+ Required?
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ SIGTAG_SIGSIZE
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1000
+ </div>
+
+ </td><td>
+ <div class="para">
+ INT32
+ </div>
+
+ </td><td>
+ <div class="para">
+ Yes
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ SIGTAG_PGP
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1002
+ </div>
+
+ </td><td>
+ <div class="para">
+ BIN
+ </div>
+
+ </td><td>
+ <div class="para">
+ Optional
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ SIGTAG_MD5
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1004
+ </div>
+
+ </td><td>
+ <div class="para">
+ BIN
+ </div>
+
+ </td><td>
+ <div class="para">
+ Yes
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ SIGTAG_GPG
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1005
+ </div>
+
+ </td><td>
+ <div class="para">
+ BIN
+ </div>
+
+ </td><td>
+ <div class="para">
+ Optional
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ SIGTAG_PAYLOADSIZE
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1007
+ </div>
+
+ </td><td>
+ <div class="para">
+ INT32
+ </div>
+
+ </td><td>
+ <div class="para">
+ Optional
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ SIGTAG_SHA1HEADER
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1010
+ </div>
+
+ </td><td>
+ <div class="para">
+ STRING
+ </div>
+
+ </td><td>
+ <div class="para">
+ Optional
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ SIGTAG_DSAHEADER
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1011
+ </div>
+
+ </td><td>
+ <div class="para">
+ BIN
+ </div>
+
+ </td><td>
+ <div class="para">
+ Optional
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ SIGTAG_RSAHEADER
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1012
+ </div>
+
+ </td><td>
+ <div class="para">
+ BIN
+ </div>
+
+ </td><td>
+ <div class="para">
+ Optional
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ The SIGTAG_SIGSIZE tag specifies the size of the header and payload sections, while the SIGTAG_PAYLOADSIZE holds the uncompressed size of the payload.
+ </div><div class="para">
+ To verify the integrity of the package, the SIGTAG_MD5 tag holds a 128-bit MD5 checksum of the header and payload sections. The SIGTAG_SHA1HEADER holds an SHA1 checksum of the entire header section.
+ </div><div class="para">
+ To verify the authenticity of the package, the SIGTAG_PGP tag holds a Version 3 OpenPGP Signature Packet RSA signature of the header and payload areas. The SIGTAG_GPG tag holds a Version 3 OpenPGP Signature Packet DSA signature of the header and payload areas. The SIGTAG_DSAHEADER holds a DSA signature of just the header section. If the SIGTAG_DSAHEADER tag is included, the SIGTAG_GPG tag must also be present. The SIGTAG_ RSAHEADER holds an RSA signature of just the header section. If the SIGTAG_ RSAHEADER tag is included, the SIGTAG_PGP tag must also be present.
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id511298" class="title">Installation Tags</h1></div></div></div><div class="para">
+ A set of installation-specific tags tells the rpm program how to run the pre- and post-installation scripts. Table D-5 lists these tags.
+ </div><div class="para">
+ Table D-5 Installation tags
+ </div><div class="informaltable"><table border="1"><colgroup><col width="25%" /><col width="25%" /><col width="25%" /><col width="25%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Constant
+ </div>
+
+ </td><td>
+ <div class="para">
+ Value
+ </div>
+
+ </td><td>
+ <div class="para">
+ Type
+ </div>
+
+ </td><td>
+ <div class="para">
+ Required?
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_PREINPROG
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1085
+ </div>
+
+ </td><td>
+ <div class="para">
+ STRING
+ </div>
+
+ </td><td>
+ <div class="para">
+ Optional
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_POSTINPROG
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1086
+ </div>
+
+ </td><td>
+ <div class="para">
+ STRING
+ </div>
+
+ </td><td>
+ <div class="para">
+ Optional
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_PREUNPROG
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1087
+ </div>
+
+ </td><td>
+ <div class="para">
+ STRING
+ </div>
+
+ </td><td>
+ <div class="para">
+ Optional
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_POSTUNPROG
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1088
+ </div>
+
+ </td><td>
+ <div class="para">
+ STRING
+ </div>
+
+ </td><td>
+ <div class="para">
+ Optional
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ The RPMTAG_PREINPROG tag holds the name of the interpreter, such as sh, to run the pre-install script. Similarly, the RPMTAG_POSTINPROG tag holds the name of the interpreter to run the post-install script. RPMTAG_PREUNPROG and RPMTAG_POSTUNPROG are the same for the uninstall scripts.
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id564369" class="title">File Information Tags</h1></div></div></div><div class="para">
+ File information tags are placed in the header for convenient access. These tags describe the files in the payload. Table D-6 lists these tags.
+ </div><div class="para">
+ Table D-6 File information tags
+ </div><div class="informaltable"><table border="1"><colgroup><col width="25%" /><col width="25%" /><col width="25%" /><col width="25%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Constant
+ </div>
+
+ </td><td>
+ <div class="para">
+ Value
+ </div>
+
+ </td><td>
+ <div class="para">
+ Type
+ </div>
+
+ </td><td>
+ <div class="para">
+ Required?
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_OLDFILENAMES
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1027
+ </div>
+
+ </td><td>
+ <div class="para">
+ STRING_ARRAY
+ </div>
+
+ </td><td>
+ <div class="para">
+ Optional
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_FILESIZES
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1028
+ </div>
+
+ </td><td>
+ <div class="para">
+ INT32
+ </div>
+
+ </td><td>
+ <div class="para">
+ Yes
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_FILEMODES
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1030
+ </div>
+
+ </td><td>
+ <div class="para">
+ INT16
+ </div>
+
+ </td><td>
+ <div class="para">
+ Yes
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_FILERDEVS
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1033
+ </div>
+
+ </td><td>
+ <div class="para">
+ INT16
+ </div>
+
+ </td><td>
+ <div class="para">
+ Yes
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_FILEMTIMES
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1034
+ </div>
+
+ </td><td>
+ <div class="para">
+ INT32
+ </div>
+
+ </td><td>
+ <div class="para">
+ Yes
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_FILEMD5S
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1035
+ </div>
+
+ </td><td>
+ <div class="para">
+ STRING_ARRAY
+ </div>
+
+ </td><td>
+ <div class="para">
+ Yes
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_FILELINKTOS
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1036
+ </div>
+
+ </td><td>
+ <div class="para">
+ STRING_ARRAY
+ </div>
+
+ </td><td>
+ <div class="para">
+ Yes
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_FILEFLAGS
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1037
+ </div>
+
+ </td><td>
+ <div class="para">
+ INT32
+ </div>
+
+ </td><td>
+ <div class="para">
+ Yes
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_FILEUSERNAME
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1039
+ </div>
+
+ </td><td>
+ <div class="para">
+ STRING_ARRAY
+ </div>
+
+ </td><td>
+ <div class="para">
+ Yes
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_FILEGROUPNAME
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1040
+ </div>
+
+ </td><td>
+ <div class="para">
+ STRING_ARRAY
+ </div>
+
+ </td><td>
+ <div class="para">
+ Yes
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_FILEDEVICES
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1095
+ </div>
+
+ </td><td>
+ <div class="para">
+ INT32
+ </div>
+
+ </td><td>
+ <div class="para">
+ Yes
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_FILEINODES
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1096
+ </div>
+
+ </td><td>
+ <div class="para">
+ INT32
+ </div>
+
+ </td><td>
+ <div class="para">
+ Yes
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_FILELANGS
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1097
+ </div>
+
+ </td><td>
+ <div class="para">
+ STRING_ARRAY
+ </div>
+
+ </td><td>
+ <div class="para">
+ Yes
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_DIRINDEXES
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1116
+ </div>
+
+ </td><td>
+ <div class="para">
+ INT32
+ </div>
+
+ </td><td>
+ <div class="para">
+ Optional
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_BASENAMES
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1117
+ </div>
+
+ </td><td>
+ <div class="para">
+ STRING_ARRAY
+ </div>
+
+ </td><td>
+ <div class="para">
+ Optional
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_DIRNAMES
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1118
+ </div>
+
+ </td><td>
+ <div class="para">
+ STRING_ARRAY
+ </div>
+
+ </td><td>
+ <div class="para">
+ Optional
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ The RPMTAG_OLDFILENAMES tag is used when the files are not compressed, when the RPMTAG_REQUIRENAME tag does not indicate rpmlib(CompressedFileNames). The RPMTAG_FILESIZES tag specifies the size of each file in the payload, while the RPMTAG_FILEMODES tag specifies the file modes (permissions) and the RPMTAG_FILEMTIMES tag holds the last modification time for each file.
+ </div><div class="para">
+ The RPMTAG_BASENAMES tag holds an array of the base file names for the files in the payload. The RPMTAG_DIRNAMES tag holds an array of the directories for the files. The RPMTAG_DIRINDEXES tag contains an index into the RPMTAG_DIRNAMES for the directory. Each RPM must have either RPMTAG_OLDFILENAMES or the triple of RPMTAG_BASENAMES, RPMTAG_DIRNAMES, and RPMTAG_DIRINDEXES, but not both.
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id640579" class="title">Dependency Tags</h1></div></div></div><div class="para">
+ The dependency tags provide one of the most useful features of the RPM system by allowing for automated dependency checks between packages. Table D-7 lists these tags.
+ </div><div class="para">
+ Table D-7 Dependency tags
+ </div><div class="informaltable"><table border="1"><colgroup><col width="25%" /><col width="25%" /><col width="25%" /><col width="25%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Constant
+ </div>
+
+ </td><td>
+ <div class="para">
+ Value
+ </div>
+
+ </td><td>
+ <div class="para">
+ Type
+ </div>
+
+ </td><td>
+ <div class="para">
+ Required?
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_PROVIDENAME
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1047
+ </div>
+
+ </td><td>
+ <div class="para">
+ STRING_ARRAY
+ </div>
+
+ </td><td>
+ <div class="para">
+ Yes
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_REQUIREFLAGS
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1048
+ </div>
+
+ </td><td>
+ <div class="para">
+ INT32
+ </div>
+
+ </td><td>
+ <div class="para">
+ Yes
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_REQUIRENAME
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1049
+ </div>
+
+ </td><td>
+ <div class="para">
+ STRING_ARRAY
+ </div>
+
+ </td><td>
+ <div class="para">
+ Yes
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_REQUIREVERSION
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1050
+ </div>
+
+ </td><td>
+ <div class="para">
+ STRING_ARRAY
+ </div>
+
+ </td><td>
+ <div class="para">
+ Yes
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_CONFLICTFLAGS
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1053
+ </div>
+
+ </td><td>
+ <div class="para">
+ INT32
+ </div>
+
+ </td><td>
+ <div class="para">
+ Optional
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_CONFLICTNAME
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1054
+ </div>
+
+ </td><td>
+ <div class="para">
+ STRING_ARRAY
+ </div>
+
+ </td><td>
+ <div class="para">
+ Optional
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_CONFLICTVERSION
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1055
+ </div>
+
+ </td><td>
+ <div class="para">
+ STRING_ARRAY
+ </div>
+
+ </td><td>
+ <div class="para">
+ Optional
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_OBSOLETENAME
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1090
+ </div>
+
+ </td><td>
+ <div class="para">
+ STRING_ARRAY
+ </div>
+
+ </td><td>
+ <div class="para">
+ Optional
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_PROVIDEFLAGS
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1112
+ </div>
+
+ </td><td>
+ <div class="para">
+ INT32
+ </div>
+
+ </td><td>
+ <div class="para">
+ Yes
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_PROVIDEVERSION
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1113
+ </div>
+
+ </td><td>
+ <div class="para">
+ STRING_ARRAY
+ </div>
+
+ </td><td>
+ <div class="para">
+ Yes
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_OBSOLETEFLAGS
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1114
+ </div>
+
+ </td><td>
+ <div class="para">
+ INT32
+ </div>
+
+ </td><td>
+ <div class="para">
+ Optional
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMTAG_OBSOLETEVERSION
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1115
+ </div>
+
+ </td><td>
+ <div class="para">
+ INT32
+ </div>
+
+ </td><td>
+ <div class="para">
+ Optional
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ Each of these tags comes in triples, which are formatted similarly. The RPMTAG_REQUIRENAME tag holds an array of required capabilities. The RPMTAG_REQUIREVERSION tag holds an array of the versions of the required capabilities. The RPMTAG_REQUIREFLAGS tag ties the two together with a set of bit flags that specify whether the requirement is for a version less than the given number, equal to the given number, greater than or equal to the given number, and so on. Table D-8 lists these flags.
+ </div><div class="para">
+ Table D-8 Bit flags for dependencies
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Flag
+ </div>
+
+ </td><td>
+ <div class="para">
+ Value
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMSENSE_LESS
+ </div>
+
+ </td><td>
+ <div class="para">
+ 0x02
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMSENSE_GREATER
+ </div>
+
+ </td><td>
+ <div class="para">
+ 0x04
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMSENSE_EQUAL
+ </div>
+
+ </td><td>
+ <div class="para">
+ 0x08
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMSENSE_PREREQ
+ </div>
+
+ </td><td>
+ <div class="para">
+ 0x40
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMSENSE_INTERP
+ </div>
+
+ </td><td>
+ <div class="para">
+ 0x100
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMSENSE_SCRIPT_PRE
+ </div>
+
+ </td><td>
+ <div class="para">
+ 0x200
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMSENSE_SCRIPT_POST
+ </div>
+
+ </td><td>
+ <div class="para">
+ 0x400
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMSENSE_SCRIPT_PREUN
+ </div>
+
+ </td><td>
+ <div class="para">
+ 0x800
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMSENSE_SCRIPT_POSTUN
+ </div>
+
+ </td><td>
+ <div class="para">
+ 0x1000
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ The RPMTAG_PROVIDENAME, RPMTAG_PROVIDEVERSION, and RPMTAG_PROVIDEFLAGS tags work similarly for the capabilities this package provides. The RPMTAG_CONFLICTNAME, RPMTAG_CONFLICTVERSION, and RPMTAG_CONFLICTFLAGS tags specify the conflicts. The RPMTAG_OBSOLETENAME, RPMTAG_OBSOLETEVERSION, and RPMTAG_OBSOLETEFLAGS tags specify the obsoleted dependencies.
+ </div><div class="para">
+ In addition, an RPM package can define some special requirements in the RPMTAG_REQUIRENAME and RPMTAG_REQUIREVERSION tags. Table D-9 lists these requirements.
+ </div><div class="para">
+ Table D-9 Special package requirement names and versions
+ </div><div class="informaltable"><table border="1"><colgroup><col width="33%" /><col width="33%" /><col width="33%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Name
+ </div>
+
+ </td><td>
+ <div class="para">
+ Version
+ </div>
+
+ </td><td>
+ <div class="para">
+ Specifies
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Lsb
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1.3
+ </div>
+
+ </td><td>
+ <div class="para">
+ The package conforms to the Linux Standards Base RPM format.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpmlib(VersionedDependencies)
+ </div>
+
+ </td><td>
+ <div class="para">
+ 3.0.3-1
+ </div>
+
+ </td><td>
+ <div class="para">
+ The package holds dependencies or prerequisites that have versions associated with them.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpmlib(PayloadFilesHavePrefix)
+ </div>
+
+ </td><td>
+ <div class="para">
+ 4.0-1
+ </div>
+
+ </td><td>
+ <div class="para">
+ File names in the archive have a “.†prepended on the names.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpmlib(CompressedFileNames)
+ </div>
+
+ </td><td>
+ <div class="para">
+ 3.0.4-1
+ </div>
+
+ </td><td>
+ <div class="para">
+ The package uses the RPMTAG_DIRINDEXES, RPMTAG_DIRNAME and RPMTAG_BASENAMES tags for specifying file names.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ /bin/sh
+ </div>
+
+ </td><td>
+ <div class="para">
+ NA
+ </div>
+
+ </td><td>
+ <div class="para">
+ Indicates a requirement for the Bourne shell to run the installation scripts.
+ </div>
+
+ </td></tr></tbody></table></div></div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id800907" class="title">The payload</h1></div></div></div><div class="para">
+ The payload, or archive, section contains the actual files used in the package. These are the files that the rpm command installs when you install the package. To save space, data in the archive section is compressed in GNU gzip format.
+ </div><div class="para">
+ Once uncompressed, the data is in cpio format, which is how the rpm2cpio command can do its work. In cpio format, the payload is made up of records, one per file. Table D-10 lists the record structure.
+ </div><div class="para">
+ Table D-10 cpio file record structure
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Element
+ </div>
+
+ </td><td>
+ <div class="para">
+ Holds
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ cpio header
+ </div>
+
+ </td><td>
+ <div class="para">
+ Information on the file, such as the file mode (permissions)
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ File name
+ </div>
+
+ </td><td>
+ <div class="para">
+ NULL-terminated string
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Padding
+ </div>
+
+ </td><td>
+ <div class="para">
+ 0 to 3 bytes, as needed, to align the next element on a 4-byte boundary
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ File data
+ </div>
+
+ </td><td>
+ <div class="para">
+ The contents of the file
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Padding
+ </div>
+
+ </td><td>
+ <div class="para">
+ 0 to 3 bytes, as needed, to align the next file record on a 4-byte boundary
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ The information in the cpio header duplicates that of the RPM file-information header elements.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-rpm-evolution.html"><strong>Înapoi</strong>Cap. 23. RPM Feature Evolution</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch-online-resources.html"><strong>Înainte</strong>Cap. 25. RPM Resources</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-packaging-guidelines.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-packaging-guidelines.html
new file mode 100644
index 0000000..39b137f
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-packaging-guidelines.html
@@ -0,0 +1,110 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Cap. 13. Packaging Guidelines</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="index.html" title="Ghid RPM" /><link rel="prev" href="ch12s02.html" title="12.2. Summary" /><link rel="next" href="ch13s02.html" title="13.2. Following Good Practices" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch12s02.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch13s02.html"><strong>ÃŽnainte</strong></a></li></ul><div xml:lang="ro" class="
chapter" id="ch-packaging-guidelines" lang="ro"><div class="titlepage"><div><div><h2 class="title">Cap. 13. Packaging Guidelines</h2></div></div></div><div class="toc"><dl><dt><span class="sect1"><a href="ch-packaging-guidelines.html#id699628">13.1. Avoiding Common Problems</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch-packaging-guidelines.html#id629009">13.1.1. Scan the mailing lists</a></span></dt><dt><span class="sect2"><a href="ch-packaging-guidelines.html#id487576">13.1.2. Use rpmbuild</a></span></dt><dt><span class="sect2"><a href="ch-packaging-guidelines.html#id491901">13.1.3. Don’t try to defeat the system</a></span></dt><dt><span class="sect2"><a href="ch-packaging-guidelines.html#id491926">13.1.4. Turn off automatic dependency generation</a></span></dt><dt><span class="sect2"><a href="ch-packaging-guidelines.html#id661809">13.1.5. Don't list directories in %files</a></span></dt><dt><span class="sect2"><a href="ch-packaging-guidelines.html#id563382">1
3.1.6. Handling circular dependencies</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch13s02.html">13.2. Following Good Practices</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch13s02.html#id713208">13.2.1. Preparation</a></span></dt><dt><span class="sect2"><a href="ch13s02s02.html">13.2.2. Building</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch13s03.html">13.3. Summary</a></span></dt></dl></div><div class="para">
+ This chapter covers:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Avoiding common mistakes
+ </div></li><li class="listitem"><div class="para">
+ Following good practices
+ </div></li></ul></div><div class="para">
+ RPM is a complex system that helps manage thousands of packages for a complex operating system. Furthermore, RPM is very, very flexible. This flexibility makes it important that you follow the rules to create packages the proper way. Otherwise, you’ll face a host of problems with your RPMs. Following some best practices guidelines will help you avoid future problems as you release RPM updates.
+ </div><div class="para">
+ This chapter covers ways to avoid common problems as well as best-practice guidelines for creating your own RPMs.
+ </div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id699628" class="title">Avoiding Common Problems</h1></div></div></div><div class="para">
+ Developers creating RPMs seem to hit many of the same roadblocks. This section covers some of the most common problems faced by RPM users and package builders.
+ </div><div class="para">
+ Warning
+ </div><div class="para">
+ Never, never, never build RPMs logged in as the root user. See the section on Building for details.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id629009" class="title">Scan the mailing lists</h1></div></div></div><div class="para">
+ Many people have tried to solve a lot of serious problems that arise when using RPM, so if you are facing difficulties, chances are someone else has tackled those issues before. The RPM mailing list provides a technical forum for discussing RPM issues and problems. In many, if not most, cases, you can find answers to problems by scanning the mailing list archives.
+ </div><div class="para">
+ You can also sign up for the mailing list so that you can send in requests and see the responses.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ For details on viewing the RPM mailing list archives and signing up for the list, see www.rpm.org/mailing_list/. See <a href="http://groups.yahoo.com/group/rpm-list/messages">http://groups.yahoo.com/group/rpm-list/messages</a> for an archive of the list.
+ </div><div class="para">
+ If you are working with RPMs and pushing the envelope for other operating systems or complicated packages, this list is definitely worth a look.
+ </div><div class="para">
+ Before sending any messages, though, be sure to look through the message archives to see if the message has already been answered. You will save time waiting for a response if you can get an archived response right away.
+ </div><div class="para">
+ You should also ask any questions in a way that will generate the most helpful responses. This includes:
+ </div><div class="para">
+ Do your homework first. Check to see if your question has already been answered by looking at the mailing list or newsgroup archives. In the end, this saves you the most time, as you don’t have to wait for answers.
+ </div><div class="para">
+ Describe the problem and the symptoms as clearly as possible. After all, this is what you want help with.
+ </div><div class="para">
+ Use clear subject headers. This is the first part of your message that people will read. If you are not clear, the key people who could answer your questions may never even read your message. And, if they don’t read the message, you will never get an answer.
+ </div><div class="para">
+ Send your message in plain text, not HTML. Do not include a separate HTML copy of your message. This just makes it harder to read, especially for people who read collected digests of mailing lists.
+ </div><div class="para">
+ Make it easy for people to reply to you. Include your email address in your message. You might want to include a line that states something like “Please send your reply to me at†and then provide your email address.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ These tips on asking questions come from the Internet document on How to Ask Questions the Smart Way by Eric Steven Raymond and Rick Moen, available at multiple sites, including www.owlriver.com/tips/smart.
+ </div><div class="para">
+ In addition to the RPM mailing list, there is also a Usenet newsgroup, named linux.redhat.rpm. You can read this newsgroup with any newsreading program.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ Newsgroups are sometimes called discussion groups.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id487576" class="title">Use rpmbuild</h1></div></div></div><div class="para">
+ In older versions of RPM, you called the rpm –ba command to build RPMs. With RPM 4.1, you must use the rpmbuild command. If you have the rpmbuild command available, even if you are running an older version of RPM, run rpmbuild instead of rpm to build your RPMs.
+ </div><div class="para">
+ You’d be surprised at how such a simple item is one of the most-asked questions on the RPM mailing list. That’s because the rpm –ba command, and the other –b options, no longer work in RPM 4.1. These options are supported by the rpmbuild command.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id491901" class="title">Don’t try to defeat the system</h1></div></div></div><div class="para">
+ If you are finding your spec files getting more and more complex, and that you are trying to disable RPM features, chances are you are trying to defeat the system. This is not a good idea.
+ </div><div class="para">
+ The RPM system works in a certain way. You may not always agree with the way it works, but if you try to make it work in contrary ways, in most cases you’ll end up fighting RPM to no avail.
+ </div><div class="para">
+ There are certain rules, and more importantly certain conventions that RPMs should follow. The previous chapters in this section on building RPMs have outlined those conventions. Follow them. When you go against these conventions, you are really trying to defeat how the RPM system works.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id491926" class="title">Turn off automatic dependency generation</h1></div></div></div><div class="para">
+ When you build an RPM, the rpmbuild command will automatically generate dependencies on Linux shared libraries and other system commands. You can turn this off if you need to, using a number of means.
+ </div><div class="para">
+ You can disable the automatic generation of dependencies by placing the following directive in your spec file:
+ </div><div class="para">
+ Autoreq: 0
+ </div><div class="para">
+ A better approach, though, is to override the %{__find_requires} and %{__find_provides} macros, or just one of these as needed. You can null out either of these macros by adding commands like the following to your spec file:
+ </div><div class="para">
+ %define __find_requires %{nil}
+ </div><div class="para">
+ This approach is better because it allows you to override only the requires checks. In addition, you can get more specific and simply change how the automatic dependency checks are performed. For example, you can also change the definitions of these macros to perform normal dependency generation except for any problematic files or packages. These two macros resolve to shell scripts that perform the automated dependency checks, as you can see with the rpm --eval command:
+ </div><div class="para">
+ $ rpm --eval "%__find_provides"
+ </div><div class="para">
+ /usr/lib/rpm/find-provides
+ </div><div class="para">
+ rpm --eval "%__find_requires"
+ </div><div class="para">
+ /usr/lib/rpm/find-requires
+ </div><div class="para">
+ You can override these scripts to filter out any dependencies that cause problems for your packages.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id661809" class="title">Don't list directories in %files</h1></div></div></div><div class="para">
+ Unless you really mean it, don’t list directories in your %files section in your spec files. That is because the rpmbuild program will automatically add all files in that directory to your RPM. If this is a system directory, such as /usr/bin, your RPM has now claimed ownership for all the files, regardless of the source package.
+ </div><div class="para">
+ To avoid all files in the directory becoming part of the package, list the files explicitly, perhaps generating the list of files as the program builds.
+ </div><div class="para">
+ If you do need a directory installed as part of your package, use the %dir directive, described in <a class="xref" href="ch-specfiles.html">Cap. 9, <em>Working with Spec Files</em></a> .
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id563382" class="title">Handling circular dependencies</h1></div></div></div><div class="para">
+ If two packages each depend on the other, you don’t want each package’s spec file to list the other in a Requires section. If this occurs, the packages won’t install without one of the force options, since each package will require the other to be installed first.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ <a class="xref" href="ch-using-rpm.html">Cap. 3, <em>Using RPM</em></a> covers how to install or upgrade packages while ignoring dependency checks. In general, you do not want to ignore these checks.
+ </div><div class="para">
+ You can work around this issue by using the PreReq directive instead of Requires. For example, if package A depends on B and package B depends on A, you can place the following in the package B spec file:
+ </div><div class="para">
+ PreReq: A
+ </div><div class="para">
+ In addition, you can install both packages at the same time to avoid some of the problems with circular dependencies. Simply include both packages on the rpm –Uvh command line.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch12s02.html"><strong>Înapoi</strong>12.2. Summary</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch13s02.html"><strong>Înainte</strong>13.2. Following Good Practices</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-programming-c.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-programming-c.html
new file mode 100644
index 0000000..d5c818a
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-programming-c.html
@@ -0,0 +1,561 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Cap. 15. Programming RPM with C</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="index.html" title="Ghid RPM" /><link rel="prev" href="ch14s08.html" title="14.8. Summary" /><link rel="next" href="ch15s02.html" title="15.2. The Power of popt" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch14s08.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch15s02.html"><strong>ÃŽnainte</strong></a></li></ul><div xml:lang="ro" class="chapter
" id="ch-programming-c" lang="ro"><div class="titlepage"><div><div><h2 class="title">Cap. 15. Programming RPM with C</h2></div></div></div><div class="toc"><dl><dt><span class="sect1"><a href="ch-programming-c.html#id676692">15.1. Programming with the C Library</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch-programming-c.html#id609132">15.1.1. Setting Up a C Programming Environment</a></span></dt><dt><span class="sect2"><a href="ch-programming-c.html#id658946">15.1.2. Setting Up the RPM Programming Environment</a></span></dt><dt><span class="sect2"><a href="ch-programming-c.html#id658982">15.1.3. Using the RPM Library</a></span></dt><dt><span class="sect2"><a href="ch-programming-c.html#id571017">15.1.4. Compiling and Linking RPM Programs</a></span></dt><dt><span class="sect2"><a href="ch-programming-c.html#id786003">15.1.5. Getting information on your RPM environment</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch15s02.html">15.2. The Power of popt<
/a></span></dt><dd><dl><dt><span class="sect2"><a href="ch15s02.html#id839350">15.2.1. Popt aliases</a></span></dt><dt><span class="sect2"><a href="ch15s02s02.html">15.2.2. Programming with popt</a></span></dt><dt><span class="sect2"><a href="ch15s02s03.html">15.2.3. Handling Errors</a></span></dt><dt><span class="sect2"><a href="ch15s02s04.html">15.2.4. Running a popt example</a></span></dt><dt><span class="sect2"><a href="ch15s02s05.html">15.2.5. Handling rpm command-line options</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch15s03.html">15.3. Working with RPM Files</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch15s03.html#id489656">15.3.1. Opening RPM files</a></span></dt><dt><span class="sect2"><a href="ch15s03s02.html">15.3.2. Reading the RPM lead and signature</a></span></dt><dt><span class="sect2"><a href="ch15s03s03.html">15.3.3. Reading header information</a></span></dt><dt><span class="sect2"><a href="ch15s03s04.html">15.3.4. A shortcut to h
eader information</a></span></dt><dt><span class="sect2"><a href="ch15s03s05.html">15.3.5. Closing RPM files</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch15s04.html">15.4. Programming with the RPM Database</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch15s04.html#id745314">15.4.1. Database iterators</a></span></dt><dt><span class="sect2"><a href="ch15s04s02.html">15.4.2. Dependency Sets</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch15s05.html">15.5. Comparing an RPM File to an Installed Package</a></span></dt><dt><span class="sect1"><a href="ch15s06.html">15.6. Where to Go from Here</a></span></dt><dt><span class="sect1"><a href="ch15s07.html">15.7. Summary</a></span></dt></dl></div><div class="para">
+ This chapter covers:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Using the RPM C library
+ </div></li><li class="listitem"><div class="para">
+ Setting up a development environment
+ </div></li><li class="listitem"><div class="para">
+ Programming with the RPM C library
+ </div></li><li class="listitem"><div class="para">
+ The power of <code class="command">popt</code> for command-line argument processing
+ </div></li><li class="listitem"><div class="para">
+ Comparing package files to installed packages
+ </div></li></ul></div><div class="para">
+ The RPM C library allows you to perform all the operations of the rpm command from within your own C or C++ programs.
+ </div><div class="para">
+ The reason is simple: The rpm command was created using the RPM libraries. These same libraries are available for you to use in your own programs.
+ </div><div class="para">
+ The rpm command itself is quick and, for the most part, simple. So, why would you want to write RPM programs?
+ </div><div class="para">
+ There are many reasons, some of which are listed here:
+ </div><div class="para">
+ *Speed: If you need to perform a task on many RPM files such as verifying a large set of files, then performing the task from one program will be a lot faster than launching the rpm command for each file.
+ </div><div class="para">
+ *Custom options: If you need to do something the rpm command doesn't offer, or doesn't make easy, then you may want to write your own program.
+ </div><div class="para">
+ *Convenience: If you need to make many packages quickly, with custom options, your best bet may be to create a program suited for your tasks. Before doing this, though, be sure to look into whether writing a shell script will handle your task adequately. You'll find writing RPM shell scripts goes much faster than writing whole programs.
+ </div><div class="para">
+ *Installation programs: The Windows world has standardized on graphical installation programs such as InstallShield or InstallAnywhere. The RPM system, on the other hand, has focused on automated installation with the rpm command. You can combine the best of both worlds by writing a graphical installation program on top of the RPM system.
+ </div><div class="para">
+ *Integration with environments: You may want to better integrate RPM with a Linux desktop environment such as GNOME or KDE.
+ </div><div class="para">
+ *Working with other languages: This book covers programming RPM with C, the core language for the library, as well as the Python and Perl scripting languages. You can use the RPM library, though, to help bind with other languages such as Tcl, Ruby, or even C# (especially one of the C# implementations for Linux).
+ </div><div class="para">
+ This chapter and the next cover RPM programming. This chapter covers the RPM C programming library, which provides low-level access to RPM functionality. The next chapter covers the RPM Python programming library, which provides a much higher-level of abstraction. If you are attempting to write a complex RPM program, your best bet is to try the Python API first. Even so, there is a lot you can do with the RPM C library.
+ </div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id676692" class="title">Programming with the C Library</h1></div></div></div><div class="para">
+ RPM C programs are C programs that call on functions in the RPM library, often called rpmlib. To use the rpmlib, you need to set up a C programming environment and install the rpm-devel package.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id609132" class="title">Setting Up a C Programming Environment</h1></div></div></div><div class="para">
+ At the very least, you’ll need a C compiler, gcc, and a text editor. The easiest way to get the C compiler is to install the packages grouped under Software Development with the Red Hat package management tool.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ See <a class="xref" href="ch-management-software.html">Cap. 7, <em>RPM Management Software</em></a> for more on the Red Hat package management tool.
+ </div><div class="para">
+ The gcc package requires a number of capabilities. Make sure you install all the necessary packages. Just about every Linux distribution includes gcc and everything you need to develop C programs, so this should not be a problem.
+ </div><div class="para">
+ For text editors, you can use the vi or emacs text editors, or any of a number of graphical editors such as gedit.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ <a class="xref" href="ch-development-tools.html">Cap. 26, <em>Linux Text Editors and Development Tools</em></a> covers Linux text editors and development tools.
+ </div><div class="para">
+ Once you have a C programming environment set up, you next need to get the RPM library for an RPM development environment.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id658946" class="title">Setting Up the RPM Programming Environment</h1></div></div></div><div class="para">
+ To program with the RPM library, you need to install the rpm-devel package. You must have a version of rpm-devel that matches your version of the rpm package. If you have Red Hat Linux, your installation CDs will also have the version of the RPM development package that corresponds to your system.
+ </div><div class="para">
+ Your program should link against the same libraries that are used by the rpm command itself in order to insure compatibility, so make sure that the version of the rpm-devel package matches the rpm package itself. In most cases, the best bet is to use the RPM programs and libraries that come with your version of Linux.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ You can also download the rpm packages from ftp://ftp.rpm.org/pub/rpm/dist/. This site includes versions of the RPM libraries going back to 1996, ancient history in terms of Linux.
+ </div><div class="para">
+ The package you need is rpm-devel. If you installed Red Hat Linux 8.0, the package is rpm-devel-4.1-1.06. This package includes header files, documentation, and libraries.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id658982" class="title">Using the RPM Library</h1></div></div></div><div class="para">
+ All C programs using the RPM library need to include the file rpmlib.h, which defines the core data structures, constants, and functions. One thing you’ll quickly note is that the RPM C library accesses RPM data at a very low level. This is one reason why many developers are moving to Python for their RPM programs, since the Python RPM API presents a higher level of abstraction.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ <a class="xref" href="ch-rpm-programming-python.html">Cap. 16, <em>Programming RPM with Python</em></a> covers programming RPM with Python.
+ </div><div class="para">
+ In addition to rpmlib.h, the header file rpmcli.h defines a high-level API based on the command-line options to the rpm command. (The cli in rpmcli stands for command-line interface.) Table 16-1 lists other important RPM header files that make up the major subsystems of the RPM system.
+ </div><div class="para">
+ Table 16-1 RPM sub-system header files
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ File
+ </div>
+
+ </td><td>
+ <div class="para">
+ Defines
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpmdb.h
+ </div>
+
+ </td><td>
+ <div class="para">
+ RPM database access
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpmio.h
+ </div>
+
+ </td><td>
+ <div class="para">
+ RPM input/output routines
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ popt.h
+ </div>
+
+ </td><td>
+ <div class="para">
+ Command-line option processing
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ In addition, a number of header files define the major data objects in the RPM system and the functions that operate on these data objects. Table 16-2 lists these header files.
+ </div><div class="para">
+ Table 16-2 RPM data object header files
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ File
+ </div>
+
+ </td><td>
+ <div class="para">
+ Defines
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpmts.h
+ </div>
+
+ </td><td>
+ <div class="para">
+ Transaction sets
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpmte.h
+ </div>
+
+ </td><td>
+ <div class="para">
+ Transaction elements (packages)
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpmds.h
+ </div>
+
+ </td><td>
+ <div class="para">
+ Dependency sets
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpmfi.h
+ </div>
+
+ </td><td>
+ <div class="para">
+ File information
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ header.h
+ </div>
+
+ </td><td>
+ <div class="para">
+ Package headers
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ All the RPM include files are located in /usr/include/rpm on most versions of Linux.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ You can use the rpm command and the queries introduced in <a class="xref" href="ch-using-rpm-db.html">Cap. 4, <em>Using the RPM Database</em></a> to determine exactly where the header files are located. Simply execute the following command:
+ </div><div class="para">
+ $ rpm –ql rpm-devel
+ </div><div class="para">
+ Examine the output of this command for include files.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id571017" class="title">Compiling and Linking RPM Programs</h1></div></div></div><div class="para">
+ RPM programs using the rpmlib C API are the same as C programs everywhere. You need to include the proper header files that define the API calls you need, and link with the right set of libraries.
+ </div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id571029" class="title">Include Files</h1></div></div></div><div class="para">
+ The rpm include files are located in /usr/include/rpm, so you should add this directory to the set of directories that the C compiler looks in for include files with the –I command-line option. For example:
+ </div><div class="para">
+ $ gcc –I/usr/include/rpm –c rpm1.c
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ This also means that you can install the rpm header files in other directories as needed, and just change the –I command-line option.
+ </div><div class="para">
+ To help debug problems, you probably want to add the -Wall (output all warnings) and -g (compile with debugging information). For example:
+ </div><div class="para">
+ $ gcc -Wall -g –I/usr/include/rpm –c rpm1.c
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id740766" class="title">Libraries</h1></div></div></div><div class="para">
+ The main rpm library is librpm.a, or a shared version of this same library. To do most anything with RPM programming, you need to link in the following libraries, as listed in Table 16-3.
+ </div><div class="para">
+ Table 16-3 Required rpm libraries
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Library
+ </div>
+
+ </td><td>
+ <div class="para">
+ Usage
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpm
+ </div>
+
+ </td><td>
+ <div class="para">
+ Main RPM library
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpmdb
+ </div>
+
+ </td><td>
+ <div class="para">
+ RPM database library
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpmio
+ </div>
+
+ </td><td>
+ <div class="para">
+ RPM input/output
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ popt
+ </div>
+
+ </td><td>
+ <div class="para">
+ Command-line option parsing library
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ If you are creating RPMs from your C programs, you also need to link in the rpmbuild library. To compile and link a simple RPM program, you need a command like the following:
+ </div><div class="para">
+ gcc -I/usr/include/rpm -o program program.c –lrpmbuild \
+ </div><div class="para">
+ -lrpm -lrpmdb -lrpmio –lpopt
+ </div><div class="para">
+ On some versions of Linux or on other operating systems, you’ll likely need to link a set of helper libraries, as shown following:
+ </div><div class="para">
+ gcc -I/usr/include/rpm -o program program.c –lrpmbuild \
+ </div><div class="para">
+ -lrpm -lrpmdb -lrpmio –lpopt -lelf -lbz2 -lz
+ </div><div class="para">
+ If you have installed the rpm libraries in a non-standard directory, you need to use the –L option to specify where else to look for libraries. For example:
+ </div><div class="para">
+ gcc -I/usr/include/rpm -o program program.c –L/opt/lib/rpm \
+ </div><div class="para">
+ -lrpmbuild -lrpm -lrpmdb -lrpmio –lpopt -lelf -lbz2 -lz
+ </div><div class="para">
+ The -L option tells the cc compiler to look in the /opt/lib/rpm directory as well as in the standard locations such as /usr/lib.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ Starting with RPM 4.2, you should just need to link in the rpm library. The other libraries will get pulled in automatically if needed.
+ </div></div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id786003" class="title">Getting information on your RPM environment</h1></div></div></div><div class="para">
+ A large part of the RPM system lies in system-specific configuration, including the platform you are running on, compatible platforms, and locations of various files. The RPM rc and macro systems support hundreds of options tuned to the specifics of your system, and any customizations you have configured.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ <a class="xref" href="ch-customizing-rpm.html">Cap. 20, <em>Customizing RPM Behavior</em></a> covers customizing RPM.
+ </div><div class="para">
+ Your C programs need to access these RPM system settings to ensure that all data values are properly set up for your system architecture and installation. So, to start an RPM C program, you need to read in all the configuration files. To do this, call rpmReadConfigFiles.
+ </div><div class="para">
+ int rpmReadConfigFiles(const char *files, const char *target);
+ </div><div class="para">
+ The files parameter holds a colon-delimited list of files that make up your system’s configuration. The target parameter holds the target platform. You can pass NULL for both these parameters to use the RPM defaults, which is generally what you want.
+ </div><div class="para">
+ The rpmReadConfigFiles function returns a 0 on success, or –1 on errors.
+ </div><div class="para">
+ Once you have read in the configuration files, you can access values in the configuration, or print it out.
+ </div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id794533" class="title">Printing the Configuration</h1></div></div></div><div class="para">
+ To print out the configuration, call rpmShowRC.
+ </div><div class="para">
+ int rpmShowRC(FILE* output);
+ </div><div class="para">
+ Pass in an output file to print the configuration to, such as stdout. For example:
+ </div><div class="para">
+ rpmShowRC( stdout );
+ </div><div class="para">
+ The rpmShowRC function always returns 0.
+ </div><div class="para">
+ To control some of the output from rpmShowRC, and other RPM library functions, you can set the logging verbosity level by calling rpmSetVerbosity:
+ </div><div class="para">
+ void rpmSetVerbosity(int level);
+ </div><div class="para">
+ For example:
+ </div><div class="para">
+ rpmSetVerbosity(RPMMESS_NORMAL);
+ </div><div class="para">
+ Table 16-4 lists the verbosity levels from rpmio/rpmmessages.h going from least output to more output.
+ </div><div class="para">
+ Table 16-4 Output verbosity levels
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Level
+ </div>
+
+ </td><td>
+ <div class="para">
+ Usage
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMMESS_FATALERROR
+ </div>
+
+ </td><td>
+ <div class="para">
+ Only critical error conditions and above
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMMESS_ERROR
+ </div>
+
+ </td><td>
+ <div class="para">
+ Only error conditions and above
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMMESS_WARNING
+ </div>
+
+ </td><td>
+ <div class="para">
+ Only warning conditions and above
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMMESS_QUIET
+ </div>
+
+ </td><td>
+ <div class="para">
+ Same as RPMMESS_WARNING
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMMESS_NORMAL
+ </div>
+
+ </td><td>
+ <div class="para">
+ Only significant messages
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMMESS_VERBOSE
+ </div>
+
+ </td><td>
+ <div class="para">
+ Verbose informational messages
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMMESS_DEBUG
+ </div>
+
+ </td><td>
+ <div class="para">
+ Debugging messages, and everything above
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ You can put together a simple RPM program such as the one shown in Listing 16-1.
+ </div><div class="para">
+ Listing 16-1: rpm1.c
+ </div><div class="para">
+ /* Show the rpmrc settings. */
+ </div><div class="para">
+ #include <stdio.h>
+ </div><div class="para">
+ #include <stdlib.h>
+ </div><div class="para">
+ </div><div class="para">
+ #include <rpmlib.h>
+ </div><div class="para">
+ </div><div class="para">
+ </div><div class="para">
+ int main(int argc, char * argv[]) {
+ </div><div class="para">
+ </div><div class="para">
+ int status = rpmReadConfigFiles( (const char*) NULL,
+ </div><div class="para">
+ (const char*) NULL);
+ </div><div class="para">
+ </div><div class="para">
+ if (status != 0) {
+ </div><div class="para">
+ printf("Error reading RC files.\n");
+ </div><div class="para">
+ exit(-1);
+ </div><div class="para">
+ } else {
+ </div><div class="para">
+ printf("Read RC OK\n");
+ </div><div class="para">
+ }
+ </div><div class="para">
+ </div><div class="para">
+ rpmSetVerbosity(RPMMESS_NORMAL);
+ </div><div class="para">
+ </div><div class="para">
+ rpmShowRC( stdout );
+ </div><div class="para">
+ </div><div class="para">
+ exit(0);
+ </div><div class="para">
+ }
+ </div><div class="para">
+ Compile this program with a command like the following:
+ </div><div class="para">
+ $ cc -I/usr/include/rpm -o rpm1 rpm1.c -lrpm -lrpmdb -lrpmio –lpopt
+ </div><div class="para">
+ When you run this program, you should see the contents of your configuration printed to the screen.
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id622143" class="title">Expanding the Value of Macros</h1></div></div></div><div class="para">
+ With all the rc and macro configuration files, the RPM system has a lot of values, usually called macros, that you can use to refer to settings. The term macro is used because the values can be more than simple strings. You can have one macro refer to the value of other macros, for example. The basic macro syntax is:
+ </div><div class="para">
+ %name_of_macro
+ </div><div class="para">
+ For example:
+ </div><div class="para">
+ %_target
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ Most of the internal RPM macros start with an underscore, _.
+ </div><div class="para">
+ You can expand a macro with the rpm --eval command:
+ </div><div class="para">
+ $ rpm --eval %_target
+ </div><div class="para">
+ i386-linux
+ </div><div class="para">
+ You can also refer to a macro using the following syntax:
+ </div><div class="para">
+ %{name_of_macro}
+ </div><div class="para">
+ For example:
+ </div><div class="para">
+ %{_target}
+ </div><div class="para">
+ This syntax makes it easier to include a macro in combinations with other text and other macros, since it clearly delineates the macro name.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ <a class="xref" href="ch-customizing-rpm.html">Cap. 20, <em>Customizing RPM Behavior</em></a> covers macros in depth. In your C programs, your code will likely need to expand the value of macros to place data in the proper directories, determine the platform architecture, and so on.
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id628579" class="title">Expanding Macros in Your Code</h1></div></div></div><div class="para">
+ You can use rpmExpand to determine the value of system macros from within your C programs.
+ </div><div class="para">
+ The rpmExpand function can expand the values of one or more macros, returning the expanded value. You can pass a variable number of parameters to rpmExpand, and you must terminate the list with a NULL:
+ </div><div class="para">
+ char* rpmExpand (const char *arg,...);
+ </div><div class="para">
+ You need to free the data returned by rpmExpand by calling free.
+ </div><div class="para">
+ The program in Listing 16-2 takes the first command-line argument to your program (after the program name) and expands that argument as a macro.
+ </div><div class="para">
+ Listing 16-2: rpmexpand.c
+ </div><div class="para">
+ /* Show some macro settings. */
+ </div><div class="para">
+ #include <stdio.h>
+ </div><div class="para">
+ #include <stdlib.h>
+ </div><div class="para">
+ </div><div class="para">
+ #include <rpmlib.h>
+ </div><div class="para">
+ #include <rpmmacro.h>
+ </div><div class="para">
+ </div><div class="para">
+ int main(int argc, char * argv[]) {
+ </div><div class="para">
+ </div><div class="para">
+ int status = rpmReadConfigFiles( (const char*) NULL,
+ </div><div class="para">
+ (const char*) NULL);
+ </div><div class="para">
+ </div><div class="para">
+ if (status != 0) {
+ </div><div class="para">
+ printf("Error reading RC files.\n");
+ </div><div class="para">
+ exit(-1);
+ </div><div class="para">
+ }
+ </div><div class="para">
+ </div><div class="para">
+ char* value = rpmExpand(argv[1], (const char*) NULL);
+ </div><div class="para">
+ </div><div class="para">
+ printf("Value of macro is [%s]\n", value);
+ </div><div class="para">
+ </div><div class="para">
+ exit(0);
+ </div><div class="para">
+ }
+ </div><div class="para">
+ Compile and link this program as shown previously.
+ </div><div class="para">
+ When you run this program, pass the name of a macro to expand. For example:
+ </div><div class="para">
+ $ ./rpmexpand %_target
+ </div><div class="para">
+ Value of macro is [i386-linux]
+ </div><div class="para">
+ You can pass multiple macros together, as shown following:
+ </div><div class="para">
+ $ ./rpmexpand %_builddir/%_target
+ </div><div class="para">
+ Value of macro is [/usr/src/redhat/BUILD/i386-linux]
+ </div><div class="para">
+ You can verify this program with the rpm --eval command, introduced previously:
+ </div><div class="para">
+ $ rpm --eval %_builddir/%_target
+ </div><div class="para">
+ /usr/src/redhat/BUILD/i386-linux
+ </div></div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch14s08.html"><strong>Înapoi</strong>14.8. Summary</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch15s02.html"><strong>Înainte</strong>15.2. The Power of popt</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-programming-perl.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-programming-perl.html
new file mode 100644
index 0000000..e00e69e
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-programming-perl.html
@@ -0,0 +1,50 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Cap. 17. Programming RPM with Perl</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="index.html" title="Ghid RPM" /><link rel="prev" href="ch16s08.html" title="16.8. Summary" /><link rel="next" href="ch17s02.html" title="17.2. Working with RPM Files" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch16s08.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch17s02.html"><strong>ÃŽnainte</strong></a></li></ul><div xml:lang="ro" class="ch
apter" id="ch-programming-perl" lang="ro"><div class="titlepage"><div><div><h2 class="title">Cap. 17. Programming RPM with Perl</h2></div></div></div><div class="toc"><dl><dt><span class="sect1"><a href="ch-programming-perl.html#id747785">17.1. Getting and Using the Perl RPM Modules</a></span></dt><dt><span class="sect1"><a href="ch17s02.html">17.2. Working with RPM Files</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch17s02.html#id675588">17.2.1. Opening package files</a></span></dt><dt><span class="sect2"><a href="ch17s02s02.html">17.2.2. Listing tags from the package</a></span></dt><dt><span class="sect2"><a href="ch17s02s03.html">17.2.3. Convenience methods</a></span></dt><dt><span class="sect2"><a href="ch17s02s04.html">17.2.4. Listing the name and version</a></span></dt><dt><span class="sect2"><a href="ch17s02s05.html">17.2.5. Checking whether the package is a source package</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch17s03.html">17.3. Program
ming with the RPM Database</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch17s03.html#id668276">17.3.1. Opening the database</a></span></dt><dt><span class="sect2"><a href="ch17s03s02.html">17.3.2. Finding packages</a></span></dt><dt><span class="sect2"><a href="ch17s03s03.html">17.3.3. Iterating over packages</a></span></dt><dt><span class="sect2"><a href="ch17s03s04.html">17.3.4. Additional query subroutines</a></span></dt><dt><span class="sect2"><a href="ch17s03s05.html">17.3.5. Getting information on packages</a></span></dt><dt><span class="sect2"><a href="ch17s03s06.html">17.3.6. Comparing versions</a></span></dt><dt><span class="sect2"><a href="ch17s03s07.html">17.3.7. Closing the database</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch17s04.html">17.4. Where to Go from Here</a></span></dt><dt><span class="sect1"><a href="ch17s05.html">17.5. Summary</a></span></dt></dl></div><div class="para">
+ This chapter covers:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Using the RPM2 module to access information on package files
+ </div></li><li class="listitem"><div class="para">
+ Querying the RPM database from Perl
+ </div></li><li class="listitem"><div class="para">
+ Cross-referencing capabilities by the packages that provide and require capabilities
+ </div></li><li class="listitem"><div class="para">
+ Extracting information on packages
+ </div></li></ul></div><div class="para">
+ Perl is one of the most popular scripting languages. Used by system administrators, software developers, and a host of other users, Perl runs on many operating systems including Linux, UNIX, and Windows. Perl stands for Practical Extraction and Report Language, or sometimes Pathologically Eclectic Rubbish Lister.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ In the same vein, LISP stands for Lots of Irritating Single Parenthesis and COBOL for Completely Obnoxious Business Oriented Language.
+ </div><div class="para">
+ I began my book Cross-Platform Perl (John Wiley & Sons, 2000) by mentioning that when I first started learning Perl, I thought it was an evil plot. I still do. But it is a very practical evil plot. You can get a lot of work done with Perl, and quickly.
+ </div><div class="para">
+ Because of a long history of text processing, Perl is especially popular among system administrators. Perl also supports add-on packages, called modules. You can find thousands of add-on modules for text processing, networking, and a plethora of other tasks. There are so many modules available that some people who don’t like the Perl syntax script with Perl anyway, because the available modules save a lot of time.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ See search.cpan.org, the Comprehensive Perl Archive Network, for a listing of many Perl modules.
+ </div><div class="para">
+ This chapter covers working with RPM files and the RPM database using Perl. You can combine RPM usage with other Perl usage, such as generating HTML files or downloading RPMs over a network link.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ Many of the RPM tools covered in <a class="xref" href="ch-management-software.html">Cap. 7, <em>RPM Management Software</em></a> are written in Perl.
+ </div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id747785" class="title">Getting and Using the Perl RPM Modules</h1></div></div></div><div class="para">
+ A number of Perl RPM modules are available. No one module provides all the features you need, although with time, the Perl modules will consolidate into a few modules that most everyone uses. As of this writing, the RPM2 module, by Chip Turner of Red Hat, provides the most recent approach to working with the RPM system from Perl. This chapter covers the RPM2 module.
+ </div><div class="para">
+ Red Hat Linux 8.0 comes with a perl-RPM2 package, which you need to install to use this module. Otherwise, you can download the module from www.cpan.org. Install this module, as well as the perl module, which provides the Perl language interpreter. Once you have this module installed and the perl package installed, you are ready to go.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ The version of the perl-RPM2 package that ships with Red Hat Linux 8.0 has a bug in that it will not open package files that were created with the version of rpm that ships with Red Hat Linux 8.0. That is, the Perl module cannot read package files that ship with Red Hat Linux. You can read older package files, though. This problem only affects attempts to read .rpm files, not installed packages. The bug is related to reading signed packages but not having the GPG keys in the keyring. The latest version on search.cpan.org fixes this problem.
+ </div><div class="para">
+ The RPM2 module contains Perl methods to work on two types of RPM objects: RPM files and installed packages.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch16s08.html"><strong>Înapoi</strong>16.8. Summary</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch17s02.html"><strong>Înainte</strong>17.2. Working with RPM Files</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-rpm-evolution.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-rpm-evolution.html
new file mode 100644
index 0000000..0408b63
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-rpm-evolution.html
@@ -0,0 +1,76 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Cap. 23. RPM Feature Evolution</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="index.html" title="Ghid RPM" /><link rel="prev" href="ch22s05.html" title="22.5. The Change Log" /><link rel="next" href="ch-package-structure.html" title="Cap. 24. RPM Package File Structure" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch22s05.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch-package-structure.html"><strong>ÃŽnainte</strong></
a></li></ul><div xml:lang="ro" class="chapter" id="ch-rpm-evolution" lang="ro"><div class="titlepage"><div><div><h2 class="title">Cap. 23. RPM Feature Evolution</h2></div></div></div><div class="para">
+ Although RPM implementations are largely compatible from version to version, RPM packagers must remember that RPM is a still-evolving program and that its developers are adding features to it with each new version. When producing RPM package files, packagers must keep in mind the audience that will be using the final RPM package files. They must decide which versions of RPM they intend the package to be used with and must use only the lowest common denominator set of features implemented in the oldest of the RPM versions they are targeting. As a quick reference, keep in mind the RPM features noted here and the RPM version in which they are introduced. In considering these revisions of RPM, the main releases of interest are RPM 2.5, RPM 3.0.5, RPM 4.0.4, and RPM 4.1.
+ </div><div class="para">
+ RPM 2.5 is not widely used anymore; packages should target RPM 2.5 only if the intention is for the RPM package to install using absolutely all RPM versions.
+ </div><div class="para">
+ RPM 3.0.5 is the final release of the 3.x series of RPM. It was the release of RPM shipped with Red Hat Linux 6.2 and older releases. It is still in wide use by other vendors as well. Cobalt’s Linux distributions use an RPM implementation version based on RPM 3.0.5, for example. (Red Hat Linux was upgraded to RPM 4 via an errata.)
+ </div><div class="para">
+ RPM 4.0.4 was used with the 7.x releases of Red Hat Linux, and RPM 4.1 first shipped with Red Hat Linux 8.0. Packages produced targeting RPM 3.0.5 should work with nearly all implementations of RPM still in use today. Packages produced targeting RPM 4.0.4 or RPM 4.1 will work only with recent RPM implementations.
+ </div><div class="para">
+ RPM 2.5 is the oldest version of RPM that can, by any stretch of the imagination, still be considered in use. With RPM 2.5, most of the basic RPM features were in place, as well as more advanced functions such as triggers and support for internationalization of Summary:, Description:, and Group: tags in the RPM file header. RPM 2.5 was also the first version of RPM to use the RPM version 3 RPM file format.
+ </div><div class="para">
+ RPM 2.5.3 added support for Epochs to the RPM header, implementing RPMTAG_EPOCH.
+ </div><div class="para">
+ RPM 2.5.4 introduced the %license and %readme file types, which can be used in the RPM spec file to indicate license and README files.
+ </div><div class="para">
+ RPM 2.5.6 added support for usage of the Epoch: keyword in the RPM spec file, allowing you to force an Epoch for your package. The Epoch: keyword replaced the older Serial: keyword, which semantically behaved similarly.
+ </div><div class="para">
+ RPM 2.5.7 enforced the previously implied standard that the "-" character should not be used within the Version or Release fields in the RPM spec file.
+ </div><div class="para">
+ RPM 2.90 introduced support for signing and verifying RPM package files using GPG, the GNU Privacy Guard.
+ </div><div class="para">
+ RPM 2.91 allowed the usage of Provides: directives that defined absolute paths to provided files. Prior to RPM 2.91, Provides: could be used only for listing provided capabilities, not for using statements like Provides: /path/to/file to indicate provided files.
+ </div><div class="para">
+ RPM 3.0.2 permitted usage of multiple Provides: lines for the first time, eliminating the need to combine all provided capabilities and files on the same line in the spec file.
+ </div><div class="para">
+ RPM 3.0.3 added support for versioned dependencies. Prior to RPM 3.0.3, spec files could indicate that a package required another package or provided a specific capability, but they could not indicate the acceptable versions of the required package or which version of the capability the package provided.
+ </div><div class="para">
+ RPM 3.0.4 introduced CompressedFileNames support to RPM. Prior to RPM 3.0.4, RPM packaged the absolute paths of all archived files within the package file. Package file headers contained statements such as
+ </div><div class="para">
+ fileName #0: /usr/bin/ar
+ </div><div class="para">
+ fileName #1: /usr/bin/as
+ </div><div class="para">
+ fileName #2: /usr/bin/gasp
+ </div><div class="para">
+ fileName #3: /usr/bin/gprof
+ </div><div class="para">
+ With CompressedFileNames support, the RPM package file header instead stores the directory name, then just the base name of files within that directory. Package file headers now contain statements such as the following for a given directory with a number of files within that directory:
+ </div><div class="para">
+ dirName #0: /usr/bin
+ </div><div class="para">
+ baseName dirIndex
+ </div><div class="para">
+ #0 ar 0
+ </div><div class="para">
+ #1 as 0
+ </div><div class="para">
+ #2 gasp 0
+ </div><div class="para">
+ #3 gprof 0
+ </div><div class="para">
+ Each file entry now holds the file's base name within the directory, as well as an index number that refers to the directory entry. Since packages typically contain lots of files within the same directory, CompressedFileNames support results in significant memory savings when processing packages for installation.
+ </div><div class="para">
+ RPM 3.0.5 added PayloadIsBzip2 support to RPM, allowing the data payload of RPM package files to be compressed using bzip2 instead of gzip. Even though RPM now supports bzip2 compression of package files, this feature is rarely used in practice, since significantly more memory and time is required to install bzip2-compressed RPM package files than to install gzip-compressed RPM package files. RPM 3.0.5 also added support to RPM for manipulating existing RPM version 4 file format packages; packages produced with RPM 3.0.5 can only be RPM version 3 file format, however.
+ </div><div class="para">
+ RPM 4.0 implemented several significant changes to RPM. RPM 4.0 created package files using RPM version 4 package file format. RPM 4.0 also switched from Berkeley db 1.85 to Berkeley db 3.1 as the database program used for creation and manipulation of the RPM database. The RPM package database file was renamed as well. The db3 package database file is /var/lib/rpm/Packages, and the older db1 package database file was /var/lib/rpm/packages.rpm. Changing the package database file name allowed old and new versions to co-exist if necessary, simplifying upgrades from older RPM releases to the new RPM 4.0 release. RPM 4.0 also introduced the PayloadFilesHavePrefix feature, changing the way archived files are named within the RPM package file. RPM package files contain a cpio archive of files. Prior to RPM 4.0, file names in the cpio archive were stored without a root prefix. With PayloadFilesHavePrefix, all file names within the cpio archive files now have a root prefix, such as
./usr/bin/ar. This modification made it possible for RPM package files to contain the root directory, “./â€. Additional sanity-checking was added to the RPM 4.0 spec file parser; beginning with 4.0, RPM no longer allows dangling symbolic links that contain the BuildRoot. This change eliminates a class of common mistakes made when producing RPMs. Finally, RPM 4.0 implicitly generates Provides: directives; whenever a package header is read, the Provides: directive Provides: %{name} = %{epoch}:%{version}-%{release} is automatically generated, ensuring that all packages explicitly provide themselves as a capability and removing the need to provide self-capabilities within the package spec file.
+ </div><div class="para">
+ RPM 4.0.2 introduced the use of SHA-1 message digests to validate RPM header regions.
+ </div><div class="para">
+ RPM 4.0.3 added the %dev(type,major,minor) spec file directive, allowing creation of device nodes. In addition, the %configure spec file directive now supported --target and –host, simplifying cross compilation when using RPM. The %files directive was extended by adding the %exclude subdirective that could be used to exclude files from inclusion. Finally, RPM 4.0.3 switched back to creating package files in RPM version 3 package file format by default, although it still supports RPM version 4 package file format as well.
+ </div><div class="para">
+ RPM 4.0.4 provided PartialHardlinkSets support. RPM package files are sometimes created which contain multiple copies of the same file, stored as hard links to save space. Prior to RPM 4.0.4, RPM has always treated collections of hard links as an all-or-nothing proposition; all hard links were created, or else none were created. This behavior posed problems when some hard links in a set were tagged with attributes such as %doc or %lang, since rpm commands make it possible to install an RPM package file without installing any files with %doc attributes. Prior to RPM 4.0.4, doing so would break the hard link set, preventing creation of all hard links in the set. PartialHardlinkSet corrects this problem by allowing successful creation of subsets of the hard link set. RPM 4.0.4 also provided automatic generation of Perl module Requires: directives. find-requires now parses all packaged Perl scripts, generating any determined dependencies. In addition, RPM 4.0.4 provides transa
ction support for RPM.
+ </div><div class="para">
+ RPM 4.1 adds separate header DSA and RSA signatures, allowing verification of RPM package headers.
+ </div><div class="para">
+ Finally, when considering the RPM features required by your prepared package, remember that some required RPM features are specified manually within the package spec file, while others are automatically added by RPM during the RPM package file build process. For example, usage of versioned Requires: directives in a spec file will make the resulting RPM package file correctly installable only by RPM release 3.0.3 or later. Similarly, the preparation of any package using RPM release 4.0 or later will automatically produce RPM package files that can only be manipulated by releases of RPM that support the PayloadFilesHavePrefix feature. In the first case, you chose to produce packages that worked with RPM release 3.0.5 or later but not with RPM release 2.5 by including a new directive in the package spec file. In the second case, however, you did not explicitly produce packages that work only with recent RPM releases. The simple fact that you built your RPM package using RPM r
elease 4.0 means that you automatically used features that only RPM 4.0 and later releases understand. These automatic internal requirements are quite common in the later versions; as a result, the best practice is to decide the oldest version of RPM that you wish to support, then to build all packages using that version of RPM, keeping its feature set in mind as you prepare and build the packages.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch22s05.html"><strong>Înapoi</strong>22.5. The Change Log</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch-package-structure.html"><strong>Înainte</strong>Cap. 24. RPM Package File Structure</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-rpm-overview.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-rpm-overview.html
new file mode 100644
index 0000000..023bc37
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-rpm-overview.html
@@ -0,0 +1,72 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Cap. 2. RPM Overview</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="index.html" title="Ghid RPM" /><link rel="prev" href="ch01s04.html" title="1.4. Summary" /><link rel="next" href="ch02s02.html" title="2.2. Querying the RPM Database" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch01s04.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch02s02.html"><strong>ÃŽnainte</strong></a></li></ul><div xml:lang="ro" class="c
hapter" id="ch-rpm-overview" lang="ro"><div class="titlepage"><div><div><h2 class="title">Cap. 2. RPM Overview</h2></div></div></div><div class="toc"><dl><dt><span class="sect1"><a href="ch-rpm-overview.html#id860916">2.1. Understanding the Package File</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch-rpm-overview.html#id580488">2.1.1. RPM file format</a></span></dt><dt><span class="sect2"><a href="ch-rpm-overview.html#id800106">2.1.2. Binary RPMs and Source RPMs</a></span></dt><dt><span class="sect2"><a href="ch-rpm-overview.html#id847399">2.1.3. Source RPMs</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch02s02.html">2.2. Querying the RPM Database</a></span></dt><dt><span class="sect1"><a href="ch02s03.html">2.3. Running RPM Commands</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch02s03.html#id854435">2.3.1. Working with the <code class="command">rpm</code> command</a></span></dt><dt><span class="sect2"><a href="ch02s03s02.html">2.3.2. Other
RPM commands</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch02s04.html">2.4. Summary</a></span></dt></dl></div><div class="para">
+ This chapter covers:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Understanding the package file
+ </div></li><li class="listitem"><div class="para">
+ Querying the RPM database
+ </div></li><li class="listitem"><div class="para">
+ Running RPM commands
+ </div></li></ul></div><div class="para">
+ Working with RPM packages, files, commands, and databases can be complicated. There are thousands of files, for hundreds if not thousands of packages, installed on your system. You need some way to manage it all. The RPM system can help you do that.
+ </div><div class="para">
+ This chapter provides an overview of the components that make up the RPM system for package management: package files, databases, and RPM commands.
+ </div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id860916" class="title">Understanding the Package File</h1></div></div></div><div class="para">
+ RPM provides for installing, upgrading and removing packages. Typically, each package is an application and all the necessary files associated with that application. For example, the Apache Web server comes with a number of configuration files, a large set of documentation files, and the Apache server itself. All of this fits into one RPM package.
+ </div><div class="para">
+ One of the main advantages of the RPM system is that each .rpm file holds a complete package. For example, the following file holds the <code class="filename">mlocate</code> package:
+ </div><div class="para">
+ <code class="filename">mlocate-0.22.2-2.i686.rpm</code>
+ </div><div class="para">
+ Based on the naming conventions discussed in <a class="xref" href="ch-intro-rpm.html">Cap. 1, <em>Introduction to RPM</em></a>, this package represents <code class="filename">mlocate</code> package, version 0.22.2, second build of an RPM package, for i686 (Intel) architecture systems.
+ </div><div class="para">
+ With a single command, you can copy an .rpm file to another Linux system and install it, getting the complete contents of the package, or you can use other commands to remove or update the package.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id580488" class="title">RPM file format</h1></div></div></div><div class="para">
+ RPM files hold a number of tagged data items and a payload, the files to install on your system. The tagged data items describe the package and can contain optional features. For example, the NAME tag holds the package name. The optional PRE tag holds a pre-installation script, a script that the rpm command runs prior to installing the files in the package payload.
+ </div><div class="para">
+ Under the covers, RPM package files contain four sections. The first is a leading identification area that marks the file as an RPM package (created with a particular version of the RPM system). The remaining sections are the signature, the tagged data (called the header), and the payload. Each of these sections has important information about the package, although the payload section contains the actual content of the package.
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term">Signature</span></dt><dd><div class="para">
+ The signature appears after the lead or identifier section, which marks the file as an RPM file. Like your signature when you sign a check, the RPM signature helps verify the integrity of the package. No, the signature doesn’t check for bugs in software applications. Instead, it ensures that you have downloaded a valid RPM archive.
+ </div><div class="para">
+ The signature works by performing a mathematical function on the header and archive sections of the file. The mathematical function can be an encryption process, such as PGP (Pretty Good Privacy), or a message digest in MD5 format.
+ </div></dd><dt class="varlistentry"><span class="term">Header</span></dt><dd><div class="para">
+ The header contains zero or more tagged blocks of data that pertain to the package. The header contains information such as copyright messages, version numbers, and package summaries.
+ </div></dd><dt class="varlistentry"><span class="term">Payload</span></dt><dd><div class="para">
+ The payload section contains the actual files used in the package. These files are installed when you install the package. To save space, data in the payload section is compressed in GNU <code class="command">gzip</code> format.
+ </div></dd></dl></div><div class="para">
+ Once uncompressed, the data is in <code class="command">cpio</code> format, which is how the <code class="command">rpm2cpio</code> command (introduced in the "Other RPM commands" section later in this chapter) can do its work.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id800106" class="title">Binary RPMs and Source RPMs</h1></div></div></div><div class="para">
+ There are two main types of RPM packages: binary (or applications) and source. A binary RPM has been compiled for a particular architecture. For example, the Apache Web server compiled for an Intel Pentium, or i686, architecture won’t work on a Sharp Zaurus, which runs an Intel ARM processor. To run on both systems, you would need two separate packages: one for the Pentium i686 and one for the ARM.
+ </div><div class="para">
+ In addition to binary RPMs, you can get source code RPMs. These RPMs are packages that provide the source code for other packages.
+ </div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id653487" class="title">Binary RPMs</h1></div></div></div><div class="para">
+ Binary RPMs hold complete applications or libraries of functions compiled for a particular architecture. Most binary RPMs contain complete applications, such as the Apache Web server or the AbiWord word processor. These application binary RPMs usually depend on a number of system libraries which are, in turn, also provided by binary RPMs.
+ </div><div class="note"><div class="admonition_header"><h2>Finding More Software</h2></div><div class="admonition"><div class="para">
+ <a class="xref" href="ch-management-software.html">Cap. 7, <em>RPM Management Software</em></a> covers a number of locations where you can find RPM applications galore. Your Linux installation CDs or DVDs are also a great source for applications. Most Linux distributions come with more applications than you can imagine using.
+ </div></div></div><div class="para">
+ Although most binary RPMs are complete applications, others provide libraries. For example, the Simple DirectMedia Layer library (SDL), which provides graphics for many games, can be packaged as an RPM file. A number of programs, mostly games, use this library for enhanced multimedia such as rich graphics. RPMs that provide libraries allow multiple applications to share the same library. Typically, the libraries are packaged into separate RPMs from the applications.
+ </div><div class="para">
+ In addition to binary RPMs that hold applications or libraries compiled for a particular architecture, RPM supports the concept of platform-independent binary RPMs. These platform-independent RPMs, called noarch as a shorted form of “no architecture†dependencies, provide applications or libraries that are not dependent on any platform. Applications written in Perl, Python, or other scripting languages often do not depend on code compiled for a particular architecture. In addition, compiled Java applications are usually free of platform dependencies.
+ </div></div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id847399" class="title">Source RPMs</h1></div></div></div><div class="para">
+ The <code class="filename">mlocate</code> package, mentioned previously, contains the <code class="filename">mlocate</code> application used to search for files on the system. The source code used to create this application is stored in an <code class="filename">mlocate</code> source RPM, for example:
+ </div><div class="para">
+ <code class="filename">mlocate-0.22.2-2.src.rpm</code>
+ </div><div class="para">
+ By convention, source RPMs have a file name ending in .src.rpm.
+ </div><div class="para">
+ Source RPMs should contain all the commands, usually in scripts, necessary to recreate the binary RPM. Having a source RPM means that you can recreate the binary RPM at any time. This is a very important goal of the RPM system.
+ </div><div class="note"><div class="admonition_header"><h2>Source RPMs and Open Source Licencing</h2></div><div class="admonition"><div class="para">
+ Source RPMs have nothing to do with open-source software licenses. Linux is famous for being an open-source operating system. In RPM terms, that means the source code for the Linux kernel and most Linux applications are freely available as source RPMs. But you can also make source RPMs for proprietary programs. The key issue is that you are unlikely to distribute the source RPMs for proprietary packages.
+ </div><div class="para">
+ Furthermore, a number of open-source applications are not available as source RPMs. That's a shame, since source RPMs would make these applications easier to install.
+ </div></div></div><div class="para">
+ While source RPMs hold the commands necessary to create the binary RPM, there may be differences in your Linux environment that would result in rebuilding a binary RPM that is different from the original binary RPM. For example, the compile scripts for some packages may add in optional code depending on which libraries or which versions of libraries are found on your system. <a class="xref" href="ch-packaging-guidelines.html">Cap. 13, <em>Packaging Guidelines</em></a> covers many issues in creating RPMs, and <a class="xref" href="ch-other-linuxes.html">Cap. 18, <em>Using RPM on Non-Red Hat Linuxes</em></a> and <a class="xref" href="ch-other-os.html">Cap. 19, <em>RPM on Other Operating Systems</em></a> cover issues related to other versions of Linux and other operating systems, respectively. If you follow the guidelines when making your own RPMs, you should result in source RPMs that reproduce binary RPMs as consistently as possible.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch01s04.html"><strong>Înapoi</strong>1.4. Summary</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch02s02.html"><strong>Înainte</strong>2.2. Querying the RPM Database</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-rpm-programming-python.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-rpm-programming-python.html
new file mode 100644
index 0000000..53e970b
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-rpm-programming-python.html
@@ -0,0 +1,54 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Cap. 16. Programming RPM with Python</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="index.html" title="Ghid RPM" /><link rel="prev" href="ch15s07.html" title="15.7. Summary" /><link rel="next" href="ch16s02.html" title="16.2. The Python API Hierarchy" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch15s07.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch16s02.html"><strong>ÃŽnainte</strong></a></li></ul><div xml:lang="ro" class="
chapter" id="ch-rpm-programming-python" lang="ro"><div class="titlepage"><div><div><h2 class="title">Cap. 16. Programming RPM with Python</h2></div></div></div><div class="toc"><dl><dt><span class="sect1"><a href="ch-rpm-programming-python.html#id754566">16.1. Setting Up a Python Development Environment</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch-rpm-programming-python.html#id639412">16.1.1. Installing the base Python packages</a></span></dt><dt><span class="sect2"><a href="ch-rpm-programming-python.html#id639641">16.1.2. Using Python for graphics</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch16s02.html">16.2. The Python API Hierarchy</a></span></dt><dt><span class="sect1"><a href="ch16s03.html">16.3. Programming with the RPM Database</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch16s03.html#id821727">16.3.1. Accessing the RPM database</a></span></dt><dt><span class="sect2"><a href="ch16s03s02.html">16.3.2. Querying the RPM database</a
></span></dt><dt><span class="sect2"><a href="ch16s03s03.html">16.3.3. Examining the package header</a></span></dt><dt><span class="sect2"><a href="ch16s03s04.html">16.3.4. Querying for specific packages</a></span></dt><dt><span class="sect2"><a href="ch16s03s05.html">16.3.5. Printing information on packages</a></span></dt><dt><span class="sect2"><a href="ch16s03s06.html">16.3.6. Refining queries</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch16s04.html">16.4. Reading Package Files</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch16s04.html#id662386">16.4.1. Reading headers from package files</a></span></dt><dt><span class="sect2"><a href="ch16s04s02.html">16.4.2. Setting the verification flags</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch16s05.html">16.5. Dependency Comparisons</a></span></dt><dt><span class="sect1"><a href="ch16s06.html">16.6. Installing and Upgrading Packages</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch16
s06.html#id615216">16.6.1. Building up the transaction set</a></span></dt><dt><span class="sect2"><a href="ch16s06s02.html">16.6.2. Transaction elements</a></span></dt><dt><span class="sect2"><a href="ch16s06s03.html">16.6.3. Checking and reordering the transaction elements</a></span></dt><dt><span class="sect2"><a href="ch16s06s04.html">16.6.4. Running the transaction</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch16s07.html">16.7. Where to Go from Here</a></span></dt><dt><span class="sect1"><a href="ch16s08.html">16.8. Summary</a></span></dt></dl></div><div class="para">
+ This chapter covers:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Using the RPM with Python
+ </div></li><li class="listitem"><div class="para">
+ Installing the necessary modules
+ </div></li><li class="listitem"><div class="para">
+ Programming with the RPM database
+ </div></li><li class="listitem"><div class="para">
+ Programming with RPM files
+ </div></li><li class="listitem"><div class="para">
+ Installing packages programmatically
+ </div></li></ul></div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id754566" class="title">Setting Up a Python Development Environment</h1></div></div></div><div class="para">
+ Setting up a Python development environment is much the same as setting up a C programming environment. You need to install a set of packages for general Python development, install a package that provides the Python API to the RPM system, and choose a program for editing your Python scripts.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ <a class="xref" href="ch-development-tools.html">Cap. 26, <em>Linux Text Editors and Development Tools</em></a> covers Linux text editors and development tools.
+ </div><div class="para">
+ If you want to make a graphical user interface in your Python programs, you need to install a separate Python package.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id639412" class="title">Installing the base Python packages</h1></div></div></div><div class="para">
+ The base Python package needed for developing applications is python. For RPM usage, you should install Python 2.2, not Python 1.5. That’s because the RPM bindings for Python are moving to support only 2.2 and higher releases.
+ </div><div class="para">
+ The Python package for RPM access is rpm-python. Install these as you would any other packages.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ <a class="xref" href="ch-using-rpm.html">Cap. 3, <em>Using RPM</em></a> covers installing packages.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id639641" class="title">Using Python for graphics</h1></div></div></div><div class="para">
+ Python supports a number of different toolkits for creating graphical user interfaces. You need one of these toolkits if you want to create Python applications that sport a user interface instead of command-line tools. Among the most popular toolkits are PyGKT, PyQt, and Tkinter.
+ </div><div class="para">
+ *PyGTK is a binding between Python and the GTK+ toolkit used by the GNOME desktop, one of two main desktop environments for Linux. (KDE is the other main desktop environment.) The Red Hat redhat-config-packages program uses PyGTK and sports a very good-looking user interface.
+ </div><div class="para">
+ PyGTK provides full access to the GTK+ widgets such as menus, dialog windows, and buttons. Install the pygtk2 module for PyGTK. For more on PyGTK, see www.daa.com.au/~james/pygtk/.
+ </div><div class="para">
+ *PyQt connects Python scripts to the Qt C++ user interface toolkit. Qt forms the base library used by the KDE desktop environment and KDE applications. As with PyGTK, PyQt allows you to access the rich widget set provided by the library.
+ </div><div class="para">
+ Install the PyQt package for PyQt. For more on PyQt, see www.riverbankcomputing.co.uk/pyqt/.
+ </div><div class="para">
+ *Tkinter is considered a standard part of Python and is based on the Tk (pronounced teekay) toolkit from the Tcl scripting language. The main advantages of Tkinter are that it is considered part of Python, meaning users are more likely to have it, and Tkinter works on multiple platforms, including Windows.
+ </div><div class="para">
+ The main drawback of Tkinter is that the widget sets are not as rich as PyQt or PyGTK. For more on Tkinter, see www.python.org/topics/tkinter/.
+ </div><div class="para">
+ After you’ve set up your environment and installed all the necessary packages, the next step is to start working with the Python API for RPM.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch15s07.html"><strong>Înapoi</strong>15.7. Summary</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch16s02.html"><strong>Înainte</strong>16.2. The Python API Hierarchy</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-rpmbuild.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-rpmbuild.html
new file mode 100644
index 0000000..bee5a9d
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-rpmbuild.html
@@ -0,0 +1,290 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Cap. 11. Controlling the Build with rpmbuild</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="index.html" title="Ghid RPM" /><link rel="prev" href="ch10s07.html" title="10.7. Summary" /><link rel="next" href="ch11s02.html" title="11.2. Building RPMs Without an External Spec File" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch10s07.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch11s02.html"><strong>ÃŽnainte</strong></a></li></ul><div xm
l:lang="ro" class="chapter" id="ch-rpmbuild" lang="ro"><div class="titlepage"><div><div><h2 class="title">Cap. 11. Controlling the Build with <code class="command">rpmbuild</code></h2></div></div></div><div class="toc"><dl><dt><span class="sect1"><a href="ch-rpmbuild.html#id441726">11.1. Building RPMs with the rpmbuild Command</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch-rpmbuild.html#id554393">11.1.1. Customizing the build</a></span></dt><dt><span class="sect2"><a href="ch-rpmbuild.html#id658328">11.1.2. Testing the build</a></span></dt><dt><span class="sect2"><a href="ch-rpmbuild.html#id658349">11.1.3. Debugging the build</a></span></dt><dt><span class="sect2"><a href="ch-rpmbuild.html#id620879">11.1.4. Cleaning up</a></span></dt><dt><span class="sect2"><a href="ch-rpmbuild.html#id617777">11.1.5. Building for other platforms</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch11s02.html">11.2. Building RPMs Without an External Spec File</a></span></dt
><dd><dl><dt><span class="sect2"><a href="ch11s02.html#id558731">11.2.1. Options for working with tar archives</a></span></dt><dt><span class="sect2"><a href="ch11s02s02.html">11.2.2. The expected archive structure</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch11s03.html">11.3. Working with Source RPMs</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch11s03.html#id670165">11.3.1. Rebuilding binary RPMS from source RPMs</a></span></dt><dt><span class="sect2"><a href="ch11s03s02.html">11.3.2. Recompiling binaries from source RPMs</a></span></dt><dt><span class="sect2"><a href="ch11s03s03.html">11.3.3. SRPMS? Finding source RPMs</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch11s04.html">11.4. Signing Built RPMs</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch11s04.html#id580590">11.4.1. Checking that the GPG software is installed</a></span></dt><dt><span class="sect2"><a href="ch11s04s02.html">11.4.2. Configuring a signature</a></spa
n></dt><dt><span class="sect2"><a href="ch11s04s03.html">11.4.3. Signing with the rpmbuild command</a></span></dt><dt><span class="sect2"><a href="ch11s04s04.html">11.4.4. Signing with the rpm command</a></span></dt><dt><span class="sect2"><a href="ch11s04s05.html">11.4.5. Verifying signatures</a></span></dt><dt><span class="sect2"><a href="ch11s04s06.html">11.4.6. Importing public keys</a></span></dt><dt><span class="sect2"><a href="ch11s04s07.html">11.4.7. Getting the Red Hat public key</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch11s05.html">11.5. Summary</a></span></dt></dl></div><div class="para">
+ This chapter covers:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Building with the <code class="command">rpmbuild</code> command
+ </div></li><li class="listitem"><div class="para">
+ Building RPMs without an external spec file
+ </div></li><li class="listitem"><div class="para">
+ Working with source RPMs
+ </div></li><li class="listitem"><div class="para">
+ Optimizing builds
+ </div></li><li class="listitem"><div class="para">
+ Signing built RPMs
+ </div></li></ul></div><div class="para">
+ The preceding chapters in this Part cover details on how to put together RPMs. This chapter rounds out the discussion by delving into more details on the rpmbuild command.
+ </div><div class="para">
+ You can customize how rpmbuild creates RPMs, and you can use RPM commands to test and debug your package.
+ </div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id441726" class="title">Building RPMs with the rpmbuild Command</h1></div></div></div><div class="para">
+ The rpmbuild command provides a workhorse command for building RPMs in all sorts of ways. The basic syntax, as shown in <a class="xref" href="ch-creating-rpms.html">Cap. 8, <em>Creating RPMs: An Overview</em></a>, is:
+ </div><div class="para">
+ rpmbuild -bBuildStage spec_file
+ </div><div class="para">
+ The BuildStage is a letter, such as c, to prepare and compile the application, executing through the %build section, or i, to execute through the %install section. This allows you a good deal of flexibility for building the entire RPM or stopping at some point prior to a full build.
+ </div><div class="para">
+ There’s more to the rpmbuild command, though. Quite a few additional options allow you to further customize the build.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ As mentioned in <a class="xref" href="ch-creating-rpms.html">Cap. 8, <em>Creating RPMs: An Overview</em></a> , previous versions of the RPM system used the rpm command with a -b, for build, option. This option is no longer supported. Use the rpmbuild command to build RPMs.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id554393" class="title">Customizing the build</h1></div></div></div><div class="para">
+ You can customize the rpmbuild command with the options listed in Table 12-1.
+ </div><div class="para">
+ Table 12-1 Extra build options for the rpmbuild command
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Option
+ </div>
+
+ </td><td>
+ <div class="para">
+ Usage
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --buildroot directory
+ </div>
+
+ </td><td>
+ <div class="para">
+ Override the default root directory for building with directory, generally not very useful since most packages already name a buildroot
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --clean
+ </div>
+
+ </td><td>
+ <div class="para">
+ Remove the build tree after building
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nobuild
+ </div>
+
+ </td><td>
+ <div class="para">
+ Just test the spec file and do not run the build
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --rmsource
+ </div>
+
+ </td><td>
+ <div class="para">
+ Remove the sources after the build
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --rmspec
+ </div>
+
+ </td><td>
+ <div class="para">
+ Remove the spec file after the build
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --short-circuit
+ </div>
+
+ </td><td>
+ <div class="para">
+ With the -bc or -bi options, jump directly to the given stage and resume the build from that stage
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --sign
+ </div>
+
+ </td><td>
+ <div class="para">
+ Sign the package with a GPG signature
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --target platform
+ </div>
+
+ </td><td>
+ <div class="para">
+ Build for the given platform. May not work if you don't have the other platform build commands, such as cross compilers, set up. Can work for Intel platforms with i386, i686, and so on.
+ </div>
+
+ </td></tr></tbody></table></div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id658328" class="title">Testing the build</h1></div></div></div><div class="para">
+ One of the most useful options is --nobuild, which tells the rpmbuild command to not build anything. This may seem silly, but the --nobuild option is very useful for testing whether your RPMs can be built. With the --nobuild option, the rpmbuild command parses the spec file and checks for errors, but does not run any of the build stages.
+ </div><div class="para">
+ The --buildroot allows you to specify a different top-level directory for building, overriding the BuildRoot tag in the spec file. This means you can build in a separate location, which is helpful in case there are mistakes. Using a separate directory means the build won’t get mixed with anything else in the build root directory.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id658349" class="title">Debugging the build</h1></div></div></div><div class="para">
+ The --short-circuit option tells the rpmbuild command to restart at a particular location in the build. Rather than working its way through all the steps up to the build stage you ask for, the --short-circuit option allows the rpmbuild command to restart just at the step you ask for.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ This works with the -bc and -bi options only, as well as the -tc and -ti options covered later in this chapter.
+ </div><div class="para">
+ For example, if you run the rpmbuild -bc command to stop after the %build section, you can use the --short-circuit option to restart the build at the %build section. If you found a problem in the %build section and corrected it, you can quickly get going again by restarting the build at the %build section rather than extracting all the sources yet again.
+ </div><div class="para">
+ This option is most useful when you are compiling a package, hit an error, and fix that error. Without the --short-circuit option, you’ll likely end up spending a lot of time recompiling the code you have already compiled.
+ </div><div class="para">
+ During normal development of an RPM package, you will likely execute each build section, one at a time, stop, fix any errors and restart where you left off. You’ll go through this cycle a number of times before the RPM finally builds right.
+ </div><div class="para">
+ Warning
+ </div><div class="para">
+ Never distribute an RPM made with the --short-circuit option. Instead, once you have everything working, start from scratch and rebuild the RPM. This is to avoid any problems with a partially-created RPM.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id620879" class="title">Cleaning up</h1></div></div></div><div class="para">
+ The --clean option tells the rpmbuild command to remove the build tree when complete. This helps ensure that the next time you run the rpmbuild command, you are starting from a known situation.
+ </div><div class="para">
+ For example:
+ </div><div class="para">
+ $ rpmbuild --clean /usr/src/redhat/SPECS/jikes.spec
+ </div><div class="para">
+ Executing(--clean): /bin/sh -e /var/tmp/rpm-tmp.98247
+ </div><div class="para">
+ + umask 022
+ </div><div class="para">
+ + cd /usr/src/redhat/BUILD
+ </div><div class="para">
+ + rm -rf jikes-1.17
+ </div><div class="para">
+ + exit 0
+ </div><div class="para">
+ You can use the --clean option alone, as shown previously, or in concert with another option such as -bi to build and install a binary RPM. In the latter case, the rpmbuild command will clean the built files after the rest of the command finishes.
+ </div><div class="para">
+ Similarly, the --rmsource option tells the rpmbuild command to remove the sources after completing the command. You can call this option with another option, such as -bi for building and installing a binary RPM (and then removing the sources), or alone on the command line to remove the sources only.
+ </div><div class="para">
+ For example:
+ </div><div class="para">
+ rpmbuild --rmsource jikes.spec
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ The abbreviation rm is short for remove. It comes from the Linux rm command, used for removing files.
+ </div><div class="para">
+ The --rmspec option tells the rpmbuild command to remove the spec file when done with the command. As with the --rmsource option, you can use the --rmspec option in conjunction with another rpmbuild option or on its own to just remove the spec file.
+ </div><div class="para">
+ For example:
+ </div><div class="para">
+ rpmbuild --rmspec jikes.spec
+ </div><div class="para">
+ Warning
+ </div><div class="para">
+ The file you are removing with this command is the spec file you are passing to the command. Be careful, because you cannot undo this operation and you have now lost your spec file, except inside your source package.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id617777" class="title">Building for other platforms</h1></div></div></div><div class="para">
+ The --target option tells the rpmbuild command to build a package for another platform. You need to pass the name of the platform. For example:
+ </div><div class="para">
+ rpmbuild -bi --target i486-redhat-linux
+ </div><div class="para">
+ The basic format is:
+ </div><div class="para">
+ cpu-vendor-os
+ </div><div class="para">
+ For example, i686-redhat-linux specifies a 686 CPU with Red Hat Linux. Other CPUs include ppc for PowerPC and sparc for Sun SPARC.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ The --target option sets the target architecture at build time. <a class="xref" href="ch-using-rpm.html">Cap. 3, <em>Using RPM</em></a> covers how you can use the --ignoreos and --ignorearch options when installing RPMs to ignore the operating system and architecture that is flagged within the RPM. Of course, this works only if you are installing on a compatible architecture.
+ </div><div class="para">
+ On the surface level, the --target option overrides some of the macros in the spec file, %_target, %_target_arch, and %_target_os. This flags the RPM for the new target platform.
+ </div><div class="para">
+ Under the covers, setting the architecture macros is not enough. You really cannot create a PowerPC executable, for example, on an Intel-architecture machine, unless you have a PowerPC cross compiler, a compiler that can make PowerPC executables.
+ </div><div class="para">
+ Warning
+ </div><div class="para">
+ Set the target with care. Make sure you can really build executable programs for that architecture.
+ </div><div class="para">
+ If you try to compile a system that uses the GNU configure system to configure the build, your target will likely be ignored. For example, if you try to build the aforementioned jikes package with a target of ppc-ibm-aix, to specify IBM’s UNIX, called AIX, on a PowerPC architecture, you will see the target ignored as the configure system detects that it's running on Linux on an i686 architecture.
+ </div><div class="para">
+ For example:
+ </div><div class="para">
+ $ rpmbuild -bc --target ppc-ibm-aix /usr/src/redhat/SPECS/jikes.spec
+ </div><div class="para">
+ Building target platforms: ppc-ibm-aix
+ </div><div class="para">
+ Building for target ppc-ibm-aix
+ </div><div class="para">
+ Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.94955
+ </div><div class="para">
+ + umask 022
+ </div><div class="para">
+ + cd /usr/src/redhat/BUILD
+ </div><div class="para">
+ + LANG=C
+ </div><div class="para">
+ + export LANG
+ </div><div class="para">
+ + cd /usr/src/redhat/BUILD
+ </div><div class="para">
+ + rm -rf jikes-1.17
+ </div><div class="para">
+ + /usr/bin/gzip -dc /usr/src/redhat/SOURCES/jikes-1.17.tar.gz
+ </div><div class="para">
+ + tar -xf -
+ </div><div class="para">
+ + STATUS=0
+ </div><div class="para">
+ + '[' 0 -ne 0 ']'
+ </div><div class="para">
+ + cd jikes-1.17
+ </div><div class="para">
+ ++ /usr/bin/id -u
+ </div><div class="para">
+ + '[' 500 = 0 ']'
+ </div><div class="para">
+ ++ /usr/bin/id -u
+ </div><div class="para">
+ + '[' 500 = 0 ']'
+ </div><div class="para">
+ + /bin/chmod -Rf a+rX,g-w,o-w .
+ </div><div class="para">
+ + exit 0
+ </div><div class="para">
+ Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.15710
+ </div><div class="para">
+ + umask 022
+ </div><div class="para">
+ + cd /usr/src/redhat/BUILD
+ </div><div class="para">
+ + cd jikes-1.17
+ </div><div class="para">
+ + LANG=C
+ </div><div class="para">
+ + export LANG
+ </div><div class="para">
+ + ./configure CXXFLAGS=-O3 --prefix=/tmp/jikesrpm/usr
+ </div><div class="para">
+ checking for a BSD-compatible install... /usr/bin/install -c
+ </div><div class="para">
+ checking whether build environment is sane... yes
+ </div><div class="para">
+ checking for gawk... gawk
+ </div><div class="para">
+ checking whether make sets ${MAKE}... yes
+ </div><div class="para">
+ checking whether to enable maintainer-specific portions of Makefiles... no
+ </div><div class="para">
+ checking build system type... i686-pc-linux-gnu
+ </div><div class="para">
+ checking host system type... i686-pc-linux-gnu
+ </div><div class="para">
+ checking for g++... g++
+ </div><div class="para">
+ As you can see, the command starts out with the target as the platform, but the configure script soon overrides that, as shown at the end of the truncated output.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch10s07.html"><strong>Înapoi</strong>10.7. Summary</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch11s02.html"><strong>Înainte</strong>11.2. Building RPMs Without an External Spec File</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-scripting.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-scripting.html
new file mode 100644
index 0000000..c51fe17
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-scripting.html
@@ -0,0 +1,36 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Cap. 14. Automating RPM with Scripts</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="index.html" title="Ghid RPM" /><link rel="prev" href="ch13s03.html" title="13.3. Summary" /><link rel="next" href="ch14s02.html" title="14.2. Distinguishing Scripting Languages from Programming Languages" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch13s03.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch14s02.html"><strong>ÃŽnainte</strong></a
></li></ul><div xml:lang="ro" class="chapter" id="ch-scripting" lang="ro"><div class="titlepage"><div><div><h2 class="title">Cap. 14. Automating RPM with Scripts</h2></div></div></div><div class="toc"><dl><dt><span class="sect1"><a href="ch-scripting.html#id642750">14.1. Scripting</a></span></dt><dt><span class="sect1"><a href="ch14s02.html">14.2. Distinguishing Scripting Languages from Programming Languages</a></span></dt><dt><span class="sect1"><a href="ch14s03.html">14.3. Deciding When to Program and When to Script</a></span></dt><dt><span class="sect1"><a href="ch14s04.html">14.4. Shell Scripting Basics</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch14s04.html#id698724">14.4.1. Writing a script</a></span></dt><dt><span class="sect2"><a href="ch14s04s02.html">14.4.2. Running a script</a></span></dt><dt><span class="sect2"><a href="ch14s04s03.html">14.4.3. Problems running scripts</a></span></dt><dt><span class="sect2"><a href="ch14s04s04.html">14.4.4. Turning a
script into a command</a></span></dt><dt><span class="sect2"><a href="ch14s04s05.html">14.4.5. Passing command-line options to your script</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch14s05.html">14.5. Examining RPM Files</a></span></dt><dt><span class="sect1"><a href="ch14s06.html">14.6. Querying the RPM Database</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch14s06.html#id793185">14.6.1. Querying for all packages installed at the same time</a></span></dt><dt><span class="sect2"><a href="ch14s06s02.html">14.6.2. Reading HTML documentation for a package</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch14s07.html">14.7. Where to Go From Here</a></span></dt><dt><span class="sect1"><a href="ch14s08.html">14.8. Summary</a></span></dt></dl></div><div class="para">
+ This chapter covers:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Deciding when to program and when to script
+ </div></li><li class="listitem"><div class="para">
+ Examining RPM files with scripts
+ </div></li><li class="listitem"><div class="para">
+ Querying the RPM database with scripts
+ </div></li></ul></div><div class="para">
+ The rpm command provides a very high-level view of package management. Most of the operations you need to perform require only a single invocation. Some of the command-line options to the rpm command tend to get very complex, however, especially for detailed queries. That’s where scripting can help.
+ </div><div class="para">
+ This chapter covers scripting, specifically shell scripting, with the rpm command, especially for newcomers to Linux scripting
+ </div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id642750" class="title">Scripting</h1></div></div></div><div class="para">
+ Scripting allows you to quickly write new commands in a language, called a scripting language, that can help automate your work. Used heavily by system administrators and lightly by software developers, scripts can help remove some of the tedium from your day-to-day tasks. Scripts can also hold the complex query formats used with the rpm command so you don’t have to remember them.
+ </div><div class="para">
+ Scripts start out as text files. These text files hold commands in the scripting language. Most of these script file commands run commands installed on your system, such as rpm. To run a script, invoke a command, called an interpreter, that reads in the script file and executes the commands inside the script.
+ </div><div class="para">
+ Programming is usually considered different from scripting, even though there are many similarities. Programs start out as text files. These text files hold commands in the programming language and sometimes, not often, calls to commands installed on your system. Programs generally involve more work than scripts and are generally larger, containing more commands.
+ </div><div class="para">
+ Furthermore, most programs need to be compiled. A separate command parses the program text files and generates some form of machine code. Multiple pieces of a program may be linked together to form a command you can call from your shell prompt.
+ </div><div class="para">
+ Some programming languages, such as Java or C#, are compiled to a generic bytecode format. A compiled Java program, for example, is the same no matter what the architecture. To run such a program, you need a runtime engine such as the java command provides. (Runtime engine is a fancy term for interpreter.)
+ </div><div class="para">
+ Such differences between scripting and programming sometimes get in the way of performing real work. For example, I once worked with a group of people who were convinced that they were not programmers. They felt that programming was an art that was far beyond them. Yet, they wrote hundreds of kilobytes of scripts to create a sophisticated graphical interface for a Computer-Aided Design system. In my mind, they were programming (and doing quite well at it). In their minds, though, there was a clear distinction between scripting at mdwhat they could do at mdand programming, which was beyond them, they thought.
+ </div><div class="para">
+ Don’t get caught up in this. Use the right tool for the job.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch13s03.html"><strong>Înapoi</strong>13.3. Summary</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch14s02.html"><strong>Înainte</strong>14.2. Distinguishing Scripting Languages from Pro...</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-specfile-syntax.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-specfile-syntax.html
new file mode 100644
index 0000000..803557b
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-specfile-syntax.html
@@ -0,0 +1,164 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Cap. 22. Spec File Syntax</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="index.html" title="Ghid RPM" /><link rel="prev" href="ch21s02s04.html" title="21.2.4. Customizing the build" /><link rel="next" href="ch22s02.html" title="22.2. Macros" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch21s02s04.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch22s02.html"><strong>ÃŽnainte</strong></a></li></ul><div xml:lang="ro" cla
ss="chapter" id="ch-specfile-syntax" lang="ro"><div class="titlepage"><div><div><h2 class="title">Cap. 22. Spec File Syntax</h2></div></div></div><div class="toc"><dl><dt><span class="sect1"><a href="ch-specfile-syntax.html#id654084">22.1. Package Information Tags</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch-specfile-syntax.html#id722547">22.1.1. Comments</a></span></dt><dt><span class="sect2"><a href="ch-specfile-syntax.html#id857248">22.1.2. Build settings</a></span></dt><dt><span class="sect2"><a href="ch-specfile-syntax.html#id857280">22.1.3. Dependency tags</a></span></dt><dt><span class="sect2"><a href="ch-specfile-syntax.html#id699217">22.1.4. Source files</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch22s02.html">22.2. Macros</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch22s02.html#id653606">22.2.1. Variable definition macros</a></span></dt><dt><span class="sect2"><a href="ch22s02s02.html">22.2.2. Conditional macros</a></span></
dt><dt><span class="sect2"><a href="ch22s02s03.html">22.2.3. Built-in macros</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch22s03.html">22.3. Build Sections</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch22s03.html#id641190">22.3.1. Build preparation</a></span></dt><dt><span class="sect2"><a href="ch22s03s02.html">22.3.2. Build</a></span></dt><dt><span class="sect2"><a href="ch22s03s03.html">22.3.3. Installation</a></span></dt><dt><span class="sect2"><a href="ch22s03s04.html">22.3.4. Clean up</a></span></dt><dt><span class="sect2"><a href="ch22s03s05.html">22.3.5. Install and uninstall scripts</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch22s04.html">22.4. File Tags</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch22s04.html#id786867">22.4.1. Making relocatable packages</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch22s05.html">22.5. The Change Log</a></span></dt></dl></div><div class="para">
+ This appendix covers:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ The package information tags
+ </div></li><li class="listitem"><div class="para">
+ Build sections
+ </div></li></ul></div><div class="para">
+ The RPM spec file is divided into two main parts: the package information tags, such as the name of the package, and the build sections, such as the commands to compile the software.
+ </div><div class="para">
+ The following sections summarize the spec file syntax.
+ </div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id654084" class="title">Package Information Tags</h1></div></div></div><div class="para">
+ The package information tags contain most of the header tags that you can query with the rpm command. First and foremost, this includes a name.
+ </div><div class="para">
+ The name-epoch-version-release tags, which form the NEVR used to identify packages, should all appear in your spec file, although you can skip the Epoch tag.
+ </div><div class="para">
+ Name: name
+ </div><div class="para">
+ # Epoch: 1
+ </div><div class="para">
+ Version: version_number
+ </div><div class="para">
+ Release: package_release_number
+ </div><div class="para">
+ The optional Epoch tag provides an ordering for the version numbers (replacing the deprecated Serial tag). Use this tag if RPM cannot figure out the ordering of which release comes after another.
+ </div><div class="para">
+ Epoch: 42
+ </div><div class="para">
+ A number of tags allow you to define who made the package and under what conditions has the package been released:
+ </div><div class="para">
+ Vendor: name_of_vendor
+ </div><div class="para">
+ URL: URL_to_package_home
+ </div><div class="para">
+ Copyright: package_copyright_message
+ </div><div class="para">
+ Distribution: Linux_or_product_distribution
+ </div><div class="para">
+ Packager: John Q. Smith <john.smith at somecompany.yow>
+ </div><div class="para">
+ Group: group_for_categorizing_package
+ </div><div class="para">
+ Use the Group tag to help users categorize your package.
+ </div><div class="para">
+ The Icon tag allows you to provide a desktop icon for the package:
+ </div><div class="para">
+ Icon: filename.xpm
+ </div><div class="para">
+ A one-line summary is essential to tell users what your package is for:
+ </div><div class="para">
+ Summary: one_line_description_of_package
+ </div><div class="para">
+ You should also include a longer description section, marked by %description:
+ </div><div class="para">
+ %description
+ </div><div class="para">
+ Tcsh is an enhanced but completely compatible version of csh, the C
+ </div><div class="para">
+ shell. Tcsh is a command language interpreter which can be used both
+ </div><div class="para">
+ as an interactive login shell and as a shell script command processor.
+ </div><div class="para">
+ Tcsh includes a command line editor, programmable word completion,
+ </div><div class="para">
+ spelling correction, a history mechanism, job control and a C language
+ </div><div class="para">
+ like syntax.
+ </div><div class="para">
+ In the description section, blank lines indicate paragraphs. Lines that start with a space are not formatted.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id722547" class="title">Comments</h1></div></div></div><div class="para">
+ To help document your work, you can include comments (to yourself and others reading the spec file). Any line starting with a hash character, #, holds a comment. RPM will ignore comments.
+ </div><div class="para">
+ # This is a comment.
+ </div><div class="para">
+ In spec files, comments are used mostly to help explain your syntax choices to yourself should you view the spec file later.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ Avoid percent signs, %, in comments, which may get interpreted as RPM macros. See <a class="xref" href="ch-specfiles.html">Cap. 9, <em>Working with Spec Files</em></a> for details.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id857248" class="title">Build settings</h1></div></div></div><div class="para">
+ The BuildArchitectures tag names the architectures that a binary RPM will run on. See <a class="xref" href="ch-customizing-rpm.html">Cap. 20, <em>Customizing RPM Behavior</em></a> for a description of the architecture settings. A special value of noarch indicates a package that is not dependent on a particular architecture, such as a Perl or Python script.
+ </div><div class="para">
+ The BuildPreReq tag lists any prerequisites for building. For example:
+ </div><div class="para">
+ BuildPreReq: ncurses-devel
+ </div><div class="para">
+ The Buildroot tag names the temporary directory in which to build the package. For example:
+ </div><div class="para">
+ Buildroot: %{_tmppath}/%{name}-root
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id857280" class="title">Dependency tags</h1></div></div></div><div class="para">
+ Dependency tags define all the dependencies for the package, as described in <a class="xref" href="ch-dependencies.html">Cap. 5, <em>Package Dependencies</em></a> .
+ </div><div class="para">
+ For each dependency, you can specify a capability name alone. For example:
+ </div><div class="para">
+ Provides: capability_name
+ </div><div class="para">
+ You can also provide a particular version number or indicate that your package has a dependency on a version larger or smaller than a given number. For example:
+ </div><div class="para">
+ Requires: capability_name >= version_number
+ </div><div class="para">
+ Requires: capability_name <= version_number
+ </div><div class="para">
+ Requires: capability_name > version_number
+ </div><div class="para">
+ Requires: capability_name < version_number
+ </div><div class="para">
+ Requires: capability_name == version_number
+ </div><div class="para">
+ Requires: capability_name = version_number
+ </div><div class="para">
+ The == and = act the same for dependencies. Both check for a version equal to the given number. You can provide multiple items, separated by commas. For example:
+ </div><div class="para">
+ Requires: python >= 1.3, perl
+ </div><div class="para">
+ For add-on modules for interpreters, especially Perl, you can use the following syntax to define capabilities:
+ </div><div class="para">
+ Provides: perl(MIME-Base64)
+ </div><div class="para">
+ This example provides the MIME-Base64 add-on Perl module.
+ </div><div class="para">
+ You can also use or to specify more than one possibility. For example:
+ </div><div class="para">
+ perl(IO-Wrap) == 4.5 or perl(IO-Wrap)-4.5
+ </div><div class="para">
+ The Provides, Requires, Obsoletes, and Conflicts dependency tags all work the same for capability names and version numbers.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ You can also specify BuildRequires tags for capabilities necessary to build the package, not to install it. A BuildConflicts tag names capabilities that conflict for building, such as a particular version of the gcc C compiler.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id699217" class="title">Source files</h1></div></div></div><div class="para">
+ The source and patch tags identify the source files used to build the binary package. The patch tags identify any patches used to modify the sources.
+ </div><div class="para">
+ If you have more than one of a particular kind of tag, append a number. For example:
+ </div><div class="para">
+ Source0: ftp://ftp.uk.linux.org/pub/linux/telnet-%{telnet_version}.tar.gz
+ </div><div class="para">
+ Source2: telnet-client.tar.gz
+ </div><div class="para">
+ Source3: telnet-xinetd
+ </div><div class="para">
+ Source4: telnet.wmconfig
+ </div><div class="para">
+ Patch1: telnet-client-cvs.patch
+ </div><div class="para">
+ Patch5: telnetd-0.17.diff
+ </div><div class="para">
+ Patch6: telnet-0.17-env.patch
+ </div><div class="para">
+ Patch7: telnet-0.17-issue.patch
+ </div><div class="para">
+ Patch8: telnet-0.17-sa-01-49.patch
+ </div><div class="para">
+ Patch9: telnet-0.17-env-5x.patch
+ </div><div class="para">
+ Patch10: telnet-0.17-pek.patch
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch21s02s04.html"><strong>Înapoi</strong>21.2.4. Customizing the build</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch22s02.html"><strong>Înainte</strong>22.2. Macros</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-specfiles.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-specfiles.html
new file mode 100644
index 0000000..10f272e
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-specfiles.html
@@ -0,0 +1,42 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Cap. 9. Working with Spec Files</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="index.html" title="Ghid RPM" /><link rel="prev" href="ch08s04.html" title="8.4. Summary" /><link rel="next" href="ch09s02.html" title="9.2. Writing Spec Files" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch08s04.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch09s02.html"><strong>ÃŽnainte</strong></a></li></ul><div xml:lang="ro" class="chapter"
id="ch-specfiles" lang="ro"><div class="titlepage"><div><div><h2 class="title">Cap. 9. Working with Spec Files</h2></div></div></div><div class="toc"><dl><dt><span class="sect1"><a href="ch-specfiles.html#id638671">9.1. Reading Spec Files</a></span></dt><dt><span class="sect1"><a href="ch09s02.html">9.2. Writing Spec Files</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch09s02.html#id686530">9.2.1. Comments</a></span></dt><dt><span class="sect2"><a href="ch09s02s02.html">9.2.2. Storing spec files on disk</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch09s03.html">9.3. Defining Package Information</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch09s03.html#id562505">9.3.1. Describing the package</a></span></dt><dt><span class="sect2"><a href="ch09s03s02.html">9.3.2. Setting build locations</a></span></dt><dt><span class="sect2"><a href="ch09s03s03.html">9.3.3. Naming source files</a></span></dt><dt><span class="sect2"><a href="ch09s03s04.html">9
.3.4. Naming patches</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch09s04.html">9.4. Controlling the Build</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch09s04.html#id519246">9.4.1. Preparing for the build</a></span></dt><dt><span class="sect2"><a href="ch09s04s02.html">9.4.2. Building the software</a></span></dt><dt><span class="sect2"><a href="ch09s04s03.html">9.4.3. Installing the software</a></span></dt><dt><span class="sect2"><a href="ch09s04s04.html">9.4.4. Cleaning up after the build</a></span></dt><dt><span class="sect2"><a href="ch09s04s05.html">9.4.5. Defining installation scripts</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch09s05.html">9.5. Filling the List of Files</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch09s05.html#id868856">9.5.1. Using wildcards</a></span></dt><dt><span class="sect2"><a href="ch09s05s02.html">9.5.2. Naming directories of files</a></span></dt><dt><span class="sect2"><a href="ch09s05s03.htm
l">9.5.3. Marking files as documentation or configuration files</a></span></dt><dt><span class="sect2"><a href="ch09s05s04.html">9.5.4. Setting file attributes</a></span></dt><dt><span class="sect2"><a href="ch09s05s05.html">9.5.5. Verifying the %files section</a></span></dt><dt><span class="sect2"><a href="ch09s05s06.html">9.5.6. Filling the list of files automatically</a></span></dt><dt><span class="sect2"><a href="ch09s05s07.html">9.5.7. Handling RPM build errors for unpackaged files</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch09s06.html">9.6. Adding Change Log Entries</a></span></dt><dt><span class="sect1"><a href="ch09s07.html">9.7. Defining Spec File Macros</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch09s07.html#id724189">9.7.1. Built-in macros</a></span></dt><dt><span class="sect2"><a href="ch09s07s02.html">9.7.2. Spec file-specific macros</a></span></dt><dt><span class="sect2"><a href="ch09s07s03.html">9.7.3. Defining new macros</a></span
></dt><dt><span class="sect2"><a href="ch09s07s04.html">9.7.4. Specifying parameters to macros</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch09s08.html">9.8. Creating XML Spec Files</a></span></dt><dt><span class="sect1"><a href="ch09s09.html">9.9. Summary</a></span></dt></dl></div><div class="para">
+ This chapter covers:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Writing spec files
+ </div></li><li class="listitem"><div class="para">
+ Defining package information
+ </div></li><li class="listitem"><div class="para">
+ Controlling the build
+ </div></li><li class="listitem"><div class="para">
+ Listing the files in the package
+ </div></li><li class="listitem"><div class="para">
+ Defining spec file macros
+ </div></li></ul></div><div class="para">
+ The previous chapter introduces the concepts of how to build RPMs, and briefly covered the spec file, which controls how RPM packages are built and installed. This chapter delves into how to create spec files and the next chapter covers advanced spec file topics such as using conditional commands and making relocatable packages.
+ </div><div class="para">
+ A spec file defines all the commands and values that are required for creating a package, everything from the name and version number to the actual commands used to build the program you are packaging.
+ </div><div class="para">
+ This chapter covers the spec file syntax and how to write spec files. In goes in depth into defining information about your package, controlling how the software will be built, defining what exactly should go into the package, and customizing your build with RPM macros.
+ </div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id638671" class="title">Reading Spec Files</h1></div></div></div><div class="para">
+ The first step to learning more about spec files is to read through some of the huge number of spec files for the source RPMs that come with your Linux distribution. Looking at these files will show two things right away:
+ </div><div class="para">
+ *You will see that the spec file syntax is not really as complicated as it appears.
+ </div><div class="para">
+ *You will see how many others have solved problems similar to those you need to solve.
+ </div><div class="para">
+ I’ve used real-world examples throughout this book, to show how the RPMs you need to deal with actually work. Some of the more interesting packages include anything that has a client and a server component, anything with networking or e-mail, and anything that installs a system service. All these types of packages solve problems that you will commonly face. Some useful spec files to look at are those for anonftp, telnet, vnc, and sendmail. To get these spec files, you need to install the corresponding source RPMs for each of these packages.
+ </div><div class="para">
+ As you read through spec files, you’ll start to see common patterns in how packages are defined, named, the macros used, and common elements in the build sections of the spec files. You’ll also see how network services are installed on Linux, as well as example install and uninstall scripts. The next sections provide more information on the things to look for within spec files.
+ </div><div class="para">
+ Furthermore, even with the plethora of options RPM provides, if you know shell scripting basics and something about how C programs are normally built, with configure scripts and make commands, you will find most spec files relatively easy to understand.
+ </div><div class="para">
+ The following sections go into the details of writing your own spec files. Keep your example spec files handy as you read through these sections.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch08s04.html"><strong>Înapoi</strong>8.4. Summary</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch09s02.html"><strong>Înainte</strong>9.2. Writing Spec Files</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-transactions.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-transactions.html
new file mode 100644
index 0000000..36eb692
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-transactions.html
@@ -0,0 +1,46 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Cap. 6. Transactions</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="index.html" title="Ghid RPM" /><link rel="prev" href="ch05s04.html" title="5.4. Summary" /><link rel="next" href="ch06s02.html" title="6.2. Transactions with the rpm Command" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch05s04.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch06s02.html"><strong>ÃŽnainte</strong></a></li></ul><div xml:lang="ro"
class="chapter" id="ch-transactions" lang="ro"><div class="titlepage"><div><div><h2 class="title">Cap. 6. Transactions</h2></div></div></div><div class="toc"><dl><dt><span class="sect1"><a href="ch-transactions.html#id810029">6.1. Understanding Transactions</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch-transactions.html#id726466">6.1.1. When do you need transactions?</a></span></dt><dt><span class="sect2"><a href="ch-transactions.html#id794653">6.1.2. Backing out of transactions</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch06s02.html">6.2. Transactions with the rpm Command</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch06s02.html#id817275">6.2.1. Transaction IDs</a></span></dt><dt><span class="sect2"><a href="ch06s02s02.html">6.2.2. Rolling Back Transactions</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch06s03.html">6.3. Saving Old Packages</a></span></dt><dt><span class="sect1"><a href="ch06s04.html">6.4. Summary</a></span
></dt></dl></div><div class="para">
+ This chapter covers:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Understanding transactions
+ </div></li><li class="listitem"><div class="para">
+ Querying for packages based on transactions
+ </div></li><li class="listitem"><div class="para">
+ Rolling back transactions
+ </div></li><li class="listitem"><div class="para">
+ Saving old packages when upgrading
+ </div></li></ul></div><div class="para">
+ When packages depend on other packages, you may have to install multiple packages to add a single application. Some of the packages may install cleanly; others may not. But you have to install all of the packages to get the complete application. The designers of the RPM system understood this problem and added the concept of transactions to RPM.
+ </div><div class="para">
+ This chapter covers transactions and how they can help you cleanly install a set of dependent packages. But transactions won’t solve all your problems. You still have to resolve conflicts and dependencies by using the techniques provided in the last three chapters.
+ </div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id810029" class="title">Understanding Transactions</h1></div></div></div><div class="para">
+ A transaction is a way to delimit a set of operations. All the operations can be undone, often called rolled back. Once rolled back, the system is back in the same state it was prior to the transaction. If all the operations succeed, though, the system will be in a new state. The key issue is that all of the operations must complete successfully, or you can roll back the entire transaction. The assumption is that if any of the operations fail, the system will be in an inconsistent or erroneous state. Transactions are a way to prevent that.
+ </div><div class="para">
+ Transactions are common when working with databases, but they are just as important when working with packages.
+ </div><div class="para">
+ Starting with RPM version 4.0.4, transactions and rollbacks became a workable part of any administrator's toolkit. With RPM, the rpm command sets up a transaction any time you attempt to install, remove, or upgrade more than one package. The rpm command automatically makes a transaction.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id726466" class="title">When do you need transactions?</h1></div></div></div><div class="para">
+ Whenever you install or remove packages, the RPM system assigns a transaction and a transaction ID to the set of packages. You can then perform operations on the packages that share the same ID, including rolling back the transaction.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ Rollbacks work only for package upgrades with the 4.1 version of the RPM system, not package installs
+ </div><div class="para">
+ The RPM system saves an image of the RPM package header for each package installed or removed. You can use this image, along with RPM transaction IDs, to back out of transactions should something go wrong when setting up your system.
+ </div><div class="para">
+ The main advantage of transactions with RPM, though, is the fact that the rpm command automatically sets up a transaction for all the packages on each command line and does not perform the operation if any package fails. This ability to automatically set up transactions for each call to the rpm command eliminates many errors when working with packages.
+ </div><div class="para">
+ Use a transaction when you need to be sure that a set of packages install properly.
+ </div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id794653" class="title">Backing out of transactions</h1></div></div></div><div class="para">
+ With RPM, backing out of a transaction involves two operations: rolling back the transaction and reinstalling the former packages to restore the previous system state. In the simplest case, the rpm command handles all the tasks for you. If you try to install, upgrade, or remove multiple packages and any package fails, the rpm command will restore the system state for you.
+ </div><div class="para">
+ This automatic support for transactions is a great help to system administrators, but it only applies when you first install, upgrade, or remove the packages. If you have upgraded your system and later discover problems, then you can also use the --rollback option to roll the system back from a set of upgrades, in a limited set of circumstances.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch05s04.html"><strong>Înapoi</strong>5.4. Summary</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch06s02.html"><strong>Înainte</strong>6.2. Transactions with the rpm Command</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-using-rpm-db.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-using-rpm-db.html
new file mode 100644
index 0000000..8ee46ce
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-using-rpm-db.html
@@ -0,0 +1,320 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Cap. 4. Using the RPM Database</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="index.html" title="Ghid RPM" /><link rel="prev" href="ch03s05.html" title="3.5. Summary" /><link rel="next" href="RPM_Guide-Using_RPM_DB-getting_information.html" title="4.2. Getting Information on Packages" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch03s05.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="RPM_Guide-Using_RPM_DB-getting_informat
ion.html"><strong>ÃŽnainte</strong></a></li></ul><div xml:lang="ro" class="chapter" id="ch-using-rpm-db" lang="ro"><div class="titlepage"><div><div><h2 class="title">Cap. 4. Using the RPM Database</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="ch-using-rpm-db.html#RPM_Guide-Using_RPM_DB-querying_database">4.1. Querying the RPM Database</a></span></dt><dd><dl><dt><span class="section"><a href="ch-using-rpm-db.html#id669857">4.1.1. Querying packages</a></span></dt><dt><span class="section"><a href="ch-using-rpm-db.html#RPM_Guide-Using_RPM_DB-query_everything">4.1.2. Querying everything</a></span></dt><dt><span class="section"><a href="ch-using-rpm-db.html#RPM_Guide-Using_RPM_DB-refining_query">4.1.3. Refining the query</a></span></dt><dt><span class="section"><a href="ch-using-rpm-db.html#RPM_Guide-Using_RPM_DB-which_package">4.1.4. Finding which packages own files</a></span></dt></dl></dd><dt><span class="section"><a href="RPM_Guide-Using_RPM_DB
-getting_information.html">4.2. Getting Information on Packages</a></span></dt><dd><dl><dt><span class="section"><a href="RPM_Guide-Using_RPM_DB-getting_information.html#RPM_Guide-USing_RPM_DB-getting_information-describing_packages">4.2.1. Describing packages</a></span></dt><dt><span class="section"><a href="RPM_Guide-Using_RPM_DB-package_groups.html">4.2.2. Package groups</a></span></dt><dt><span class="section"><a href="ch04s02s03.html">4.2.3. Listing the files in a package</a></span></dt><dt><span class="section"><a href="RPM_Guide-Using_RPM_DB-listing_conf_files.html">4.2.4. Listing the configuration files for a package</a></span></dt><dt><span class="section"><a href="ch04s02s05.html">4.2.5. Listing the documentation files for a package</a></span></dt><dt><span class="section"><a href="RPM_Guide-Using_RPM_DB-file_state.html">4.2.6. Listing the state of the files in a package</a></span></dt><dt><span class="section"><a href="RPM_Guide-Using_RPM_DB-listing_scripts.html">
4.2.7. Listing the scripts in a package</a></span></dt><dt><span class="section"><a href="RPM_Guide-Using_RPM_DB-Listing_changed.html">4.2.8. Listing what has changed</a></span></dt><dt><span class="section"><a href="RPM_Guide-Using_RPM_DB-Combining_queries.html">4.2.9. Combining queries</a></span></dt><dt><span class="section"><a href="RPM_Guide-Using_RPM_DB-Cusomt_queries.html">4.2.10. Creating custom queries</a></span></dt><dt><span class="section"><a href="RPM_Guide-Using_RPM_DB-Query_format_tags.html">4.2.11. Working With Query Format Tags</a></span></dt><dt><span class="section"><a href="RPM_Guide-Using_RPM_DB-Querying_for_package_information.html">4.2.12. Querying for Package Information</a></span></dt><dt><span class="section"><a href="RPM_Guide-Using_RPM_DB-Formatting_arrays.html">4.2.13. Formatting Arrays</a></span></dt><dt><span class="section"><a href="RPM_Guide-Using_RPM_DB-Special_formatting.html">4.2.14. Special Formatting</a></span></dt><dt><span class="secti
on"><a href="RPM_Guide-Using_RPM_DB-querying_pacakge_dependencies.html">4.2.15. Querying for Package Dependencies</a></span></dt><dt><span class="section"><a href="RPM-Guide-Using_RPM_DB-Querying_file_information.html">4.2.16. Querying for File Information</a></span></dt><dt><span class="section"><a href="RPM_Guide-Using_RPM_DB-Other_Query_Format_Tags.html">4.2.17. Other Query Format Tags</a></span></dt></dl></dd><dt><span class="section"><a href="ch04s03.html">4.3. Other queries</a></span></dt><dt><span class="section"><a href="RPM_Guide-Using_RPM_DB-Getting_information_on_package_files.html">4.4. Getting Information on Package Files</a></span></dt><dd><dl><dt><span class="section"><a href="RPM_Guide-Using_RPM_DB-Getting_information_on_package_files.html#RPM_Guide_Using_RPM_DB-Querying_package_files_remotely">4.4.1. Querying Package Files Remotely</a></span></dt><dt><span class="section"><a href="RPM-Guide-Using_RPM-DB-verifying_packages.html">4.4.2. Verifying Installed RPM
Packages</a></span></dt><dt><span class="section"><a href="RPM_GUide-Using_RPM_DB-working_with_RPM_db.html">4.4.3. Working With the RPM Database</a></span></dt><dt><span class="section"><a href="RPM_Guide-Using_RPM_DB-summary.html">4.4.4. Summary</a></span></dt></dl></dd></dl></div><div class="para">
+ This chapter covers:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Querying the RPM database
+ </div></li><li class="listitem"><div class="para">
+ Getting information on RPM files
+ </div></li><li class="listitem"><div class="para">
+ Finding out which packages own files on your system
+ </div></li><li class="listitem"><div class="para">
+ Verifying installed packages
+ </div></li><li class="listitem"><div class="para">
+ Backing up the RPM database
+ </div></li><li class="listitem"><div class="para">
+ Repairing damaged RPM databases
+ </div></li></ul></div><div class="para">
+ Every package you install with RPM is recorded in the RPM database. The RPM system includes commands to query this database to find out which packages are installed and to provide quite a few details about these packages.
+ </div><div class="para">
+ This chapter covers querying both the RPM database and RPM package files. Both types of query are important:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Query the RPM database to see what is installed, or not installed, on your system.
+ </div></li><li class="listitem"><div class="para">
+ Query package files to see what the files require, as well as what the files provide.
+ </div></li></ul></div><div class="para">
+ In addition to querying the RPM database, you can use the database to verify packages. Since this database is so important to the management of your Linux system, this chapter covers how to back it up, as well as how to repair a damaged RPM database.
+ </div><div class="section" id="RPM_Guide-Using_RPM_DB-querying_database"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="RPM_Guide-Using_RPM_DB-querying_database">4.1. Querying the RPM Database</h2></div></div></div><div class="para">
+ In <a class="xref" href="ch-using-rpm.html">Cap. 3, <em>Using RPM</em></a> , you saw that the rpm command usually takes one major command-line option to tell it the operation to perform and a myriad of command-line options to customize the operation. The rpm command may also take the name of one or more RPM package files or the name of one or more installed packages. For example, the <code class="command">rpm –i</code> command performs an installation operation, and the <code class="command">rpm –U</code> command performs an upgrade.
+ </div><div class="para">
+ For querying the RPM database, the major command-line option is <code class="literal">–q</code>, short for query. This option tells the rpm command to query the RPM database. You can also use the long option <code class="literal">--query</code>.
+ </div><div class="para">
+ In the last few chapters, you've used the <code class="literal">–q</code> option with the rpm command to query just for the presence or absence of installed packages. You can expand the <code class="literal">-q</code> option to perform a wide array of queries to find out information about the packages installed on a Linux system.
+ </div><div class="section"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id669857">4.1.1. Querying packages</h3></div></div></div><div class="para">
+ The basic format of the <code class="command">rpm –q</code> command follows:
+ </div><div class="para">
+ <code class="command">rpm –q <em class="replaceable"><code>package_name</code></em></code>
+ </div><div class="para">
+ You need to provide the name of a package to query. For example:
+ </div><div class="para">
+ <code class="command">rpm -q telnet-0.17</code>
+ </div><div class="para">
+ This command returns the name of the package, if installed. For example:
+ </div><pre class="screen">
+ telnet-0.17-20
+</pre><div class="para">
+ If the package is not installed, you’ll see a message like the following:
+ </div><pre class="screen">
+ package telnet-0.17 is not installed
+</pre><div class="para">
+ You can provide the whole package name to the rpm command, which includes the name, the version, and the RPM package number, as discussed in <a class="xref" href="ch-rpm-overview.html">Cap. 2, <em>RPM Overview</em></a> . You can also just provide the name and version number, as shown previously, or just the base name of the package.
+ </div><div class="para">
+ For example, the following command uses just the base name of the package:
+ </div><div class="para">
+ <code class="command">rpm -q telnet</code>
+ </div><pre class="screen">
+ telnet-0.17-20
+</pre><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ The rpm –q command expects a package name. Although it supports some amount of customized queries, you really need to know which packages you want the rpm command to report on.
+ </div></div></div><div class="para">
+ You can provide more than one package name; the rpm command reports on each package, as shown following.
+ </div><div class="para">
+ <code class="command">rpm -q telnet telnet-server</code>
+ </div><pre class="screen">
+ telnet-0.17-20
+ telnet-server-0.17-20
+</pre><div class="para">
+ You need to change the way you query if you want to perform searches when you do not know the full package name in advance. The following sections cover options for creating various queries.
+ </div></div><div class="section" id="RPM_Guide-Using_RPM_DB-query_everything"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="RPM_Guide-Using_RPM_DB-query_everything">4.1.2. Querying everything</h3></div></div></div><div class="para">
+ Up to now, we have used the rpm command to query only for specific packages. The <code class="literal">–a</code> option tells the rpm command to query for all packages. You can also use the longer option, <code class="literal">--all</code>, in place of <code class="literal">–a</code>.
+ </div><div class="para">
+ For example:
+ </div><div class="para">
+ <code class="command">rpm -qa</code>
+ </div><div class="para">
+ This command returns every package installed on your system, quite a few packages. The packages are returned one per line, as shown following.
+ </div><div class="para">
+
+<pre class="screen">m17n-db-gujarati-1.5.5-4.fc13.noarch
+libvisual-0.4.0-9.fc12.x86_64
+hal-filesystem-0.5.14-3.fc13.x86_64
+fedora-logos-13.0.2-1.fc13.noarch
+kdepim-runtime-libs-4.4.5-1.fc13.x86_64
+lpsolve-5.5.0.15-3.fc13.x86_64
+kipi-plugins-1.2.0-1.fc13.x86_64
+kbd-1.15-9.fc12.x86_64
+perl-Glib-1.201-4.fc12.x86_64
+kdeplasma-addons-4.4.5-1.fc13.x86_64
+</pre>
+
+ </div><div class="para">
+ This output has been modified to meet size constraints. Try the <code class="command">rpm –qa</code> command to see the full output for your system.
+ </div><div class="para">
+ There may be over a thousand packages on your system. Even so, the <code class="command">rpm –qa</code> command executes surprisingly fast.
+ </div></div><div class="section" id="RPM_Guide-Using_RPM_DB-refining_query"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="RPM_Guide-Using_RPM_DB-refining_query">4.1.3. Refining the query</h3></div></div></div><div class="para">
+ When you query all the installed packages, you get too much output for most purposes, other than to get a general idea of the magnitude of packages installed on your system. But if you cannot remember a package name, there's no real option, other than writing your own RPM query program.
+ </div><div class="para">
+ You can take advantage of the power of the Linux shells, though, and the wonderful ability to pipe the output of one command into another to work around this problem. With the large amount of output, you may want to pipe the output to the <code class="command">more</code> or <code class="command">less</code> programs, and display the output one page at a time.
+ </div><div class="para">
+ Even with <code class="command">more</code> and <code class="command">less</code>, the <code class="command">rpm –qa</code> command outputs too much information to be really useful, unless you can somehow filter the information automatically.
+ </div><div class="section" id="RPM_Guide-Using_RPM_DB-refining-grep"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="RPM_Guide-Using_RPM_DB-refining-grep">4.1.3.1. Piping the Output To grep</h4></div></div></div><div class="para">
+ The Linux (and Unix) <code class="command">grep</code> command provides a powerful tool for filtering through textual data. If you pipe the output of the <code class="command">rpm –qa</code> command into the <code class="command">grep</code> command, you have a powerful search engine at your fingertips.
+ </div><div class="para">
+ For example, if you know that most packages that provide tools for the SSH service have "ssh" in their names, you can find all these packages by using a command like the following:
+ </div><div class="para">
+ <code class="command">rpm -qa | grep ssh</code>
+ </div><div class="para">
+ This command outputs packages such as the following:
+ </div><pre class="screen">ksshaskpass-0.5.3-1.fc13.x86_64
+openssh-server-5.4p1-3.fc13.x86_64
+libssh2-1.2.4-1.fc13.i686
+openssh-askpass-5.4p1-3.fc13.x86_64
+libssh2-1.2.4-1.fc13.x86_64
+openssh-5.4p1-3.fc13.x86_64
+openssh-clients-5.4p1-3.fc13.x86_64
+libssh-0.4.4-1.fc13.x86_64</pre><div class="para">
+ You can also use the --pipe option to the rpm command, introduced in <a class="xref" href="ch-using-rpm.html">Cap. 3, <em>Using RPM</em></a> . With this option, your command becomes:
+ </div><div class="para">
+ <code class="command">rpm -qa --pipe "grep ssh"</code>
+ </div><div class="note"><div class="admonition_header"><h2>Notă</h2></div><div class="admonition"><div class="para">
+ <a class="xref" href="ch-rpm-programming-python.html">Cap. 16, <em>Programming RPM with Python</em></a> covers programming with the RPM system with the Python scripting language.
+ </div></div></div><div class="para">
+ You can take advantage of some of the options that the grep command supports, including -i for ignoring the case of the string to match, --regexp to pass a regular expression to grep, and -v, to output only those entries that do not match the search string.
+ </div><div class="note"><div class="admonition_header"><h2>Notă</h2></div><div class="admonition"><div class="para">
+ If you are unfamiliar with grep, the online manual pages for the grep command provide a listing of the command-line options available for grep as well as a short tutorial on regular expressions supported by grep.
+ </div></div></div><div class="para">
+ Table 5-1 lists some of the common package-naming conventions. Remember that these are just conventions, not hard-and-fast rules. You can use these conventions in concert with rpm queries.
+ </div><div class="para">
+ Table 5-1 Common Naming Conventions on Linux
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Convention
+ </div>
+
+ </td><td>
+ <div class="para">
+ Usually indicates
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Starts with g
+ </div>
+
+ </td><td>
+ <div class="para">
+ GNOME desktop application or a GNU application, especially GNU C programming tools and libraries
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Starts with j
+ </div>
+
+ </td><td>
+ <div class="para">
+ Cross-platform Java application
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Starts with k
+ </div>
+
+ </td><td>
+ <div class="para">
+ KDE desktop application, Linux kernel package, or Kerberos security package
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Starts with py
+ </div>
+
+ </td><td>
+ <div class="para">
+ Python application
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Starts with rh
+ </div>
+
+ </td><td>
+ <div class="para">
+ Red Hat application, usually for configuring your system
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Starts with tk
+ </div>
+
+ </td><td>
+ <div class="para">
+ Graphical Tcl application
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Starts with x
+ </div>
+
+ </td><td>
+ <div class="para">
+ X Window System graphical desktop application
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Ends with wm
+ </div>
+
+ </td><td>
+ <div class="para">
+ Window manager for controlling the layout of windows on the screen
+ </div>
+
+ </td></tr></tbody></table></div></div><div class="section" id="RPM_Guide-Using_RPM_DB-refining-wildcards"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="RPM_Guide-Using_RPM_DB-refining-wildcards">4.1.3.2. Querying with Wildcards</h4></div></div></div><div class="para">
+ In addition to using other Linux commands, the rpm command supports some search options. You can pass a wildcard to <code class="command">rpm –qa</code> (but not just <code class="command">rpm –q</code>, you need the <code class="literal">–a</code> to look for all packages). For example:
+ </div><div class="para">
+ <code class="command">rpm -qa "kernel*"</code>
+ </div><pre class="screen">kernel-2.6.33.6-147.fc13.x86_64
+kernel-2.6.33.5-112.fc13.x86_64
+kernel-devel-2.6.33.5-112.fc13.x86_64
+kernel-headers-2.6.33.6-147.fc13.x86_64
+kernel-2.6.33.5-124.fc13.x86_64
+kernel-devel-2.6.33.5-124.fc13.x86_64
+kernel-devel-2.6.33.6-147.fc13.x86_64</pre><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ The quotation marks around "kernel*" are to prevent the Linux shell from expanding the wildcard character, *, to try to match a list of file names in the local directory. By passing the command-line parameter as "kernel*", the rpm program gets to see the * character. Otherwise, the shell expands the parameter and the program, rpm in this case, never sees the *.
+ </div></div></div><div class="para">
+ This command searches for all package names starting with send. You can reverse this with an exclamation mark. For example:
+ </div><div class="para">
+ $ rpm -qa '!send*'
+ </div><div class="para">
+ This command works sort of like <code class="command">grep –v</code> and searches for all packages that do not start with "send".
+ </div><div class="para">
+ There are quite a few other Linux commands you can use in pipelines with the <code class="command">rpm –qa</code> command to better filter and display the data, such as <code class="command">wc –l</code> to count the number of packages that you query. You can also use a number of other query options to find out more specialized information from the RPM database.
+ </div></div></div><div class="section" id="RPM_Guide-Using_RPM_DB-which_package"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="RPM_Guide-Using_RPM_DB-which_package">4.1.4. Finding which packages own files</h3></div></div></div><div class="para">
+ One of the common problems with package management comes when you want to track a given file on your system back to the package that “owns†the file (that is, the package that, when installed, installed the particular file).
+ </div><div class="para">
+ The <code class="option">-qf</code> option tells the rpm command to query for all packages that own a particular file. You can also use the longer option, <code class="option">--file</code>, in place of <code class="option">–f</code>. The basic syntax follows:
+ </div><div class="para">
+ <code class="command">rpm -qf <em class="replaceable"><code>filename</code></em></code>
+ </div><div class="para">
+ For example, the grep command used in previous examples is really a file. (Just about all Linux commands are a file of some sort, be it a shell script or an executable application.) You can use a few Linux commands to determine which package provides this handy program.
+ </div><div class="para">
+ First, we need the exact path to the file. For Linux commands, you can use the <code class="command">which</code> command, if the program is in your path. (The grep program must be in your path, or commands with grep will fail.)
+ </div><div class="para">
+ Try the following command:
+ </div><div class="para">
+ <code class="command">which grep</code>
+ </div><div class="para">
+ This command returns the path to grep:
+ </div><div class="para">
+
+<pre class="screen">/bin/grep</pre>
+
+ </div><div class="para">
+ We can now check which package owns this file with the following command:
+ </div><div class="para">
+ <code class="command">rpm -qf /bin/grep</code>
+ </div><div class="para">
+
+<pre class="screen">grep-2.6.3-1</pre>
+
+ </div><div class="para">
+ You can also use the Linux back-tick operator to perform this check with one command.
+ </div><div class="para">
+ <code class="command">rpm -qf `which grep`</code>
+ </div><div class="para">
+
+<pre class="screen">grep-2.6.3-1</pre>
+
+ </div><div class="para">
+ If you use the bash shell, you can use the $(command parameters) syntax in place of the back tick, or `, characters. For example:
+ </div><div class="para">
+ <code class="command">rpm -qf $(which grep)</code>
+ </div><div class="para">
+
+<pre class="screen">grep-2.6.3-1</pre>
+
+ </div><div class="para">
+ If no package owns a given file, you’ll see output like the following:
+ </div><div class="para">
+ <code class="command">rpm -qf mail</code>
+ </div><div class="para">
+
+<pre class="screen">file mail is not owned by any package</pre>
+
+ </div><div class="para">
+ Often, the package that owns a file does not have an intuitive name. The ssh command, for example, is owned by the openssh-clients package, as shown following:
+ </div><div class="para">
+ <code class="command">rpm -qf `which ssh`</code>
+ </div><div class="para">
+
+<pre class="screen">openssh-clients-5.4p1-3</pre>
+
+ </div><div class="para">
+ As you can see, the name of a command does not always correspond directly to the name of the package that provides that command. This is where the <code class="command">rpm –qf</code> command proves very useful. Otherwise, you would just have to know that OpenSSH is the project responsible for this command.
+ </div><div class="note"><div class="admonition_header"><h2>Symbolic Links</h2></div><div class="admonition"><div class="para">
+ The <code class="command">rpm -qf</code> command follows symbolic links. This was not always true with older versions of RPM, but modern RPM versions can trace package ownership to files placed in linked directories.
+ </div><div class="para">
+ For example, the directory /usr/lib/X11 is a link to the real directory, /usr/X11R6/lib/X11. You can track the package ownership of a file in that directory, XKeysymDB, for example, by using the following command:
+ </div><div class="para">
+ <code class="command">rpm -qf /usr/lib/X11/XKeysymDB</code>
+ </div><div class="para">
+
+<pre class="screen">XFree86-4.2.0-72</pre>
+
+ </div><div class="para">
+ This file, XKeysymDB, really resides in /usr/X11R6/lib/X11.
+ </div></div></div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch03s05.html"><strong>Înapoi</strong>3.5. Summary</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="RPM_Guide-Using_RPM_DB-getting_information.html"><strong>Înainte</strong>4.2. Getting Information on Packages</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-using-rpm.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-using-rpm.html
new file mode 100644
index 0000000..f2f075b
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-using-rpm.html
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Cap. 3. Using RPM</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="index.html" title="Ghid RPM" /><link rel="prev" href="ch02s04.html" title="2.4. Summary" /><link rel="next" href="ch03s02.html" title="3.2. Upgrading and Installing Software" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch02s04.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch03s02.html"><strong>ÃŽnainte</strong></a></li></ul><div xml:lang="ro"
class="chapter" id="ch-using-rpm" lang="ro"><div class="titlepage"><div><div><h2 class="title">Cap. 3. Using RPM</h2></div></div></div><div class="toc"><dl><dt><span class="sect1"><a href="ch-using-rpm.html#id557035">3.1. The <code class="command">rpm</code> Command</a></span></dt><dt><span class="sect1"><a href="ch03s02.html">3.2. Upgrading and Installing Software</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch03s02.html#id778012">3.2.1. Upgrading with the <code class="command">rpm</code> command</a></span></dt><dt><span class="sect2"><a href="ch03s02s02.html">3.2.2. Upgrading packages</a></span></dt><dt><span class="sect2"><a href="ch03s02s03.html">3.2.3. Freshening up</a></span></dt><dt><span class="sect2"><a href="ch03s02s04.html">3.2.4. Installing Packages</a></span></dt><dt><span class="sect2"><a href="ch03s02s05.html">3.2.5. Installing Over the Internet</a></span></dt><dt><span class="sect2"><a href="ch03s02s06.html">3.2.6. Installing source RPMs</a></span>
</dt></dl></dd><dt><span class="sect1"><a href="ch03s03.html">3.3. Removing Software</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch03s03.html#id780124">3.3.1. Checking that the package has been removed</a></span></dt><dt><span class="sect2"><a href="ch03s03s02.html">3.3.2. Removing multiple packages at a time</a></span></dt><dt><span class="sect2"><a href="ch03s03s03.html">3.3.3. Options when removing packages</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch03s04.html">3.4. Other <code class="command">rpm</code> Command Options</a></span></dt><dt><span class="sect1"><a href="ch03s05.html">3.5. Summary</a></span></dt></dl></div><div class="para">
+ This chapter covers:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Installing and upgrading software
+ </div></li><li class="listitem"><div class="para">
+ Removing software
+ </div></li></ul></div><div class="para">
+ This chapter covers the most common uses for RPM: installing, removing, and upgrading software. These are the most frequently used RPM commands.
+ </div><div class="para">
+ The RPM system includes the options you might expect, such as installing a package, but there’s a lot more you can do. For example, you can install packages from remote sites using HTTP or FTP to download the package to install. There are quite a few other <code class="command">rpm</code> options you can use to get information and feedback on installation, for example.
+ </div><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id557035" class="title">The <code class="command">rpm</code> Command</h1></div></div></div><div class="para">
+ Just about everything you do with RPM requires the <code class="command">rpm</code> command. As a nice added benefit, just about everything you do with RPM requires a single invocation of the <code class="command">rpm</code> command. That means common tasks such as installing and removing software can be done quickly and efficiently. The basics of the <code class="command">rpm</code> command are not very hard, and you can perform the basic tasks within a few minutes of reading this chapter.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch02s04.html"><strong>Înapoi</strong>2.4. Summary</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch03s02.html"><strong>Înainte</strong>3.2. Upgrading and Installing Software</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch01s02.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch01s02.html
new file mode 100644
index 0000000..ed144a0
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch01s02.html
@@ -0,0 +1,48 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.2. RPM Design Goals</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-intro-rpm.html" title="Cap. 1. Introduction to RPM" /><link rel="prev" href="ch-intro-rpm.html" title="Cap. 1. Introduction to RPM" /><link rel="next" href="ch01s02s02.html" title="1.2.2. Package-oriented focus" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-intro-rpm.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch01s02s02.html"><strong>ÃŽ
nainte</strong></a></li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id830934" class="title">RPM Design Goals</h1></div></div></div><div class="para">
+ All of these early system-management tools took a similar approach. They provided the capability to install an entire application with a single command, to track the files it put on the system, and to remove those files by using another single command. As the preponderance of multiple early tools suggests, this approach to system management was popular. All of these early tools, however, had numerous technical or practical deficiencies. Some tools were designed only for Linux on 32-bit Intel-compatible hardware, even though Linux by this point was already running on other CPUs in addition to the IA32 family. As Linux was spreading to multiple architectures, a package-management system that could produce packages for multiple architectures was needed. Other tools had technical flaws in how they prepared packages, making it difficult to verify that packages had been prepared correctly or to see exactly how the software was prepared.
+ </div><div class="para">
+ Because of these concerns, after their initial releases of RPP-based distributions, Red Hat looked closely at both their own RPP software and other software such as BOGUS's <code class="command">pms</code> software. Developers at Red Hat, particularly Marc Ewing and Erik Troan, set out to develop what they initially called the Red Hat Package Manager (RPM). Based on experiences with earlier Linux packaging software and knowledge about packaging tools used on other platforms, Red Hat had several design goals in mind when they developed RPM. These design points include the following features:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Ease of use
+ </div></li><li class="listitem"><div class="para">
+ Package-oriented focus
+ </div></li><li class="listitem"><div class="para">
+ Upgradability of packages
+ </div></li><li class="listitem"><div class="para">
+ Tracking of package interdependencies
+ </div></li><li class="listitem"><div class="para">
+ Query capabilities
+ </div></li><li class="listitem"><div class="para">
+ Verification
+ </div></li><li class="listitem"><div class="para">
+ Support for multiple architectures
+ </div></li><li class="listitem"><div class="para">
+ Use of pristine sources
+ </div></li></ul></div><div class="para">
+ The following sections demonstrate how Red Hat incorporated each of these design goals into RPM.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id620200" class="title">Ease of use</h1></div></div></div><div class="para">
+ Perhaps the primary design goal for RPM is that it must be easy to use. Manual software installation has been the primary method of putting software onto Unix boxes for over 30 years now and has worked very well for those three decades. To offer a compelling reason to use the new software, RPM must be significantly easier to use than other Linux package-management tools. For that reason, most tasks that can be handled using RPM were designed to be carried out via a single command. For example, software installation using RPM requires a single command (<strong class="userinput"><code>rpm -U software_package</code></strong>), while manual software installation using older manual methods typically requires at least six steps to complete the same task:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ <code class="command">tar zxf <em class="replaceable"><code>software_package</code></em></code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">cd <em class="replaceable"><code>software_package</code></em></code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">./configure</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">make</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">su</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">make install</code>
+ </div></li></ol></div><div class="para">
+ Similarly, removal of applications installed using RPM requires a single command (<strong class="userinput"><code>rpm -e <em class="replaceable"><code>software_package</code></em></code></strong>); manual removal of an installed application requires that each file associated with that application be manually deleted.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-intro-rpm.html"><strong>Înapoi</strong>Cap. 1. Introduction to RPM</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch01s02s02.html"><strong>Înainte</strong>1.2.2. Package-oriented focus</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch01s02s02.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch01s02s02.html
new file mode 100644
index 0000000..0c7d6df
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch01s02s02.html
@@ -0,0 +1,14 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.2.2. Package-oriented focus</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch01s02.html" title="1.2. RPM Design Goals" /><link rel="prev" href="ch01s02.html" title="1.2. RPM Design Goals" /><link rel="next" href="ch01s02s03.html" title="1.2.3. Package upgradability" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch01s02.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch01s02s03.html"><strong>ÃŽnainte</strong></a></li></ul
><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id852861" class="title">Package-oriented focus</h1></div></div></div><div class="para">
+ Like its predecessors, RPM is intended to operate on a package level. Rather than operating on a single-file basis (as when you manually install software using Unix command-line tools like mv and cp) or on an entire system basis (as with many PC operating systems, which provide the ability to upgrade entire releases but not to upgrade individual components), RPM provides software that can manage hundreds or thousands of packages.
+ </div><div class="para">
+ Each package is a discrete bundle of related files and associated documentation and configuration information; typically, each package is a separate application. By focusing on the package as the managed unit, RPM makes installation and deletion of applications extremely straightforward.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch01s02.html"><strong>Înapoi</strong>1.2. RPM Design Goals</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch01s02s03.html"><strong>Înainte</strong>1.2.3. Package upgradability</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch01s02s03.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch01s02s03.html
new file mode 100644
index 0000000..27bcc70
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch01s02s03.html
@@ -0,0 +1,14 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.2.3. Package upgradability</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch01s02.html" title="1.2. RPM Design Goals" /><link rel="prev" href="ch01s02s02.html" title="1.2.2. Package-oriented focus" /><link rel="next" href="ch01s02s04.html" title="1.2.4. Package interdependencies" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch01s02s02.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch01s02s04.html"><strong>ÃŽnainte</st
rong></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id852883" class="title">Package upgradability</h1></div></div></div><div class="para">
+ In addition to its package-oriented focus, RPM is designed to support upgrading packages. Once an application has been installed from an RPM package, a newer version of the same application can be installed using RPM. Doing so upgrades the existing application, removing its old files and replacing them with new files. In addition, however, RPM takes care to preserve any customizations that have been made to that application. The Apache Web server application, for example, is commonly installed on Linux machines that need the ability to serve Web pages.
+ </div><div class="para">
+ Apache's configuration information, which specifies things such as which files on the system should be made available as Web pages and who should be able to access those Web pages, is stored in a text file, typically <code class="filename">/etc/httpd/conf/httpd.conf</code>. Suppose Apache has been installed using RPM and that you have then customized <code class="filename">httpd.conf</code> to specify its configuration. If you upgrade Apache using RPM, as part of the upgrade procedure, the RPM application will take precautions to preserve the customizations you have made to the Apache configuration. In contrast, manual upgrades of applications often overwrite any existing configuration files, losing all site customizations the system administrator has made.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch01s02s02.html"><strong>Înapoi</strong>1.2.2. Package-oriented focus</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch01s02s04.html"><strong>Înainte</strong>1.2.4. Package interdependencies</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch01s02s04.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch01s02s04.html
new file mode 100644
index 0000000..6c095ad
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch01s02s04.html
@@ -0,0 +1,18 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.2.4. Package interdependencies</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch01s02.html" title="1.2. RPM Design Goals" /><link rel="prev" href="ch01s02s03.html" title="1.2.3. Package upgradability" /><link rel="next" href="ch01s02s05.html" title="1.2.5. Query capabilities" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch01s02s03.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch01s02s05.html"><strong>ÃŽnainte</strong></a
></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id698550" class="title">Package interdependencies</h1></div></div></div><div class="para">
+ Software that manages the applications installed on the system on an application level (such as RPM) does have one potential drawback in comparison with system-wide software management systems (such as PC operating systems like Microsoft Windows or OS/2, which allow the entire system to be upgraded but do not generally allow individual components to be upgraded, added, or removed). Software applications often have interdependencies; some applications work only when other applications are installed.
+ </div><div class="para">
+ The Postfix and Sendmail mail transfer agent (MTA) applications that are commonly used on Linux boxes to serve e-mail, for example, can both be configured to require users to authenticate themselves (by submitting a correct user name and password) successfully before they can use the e-mail server. This feature is often used to prevent unauthorized access to the e-mail server, preventing unscrupulous advertisers from using the server as a tool to send unsolicited commercial e-mail (or UCE, popularly known as spam). For this optional feature of Postfix and Sendmail to work, however, additional software must be installed. Both applications use another application, Cyrus SASL, which provides the Simple Authentication and Security Layer (SASL) software that Postfix or Sendmail can use to check user names and passwords. In other words, Postfix and Sendmail depend on Cyrus SASL.
+ </div><div class="para">
+ For system-wide software management systems, logical interdependencies between system components such as these are easy to track. All required components are included as part of the system, and upgrading the system upgrades all these components, ensuring that all can still interoperate. On Microsoft Windows 2000, IIS (the application used on Windows to serve Web pages) requires several other applications such as <code class="command">EventLog</code> (the Windows application that records system events, much like the Linux <code class="command">syslogd</code> and <code class="command">klogd</code> software) to be present. Since Windows is managed on a system level, not a package level, this dependency is guaranteed to be satisfied. On Linux systems using RPM, however, the situation is different. On Linux, for example, the Postfix application requires the <code class="command">syslogd</code> application, which records system events. However, RPM provides the flexibility to in
stall some applications but not install others or to uninstall others later. When you install Postfix, you have no guarantee that <code class="command">syslogd</code> is already installed. If <code class="command">syslogd</code> is not installed, Postfix will not work correctly.
+ </div><div class="para">
+ To avoid problems, Red Hat developers realized that RPMs must also track dependency information about what software they require for correct functionality, and that the RPM install and uninstall applications must use this dependency information. Because of dependencies, installing Postfix using RPM on a system without <code class="command">syslogd</code> installed generates a warning that <code class="command">syslogd</code> must also be installed. Similarly, attempting to uninstall <code class="command">syslogd</code> from a system that already has Postfix installed generates a warning that installed applications require the software that is being deleted. These warnings can be overridden if necessary, but by default RPM enforces these dependencies (refusing, for example, to let you uninstall <code class="command">syslogd</code> without also uninstalling applications that require it, such as Postfix), preventing you from accidentally breaking applications by inadvertently
uninstalling other software that they require to operate.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch01s02s03.html"><strong>Înapoi</strong>1.2.3. Package upgradability</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch01s02s05.html"><strong>Înainte</strong>1.2.5. Query capabilities</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch01s02s05.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch01s02s05.html
new file mode 100644
index 0000000..7b5b23b
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch01s02s05.html
@@ -0,0 +1,12 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.2.5. Query capabilities</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch01s02.html" title="1.2. RPM Design Goals" /><link rel="prev" href="ch01s02s04.html" title="1.2.4. Package interdependencies" /><link rel="next" href="ch01s02s06.html" title="1.2.6. Package verification" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch01s02s04.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch01s02s06.html"><strong>ÃŽnainte</stro
ng></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id641518" class="title">Query capabilities</h1></div></div></div><div class="para">
+ As part of its implementation, the RPM software maintains a database on the system of all packages that have been installed, and documenting which files those packages have installed on the system. RPM is designed to be queried easily, making it possible for you to search this database to determine what applications have been installed on the system and to see which packages have supplied each file on the system. This feature makes RPM-based systems extremely easy to use, since a single RPM command can be used to view all installed applications on the system.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch01s02s04.html"><strong>Înapoi</strong>1.2.4. Package interdependencies</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch01s02s06.html"><strong>Înainte</strong>1.2.6. Package verification</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch01s02s06.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch01s02s06.html
new file mode 100644
index 0000000..0007e1f
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch01s02s06.html
@@ -0,0 +1,12 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.2.6. Package verification</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch01s02.html" title="1.2. RPM Design Goals" /><link rel="prev" href="ch01s02s05.html" title="1.2.5. Query capabilities" /><link rel="next" href="ch01s02s07.html" title="1.2.7. Multiple architectures" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch01s02s05.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch01s02s07.html"><strong>ÃŽnainte</strong></
a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id641535" class="title">Package verification</h1></div></div></div><div class="para">
+ RPM also maintains a variety of information about each installed file in this system database, such as what permissions each file should have and what size each file should be. Red Hat developers designed this database to be useful for software verification. Over time, installed software will fail to work for reasons as mundane as the system administrator setting incorrect permissions on files or as exotic as nuclear decay of one of the computer's atoms releasing an alpha particle that can affect the computer's memory, corrupting that bit of memory and causing errors. Although RPM cannot prevent all errors that cause installed software to fail (obviously, there's not a single thing any software can do to prevent nuclear decay), it can be used to eliminate common errors. When an application fails, you can use the RPM database to make sure that all files associated with that application still have correct Unix file permissions and that no files associated with that applicati
on have become altered or corrupted.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch01s02s05.html"><strong>Înapoi</strong>1.2.5. Query capabilities</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch01s02s07.html"><strong>Înainte</strong>1.2.7. Multiple architectures</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch01s02s07.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch01s02s07.html
new file mode 100644
index 0000000..8c3704e
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch01s02s07.html
@@ -0,0 +1,18 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.2.7. Multiple architectures</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch01s02.html" title="1.2. RPM Design Goals" /><link rel="prev" href="ch01s02s06.html" title="1.2.6. Package verification" /><link rel="next" href="ch01s02s08.html" title="1.2.8. Pristine sources" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch01s02s06.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch01s02s08.html"><strong>ÃŽnainte</strong></a></
li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id574188" class="title">Multiple architectures</h1></div></div></div><div class="para">
+ Most of the RPM design goals mentioned so far are intended primarily to ease the life of system administrators and others who regularly install, remove, and upgrade applications or who need to see what is installed or verify that installed applications have been installed correctly. Some of the design goals for RPM are intended primarily not for those sorts of users of RPM but for users who must prepare software to be installed using RPM.
+ </div><div class="para">
+ One of the major limitations of early Linux package management utilities was that they could produce packages suitable only for installation on one type of computer: those that used 32-bit Intel-compatible CPUs. By 1994, Linux was beginning to support other CPUs in addition to the originally supported Intel CPUs. (Initially, Digital's Alpha processor and Motorola's 68000 series of processors were among the first additional CPUs that Linux supported. These days, Linux supports dozens of CPU architectures.) This posed a problem for distribution developers such as Red Hat and Debian, and for application vendors who desired to package their software for use on Linux. Because the available packaging methods could not produce packages for multiple architectures, packagers making software for multiple CPUs had to do extra work to prepare their packages.
+ </div><div class="para">
+ Furthermore, once the packagers had prepared packages, no method was available to indicate the architecture the packages targeted, making it difficult for end users to know on which machine types they could install the packages.
+ </div><div class="para">
+ Red Hat decided to overcome these limitations by incorporating architecture support into RPM, adding features so that the basic setup a packager performs to create a package could be leveraged to produce packages that would run on various CPUs, and so that end users could look at a package and immediately identify for which types of systems it was intended.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch01s02s06.html"><strong>Înapoi</strong>1.2.6. Package verification</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch01s02s08.html"><strong>Înainte</strong>1.2.8. Pristine sources</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch01s02s08.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch01s02s08.html
new file mode 100644
index 0000000..271e6ba
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch01s02s08.html
@@ -0,0 +1,14 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.2.8. Pristine sources</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch01s02.html" title="1.2. RPM Design Goals" /><link rel="prev" href="ch01s02s07.html" title="1.2.7. Multiple architectures" /><link rel="next" href="ch01s03.html" title="1.3. RPM Terminology" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch01s02s07.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch01s03.html"><strong>ÃŽnainte</strong></a></li></ul
><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id574227" class="title">Pristine sources</h1></div></div></div><div class="para">
+ The BOGUS distribution's <code class="command">pms</code> packaging system introduced the use of pristine source code to prepare packages. With Red Hat's early RPP package system and other similar early efforts, software packagers would compile software manually, then run commands to produce a package of that compiled software. Any changes made to the application's original source code were not recorded and would have to be recreated by the next person to package that software. Furthermore, end users wanting to know what changes had been made to the software they were running had no method of accessing that information.
+ </div><div class="para">
+ With RPM, Red Hat developed a package system that produced two types of packages: binary and source. Binary packages are compiled software that can be installed and used. Source packages contain the source code for that software, along with a file documenting how that source code must be compiled to produce that binary package. This feature is probably the single most significant difference between modern Linux packaging software (such as RPM) and the packaging software used on other systems (such as the pkg format that commercial Unix systems use). Source packaging makes the job of software packager easier, since packagers can use old source packages as a reference when preparing new versions of those packages. Source packages are also convenient for the end user, because they make it easily possible to change options with which that software was compiled and to produce a new binary package that supports the features the user needs.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch01s02s07.html"><strong>Înapoi</strong>1.2.7. Multiple architectures</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch01s03.html"><strong>Înainte</strong>1.3. RPM Terminology</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch01s03.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch01s03.html
new file mode 100644
index 0000000..6c8b999
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch01s03.html
@@ -0,0 +1,200 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.3. RPM Terminology</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-intro-rpm.html" title="Cap. 1. Introduction to RPM" /><link rel="prev" href="ch01s02s08.html" title="1.2.8. Pristine sources" /><link rel="next" href="ch01s04.html" title="1.4. Summary" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch01s02s08.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch01s04.html"><strong>ÃŽnainte</strong></a></li></ul><d
iv class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id641648" class="title">RPM Terminology</h1></div></div></div><div class="para">
+ When working with RPM, understanding the package concept is key. RPM packages are provided as compressed archive files that contain one or more files, as well as instructions specifying installation information about those files, including the ownerships and permissions that should be applied to each file during installation. The instructions can also contain scripts to be run after installation or before uninstallation. These package files are extremely convenient; they provide a single file that can be easily transferred between machines for installation rather than having to transfer each file to be installed.
+ </div><div class="para">
+ To help in installation and management, all package files are labeled with highly identifiable names. Package files have four-part names, which typically look something like:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">kernel-smp-2.6.32.9-3.i686.rpm</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">kernel-smp-2.6.32.9-3.x86_64.rpm</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">kernel-smp-2.6.32.9-3.ppc.rpm</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">rootfiles-7.2-1.noarch.rpm</code>
+ </div></li></ul></div><div class="para">
+ Here, the four parts of each name are separated from each other by dashes or periods. The structure of the package file name is
+ </div><div class="para">
+ <code class="filename">name-version-release.architecture.rpm</code>
+ </div><div class="para">
+ The name identifies what software is contained within the archive file. Typically, this is a name of an application or package that the archive installs on the system. For example, <code class="filename">kernel-smp</code> can be installed to provide a very important application, the SMP (symmetric multiprocessing, meaning it supports systems with more than one CPU in them) version of the Linux kernel, on the system. Sometimes, rather than an application, the software is a collection of other files needed on the system. The <code class="filename">rootfiles</code> package, for example, is not an application but is a collection of basic environmental configuration files for the <code class="systemitem">root</code> user's account (such as <code class="filename">/root/.bashrc</code>, the <code class="systemitem">root</code> user's Bash configuration file) that provides a usable, preconfigured working environment for the <code class="systemitem">root</code> user.
+ </div><div class="para">
+ The second field in every package file's name is the version field. This field identifies the version number of the software that is contained in the package file. For example, <code class="filename">kernel-smp-2.6.32.9</code> indicates the RPM holds the 2.6.32.9 release of the SMP version of the Linux kernel, and <code class="filename">rootfiles-7.2</code> is the 7.2 release of the <code class="filename">rootfiles</code> configuration files.
+ </div><div class="para">
+ Every package file name also has a third component: the release field. This field identifies which release of that version of the software the package file contains. Package files contain both software and instructions about how to install that software. As packages of a particular version of software are being prepared, mistakes are sometimes made in these instruction files, or bugs are sometimes fixed within a software version; more recent package files of that software version need to be prepared that correct the problem. The –1 in the <code class="filename">rootfiles-7.2-1</code> package shows this is the first release of the 7.2 version of the <code class="filename">rootfiles</code> software. The packager of <code class="filename">rootfiles</code> version 7.2 got everything right on the first try and had no need to prepare more than one release. The –3 in the <code class="filename">kernel-smp-2.6.32.9-3</code> package, on the other hand, is the third release of th
e 2.6.32.9 version of the SMP-capable Linux kernel. This release incorporates new patches to fix bugs present in older releases of the 2.6.32.9 version of the Linux SMP kernel. The software packager increased the release number so that end users could distinguish the more recent, bug-fixed package file from the older, less bug-free package file.
+ </div><div class="para">
+ The final field in package file names is the architecture, which identifies the system types for which the package file is appropriate. For example, the <code class="filename">kernel-smp-2.6.32.9-3.x86_64</code> package is intended for use on machines with a 64-bit CPU, and <code class="filename">kernel-smp-2.6.32-9-3.i686</code> is intended for use on machines with an i686 (Pentium-class) CPU or better. An architecture name of noarch indicates this is a special architecture such that the files in the package work on any architecture. Typically, this is because the files are all interpreted scripts, not binary executables, or are documentation.
+ </div><div class="para">
+ RPM supports various architectures. Table 2-1 presents the architectures available for different platforms as of RPM version 4.7.
+ </div><div class="para">
+ Table 2-1 Supported Architectures
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Platform
+ </div>
+
+ </td><td>
+ <div class="para">
+ Architectures
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Intel-compatible 32-bit
+ </div>
+
+ </td><td>
+ <div class="para">
+ i386, i486, i586, i686, athlon, geode, pentium3, pentium4
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Intel-compatible 64-bit
+ </div>
+
+ </td><td>
+ <div class="para">
+ x86_64, amd64
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Intel Itanium
+ </div>
+
+ </td><td>
+ <div class="para">
+ ia64
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ HPAlpha (formerly Digital, Compaq)
+ </div>
+
+ </td><td>
+ <div class="para">
+ alpha, alphaev5, alphaev56, alphapca56, alphaev6, alphaev67
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Sparc/Ultra Sparc (Sun)
+ </div>
+
+ </td><td>
+ <div class="para">
+ sparc, sparcv8, sparcv9, sparc64, sparc64v, sun4, sun4c, sun4d, sun4m, sun4u,
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ ARM
+ </div>
+
+ </td><td>
+ <div class="para">
+ armv3l, armv4b, armv4l, armv5tel, armv5tejl, armv6l,armv7l
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ MIPS
+ </div>
+
+ </td><td>
+ <div class="para">
+ mips, mipsel
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Power PC
+ </div>
+
+ </td><td>
+ <div class="para">
+ ppc, ppciseries, ppcpseries, ppc64, ppc8260, ppc8560, ppc32dy4
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Motorola 68000 series
+ </div>
+
+ </td><td>
+ <div class="para">
+ m68k, m68kmint, atarist, atariste, ataritt, falcon, atariclone, milan, hades
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ SGI MIPS
+ </div>
+
+ </td><td>
+ <div class="para">
+ Sgi
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ IBM RS6000
+ </div>
+
+ </td><td>
+ <div class="para">
+ rs6000
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ IBM S/390
+ </div>
+
+ </td><td>
+ <div class="para">
+ i370, s390x, s390
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Platform independent
+ </div>
+
+ </td><td>
+ <div class="para">
+ noarch
+ </div>
+
+ </td></tr></tbody></table></div><div class="note"><div class="admonition_header"><h2>Architecture Compatibility</h2></div><div class="admonition"><div class="para">
+ When choosing an appropriate architecture for your machine, be aware that more recent architectures typically run software that targets older architectures within the same family; the reverse, however, is not true. For example, within the 32-bit Intel-compatible architectures, a 686-class (Pentium II / III / IV) machine runs files within i386, i486, i586, and i686 RPM package files, but a 386-class (80386) machine runs files within i386 RPM package files only. Similarly, for the Alpha architecture, more recent Alpha EV68 CPUs can run programs from RPM package files with alphaev67, alphaev6, alphaev56, alphaev5, and alpha architectures, but an older Alpha EV56 machine can run programs from RPM package files with alpha, alphaev5, or alphaev56 architectures only.
+ </div></div></div><div class="para">
+ Notice that the four fields in RPM package file names are separated from each other by punctuation, either a dash (-) or a period (.). Periods and dashes, however, are also allowed within fields. 7.2 is a valid version number, just as <code class="filename">kernel-source</code> is a valid software name. Finally, keep in mind that all RPM package files use an .rpm file-name extension to denote that they are RPMs.
+ </div><div class="para">
+ Once installed, package names are slightly different from package file names. Package files, which can be downloaded from the Internet, copied off of CDs, and otherwise easily transferred between machines, always have names that looks like name-version-release.architecture.rpm. Installed packages, however, have names that look like <code class="filename">name-version-release</code>. Once installed, packages are referred to without the architecture field and the .rpm extension. Furthermore, installed packages consist of lots of files, not a single RPM file. For example, the package file <code class="filename">kernel-smp-2.6.32.9-3.i686.rpm</code> after installation is referred to as <code class="filename">kernel-smp-2.6.32.9-3</code>. To simplify usage even further, installed packages can be referred to by their name field only, so this file would become simply <code class="filename">kernel-smp</code>.
+ </div><div class="warning"><div class="admonition_header"><h2>Software Names May Differ from Package Names</h2></div><div class="admonition"><div class="para">
+ Once installed, the name of the package does not have to be the same as the name portion of the original package file. By convention though, the package name matches the name, version, and release part of the file name.
+ </div></div></div><div class="para">
+ Usage of the name field by itself to name packages assumes that multiple versions or releases of that particular software are not installed. However, it is in some cases necessary to install different versions or releases of the same package. My desktop at home is a 64-bit AMD system. On it, I have the following Linux kernels installed:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ kernel-2.6.32.9-70.fc12
+ </div></li><li class="listitem"><div class="para">
+ kernel-2.6.32.10-90.fc12
+ </div></li><li class="listitem"><div class="para">
+ kernel-2.6.32.11-99.fc12
+ </div></li></ul></div><div class="para">
+ This example uses the <code class="command">rpm <code class="option">–q</code></code> command to query for all installed versions of the given package, <code class="filename">kernel</code>.
+ </div><div class="note"><div class="admonition_header"><h2>The RPM Database</h2></div><div class="admonition"><div class="para">
+ <a class="xref" href="ch-using-rpm-db.html">Cap. 4, <em>Using the RPM Database</em></a> covers querying the RPM database in depth.
+ </div></div></div><div class="para">
+ I have three different versions installed on this system. Since I have multiple packages installed of the <code class="filename">kernel</code> software, I have to use the full package name (such as <code class="filename">kernel-2.6.32.11-99</code>) whenever I want to work with my installed <code class="filename">kernel</code> packages.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch01s02s08.html"><strong>Înapoi</strong>1.2.8. Pristine sources</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch01s04.html"><strong>Înainte</strong>1.4. Summary</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch01s04.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch01s04.html
new file mode 100644
index 0000000..66173a4
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch01s04.html
@@ -0,0 +1,28 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.4. Summary</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-intro-rpm.html" title="Cap. 1. Introduction to RPM" /><link rel="prev" href="ch01s03.html" title="1.3. RPM Terminology" /><link rel="next" href="ch-rpm-overview.html" title="Cap. 2. RPM Overview" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch01s03.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch-rpm-overview.html"><strong>ÃŽnainte</strong><
/a></li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id814834" class="title">Summary</h1></div></div></div><div class="para">
+ The RPM system wasn’t created to solve some theoretical problem. Instead, it is the result of years of hard-won practical experience in trying to manage systems with a large number of applications. RPM builds upon older systems that were created to solve some of the problems faced by system administrators. RPM goes further, though, and tries to provide a complete package-management solution. This includes the ability to deal with wrinkles that Linux faces but that many other operating systems do not need to address.
+ </div><div class="para">
+ For example, most other operating systems don’t support more than one or two processor architectures. Sun’s Solaris, for example, supports only the SPARC and Intel architectures. Linux supports these and more. Most other operating systems also don’t include nearly so many applications. From the OpenOffice.org office suite to the Apache Web server, Linux distributions are literally packed with applications. As a final point, most other operating systems provide mainly closed-source applications. Linux, on the other hand, includes thousands of open-source applications.
+ </div><div class="para">
+ From the perspective of the organizations making Linux distributions, these wrinkles make Linux harder to manage. Luckily for end users, the solution to these problems helps make the RPM system better able to manage user systems:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Supports Multiple Architectures — The RPM system tags each package with the processor architecture.
+ </div></li><li class="listitem"><div class="para">
+ Permits Multiple Software Versions in Parallel — RPM allows for multiple versions of the same package to be installed on the same system.
+ </div></li><li class="listitem"><div class="para">
+ One File Per Program — RPM packs all of the files in a package into one file, called an RPM file, for easy transfer to other systems.
+ </div></li><li class="listitem"><div class="para">
+ Requires Only One Command Per Action — Most RPM operations such as installing or removing packages require only a single command to run.
+ </div></li><li class="listitem"><div class="para">
+ Uses Pristine Sourcecode — The RPM system supports building RPM packages from a pristine set of sources. This means you can reproduce the commands required to build an application, improving quality.
+ </div></li></ol></div><div class="para">
+ This chapter introduced the RPM system and the history behind it. The next chapter delves into the RPM basics, including files, database, and commands.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch01s03.html"><strong>Înapoi</strong>1.3. RPM Terminology</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch-rpm-overview.html"><strong>Înainte</strong>Cap. 2. RPM Overview</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch02s02.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch02s02.html
new file mode 100644
index 0000000..b560c88
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch02s02.html
@@ -0,0 +1,60 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.2. Querying the RPM Database</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-rpm-overview.html" title="Cap. 2. RPM Overview" /><link rel="prev" href="ch-rpm-overview.html" title="Cap. 2. RPM Overview" /><link rel="next" href="ch02s03.html" title="2.3. Running RPM Commands" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-rpm-overview.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch02s03.html"><strong>ÃŽnainte</strong>
</a></li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id670724" class="title">Querying the RPM Database</h1></div></div></div><div class="para">
+ The RPM database holds information about all the RPM packages installed on your system. You can use this database to query what is installed, to help determine if you have the latest versions of software, and to verify that your system is properly set up, at least from a packaging point of view.
+ </div><div class="para">
+ The RPM database itself is stored in the directory <code class="filename">/var/lib/rpm/</code>, and should contain files like the following:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">Basenames</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">Conflictname</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">__db.001</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">__db.002</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">__db.003</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">Dirnames</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">Filemd5s</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">Group</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">Installtid</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">Name</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">Packages</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">Providename</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">Provideversion</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">Pubkeys</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">Requirename</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">Requireversion</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">Sha1header</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">Sigmd5</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">Triggername</code>
+ </div></li></ul></div><div class="note"><div class="admonition_header"><h2>The RPM Database</h2></div><div class="admonition"><div class="para">
+ <a class="xref" href="ch-using-rpm-db.html">Cap. 4, <em>Using the RPM Database</em></a> covers the database in more detail.
+ </div></div></div><div class="para">
+ These files make up the RPM database. The file <code class="filename">__db.001</code> and similar files are lock files used by the RPM system. The other files are databases in Berkeley DB format. The most important file is <code class="filename">Packages</code>. The <code class="filename">Packages</code> file contains the header tag information for each package indexed by an index number for each package. This number slowly grows with time.
+ </div><div class="para">
+ The other files, such as <code class="filename">Name</code>, <code class="filename">Providename</code>, and <code class="filename">Group</code>, exist to speed access to particular types of information. Treat your RPM database with care. Back up the files, especially after upgrading, installing, or removing packages.
+ </div><div class="note"><div class="admonition_header"><h2>Recreating The RPM Database</h2></div><div class="admonition"><div class="para">
+ Only the <code class="filename">Packages</code> file is essential. You can recreate the rest of the files using the <code class="command">rpm <code class="option">--rebuilddb</code></code> command, introduced in <a class="xref" href="ch-using-rpm-db.html">Cap. 4, <em>Using the RPM Database</em></a>.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-rpm-overview.html"><strong>Înapoi</strong>Cap. 2. RPM Overview</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch02s03.html"><strong>Înainte</strong>2.3. Running RPM Commands</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch02s03.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch02s03.html
new file mode 100644
index 0000000..f6c2f12
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch02s03.html
@@ -0,0 +1,105 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.3. Running RPM Commands</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-rpm-overview.html" title="Cap. 2. RPM Overview" /><link rel="prev" href="ch02s02.html" title="2.2. Querying the RPM Database" /><link rel="next" href="ch02s03s02.html" title="2.3.2. Other RPM commands" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch02s02.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch02s03s02.html"><strong>ÃŽnainte</strong>
</a></li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id854415" class="title">Running RPM Commands</h1></div></div></div><div class="para">
+ The primary RPM command is simply <code class="command">rpm</code>. One of the original goals of the RPM system is providing ease of use. In support of this goal, just about everything you want to do with the RPM system can be done with this one command. For most usage, the command-line parameters to the <code class="command">rpm</code> command determine the actions it should take.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id854435" class="title">Working with the <code class="command">rpm</code> command</h1></div></div></div><div class="para">
+ The <code class="command">rpm</code> command performs the most common package-management functions, along with a host of uncommon functions as well. The table below lists the main operations you can perform with the <code class="command">rpm</code> command and the command-line options to specify the given operations.
+ </div><div class="table" id="tb-rpm-operations"><h6>Tabel 2.1. The main <code class="command">rpm</code> operations</h6><div class="table-contents"><table summary="The main rpm operations" border="1"><colgroup><col class="Operation" width="33%" /><col class="Short Option" width="33%" /><col class="Long Option" width="33%" /></colgroup><thead><tr><th>
+ Operation
+ </th><th>
+ Short Option
+ </th><th>
+ Long Option
+ </th></tr></thead><tbody><tr><td>
+ Upgrade/install
+ </td><td>
+ -U
+ </td><td>
+ --upgrade
+ </td></tr><tr><td>
+ Install
+ </td><td>
+ -I
+ </td><td>
+ --install
+ </td></tr><tr><td>
+ Remove
+ </td><td>
+ -e
+ </td><td>
+ --erase
+ </td></tr><tr><td>
+ Query
+ </td><td>
+ -q
+ </td><td>
+ --query
+ </td></tr><tr><td>
+ Verify
+ </td><td>
+ -V
+ </td><td>
+ --verify
+ </td></tr><tr><td>
+ Check signature
+ </td><td>
+ -K
+ </td><td>
+ --checksig
+ </td></tr><tr><td>
+ Freshen (upgrade) already-installed package
+ </td><td>
+ -F
+ </td><td>
+ --freshen
+ </td></tr><tr><td>
+ Initialize database
+ </td><td>
+ None
+ </td><td>
+ --initdb
+ </td></tr><tr><td>
+ Rebuild database
+ </td><td>
+ None
+ </td><td>
+ --rebuilddb
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ Using this table as a guide, you can explore the options to the <code class="command">rpm</code> command. To install or upgrade a package, use the <code class="option">-U</code> command-line option:
+ </div><pre class="screen">
+<strong class="userinput"><code>rpm -U <em class="replaceable"><code>filename.rpm</code></em></code></strong></pre><div class="para">
+ For example, to install the <code class="filename">mlocate</code> RPM used as an example in this chapter, run the following command:
+ </div><pre class="screen">
+<strong class="userinput"><code>rpm -U <em class="replaceable"><code>mlocate-0.22.2-2.i686.rpm</code></em></code></strong></pre><div class="para">
+ To get extra feedback, you can use a command like the following, with the <code class="option">-h</code> and <code class="option">-v</code> options in conjunction with the <code class="option">–U</code> option:
+ </div><pre class="screen">
+<strong class="userinput"><code>rpm -Uhv <em class="replaceable"><code>mlocate-0.22.2-2.i686.rpm</code></em></code></strong></pre><div class="para">
+ When you run this command you will see more output than the default, which is no output unless there are errors. With the <code class="option">–h</code> option, the <code class="command">rpm</code> command will print a series of hash marks, #, to provide feedback that the command is still running. With the <code class="option">–v</code> option, the <code class="command">rpm</code> command provides more verbose messages.
+ </div><div class="note"><div class="admonition_header"><h2>Installing a Package</h2></div><div class="admonition"><div class="para">
+ The most common command to install a package is:
+ </div><pre class="screen">
+<strong class="userinput"><code>rpm -Uhv <em class="replaceable"><code>package_file.rpm</code></em></code></strong></pre><div class="para">
+ This command upgrades a package with extra output. If the package has not been installed, this command installs the package. See <a class="xref" href="ch-using-rpm.html">Cap. 3, <em>Using RPM</em></a> for more on upgrading and installing.
+ </div></div></div><div class="para">
+ To remove a package (called erase in RPM terminology), use the <code class="option">–e</code> command-line option:
+ </div><pre class="screen">
+<strong class="userinput"><code>rpm –e <em class="replaceable"><code>package_name</code></em></code></strong></pre><div class="note"><div class="admonition_header"><h2>Using File Extensions</h2></div><div class="admonition"><div class="para">
+ Notice that you install a package file using the file name that ends in .rpm, but uninstall or erase a package without the .rpm extension. This is because you install RPM files, but once installed, you work with the installed packages. The file name and the package name do not have to correspond, but typically (and sanely) they have the same base name.
+ </div></div></div><div class="para">
+ To list every RPM package installed on your system, use a command like the following.
+ </div><pre class="screen">
+<strong class="userinput"><code>rpm –qa</code></strong></pre><div class="para">
+ Expect to wait while this command completes. Most Linux systems have numerous packages installed, which will result in many lines of output. To better see the output, you can pipe this command to the more command, as shown following:
+ </div><pre class="screen">
+<strong class="userinput"><code>rpm –qa | more</code></strong></pre><div class="para">
+ You will then see the package listing one screen at a time.
+ </div><div class="note"><div class="admonition_header"><h2><code class="command">rpm</code> Options</h2></div><div class="admonition"><div class="para">
+ <a class="xref" href="ch-command-reference.html">Cap. 21, <em>RPM Command Reference</em></a> lists all the options for the <code class="command">rpm</code> command.
+ </div></div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch02s02.html"><strong>Înapoi</strong>2.2. Querying the RPM Database</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch02s03s02.html"><strong>Înainte</strong>2.3.2. Other RPM commands</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch02s03s02.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch02s03s02.html
new file mode 100644
index 0000000..b231577
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch02s03s02.html
@@ -0,0 +1,30 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.3.2. Other RPM commands</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch02s03.html" title="2.3. Running RPM Commands" /><link rel="prev" href="ch02s03.html" title="2.3. Running RPM Commands" /><link rel="next" href="ch02s04.html" title="2.4. Summary" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch02s03.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch02s04.html"><strong>ÃŽnainte</strong></a></li></ul><div class="s
ect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id864826" class="title">Other RPM commands</h1></div></div></div><div class="para">
+ In addition to <code class="command">rpm</code>, the RPM system includes a few more commands, including <code class="command">rpmbuild</code> and <code class="command">rpm2cpio</code>.
+ </div><div class="para">
+ The <code class="command">rpmbuild</code> command helps build RPM packages. Its usage is discussed in depth in Part II of this book.
+ </div><div class="para">
+ The <code class="command">rpm2cpio</code> command exports an RPM package file into the format that the <code class="command">cpio</code> command expects. The <code class="filename">cpio</code> command works with many tape-backup packages. You can also take advantage of the fact that <code class="filename">cpio</code> can list the individual files in a <code class="filename">cpio</code> archive or extract files. To list the files in an RPM package, use a command like the following:
+ </div><pre class="screen">
+<strong class="userinput"><code>rpm2cpio <em class="replaceable"><code>package_file.rpm</code></em> | cpio –t</code></strong></pre><div class="para">
+ For example, the following command lists all the files in the <code class="filename">mlocate</code> package:
+ </div><pre class="screen">
+<strong class="userinput"><code>rpm2cpio <em class="replaceable"><code>mlocate-0.22.2-2.i686.rpm</code></em> | cpio –t</code></strong></pre><div class="para">
+ To display:
+ </div><pre class="screen">
+<code class="computeroutput"> ./etc/cron.daily/mlocate.cron ./etc/updatedb.conf ./usr/bin/locate ./usr/bin/updatedb ./usr/share/doc/mlocate-0.22.2 ./usr/share/doc/mlocate-0.22.2/AUTHORS ./usr/share/doc/mlocate-0.22.2/COPYING ./usr/share/doc/mlocate-0.22.2/NEWS ./usr/share/doc/mlocate-0.22.2/README ./usr/share/locale/bg/LC_MESSAGES/mlocate.mo ./usr/share/locale/ca/LC_MESSAGES/mlocate.mo ./usr/share/locale/cs/LC_MESSAGES/mlocate.mo ./usr/share/locale/da/LC_MESSAGES/mlocate.mo ./usr/share/locale/de/LC_MESSAGES/mlocate.mo ./usr/share/locale/es/LC_MESSAGES/mlocate.mo ./usr/share/locale/fr/LC_MESSAGES/mlocate.mo ./usr/share/locale/hu/LC_MESSAGES/mlocate.mo ./usr/share/locale/it/LC_MESSAGES/mlocate.mo ./usr/share/locale/ja/LC_MESSAGES/mlocate.mo ./usr/share/locale/ms/LC_MESSAGES/mlocate.mo ./usr/share/locale/nl/LC_MESSAGES/mlocate.mo ./usr/share/locale/pl/LC_MESSAGES/mlocate.mo ./usr/share/locale/pt/LC_MESSAGES/mlocate.mo ./usr/share/locale/pt_BR/LC_MESSAGES/mlocate.mo ./usr/share/
locale/sr/LC_MESSAGES/mlocate.mo ./usr/share/locale/sr at latin/LC_MESSAGES/mlocate.mo ./usr/share/locale/sv/LC_MESSAGES/mlocate.mo ./usr/share/locale/zh_CN/LC_MESSAGES/mlocate.mo ./usr/share/man/man1/locate.1.gz ./usr/share/man/man5/mlocate.db.5.gz ./usr/share/man/man5/updatedb.conf.5.gz ./usr/share/man/man8/updatedb.8.gz ./var/lib/mlocate 555 blocks </code></pre><div class="para">
+ The <code class="command">rpm2cpio</code> command can also help if you want to extract a single file from the RPM package, using the <code class="command">cpio <code class="option">–ivd</code></code> command-line options, as follows:
+ </div><pre class="screen">
+ <strong class="userinput"><code>rpm2cpio <em class="replaceable"><code>mlocate-0.22.2-2.i686.rpm</code></em> | cpio –ivd <em class="replaceable"><code>usr/share/doc/mlocate-0.22.2/README</code></em></code></strong></pre><div class="para">
+ This command will output local <code class="filename">usr/share/doc/mlocate-0.22.2/README</code> subdirectories and the <code class="filename">README</code> file located under <code class="filename">usr/share/doc/mlocate-0.22.2</code>.
+ </div><div class="para">
+ The <code class="option">–i</code> option tells <code class="command">cpio</code> to extract files. The <code class="option">–d</code> option tells <code class="command">cpio</code> to make any local subdirectories as needed (<code class="filename">usr/share/doc/mlocate-0.22.2</code>, in this example), and the <code class="option">–v</code> option asks <code class="command">cpio</code> to politely output verbose messages about what it does. Of course, verbose is in the eye of the beholder; with many Unix and Linux commands, verbose output is still somewhat terse.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch02s03.html"><strong>Înapoi</strong>2.3. Running RPM Commands</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch02s04.html"><strong>Înainte</strong>2.4. Summary</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch02s04.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch02s04.html
new file mode 100644
index 0000000..aa3a3f4
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch02s04.html
@@ -0,0 +1,14 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.4. Summary</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-rpm-overview.html" title="Cap. 2. RPM Overview" /><link rel="prev" href="ch02s03s02.html" title="2.3.2. Other RPM commands" /><link rel="next" href="ch-using-rpm.html" title="Cap. 3. Using RPM" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch02s03s02.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch-using-rpm.html"><strong>ÃŽnainte</strong></a
></li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id571148" class="title">Summary</h1></div></div></div><div class="para">
+ The RPM files, the RPM database, and the RPM commands are the primary components that make up the RPM system. This chapter introduces you to the format and types of RPM files, the importance of maintaining the database, and the basic rpm command.
+ </div><div class="para">
+ The next chapter covers the most frequently used RPM commands. These commands allow you to install, uninstall, and update RPM packages.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch02s03s02.html"><strong>Înapoi</strong>2.3.2. Other RPM commands</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch-using-rpm.html"><strong>Înainte</strong>Cap. 3. Using RPM</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch03s02.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch03s02.html
new file mode 100644
index 0000000..33e5adb
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch03s02.html
@@ -0,0 +1,399 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.2. Upgrading and Installing Software</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-using-rpm.html" title="Cap. 3. Using RPM" /><link rel="prev" href="ch-using-rpm.html" title="Cap. 3. Using RPM" /><link rel="next" href="ch03s02s02.html" title="3.2.2. Upgrading packages" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-using-rpm.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch03s02s02.html"><strong>ÃŽnainte</strong></a></li>
</ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id556774" class="title">Upgrading and Installing Software</h1></div></div></div><div class="para">
+ To install software, you need something to install. Typically, this is a file packaged as RPM, using a file-name extension of <code class="filename">rpm</code>. Of course, this isn’t required, but just about every RPM package is stored in a file with a <code class="filename">rpm</code> extension. For example, the following file holds an RPM package, ready to be installed:
+ </div><div class="para">
+ <code class="filename">jikes-1.16-1.i386.rpm</code>
+ </div><div class="para">
+ This package holds an application named <code class="command">jikes</code> (a Java language compiler application). From the discussion in the last two chapters, you should be able to determine the version of the program this RPM holds and which release of the RPM package this represents.
+ </div><div class="para">
+ Other RPMs hold sources, the program source codes used to create an application or programming library. For example, the following file holds a source RPM:
+ </div><div class="para">
+ <code class="filename">jikes-1.16-1.src.rpm</code>
+ </div><div class="para">
+ The <code class="filename">src</code> in the package name is short for source. This file-naming convention is not required, but is used by just about all source code packages. (Following conventions helps other administrators know what to expect.)
+ </div><div class="note"><div class="admonition_header"><h2>Building Packages from Source RPMs</h2></div><div class="admonition"><div class="para">
+ Refer to <a class="xref" href="ch-creating-rpms.html">Cap. 8, <em>Creating RPMs: An Overview</em></a> and <a class="xref" href="ch-rpmbuild.html">Cap. 11, <em>Controlling the Build with <code class="command">rpmbuild</code></em></a> for information on building RPMs from source RPMs.
+ </div></div></div><div class="para">
+ The <code class="command">rpm</code> command provides three main operations for upgrading and installing packages:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term">Upgrade</span></dt><dd><div class="para">
+ An upgrade operation means installing a new version of a package and removing all previous versions of the same package. If you have not installed a package previously, the upgrade operation will install the package.
+ </div></dd><dt class="varlistentry"><span class="term">Freshen</span></dt><dd><div class="para">
+ A freshen operation means to install a new version of a package only if you have already installed another version of the package.
+ </div></dd><dt class="varlistentry"><span class="term">Install</span></dt><dd><div class="para">
+ An install operation installs a package for the first time. It also, through special command-line parameters, allows you to install multiple versions of a package, usually not what you want. So, in the vast majority of cases, you want to run the upgrade operation for all package installations.
+ </div></dd></dl></div><div class="para">
+ The following sections cover the command-line options that apply to these operations.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id778012" class="title">Upgrading with the <code class="command">rpm</code> command</h1></div></div></div><div class="para">
+ </div><div class="para">
+ Almost all installation steps use the <code class="command">rpm</code> command with the <code class="option">–U</code> option, short for upgrade, as introduced in <a class="xref" href="ch-rpm-overview.html">Cap. 2, <em>RPM Overview</em></a> . The basic syntax is:
+ </div><div class="para">
+ <code class="command">rpm</code> <code class="option">-U</code> <em class="replaceable"><code>package_name</code></em>
+ </div><div class="para">
+ For example:
+ </div><div class="para">
+
+<pre class="screen">
+<strong class="userinput"><code>rpm –U jikes-1.16-1.i386.rpm</code></strong></pre>
+
+ </div><div class="para">
+ You can also use the <code class="option">--upgrade</code> long option in place of <code class="option">-U</code>.
+ </div><div class="para">
+ Unless something goes wrong, you won’t see any response except for the shell prompt ready for your next command. Options for the <code class="command">rpm</code> command, covered shortly, present positive feedback that the package has been installed.
+ </div><div class="para">
+ The <code class="command">rpm</code> command may print out warnings, such as the one following:
+ </div><pre class="screen">
+<code class="computeroutput">warning: pyxf86config-0.3.1-2.i386.rpm: Header V3 DSA signature: NOKEY, key ID 897da07a</code></pre><div class="para">
+ This warning comes from the fact that the package was signed, but the key was not found. <a class="xref" href="ch-rpmbuild.html">Cap. 11, <em>Controlling the Build with <code class="command">rpmbuild</code></em></a> covers signing packages. In most cases, warnings such as this one are not that serious. Errors, though, should be treated seriously.
+ </div><div class="note"><div class="admonition_header"><h2><code class="systemitem">root</code> Permissions</h2></div><div class="admonition"><div class="para">
+ Just about every package you want to upgrade or install requires <code class="systemitem">root</code>, or super user, permissions. That’s because most Linux application RPMs hold files that must be installed in a protected directory such as <code class="filename">/usr/bin/</code>. In addition, RPM requires root access to modify the RPM database. Even if you could modify the system directories like <code class="filename">/usr/bin/</code>, you must also be able to modify the RPM database to successfully install or remove packages.
+ </div></div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id757070" class="title">Checking That the Package Is Installed</h1></div></div></div><div class="para">
+ Use the <code class="command">rpm –q</code> command to quickly verify a package has been installed. To verify, you need to use the name of the installed package, not the name of the RPM file. You can also use a partial package name, such as <code class="filename">jikes</code> in this case. For example:
+ </div><pre class="screen">
+<strong class="userinput"><code>rpm –q <em class="replaceable"><code>jikes</code></em></code></strong></pre><div class="para">
+ When you run this command, you should see a response like the following:
+ </div><pre class="screen">
+<code class="computeroutput">jikes-1.16-1</code></pre><div class="para">
+ The response shows that the package named <code class="filename">jikes-1.16-1</code> has been installed. This package name corresponds to the RPM file used in the preceding installation example.
+ </div><div class="para">
+ </div><div class="para">
+ The <code class="command">rpm -q</code> command just asks the RPM database if the package has been installed. There may be other issues with the package that this command won’t show. For now, though, the <code class="command">rpm –q</code> command verifies that package has been installed.
+ </div><div class="para">
+ If the package has been not installed, you will see a message similar to the following:
+ </div><pre class="screen">
+<code class="computeroutput">package jikes is not installed</code></pre></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id701339" class="title">Getting Feedback During Installation and upgrades</h1></div></div></div><div class="para">
+ The <code class="option">-h</code> option to the <code class="command">rpm</code> command prints out # signs, also called hash marks (hence the <code class="option">-h</code>). These hash marks provide some confirmation that the <code class="command">rpm</code> command is still running. This is important, since large packages may take a long time to install or upgrade. Run this command like the following:
+ </div><pre class="screen">
+<strong class="userinput"><code>rpm -Uh jikes-1.16-1.i386.rpm</code></strong></pre><div class="para">
+ You'll see this output:
+ </div><pre class="screen">
+<code class="computeroutput">########################################### [100%] ########################################### [100%]</code></pre><div class="para">
+ The hash marks are printed one at a time as the command does its work. If the package was not created properly, you may see warnings like the following:
+ </div><pre class="screen">
+<code class="computeroutput">########################################### [100%] warning: user cabbey does not exist - using root warning: user cabbey does not exist - using root warning: user cabbey does not exist - using root ########################################### [100%]</code></pre><div class="note"><div class="admonition_header"><h2>Reinstalling Packages</h2></div><div class="admonition"><div class="para">
+ You can install a package more than once. The <code class="command">rpm</code> command won't complain. The upgrade operation, though, will remove all other versions of a package. This is one more reason to use the <code class="option">–U</code> upgrade option.
+ </div></div></div><div class="para">
+ In addition to hash marks, you can get more verbose output from the tight-lipped <code class="command">rpm</code> command. The <code class="option">-v</code> option to the <code class="command">rpm</code> command tells the command to print out verbose information as the command runs. Remember, though, that verbose is used in the traditional Unix and Linux meaning, which is normally not all that verbose. In the Unix/Linux context, verbose usually means slightly more than nothing. The syntax for the command follows:
+ </div><pre class="screen">
+<strong class="userinput"><code>rpm -Uhv jikes-1.16-1.i386.rpm</code></strong></pre><div class="para">
+ With the <code class="option">-v</code> command-line option, you will see output more like the following:
+ </div><pre class="screen">
+<code class="computeroutput">Preparing... ########################################### [100%] 1:jikes ########################################### [100%]</code></pre><div class="note"><div class="admonition_header"><h2>Standard Command for Package Installation</h2></div><div class="admonition"><div class="para">
+ The most common command to install a package is <code class="command">rpm -Uhv <em class="replaceable"><code>package_file.rpm</code></em></code>. That is, upgrade with verbose output and hashes.
+ </div></div></div><div class="para">
+ To get extra verbose information, use the <code class="option">-vv</code> command-line option. Think of this as doubly verbose. Usually, though, this extra information has no meaning unless you are debugging an RPM package that you are building. See the chapters in Part II on Creating RPMs for more on how to build RPM packages.
+ </div><div class="para">
+ A double-verbose command uses much the same syntax as shown previously:
+ </div><pre class="screen">
+<strong class="userinput"><code>rpm -Uhvv jikes-1.16-1.i386.rpm</code></strong></pre><div class="para">
+ With the double-verbose option, the output appears as follows:
+ </div><pre class="screen">
+<code class="computeroutput">D: ============== jikes-1.16-1.i386.rpm D: Expected size: 702988 = lead(96)+sigs(100)+pad(4)+data(702788) D: Actual size: 702988 D: jikes-1.16-1.i386.rpm: MD5 digest: OK (2dba32192eca23eb480d1d02a9b6c022) D: added binary package [0] D: found 0 source and 1 binary packages D: opening db environment /var/lib/rpm/Packages joinenv D: opening db index /var/lib/rpm/Packages rdonly mode=0x0 D: locked db index /var/lib/rpm/Packages D: ========== +++ jikes-1.16-1 D: opening db index /var/lib/rpm/Depends create mode=0x0 D: Requires: <code class="command">rpm</code>lib(PayloadFilesHavePrefix) <= 4.0-1 YES (rpmlib provides) D: opening db index /var/lib/rpm/Providename rdonly mode=0x0 D: opening db index /var/lib/rpm/Pubkeys rdonly mode=0x0 D: read h# 9 Header V3 DSA signature: NOKEY, key ID 897da07a D: Requires: ld-linux.so.2 YES (db provides) D: read h# 9 Header V3 DSA signature: NOKEY, key ID 897da07a D: Requires: libc.so.6 YES (db provides) D: read h#
9 Header V3 DSA signature: NOKEY, key ID 897da07a D: Requires: libm.so.6 YES (db provides) D: read h# 633 Header V3 DSA signature: NOKEY, key ID 897da07a D: Requires: libstdc++-libc6.2-2.so.3 YES (db provides) D: read h# 9 Header V3 DSA signature: NOKEY, key ID 897da07a D: Requires: libc.so.6(GLIBC_2.0) YES (db provides) D: read h# 9 Header V3 DSA signature: NOKEY, key ID 897da07a D: Requires: libc.so.6(GLIBC_2.1) YES (db provides) D: read h# 9 Header V3 DSA signature: NOKEY, key ID 897da07a D: Requires: libc.so.6(GLIBC_2.1.3) YES (db provides) D: Requires: <code class="command">rpm</code>lib(CompressedFileNames) <= 3.0.4-1 YES (rpmlib provides) D: closed db index /var/lib/rpm/Pubkeys D: closed db index /var/lib/rpm/Depends D: closed db index /var/lib/rpm/Providename D: closed db index /var/lib/rpm/Packages D: closed db environment /var/lib/rpm/Packages D: ========== recording tsort relations D: ========== tsorting packages (order, #predecessors, #succesors, tree, depth)D
: 0 0 0 0 0 +jikes-1.16-1 D: installing binary packages D: opening db environment /var/lib/rpm/Packages joinenv D: opening db index /var/lib/rpm/Packages create mode=0x42 D: getting list of mounted filesystems D: sanity checking 1 elements D: opening db index /var/lib/rpm/Name create mode=0x42 D: read h# 707 Header sanity check: OK D: computing 3 file fingerprints Preparing... D: computing file dispositions D: opening db index /var/lib/rpm/Basenames create mode=0x42 ########################################### [100%] package jikes-1.16-1 is already installed D: closed db index /var/lib/rpm/Basenames D: closed db index /var/lib/rpm/Name D: closed db index /var/lib/rpm/Packages D: closed db environment /var/lib/rpm/Packages</code></pre><div class="note"><div class="admonition_header"><h2>Short and Long Options</h2></div><div class="admonition"><div class="para">
+ Although most Unix and Linux applications use a single minus sign for command-line options, such as <code class="command">rpm</code> <code class="option">-U</code>, many programs use two minus signs to indicate longer option names. For example, with the <code class="command">rpm</code> command, <code class="option">-U</code> and <code class="option">--upgrade</code> are treated the same. You can use the short option, <code class="option">-U</code>, or the long option, <code class="option">--upgrade</code>.
+ </div><div class="para">
+ There are long options for virtually every short option. There are also long options that are rarely used, for which there are no short options.
+ </div></div></div><div class="para">
+ One rarely used feedback option is <code class="option">--percent</code>. The <code class="option">--percent</code> option prints out decimal numbers that show the percentage completed as the <code class="command">rpm</code> command executes. This option is most useful if you wrap the <code class="command">rpm</code> command within some other command, such as a graphical user interface created from a Perl, Python, or Tcl/Tk script.
+ </div><div class="para">
+ The basic syntax is:
+ </div><pre class="screen">
+<strong class="userinput"><code>rpm -U --percent jikes-1.16-1.i386.rpm</code></strong></pre><div class="para">
+ When you run this command, you see output like the following:
+ </div><pre class="screen">
+<code class="computeroutput">%% 0.000000 %% 2.661902 %% 5.318614 %% 10.632039 %% 15.945465 %% 18.602177 %% 23.915603 %% 29.229028 %% 34.542453 %% 39.855879 %% 45.169304 %% 50.482729 %% 53.139442 %% 55.796154 %% 61.109580 %% 66.423005 %% 71.736430 %% 74.393143 %% 79.706568 %% 82.363281 %% 87.676706 %% 90.333419 %% 95.646844 %% 98.303557 %% 99.422736 %% 99.910411 %% 99.994892 %% 100.000000</code></pre><div class="para">
+ These decimal numbers output by the <code class="option">--percent</code> option are really meant to be input into another program, perhaps a program that shows a graphical progress meter. Each number output then updates the meter.
+ </div><div class="note"><div class="admonition_header"><h2>Percentages may be Approximate</h2></div><div class="admonition"><div class="para">
+ Don't trust the numbers too much. Claiming the package is 53.139442 percent installed just asks the user to be skeptical that it is exactly that far.
+ </div></div></div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id554553" class="title">The Installation Task In Detail</h1></div></div></div><div class="para">
+ You can use the <code class="command">rpm –U</code> command or the <code class="command">rpm –i</code> command to install a package. When the <code class="command">rpm</code> command installs a package, it goes through a number of steps:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Checking the package and the files it wants to install
+ </div></li><li class="listitem"><div class="para">
+ Performing preinstallation tasks
+ </div></li><li class="listitem"><div class="para">
+ Uncompressing the files and placing them in the proper locations
+ </div></li><li class="listitem"><div class="para">
+ Performing post-processing tasks
+ </div></li><li class="listitem"><div class="para">
+ Updating the RPM Database
+ </div></li></ol></div><div class="para">
+ When checking the package, <code class="command">rpm</code> checks that all the dependencies are installed. Dependencies are packages required by the RPM package you want to install. For example, a database-administration package for a particular database may require that the database itself was already installed.
+ </div><div class="para">
+ In addition to checking for dependencies, the <code class="command">rpm</code> command checks for conflicting packages. For example, when you are trying to install an older version of a package on top of a newer version, running the <code class="command">rpm</code> command alerts you to that conflict. This conflict-checking goes deeper than packages, though. Individual files may conflict if you are trying to install a package that has an older version of a particular file.
+ </div><div class="para">
+ After the checks, the <code class="command">rpm</code> command executes the preinstallation tasks (covered in depth in Part II). After all this preparatory work, the <code class="command">rpm</code> command finally gets down to business and installs the files in the package. These files are stored in compressed format (compressed with <code class="command">gzip</code> compression) inside the RPM file.
+ </div><div class="para">
+ After installing the files, there may be some post-processing tasks (also covered in Part II). At the end of its run, the <code class="command">rpm</code> command updates the RPM database to reflect the new package information. This update is very important and allows you to track packages.
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id617149" class="title">Taking a Test Drive</h1></div></div></div><div class="para">
+ The <code class="option">--test</code> command-line option tells the <code class="command">rpm</code> command to test the installation or upgrade process but not to install the file. For example, the following command performs an upgrade or install of the <code class="filename">jikes</code> package, but in test mode only. No files will actually be installed.
+ </div><pre class="screen">
+<strong class="userinput"><code>rpm -U --test jikes-1.16-1.i386.rpm</code></strong></pre><div class="para">
+ This command will print nothing if the tested installation or upgrade runs smoothly. If, on the other hand, a problem results from the tested installation, you will receive an error message. If the package is already installed, you will see a message like the following:
+ </div><pre class="screen">
+<code class="computeroutput">package jikes-1.16-1 is already installed</code></pre><div class="para">
+ If the file is corrupted, you will see output like the following:
+ </div><pre class="screen">
+<code class="computeroutput">chap4.txt: not an <code class="command">rpm</code> package (or package manifest):</code></pre><div class="para">
+ This example was run against a file that was clearly not an RPM package.
+ </div><div class="para">
+ The test option can help you determine package dependencies, too.
+ </div><div class="para">
+ You can often determine dependencies at a glance--if you know something about the software you are installing. For example, if you know that Ruby is a scripting language, you can guess that packages starting with <code class="filename">eruby</code>, such as <code class="filename">eruby-devel-0.9.8-2.i386.rpm</code>, will depend on a base <code class="filename">ruby</code> package.
+ </div><div class="para">
+ To show this, query for any <code class="filename">ruby</code> packages by using a command like the following:
+ </div><pre class="screen">
+<strong class="userinput"><code>rpm -q ruby</code></strong></pre><div class="para">
+ If you have not installed a <code class="filename">ruby</code> package, you'll see a message like the following:
+ </div><pre class="screen">
+<code class="computeroutput">package ruby is not installed</code></pre><div class="note"><div class="admonition_header"><h2>Package Names</h2></div><div class="admonition"><div class="para">
+ Most packages use all lowercase names. Thus, you can expect packages for the Ruby scripting language to start with <code class="filename">ruby</code>.
+ </div></div></div><div class="para">
+ Package dependencies can quickly devolve into a nightmare in which one package depends upon another and that package in turn depends on yet another.
+ </div><div class="para">
+ This is where the <code class="option">--test</code> option comes in handy, since you can check that the dependencies are resolved prior to trying to install. (Note that the <code class="command">rpm</code> command will check dependencies on real installs as well. The <code class="option">--test</code> option just allows you to check that the installation will succeed prior to trying it.) For example, if you try to install a package named <code class="filename">eruby-devel-0.9.8-2.i386.rpm</code>, you may want to run a <code class="option">--test</code> option first:
+ </div><pre class="screen">
+<strong class="userinput"><code>rpm -U --test eruby-devel-0.9.8-2.i386.rpm</code></strong></pre><div class="para">
+ You'll then see a response like the following, presuming you have no <code class="filename">ruby</code> packages installed:
+ </div><pre class="screen">
+<code class="computeroutput">error: Failed dependencies: eruby-libs = 0.9.8 is needed by eruby-devel-0.9.8-2</code></pre><div class="para">
+ Now you can see that the package in the file <code class="filename">eruby-devel-0.9.8-2.i386.rpm</code> depends on another package, <code class="filename">eruby-libs</code> in this case. In fact, this package depends on the <code class="filename">eruby-libs</code> package having a version number of 0.9.8. These packages are obviously interrelated. From the name <code class="filename">eruby-libs</code>, you can guess that the package will be in a file with a name like <code class="filename">eruby-libs-0.9.8-2.i386.rpm</code>. (I cheated and used the actual package on the Red Hat installation CDs.)
+ </div><div class="para">
+ But you can see how the version numbers of the two files, and the RPM revision levels, match up, as follows:
+ </div><div class="para">
+ <code class="filename">eruby-devel-0.9.8-2.i386.rpm</code>
+ </div><div class="para">
+ <code class="filename">eruby-libs-0.9.8-2.i386.rpm</code>
+ </div><div class="para">
+ So, now you think your problems are over. You have the package that <code class="filename">eruby-devel-0.9.8-2.i386.rpm</code> depends on: <code class="filename">eruby-libs-0.9.8-2.i386.rpm</code>. Just to be careful, though, you can test that package as well, with a command like the following:
+ </div><pre class="screen">
+<strong class="userinput"><code>rpm -U --test eruby-libs-0.9.8-2.i386.rpm</code></strong></pre><div class="para">
+ Alas, this output leads you farther down into dependency nightmare:
+ </div><pre class="screen">
+<code class="computeroutput">error: Failed dependencies: ruby-libs >= 1.6.4 is needed by eruby-libs-0.9.8-2 libruby.so.1.6 is needed by eruby-libs-0.9.8-2</code></pre><div class="para">
+ This short example shows why it makes sense to test packages prior to installing or upgrading them.
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id735962" class="title">Installing or upgrading More Than One Package At A Time</h1></div></div></div><div class="para">
+ Up to now, all the examples shown have used the <code class="command">rpm</code> command to install or upgrade one package at a time. You can optionally choose to install or upgrade a number of packages at the same time. Just list each file name on the <code class="command">rpm</code> command line. The basic syntax follows:
+ </div><pre class="screen">
+<strong class="userinput"><code>rpm -U package1.rpm <em class="replaceable"><code>package2.rpm .. package100.rpm</code></em></code></strong></pre><div class="para">
+ Simply list all the packages one after another. For example:
+ </div><pre class="screen">
+<strong class="userinput"><code>rpm -U aspell-en-ca-0.33.7.1-16.i386.rpm aspell-en-gb-0.33.7.1-16.i386.rpm</code></strong></pre><div class="para">
+ This command installs two packages, the <code class="filename">aspell</code> packages for Canadian and British English, respectively.
+ </div><div class="para">
+ The <code class="option">--noorder</code> option tells the <code class="command">rpm</code> command not to reorder the packages you are trying to install. Usually, the <code class="command">rpm</code> command will reorder the list of packages in the best order for handling the dependencies. This option really only comes into play when you are installing more than one package where the packages depend on each other. In most cases, you do not want to use this option, since this may mean that packages fail to properly install because necessary packages are not already installed.
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id559429" class="title">Installing in Different Directories</h1></div></div></div><div class="para">
+ The <code class="option">--prefix</code> and <code class="option">--relocate</code> options should make the <code class="command">rpm</code> command relocate a package to a new location. Not all packages allow relocations, though. The basic format of the command with the <code class="option">--prefix</code> option is:
+ </div><pre class="screen">
+<strong class="userinput"><code>rpm -U --prefix <em class="replaceable"><code>/new/directory package.rpm</code></em></code></strong></pre><div class="para">
+ With the <code class="option">--relocate</code> option, the command format is:
+ </div><pre class="screen">
+<strong class="userinput"><code>rpm -i --relocate <em class="replaceable"><code>/old/directory=/new/directory package.rpm</code></em></code></strong></pre><div class="para">
+ You can also use the <code class="option">--root</code> option to specify a different directory for the <code class="command">rpm</code> command to assume is the system's root, or <code class="filename">/</code>, directory. This causes the <code class="command">rpm</code> command to install files under the new root, instead of in system locations under <code class="filename">/</code>. This option is most useful for testing the installation of a complete system under a test directory. The command should use the following format:
+ </div><pre class="screen">
+<strong class="userinput"><code>rpm -U --root /tmp --dbpath /var/lib/rpm jikes-1.16-1.i386.rpm</code></strong></pre><div class="para">
+ The <code class="option">--root</code> option tells the <code class="command">rpm</code> command that the root for this install is in <code class="filename">/tmp/</code>. Installs with the <code class="option">--root</code> option take place within a <code class="command">chroot()</code> environment. This is often useful for setting up a test environment.
+ </div><div class="para">
+ The <code class="option">--dbpath</code> option tells the <code class="command">rpm</code> command that the RPM database is located in the normal location, <code class="filename">/var/lib/rpm/</code>.
+ </div><div class="para">
+ Using the <code class="option">--dbpath</code> and <code class="option">--root</code> options will give you problems unless you have installed all the dependencies in the same virtual root directory. This includes all the standard Linux C libraries. For example, if you just run the example command, you'll see error output like the following:
+ </div><pre class="screen">
+<code class="computeroutput">error: Failed dependencies: ld-linux.so.2 is needed by jikes-1.16-1 libc.so.6 is needed by jikes-1.16-1 libm.so.6 is needed by jikes-1.16-1 libstdc++-libc6.2-2.so.3 is needed by jikes-1.16-1 libc.so.6(GLIBC_2.0) is needed by jikes-1.16-1 libc.so.6(GLIBC_2.1) is needed by jikes-1.16-1 libc.so.6(GLIBC_2.1.3) is needed by jikes-1.16-1</code></pre><div class="para">
+ You can use the <code class="option">--badreloc</code> option with the <code class="option">--relocate</code> option to permit relocations on all files in the package. Usually, only those paths to files that are listed as relocatable are supported by the <code class="option">--relocate</code> option.
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id617032" class="title">Forcing the Issue</h1></div></div></div><div class="para">
+ A number of <code class="command">rpm</code> options cause the <code class="command">rpm</code> command to complain about problems and, in general, fail to install your package. You can use a number of options to run roughshod over the RPM and get it to do what you want.
+ </div><div class="para">
+ The <code class="option">--replacepkgs</code> option tells the <code class="command">rpm</code> command to replace, or reinstall, packages it may have already installed.
+ </div><div class="para">
+ The <code class="option">--replacefiles</code> option tells the <code class="command">rpm</code> command to overwrite files owned by a another package.
+ </div><div class="para">
+ The <code class="option">--justdb</code> option tells the <code class="command">rpm</code> command to update the RPM database, not to install the files. You will need to be logged in as the root user to modify the RPM database.
+ </div><div class="para">
+ The <code class="option">--nosuggest</code> option tells the <code class="command">rpm</code> command to skip any suggestions for packages that may fill in missing dependencies. You almost never want to use this option.
+ </div><div class="para">
+ The <code class="option">--excludepath</code> option tells the <code class="command">rpm</code> command to exclude all files that start with the given path. For example:
+ </div><pre class="screen">
+<strong class="userinput"><code>rpm -U --excludepath /usr/lib eruby-devel-0.9.8-2.i386.rpm</code></strong></pre><div class="para">
+ This command installs or upgrades all the files in the package, except for those files that would be placed in a directory starting with <code class="filename">/usr/lib/</code>.
+ </div><div class="para">
+ The <code class="option">--allfiles</code> option tells the <code class="command">rpm</code> command to install or upgrade all files in the package, regardless of whether the files exist or not on your hard disk.
+ </div><div class="para">
+ The <code class="option">--oldpackage</code> tells the <code class="command">rpm</code> command to allow you to install an older version of a package on top of a more recent one. You don't usually want to do this, but you may need to under the following circumstances:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ If the more recent package has some bug or security vulnerability and you need to downgrade to a former version.
+ </div></li><li class="listitem"><div class="para">
+ If the more recent package won't work with some other package that depends on a particular former version of a package.
+ </div></li></ol></div><div class="para">
+ The latter case is very common if you upgrade your system in a piecemeal fashion. If a low-level library changes, it may take a while for all the packages that depend on the low-level library to get updated to use the latest version.
+ </div><div class="para">
+ Note that when you purchase an upgraded version of Linux, such as Red Hat Linux, all the packages with the product should be properly aligned with each other as to versions. This alignment problem is an issue that the Linux vendors, such as Red Hat, need to take care of. The main problems occur when you need packages beyond those offered with your Linux distribution.
+ </div><div class="para">
+ To combine some of these options, you can use <code class="option">--force</code>, which tells the <code class="command">rpm</code> command to turn on the <code class="option">--replacepkgs</code>, <code class="option">--replacefiles</code>, and <code class="option">--oldpackage</code> modes.
+ </div><div class="para">
+ The <code class="option">--nodeps</code> command-line option tells the <code class="command">rpm</code> command to skip the dependencies check and install anyway.
+ </div><div class="warning"><div class="admonition_header"><h2>Avoid Forcing Package Operations</h2></div><div class="admonition"><div class="para">
+ The <code class="command">rpm</code> command complains with good reason. Unless you really, really know what you are doing, don't force the issue by using these command-line options.
+ </div></div></div><div class="para">
+ Consider the <code class="filename">eruby-devel-0.9.8-2.i386.rpm</code> from the previous example. You can force the <code class="command">rpm</code> command to install this package, even though it depends on another package that in turn depends on yet another. The following command will force the installation of the package in the <code class="filename">eruby-devel-0.9.8-2.i386.rpm</code> file:
+ </div><pre class="screen">
+<strong class="userinput"><code>rpm -U --nodeps eruby-devel-0.9.8-2.i386.rpm</code></strong></pre><div class="para">
+ Just to be sure, you can query for the package using a command like the following.
+ </div><pre class="screen">
+<strong class="userinput"><code>rpm -q eruby-devel</code></strong></pre><div class="para">
+ The response should be:
+ </div><pre class="screen">
+<code class="computeroutput">eruby-devel-0.9.8-2</code></pre><div class="para">
+ The package is installed, but it likely won't work, since it really does depend on other packages. These package dependencies aren’t for show. You may have a valid reason to force a package to get installed, but you should go back later to try to resolve all the dependencies.
+ </div><div class="para">
+ In addition to forcing the <code class="command">rpm</code> command not to do certain things, you can use the <code class="option">--aid</code> option to have the <code class="command">rpm</code> command do something nice for you. The <code class="option">--aid</code> option tells the <code class="command">rpm</code> command to add all the packages it would suggest into the set of packages to install. The <code class="command">rpm</code> command has enough information to suggest a package or packages that ought to contain the dependent files.
+ </div><div class="para">
+ The <code class="option">--aid</code> option depends on a separate package that contains an RPM database with all packages installed. For Red Hat Linux, this package is <code class="filename">rpmdb-redhat</code>. This separate database, built as if all packages were installed (all packages that come with Red Hat Linux in this case), allows the <code class="command">rpm</code> command to search for which packages would solve dependencies.
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id744590" class="title">Skipping the Scripts</h1></div></div></div><div class="para">
+ As part of the package installation, as well as removal, the RPM package may have scripts that the <code class="command">rpm</code> command should run. These include pre- and post-installation scripts, as well as pre- and post-uninstallation scripts. These scripts can perform options such as automatically configuring the application based on the target environment. For example, an installation script may try to detect whether a site uses Postfix or Sendmail for transferring mail messages and configure the newly-installed package accordingly.
+ </div><div class="para">
+ In most cases, the <code class="command">rpm</code> command will execute these scripts at the proper time, unless you explicitly turn the command to skip the scripts. The <code class="option">--noscripts</code> option tells the <code class="command">rpm</code> command to skip running the pre- and post-installation scripts.
+ </div><div class="para">
+ If you want, you can exercise a finer grain of control. The <code class="option">--nopre</code> option tells the <code class="command">rpm</code> command to skip any pre-installation scripts. The <code class="option">--nopost</code> option tells the <code class="command">rpm</code> command to skip any post-installation scripts.
+ </div><div class="para">
+ Similarly, the <code class="option">--nopreun</code> option tells the <code class="command">rpm</code> command to skip any pre-uninstallation scripts, and the <code class="option">--nopostun</code> option tells the <code class="command">rpm</code> command to skip any post-uninstallation scripts.
+ </div><div class="para">
+ The <code class="option">--noscripts</code> option is the same as turning on all these options.
+ </div><div class="para">
+ The table below summarizes these options.
+ </div><div class="table" id="tb-skipping-scripts"><h6>Tabel 3.1. Skipping scripts</h6><div class="table-contents"><table summary="Skipping scripts" border="1"><colgroup><col class="Option" width="50%" /><col class="Usage" width="50%" /></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Usage
+ </th></tr></thead><tbody><tr><td>
+ <div class="para">
+ <code class="option">--nopre</code>
+ </div>
+
+ </td><td>
+ <div class="para">
+ Skip pre-installation scripts.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ <code class="option">--nopost</code>
+ </div>
+
+ </td><td>
+ <div class="para">
+ Skip post-installation scripts.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ <code class="option">--nopreun</code>
+ </div>
+
+ </td><td>
+ <div class="para">
+ Skip pre-uninstallation scripts.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ <code class="option">--nopostun</code>
+ </div>
+
+ </td><td>
+ <div class="para">
+ Skip post-uninstallation scripts.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ <code class="option">--noscripts</code>
+ </div>
+
+ </td><td>
+ <div class="para">
+ Skip all the scripts; same as <code class="option">--nopre</code>, <code class="option">--nopost</code>, <code class="option">--nopreun</code>, and <code class="option">--nopostun</code>.
+ </div>
+
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ In most cases, you never want to disable these scripts. Many RPMs uses these scripts to perform the final steps of the installation, especially the post-installation scripts. For example, the Mozilla Web browser and most network services require some kind of post-processing (using a post-installation script) or the packages will not be properly installed.
+ </div><div class="para">
+ In addition to pre- and post-installation scripts, the RPM system supports triggers, a topic covered in detail in <a class="xref" href="ch-advanced-packaging.html">Cap. 10, <em>Creare avansată pachete RPM</em></a>.
+ </div><div class="para">
+ During installation, you can tell the <code class="command">rpm</code> command not to execute all the triggers or not to execute certain triggers. The <code class="option">--notriggers</code> option tells the <code class="command">rpm</code> command to skip all triggers.
+ </div><div class="para">
+ You can gain more fine-grained control with a further set of options in place of <code class="option">--notriggers</code>. The <code class="option">--notriggerin</code> option turns off triggers during installation. The <code class="option">--notriggerun</code> option turns off uninstallation triggers, and the <code class="option">--notriggerpostun</code> option turns off the post-uninstallation triggers.
+ </div><div class="para">
+ The <code class="option">--notriggers</code> option is the same as all three, <code class="option">--notriggerin</code>, <code class="option">--notriggerun</code>, and <code class="option">--notriggerpostun</code>.
+ </div><div class="para">
+ The table below summarizes these options.
+ </div><div class="table" id="tb-skipping-triggers"><h6>Tabel 3.2. Skipping Triggers</h6><div class="table-contents"><table summary="Skipping Triggers" border="1"><colgroup><col class="Option" width="50%" /><col class="Usage" width="50%" /></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Usage
+ </th></tr></thead><tbody><tr><td>
+ <div class="para">
+ <code class="option">--notriggerin</code>
+ </div>
+
+ </td><td>
+ <div class="para">
+ Skip installation triggers.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ <code class="option">--notriggerun</code>
+ </div>
+
+ </td><td>
+ <div class="para">
+ Skip uninstallation triggers.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ <code class="option">--notriggerpostun</code>
+ </div>
+
+ </td><td>
+ <div class="para">
+ Skip post-uninstallation triggers.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ <code class="option">--notriggers</code>
+ </div>
+
+ </td><td>
+ <div class="para">
+ Skip all the triggers; same as <code class="option">--notriggerin</code>, <code class="option">--notriggerun</code>, and <code class="option">--notriggerpostun</code>.
+ </div>
+
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id795970" class="title">Ignorance Is Bliss</h1></div></div></div><div class="para">
+ The <code class="command">rpm</code> command supports several ignore options that tell the command to ignore some aspect of a package it would normally complain about.
+ </div><div class="para">
+ The <code class="option">--ignorearch</code> option tells the <code class="command">rpm</code> command to ignore the architecture of the package and install the package, even if the architecture of the package and the architecture of your system do not match. This is a very dangerous option. Linux runs on everything from tiny wristwatches, PDAs such as the Sharp Zaurus, PCs, Macintosh PCs, RISC servers, and all the way up to huge supercomputers and mainframes. If you try to install a binary package compiled for the ARM or PowerPC processor on an Intel-architecture Linux system, the package will at best fail. At worst, it may damage parts of your system.
+ </div><div class="para">
+ Similarly, the <code class="option">--ignoreos</code> command-line option tells the <code class="command">rpm</code> command to ignore the operating system. Again, this is likely not a good idea in most situations. Applications compiled for Windows generally won’t run on Linux. SCO Unix systems, however, can run some Linux applications, so you may have a valid reason to ignore the operating system. Again, use only with extreme care.
+ </div><div class="para">
+ The <code class="option">--ignoresize</code> option tells the <code class="command">rpm</code> command to ignore or skip a check of your hard disk to ensure it has enough space to install the package.
+ </div><div class="warning"><div class="admonition_header"><h2>Ignoring Storage Limits</h2></div><div class="admonition"><div class="para">
+ Don't use the <code class="option">--ignoresize</code> option if you have a nearly full hard disk, especially for a root, or <code class="filename">/</code>, partition.
+ </div></div></div><div class="para">
+ The <code class="option">--nodigest</code> option tells the <code class="command">rpm</code> command to skip the test of the digest, the special value that helps verify the package correctness.
+ </div><div class="para">
+ The <code class="option">--nosignature</code> option tells the <code class="command">rpm</code> command to skip the test of the digest, the encrypted key, that helps also verify the package correctness.
+ </div><div class="warning"><div class="admonition_header"><h2>Unsafe Options</h2></div><div class="admonition"><div class="para">
+ Use these <code class="command">rpm</code> command-line options with extreme care and only after carefully considering the circumstances. Wrongful use of these options may damage your operating system.
+ </div></div></div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id862934" class="title">Documentation? What Documentation?</h1></div></div></div><div class="para">
+ The <code class="option">--excludedocs</code> command-line option tells the <code class="command">rpm</code> command to ignore any files in the RPM package that are marked as documentation. Considering the general lack of documentation for many Linux applications, you are really asking for trouble by invoking this option. If the documentation takes up a lot of disk space, however, you may want to avoid installing documentation files. This is about the only situation in which this option makes sense.
+ </div><div class="para">
+ In reverse of <code class="option">--excludedocs</code>, the <code class="option">--includedocs</code> command-line parameter tells the <code class="command">rpm</code> command to install documentation. This is usually the default, so you rarely need this option.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-using-rpm.html"><strong>Înapoi</strong>Cap. 3. Using RPM</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch03s02s02.html"><strong>Înainte</strong>3.2.2. Upgrading packages</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch03s02s02.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch03s02s02.html
new file mode 100644
index 0000000..5b05695
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch03s02s02.html
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.2.2. Upgrading packages</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch03s02.html" title="3.2. Upgrading and Installing Software" /><link rel="prev" href="ch03s02.html" title="3.2. Upgrading and Installing Software" /><link rel="next" href="ch03s02s02s02.html" title="3.2.2.2. Smart Upgrades" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch03s02.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch03s02s02s02.html"><st
rong>ÃŽnainte</strong></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id555144" class="title">Upgrading packages</h1></div></div></div><div class="para">
+ The <code class="command">rpm</code> <code class="option">–U</code> command works for both installation of new packages and for upgrading. When you get beyond simple installations, you begin to see the power of the RPM system where most operations require just one command. The <code class="command">rpm -U</code> command is a very powerful tool and performs some complex operations with just one command. For example, the following commands show the sequence for upgrading the <code class="filename">jpilot</code> package, which is used for Palm PDA synchronization.
+ </div><pre class="screen">
+<strong class="userinput"><code># rpm -q jpilot</code></strong></pre><pre class="screen">
+<code class="computeroutput">jpilot-0.97-1</code></pre><pre class="screen">
+<strong class="userinput"><code># rpm -U jpilot-0.99.2-8.i386.rpm # rpm -q jpilot</code></strong></pre><pre class="screen">
+<code class="computeroutput">jpilot-0.99.2-8</code></pre><div class="para">
+ Note that the old version of the <code class="filename">jpilot</code> package is no longer installed. The <code class="command">rpm -U</code> command removed that package.
+ </div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id555211" class="title">Options When Upgrading</h1></div></div></div><div class="para">
+ You can pass more than one package name on the command line when upgrading. In addition, you can use the installation and upgrade options discussed previously when upgrading.
+ </div><div class="note"><div class="admonition_header"><h2>Uninstallation Scripts</h2></div><div class="admonition"><div class="para">
+ When upgrading, the <code class="option">--noscripts</code> option only turns off the scripts from the new package. If an old package is removed, the uninstallation scripts for the old package still get executed.
+ </div></div></div><div class="para">
+ When upgrading, you can also use the <code class="option">--repackage</code> option, which works the same as when removing packages. The <code class="option">--repackage</code> option tells the <code class="command">rpm</code> command to create a package, an RPM file, from any packages it would erase. Note that this option will not create a complete package. You will not be able to reinstall a package created by the <code class="option">--repackage</code> option. At best, the <code class="option">--repackage</code> option provides a backup of the old package, from which you could create a working package. Be careful with the <code class="option">--repackage</code> option.
+ </div><div class="para">
+ For example, the following command shows how to upgrade a package with the <code class="option">--repackage</code> option.
+ </div><pre class="screen">
+<strong class="userinput"><code>rpm -U --repackage jpilot-0.99.2-8.i386.rpm</code></strong></pre><div class="note"><div class="admonition_header"><h2>Consistent Package Names</h2></div><div class="admonition"><div class="para">
+ Upgrading and freshening depend on versions of a particular package keeping the same base package name between versions. For most packages this is true, but some packages violate this convention. For example, the Java programming developer's kit (JDK) uses the name <code class="filename">jdk-1.3.1_01.i386.rpm</code> for the 1.3.1 version but changes to <code class="filename">j2sdk-1_4_0_01-fcs-linux-i386.rpm</code> for the 1.4.0 version.
+ </div></div></div><div class="para">
+ Watch out for package-name changes like this.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch03s02.html"><strong>Înapoi</strong>3.2. Upgrading and Installing Software</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch03s02s02s02.html"><strong>Înainte</strong>3.2.2.2. Smart Upgrades</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch03s02s02s02.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch03s02s02s02.html
new file mode 100644
index 0000000..9b87223
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch03s02s02s02.html
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.2.2.2. Smart Upgrades</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch03s02s02.html" title="3.2.2. Upgrading packages" /><link rel="prev" href="ch03s02s02.html" title="3.2.2. Upgrading packages" /><link rel="next" href="ch03s02s03.html" title="3.2.3. Freshening up" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch03s02s02.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch03s02s03.html"><strong>ÃŽnainte</strong></a>
</li></ul><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id770589" class="title">Smart Upgrades</h1></div></div></div><div class="para">
+ The <code class="command">rpm</code> command really shines in the upgrade process. Not only can you upgrade a package with one simple command, but the <code class="command">rpm</code> command has some built-in smarts that really help.
+ </div><div class="para">
+ When upgrading, the <code class="command">rpm</code> command checks each file in the package. It actually compares checksums of the files. An MD5 checksum is a small value computed from the data in a file. Any change to a file results in a different checksum value.
+ </div><div class="para">
+ The <code class="command">rpm</code> command compares the checksums of three versions of each file: the version of the file from the old package, the version of the file in the new package, and the version of the file on disk.
+ </div><div class="para">
+ The <code class="command">rpm</code> command looks at all three versions of the files to handle the common case where you may have edited a configuration file on disk. This is where the <code class="command">rpm</code> command starts working with some upgrade rules. Note that this special processing only applies to files marked as configuration files within the RPM. <a class="xref" href="ch-specfiles.html">Cap. 9, <em>Working with Spec Files</em></a> covers how to mark files as configuration files.
+ </div><div class="para">
+ If the file on disk is identical to the file in the original package, meaning you have not changed the file, the <code class="command">rpm</code> command simply installs the file from the new version of the package on top of the old file.
+ </div><div class="para">
+ If the original package configuration file and the new package file are the same, that is, the file has not changed between the package versions, but the configuration file has been changed on disk, the <code class="command">rpm</code> command leaves that file alone. The <code class="command">rpm</code> command makes the assumption that if the file hasn’t changed between versions of the package, and you have modified the file, chances are your file will work with the new package. This takes care of the common case where you have edited an application’s configuration files.
+ </div><div class="para">
+ But if the file on disk is different from the original version of the file, and the file on disk is different from the new version of the file, the <code class="command">rpm</code> command installs the new version of the file on top of your changed version. This is because the new version of the file is known to work with the new package. The <code class="command">rpm</code> command saves your work by backing up your modified configuration file, renaming the file with a new <code class="filename">.rpmsave</code> extension. The <code class="command">rpm</code> command also warns you that it is backing up your modified file with a message that tells you the old file name and the new file name.
+ </div><div class="para">
+ If the RPM package uses the option <code class="command">%config(noreplace)</code> with the file, then the <code class="command">rpm</code> command will store the new file with a <code class="filename">rpm</code>new extension if you have modified the file on disk.
+ </div><div class="para">
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch03s02s02.html"><strong>Înapoi</strong>3.2.2. Upgrading packages</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch03s02s03.html"><strong>Înainte</strong>3.2.3. Freshening up</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch03s02s03.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch03s02s03.html
new file mode 100644
index 0000000..78e99f2
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch03s02s03.html
@@ -0,0 +1,17 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.2.3. Freshening up</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch03s02.html" title="3.2. Upgrading and Installing Software" /><link rel="prev" href="ch03s02s02s02.html" title="3.2.2.2. Smart Upgrades" /><link rel="next" href="ch03s02s04.html" title="3.2.4. Installing Packages" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch03s02s02s02.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch03s02s04.html"><strong>Ã
Žnainte</strong></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id879542" class="title">Freshening up</h1></div></div></div><div class="para">
+ A freshen operation means to install a new version of a package only if you have already installed another version of the package. Thus, a freshen operation is very similar to the upgrade operation except that a freshen requires you to have previously installed the package, while an upgrade can install a package for the first time. The basic syntax for freshening a package is to use the <code class="option">-F</code> option.
+ </div><pre class="screen">
+<strong class="userinput"><code>rpm -F <em class="replaceable"><code>package_name</code></em></code></strong></pre><div class="para">
+ You can also use the <code class="option">--freshen</code> long option in place of <code class="option">-F</code>.
+ </div><div class="para">
+ As with upgrading, the options to the <code class="command">rpm</code> command are the same, except for the <code class="option">-F</code> or <code class="option">--freshen</code> option that indicates the operation. These are the options discussed in the sections on upgrading and installing software.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch03s02s02s02.html"><strong>Înapoi</strong>3.2.2.2. Smart Upgrades</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch03s02s04.html"><strong>Înainte</strong>3.2.4. Installing Packages</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch03s02s04.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch03s02s04.html
new file mode 100644
index 0000000..6010a91
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch03s02s04.html
@@ -0,0 +1,21 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.2.4. Installing Packages</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch03s02.html" title="3.2. Upgrading and Installing Software" /><link rel="prev" href="ch03s02s03.html" title="3.2.3. Freshening up" /><link rel="next" href="ch03s02s05.html" title="3.2.5. Installing Over the Internet" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch03s02s03.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch03s02s05.html"><strong>Ã
Žnainte</strong></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id879598" class="title">Installing Packages</h1></div></div></div><div class="para">
+ The <code class="option">–i</code> or <code class="option">--install</code> option tells the <code class="command">rpm</code> command to run an installation operation, which, as you’d suspect, installs packages. The basic syntax is:
+ </div><pre class="screen">
+<strong class="userinput"><code>rpm –i <em class="replaceable"><code>filename.rpm</code></em></code></strong></pre><div class="para">
+ For example:
+ </div><pre class="screen">
+<strong class="userinput"><code>rpm –i jikes-1.16-1.i386.rpm</code></strong></pre><div class="warning"><div class="admonition_header"><h2>Use Upgrade, Rather Than Install</h2></div><div class="admonition"><div class="para">
+ You should normally install packages with <code class="command">rpm</code> <code class="option">-U</code>, not <code class="command">rpm</code> <code class="option">-i</code>. One of the main reasons is that <code class="command">rpm</code> <code class="option">-i</code> allows you to install multiple instances of the same (identical) package. This is usually not what you want.
+ </div></div></div><div class="para">
+ The <code class="command">rpm –i</code> command works with the installation options discussed previously. The <code class="option">–U</code>, <code class="option">-F</code> and <code class="option">–i</code> options all accept mostly the same options, except as discussed previously.
+ </div><div class="para">
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch03s02s03.html"><strong>Înapoi</strong>3.2.3. Freshening up</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch03s02s05.html"><strong>Înainte</strong>3.2.5. Installing Over the Internet</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch03s02s05.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch03s02s05.html
new file mode 100644
index 0000000..61afc1f
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch03s02s05.html
@@ -0,0 +1,41 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.2.5. Installing Over the Internet</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch03s02.html" title="3.2. Upgrading and Installing Software" /><link rel="prev" href="ch03s02s04.html" title="3.2.4. Installing Packages" /><link rel="next" href="ch03s02s05s02.html" title="3.2.5.2. Installing Using HTTP" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch03s02s04.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch03s02s05s02.html"><s
trong>ÃŽnainte</strong></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id630154" class="title">Installing Over the Internet</h1></div></div></div><div class="para">
+ All the commands to install packages covered so far assume that you have a local RPM file that you want to install. This is by far the most common case, but you can also use the <code class="command">rpm</code> command to install packages available on a network. With the <code class="command">rpm</code> command, you can get the packages to install by using the FTP or HTTP network protocols.
+ </div><div class="para">
+ With the File Transfer Protocol (FTP), the <code class="command">rpm</code> command connects to an FTP file server, downloads the named package, and installs that package. With the HyperText Transfer Protocol (HTTP) used for Web pages, the <code class="command">rpm</code> command connects to a Web server, downloads the named package, and installs that package.
+ </div><div class="warning"><div class="admonition_header"><h2>Name Spoofing</h2></div><div class="admonition"><div class="para">
+ When using either FTP or HTTP, you need to provide the name of the remote server. An attack on your system can compromise the system of converting server host names into network addresses, thus spoofing the <code class="command">rpm</code> command into installing a malicious package from the wrong host.
+ </div></div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id630205" class="title">Installing Using FTP</h1></div></div></div><div class="para">
+ The key to making the network protocols work with the <code class="command">rpm</code> command is that you need to create a URL for the remote file name. The basic format of the command follows:
+ </div><pre class="screen">
+<strong class="userinput"><code>rpm -i <em class="replaceable"><code>ftp://hostname/path/to/file/filename.rpm</code></em></code></strong></pre><div class="para">
+ Note the use of ftp: in the URL for the file.
+ </div><div class="para">
+ For example, the following downloads a package from an IBM FTP server.
+ </div><pre class="screen">
+<strong class="userinput"><code>rpm -i ftp://www-126.ibm.com/pub/jikes/jikes-1.16-1.src.rpm</code></strong></pre><div class="para">
+ Many FTP servers require users to log in. If you do not pass a user name and password on the <code class="command">rpm</code> command line, the <code class="command">rpm</code> command will prompt you for the missing data.
+ </div><div class="para">
+ You can add a user name prior to the host name, separating the user name from the host name with an at sign, @. For example:
+ </div><pre class="screen">
+<strong class="userinput"><code>rpm -i ftp://unclejoe@www-126.ibm.com/pub/jikes/jikes-1.16-1.src.rpm</code></strong></pre><div class="para">
+ In this case, the user name is unclejoe.
+ </div><div class="note"><div class="admonition_header"><h2>Credentials are Examples</h2></div><div class="admonition"><div class="para">
+ These examples do not show valid user names or passwords.
+ </div></div></div><div class="para">
+ With just a user name, the <code class="command">rpm</code> command will prompt you for the password. You can also include the password on the <code class="command">rpm</code> command line. Separate the user name from the password with a colon (:).
+ </div><div class="para">
+ For example:
+ </div><pre class="screen">
+<strong class="userinput"><code>rpm -i ftp://unclejoe:workers@www-126.ibm.com/pub/jikes/jikes-1.16-1.src.rpm</code></strong></pre><div class="para">
+ In this case, the user name is unclejoe and the password is workers.
+ </div><div class="para">
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch03s02s04.html"><strong>Înapoi</strong>3.2.4. Installing Packages</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch03s02s05s02.html"><strong>Înainte</strong>3.2.5.2. Installing Using HTTP</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch03s02s05s02.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch03s02s05s02.html
new file mode 100644
index 0000000..2e16474
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch03s02s05s02.html
@@ -0,0 +1,13 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.2.5.2. Installing Using HTTP</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch03s02s05.html" title="3.2.5. Installing Over the Internet" /><link rel="prev" href="ch03s02s05.html" title="3.2.5. Installing Over the Internet" /><link rel="next" href="ch03s02s06.html" title="3.2.6. Installing source RPMs" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch03s02s05.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch03s02s06.html">
<strong>ÃŽnainte</strong></a></li></ul><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id853762" class="title">Installing Using HTTP</h1></div></div></div><div class="para">
+ The <code class="command">rpm</code> command supports the HTTP protocol, used by most Web servers, as well as FTP. Similar to accessing a file via FTP, you need to pass the <code class="command">rpm</code> command a URL identifying the file. For example:
+ </div><pre class="screen">
+<strong class="userinput"><code>rpm –i http://ftp.redhat.com/pub/contrib/noarch/SRPMS/Squeak-sources-3-1.src.rpm</code></strong></pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch03s02s05.html"><strong>Înapoi</strong>3.2.5. Installing Over the Internet</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch03s02s06.html"><strong>Înainte</strong>3.2.6. Installing source RPMs</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch03s02s06.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch03s02s06.html
new file mode 100644
index 0000000..c4d327c
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch03s02s06.html
@@ -0,0 +1,32 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.2.6. Installing source RPMs</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch03s02.html" title="3.2. Upgrading and Installing Software" /><link rel="prev" href="ch03s02s05s02.html" title="3.2.5.2. Installing Using HTTP" /><link rel="next" href="ch03s03.html" title="3.3. Removing Software" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch03s02s05s02.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch03s03.html"><strong>ÃŽna
inte</strong></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id853791" class="title">Installing source RPMs</h1></div></div></div><div class="para">
+ Source RPMs contain the source code used to build an application or programming library and the scripts used to build the software into the application or library. These scripts are called the recipes for building the software.
+ </div><div class="para">
+ Source RPMs usually contain program source code. They may also contain patches to program sources, scripts to build the program, special files used by desktop environments, icons, and other files considered to be part of the source code, such as programming guides.
+ </div><div class="note"><div class="admonition_header"><h2>Patch Files</h2></div><div class="admonition"><div class="para">
+ A patch is a file that contains just the differences between one version of a file and another. The differences include the actual text that has changed and enough contextual information that a program can locate where the changes are to take place. Usually, a patch is created with the <code class="command">diff</code> command, and the source code is patched with the <code class="command">patch</code> command.
+ </div></div></div><div class="para">
+ In most cases, each binary RPM will have a corresponding source RPM. This is not always true, however.
+ </div><div class="para">
+ One source RPM may contain enough shared program code to build multiple application RPMs. Furthermore, the source code is not available for all packages. Commercial applications, for example, rarely come with source code. In this case, obviously, no source RPMs are available. Or, a source RPM for a commercial application may provide no source code, but still provide a way to build the resulting application. See <a class="xref" href="ch-specfiles.html">Cap. 9, <em>Working with Spec Files</em></a> for more on the source files and options for not including the sources in a source RPM.
+ </div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id720372" class="title">Open-source Software</h1></div></div></div><div class="para">
+ Linux, and thousands of applications that run on Linux, are called open-source software. That’s because the program source code for Linux and these applications are available.
+ </div><div class="para">
+ Many users feel having access to the source code is vital, especially because:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Vendors may stop supporting a package. With the sources, you can conceivably maintain the packages yourself, or more likely, others can take up the task and maintain these crucial packages.
+ </div></li><li class="listitem"><div class="para">
+ Having the source code makes it easier to track down and fix security vulnerabilities, although malicious users also have access to the same source code.
+ </div></li><li class="listitem"><div class="para">
+ You can enhance and extend packages for which the program sources are available.
+ </div></li></ul></div><div class="para">
+ Linux applications are available under a variety of open-source licenses. (In fact, it may seem that there are as many licenses as packages.) See the site <a href="http://www.opensource.org/licenses/">http://www.opensource.org/licenses/</a> for details.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch03s02s05s02.html"><strong>Înapoi</strong>3.2.5.2. Installing Using HTTP</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch03s03.html"><strong>Înainte</strong>3.3. Removing Software</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch03s03.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch03s03.html
new file mode 100644
index 0000000..e5524ba
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch03s03.html
@@ -0,0 +1,48 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.3. Removing Software</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-using-rpm.html" title="Cap. 3. Using RPM" /><link rel="prev" href="ch03s02s06.html" title="3.2.6. Installing source RPMs" /><link rel="next" href="ch03s03s02.html" title="3.3.2. Removing multiple packages at a time" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch03s02s06.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch03s03s02.html"><strong>
ÃŽnainte</strong></a></li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id715184" class="title">Removing Software</h1></div></div></div><div class="para">
+ The <code class="command">rpm</code> command is good for more than just installing and upgrading software packages. Many times, you will need to remove packages as well.
+ </div><div class="para">
+ To remove a package, use the <code class="option">-e</code> option to the <code class="command">rpm</code> command, short for erase. The basic syntax follows:
+ </div><pre class="screen">
+<strong class="userinput"><code>rpm -e <em class="replaceable"><code>package_name</code></em></code></strong></pre><div class="note"><div class="admonition_header"><h2>Use Package Names, Not File Names</h2></div><div class="admonition"><div class="para">
+ When erasing or removing packages, use the package name, not the RPM file name. If you think about this, it makes sense. You don't always have the original RPM files when the time comes to remove a package.
+ </div></div></div><div class="para">
+ For example:
+ </div><pre class="screen">
+<strong class="userinput"><code>rpm -e jikes-1.16-1</code></strong></pre><div class="para">
+ This example removes the <code class="filename">jikes-1.16-1</code> package used in previous examples.
+ </div><div class="note"><div class="admonition_header"><h2><code class="systemitem">root</code> Access is Required</h2></div><div class="admonition"><div class="para">
+ You will need to use the <code class="systemitem">root</code> account, or super user, to remove most packages. This is because the package files themselves are protected. In addition, the RPM database is protected.
+ </div></div></div><div class="para">
+ This is only natural, since most RPMs are used to install system-level commands and applications.
+ </div><div class="para">
+ When removing a package, the <code class="command">rpm</code> command first checks that no other packages depend on the package you intend to remove. This is very important, since you otherwise can damage your Linux system by inadvertently removing packages needed by the rest of the system.
+ </div><div class="para">
+ The <code class="command">rpm</code> command supports the <code class="option">--test</code> option for removing packages as well as when installing. As with installing, the <code class="option">--test</code> option tells the <code class="command">rpm</code> command to test to see whether it can remove the given package but not to force the removal.
+ </div><div class="para">
+ For example, if you try to remove the very important-looking <code class="filename">syslinux-1.75-3</code> package, you can use the <code class="option">--test</code> option to see if this works.
+ </div><div class="para">
+ For example:
+ </div><pre class="screen">
+<strong class="userinput"><code>rpm -e --test syslinux-1.75-3</code></strong></pre><div class="para">
+ This command will issue an error such as the following:
+ </div><pre class="screen">
+<code class="computeroutput">error: Failed dependencies: syslinux is needed by (installed) mkbootdisk-1.4.8-1</code></pre><div class="note"><div class="admonition_header"><h2>Alternative Option Name</h2></div><div class="admonition"><div class="para">
+ When removing packages, you can use the long option name, <code class="option">--erase</code>, in place of <code class="option">–e</code>.
+ </div></div></div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id780124" class="title">Checking that the package has been removed</h1></div></div></div><div class="para">
+ As before, you can use the <code class="command">rpm</code> <code class="option">–q</code> command to query whether a package is installed. After running the <code class="command">rpm</code> <code class="option">–e</code> command, you can run the <code class="command">rpm</code> <code class="option">–q</code> command to check whether the package has been removed. If the <code class="command">rpm</code> <code class="option">–q</code> command shows that the package is not installed, that tells you the erase operation has worked.
+ </div><div class="para">
+ For example:
+ </div><pre class="screen">
+<strong class="userinput"><code># rpm -q jikes</code></strong></pre><pre class="screen">
+<code class="computeroutput">jikes-1.16-1</code></pre><pre class="screen">
+<strong class="userinput"><code># rpm -e jikes-1.16-1 # rpm -q jikes</code></strong></pre><pre class="screen">
+<strong class="userinput"><code>package jikes is not installed</code></strong></pre></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch03s02s06.html"><strong>Înapoi</strong>3.2.6. Installing source RPMs</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch03s03s02.html"><strong>Înainte</strong>3.3.2. Removing multiple packages at a time</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch03s03s02.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch03s03s02.html
new file mode 100644
index 0000000..9fc1d02
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch03s03s02.html
@@ -0,0 +1,15 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.3.2. Removing multiple packages at a time</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch03s03.html" title="3.3. Removing Software" /><link rel="prev" href="ch03s03.html" title="3.3. Removing Software" /><link rel="next" href="ch03s03s03.html" title="3.3.3. Options when removing packages" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch03s03.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch03s03s03.html"><strong>ÃŽnainte</strong></
a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id726603" class="title">Removing multiple packages at a time</h1></div></div></div><div class="para">
+ You can remove multiple packages at once by listing each package consecutively on the command line. For example:
+ </div><pre class="screen">
+<strong class="userinput"><code>rpm -e aspell-en-ca-0.33.7.1-16 aspell-en-gb-0.33.7.1-16</code></strong></pre><div class="para">
+ This command removes the <code class="filename">aspell-en-ca-0.33.7.1-16</code> and <code class="filename">aspell-en-gb-0.33.7.1-16</code> packages.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch03s03.html"><strong>Înapoi</strong>3.3. Removing Software</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch03s03s03.html"><strong>Înainte</strong>3.3.3. Options when removing packages</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch03s03s03.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch03s03s03.html
new file mode 100644
index 0000000..b408ad3
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch03s03s03.html
@@ -0,0 +1,26 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.3.3. Options when removing packages</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch03s03.html" title="3.3. Removing Software" /><link rel="prev" href="ch03s03s02.html" title="3.3.2. Removing multiple packages at a time" /><link rel="next" href="ch03s04.html" title="3.4. Other rpm Command Options" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch03s03s02.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch03s04.html"><strong>ÃŽnai
nte</strong></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id740883" class="title">Options when removing packages</h1></div></div></div><div class="para">
+ The <code class="option">--allmatches</code> option tells the <code class="command">rpm</code> command to remove all packages with names that match the names you pass on the command line. If you do not use the <code class="option">--allmatches</code> option, the <code class="command">rpm</code> command will issue an error if more than one package matches the name or names you pass on the command line.
+ </div><div class="para">
+ The <code class="option">--nodeps</code> option tells the <code class="command">rpm</code> command to skip the test of dependencies. Use this option when you really, really, want to uninstall a package.
+ </div><div class="warning"><div class="admonition_header"><h2>Unsafe Commands</h2></div><div class="admonition"><div class="para">
+ Using any option that does not perform the full removal of the package, or skips some of the checks built into the <code class="command">rpm</code> command, can result in damage to your Linux system. Use these options with care.
+ </div></div></div><div class="para">
+ The <code class="option">--repackage</code> option, described previously, tells the <code class="command">rpm</code> command to create a package, an RPM file, from any packages it would erase. These packages will appear in the default repackage directory, which is normally <code class="filename">/var/spool/repackage/</code>. Check your RPM settings to be sure of the directory configured on your system.
+ </div><div class="note"><div class="admonition_header"><h2>Repackaged Files</h2></div><div class="admonition"><div class="para">
+ Packages created with the <code class="option">--repackage</code> option are not full packages. You cannot install these packages.
+ </div></div></div><div class="para">
+ Similar to the options when installing or upgrading packages, you can use the <code class="option">--noscripts</code> and <code class="option">--notriggers</code> options when removing packages. The <code class="option">--noscripts</code> option tells the <code class="command">rpm</code> command not to run any uninstallation scripts. You can refine this by using either <code class="option">--nopreun</code> or <code class="option">--nopostun</code> in place of the <code class="option">--noscripts</code> option.
+ </div><div class="para">
+ The <code class="option">--nopreun</code> option tells the <code class="command">rpm</code> command not to run the pre-uninstallation scripts. The <code class="option">--nopostun</code> option tells the <code class="command">rpm</code> command not to run the post-uninstallation scripts.
+ </div><div class="para">
+ The <code class="option">--notriggers</code> option works in a similar fashion. The <code class="option">--notriggers</code> option tells the <code class="command">rpm</code> command not to execute any triggers. For a finer grain of control, use <code class="option">--notriggerun</code> to prevent any uninstallation triggers and <code class="option">--notriggerpostun</code> to prevent any post-uninstallation triggers.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch03s03s02.html"><strong>Înapoi</strong>3.3.2. Removing multiple packages at a time</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch03s04.html"><strong>Înainte</strong>3.4. Other rpm Command Options</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch03s04.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch03s04.html
new file mode 100644
index 0000000..9b1ade9
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch03s04.html
@@ -0,0 +1,55 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.4. Other rpm Command Options</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-using-rpm.html" title="Cap. 3. Using RPM" /><link rel="prev" href="ch03s03s03.html" title="3.3.3. Options when removing packages" /><link rel="next" href="ch03s05.html" title="3.5. Summary" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch03s03s03.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch03s05.html"><strong>ÃŽnainte</strong></a></li></u
l><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id730096" class="title">Other <code class="command">rpm</code> Command Options</h1></div></div></div><div class="para">
+ Options such as <code class="option">-v</code> (for more verbose output) work with the <code class="command">rpm</code> command for installing, removing, and upgrading packages, as well as most other uses of the <code class="command">rpm</code> command.
+ </div><div class="para">
+ Other <code class="command">rpm</code> command options, which work with most RPM actions, include <code class="option">--quiet</code> to turn off most output except for errors, and <code class="option">--root</code>, covered previously.
+ </div><div class="para">
+ The <code class="option">--rcfile</code> option tells the <code class="command">rpm</code> command to use one or more other files to initialize the RPM system. These files tell the <code class="command">rpm</code> command the system architecture, operating system, and default location of the RPM database, among a host of other settings.
+ </div><div class="note"><div class="admonition_header"><h2><code class="filename">rc</code> Files</h2></div><div class="admonition"><div class="para">
+ The term <code class="filename">rc</code> comes from Unix shells, with initialization files such as <code class="filename">.cshrc</code> for the C shell, <code class="command">csh</code>. The term <code class="filename">rc</code> was originally a shorthand for run commands. An <code class="filename">rc</code> is a file of commands that run when the application starts up. For example, the C shell, <code class="command">csh</code>, runs the commands in file named <code class="filename">.cshrc</code> when the shell starts.
+ </div></div></div><div class="para">
+ In most cases, the application looks in the user home directory for a specific file tied to the application. For the <code class="command">rpm</code> command, this file is <code class="filename">.rpmrc</code>. The leading period makes the file hidden for most directory listings.
+ </div><div class="para">
+ In addition to the user-level file of commands, most applications supporting this mechanism have a way for site administrators to customize the command for all users. For example, your system may have a file named <code class="filename">/etc/rpmrc</code> (with no leading period) that customizes the <code class="command">rpm</code> command for all users on your system. See <a class="xref" href="ch-customizing-rpm.html">Cap. 20, <em>Customizing RPM Behavior</em></a> for a more in-depth look at the chain of these files.
+ </div><div class="para">
+ The syntax for the <code class="option">--rcfile</code> option is
+ </div><div class="para">
+ <code class="option">--rcfile</code> <em class="replaceable"><code>filename</code></em>
+ </div><div class="para">
+ You can also supply more than one file name. This syntax follows:
+ </div><div class="para">
+ <code class="option">--rcfile</code> <em class="replaceable"><code>filename1:filename2:filename3</code></em>
+ </div><div class="para">
+ Separate each file name with a colon.
+ </div><div class="para">
+ With Red Hat Linux, the default set of initialization files are:
+ </div><pre class="screen">
+<code class="computeroutput">/usr/lib/rpm/rpmrc:/usr/lib/rpm/redhat/rpmrc:/etc/rpmrc:~/.rpmrc</code></pre><div class="note"><div class="admonition_header"><h2>Tilde (~) Denotes Home Directory</h2></div><div class="admonition"><div class="para">
+ The <code class="filename">~/.rpmrc</code> means to look in the user's home directory for a file named <code class="filename">rpmrc</code>.
+ </div><div class="para">
+ You can use the <code class="option">--showrc</code> option to list all the <code class="filename">rc</code> settings.
+ </div></div></div><div class="note"><div class="admonition_header"><h2>The <code class="option">--showrc</code> Option</h2></div><div class="admonition"><div class="para">
+ See <a class="xref" href="ch-customizing-rpm.html">Cap. 20, <em>Customizing RPM Behavior</em></a> for more on the <code class="option">--showrc</code> option.
+ </div></div></div><div class="para">
+ The <code class="option">--version</code> option tells the <code class="command">rpm</code> command to print out the version number of the command and then exit. For example:
+ </div><pre class="screen">
+<strong class="userinput"><code>rpm --version</code></strong></pre><div class="para">
+ This command prints out a version number, like the following:
+ </div><pre class="screen">
+<code class="computeroutput">RPM version 4.1</code></pre><div class="para">
+ The <code class="option">--dbpath</code> option, mentioned previously, tells the <code class="command">rpm</code> command to use a different RPM database. This is useful when testing a complete system install, where you want to change the RPM database but don't want that to affect your running Linux system. In this case, you can use a different RPM database and test out your changes. The basic syntax for this option is:
+ </div><div class="para">
+ <code class="option">--dbpath</code> <em class="replaceable"><code>directory_name</code></em>
+ </div><div class="para">
+ The <code class="option">--pipe</code> option tells the <code class="command">rpm</code> command to send, or pipe, its output to another program. The syntax for this option is:
+ </div><div class="para">
+ <code class="option">--pipe</code> <em class="replaceable"><code>command_to_send_out_to</code></em>
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch03s03s03.html"><strong>Înapoi</strong>3.3.3. Options when removing packages</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch03s05.html"><strong>Înainte</strong>3.5. Summary</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch03s05.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch03s05.html
new file mode 100644
index 0000000..02c99f4
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch03s05.html
@@ -0,0 +1,72 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.5. Summary</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-using-rpm.html" title="Cap. 3. Using RPM" /><link rel="prev" href="ch03s04.html" title="3.4. Other rpm Command Options" /><link rel="next" href="ch-using-rpm-db.html" title="Cap. 4. Using the RPM Database" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch03s04.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch-using-rpm-db.html"><strong>ÃŽnainte
</strong></a></li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id872753" class="title">Summary</h1></div></div></div><div class="para">
+ This chapter covered the easy part of managing packages, the common actions of installing, removing, and upgrading software.
+ </div><div class="para">
+ The <code class="command">rpm</code> <code class="option">–e</code> command removes packages. The <code class="command">rpm</code> <code class="option">–U</code> command upgrades packages by installing new packages and removing old versions of all the packages upgraded. RPM upgrades also work for installing new packages. The <code class="command">rpm</code> <code class="option">–F</code> command freshens packages. This command only upgrades a package if an older version of the package has already been installed. The <code class="command">rpm</code> <code class="option">–i</code> command installs packages.
+ </div><div class="para">
+ The table below summarizes the <code class="command">rpm</code> command-line options for installing, removing, and upgrading packages.
+ </div><div class="table" id="tb-rpm-command-options"><h6>Tabel 3.3. Installing, Removing, and Upgrading with the <code class="command">rpm</code> command</h6><div class="table-contents"><table summary="Installing, Removing, and Upgrading with the rpm command" border="1"><colgroup><col class="Command" width="50%" /><col class="Usage" width="50%" /></colgroup><thead><tr><th>
+ Command
+ </th><th>
+ Usage
+ </th></tr></thead><tbody><tr><td>
+ <div class="para">
+ <code class="command">rpm –i <em class="replaceable"><code>install_options package_files</code></em></code>
+ </div>
+
+ </td><td>
+ <div class="para">
+ Install packages.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ <code class="command">rpm –e <em class="replaceable"><code>remove_options packages</code></em></code>
+ </div>
+
+ </td><td>
+ <div class="para">
+ Erase, remove, packages.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ <code class="command">rpm –U <em class="replaceable"><code>install_options package_files</code></em></code>
+ </div>
+
+ </td><td>
+ <div class="para">
+ Upgrade or install packages. Use this option for installations.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ <code class="command">rpm –Uvh <em class="replaceable"><code>install_options package_files</code></em></code>
+ </div>
+
+ </td><td>
+ <div class="para">
+ Upgrade or install packages with extra output. This is the recommended command to install packages.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ <code class="command">rpm –F <em class="replaceable"><code>install_options package_files</code></em></code>
+ </div>
+
+ </td><td>
+ <div class="para">
+ Freshen packages.
+ </div>
+
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ Unfortunately, modern system management gets more complex than that. The next chapter delves into package dependencies and the nightmare you can get into when one package depends on another that then depends on another, ad infinitum.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch03s04.html"><strong>Înapoi</strong>3.4. Other rpm Command Options</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch-using-rpm-db.html"><strong>Înainte</strong>Cap. 4. Using the RPM Database</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch04s02s03.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch04s02s03.html
new file mode 100644
index 0000000..c887f47
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch04s02s03.html
@@ -0,0 +1,101 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>4.2.3. Listing the files in a package</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="RPM_Guide-Using_RPM_DB-getting_information.html" title="4.2. Getting Information on Packages" /><link rel="prev" href="RPM_Guide-Using_RPM_DB-package_groups.html" title="4.2.2. Package groups" /><link rel="next" href="RPM_Guide-Using_RPM_DB-listing_conf_files.html" title="4.2.4. Listing the configuration files for a package" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="RPM_Gui
de-Using_RPM_DB-package_groups.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="RPM_Guide-Using_RPM_DB-listing_conf_files.html"><strong>ÃŽnainte</strong></a></li></ul><div class="section"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id880051">4.2.3. Listing the files in a package</h3></div></div></div><div class="para">
+ The <code class="option">–l</code> (ell) option queries all the files in a package. You can also use the longer option, --list, in place of –l. The basic syntax is:
+ </div><div class="para">
+ rpm –ql package
+ </div><div class="para">
+ For example, to query the files in the tcsh package, you’ll see the following:
+ </div><div class="para">
+ <code class="command">rpm -ql tcsh</code>
+ </div><pre class="screen">
+ /bin/csh
+ /bin/tcsh
+ /usr/share/doc/tcsh-6.10
+ /usr/share/doc/tcsh-6.10/FAQ
+ /usr/share/doc/tcsh-6.10/Fixes
+ /usr/share/doc/tcsh-6.10/NewThings
+ /usr/share/doc/tcsh-6.10/complete.tcsh
+ /usr/share/doc/tcsh-6.10/eight-bit.txt
+ /usr/share/doc/tcsh-6.10/tcsh.html
+ /usr/share/doc/tcsh-6.10/tcsh.html/header.html
+ /usr/share/doc/tcsh-6.10/tcsh.html/index.html
+ /usr/share/doc/tcsh-6.10/tcsh.html/lists.html
+ /usr/share/doc/tcsh-6.10/tcsh.html/tcsh.man
+ /usr/share/doc/tcsh-6.10/tcsh.html/tcsh.man2html
+ /usr/share/doc/tcsh-6.10/tcsh.html/top.html
+ /usr/share/locale/de/LC_MESSAGES/tcsh
+ /usr/share/locale/el/LC_MESSAGES/tcsh
+ /usr/share/locale/es/LC_MESSAGES/tcsh
+ /usr/share/locale/fr/LC_MESSAGES/tcsh
+ /usr/share/locale/it/LC_MESSAGES/tcsh
+ /usr/share/locale/ja/LC_MESSAGES/tcsh
+ /usr/share/man/man1/tcsh.1.gz
+</pre><div class="note"><div class="admonition_header"><h2>Listing multiple packages</h2></div><div class="admonition"><div class="para">
+ You can pass more than one package name to this option, but it won’t tell you which package owns which file. Use the <code class="option">--filesbypkg</code> option to list files by package.
+ </div><div class="para">
+ For example:
+ </div><div class="para">
+ <code class="command">rpm -q --filesbypkg file openssh-clients</code>
+ </div><pre class="screen">
+ file /usr/bin/file
+ file /usr/share/magic
+ file /usr/share/magic.mgc
+ file /usr/share/magic.mime
+ file /usr/share/man/man1/file.1.gz
+ file /usr/share/man/man5/magic.5.gz
+ openssh-clients /etc/ssh/ssh_config
+ openssh-clients /usr/bin/sftp
+ openssh-clients /usr/bin/slogin
+ openssh-clients /usr/bin/ssh
+ openssh-clients /usr/bin/ssh-add
+ openssh-clients /usr/bin/ssh-agent
+ openssh-clients /usr/bin/ssh-keyscan
+ openssh-clients /usr/share/man/man1/sftp.1.gz
+ openssh-clients /usr/share/man/man1/slogin.1.gz
+ openssh-clients /usr/share/man/man1/ssh-add.1.gz
+ openssh-clients /usr/share/man/man1/ssh-agent.1.gz
+ openssh-clients /usr/share/man/man1/ssh-keyscan.1.gz
+ openssh-clients /usr/share/man/man1/ssh.1.gz
+</pre><div class="para">
+ Use this option without –l, because the –l option will also list the files alone, without any package name.
+ </div></div></div><div class="para">
+ The –v (verbose) option can give you more information on the files when used with the various query options. For example:
+ </div><div class="para">
+ <code class="command">rpm -qlv tcsh</code>
+ </div><pre class="screen">
+lrwxrwxrwx 1 root root 4 Dec 15 2009 /bin/csh -> tcsh
+-rwxr-xr-x 1 root root 386984 Dec 15 2009 /bin/tcsh
+drwxr-xr-x 2 root root 0 Dec 15 2009 /usr/share/doc/tcsh-6.17
+-rw-r--r-- 1 root root 17782 Mar 2 2006 /usr/share/doc/tcsh-6.17/BUGS
+-rw-r--r-- 1 root root 12773 May 19 2004 /usr/share/doc/tcsh-6.17/FAQ
+-rw-r--r-- 1 root root 85246 Jul 10 2009 /usr/share/doc/tcsh-6.17/Fixes
+-rw-r--r-- 1 root root 6518 Oct 2 1998 /usr/share/doc/tcsh-6.17/NewThings
+-rw-r--r-- 1 root root 11809 May 19 2004 /usr/share/doc/tcsh-6.17/WishList
+-rw-r--r-- 1 root root 56615 Oct 1 2007 /usr/share/doc/tcsh-6.17/complete.tcsh
+-rw-r--r-- 1 root root 46682 Dec 15 2009 /usr/share/locale/de/LC_MESSAGES/tcsh
+-rw-r--r-- 1 root root 48387 Dec 15 2009 /usr/share/locale/el/LC_MESSAGES/tcsh
+-rw-r--r-- 1 root root 45670 Dec 15 2009 /usr/share/locale/en/LC_MESSAGES/tcsh
+-rw-r--r-- 1 root root 48234 Dec 15 2009 /usr/share/locale/es/LC_MESSAGES/tcsh
+-rw-r--r-- 1 root root 45130 Dec 15 2009 /usr/share/locale/et/LC_MESSAGES/tcsh
+-rw-r--r-- 1 root root 47757 Dec 15 2009 /usr/share/locale/fi/LC_MESSAGES/tcsh
+-rw-r--r-- 1 root root 47978 Dec 15 2009 /usr/share/locale/fr/LC_MESSAGES/tcsh
+-rw-r--r-- 1 root root 49085 Dec 15 2009 /usr/share/locale/it/LC_MESSAGES/tcsh
+-rw-r--r-- 1 root root 33848 Dec 15 2009 /usr/share/locale/ja/LC_MESSAGES/tcsh
+-rw-r--r-- 1 root root 45160 Dec 15 2009 /usr/share/locale/pl/LC_MESSAGES/tcsh
+-rw-r--r-- 1 root root 46148 Dec 15 2009 /usr/share/locale/ru/LC_MESSAGES/tcsh
+-rw-r--r-- 1 root root 45492 Dec 15 2009 /usr/share/locale/uk/LC_MESSAGES/tcsh
+lrwxrwxrwx 1 root root 9 Dec 15 2009 /usr/share/man/man1/csh.1.gz -> tcsh.1.gz
+-rw-r--r-- 1 root root 63984 Dec 15 2009 /usr/share/man/man1/tcsh.1.gz
+</pre><div class="para">
+ This information is the same as a long listing on the files.
+ </div><div class="para">
+ As you can see, the <code class="option">–l</code> option results in quite a lot of output. In some cases, though, you aren’t interested in documentation and other miscellaneous files in the package. It’s the commands and libraries that cause the most package-related problems. To help with this, you can use a series of rpm options to list only certain types of files.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="RPM_Guide-Using_RPM_DB-package_groups.html"><strong>Înapoi</strong>4.2.2. Package groups</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="RPM_Guide-Using_RPM_DB-listing_conf_files.html"><strong>Înainte</strong>4.2.4. Listing the configuration files for a pack...</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch04s02s05.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch04s02s05.html
new file mode 100644
index 0000000..95225b9
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch04s02s05.html
@@ -0,0 +1,35 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>4.2.5. Listing the documentation files for a package</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="RPM_Guide-Using_RPM_DB-getting_information.html" title="4.2. Getting Information on Packages" /><link rel="prev" href="RPM_Guide-Using_RPM_DB-listing_conf_files.html" title="4.2.4. Listing the configuration files for a package" /><link rel="next" href="RPM_Guide-Using_RPM_DB-file_state.html" title="4.2.6. Listing the state of the files in a package" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a ac
cesskey="p" href="RPM_Guide-Using_RPM_DB-listing_conf_files.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="RPM_Guide-Using_RPM_DB-file_state.html"><strong>ÃŽnainte</strong></a></li></ul><div class="section"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id554170">4.2.5. Listing the documentation files for a package</h3></div></div></div><div class="para">
+ Similarly to the <code class="option">–c</code> option, the <code class="option">–d</code> option tells the <code class="command">rpm –q</code> command to list just the documentation files for a package. The basic syntax is:
+ </div><div class="para">
+ <code class="command">rpm –qd <em class="replaceable"><code>package_name</code></em></code>
+ </div><div class="para">
+ For example:
+ </div><div class="para">
+ <code class="command">rpm -qd tcsh</code>
+ </div><pre class="screen">
+ /usr/share/doc/tcsh-6.10/FAQ
+ /usr/share/doc/tcsh-6.10/Fixes
+ /usr/share/doc/tcsh-6.10/NewThings
+ /usr/share/doc/tcsh-6.10/complete.tcsh
+ /usr/share/doc/tcsh-6.10/eight-bit.txt
+ /usr/share/doc/tcsh-6.10/tcsh.html/header.html
+ /usr/share/doc/tcsh-6.10/tcsh.html/index.html
+ /usr/share/doc/tcsh-6.10/tcsh.html/lists.html
+ /usr/share/doc/tcsh-6.10/tcsh.html/tcsh.man
+ /usr/share/doc/tcsh-6.10/tcsh.html/tcsh.man2html
+ /usr/share/doc/tcsh-6.10/tcsh.html/top.html
+ /usr/share/man/man1/tcsh.1.gz
+</pre><div class="note"><div class="admonition_header"><h2>Getting more information</h2></div><div class="admonition"><div class="para">
+ You can add the –v option to all of the file-listing options to get more information.
+ </div></div></div><div class="para">
+ You can also use the longer option, <code class="option">--docfiles</code>, in place of <code class="option">–d</code>.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="RPM_Guide-Using_RPM_DB-listing_conf_files.html"><strong>Înapoi</strong>4.2.4. Listing the configuration files for a pack...</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="RPM_Guide-Using_RPM_DB-file_state.html"><strong>Înainte</strong>4.2.6. Listing the state of the files in a package</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch04s03.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch04s03.html
new file mode 100644
index 0000000..2155e1f
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch04s03.html
@@ -0,0 +1,96 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>4.3. Other queries</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-using-rpm-db.html" title="Cap. 4. Using the RPM Database" /><link rel="prev" href="RPM_Guide-Using_RPM_DB-Other_Query_Format_Tags.html" title="4.2.17. Other Query Format Tags" /><link rel="next" href="RPM_Guide-Using_RPM_DB-Getting_information_on_package_files.html" title="4.4. Getting Information on Package Files" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="RPM_Guide-Usin
g_RPM_DB-Other_Query_Format_Tags.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="RPM_Guide-Using_RPM_DB-Getting_information_on_package_files.html"><strong>ÃŽnainte</strong></a></li></ul><div class="section"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="id543108">4.3. Other queries</h2></div></div></div><div class="para">
+ If what you’ve seen so far isn’t enough, the rpm command supports a number of extra queries, mostly of use to developers.
+ </div><div class="para">
+ Table 5-7 summarizes these extra queries.
+ </div><div class="para">
+ Table 5-7 Extra Queries
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Option
+ </div>
+
+ </td><td>
+ <div class="para">
+ Meaning
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --dump
+ </div>
+
+ </td><td>
+ <div class="para">
+ Dumps out extra information on files
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --fileid md5_id
+ </div>
+
+ </td><td>
+ <div class="para">
+ Queries for the package with the given MD5 digest
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --hdrid sha1_header_id
+ </div>
+
+ </td><td>
+ <div class="para">
+ Queries for the package with the given header identifier number, in SHA1 format
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --last
+ </div>
+
+ </td><td>
+ <div class="para">
+ Reorders the output of the rpm command to show the most recently-installed packages first
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --pkgid md5_id
+ </div>
+
+ </td><td>
+ <div class="para">
+ Queries for the package with the given MD5 package ID
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --querybynumber number
+ </div>
+
+ </td><td>
+ <div class="para">
+ Queries for the given entry, by number, in the RPM database
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --tid transaction_id
+ </div>
+
+ </td><td>
+ <div class="para">
+ Queries for the package or packages with the given transaction ID
+ </div>
+
+ </td></tr></tbody></table></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="RPM_Guide-Using_RPM_DB-Other_Query_Format_Tags.html"><strong>Înapoi</strong>4.2.17. Other Query Format Tags</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="RPM_Guide-Using_RPM_DB-Getting_information_on_package_files.html"><strong>Înainte</strong>4.4. Getting Information on Package Files</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch05s02.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch05s02.html
new file mode 100644
index 0000000..ce4b519
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch05s02.html
@@ -0,0 +1,148 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.2. Checking for Dependencies</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-dependencies.html" title="Cap. 5. Package Dependencies" /><link rel="prev" href="ch-dependencies.html" title="Cap. 5. Package Dependencies" /><link rel="next" href="ch05s02s02.html" title="5.2.2. Determining the capabilities a package provides" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-dependencies.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="
n" href="ch05s02s02.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id735799" class="title">Checking for Dependencies</h1></div></div></div><div class="para">
+ The rpm –q command queries the RPM database or RPM package files. With the right options to this command, you can check for the four types of package dependencies as well. These options are based on the concept of capabilities introduced previously.
+ </div><div class="para">
+ You can query what capabilities a package requires. You can also query what capabilities a package provides. You can query for the obsoleting and conflicting information as well. Furthermore, given a capability, you can query which packages require this capability as well as which packages provide this capability.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ There are quite a few more options you can use with the rpm –q command for querying packages. See <a class="xref" href="ch-using-rpm-db.html">Cap. 4, <em>Using the RPM Database</em></a> for more on querying packages and package files.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id675733" class="title">Determining the capabilities a package requires</h1></div></div></div><div class="para">
+ The first and most important step is to determine what capabilities a package requires. If all the required capabilities are met, you can safely install the package (barring other things that can go wrong, such as conflicts). The requires dependencies are by far the most important.
+ </div><div class="para">
+ The --requires option to the rpm –q command lists the capabilities a given package requires. The basic syntax is:
+ </div><div class="para">
+ rpm –q query_options --requires packages
+ </div><div class="para">
+ For example:
+ </div><div class="para">
+ $ rpm -qp --requires sendmail-8.12.5-7.i386.rpm
+ </div><div class="para">
+ /usr/sbin/alternatives
+ </div><div class="para">
+ rpmlib(VersionedDependencies) <= 3.0.3-1
+ </div><div class="para">
+ chkconfig >= 1.3
+ </div><div class="para">
+ /usr/sbin/useradd
+ </div><div class="para">
+ /bin/mktemp
+ </div><div class="para">
+ fileutils
+ </div><div class="para">
+ gawk
+ </div><div class="para">
+ sed
+ </div><div class="para">
+ sh-utils
+ </div><div class="para">
+ procmail
+ </div><div class="para">
+ bash >= 2.0
+ </div><div class="para">
+ /bin/sh
+ </div><div class="para">
+ /bin/sh
+ </div><div class="para">
+ /bin/sh
+ </div><div class="para">
+ /bin/sh
+ </div><div class="para">
+ /bin/sh
+ </div><div class="para">
+ rpmlib(PayloadFilesHavePrefix) <= 4.0-1
+ </div><div class="para">
+ rpmlib(CompressedFileNames) <= 3.0.4-1
+ </div><div class="para">
+ /bin/bash
+ </div><div class="para">
+ libcrypto.so.2
+ </div><div class="para">
+ libcrypt.so.1
+ </div><div class="para">
+ libc.so.6
+ </div><div class="para">
+ libc.so.6(GLIBC_2.0)
+ </div><div class="para">
+ libc.so.6(GLIBC_2.1)
+ </div><div class="para">
+ libc.so.6(GLIBC_2.1.3)
+ </div><div class="para">
+ libc.so.6(GLIBC_2.2)
+ </div><div class="para">
+ libdb-4.0.so
+ </div><div class="para">
+ libgdbm.so.2
+ </div><div class="para">
+ libhesiod.so.0
+ </div><div class="para">
+ liblber.so.2
+ </div><div class="para">
+ libldap.so.2
+ </div><div class="para">
+ libnsl.so.1
+ </div><div class="para">
+ libnsl.so.1(GLIBC_2.0)
+ </div><div class="para">
+ libresolv.so.2
+ </div><div class="para">
+ libresolv.so.2(GLIBC_2.0)
+ </div><div class="para">
+ libresolv.so.2(GLIBC_2.2)
+ </div><div class="para">
+ libsasl.so.7
+ </div><div class="para">
+ libssl.so.2
+ </div><div class="para">
+ This example tests an RPM package file, sendmail-8.12.5-7.i386.rpm, for the requires dependency, in other words, what capabilities the package requires. The sendmail package depends on a lot of other parts of the system, as you can see in the response to the command shown previously. Most of the dependencies are for system libraries (all the dependencies ending in .so or .so.number). This package requires other capabilities (packages in this case). It also requires the chkconfig package at a specific version, version 1.3 or higher, and the bash package at version 2.0 or higher. The sendmail package also requires a particular version of the RPM system (the rpmlib dependency).
+ </div><div class="para">
+ Warning
+ </div><div class="para">
+ Always check what a package requires before installing the package. You can also use the --test option when trying to install the package to first test whether the installation can proceed. See <a class="xref" href="ch-using-rpm.html">Cap. 3, <em>Using RPM</em></a> for details on installing packages and the --test option. The rpm command will perform all these checks for you anyway. Checking in advance, though, with the --test option, helps avoid dependency hell with circular dependencies.
+ </div><div class="para">
+ You can also check for what an installed package requires with the --requires option. For example:
+ </div><div class="para">
+ rpm -q --requires sendmail
+ </div><div class="para">
+ You can use the -R short option in place of the --requires option.
+ </div><div class="para">
+ This command returns the same data as the previous command but queries an installed package rather than an RPM package file.
+ </div><div class="para">
+ You might assume that applications have the most dependencies, which is true. But even source packages may depend on other packages, often the packages needed to build the sources into an application. For example, the following command lists the capabilities required by a source RPM:
+ </div><div class="para">
+ $ rpm -qp --requires telnet-0.17-23.src.rpm
+ </div><div class="para">
+ ncurses-devel
+ </div><div class="para">
+ Some packages require particular versions of other packages, for example:
+ </div><div class="para">
+ rpm -qp --requires xcdroast-0.98a9-18.src.rpm
+ </div><div class="para">
+ imlib-devel >= 1.9.13-9
+ </div><div class="para">
+ gtk+-devel >= 1.2.10
+ </div><div class="para">
+ desktop-file-utils >= 0.2.92
+ </div><div class="para">
+ rpmlib(CompressedFileNames) <= 3.0.4-1
+ </div><div class="para">
+ This example shows that the xcdroast source package requires the imlib-devel capability (in this case, a package) at version 1.9.13-9 or higher, the gtk+-devel package at version 1.2.10 or higher, and the desktop-file-utils package at version 0.2.92 or higher. This is a more stringent requirement than just depending on the given packages being installed. This RPM is also an older RPM package, based on the requirement for the rpmlib to be prior or equal to 3.0.4-1.
+ </div><div class="para">
+ Some packages may require a particular version of the rpmlib, or RPM library. For example, the setup package contains special system configuration files, including the default password file, /etc/passwd.
+ </div><div class="para">
+ $ rpm -q --requires setup
+ </div><div class="para">
+ rpmlib(PayloadFilesHavePrefix) <= 4.0-1
+ </div><div class="para">
+ rpmlib(CompressedFileNames) <= 3.0.4-1
+ </div><div class="para">
+ As shown in this example, this package depends only on capabilities of the RPM system itself. The particular requirements shown here specify how the rpm command should treat the package payload, including how the files are listed in the package and what type of compression is used.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-dependencies.html"><strong>Înapoi</strong>Cap. 5. Package Dependencies</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch05s02s02.html"><strong>Înainte</strong>5.2.2. Determining the capabilities a package pro...</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch05s02s02.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch05s02s02.html
new file mode 100644
index 0000000..651a3fa
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch05s02s02.html
@@ -0,0 +1,112 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.2.2. Determining the capabilities a package provides</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch05s02.html" title="5.2. Checking for Dependencies" /><link rel="prev" href="ch05s02.html" title="5.2. Checking for Dependencies" /><link rel="next" href="ch05s02s03.html" title="5.2.3. Checking for conflicts" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch05s02.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch05s02s03.html"><strong>ÃŽnainte</s
trong></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id814902" class="title">Determining the capabilities a package provides</h1></div></div></div><div class="para">
+ Packages require capabilities, and they can provide capabilities for other packages to require. To list the capabilities a package provides, use the --provides option. These capabilities can be arbitrary names, shared libraries (.so files), and the package name itself. The basic syntax is:
+ </div><div class="para">
+ rpm –q query_options --provides packages
+ </div><div class="para">
+ For example, the tcsh shell package provides two capabilities, at a particular version number, as shown following:
+ </div><div class="para">
+ $ rpm -q --provides tcsh
+ </div><div class="para">
+ csh = 6.12
+ </div><div class="para">
+ tcsh = 6.12-2
+ </div><div class="para">
+ Other packages provide a lot more, including shared libraries. The httpd package provides a long list of capabilities, as shown following:
+ </div><div class="para">
+ $ rpm -q --provides httpd
+ </div><div class="para">
+ webserver
+ </div><div class="para">
+ httpd-mmn = 20020628
+ </div><div class="para">
+ libapr.so.0
+ </div><div class="para">
+ libaprutil.so.0
+ </div><div class="para">
+ mod_access.so
+ </div><div class="para">
+ mod_actions.so
+ </div><div class="para">
+ mod_alias.so
+ </div><div class="para">
+ mod_asis.so
+ </div><div class="para">
+ mod_auth_anon.so
+ </div><div class="para">
+ mod_auth_dbm.so
+ </div><div class="para">
+ mod_auth_digest.so
+ </div><div class="para">
+ mod_auth.so
+ </div><div class="para">
+ mod_autoindex.so
+ </div><div class="para">
+ mod_cern_meta.so
+ </div><div class="para">
+ mod_cgi.so
+ </div><div class="para">
+ mod_dav_fs.so
+ </div><div class="para">
+ mod_dav.so
+ </div><div class="para">
+ mod_deflate.so
+ </div><div class="para">
+ mod_dir.so
+ </div><div class="para">
+ mod_env.so
+ </div><div class="para">
+ mod_expires.so
+ </div><div class="para">
+ mod_headers.so
+ </div><div class="para">
+ mod_imap.so
+ </div><div class="para">
+ mod_include.so
+ </div><div class="para">
+ mod_info.so
+ </div><div class="para">
+ mod_log_config.so
+ </div><div class="para">
+ mod_mime_magic.so
+ </div><div class="para">
+ mod_mime.so
+ </div><div class="para">
+ mod_negotiation.so
+ </div><div class="para">
+ mod_proxy_connect.so
+ </div><div class="para">
+ mod_proxy_ftp.so
+ </div><div class="para">
+ mod_proxy_http.so
+ </div><div class="para">
+ mod_proxy.so
+ </div><div class="para">
+ mod_rewrite.so
+ </div><div class="para">
+ mod_setenvif.so
+ </div><div class="para">
+ mod_speling.so
+ </div><div class="para">
+ mod_status.so
+ </div><div class="para">
+ mod_suexec.so
+ </div><div class="para">
+ mod_unique_id.so
+ </div><div class="para">
+ mod_userdir.so
+ </div><div class="para">
+ mod_usertrack.so
+ </div><div class="para">
+ mod_vhost_alias.so
+ </div><div class="para">
+ httpd = 2.0.40-8
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch05s02.html"><strong>Înapoi</strong>5.2. Checking for Dependencies</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch05s02s03.html"><strong>Înainte</strong>5.2.3. Checking for conflicts</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch05s02s03.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch05s02s03.html
new file mode 100644
index 0000000..d0a20ab
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch05s02s03.html
@@ -0,0 +1,26 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.2.3. Checking for conflicts</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch05s02.html" title="5.2. Checking for Dependencies" /><link rel="prev" href="ch05s02s02.html" title="5.2.2. Determining the capabilities a package provides" /><link rel="next" href="ch05s02s04.html" title="5.2.4. Determining which packages require a certain capability" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch05s02s02.html"><strong>ÃŽnapoi</strong></a></li><li class="ne
xt"><a accesskey="n" href="ch05s02s04.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id715101" class="title">Checking for conflicts</h1></div></div></div><div class="para">
+ Use the --conflicts option to check what conflicts with a given package. The basic syntax is:
+ </div><div class="para">
+ rpm –q query_options --conflicts packages
+ </div><div class="para">
+ For example:
+ </div><div class="para">
+ # rpm -q --conflicts httpd
+ </div><div class="para">
+ thttpd
+ </div><div class="para">
+ This command tells you that the httpd package (the Apache Web server) conflicts with the thttpd package. Both packages provide a similar capability. By marking the conflict, the httpd package tells you that you cannot normally install both the httpd and thttpd packages on a system. This information comes from the httpd package, which has an entry in the package that indicates the conflict. The conflict is not guaranteed. These packages may work together, but the creator of the httpd package felt that httpd would not work with the thttpd package and helpfully let us all know.
+ </div><div class="para">
+ The RPM system will report on the conflicts and indicate an error if you try to install conflicting packages. The idea of conflicts really gives package creators a way to alert users to potential problems and to tell us that one package likely won’t work with another.
+ </div><div class="para">
+ The force options discussed in <a class="xref" href="ch-using-rpm.html">Cap. 3, <em>Using RPM</em></a> allow you to override conflicts, if absolutely necessary. In most cases, though, a conflict presents you with the choice to install one or the other of the packages, but not both.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch05s02s02.html"><strong>Înapoi</strong>5.2.2. Determining the capabilities a package pro...</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch05s02s04.html"><strong>Înainte</strong>5.2.4. Determining which packages require a certa...</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch05s02s04.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch05s02s04.html
new file mode 100644
index 0000000..306f105
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch05s02s04.html
@@ -0,0 +1,224 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.2.4. Determining which packages require a certain capability</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch05s02.html" title="5.2. Checking for Dependencies" /><link rel="prev" href="ch05s02s03.html" title="5.2.3. Checking for conflicts" /><link rel="next" href="ch05s02s05.html" title="5.2.5. Determining which package provides a certain capability" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch05s02s03.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href
="ch05s02s05.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id756968" class="title">Determining which packages require a certain capability</h1></div></div></div><div class="para">
+ In addition to querying capabilities and requirements of a particular package, you can query the capabilities themselves. This function allows you to check which packages require a given capability.
+ </div><div class="para">
+ The --whatrequires option tells the rpm command to report on which packages in the RPM database require a certain capability. The basic syntax is:
+ </div><div class="para">
+ rpm –q query_options --whatrequires capability
+ </div><div class="para">
+ Some packages are not required by anything:
+ </div><div class="para">
+ $ rpm -q --whatrequires tcsh
+ </div><div class="para">
+ no package requires tcsh
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ Don’t worry about the poor tcsh package being lonely. Because other packages do not require this package, you can easily remove the tcsh package without affecting the rest of your system.
+ </div><div class="para">
+ This example shows a package name as the capability. Shared libraries are also considered capabilities. You can query on these as well. For example:
+ </div><div class="para">
+ $ rpm -q --whatrequires librpm-4.1.so
+ </div><div class="para">
+ rpm-4.1-1.06
+ </div><div class="para">
+ net-snmp-5.0.1-6
+ </div><div class="para">
+ rpm-python-4.1-1.06
+ </div><div class="para">
+ rpm-devel-4.1-1.06
+ </div><div class="para">
+ rpm-build-4.1-1.06
+ </div><div class="para">
+ This example shows that the core RPM library is used by a number of RPM-related packages, along with, oddly enough, the net-snmp system-management package.
+ </div><div class="para">
+ The capability you query for must be an explicit capability. For example, you will get different results if you query for the bash package or the command, /bin/bash. If you query for the bash package, you will see the packages that explicitly require the capability bash. For example:
+ </div><div class="para">
+ $ rpm -q --whatrequires bash
+ </div><div class="para">
+ gpm-1.19.3-20
+ </div><div class="para">
+ info-4.0b-3
+ </div><div class="para">
+ initscripts-6.40-1
+ </div><div class="para">
+ sendmail-8.11.6-3
+ </div><div class="para">
+ sysklogd-1.4.1-4
+ </div><div class="para">
+ vixie-cron-3.0.1-63
+ </div><div class="para">
+ ypbind-1.8-1
+ </div><div class="para">
+ ypserv-1.3.12-2
+ </div><div class="para">
+ If you instead query for the capability /bin/bash, that is, the file /bin/bash, you will see a different list of packages. For example:
+ </div><div class="para">
+ $ rpm -q --whatrequires /bin/bash
+ </div><div class="para">
+ apmd-3.0final-34
+ </div><div class="para">
+ at-3.1.8-20
+ </div><div class="para">
+ autofs-3.1.7-21
+ </div><div class="para">
+ autofs-3.1.7-21
+ </div><div class="para">
+ bash-2.05-8
+ </div><div class="para">
+ bind-9.1.3-4
+ </div><div class="para">
+ cipe-1.4.5-6
+ </div><div class="para">
+ crontabs-1.10-1
+ </div><div class="para">
+ dialog-0.9a-5
+ </div><div class="para">
+ gpm-1.19.3-20
+ </div><div class="para">
+ hotplug-2001_04_24-11
+ </div><div class="para">
+ initscripts-6.40-1
+ </div><div class="para">
+ ipchains-1.3.10-10
+ </div><div class="para">
+ iproute-2.2.4-14
+ </div><div class="para">
+ kudzu-0.99.23-1
+ </div><div class="para">
+ logwatch-2.1.1-3
+ </div><div class="para">
+ man-1.5i2-6
+ </div><div class="para">
+ mkbootdisk-1.4.2-3
+ </div><div class="para">
+ mkinitrd-3.2.6-1
+ </div><div class="para">
+ mutt-1.2.5i-17
+ </div><div class="para">
+ openssh-server-3.1p1-2
+ </div><div class="para">
+ pine-4.44-1.72.0
+ </div><div class="para">
+ rpm-build-4.0.3-1.03
+ </div><div class="para">
+ rusers-server-0.17-12
+ </div><div class="para">
+ sendmail-8.11.6-3
+ </div><div class="para">
+ shapecfg-2.2.12-7
+ </div><div class="para">
+ sharutils-4.2.1-8
+ </div><div class="para">
+ sysklogd-1.4.1-4
+ </div><div class="para">
+ tetex-1.0.7-30
+ </div><div class="para">
+ ucd-snmp-4.2.1-7
+ </div><div class="para">
+ vixie-cron-3.0.1-63
+ </div><div class="para">
+ xinetd-2.3.3-1
+ </div><div class="para">
+ ypbind-1.8-1
+ </div><div class="para">
+ ypserv-1.3.12-2
+ </div><div class="para">
+ There is no short form for the --whatrequires option.
+ </div><div class="para">
+ Other capabilities, especially system-level shared libraries, are used by a large number of packages. For example:
+ </div><div class="para">
+ # rpm -q --whatrequires libcrypt.so.1 | sort
+ </div><div class="para">
+ autofs-3.1.7-21
+ </div><div class="para">
+ cvs-1.11.1p1-3
+ </div><div class="para">
+ cyrus-sasl-1.5.24-23
+ </div><div class="para">
+ cyrus-sasl-devel-1.5.24-23
+ </div><div class="para">
+ cyrus-sasl-plain-1.5.24-23
+ </div><div class="para">
+ fetchmail-5.9.0-1
+ </div><div class="para">
+ ircii-4.4Z-7
+ </div><div class="para">
+ krbafs-1.0.9-2
+ </div><div class="para">
+ nss_ldap-172-2
+ </div><div class="para">
+ openldap12-1.2.12-4
+ </div><div class="para">
+ openldap-2.0.11-13
+ </div><div class="para">
+ openldap-clients-2.0.11-13
+ </div><div class="para">
+ pam-0.75-19
+ </div><div class="para">
+ pam_krb5-1.46-1
+ </div><div class="para">
+ passwd-0.64.1-7
+ </div><div class="para">
+ perl-5.6.0-17
+ </div><div class="para">
+ pine-4.44-1.72.0
+ </div><div class="para">
+ pwdb-0.61.1-3
+ </div><div class="para">
+ python-1.5.2-35
+ </div><div class="para">
+ rsh-0.17-5
+ </div><div class="para">
+ rsh-server-0.17-5
+ </div><div class="para">
+ screen-3.9.9-3
+ </div><div class="para">
+ sendmail-8.11.6-3
+ </div><div class="para">
+ shadow-utils-20000902-4
+ </div><div class="para">
+ sh-utils-2.0.11-5
+ </div><div class="para">
+ SysVinit-2.78-19
+ </div><div class="para">
+ tcsh-6.10-6
+ </div><div class="para">
+ util-linux-2.11f-17
+ </div><div class="para">
+ vim-enhanced-5.8-7
+ </div><div class="para">
+ wu-ftpd-2.6.1-20
+ </div><div class="para">
+ xinetd-2.3.3-1
+ </div><div class="para">
+ ypserv-1.3.12-2
+ </div><div class="para">
+ yp-tools-2.5-1
+ </div><div class="para">
+ Quite a few packages require encryption and decryption (the purpose of this library), making this library crucial to operating the system. Many of the packages listed here are in turn depended on by even more packages.
+ </div><div class="para">
+ To help trace back capabilities, you can combine the queries. For example:
+ </div><div class="para">
+ $ rpm -q --provides sendmail
+ </div><div class="para">
+ smtpdaemon
+ </div><div class="para">
+ sendmail = 8.11.6-3
+ </div><div class="para">
+ $ rpm -q --whatrequires smtpdaemon
+ </div><div class="para">
+ fetchmail-5.9.0-1
+ </div><div class="para">
+ mutt-1.2.5i-17
+ </div><div class="para">
+ The first command lists the capabilities that the sendmail package provides, including the generic capability of smtpdaemon. You can then list which packages require this particular capability, as shown in the second command. This is a big help for wading through a mess of packages depending on packages depending on yet more packages.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch05s02s03.html"><strong>Înapoi</strong>5.2.3. Checking for conflicts</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch05s02s05.html"><strong>Înainte</strong>5.2.5. Determining which package provides a certa...</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch05s02s05.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch05s02s05.html
new file mode 100644
index 0000000..2854ae3
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch05s02s05.html
@@ -0,0 +1,42 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.2.5. Determining which package provides a certain capability</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch05s02.html" title="5.2. Checking for Dependencies" /><link rel="prev" href="ch05s02s04.html" title="5.2.4. Determining which packages require a certain capability" /><link rel="next" href="ch05s03.html" title="5.3. Triggers" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch05s02s04.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch05s03.html"><st
rong>ÃŽnainte</strong></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id611860" class="title">Determining which package provides a certain capability</h1></div></div></div><div class="para">
+ To complete the circle, you can query for which package provides a certain capability. This knowledge allows you to trace a requirement back to the package that provides it.
+ </div><div class="para">
+ The --whatprovides option tells the rpm command to list the capabilities a package provides. Use the --whatprovides option with the –q, or query, option to the rpm command. (There is no short form for the --whatrprovides option.)
+ </div><div class="para">
+ The basic syntax follows:
+ </div><div class="para">
+ rpm –q --whatprovides capability
+ </div><div class="para">
+ For example, to query what package provides the capability webserver, use the following command:
+ </div><div class="para">
+ $ rpm -q --whatprovides webserver
+ </div><div class="para">
+ httpd-2.0.40-8
+ </div><div class="para">
+ In this case, the capability is identified by an arbitrary string, webserver. This is a generic name for a given capability, serving Web pages.
+ </div><div class="para">
+ You can also trace individual files using the --whatprovides option. For example:
+ </div><div class="para">
+ $ rpm -q --whatprovides /etc/skel/.bashrc
+ </div><div class="para">
+ bash-2.05-8
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ The rpm –qf command, covered in the last chapter, is an easier way to get to the same information when tracking which package provides a particular file. For example:
+ </div><div class="para">
+ rpm -qf /etc/skel/.bashrc
+ </div><div class="para">
+ bash-2.05-8
+ </div><div class="para">
+ If you are querying particular files, use rpm –qf. If you are querying capabilities, use --whatprovides.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch05s02s04.html"><strong>Înapoi</strong>5.2.4. Determining which packages require a certa...</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch05s03.html"><strong>Înainte</strong>5.3. Triggers</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch05s03.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch05s03.html
new file mode 100644
index 0000000..18def12
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch05s03.html
@@ -0,0 +1,222 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.3. Triggers</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-dependencies.html" title="Cap. 5. Package Dependencies" /><link rel="prev" href="ch05s02s05.html" title="5.2.5. Determining which package provides a certain capability" /><link rel="next" href="ch05s04.html" title="5.4. Summary" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch05s02s05.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch05s04.html
"><strong>ÃŽnainte</strong></a></li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id608693" class="title">Triggers</h1></div></div></div><div class="para">
+ A trigger is a script that gets run when a package is installed or uninstalled. Triggers allow packages that depend on other packages to properly configure themselves when those other packages are installed or removed.
+ </div><div class="para">
+ The --triggers option to the rpm command lists any trigger scripts in a given package. For example:
+ </div><div class="para">
+ $ rpm -q --triggers sendmail
+ </div><div class="para">
+ triggerpostun script (through /bin/sh) -- sendmail < 8.10.0
+ </div><div class="para">
+ /sbin/chkconfig --add sendmail
+ </div><div class="para">
+ This shows that the sendmail mail transfer agent (mail-sending program) provides a short trigger script.
+ </div><div class="para">
+ In contrast, the anonftp (anonymous file transfer) package has a fairly complex set of triggers, as shown following:
+ </div><div class="para">
+ $ rpm -q --triggers anonftp
+ </div><div class="para">
+ triggerin script (through /bin/sh) -- glibc
+ </div><div class="para">
+ copy() { file="`ls --sort=time $1 |head -n 1`"; ln -f "$file" "$2" 2>/dev/null |
+ </div><div class="para">
+ | cp -df "$file" "$2"; }
+ </div><div class="para">
+ # Kill off old versions
+ </div><div class="para">
+ rm -f /var/ftp/lib/ld-* /var/ftp/lib/libc* /var/ftp/lib/libnsl* /var/ftp/lib/lib
+ </div><div class="para">
+ nss_files* &>/dev/null || :
+ </div><div class="para">
+ # Copy parts of glibc, needed by various programs in bin.
+ </div><div class="para">
+ LIBCVER=`basename $(ls --sort=time /lib/libc-*.so |head -n 1) .so |cut -f2- -d-`
+ </div><div class="para">
+ copy /lib/ld-${LIBCVER}.so /var/ftp/lib
+ </div><div class="para">
+ copy /lib/libc-${LIBCVER}.so /var/ftp/lib
+ </div><div class="para">
+ copy /lib/libnsl-${LIBCVER}.so /var/ftp/lib
+ </div><div class="para">
+ copy /lib/libnss_files-${LIBCVER}.so /var/ftp/lib
+ </div><div class="para">
+ md5sum /var/ftp/lib/lib*-*.so /var/ftp/lib/libtermcap.so.*.*.* 2>/dev/null >/var
+ </div><div class="para">
+ /ftp/lib/libs.md5
+ </div><div class="para">
+ chmod 0400 /var/ftp/lib/libs.md5
+ </div><div class="para">
+ # Use ldconfig to build symlinks and whatnot.
+ </div><div class="para">
+ [ ! -e /var/ftp/etc/ld.so.conf ] && touch /var/ftp/etc/ld.so.conf
+ </div><div class="para">
+ /sbin/ldconfig -r /var/ftp
+ </div><div class="para">
+ triggerin script (through /bin/sh) -- fileutils
+ </div><div class="para">
+ copy() { file="`ls --sort=time $1 |head -n 1`"; ln -f "$file" "$2" 2>/dev/null |
+ </div><div class="para">
+ | cp -df "$file" "$2"; }
+ </div><div class="para">
+ copy /bin/ls /var/ftp/bin
+ </div><div class="para">
+ md5sum `ls /var/ftp/bin/* |grep -v bin.md5` >/var/ftp/bin/bin.md5
+ </div><div class="para">
+ chmod 0400 /var/ftp/bin/bin.md5
+ </div><div class="para">
+ triggerin script (through /bin/sh) -- cpio
+ </div><div class="para">
+ copy() { file="`ls --sort=time $1 |head -n 1`"; ln -f "$file" "$2" 2>/dev/null |
+ </div><div class="para">
+ | cp -df "$file" "$2"; }
+ </div><div class="para">
+ copy /bin/cpio /var/ftp/bin
+ </div><div class="para">
+ md5sum `ls /var/ftp/bin/* |grep -v bin.md5` >/var/ftp/bin/bin.md5
+ </div><div class="para">
+ chmod 0400 /var/ftp/bin/bin.md5
+ </div><div class="para">
+ triggerin script (through /bin/sh) -- tar
+ </div><div class="para">
+ copy() { file="`ls --sort=time $1 |head -n 1`"; ln -f "$file" "$2" 2>/dev/null |
+ </div><div class="para">
+ | cp -df "$file" "$2"; }
+ </div><div class="para">
+ copy /bin/tar /var/ftp/bin
+ </div><div class="para">
+ md5sum `ls /var/ftp/bin/* |grep -v bin.md5` >/var/ftp/bin/bin.md5
+ </div><div class="para">
+ chmod 0400 /var/ftp/bin/bin.md5
+ </div><div class="para">
+ triggerin script (through /bin/sh) -- gzip
+ </div><div class="para">
+ copy() { file="`ls --sort=time $1 |head -n 1`"; ln -f "$file" "$2" 2>/dev/null |
+ </div><div class="para">
+ | cp -df "$file" "$2"; }
+ </div><div class="para">
+ copy /bin/gzip /var/ftp/bin
+ </div><div class="para">
+ ln -sf gzip /var/ftp/bin/zcat
+ </div><div class="para">
+ md5sum `ls /var/ftp/bin/* |grep -v bin.md5` >/var/ftp/bin/bin.md5
+ </div><div class="para">
+ chmod 0400 /var/ftp/bin/bin.md5
+ </div><div class="para">
+ triggerin script (through /bin/sh) -- libtermcap
+ </div><div class="para">
+ copy() { file="`ls --sort=time $1 |head -n 1`"; ln -f "$file" "$2" 2>/dev/null |
+ </div><div class="para">
+ | cp -df "$file" "$2"; }
+ </div><div class="para">
+ rm -f /var/ftp/lib/libtermcap.so.*.*.* &>/dev/null || :
+ </div><div class="para">
+ copy '/lib/libtermcap.so.*.*.*' /var/ftp/lib
+ </div><div class="para">
+ md5sum /var/ftp/lib/lib*-*.so /var/ftp/lib/libtermcap.so.*.*.* 2>/dev/null >/var
+ </div><div class="para">
+ /ftp/lib/libs.md5
+ </div><div class="para">
+ chmod 0400 /var/ftp/lib/libs.md5
+ </div><div class="para">
+ # Use ldconfig to build symlinks and whatnot.
+ </div><div class="para">
+ [ ! -e /var/ftp/etc/ld.so.conf ] && touch /var/ftp/etc/ld.so.conf
+ </div><div class="para">
+ /sbin/ldconfig -r /var/ftp
+ </div><div class="para">
+ triggerin script (through /bin/sh) -- ncompress
+ </div><div class="para">
+ copy() { file="`ls --sort=time $1 |head -n 1`"; ln -f "$file" "$2" 2>/dev/null |
+ </div><div class="para">
+ | cp -df "$file" "$2"; }
+ </div><div class="para">
+ copy /usr/bin/compress /var/ftp/bin
+ </div><div class="para">
+ md5sum `ls /var/ftp/bin/* |grep -v bin.md5` >/var/ftp/bin/bin.md5
+ </div><div class="para">
+ chmod 0400 /var/ftp/bin/bin.md5
+ </div><div class="para">
+ triggerpostun script (through /bin/sh) -- anonftp 4.0
+ </div><div class="para">
+ if [ "$2" != 1 ] ; then
+ </div><div class="para">
+ # The user has multiple glibc packages installed. We can't read the
+ </div><div class="para">
+ # user's mind, so don't do anything.
+ </div><div class="para">
+ exit 0
+ </div><div class="para">
+ fi
+ </div><div class="para">
+ copy() { file="`ls --sort=time $1 |head -n 1`"; ln -f "$file" "$2" 2>/dev/null |
+ </div><div class="para">
+ | cp -df "$file" "$2"; }
+ </div><div class="para">
+ # Kill off old versions
+ </div><div class="para">
+ rm -f /var/ftp/lib/ld-* /var/ftp/lib/libc* /var/ftp/lib/libnsl* /var/ftp/lib/lib
+ </div><div class="para">
+ nss_files* &>/dev/null || :
+ </div><div class="para">
+ # Copy parts of glibc, needed by various programs in bin.
+ </div><div class="para">
+ LIBCVER=`basename /lib/libc-*.so .so | cut -f2- -d-`
+ </div><div class="para">
+ copy /lib/ld-${LIBCVER}.so /var/ftp/lib
+ </div><div class="para">
+ copy /lib/libc-${LIBCVER}.so /var/ftp/lib
+ </div><div class="para">
+ copy /lib/libnsl-${LIBCVER}.so /var/ftp/lib
+ </div><div class="para">
+ copy /lib/libnss_files-${LIBCVER}.so /var/ftp/lib
+ </div><div class="para">
+ copy /bin/ls /var/ftp/bin
+ </div><div class="para">
+ copy /bin/cpio /var/ftp/bin
+ </div><div class="para">
+ copy /bin/tar /var/ftp/bin
+ </div><div class="para">
+ copy /bin/gzip /var/ftp/bin
+ </div><div class="para">
+ ln -sf gzip /var/ftp/bin/zcat
+ </div><div class="para">
+ copy /usr/bin/compress /var/ftp/bin
+ </div><div class="para">
+ rm -f /var/ftp/lib/libtermcap.so.*.*.* &>/dev/null || :
+ </div><div class="para">
+ copy '/lib/libtermcap.so.*.*.*' /var/ftp/lib
+ </div><div class="para">
+ # Use ldconfig to build symlinks and whatnot.
+ </div><div class="para">
+ [ ! -e /var/ftp/etc/ld.so.conf ] && touch /var/ftp/etc/ld.so.conf
+ </div><div class="para">
+ /sbin/ldconfig -r /var/ftp
+ </div><div class="para">
+ # Generate md5sums for verifyscript
+ </div><div class="para">
+ md5sum /var/ftp/lib/lib*-*.so /var/ftp/lib/libtermcap.so.*.*.* 2>/dev/null >/var
+ </div><div class="para">
+ /ftp/lib/libs.md5
+ </div><div class="para">
+ chmod 0400 /var/ftp/lib/libs.md5
+ </div><div class="para">
+ md5sum `ls /var/ftp/bin/* |grep -v bin.md5` >/var/ftp/bin/bin.md5
+ </div><div class="para">
+ chmod 0400 /var/ftp/bin/bin.md5
+ </div><div class="para">
+ Reading through the scripts indicates that this package seems to be triggered by the glibc standard C programming library package. You can confirm this by using the --triggeredby option to the rpm command, as shown following:
+ </div><div class="para">
+ $ rpm -q --triggeredby glibc
+ </div><div class="para">
+ anonftp-4.0-9
+ </div><div class="para">
+ The anonftp package needs to be notified on changes to the glibc package, so that the anonftp package can properly set up its application. It actually uses part of glibc and is therefore highly susceptible to changes in the glibc package. Thus, the use of triggers provides essentially an extended form of dependencies. The anonftp package in this example depends so much on the glibc package that it needs to execute scripts whenever the glibc package changes.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch05s02s05.html"><strong>Înapoi</strong>5.2.5. Determining which package provides a certa...</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch05s04.html"><strong>Înainte</strong>5.4. Summary</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch05s04.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch05s04.html
new file mode 100644
index 0000000..e4938e6
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch05s04.html
@@ -0,0 +1,20 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.4. Summary</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-dependencies.html" title="Cap. 5. Package Dependencies" /><link rel="prev" href="ch05s03.html" title="5.3. Triggers" /><link rel="next" href="ch-transactions.html" title="Cap. 6. Transactions" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch05s03.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch-transactions.html"><strong>ÃŽnainte</strong></a>
</li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id633930" class="title">Summary</h1></div></div></div><div class="para">
+ Linux comes with many packages. Most of these packages depend on some other packages installed on your system. In RPM terms, packages provide capabilities and depend on capabilities that other packages provide. When the rpm command checks the RPM database for dependencies, it checks to ensure that all the capabilities that a given package requires are met by other installed packages.
+ </div><div class="para">
+ You can trace the capabilities a package requires with the --requires option to the rpm command. You can see what capabilities a package provides for others with the --provides option.
+ </div><div class="para">
+ Once you know a capability, you can query which package provides that capability with the --whatprovides option to the rpm command. And you can see which packages require that capability with the --whatrequires option.
+ </div><div class="para">
+ Triggers are an extended form of dependencies. A trigger is a script that gets executed when other packages are installed or removed. This allows a package with a high dependence on another package to track changes in that package and reconfigure itself as needed.
+ </div><div class="para">
+ The next chapter delves into transactions, which provide a safe means to install a set of packages. With transactions, either all the packages get installed, or none.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch05s03.html"><strong>Înapoi</strong>5.3. Triggers</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch-transactions.html"><strong>Înainte</strong>Cap. 6. Transactions</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch06s02.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch06s02.html
new file mode 100644
index 0000000..18ac6f2
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch06s02.html
@@ -0,0 +1,184 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>6.2. Transactions with the rpm Command</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-transactions.html" title="Cap. 6. Transactions" /><link rel="prev" href="ch-transactions.html" title="Cap. 6. Transactions" /><link rel="next" href="ch06s02s02.html" title="6.2.2. Rolling Back Transactions" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-transactions.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch06s02s02.html"><strong>ÃŽna
inte</strong></a></li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id633675" class="title">Transactions with the rpm Command</h1></div></div></div><div class="para">
+ To set up an RPM transaction, you don't have to do much. All you need to do is pass more than one RPM package on the rpm command line. For example, to set up a transaction for installing three packages, use a command like the following:
+ </div><div class="para">
+ rpm -ihv package1.rpm package2.rpm package3.rpm
+ </div><div class="para">
+ If any of the packages fail to install, the rpm command will not install any packages. All of the packages will be installed, or none.
+ </div><div class="para">
+ This way, if you have a number of packages that together perform some function, such as an Integrated Development Environment (IDE), along with program-language compilers and other software-development tools, you can ensure that all get installed.
+ </div><div class="para">
+ As an example, say you need to install the gnorpm package, which provides a graphical front end for the rpm command, and the rpmrebuild package, which allows you to create RPMs from already-installed packages.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ The gnorpm command is covered in <a class="xref" href="ch-management-software.html">Cap. 7, <em>RPM Management Software</em></a> . The rpmrebuild package is covered in the "Saving Old Packages" section in this chapter.
+ </div><div class="para">
+ You can install these packages with a transaction by using the following command:
+ </div><div class="para">
+ # rpm -ihv gnorpm-0.9-1.i386.rpm rpmrebuild-1.0-0.noarch.rpm
+ </div><div class="para">
+ Preparing... ########################################### [100%]
+ </div><div class="para">
+ package gnorpm-0.9-1 is already installed
+ </div><div class="para">
+ The rpmrebuild package can be installed. (We know this since the rpm command did not issue an error about this package.) But because it was on the same command line as the gnorpm package, the transaction failed. No packages were installed.
+ </div><div class="para">
+ To check that the rpmrebuild package was not installed (that is, to check that the transaction worked as expected), you can use the rpm –q command to see if the rpmrebuild package was installed or not. To do so, use a command like the following:
+ </div><div class="para">
+ # rpm -q rpmrebuild
+ </div><div class="para">
+ package rpmrebuild is not installed
+ </div><div class="para">
+ This shows that the rpmrebuild package was not installed, even though the package could be installed on its own. To check that the package could be installed, you can use the --test option, as shown following:
+ </div><div class="para">
+ # rpm -i --test rpmrebuild-1.0-0.noarch.rpm
+ </div><div class="para">
+ #
+ </div><div class="para">
+ This command shows that the rpmrebuild package would install successfully on its own. If there were problems, the rpm command would have issued an error message.
+ </div><div class="para">
+ This example shows that when you try to install multiple packages with the rpm command, should any fail, the rpm command will not install any.
+ </div><div class="para">
+ The rpm command works similarly for removing packages and upgrading packages. When removing packages, you’ll see an error like the following if any of the packages on the command line cannot be removed:
+ </div><div class="para">
+ # rpm -e setup jikes-1.17
+ </div><div class="para">
+ error: Failed dependencies:
+ </div><div class="para">
+ setup is needed by (installed) basesystem-8.0-1
+ </div><div class="para">
+ setup >= 2.0.3 is needed by (installed) initscripts-6.95-1
+ </div><div class="para">
+ setup >= 2.5.4-1 is needed by (installed) filesystem-2.1.6-5
+ </div><div class="para">
+ setup is needed by (installed) xinetd-2.3.7-2
+ </div><div class="para">
+ setup is needed by (installed) dump-0.4b28-4
+ </div><div class="para">
+ The setup package could not be removed because it had several capabilities needed by other packages. You can check that the jikes package was not removed by using the rpm –q command, even though it had no failed dependencies:
+ </div><div class="para">
+ # rpm -q jikes
+ </div><div class="para">
+ jikes-1.17-1
+ </div><div class="para">
+ This package was not removed because it appeared as part of the same command that failed, so none of the operations were performed.
+ </div><div class="para">
+ When upgrading, you will also see an error message if any of the package upgrades fail. For example:
+ </div><div class="para">
+ # rpm -Uhv jikes-1.14-1.i386.rpm autoupdate-3.1.5-1.noarch.rpm
+ </div><div class="para">
+ error: jikes-1.14-1.i386.rpm cannot be installed
+ </div><div class="para">
+ You can then check that the jikes package, in this example, was not downgraded to the earlier version with the rpm –q command:
+ </div><div class="para">
+ # rpm -q jikes
+ </div><div class="para">
+ jikes-1.17-1
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id817275" class="title">Transaction IDs</h1></div></div></div><div class="para">
+ The rpm command gives every package installed a transaction ID. The transaction ID is a Unix time stamp (number of seconds since January 1, 1970). You can then perform some operations on packages based on the transaction ID.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ The fact that a transaction ID uses a Unix timestamp may change in the future.
+ </div><div class="para">
+ All the packages installed at the same time are given the same transaction ID. This means that you can perform operations on a set of packages, the packages that were installed together.
+ </div><div class="para">
+ But there’s also a downside to this. All the packages installed when you first installed or upgraded your Linux system are given the same transaction ID. This means you cannot selectively act on these packages using the transaction ID, because you will likely get far more packages than you want to work on.
+ </div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id640877" class="title">Viewing RPM Transaction IDs</h1></div></div></div><div class="para">
+ To view the install transaction ID (a date code) for a given package, you can use a command like the following:
+ </div><div class="para">
+ $ rpm -q --qf "%-20{NAME} %-20{INSTALLTID}\n" jikes
+ </div><div class="para">
+ jikes 1035589778
+ </div><div class="para">
+ This command uses the --qf or --queryformat option to specify the data to return from the RPM query command. In this case, the command requests the name of the package as well as the transaction ID (TID) for installation.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ <a class="xref" href="ch-using-rpm-db.html">Cap. 4, <em>Using the RPM Database</em></a> describes the --queryformat option.
+ </div><div class="para">
+ There is also a transaction ID for removal, the REMOVETID. You can also query for this ID. For example, if a package hasn't been removed, you'll see an entry like the following:
+ </div><div class="para">
+ $ rpm -qa --qf "%-20{NAME} %-20{REMOVETID}\n" termcap
+ </div><div class="para">
+ termcap (none)
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id644478" class="title">Viewing the Packages Associated with a Transaction ID</h1></div></div></div><div class="para">
+ Once you have a transaction ID, you can use the --tid option, short for transaction ID, to query for the package associated with a given transaction, using a command like the following:
+ </div><div class="para">
+ $ rpm -q --tid 1035589778
+ </div><div class="para">
+ jikes-1.17-1
+ </div><div class="para">
+ This example uses the transaction ID that the earlier query example returned. If you installed more than one package at the same time, you will see a listing of all the packages that share the transaction ID.
+ </div><div class="para">
+ For example, to see many packages with one transaction ID, you can query for packages installed when you installed or upgraded your version of Linux. First, query for the transaction ID of a package you know was installed with the Linux distribution, such as setup on a Red Hat system:
+ </div><div class="para">
+ $ rpm -q --qf "%-20{NAME} %-20{INSTALLTID}\n" setup
+ </div><div class="para">
+ setup 1033838323
+ </div><div class="para">
+ Second, use this transaction ID and query for all packages with this ID, using code like the following:
+ </div><div class="para">
+ $ rpm -q --tid 1033838323 | more
+ </div><div class="para">
+ redhat-menus-0.26-1
+ </div><div class="para">
+ glibc-2.2.93-5
+ </div><div class="para">
+ cracklib-2.7-18
+ </div><div class="para">
+ gdbm-1.8.0-18
+ </div><div class="para">
+ gmp-4.1-4
+ </div><div class="para">
+ libacl-2.0.11-2
+ </div><div class="para">
+ libjpeg-6b-21
+ </div><div class="para">
+ linc-0.5.2-2
+ </div><div class="para">
+ pcre-3.9-5
+ </div><div class="para">
+ shadow-utils-20000902-12
+ </div><div class="para">
+ libtermcap-2.0.8-31
+ </div><div class="para">
+ freetype-2.1.2-7
+ </div><div class="para">
+ info-4.2-5
+ </div><div class="para">
+ fileutils-4.1.9-11
+ </div><div class="para">
+ psmisc-20.2-6
+ </div><div class="para">
+ ntp-4.1.1a-9
+ </div><div class="para">
+ mount-2.11r-10
+ </div><div class="para">
+ cracklib-dicts-2.7-18
+ </div><div class="para">
+ krb5-libs-1.2.5-6
+ </div><div class="para">
+ cyrus-sasl-2.1.7-2
+ </div><div class="para">
+ usermode-1.63-1
+ </div><div class="para">
+ Xft-2.0-1
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ Be sure to replace the transaction ID shown here with the transaction ID obtained by querying your system.
+ </div><div class="para">
+ This example shows just a few of the packages installed when the Red Hat Linux was installed.
+ </div><div class="para">
+ With these options, you can find the transaction IDs for given packages and can use the rpm command to install, remove, or otherwise modify the packages that share a transaction ID.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-transactions.html"><strong>Înapoi</strong>Cap. 6. Transactions</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch06s02s02.html"><strong>Înainte</strong>6.2.2. Rolling Back Transactions</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch06s02s02.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch06s02s02.html
new file mode 100644
index 0000000..6b03d57
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch06s02s02.html
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>6.2.2. Rolling Back Transactions</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch06s02.html" title="6.2. Transactions with the rpm Command" /><link rel="prev" href="ch06s02.html" title="6.2. Transactions with the rpm Command" /><link rel="next" href="ch06s03.html" title="6.3. Saving Old Packages" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch06s02.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch06s03.html"><strong>ÃŽnain
te</strong></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id516412" class="title">Rolling Back Transactions</h1></div></div></div><div class="para">
+ The --rollback option to the rpm command allows you to roll back upgrades based on a time. Use a command like the following:
+ </div><div class="para">
+ # rpm –U --rollback "3 months ago"
+ </div><div class="para">
+ </div><div class="para">
+ The --rollback option is very limited in what it can do. The --rollback option works only for packages that have been upgraded. You cannot rollback the initial installation of a package. This is to prevent you from accidentally rolling back all packages.
+ </div><div class="para">
+ The --rollback option works best if you want to restore the system to a previous state, prior to performing any other RPM operations. That is, soon after you upgraded a package and decide that it isn’t working right. If you have modified the RPM system after performing the transaction you want to rollback, there may be unintended consequences if any new package depends on the packages you want to roll back. In addition, the --rollback option only works in limited situations but does not always report when these conditions are not met. The rpm command may simply do nothing, or it may remove packages you do not expect.
+ </div><div class="para">
+ Warning
+ </div><div class="para">
+ Before running the --rollback option, backup your RPM database as described in <a class="xref" href="ch-using-rpm-db.html">Cap. 4, <em>Using the RPM Database</em></a> .
+ </div><div class="para">
+ Because of all these limitations, rollbacks do not work in all situations. In place of the --rollback option, you can use the query shortcuts introduced in <a class="xref" href="ch-using-rpm-db.html">Cap. 4, <em>Using the RPM Database</em></a> and find the packages you have installed recently (if that is what you want to roll back). In this case, you can use the rpm command to remove the packages you want to get rid of and reinstall the packages you want to restore.
+ </div><div class="para">
+ In many cases, this manual approach is safest, and you will have a clearer understanding about what was installed or upgraded on your system.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch06s02.html"><strong>Înapoi</strong>6.2. Transactions with the rpm Command</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch06s03.html"><strong>Înainte</strong>6.3. Saving Old Packages</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch06s03.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch06s03.html
new file mode 100644
index 0000000..b4c877d
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch06s03.html
@@ -0,0 +1,69 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>6.3. Saving Old Packages</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-transactions.html" title="Cap. 6. Transactions" /><link rel="prev" href="ch06s02s02.html" title="6.2.2. Rolling Back Transactions" /><link rel="next" href="ch06s04.html" title="6.4. Summary" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch06s02s02.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch06s04.html"><strong>ÃŽnainte</strong></a></li></
ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id505472" class="title">Saving Old Packages</h1></div></div></div><div class="para">
+ When installing, removing, or upgrading, you can use the --repackage command-line option to save a version of something like the old package to a file, making a backup of the older package contents.
+ </div><div class="para">
+ Warning
+ </div><div class="para">
+ The package created by the --repackage option is not a complete RPM package. You can use the rpmbuild command to make it into a complete package, but by itself, it will not be a complete package. See <a class="xref" href="ch-specfiles.html">Cap. 9, <em>Working with Spec Files</em></a>, <a class="xref" href="ch-advanced-packaging.html">Cap. 10, <em>Creare avansată pachete RPM</em></a>, and <a class="xref" href="ch-rpmbuild.html">Cap. 11, <em>Controlling the Build with <code class="command">rpmbuild</code></em></a> for more on building packages.
+ </div><div class="para">
+ </div><div class="para">
+ You can later reinstall the old files, once they have been made into a complete package. This can be quite useful if something goes wrong or the upgraded package has bugs. You can fall back to the old package if needed.
+ </div><div class="para">
+ By default, the --repackage option puts the old package in the /var/spool/repackage directory. Other common directories are /var/spool/up2date or /var/tmp. Your RPM configuration determines the directory used by this option.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ The up2date name comes from the Red Hat service for keeping a system up to date with regard to package versions.
+ </div><div class="para">
+ For example, say you have a package, jikes (a Java programming language compiler used in previous examples) that you want to upgrade. But you are worried that the new version may not work properly.
+ </div><div class="para">
+ First, check the version you have. For example:
+ </div><div class="para">
+ # rpm -q jikes
+ </div><div class="para">
+ jikes-1.14-1
+ </div><div class="para">
+ This shows you are at version 1.14 of the jikes Java compiler. You can then upgrade to version 1.17 while repackaging the old version, as shown following:
+ </div><div class="para">
+ # rpm -Uhv --repackage jikes-1.17-glibc2.2-1.i386.rpm
+ </div><div class="para">
+ Preparing... ########################################### [100%]
+ </div><div class="para">
+ Repackaging...
+ </div><div class="para">
+ 1:jikes ########################################### [100%]
+ </div><div class="para">
+ Upgrading...
+ </div><div class="para">
+ 1:jikes ########################################### [100%]
+ </div><div class="para">
+ This upgrade has kept a copy of the old package in the /var/spool/repackage directory. You can verify this with the following command:
+ </div><div class="para">
+ $ ls -l /var/spool/repackage/
+ </div><div class="para">
+ total 692
+ </div><div class="para">
+ -rw-r--r-- 1 root root 703037 Oct 25 18:49 jikes-1.14-1.i386.rpm
+ </div><div class="para">
+ You can see a version of the old package, with the old version number.
+ </div><div class="para">
+ Warning
+ </div><div class="para">
+ This is not the same as the original package. This is not a complete package.
+ </div><div class="para">
+ The repackaged RPM contains a snapshot of the package’s files as they were on your hard disk, not as they were when you originally installed the package. Thus, the contents may differ if the files have changed on your hard disk. In addition, the --repackage option may not properly sign the package as the original was.
+ </div><div class="para">
+ In addition to the --repackage option with the rpm command, you can use a free tool called rpmrebuild to make snapshots of any installed packages.
+ </div><div class="para">
+ Written by Eric Gerbier, rpmrebuild allows you to create an RPM from the installed, and perhaps modified, version of a package. You don’t have to upgrade, remove, or install a new package, as you do with the --repackage option.
+ </div><div class="para">
+ Download rpmrebuild from http://rpmrebuild.sourceforge.net/.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch06s02s02.html"><strong>Înapoi</strong>6.2.2. Rolling Back Transactions</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch06s04.html"><strong>Înainte</strong>6.4. Summary</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch06s04.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch06s04.html
new file mode 100644
index 0000000..f9e0223
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch06s04.html
@@ -0,0 +1,19 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>6.4. Summary</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-transactions.html" title="Cap. 6. Transactions" /><link rel="prev" href="ch06s03.html" title="6.3. Saving Old Packages" /><link rel="next" href="ch-management-software.html" title="Cap. 7. RPM Management Software" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch06s03.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch-management-software.html"><
strong>ÃŽnainte</strong></a></li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id732461" class="title">Summary</h1></div></div></div><div class="para">
+ Transactions allow you to install multiple packages as a group and know that either all the packages will succeed in installing or none of them will. This is very important if you have a set of interlocking packages that you need to install.
+ </div><div class="para">
+ All the packages you install, remove, or upgrade on the same command line are automatically made part of a transaction. The rpm command will ensure that all packages can be installed, removed, or upgraded, and will not perform the operation unless all will succeed.
+ </div><div class="para">
+ All packages installed or removed are given a transaction ID, which uses a Unix timestamp (the number of seconds since January 1, 1970). All packages installed or removed at the same time are given the same transaction ID. You can then query by transaction IDs to perform operations on all the packages installed together.
+ </div><div class="para">
+ The --repackage option tells the rpm command to make a backup RPM of the current package when you are installing or upgrading a more recent version or removing the package. By default, the backup RPM is placed in the /var/spool/repackage directory. Note that a package created this way is not exactly the same as the original package. Files may have changed on disk. In addition, packages created with the --repackage option are not real valid RPM packages. You cannot install these packages without performing extra operations to create a real RPM package from the repackaged data.
+ </div><div class="para">
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch06s03.html"><strong>Înapoi</strong>6.3. Saving Old Packages</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch-management-software.html"><strong>Înainte</strong>Cap. 7. RPM Management Software</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch07s02.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch07s02.html
new file mode 100644
index 0000000..49e373a
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch07s02.html
@@ -0,0 +1,38 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.2. Graphical RPM Management</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-management-software.html" title="Cap. 7. RPM Management Software" /><link rel="prev" href="ch-management-software.html" title="Cap. 7. RPM Management Software" /><link rel="next" href="ch07s02s02.html" title="7.2.2. Red Hat Package Management" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-management-software.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a acces
skey="n" href="ch07s02s02.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id759884" class="title">Graphical RPM Management</h1></div></div></div><div class="para">
+ Once appropriate RPMs have been obtained, they have to be installed before the application they provide can be used. You can use the rpm command-line utility to do this. The rpmfind utility also has the capability to launch the rpm utility automatically to install any software located. In addition to these two tools, however, several graphical applications are available that provide basic RPM package-management capabilities. Most of these programs offer easy-to-use GUIs that can be used to install and uninstall packages, to query packages, and to verify installed packages.
+ </div><div class="para">
+ Even though Linux and Unix fans generally aren’t bothered by command-line tools such as rpm, many newcomers to Linux fret over the seeming difficulty of the command line. They are more used to graphical applications and, in many cases, are more productive in a graphical environment. Keeping with the Linux tradition of freedom of choice, you can use the command-line tools such as the rpm commandor pick from a variety of graphical tools.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id759907" class="title">Nautilus</h1></div></div></div><div class="para">
+ Nautilus provides a visually appealing file manager that is part of the GNOME desktop. Nautilus acts as a normal file manager that can also display some types of files, such as images. In addition, you can launch applications that Nautilus knows about when you double click files. Figure 8-1 shows Nautilus in action.
+ </div><div class="para">
+ Insert 54965-0 fg0801.tif
+ </div><div class="para">
+ Figure 8-1: Browsing RPM files with Nautilus.
+ </div><div class="para">
+ If you double click an RPM file (a file ending with the extension .rpm), Nautilus will install the RPM file. First, though, Nautilus will prompt you for the root password, since you must be logged in as root to install RPMs. Figure 8-2 shows Nautilus prompting for a password.
+ </div><div class="para">
+ Insert 54965-0 fg0802.tif
+ </div><div class="para">
+ Figure 8-2: You must be logged in as root to install packages.
+ </div><div class="para">
+ After some time processing, you should see the Completed System Preparation window, as shown in Figure 8-3.
+ </div><div class="para">
+ Insert 54965-0 fg0803.tif
+ </div><div class="para">
+ Figure 8-3: Installing RPM files with Nautilus.
+ </div><div class="para">
+ When you install RPMs with Nautilus, it really runs the Red Hat Package Management tool.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ Nautilus only supports RPM functionality starting with Red Hat Linux 8.0. This functionality may not be supported in other versions of Linux.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-management-software.html"><strong>Înapoi</strong>Cap. 7. RPM Management Software</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch07s02s02.html"><strong>Înainte</strong>7.2.2. Red Hat Package Management</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch07s02s02.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch07s02s02.html
new file mode 100644
index 0000000..89af653
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch07s02s02.html
@@ -0,0 +1,54 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.2.2. Red Hat Package Management</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch07s02.html" title="7.2. Graphical RPM Management" /><link rel="prev" href="ch07s02.html" title="7.2. Graphical RPM Management" /><link rel="next" href="ch07s02s03.html" title="7.2.3. KPackage" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch07s02.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch07s02s03.html"><strong>ÃŽnainte</strong></a></li><
/ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id557775" class="title">Red Hat Package Management</h1></div></div></div><div class="para">
+ The redhat-config-packages application (say that three times fast) comes new with Red Hat Linux 8.0. You can use the Python program in this package to manage the packages that come with Red Hat Linux, using an interface that is very similar to the Red Hat Linux installation program. This similarity may make it easier for many users to manage their packages, although I found the program a bit short on explanations.
+ </div><div class="para">
+ To run this program, you first have to do a bit of searching to find it. It appears under the System Settings menu from the main Red Hat Start menu under the default Bluecurve desktop. Select the Packages choice to launch this program. You can also start the program from the command line with the following command:
+ </div><div class="para">
+ # redhat-config-packages
+ </div><div class="para">
+ This program takes a long time to read in all the information and start up. Once started, the interface provides the same categories and much the same look as the Red Hat Linux installer, as shown in Figure 8-4.
+ </div><div class="para">
+ Insert 54965-0 fg0804.tif
+ </div><div class="para">
+ Figure 8-4: The redhat-config-packages package manager.
+ </div><div class="para">
+ The packages tool divides the packages into groups. Inside each group, the packages are divided into two sets: standard and extra packages. (Red Hat places the packages into these categories, striving to make a reasonable division among the many packages that come with Linux.) If you click the check box for a group, the tool will queue up all the standard packages within that group for installation. If you uncheck a check box for a group that was checked before, the tool will queue up all the installed packages in that group for removal, both standard and extra.
+ </div><div class="para">
+ Warning
+ </div><div class="para">
+ Installing or removing all the packages in a group when you don’t know what is in the group is not a good idea.
+ </div><div class="para">
+ To delve into a group and see what is inside, click the Details link associated with that group. Clicking the Details link will bring up a window where you can check individual packages for installation and uncheck individual packages for removal. Figure 8-5 shows the details of the Web Server group.
+ </div><div class="para">
+ Insert 54965-0 fg0805.tif
+ </div><div class="para">
+ Figure 8-5: Package details for the Web Server group.
+ </div><div class="para">
+ Once you have selected all the packages you want to install, and unselected all the packages you want to remove, click the Update button on the main window of the package-management tool. After some processing, you should see the Completed System Preparation window, which lists the amount of disk space required for the new packages and the amount that will be freed by the packages to be removed. Figure 8-6 shows this window.
+ </div><div class="para">
+ Insert 54965-0 fg0806.tif
+ </div><div class="para">
+ Figure 8-6: The Completed Systems Preparation window.
+ </div><div class="para">
+ Click the Show Details button to see a complete list of all the packages to be installed and removed.
+ </div><div class="para">
+ Warning
+ </div><div class="para">
+ If the packages you choose to install depend on any other packages, the package-management tool will automatically add these packages to the list to be installed. More important, if any packages installed on your system depend on any of the packages you have marked for removal, the tool will add those additional installed packages to the list to be removed. Always examine the Show Details window to see what will really be installed and removed.
+ </div><div class="para">
+ Figure 8-7 shows the window with the package details.
+ </div><div class="para">
+ Insert 54965-0 fg0807.tif
+ </div><div class="para">
+ Figure 8-7: The Show Details window.
+ </div><div class="para">
+ The package-management tool worries me. It has an absolutely beautiful look, but it tries to do too much, especially when removing packages. Always use this program with care. I much prefer to just launch it with single packages from the Nautilus file manager.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch07s02.html"><strong>Înapoi</strong>7.2. Graphical RPM Management</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch07s02s03.html"><strong>Înainte</strong>7.2.3. KPackage</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch07s02s03.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch07s02s03.html
new file mode 100644
index 0000000..9923bfe
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch07s02s03.html
@@ -0,0 +1,32 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.2.3. KPackage</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch07s02.html" title="7.2. Graphical RPM Management" /><link rel="prev" href="ch07s02s02.html" title="7.2.2. Red Hat Package Management" /><link rel="next" href="ch07s02s04.html" title="7.2.4. Gnome-RPM" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch07s02s02.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch07s02s04.html"><strong>ÃŽnainte</strong
></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id561255" class="title">KPackage</h1></div></div></div><div class="para">
+ One popular graphical RPM management tool is KPackage, supplied with the KDE Desktop. (You can find this product at www.kde.org). KPackage offers basic package-management functionality. It can install and uninstall packages and display information about installed and available packages’ contents and headers. In addition, KPackage supports a wide variety of package formats in addition to RPMs. Be aware, however, that KPackage cannot automatically resolve dependencies. When you are installing new software packages, any dependencies required by that software must first be manually installed.
+ </div><div class="para">
+ When started, KPackage presents a basic two-paned interface.
+ </div><div class="para">
+ The left-hand panel lists Installed packages already on the system, Updated packages available to update the system, New packages available for installation, and All packages (both installed and available for installation/upgrade). When displaying package lists, KPackage organizes the displayed packages into categories based on their group.
+ </div><div class="para">
+ The right-hand panel lists information about the package currently selected in the left-hand panel. Information displayed includes the package Properties, listing the package’s header, and the File List of files that package owns. Figure 8-8 shows this panel on the right side of the interface.
+ </div><div class="para">
+ Note: old fig 8-8 deleted; renumber all remaining to match. Chapter has been changed to reflect deletion.
+ </div><div class="para">
+ Insert 54965-0 fg0808.tif
+ </div><div class="para">
+ Figure 8-8: The KPackage interface, showing properties of the selected package
+ </div><div class="para">
+ After packages have been selected, they can be installed or uninstalled, as shown in Figure 8-9
+ </div><div class="para">
+ Insert 54965-0 fg0809.tif
+ </div><div class="para">
+ Figure 8-9: KPackage installs the selected package on your command.
+ </div><div class="para">
+ In addition to supporting RPM, KPackage can be used on systems that use other packaging methods. Current versions of KPackage support Debian’s dpkg and the BSD projects’ package formats as well as RPM.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch07s02s02.html"><strong>Înapoi</strong>7.2.2. Red Hat Package Management</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch07s02s04.html"><strong>Înainte</strong>7.2.4. Gnome-RPM</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch07s02s04.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch07s02s04.html
new file mode 100644
index 0000000..0a00e96
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch07s02s04.html
@@ -0,0 +1,32 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.2.4. Gnome-RPM</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch07s02.html" title="7.2. Graphical RPM Management" /><link rel="prev" href="ch07s02s03.html" title="7.2.3. KPackage" /><link rel="next" href="ch07s03.html" title="7.3. Extending RPM Management" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch07s02s03.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch07s03.html"><strong>ÃŽnainte</strong></a></li><
/ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id550989" class="title">Gnome-RPM</h1></div></div></div><div class="para">
+ The GNOME Desktop (www.gnome.org) provides another graphical RPM-management tool, Gnome-RPM. Also known as gnorpm, Gnome-RPM is very similar to KPackage in terms of its basic functionality, although Gnome-RPM can manage only RPMs.
+ </div><div class="para">
+ When started, Gnome-RPM presents a hierarchical list of installed packages, arranged by group, as shown in Figure 8-10:
+ </div><div class="para">
+ Insert 54965-0 fg0810.tif
+ </div><div class="para">
+ Figure 8-10: The main Gnome-RPM window.
+ </div><div class="para">
+ After a specific package has been selected, you can can query to see its details, as shown in Figure 8-11:
+ </div><div class="para">
+ Insert 54965-0 fg0811.tif
+ </div><div class="para">
+ Figure 78-11: Querying the details for a package.
+ </div><div class="para">
+ With Gnome-RPM, you can also filter the list of packages to see only the list of uninstalled RPMs, as shown in Figure 8-12.
+ </div><div class="para">
+ Insert 54965-0 fg0812.tif
+ </div><div class="para">
+ Figure 78-12: Filtering to see only the uninstalled packages.
+ </div><div class="para">
+ Like KPackage, when installing new software, Gnome-RPM lacks the ability to automatically install any dependencies needed by that software.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch07s02s03.html"><strong>Înapoi</strong>7.2.3. KPackage</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch07s03.html"><strong>Înainte</strong>7.3. Extending RPM Management</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch07s03.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch07s03.html
new file mode 100644
index 0000000..90f1980
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch07s03.html
@@ -0,0 +1,184 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.3. Extending RPM Management</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-management-software.html" title="Cap. 7. RPM Management Software" /><link rel="prev" href="ch07s02s04.html" title="7.2.4. Gnome-RPM" /><link rel="next" href="ch07s03s02.html" title="7.3.2. AutoUpdate" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch07s02s04.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch07s03s02.html"><strong>ÃŽnainte</stron
g></a></li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id564859" class="title">Extending RPM Management</h1></div></div></div><div class="para">
+ RPM makes it very easy to install and uninstall software from systems. One simple command installs an entire application onto the computer, and another removes all files associated with an application. Using RPM to install and uninstall software can become tedious in some situations, however. Manually installing software on one system is no great task, but what if that same software package needs to be installed on all the computers in the department? Or on all the computers in a company? Suddenly, that one rpm -i command has become a major chore!
+ </div><div class="para">
+ Similarly, keeping one system up-to-date with the latest vendor errata, although an extremely important administrative task, is not terribly time-consuming or difficult — simply download all the errata and associated packages from the vendor; then use the command rpm -Fvh to install the packages on the system, freshening all installed software with the latest updates of that software.
+ </div><div class="para">
+ If several machines are being managed, though, the task becomes slightly more difficult. Now the vendor errata and packages must be manually copied to each machine, and rpm -Fvh must be run on each machine to update it. If many machines are being managed, and those systems are running different versions of the operating system (so that they require different errata), the task becomes even more complicated. Separate errata packages must be downloaded for every operating system version in use; then the appropriate errata collections must be pushed to each machine and manually freshened. To make life as a system administrator even more frustrating, sometimes vendor-supplied errata cannot be installed using the freshen option. A package supplied as one RPM in the initial operating-system release might be split into two RPMs for the errata, for example. When this happens, freshen cannot be used. Instead, the administrator must determine what software is currently installed on t
he system, and the errata for that software must be manually installed. Typically, this involves several rounds of comparing output from rpm -qa with the list of current errata, using rpm -Uvh to upgrade only the appropriate errata for that system.
+ </div><div class="para">
+ Worse yet, errata updating should ideally be done on an automatic basis. While rpm commands can be scheduled using system utilities such as cron or at, obviously this cannot be done when the rpm commands to be scheduled need to be interactive.
+ </div><div class="para">
+ Installation of new packages can pose problems as well. New software will often have logical dependencies upon other software that is also not currently installed. Although RPM does track software dependencies, it does not magically find all dependencies an application needs, nor does it automatically install them along with the initial application. Instead, all required “helper†applications must be searched out and manually installed. Then the desired software can be installed.
+ </div><div class="para">
+ These and similar problems are very common in the real world. Typically, system administrators manage as many as 200 or more systems. Manually logging into 200 systems and executing an rpm -i command every time another application is needed is not practical. Even when managing one system, downloading errata and manually installing it regularly quickly becomes tedious.
+ </div><div class="para">
+ Like any regular system-administration task, it should be automated. When installing new software on machines, managing dependencies and downloading and installing required support software becomes tiresome as well.
+ </div><div class="para">
+ To aid with these common problems, a variety of helper applications are available for RPM. These management aids can perform functions such as automatically managing dependencies. When an application is being installed using one of these helpers, the utility also finds and installs any required dependencies. Similarly, when errata are being installed, these management aids can automatically determine which errata are needed by the current system, even in situations in which rpm -F does not work. Some of these tools can even be used to manage clusters of computers. Running one command applies the RPM install or delete on the entire group of machines. All of these commands are designed with scriptability in mind, making them perfect for use automatically via tools such as cron or at.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id567232" class="title">AutoRPM</h1></div></div></div><div class="para">
+ One popular tool to lessen the work involved with administering RPM-based systems is AutoRPM. Written by Kirk Bauer, AutoRPM is available under a free MIT-style license from the home page www.autorpm.org.
+ </div><div class="para">
+ A Perl script, AutoRPM provides several features that make it especially useful. First, it can create local mirrors of RPM repositories. Typically, this feature might be used to create a local archive of errata for a Linux distribution. AutoRPM can also compare all currently installed RPMs against a list stored elsewhere. This list can be either an FTP site or a directory on the local system. After comparing the currently-installed RPMs against the list, AutoRPM can then update any packages from the list site that are newer than what is installed on the local system. This way, you can define one site or directory as the master site of the package versions that need to get installed on all systems and let AutoRPM ensure that all computers on your network are up to date.
+ </div><div class="para">
+ Together, these two functions make AutoRPM very convenient for keeping systems current with all errata the vendor releases. They can also be used to create a method of distributing software to a network of systems. For example, every workstation in the department can run AutoRPM, configured to watch a common directory on a local NFS server. Installing new software on every workstation in the department occurs simply by copying an RPM of the software into that directory, letting AutoRPM do the rest of the work.
+ </div><div class="para">
+ AutoRPM is designed to be used both automatically from cron and interactively from the command line. By default, AutoRPM runs via a nightly cron job and downloads all updates for software currently installed on the system. It then stores these updates in a local directory, typically /var/spool/autorpm, and e-mails an administrator a notification on the new updates. The administrator can then log onto the system and manually install the updates using the rpm command. AutoRPM can also be easily configured to install automatically any new packages it downloads. If AutoRPM is so configured, the system administrator does not even have to log in and run rpm commands to keep the system up-to-date!
+ </div><div class="para">
+ In interactive mode, AutoRPM provides a basic set of commands, listed in Table 8-2.
+ </div><div class="para">
+ Table 8-2Basic AutoRPM commands
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Command
+ </div>
+
+ </td><td>
+ <div class="para">
+ Usage
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ ?
+ </div>
+
+ </td><td>
+ <div class="para">
+ displays help on the various commands
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Help
+ </div>
+
+ </td><td>
+ <div class="para">
+ displays help on the various commands
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Info
+ </div>
+
+ </td><td>
+ <div class="para">
+ displays information about an RPM
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Fullinfo
+ </div>
+
+ </td><td>
+ <div class="para">
+ displays complete information about an RPM
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Install
+ </div>
+
+ </td><td>
+ <div class="para">
+ installs RPMs onto the system
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Add
+ </div>
+
+ </td><td>
+ <div class="para">
+ adds RPMs to the queue of RPMs to be processed
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Remove
+ </div>
+
+ </td><td>
+ <div class="para">
+ deletes RPMs from the queue of RPMs waiting to be processed
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ List
+ </div>
+
+ </td><td>
+ <div class="para">
+ displays all RPMs currently in the queue waiting to be processed
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Cd
+ </div>
+
+ </td><td>
+ <div class="para">
+ changes the local directory
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Auto
+ </div>
+
+ </td><td>
+ <div class="para">
+ executes commands defined in the system-wide configuration file
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Set
+ </div>
+
+ </td><td>
+ <div class="para">
+ displays or modifies current AutoRPM settings
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Abort
+ </div>
+
+ </td><td>
+ <div class="para">
+ exits without saving changes
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Exit
+ </div>
+
+ </td><td>
+ <div class="para">
+ Exits and saves changes
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ The commands that manipulate RPMs (such as install, used to install an RPM) accept as arguments both paths to RPM files on the local system, and also URLs pointing to RPMs on an FTP repository. In addition, they support wild cards and directory accesses, so a command such as install ftp://ftp.redhat.com/pub/redhat/linux/updates/current/* can be used to install all errata for the current release of Red Hat Linux.
+ </div><div class="para">
+ In addition to interactive mode, AutoRPM provides a noninteractive mode, suitable for use through cron. In noninteractive mode, invoked by the command autorpm --notty auto, AutoRPM consults the configuration file /etc/autorpm.conf to decide what to do. By default, /etc/autorpm.d/autorpm.conf is configured to download, but not automatically install, all errata for the release of Red Hat Linux running on the local system. Editing this file makes it possible to use AutoRPM to download all errata — or errata for other Linux distributions — or to install errata automatically once downloaded.
+ </div><div class="para">
+ Typically, AutoRPM is used to automate installation of errata updates and other software on all machines in the enterprise. To do this, one machine is selected to serve as a file server. On it, AutoRPM is configured to download and install all errata. The directory where the errata are stored on that server is then exported to the other machines in the enterprise, which also run AutoRPM. These other machines have AutoRPM configured to install all files that the file server exports. Using a configuration such as this, all machines in the enterprise get all security updates automatically installed. In addition, installing a desired new software application on all hosts in the enterprise can be done simply by copying an RPM of the application onto the file server, making it available for the AutoRPM nightly updates to access and install automatically.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch07s02s04.html"><strong>Înapoi</strong>7.2.4. Gnome-RPM</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch07s03s02.html"><strong>Înainte</strong>7.3.2. AutoUpdate</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch07s03s02.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch07s03s02.html
new file mode 100644
index 0000000..4d69f1f
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch07s03s02.html
@@ -0,0 +1,90 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.3.2. AutoUpdate</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch07s03.html" title="7.3. Extending RPM Management" /><link rel="prev" href="ch07s03.html" title="7.3. Extending RPM Management" /><link rel="next" href="ch07s03s03.html" title="7.3.3. The Red Hat Network and up2date" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch07s03.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch07s03s03.html"><strong>ÃŽna
inte</strong></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id495091" class="title">AutoUpdate</h1></div></div></div><div class="para">
+ AutoUpdate, written by Gerald Teschl, is another Perl script that can be used to automate RPM downloads or installations. Available freely under the terms of the GNU GPL from www.mat.univie.ac.at/~gerald/ftp/autoupdate, AutoUpdate is very similar to AutoRPM in terms of both functionality and potential applications. Unlike AutoRPM, AutoUpdate offers no interactive capability. However, AutoUpdate does have the capability to manage dependencies correctly; when using AutoUpdate to install software that depends upon other uninstalled software, AutoUpdate attempts to resolve the dependencies and to install all necessary software packages.
+ </div><div class="para">
+ AutoUpdate bases all decisions about what software to download or install upon its configuration file, /etc/autoupdate.d/autoupdate.conf. By default, AutoUpdate provides several additional configuration files pre-defined for downloading updates for the most popular RPM-based Linux distributions (Red Hat Linux, Mandrake Linux, Caldera/SCO OpenLinux, and SUSE Linux). The autoupdate.conf file can be modified to configure AutoUpdate to install software automatically.
+ </div><div class="para">
+ Table 8-3 lists the five commands that compose all the utilities provided by AutoUpdate:
+ </div><div class="para">
+ Table 8-3AutoUpdate commands
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Command
+ </div>
+
+ </td><td>
+ <div class="para">
+ Usage
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ autodld
+ </div>
+
+ </td><td>
+ <div class="para">
+ downloads updated versions of all installed software
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ autoget
+ </div>
+
+ </td><td>
+ <div class="para">
+ downloads specific RPMs from remote sites
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ autoupd
+ </div>
+
+ </td><td>
+ <div class="para">
+ installs more recent versions of currently installed software
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ autoins
+ </div>
+
+ </td><td>
+ <div class="para">
+ installs specific applications
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ automerge
+ </div>
+
+ </td><td>
+ <div class="para">
+ merges new RPMs into an existing directory of RPMs, removing any old versions
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ autopurge
+ </div>
+
+ </td><td>
+ <div class="para">
+ removes old RPMs from an existing directory of RPMs.
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ These tools can access remote files by using a variety of methods. Like AutoRPM, AutoUptodate can download files if given an FTP URL. AutoUpdate can also access HTTP URLs and local files. Its additional dependency-tracking functionality and support for additional file-access methods make it suitable for use in cases where AutoRPM might be inappropriate. AutoUpdate cannot be used interactively, however, making AutoRPM more useful for nonautomated purposes.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch07s03.html"><strong>Înapoi</strong>7.3. Extending RPM Management</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch07s03s03.html"><strong>Înainte</strong>7.3.3. The Red Hat Network and up2date</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch07s03s03.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch07s03s03.html
new file mode 100644
index 0000000..bac5037
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch07s03s03.html
@@ -0,0 +1,210 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.3.3. The Red Hat Network and up2date</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch07s03.html" title="7.3. Extending RPM Management" /><link rel="prev" href="ch07s03s02.html" title="7.3.2. AutoUpdate" /><link rel="next" href="ch07s03s04.html" title="7.3.4. Current" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch07s03s02.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch07s03s04.html"><strong>ÃŽnainte</strong></a></li></ul><di
v class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id652428" class="title">The Red Hat Network and up2date</h1></div></div></div><div class="para">
+ Some vendors of RPM-based Linux distributions also provide utilities that can help with management of the distributions they create. Red Hat has created two complementary products, the Red Hat Network (RHN) and up2date, which together provide much the same functionality for managing Red Hat Linux installations as tools such as AutoUpdate and AutoRPM, as well as offering more advanced features.
+ </div><div class="para">
+ Red Hat Network is a subscription-based service offered by Red Hat Red Hat Network makes software available for installation via the network. (A free evaluation is also available.) After registering machines with Red Hat Network, administrators can pull updates or new software for installation to those registered machines. In addition, administrators have access to a Web-based administrative console from which they can view the systems they manage and can push software out to those systems.
+ </div><div class="para">
+ Red Hat offers two tiers of access to Red Hat Network. Basic Service subscriptions to Red Hat Network provide the ability to manage single systems. Multiple machines can be subscribed by the same administrator for Basic Service level Red Hat Network access, but they must all be managed independently. The administrator must push out errata to each machine separately. Workgroup Service subscriptions provide the same functionality as Basic Service subscriptions, but they also provide the ability to group multiple machines for simultaneous administration. All errata updates for all machines subscribed to Workgroup Service can be pushed out by a single action, for example. Furthermore, Workgroup Service subscriptions can allow management by multiple administrators if desired, making it possible for large organizations to share responsibilities among administrators.
+ </div><div class="para">
+ When using Red Hat Network to manage machines with Workgroup Service subscriptions, Red Hat also offers two optional services: Red Hat Network Proxy Server and Red Hat Network Satellite. The Red Hat Network Proxy Server is, as its name suggests, a proxy server for the Red Hat Network. Using it, errata pushed out via Red Hat Network is downloaded by the organization (only once) to a central server in-house. All machines in that organization subscribed to Red Hat Network get their updated software from that in-house proxy server, significantly reducing the network bandwidth requirements needed to keep large organizations up to date.
+ </div><div class="para">
+ In addition, the Red Hat Network Proxy Server can be used to provide all subscribed machines with software not provided with Red Hat Linux. Custom “channels†of supplemental software can be created on the Proxy Server, and machines can be subscribed to those channels as desired. Using this feature, different departments in the organization with different software needs can create independent channels for each department, ensuring that machines get only the software needed on them. Similarly, distinct channels can be created for separate classes of machines, ensuring that servers get only software appropriate for server machines and that desktops only get only software that desktop machines need.
+ </div><div class="para">
+ The Red Hat Network is normally centrally administered through Red Hat. Machines subscribed to the Red Hat Network have a system profile on file with Red Hat that details the system’s essential configuration information (what software is installed on it, what CPU architecture it contains, and so forth) needed to determine which software errata are appropriate for that system. Similarly, the Web console through which machines subscribed to Red Hat Network can be administered is also located on a Red Hat server. Customers wishing to use Red Hat Network services, but not wanting the dependency upon Internet access to Red Hat, can create an in-house Red Hat Network by using the Red Hat Network Satellite. This solution is often practical for customers who need to keep system information confidential or for customers whose systems are not able to access the Internet.
+ </div><div class="para">
+ Red Hat provides several interfaces for administering machines subscribed to the Red Hat Network. A Web-management console is available at https://rhn.redhat.com/. Administrators of machines subscribed to any level of the Red Hat Network can simply log into this Web site and perform a variety of package-management operations from their Web browsers. In addition to viewing other things, administrators can see what software is currently installed, select and install Red Hat Linux errata or new software, or schedule a time for automatic installation of Red Hat Linux errata.
+ </div><div class="para">
+ When using Red Hat Network, rhnsd is a client-side daemon that should be run on subscribed systems. It periodically launches a helper utility, rhn_check, which connects to the Red Hat Network servers and checks for any actions (such as a scheduled installation of errata) that an administrator has selected in the Web console. If any actions have been scheduled for that client machine, rhn_check on the client initiates those actions. By default, rhnsd runs rhn_check every two hours. This time can be increased to check for configuration changes as frequently as every hour if necessary.
+ </div><div class="para">
+ In addition, Red Hat provides client-side tools that can be used in a more interactive fashion to connect to the Red Hat Network from subscribed systems. The up2date program provides a graphical and command-line tool that can be used to install packages from Red Hat Network servers. When installing a new package, up2date automatically installs any necessary dependencies the package requires, making it a very convenient tool for adding software to the system. up2date can also be run in update mode, thus telling it to install all updates available for the software already installed on the system. Commonly used options with up2date include those listed in Table 8-4.
+ </div><div class="para">
+ Table 8-4Options for the up2date command
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Option
+ </div>
+
+ </td><td>
+ <div class="para">
+ Usage
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --configure
+ </div>
+
+ </td><td>
+ <div class="para">
+ Start a dialog for configuring up2date options
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -d
+ </div>
+
+ </td><td>
+ <div class="para">
+ Download packages but do not install them
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -f
+ </div>
+
+ </td><td>
+ <div class="para">
+ Force packages to be installed, even if they have been marked to be skipped
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -i
+ </div>
+
+ </td><td>
+ <div class="para">
+ Download and install packages
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -l
+ </div>
+
+ </td><td>
+ <div class="para">
+ List available updated versions of already installed packages
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --showall
+ </div>
+
+ </td><td>
+ <div class="para">
+ List all available packages, including packages not currently installed at all
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -k
+ </div>
+
+ </td><td>
+ <div class="para">
+ List local directories containing packages
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nosig
+ </div>
+
+ </td><td>
+ <div class="para">
+ Disable GPG package signature checking
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --src
+ </div>
+
+ </td><td>
+ <div class="para">
+ Download both source and binary RPMs
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nosrc
+ </div>
+
+ </td><td>
+ <div class="para">
+ Do not download source RPMs
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -p
+ </div>
+
+ </td><td>
+ <div class="para">
+ Update the list of installed packages associated with this computer in the Red Hat Network database
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --whatprovides
+ </div>
+
+ </td><td>
+ <div class="para">
+ Ask the RHN servers which packages will resolve the listed dependencies
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --solvedeps
+ </div>
+
+ </td><td>
+ <div class="para">
+ Ask the RHN servers which packages will resolve the listed dependencies, then downloads and installs those packages
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --tmpdir
+ </div>
+
+ </td><td>
+ <div class="para">
+ Specify the temporary directory to which packages should be downloaded
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -u
+ </div>
+
+ </td><td>
+ <div class="para">
+ Update all software currently installed on the system to the latest available version
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nox
+ </div>
+
+ </td><td>
+ <div class="para">
+ Short for No X, this disables the X-based GUI, instead using only the command-line interface
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -v
+ </div>
+
+ </td><td>
+ <div class="para">
+ Provide more verbose output
+ </div>
+
+ </td></tr></tbody></table></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch07s03s02.html"><strong>Înapoi</strong>7.3.2. AutoUpdate</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch07s03s04.html"><strong>Înainte</strong>7.3.4. Current</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch07s03s04.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch07s03s04.html
new file mode 100644
index 0000000..9d249b1
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch07s03s04.html
@@ -0,0 +1,14 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.3.4. Current</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch07s03.html" title="7.3. Extending RPM Management" /><link rel="prev" href="ch07s03s03.html" title="7.3.3. The Red Hat Network and up2date" /><link rel="next" href="ch07s03s05.html" title="7.3.5. urpmi and RpmDrake" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch07s03s03.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch07s03s05.html"><strong>ÃŽ
nainte</strong></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id613584" class="title">Current</h1></div></div></div><div class="para">
+ The up2date command, the Red Hat Network client software, is open-source software released by Red Hat under the terms of the GNU GPL. Red Hat Network Proxy Server and Red Hat Network Satellite, the server applications with which up2date interacts, are not freely available, open-source applications. For this reason, an effort is underway to develop servers available under the terms of the GNU GPL that can be used with up2date clients. The main program in this effort is called current, which refers to keeping your systems current.
+ </div><div class="para">
+ The current server can be downloaded from http://current.tigris.org. Although not yet as functional as Red Hat Network Proxy Server or Red Hat Network Satellite, current can already be used to create a RPM repository from which up2date-using clients can retrieve and install software. More advanced features, such as support for multiple “channels†of software, will be added to current in future releases.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch07s03s03.html"><strong>Înapoi</strong>7.3.3. The Red Hat Network and up2date</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch07s03s05.html"><strong>Înainte</strong>7.3.5. urpmi and RpmDrake</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch07s03s05.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch07s03s05.html
new file mode 100644
index 0000000..bd6ec05
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch07s03s05.html
@@ -0,0 +1,18 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.3.5. urpmi and RpmDrake</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch07s03.html" title="7.3. Extending RPM Management" /><link rel="prev" href="ch07s03s04.html" title="7.3.4. Current" /><link rel="next" href="ch07s03s06.html" title="7.3.6. apt-rpm" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch07s03s04.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch07s03s06.html"><strong>ÃŽnainte</strong></a></li></ul><div c
lass="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id613608" class="title">urpmi and RpmDrake</h1></div></div></div><div class="para">
+ Mandrake provides a set of software similar to the combination of up2date and Red Hat Network or current that can be used with the Mandrake Linux distribution. Links to the source code for the Mandrake applications can be found at www.linux-mandrake.com/cooker/urpmi.html. This suite of applications is typically referred to as urpmi and includes both the urpmi command and several helper applications. urpmi itself is a command that acts as a wrapper around the rpm command. When given the name of a package to install, urpmi determines what dependencies, if any, required by the application are not already resolved and offers to install the packages necessary to fulfill those dependencies.
+ </div><div class="para">
+ When installing packages, urpmi can install from a variety of sources: FTP repositories, Web servers, local or NFS directories, and removable media such as CD-ROMs. The helper application urpmi.addmedia is used to add package sources, and the corresponding utility urpmi.removemedia is used to remove package sources no longer desired.
+ </div><div class="para">
+ Mandrake’s urpmi program includes one very handy feature. It comes with an autoirpm helper utility that can be used to configure the system to install packages on demand. This is done by running the command autoirpm.update-all, an application that scans all packages available for installation via urpmi. For every package available through urpmi, autoirpm.update-all determines what executable programs it provides, and it creates a symbolic link from that executable’s name to the autoirpm script. Attempting to execute such a symbolic link executes autoirpm, which in turn automatically uses urpmi to install the associated package. The result: on-demand installation of packages when users on the system attempt to execute the programs that those packages provide.
+ </div><div class="para">
+ Two different interfaces are available for urpmi. The urpmi command starts up urpmi in command-line mode, and the gurpmi command (or urpmi --X) starts urpmi in a graphical X-based mode. In addition, Mandrake provides a more full-featured graphical application: RpmDrake. RpmDrake provides the same package-management capabilities as urpmi, including the capability to install all required dependencies whenever installing any new packages.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch07s03s04.html"><strong>Înapoi</strong>7.3.4. Current</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch07s03s06.html"><strong>Înainte</strong>7.3.6. apt-rpm</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch07s03s06.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch07s03s06.html
new file mode 100644
index 0000000..70e0802
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch07s03s06.html
@@ -0,0 +1,46 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.3.6. apt-rpm</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch07s03.html" title="7.3. Extending RPM Management" /><link rel="prev" href="ch07s03s05.html" title="7.3.5. urpmi and RpmDrake" /><link rel="next" href="ch07s03s07.html" title="7.3.7. The poldek" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch07s03s05.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch07s03s07.html"><strong>ÃŽnainte</strong></a></
li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id613650" class="title">apt-rpm</h1></div></div></div><div class="para">
+ Another free RPM management utility is available that provides many of the features of both vendor solutions such as up2date or urpmi and of third-party utilities such as autoUpdate or KPackage. This tool is apt-rpm, a port of the Debian Project’s excellent apt (Advanced Package Tool) software.
+ </div><div class="para">
+ The Debian Project (www.debian.org/) is a nonprofit volunteer group that develops a Linux distribution, Debian GNU/Linux. The group uses a different package format, dpkg, which was developed independently of and simultaneous to Red Hat’s creation of RPM. The two formats, dpkg and RPM, are very similar in terms of utility and functionality. In addition to having created a package format, the Debian Project later developed a collection of software, apt, which could be used to manage and install dpkg-format software. And, since Debian distributions are typically installed over the Internet, this apt software has to supply advanced distributed package management functionality.
+ </div><div class="para">
+ In many respects, Debian’s implementation of apt is very similar to the functionality provided by Red Hat’s up2date/Red Hat Network products or Mandrake’s urpmi software. On Debian systems, apt is a client tool used to select and install new software packages or to update existing packages already installed on the system. To do this, it accesses a user-configured list of resources that supply new packages; these resources are typically the Debian Project’s FTP or Web servers, though they can also be CD-ROMs or local or remote file systems. For apt to be able to download packages from a resource such as a CD-ROM or an FTP server, that resource must supply two things: the software packages being downloaded and a database supplying metadata about all the packages in the repository. These resource databases are essential for apt to operate. For this reason, apt can only be used to update systems from apt-capable repositories.
+ </div><div class="para">
+ Although apt was created by the Debian Project and designed for dpkg-format software packages, nothing about apt requires that it inherently be usable only with dpkg-format packages. Because of this, and because of its powerful capabilities, Conectiva, a Brazilian Linux distribution vendor (www.conectiva.com), extended apt to support management of RPM packages in addition to dpkg packages. Conectiva’s work, commonly referred to as apt-rpm, makes the apt client software available for use on any RPM-based Linux distribution. Conectiva also provides its customers with access to apt-capable FTP servers. A related project, apt4rpm (http://apt4rpm.sourceforge.net/), supplies the necessary utilities that can be used to make any RPM repository apt-capable. By creating apt-capable servers using apt4rpm and then installing apt-rpm on the client systems, any RPM-based distribution, such as Red Hat Linux, Mandrake Linux, Caldera/SCO OpenLinux, or SUSE Linux, can then be easily manag
ed using apt.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ The freshrpms.net site, mentioned previously, provides a touted apt repository.
+ </div><div class="para">
+ Administrators managing multiple dispersed machines as well as those used to Debian administration often find it useful to configure their machines to use apt; its dependency tracking is far better than any other tool, except for Red Hat’s up2date/RHN combination. To use apt, administrators must install it on their machines and have access to an apt-capable RPM repository for the distribution they use. Several public FTP sites that support apt are now available for most of the major RPM-based distributions. Also, the administrator can create another apt-capable repository.
+ </div><div class="para">
+ Configuration of machines to use apt is simple. The apt and libapt RPMs simply need to be installed. Although binaries are sometimes available, the best success can usually be obtained by building binary RPMs from the latest Conectiva apt SRPM (source RPM), available at ftp://ftp.conectiva.com/pub/conectiva/EXPERIMENTAL/apt/.
+ </div><div class="para">
+ Once apt and libapt RPMs are installed, the sources.list file in /etc/apt needs to be modified to reference the apt-capable software site that will be used. For example, to configure a machine to access the apt-capable Red Hat Linux 7.2 software distributed by the Tuxfamily.org server, the /etc/apt/sources.list file needs to list:
+ </div><div class="para">
+ rpm http://apt-rpm.tuxfamily.org/apt redhat-7.2-i386/redhat os
+ </div><div class="para">
+ rpm http://apt-rpm.tuxfamily.org/apt redhat-updates-7.2/redhat os
+ </div><div class="para">
+ These two lines, respectively, access the Red Hat Linux 7.2 and Red Hat Linux 7.2 errata RPMs being served by the system apt-rpm.tuxfamily.org. If you also want access to source RPMs, the following lines are necessary as well.
+ </div><div class="para">
+ rpm-src http://apt-rpm.tuxfamily.org/apt redhat-7.2-i386/redhat os
+ </div><div class="para">
+ rpm-src http://apt-rpm.tuxfamily.org/apt redhat-updates-7.2/redhat os
+ </div><div class="para">
+ In addition to, or instead of, using public apt-capable servers, many sites want to create their own apt servers. If apt is being used to manage all the machines in the enterprise, a custom apt server might be needed that contains apt-accessible RPMs of all the custom software used in the enterprise. This can be done using the tools provided by the apt4rpm package (http://apt4rpm.sourceforge.net).
+ </div><div class="para">
+ Once apt has been installed on clients, and the clients have been configured to access an apt-capable server, keeping systems updated is simple. The command apt-get update updates the client system’s apt database of available software, after which the command apt-get upgrade upgrades all currently installed software to the latest version available in the software repository. By listing a site that provides vendor errata updates in /etc/apt/sources.list and then setting up a nightly cron job to run the apt-get upgrade command, administrators can be sure that client systems always have the latest errata installed. You can use a similar technique to ensure that all client systems are always up to date with the latest custom in-house applications. To do this, set up your own apt server and ensure that the latest custom applications are placed on the apt server.
+ </div><div class="para">
+ In addition, apt simplifies interactive installation of RPMs on systems that are using it. The command apt-get install package retrieves the named RPM from the apt-capable software repository and installs it. If the package requires any dependencies that are not already resolved, apt will ask for confirmation, then download and install the package and all dependencies. Similarly, apt-get remove package uninstalls the named RPM. If any other packages depend on it, it will prompt for confirmation, then uninstall the named RPM and all of its dependencies.
+ </div><div class="para">
+ In addition to these command-line utilities, several graphical front-end tools for manipulating apt are currently being ported for use with apt-rpm. Because of its ease of use for automating installation of system errata and necessary custom software, and because of the excellent dependency tracking it provides for interactive installation and uninstallation of software, apt-rpm can be excellent for managing RPM-based systems.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch07s03s05.html"><strong>Înapoi</strong>7.3.5. urpmi and RpmDrake</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch07s03s07.html"><strong>Înainte</strong>7.3.7. The poldek</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch07s03s07.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch07s03s07.html
new file mode 100644
index 0000000..0772656
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch07s03s07.html
@@ -0,0 +1,18 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.3.7. The poldek</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch07s03.html" title="7.3. Extending RPM Management" /><link rel="prev" href="ch07s03s06.html" title="7.3.6. apt-rpm" /><link rel="next" href="ch07s04.html" title="7.4. Summary" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch07s03s06.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch07s04.html"><strong>ÃŽnainte</strong></a></li></ul><div class="se
ct2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id626618" class="title">The poldek</h1></div></div></div><div class="para">
+ Also similar to the Debian apt tool, a utility called the poldek works like apt-get. The poldek was designed to quickly scan through dependencies and install a number of packages at once. You can specify all the packages to install in a file.
+ </div><div class="para">
+ The poldek automatically downloads any needed dependencies. The poldek can download files over the Internet and also help create the packages for storage on CD-ROMs. The poldek optimizes the set of packages to reduce the number of times users have to switch CDs.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ For more on the poldek, see poldek.pld.org.pl.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch07s03s06.html"><strong>Înapoi</strong>7.3.6. apt-rpm</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch07s04.html"><strong>Înainte</strong>7.4. Summary</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch07s04.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch07s04.html
new file mode 100644
index 0000000..85b3dc6
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch07s04.html
@@ -0,0 +1,24 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.4. Summary</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-management-software.html" title="Cap. 7. RPM Management Software" /><link rel="prev" href="ch07s03s07.html" title="7.3.7. The poldek" /><link rel="next" href="ch-creating-rpms.html" title="Cap. 8. Creating RPMs: An Overview" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch07s03s07.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch-creating-rpms
.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id626647" class="title">Summary</h1></div></div></div><div class="para">
+ This chapter has covered a number of tools for finding packages in RPM format, as well as tools to help manage the RPMs on your system. The rpm command does a great job of installing, removing, and upgrading packages. You can use it or choose from one of the many graphical RPM management tools shown in this chapter.
+ </div><div class="para">
+ The rpmfind utility helps find RPM packages on Internet servers. You can use rpmfind to find the latest version of the packages installed on your system.
+ </div><div class="para">
+ The Nautilus file manager allows you to browse files on disk, and it installs any RPM files you double-click.
+ </div><div class="para">
+ Red Hat Linux 8 comes with a new package-management tool available from the System Settings menu. Be careful with this tool, though, as it automatically installs--and removes--dependent packages.
+ </div><div class="para">
+ AutoRPM and AutoUpdate provide utilites that you can run periodically to ensure that your systems are up to date. The Red Hat Network and up2date also provides this capability.
+ </div><div class="para">
+ The Debian GNU/Linux apt system provides many of the same capabilities as RPM, along with the network-updating capabilities of up2date and the Red Hat Network. You can use special apt packages that adapt apt for RPM-based Linux distributions and get the best of both the RPM system and the apt system.
+ </div><div class="para">
+ The next chapter starts the major section on creating RPMs. The RPM system reduces a lot of the burden of administering Linux systems. You can take advantage of this when building any sort of software for distribution--or even when managing your own system.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch07s03s07.html"><strong>Înapoi</strong>7.3.7. The poldek</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch-creating-rpms.html"><strong>Înainte</strong>Cap. 8. Creating RPMs: An Overview</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch08s02.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch08s02.html
new file mode 100644
index 0000000..1df28d0
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch08s02.html
@@ -0,0 +1,146 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>8.2. Building RPMs</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-creating-rpms.html" title="Cap. 8. Creating RPMs: An Overview" /><link rel="prev" href="ch-creating-rpms.html" title="Cap. 8. Creating RPMs: An Overview" /><link rel="next" href="ch08s02s02.html" title="8.2.2. Placing your sources into the directory structure" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-creating-rpms.html"><strong>ÃŽnapoi</strong></a></li><li class="nex
t"><a accesskey="n" href="ch08s02s02.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id870957" class="title">Building RPMs</h1></div></div></div><div class="para">
+ In previous chapters, just about everything you want to do with RPMs is accomplished with the rpm command. Building RPMs is one exception. Just about everything you want to do to build an RPM is done by the rpmbuild command, often with a single command.
+ </div><div class="para">
+ Warning
+ </div><div class="para">
+ Older RPM manuals refer to using the –b option to the rpm command to create RPMs. Don’t use that option. Instead, always use the rpmbuild command. The reason for this change is that starting with version 4.1, RPM no longer maps the rpm -b command to the real command, rpmbuild.
+ </div><div class="para">
+ When building RPMs, go through the following steps:
+ </div><div class="para">
+ 1.Set up the directory structure.
+ </div><div class="para">
+ 2.Place the sources in the right directory.
+ </div><div class="para">
+ 3.Create a spec file that tells the rpmbuild command what to do.
+ </div><div class="para">
+ 4.Build the source and binary RPMs.
+ </div><div class="para">
+ The following sections provide details for these steps.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id823716" class="title">Setting up the directory structure</h1></div></div></div><div class="para">
+ The RPM system expects five directories, as listed in Table 9-1.
+ </div><div class="para">
+ Table 9-1 RPM directories
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Directory
+ </div>
+
+ </td><td>
+ <div class="para">
+ Usage
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ BUILD
+ </div>
+
+ </td><td>
+ <div class="para">
+ The rpmbuild command builds software in this directory.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMS
+ </div>
+
+ </td><td>
+ <div class="para">
+ The rpmbuild command stores binary RPMs it creates in this directory.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ SOURCES
+ </div>
+
+ </td><td>
+ <div class="para">
+ You should put the sources for the application in this directory.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ SPECS
+ </div>
+
+ </td><td>
+ <div class="para">
+ You should place the spec file for each RPM you plan to make in this directory.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ SRPMS
+ </div>
+
+ </td><td>
+ <div class="para">
+ The rpmbuild command places source RPMs in this directory.
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ The RPMS directory usually has a number of architecture-specific subdirectories, such as the following (on an Intel architecture system):
+ </div><div class="para">
+ $ ls RPMS
+ </div><div class="para">
+ athlon
+ </div><div class="para">
+ i386
+ </div><div class="para">
+ i486
+ </div><div class="para">
+ i586
+ </div><div class="para">
+ i686
+ </div><div class="para">
+ noarch
+ </div><div class="para">
+ By default, Red Hat Linux systems expect RPMs to be built in the /usr/src/redhat directory.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ This directory is obviously specific to Red Hat Linux. On other Linux distributions, you'll likely see other directories.
+ </div><div class="para">
+ Within the /usr/src/redhat directory, you’ll see the subdirectories listed in Table 9-1, as follows:
+ </div><div class="para">
+ $ ls /usr/src/redhat
+ </div><div class="para">
+ BUILD
+ </div><div class="para">
+ RPMS
+ </div><div class="para">
+ SOURCES
+ </div><div class="para">
+ SPECS
+ </div><div class="para">
+ SRPMS
+ </div><div class="para">
+ At first, it seems rather odd to be using a system directory to build RPMs. But remember that the RPM system was originally built to create Linux distributions. You can also change the default directories by modifying your rpmrc settings.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ See <a class="xref" href="ch-customizing-rpm.html">Cap. 20, <em>Customizing RPM Behavior</em></a> for more on the use of the rpmrc settings.
+ </div><div class="para">
+ For now, it is easiest to just change to the /usr/src/redhat directory and work from this location. To start, you will need to change ownership or permissions on these files so you can build RPMs while logged in as a normal user.
+ </div><div class="para">
+ Warning
+ </div><div class="para">
+ Do not build RPMs while logged in as root. Mistakes in building packages can have serious consequences if you are logged in as root.
+ </div><div class="para">
+ To build RPMs, you really need only two things:
+ </div><div class="para">
+ *Your sources in the SOURCES directory
+ </div><div class="para">
+ *Your spec file in the SPECS directory
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-creating-rpms.html"><strong>Înapoi</strong>Cap. 8. Creating RPMs: An Overview</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch08s02s02.html"><strong>Înainte</strong>8.2.2. Placing your sources into the directory st...</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch08s02s02.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch08s02s02.html
new file mode 100644
index 0000000..410a975
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch08s02s02.html
@@ -0,0 +1,20 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>8.2.2. Placing your sources into the directory structure</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch08s02.html" title="8.2. Building RPMs" /><link rel="prev" href="ch08s02.html" title="8.2. Building RPMs" /><link rel="next" href="ch08s02s03.html" title="8.2.3. Creating the spec file" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch08s02.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch08s02s03.html"><strong>ÃŽnainte</strong></a></li></ul><div
class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id638065" class="title">Placing your sources into the directory structure</h1></div></div></div><div class="para">
+ You can place all the source files directly in the /usr/src/redhat/SOURCES directory. In most cases, however, it is easier to create a tarball of the sources you want to build and place the tarball file in the /usr/src/redhat/SOURCES directory. The RPM specifications for commands necessary to extract the sources from such a file are trivial. Furthermore, the tarball, when extracted, should create a subdirectory specific to your package. This keeps your source code separate from other packages that also have source code in the SOURCES directory.
+ </div><div class="para">
+ The best strategy is to start in a directory of your own making, create the tarball file from the sources, and then copy the tarball file to the /usr/src/redhat/SOURCES directory.
+ </div><div class="para">
+ The convention for these tarball files is package-version.tar.gz. For example:
+ </div><div class="para">
+ jikes-1.17.tar.gz
+ </div><div class="para">
+ Place a file like this into the /usr/src/redhat/SOURCES directory. This file should include all the sources, all the build scripts, and any documentation you want to install as part of the package.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch08s02.html"><strong>Înapoi</strong>8.2. Building RPMs</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch08s02s03.html"><strong>Înainte</strong>8.2.3. Creating the spec file</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch08s02s03.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch08s02s03.html
new file mode 100644
index 0000000..57ece1b
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch08s02s03.html
@@ -0,0 +1,67 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>8.2.3. Creating the spec file</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch08s02.html" title="8.2. Building RPMs" /><link rel="prev" href="ch08s02s02.html" title="8.2.2. Placing your sources into the directory structure" /><link rel="next" href="ch08s02s03s02.html" title="8.2.3.2. The prep section" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch08s02s02.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch08s02s03s02.htm
l"><strong>ÃŽnainte</strong></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id638100" class="title">Creating the spec file</h1></div></div></div><div class="para">
+ The spec file, short for specification file, defines all the actions the rpmbuild command should take to build your application, as well as all the actions necessary for the rpm command to install and remove the application. Each source RPM should have the necessary spec file for building a binary RPM.
+ </div><div class="para">
+ The spec file is a text file. The normal naming convention is to name the file with the package name and a .spec filename extension. For example, the jikes package spec file would be named jikes.spec.
+ </div><div class="para">
+ Inside the spec file, format the information on the package using a special syntax. This syntax defines how to build the package, version numbers, dependency information, and everything else you can query about a package. This syntax differs slightly depending on the sections in the spec file. The following sections describe these spec file sections and the necessary syntax in each section.
+ </div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id638126" class="title">The introduction section</h1></div></div></div><div class="para">
+ The introduction section contains information about the package, the type of information shown with the rpm -qi command. For example:
+ </div><div class="para">
+ Summary: java source to bytecode compiler
+ </div><div class="para">
+ %define version 1.17
+ </div><div class="para">
+ Copyright: IBM Public License, http://ibm.com/developerworks/oss/license10.html
+ </div><div class="para">
+ Group: Development/Languages
+ </div><div class="para">
+ Name: jikes
+ </div><div class="para">
+ Prefix: /usr
+ </div><div class="para">
+ Provides: jikes
+ </div><div class="para">
+ Release: 1
+ </div><div class="para">
+ Source: jikes-%{version}.tar.gz
+ </div><div class="para">
+ URL: http://ibm.com/developerworks/opensource/jikes
+ </div><div class="para">
+ Version: %{version}
+ </div><div class="para">
+ Buildroot: /tmp/jikesrpm
+ </div><div class="para">
+ </div><div class="para">
+ %description
+ </div><div class="para">
+ The IBM Jikes compiler translates Java source files to bytecode. It
+ </div><div class="para">
+ also supports incremental compilation and automatic makefile generation,
+ </div><div class="para">
+ and is maintained by the Jikes Project:
+ </div><div class="para">
+ http://ibm.com/developerworks/opensource/jikes/
+ </div><div class="para">
+ In this example, you can see the Source: definition of a compressed tar archive associated with a particular version number. This also names a Buildroot: setting that defines where the files will get built into a working program. You can see the description of the package that will get printed with the rpm –qi command.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ You can further divide this first section into the preamble and other areas. For simplicity, I grouped all introductary parts of a spec file into one introduction section.
+ </div><div class="para">
+ This example comes from a real-world RPM spec file. It does not follow all the rules for creating RPMs. This example:
+ </div><div class="para">
+ *Should not explicitly provide jikes, the name of the package.
+ </div><div class="para">
+ *Should not include a Copyright tag, as this tag is deprecated.
+ </div><div class="para">
+ *Uses a %define for the version when the rpmbuild command can create a version macro for you.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch08s02s02.html"><strong>Înapoi</strong>8.2.2. Placing your sources into the directory st...</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch08s02s03s02.html"><strong>Înainte</strong>8.2.3.2. The prep section</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch08s02s03s02.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch08s02s03s02.html
new file mode 100644
index 0000000..58eb4c7
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch08s02s03s02.html
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>8.2.3.2. The prep section</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch08s02s03.html" title="8.2.3. Creating the spec file" /><link rel="prev" href="ch08s02s03.html" title="8.2.3. Creating the spec file" /><link rel="next" href="ch08s02s03s03.html" title="8.2.3.3. The build section" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch08s02s03.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch08s02s03s03.html"><strong>Ã
Žnainte</strong></a></li></ul><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id789880" class="title">The prep section</h1></div></div></div><div class="para">
+ The prep section, short for prepare, defines the commands necessary to prepare for the build. If you are starting with a compressed tar archive (a tarball) of the sources, the prep section needs to extract the sources.
+ </div><div class="para">
+ For example:
+ </div><div class="para">
+ %prep
+ </div><div class="para">
+ %setup -q
+ </div><div class="para">
+ The prep section starts with a %prep statement.
+ </div><div class="para">
+ This example uses the %setup RPM macro, which knows about tar archives, to extract the files. In most cases, this will be all you need in your spec file prep section.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch08s02s03.html"><strong>Înapoi</strong>8.2.3. Creating the spec file</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch08s02s03s03.html"><strong>Înainte</strong>8.2.3.3. The build section</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch08s02s03s03.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch08s02s03s03.html
new file mode 100644
index 0000000..1e17d8b
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch08s02s03s03.html
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>8.2.3.3. The build section</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch08s02s03.html" title="8.2.3. Creating the spec file" /><link rel="prev" href="ch08s02s03s02.html" title="8.2.3.2. The prep section" /><link rel="next" href="ch08s02s03s04.html" title="8.2.3.4. The install section" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch08s02s03s02.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch08s02s03s04.html"><stro
ng>ÃŽnainte</strong></a></li></ul><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id789915" class="title">The build section</h1></div></div></div><div class="para">
+ The spec file build section contains the commands to build the software. Usually, this will include just a few commands, since most of the real instructions appear in the Makefile. For example:
+ </div><div class="para">
+ %build
+ </div><div class="para">
+ ./configure CXXFLAGS=-O3 --prefix=$RPM_BUILD_ROOT/usr
+ </div><div class="para">
+ make
+ </div><div class="para">
+ The build section starts with a %build statement.
+ </div><div class="para">
+ The commands shown for this build section run the configure script, covered in the previous section on Linux build tools, and then run the make command with the default maketarget. If things unfold as they should, this procedure builds the software.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch08s02s03s02.html"><strong>Înapoi</strong>8.2.3.2. The prep section</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch08s02s03s04.html"><strong>Înainte</strong>8.2.3.4. The install section</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch08s02s03s04.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch08s02s03s04.html
new file mode 100644
index 0000000..e4d4631
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch08s02s03s04.html
@@ -0,0 +1,20 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>8.2.3.4. The install section</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch08s02s03.html" title="8.2.3. Creating the spec file" /><link rel="prev" href="ch08s02s03s03.html" title="8.2.3.3. The build section" /><link rel="next" href="ch08s02s03s05.html" title="8.2.3.5. The clean section" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch08s02s03s03.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch08s02s03s05.html"><stron
g>ÃŽnainte</strong></a></li></ul><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id640679" class="title">The install section</h1></div></div></div><div class="para">
+ The spec file install section holds the commands necessary to install the newly built application or library. In most cases, your install section should clean out the Buildroot directory and run the make install command. For example:
+ </div><div class="para">
+ %install
+ </div><div class="para">
+ rm -fr $RPM_BUILD_ROOT
+ </div><div class="para">
+ make install
+ </div><div class="para">
+ The install section starts with an %install statement.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch08s02s03s03.html"><strong>Înapoi</strong>8.2.3.3. The build section</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch08s02s03s05.html"><strong>Înainte</strong>8.2.3.5. The clean section</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch08s02s03s05.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch08s02s03s05.html
new file mode 100644
index 0000000..9ab9b28
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch08s02s03s05.html
@@ -0,0 +1,18 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>8.2.3.5. The clean section</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch08s02s03.html" title="8.2.3. Creating the spec file" /><link rel="prev" href="ch08s02s03s04.html" title="8.2.3.4. The install section" /><link rel="next" href="ch08s02s03s06.html" title="8.2.3.6. The files section" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch08s02s03s04.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch08s02s03s06.html"><str
ong>ÃŽnainte</strong></a></li></ul><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id640709" class="title">The clean section</h1></div></div></div><div class="para">
+ The clean section cleans up the files that the commands in the other sections create:
+ </div><div class="para">
+ %clean
+ </div><div class="para">
+ rm -rf $RPM_BUILD_ROOT
+ </div><div class="para">
+ The clean section starts with a %clean statement
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch08s02s03s04.html"><strong>Înapoi</strong>8.2.3.4. The install section</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch08s02s03s06.html"><strong>Înainte</strong>8.2.3.6. The files section</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch08s02s03s06.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch08s02s03s06.html
new file mode 100644
index 0000000..ddb7921
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch08s02s03s06.html
@@ -0,0 +1,58 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>8.2.3.6. The files section</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch08s02s03.html" title="8.2.3. Creating the spec file" /><link rel="prev" href="ch08s02s03s05.html" title="8.2.3.5. The clean section" /><link rel="next" href="ch08s02s04.html" title="8.2.4. Building RPMs with the rpmbuild command" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch08s02s03s05.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch08s02s0
4.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id640732" class="title">The files section</h1></div></div></div><div class="para">
+ Finally, the files section lists the files to go into the binary RPM, along with the defined file attributes. For example:
+ </div><div class="para">
+ %files
+ </div><div class="para">
+ %defattr(-,root,root)
+ </div><div class="para">
+ /usr/bin/jikes
+ </div><div class="para">
+ %doc /usr/doc/jikes-%{version}/license.htm
+ </div><div class="para">
+ %doc /usr/man/man1/jikes.1*
+ </div><div class="para">
+ The files section starts with a %files statement
+ </div><div class="para">
+ The %doc macro marks certain files as documentation. This allows the RPM to distinguish the files holding documentation from the other files in the RPM.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ This example skips the install and uninstall script sections, as well as a verification section. There are also no triggers defined in this RPM spec file. All of these topics are covered in <a class="xref" href="ch-specfiles.html">Cap. 9, <em>Working with Spec Files</em></a> and <a class="xref" href="ch-advanced-packaging.html">Cap. 10, <em>Creare avansată pachete RPM</em></a>.
+ </div><div class="para">
+ Once you have written your spec file, and placed the files in the SOURCES and SPECS directories under /usr/src/redhat, you’ll see files like the following:
+ </div><div class="para">
+ $ ls –CF /usr/src/redhat/*
+ </div><div class="para">
+ /usr/src/redhat/BUILD:
+ </div><div class="para">
+ </div><div class="para">
+ /usr/src/redhat/RPMS:
+ </div><div class="para">
+ athlon/ i386/ i486/ i586/ i686/ noarch/
+ </div><div class="para">
+ </div><div class="para">
+ /usr/src/redhat/SOURCES:
+ </div><div class="para">
+ jikes-1.17.tar.gz
+ </div><div class="para">
+ </div><div class="para">
+ /usr/src/redhat/SPECS:
+ </div><div class="para">
+ jikes.spec
+ </div><div class="para">
+ </div><div class="para">
+ /usr/src/redhat/SRPMS:
+ </div><div class="para">
+ That is, with a clean system and no other RPMs being built, you'll see a spec file in /usr/src/redhat/SPECS and the sources in /usr/src/redhat/SOURCES. In this example, the sources are in a compressed tar archive. (For this, the RPM spec file, jikes.spec needs to have a command in the prep section to extract the files.)
+ </div><div class="para">
+ You should now be ready to build an RPM.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch08s02s03s05.html"><strong>Înapoi</strong>8.2.3.5. The clean section</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch08s02s04.html"><strong>Înainte</strong>8.2.4. Building RPMs with the rpmbuild command</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch08s02s04.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch08s02s04.html
new file mode 100644
index 0000000..0c6b98d
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch08s02s04.html
@@ -0,0 +1,260 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>8.2.4. Building RPMs with the rpmbuild command</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch08s02.html" title="8.2. Building RPMs" /><link rel="prev" href="ch08s02s03s06.html" title="8.2.3.6. The files section" /><link rel="next" href="ch08s03.html" title="8.3. Verifying Your RPMS" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch08s02s03s06.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch08s03.html"><strong>ÃŽnainte</strong></a></li>
</ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id831271" class="title">Building RPMs with the rpmbuild command</h1></div></div></div><div class="para">
+ To build RPMs with the rpmbuild command, use the following basic syntax:
+ </div><div class="para">
+ rpmbuild -bBuildStage spec_file
+ </div><div class="para">
+ The -b option tells rpmbuild to build an RPM. The extra BuildStage option is a special code that tells the rpmbuild command how far to go when building. Table 9-2 lists these options:
+ </div><div class="para">
+ Table 9-2 Options for building with rpmbuild
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Option
+ </div>
+
+ </td><td>
+ <div class="para">
+ Usage
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -ba
+ </div>
+
+ </td><td>
+ <div class="para">
+ Build all, both a binary and source RPM
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -bb
+ </div>
+
+ </td><td>
+ <div class="para">
+ Build a binary RPM
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -bc
+ </div>
+
+ </td><td>
+ <div class="para">
+ Build (compile) the program but do not make the full RPM, stopping just after the %build section
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -bp
+ </div>
+
+ </td><td>
+ <div class="para">
+ Prepare for building a binary RPM, and stop just after the %prep section
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -bi
+ </div>
+
+ </td><td>
+ <div class="para">
+ Create a binary RPM and stop just after the %install section
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -bl
+ </div>
+
+ </td><td>
+ <div class="para">
+ Check the listing of files for the RPM and generate errors if the buildroot is missing any of the files to be installed
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -bs
+ </div>
+
+ </td><td>
+ <div class="para">
+ Build a source RPM only
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ Note
+ </div><div class="para">
+ See chapter 12 for advanced options you can use with rpmbuild.
+ </div><div class="para">
+ For example, to set up all the necessary files and prepare for building, run the following command:
+ </div><div class="para">
+ rpmbuild –bp specfile
+ </div><div class="para">
+ This example runs through the %prep section, and stops immediately after this section. With the jikes package, for example, you’ll see a result like the following:
+ </div><div class="para">
+ $ rpmbuild -bp /usr/src/redhat/SPECS/jikes.spec
+ </div><div class="para">
+ Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.72435
+ </div><div class="para">
+ + umask 022
+ </div><div class="para">
+ + cd /usr/src/redhat/BUILD
+ </div><div class="para">
+ + LANG=C
+ </div><div class="para">
+ + export LANG
+ </div><div class="para">
+ + cd /usr/src/redhat/BUILD
+ </div><div class="para">
+ + rm -rf jikes-1.17
+ </div><div class="para">
+ + /usr/bin/gzip -dc /usr/src/redhat/SOURCES/jikes-1.17.tar.gz
+ </div><div class="para">
+ + tar -xf -
+ </div><div class="para">
+ + STATUS=0
+ </div><div class="para">
+ + '[' 0 -ne 0 ']'
+ </div><div class="para">
+ + cd jikes-1.17
+ </div><div class="para">
+ ++ /usr/bin/id -u
+ </div><div class="para">
+ + '[' 500 = 0 ']'
+ </div><div class="para">
+ ++ /usr/bin/id -u
+ </div><div class="para">
+ + '[' 500 = 0 ']'
+ </div><div class="para">
+ + /bin/chmod -Rf a+rX,g-w,o-w .
+ </div><div class="para">
+ + exit 0
+ </div><div class="para">
+ After running this command, the source files are extracted into the /usr/src/redhat/BUILD directory, under the jikes-1.17 subdirectory. Using a subdirectory keeps the sources for this package from intermixing with the sources for other packages.
+ </div><div class="para">
+ Running a directory listing on the /usr/src/redhat/BUILD/jikes-1.17 subdirectory shows what the spec file %prep section commands have done. For example:
+ </div><div class="para">
+ $ ls -1 /usr/src/redhat/BUILD/jikes-1.17
+ </div><div class="para">
+ acinclude.m4
+ </div><div class="para">
+ aclocal.m4
+ </div><div class="para">
+ AUTHORS
+ </div><div class="para">
+ ChangeLog
+ </div><div class="para">
+ config.guess
+ </div><div class="para">
+ config.sub
+ </div><div class="para">
+ configure
+ </div><div class="para">
+ configure.in
+ </div><div class="para">
+ COPYING
+ </div><div class="para">
+ depcomp
+ </div><div class="para">
+ doc
+ </div><div class="para">
+ INSTALL
+ </div><div class="para">
+ install-sh
+ </div><div class="para">
+ jikes.spec
+ </div><div class="para">
+ Makefile.am
+ </div><div class="para">
+ Makefile.in
+ </div><div class="para">
+ missing
+ </div><div class="para">
+ mkinstalldirs
+ </div><div class="para">
+ NEWS
+ </div><div class="para">
+ README
+ </div><div class="para">
+ src
+ </div><div class="para">
+ TODO
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ From these sources, you see a configure script. The configure script gives a good indication of how the software needs to be built. This example also shows a README file. You know what to do with these files.
+ </div><div class="para">
+ The actual source code is in the /usr/src/redhat/BUILD/jikes-1.17/src directory. The user documentation is stored in the /usr/src/redhat/BUILD/jikes-1.17/doc directory.
+ </div><div class="para">
+ To build a binary RPM, use the –bb option to the rpmbuild command. For example:
+ </div><div class="para">
+ $ rpmbuild -bb /usr/src/redhat/SPECS/jikes.spec
+ </div><div class="para">
+ Warning
+ </div><div class="para">
+ Don’t build packages when you are logged in as the root user. Log in as a normal user instead. This is to limit the damage caused to your system if the spec file or the Makefile contains errors that delete system files, for example. If you are logged in as the root user, you will have permission to perform these destructive acts. If you are logged in as a normal user, though, these RPM spec file and Makefile errors will fail to run, because you don’t have permission to modify system files.
+ </div><div class="para">
+ This command results in a lot of output, most coming from the configure script. (This script examines the C programming environment on your system.) When the rpmbuild command completes, you’ll see the binary RPM in the proper subdirectory of the RPMS directory. You can see the RPM with a directory listing, for example:
+ </div><div class="para">
+ $ls /usr/src/redhat/RPMS/i386:
+ </div><div class="para">
+ jikes-1.17-1.i386.rpm
+ </div><div class="para">
+ To stop execution just after the %install section, use a command like the following:
+ </div><div class="para">
+ rpmbuild –bi specfile
+ </div><div class="para">
+ For example:
+ </div><div class="para">
+ # rpmbuild -bi /usr/src/redhat/SPECS/jikes.spec
+ </div><div class="para">
+ To build a source RPM out of the files you have (in this case a tar archive of the sources and the spec file), use a command like the following:
+ </div><div class="para">
+ rpmbuild –bs specfile
+ </div><div class="para">
+ For example:
+ </div><div class="para">
+ $ rpmbuild -bs /usr/src/redhat/SPECS/jikes.spec
+ </div><div class="para">
+ When done, you’ll see the source RPM in the /usr/src/redhat/SRPMS directory:
+ </div><div class="para">
+ $ ls /usr/src/redhat/SRPMS
+ </div><div class="para">
+ jikes-1.17-1.src.rpm
+ </div><div class="para">
+ To clean out the files created by building these RPMs, use the --clean option to the rpmbuild command:
+ </div><div class="para">
+ rpmbuild --clean specfile
+ </div><div class="para">
+ For example:
+ </div><div class="para">
+ $ rpmbuild --clean /usr/src/redhat/SPECS/jikes.spec
+ </div><div class="para">
+ Executing(--clean): /bin/sh -e /var/tmp/rpm-tmp.21908
+ </div><div class="para">
+ + umask 022
+ </div><div class="para">
+ + cd /usr/src/redhat/BUILD
+ </div><div class="para">
+ + rm -rf jikes-1.17
+ </div><div class="para">
+ + exit 0
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ <a class="xref" href="ch-rpmbuild.html">Cap. 11, <em>Controlling the Build with <code class="command">rpmbuild</code></em></a> covers a number of addition options for the rpmbuild command that you can use to customize the build.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch08s02s03s06.html"><strong>Înapoi</strong>8.2.3.6. The files section</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch08s03.html"><strong>Înainte</strong>8.3. Verifying Your RPMS</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch08s03.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch08s03.html
new file mode 100644
index 0000000..cd14f00
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch08s03.html
@@ -0,0 +1,59 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>8.3. Verifying Your RPMS</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-creating-rpms.html" title="Cap. 8. Creating RPMs: An Overview" /><link rel="prev" href="ch08s02s04.html" title="8.2.4. Building RPMs with the rpmbuild command" /><link rel="next" href="ch08s04.html" title="8.4. Summary" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch08s02s04.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch08s04.html"><strong
>ÃŽnainte</strong></a></li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id772204" class="title">Verifying Your RPMS</h1></div></div></div><div class="para">
+ After you've built an RPM, you can use the techniques from <a class="xref" href="ch-using-rpm-db.html">Cap. 4, <em>Using the RPM Database</em></a> to verify the RPM. You can also use the –bl option to the rpmbuild command to verify the list of files in the RPM. Use a command like the following:
+ </div><div class="para">
+ rpmbuild –bl spec_file
+ </div><div class="para">
+ For example:
+ </div><div class="para">
+ $ rpmbuild -bl /usr/src/redhat/SPECS/jikes.spec
+ </div><div class="para">
+ Processing files: jikes-1.17-1
+ </div><div class="para">
+ error: File not found: /tmp/jikesrpm/usr/bin/jikes
+ </div><div class="para">
+ error: File not found: /tmp/jikesrpm/usr/doc/jikes-1.17/license.htm
+ </div><div class="para">
+ error: File not found by glob: /tmp/jikesrpm/usr/man/man1/jikes.1*
+ </div><div class="para">
+ Provides: jikes
+ </div><div class="para">
+ </div><div class="para">
+ </div><div class="para">
+ RPM build errors:
+ </div><div class="para">
+ File not found: /tmp/jikesrpm/usr/bin/jikes
+ </div><div class="para">
+ File not found: /tmp/jikesrpm/usr/doc/jikes-1.17/license.htm
+ </div><div class="para">
+ File not found by glob: /tmp/jikesrpm/usr/man/man1/jikes.1*
+ </div><div class="para">
+ This example shows a number of errors. The -bl option checks that all the necessary files are located within the buildroot directory. The buildroot directory is a location that acts like the final installed root directory. From the previous example, this package was not properly built yet.
+ </div><div class="para">
+ In a situation like this, you can start over, or use the --short-circuit option to restart the build from a given section in the spec file. As you create an RPM, you will need to go back and forth restarting the build as you detect and fix errors.
+ </div><div class="para">
+ </div><div class="para">
+ You can also use the rpm command with options such as –V for verification on a fully-built package. For example:
+ </div><div class="para">
+ $ rpm -Vp /usr/src/redhat/RPMS/i386/jikes-1.17-1.i386.rpm
+ </div><div class="para">
+ S.5....T /usr/bin/jikes
+ </div><div class="para">
+ .......T d /usr/doc/jikes-1.17/license.htm
+ </div><div class="para">
+ ..5....T d /usr/man/man1/jikes.1.gz
+ </div><div class="para">
+ In this case, you see some file sizes and times differ. These differences can be explained by the fact that the original package was compiled on a different system and older version of Red Hat Linux than the version compiled locally.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ See the on "Verifying Installed RPM Packages" section in <a class="xref" href="ch-using-rpm-db.html">Cap. 4, <em>Using the RPM Database</em></a> for more on the -V option.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch08s02s04.html"><strong>Înapoi</strong>8.2.4. Building RPMs with the rpmbuild command</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch08s04.html"><strong>Înainte</strong>8.4. Summary</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch08s04.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch08s04.html
new file mode 100644
index 0000000..ec60d8f
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch08s04.html
@@ -0,0 +1,18 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>8.4. Summary</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-creating-rpms.html" title="Cap. 8. Creating RPMs: An Overview" /><link rel="prev" href="ch08s03.html" title="8.3. Verifying Your RPMS" /><link rel="next" href="ch-specfiles.html" title="Cap. 9. Working with Spec Files" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch08s03.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch-specfiles.html"><stron
g>ÃŽnainte</strong></a></li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id859247" class="title">Summary</h1></div></div></div><div class="para">
+ This chapter introduced the task of building RPMs, whether building RPMs from your own applications or from software you have gathered elsewhere. In both cases, the steps for building the RPMs are the same.
+ </div><div class="para">
+ In most cases, you should build an RPM of the sources for your application, an RPM that can be used to reproduce the build of the application. Create a second RPM that holds the binary application. Once you set up the commands and define the spec file for the binary RPM, making a source RPM is trivial.
+ </div><div class="para">
+ Use the rpmbuild command to create RPMs. This command uses an RPM spec file to define the commands and settings for creating the RPM.
+ </div><div class="para">
+ The next chapter delves into the spec files that define the RPM directives for your packages.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch08s03.html"><strong>Înapoi</strong>8.3. Verifying Your RPMS</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch-specfiles.html"><strong>Înainte</strong>Cap. 9. Working with Spec Files</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch09s02.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch09s02.html
new file mode 100644
index 0000000..6da000c
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch09s02.html
@@ -0,0 +1,52 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>9.2. Writing Spec Files</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-specfiles.html" title="Cap. 9. Working with Spec Files" /><link rel="prev" href="ch-specfiles.html" title="Cap. 9. Working with Spec Files" /><link rel="next" href="ch09s02s02.html" title="9.2.2. Storing spec files on disk" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-specfiles.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch09s02s02.html
"><strong>ÃŽnainte</strong></a></li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id588340" class="title">Writing Spec Files</h1></div></div></div><div class="para">
+ Spec files are text files containing RPM directives. These directives use a simple syntax of a tag name, a colon, and a value:
+ </div><div class="para">
+ TagName: value
+ </div><div class="para">
+ For example:
+ </div><div class="para">
+ Version: 1.15
+ </div><div class="para">
+ This example sets the package version to 1.15. The name of the item is not case sensitive, so tag names of version, Version, or VERSION all set the same value. This syntax works for most settings, including Name, Release, and so on.
+ </div><div class="para">
+ In addition to this directive syntax, you can define macros using the RPM %define syntax. For example:
+ </div><div class="para">
+ %define major 2
+ </div><div class="para">
+ This example defines a macro named major with a value of 2. Once defined, you can access macros using the %{macro_name} or just %macro_name syntaxes. For example:
+ </div><div class="para">
+ source: %{name}-%{version}.tar.gz
+ </div><div class="para">
+ See the section "Defining Spec File Macros" later in this chapter for more options for macros.
+ </div><div class="para">
+ Major sections in the spec file are also delimited with % markers. For example, the build section starts with %build on a line by itself.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ The multiple uses of the % sign aren’t really that confusing in practice. Read through some spec files and you should find most of the commands are easily understood.
+ </div><div class="para">
+ Blank lines separate sections in the spec file, which makes sense for readability as well.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id686530" class="title">Comments</h1></div></div></div><div class="para">
+ To help document your work, you can include comments (to yourself and others reading the spec file). Any line starting with a hash character, #, holds a comment. RPM will ignore comments.
+ </div><div class="para">
+ # This is a comment.
+ </div><div class="para">
+ In spec files, comments are mostly to help explain your syntax choices to yourself should you view the spec file later. Comments are a good thing. You should comment heavily, especially for any choice that deviates from the norm. For example, if you provide special C compiler options for building the package, add comments to describe why you picked the options and how necessary they are. Such comments help immensely should you need to port the RPM to another architecture or modify how it was built.
+ </div><div class="para">
+ Tip
+ </div><div class="para">
+ Avoid single percent signs, %, in comments. For example:
+ </div><div class="para">
+ # Added new commands to %prep
+ </div><div class="para">
+ The rpmbuild command may report an error of a second %prep section. To get around this problem, use two percent signs, such as %%prep, in spec file comments.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-specfiles.html"><strong>Înapoi</strong>Cap. 9. Working with Spec Files</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch09s02s02.html"><strong>Înainte</strong>9.2.2. Storing spec files on disk</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch09s02s02.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch09s02s02.html
new file mode 100644
index 0000000..da075b7
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch09s02s02.html
@@ -0,0 +1,82 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>9.2.2. Storing spec files on disk</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch09s02.html" title="9.2. Writing Spec Files" /><link rel="prev" href="ch09s02.html" title="9.2. Writing Spec Files" /><link rel="next" href="ch09s03.html" title="9.3. Defining Package Information" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch09s02.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch09s03.html"><strong>ÃŽnainte</strong></a></li><
/ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id686572" class="title">Storing spec files on disk</h1></div></div></div><div class="para">
+ As discussed in <a class="xref" href="ch-creating-rpms.html">Cap. 8, <em>Creating RPMs: An Overview</em></a> , the rpmbuild command expands source RPMs to the /usr/src/redhat directory. Under this directory, the RPM system assumes five subdirectories, listed in Table 10-1.
+ </div><div class="para">
+ Table 10-1 Default RPM directories
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Directory
+ </div>
+
+ </td><td>
+ <div class="para">
+ Usage
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ BUILD
+ </div>
+
+ </td><td>
+ <div class="para">
+ Where the rpmbuild command builds software
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMS
+ </div>
+
+ </td><td>
+ <div class="para">
+ Where the rpmbuild command stores binary RPMs it creates
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ SOURCES
+ </div>
+
+ </td><td>
+ <div class="para">
+ Where you should put the sources for the application
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ SPECS
+ </div>
+
+ </td><td>
+ <div class="para">
+ Where you should place the spec file
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ SRPMS
+ </div>
+
+ </td><td>
+ <div class="para">
+ Where the rpmbuild command places source RPMs
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ The spec files you create should be stored in the SPECS directory while building RPMs. (You can store your spec files permanently in any location you desire.)
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ These directories are the default directories. See <a class="xref" href="ch-specfile-syntax.html">Cap. 22, <em>Spec File Syntax</em></a> for changing RPM default values. In addition, these are the defaults for Red Hat Linux. See <a class="xref" href="ch-other-linuxes.html">Cap. 18, <em>Using RPM on Non-Red Hat Linuxes</em></a> and <a class="xref" href="ch-other-linuxes.html">Cap. 18, <em>Using RPM on Non-Red Hat Linuxes</em></a> for discussions on other versions of Linux and other non-Linux operating systems, respectively.
+ </div><div class="para">
+ With the knowledge of the spec file syntax covered in the preceding sections, you can start to write spec files. The first step is to define the basic package information.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch09s02.html"><strong>Înapoi</strong>9.2. Writing Spec Files</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch09s03.html"><strong>Înainte</strong>9.3. Defining Package Information</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch09s03.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch09s03.html
new file mode 100644
index 0000000..9ff60ee
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch09s03.html
@@ -0,0 +1,142 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>9.3. Defining Package Information</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-specfiles.html" title="Cap. 9. Working with Spec Files" /><link rel="prev" href="ch09s02s02.html" title="9.2.2. Storing spec files on disk" /><link rel="next" href="ch09s03s02.html" title="9.3.2. Setting build locations" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch09s02s02.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch09s03s02.html"><st
rong>ÃŽnainte</strong></a></li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id750601" class="title">Defining Package Information</h1></div></div></div><div class="para">
+ Most of the package information you need to enter into a spec file fleshes out the information you can query for a given package, such as the name, version, and release information, along with a longer description and a one-line summary.
+ </div><div class="para">
+ This gets a little more complicated when you set build locations, name source files, and name patches. The following sections cover how to specify the package information.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id562505" class="title">Describing the package</h1></div></div></div><div class="para">
+ The first part of the spec file defines macros (covered in the section "Defining Spec File Macros"), and describes the package. Starting with the basics, you need a name, version, and release. You also should provide a longer description. For legal reasons, you may need to include ownership and copyright information.
+ </div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id562518" class="title">Naming the Package</h1></div></div></div><div class="para">
+ The most important part of the package description is the NVR, or Name-Version-Release information, because this information is so crucial for the RPM system to compare versions and track dependencies.
+ </div><div class="para">
+ Set the name with the Name: directive. For example:
+ </div><div class="para">
+ Name: myapp
+ </div><div class="para">
+ The name should not contain any spaces or other whitespace characters such as tabs or newlines. Remember, RPM files are named, by default, name-version-release.rpm, or name-version-release-architecture.rpm, so use valid characters for file names.
+ </div><div class="para">
+ The version number is used in version comparisons. The RPM comparison algorithm is fairly complex, but can get fooled by strange version numbers. So, your best bet is to stick to dotted numerics, such as 1.5 or 2.3.1.1.4 or 1.0. Version numbers such as these will compare best from within the RPM system. For example:
+ </div><div class="para">
+ Version: 1.1.2
+ </div><div class="para">
+ You cannot use a dash in the version number, as RPM uses the dash to separate the Name-Version-Release elements. You can use a dash in the package name, though.
+ </div><div class="para">
+ The release number should start at 1 for the first RPM you build for a given version of the package, and count up from there. For example:
+ </div><div class="para">
+ Release: 1
+ </div><div class="para">
+ The release differentiates newer updates of the RPM itself, even if the underlying application hasn’t changed. (The application may be compiled with different compiler options, though.) For most usage, simply start at 1 and each time you modify the spec file and recreate the package, increment the release number.
+ </div><div class="para">
+ If the version number is not enough to allow for comparisons, for example, if the version numbering scheme has changed radically between releases, you can define an Epoch: directive. For example:
+ </div><div class="para">
+ Epoch: 3
+ </div><div class="para">
+ If you renumber your versions, use an Epoch setting to clarify the version history. For example, Sun Microsystems went from SunOS 4.1 to Solaris 2. The Epoch: helps RPM properly handle strange version number changes. Define the Epoch: as a whole number such as 1, 2, or 3.
+ </div><div class="para">
+ Warning
+ </div><div class="para">
+ Avoid using the Epoch: directive if at all possible. It is far better to use a sane version-numbering scheme than to try to resolve the mess with epoch values. The main problems with using an epoch value are that epochs are hidden from users in most cases, and using epochs can lead to very strange-looking tasks such as a newer package with a version number that looks older than the older package.
+ </div><div class="para">
+ The older Serial: directive also works similarly to the Epoch: directive. For example:
+ </div><div class="para">
+ Serial: 6
+ </div><div class="para">
+ Like the Epoch:, the Serial: directive should be a number that counts upward. Modern packages should use the Epoch: directive instead of Serial:, since Serial: has been deprecated for many, many rpm versions.
+ </div><div class="para">
+ The Group: directive provides a classification for your packages. If at all possible, use a category name that already exists for other packages, such as System Environment/Shells for a Linux shell. For example:
+ </div><div class="para">
+ Group: System Environment/Shells
+ </div><div class="para">
+ Many graphical installation tools divide packages by these categories, so you want to fit into the existing group names if possible. (See <a class="xref" href="ch-using-rpm-db.html">Cap. 4, <em>Using the RPM Database</em></a> for more on querying group information from RPMs.) The official list of groups are located in the file /usr/share/doc/rpm-4.1/GROUPS for RPM 4.1, and in a similar location for other RPM versions.
+ </div><div class="para">
+ The Distribution: directive is used by Linux distribution vendors such as Red Hat to identify that the package is part of a given distribution, or was built for a particular distribution. Most packages created outside of the Linux vendors don’t provide this directive.
+ </div><div class="para">
+ Distribution: Red Hat Linux
+ </div><div class="para">
+ The Icon: directive names an icon file stored in the RPM. The file format should be XPM or GIF, with an extension of .xpm or .gif, respectively. Some packaging tools will use this icon in a package display.
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id565381" class="title">Specifying Company Information</h1></div></div></div><div class="para">
+ For legal reasons, you probably want to specify the organization behind the RPM, any copyright or licensing information, as well as a URL to find out more information. Even if you are not concerned about corporate legal issues, you may want to identify where the package came from. Use the following directives to provide this information.
+ </div><div class="para">
+ The Vendor: directive names the company or organization behind an RPM. For example:
+ </div><div class="para">
+ Vendor: The Really Cool Company
+ </div><div class="para">
+ The URL: directive provides a URL to your company or organization home page, or perhaps to a URL for a particular application. For example:
+ </div><div class="para">
+ URL: http://mycompany.yow/products/coolstuff
+ </div><div class="para">
+ Similarly, the Packager: directive provides an optional name and e-mail address for the person who created the RPM:
+ </div><div class="para">
+ Packager: Bob Marley <marley at reggae.com>
+ </div><div class="para">
+ The License: and Copyright: directives provide legal information about your package. Older packages tended to use Copyright: as a statement of the package’s license, not copyright. For example:
+ </div><div class="para">
+ Copyright: BSD
+ </div><div class="para">
+ License: LGPL
+ </div><div class="para">
+ Warning
+ </div><div class="para">
+ The Copyright: directive is deprecated in favor of License:.
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id700765" class="title">Filling in the Description</h1></div></div></div><div class="para">
+ The Summary: directive provides a one-line short description of the package. You should not exceed much more than 50 characters when writing your summary. For example:
+ </div><div class="para">
+ Summary: A program that does exactly what you want
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ The Summary: directive of the spec file replaces the older Description: directive.
+ </div><div class="para">
+ The %description section allows for longer text describing your package. Fill in as many lines as you need after the %description section. For example:
+ </div><div class="para">
+ %description
+ </div><div class="para">
+ This is a really cool package. It contains the really cool
+ </div><div class="para">
+ program that provides a maximum return on investment,
+ </div><div class="para">
+ or ROI, for achieving your crucial business objectives
+ </div><div class="para">
+ utilizing world-class high-caliber componentized software
+ </div><div class="para">
+ implemented with world-class quality and performance
+ </div><div class="para">
+ metrics.
+ </div><div class="para">
+ The %description section supports a limited amount of formatting. Blank lines are assumed to separate paragraphs. Some graphical user interface installation programs will reformat paragraphs into a nicer-looking font and change the display width.
+ </div><div class="para">
+ Lines in the %description section that start with whitespace, such as a space or tab, will be treated as preformatted text and displayed as is, normally with a fixed-width font. The rpm command supports text formatting this way. Other rpm programs may not.
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id742346" class="title">Specifying the Platform Architecture</h1></div></div></div><div class="para">
+ Spec files can announce that a package can run on more than one operating system or is tied to a particular version of a particular operating system.
+ </div><div class="para">
+ For example, the Excludearch: directive states that a package should not be built on the given architecture or architectures. For example:
+ </div><div class="para">
+ ExcludeArch: sparc s390 s390x
+ </div><div class="para">
+ This example excludes the SPARC and S/390 mainframe architectures. You can provide more than one architecture in the directive, separated by spaces or commas.
+ </div><div class="para">
+ Similarly, the Exclusivearch: directive states that a package can only be built on the given architecture or architectures. For example:
+ </div><div class="para">
+ ExclusiveArch: i386 ia64 alpha
+ </div><div class="para">
+ This example identifies the package as only working on the Intel i386, IA-64, and Alpha architectures.
+ </div><div class="para">
+ The Excludeos: and Exclusiveos: directives restrict the operating system. For example:
+ </div><div class="para">
+ Excludeos: windows
+ </div><div class="para">
+ This example states that the package should not be built on Windows. In contrast, the Exclusiveos: directive names only the operating system or systems that the package can be built on. For example:
+ </div><div class="para">
+ Exclusiveos: linux
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ <a class="xref" href="ch-other-linuxes.html">Cap. 18, <em>Using RPM on Non-Red Hat Linuxes</em></a> and <a class="xref" href="ch-other-os.html">Cap. 19, <em>RPM on Other Operating Systems</em></a> cover RPMs on other versions of Linux and other operating systems, respectively.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch09s02s02.html"><strong>Înapoi</strong>9.2.2. Storing spec files on disk</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch09s03s02.html"><strong>Înainte</strong>9.3.2. Setting build locations</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch09s03s02.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch09s03s02.html
new file mode 100644
index 0000000..591d50f
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch09s03s02.html
@@ -0,0 +1,33 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>9.3.2. Setting build locations</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch09s03.html" title="9.3. Defining Package Information" /><link rel="prev" href="ch09s03.html" title="9.3. Defining Package Information" /><link rel="next" href="ch09s03s03.html" title="9.3.3. Naming source files" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch09s03.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch09s03s03.html"><strong>ÃŽnainte
</strong></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id587414" class="title">Setting build locations</h1></div></div></div><div class="para">
+ RPM supports two build-related directories with very similar names, the build directory and the buildroot.
+ </div><div class="para">
+ The build directory is the location where RPM actually builds the software, compiling source code, running the configure script, and so on. Normally, you do not need to worry about the build directory as the rpmbuild command properly changes to this directory as needed.
+ </div><div class="para">
+ The buildroot, on the other hand, acts as a staging area that looks like the final installation directory. The name buildroot refers to the fact that the final installation directory is usually the root directory, /. The install section of the spec file (covered in the section "Installing the Software") installs files into the buildroot directory in the proper subdirectories, as if the files were really under the system root directory, /. This allows the buildroot directory to hold all the final installed files for a package, so you can see what will really be installed by the package.
+ </div><div class="para">
+ You should always set the buildroot by defining a Buildroot: entry in your spec file. For example:
+ </div><div class="para">
+ </div><div class="para">
+ Buildroot: %{_tmppath}/%{name}-%{version}-root
+ </div><div class="para">
+ This example sets the buildroot under the temporary directory named in the %_tmppath macro. The subdirectory is named based on the name and version of the package. For example, for a package named ypbind and a version 1.12, with a %_tmppath value of /tmp, the final buildroot directory would be:
+ </div><div class="para">
+ /tmp/ypbind-1.12-root
+ </div><div class="para">
+ Once you set a buildroot, your scripts run from the spec file and commands within the spec file can access the buildroot using the RPM_BUILD_ROOT environment variable. You normally need to access the RPM_BUILD_ROOT environment variable in the install section of the spec file (covered in the section "Installing the Software").
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ You can override the buildroot with the --buildroot command-line parameter to the rpmbuild command.
+ </div><div class="para">
+ The buildroot replaces the older, and now obsolete directive, Root:.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch09s03.html"><strong>Înapoi</strong>9.3. Defining Package Information</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch09s03s03.html"><strong>Înainte</strong>9.3.3. Naming source files</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch09s03s03.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch09s03s03.html
new file mode 100644
index 0000000..8d06b2e
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch09s03s03.html
@@ -0,0 +1,48 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>9.3.3. Naming source files</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch09s03.html" title="9.3. Defining Package Information" /><link rel="prev" href="ch09s03s02.html" title="9.3.2. Setting build locations" /><link rel="next" href="ch09s03s04.html" title="9.3.4. Naming patches" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch09s03s02.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch09s03s04.html"><strong>ÃŽnainte</
strong></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id587483" class="title">Naming source files</h1></div></div></div><div class="para">
+ Most packages have one or more bundles of source code, which you need to name in the spec file. In most cases, you will have a compressed tar archive of source files. These may be files developed by your organization or downloaded from an Internet site. You can define one or more source tags, counting from 0. For example:
+ </div><div class="para">
+ Source0: telnet-client.tar.gz
+ </div><div class="para">
+ Source1: telnet-xinetd
+ </div><div class="para">
+ Source2: telnet.wmconfig
+ </div><div class="para">
+ In this example, Source0: refers to a compressed tar archive. The rpmbuild program will extract the files into the buildroot directory. The Source1: and Source2: directives name individual source files. You can name compressed tar archives or individual files as needed.
+ </div><div class="para">
+ If you just have one Source directive, you can skip the 0. For example:
+ </div><div class="para">
+ Source: telnet-client.tar.gz
+ </div><div class="para">
+ You can also use FTP or HTTP URLs to name sources. For example:
+ </div><div class="para">
+ Source0: ftp://ftp.somesite.yow/pub/linux/%{telnet_version}.tar.gz
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ The URLs listed in source directives are for convenience and future reference only. RPM will not download these files.
+ </div><div class="para">
+ The files named by the Source directives will get included into the source RPM. Sometimes you need to keep some sources out of the source RPM. This could be for proprietary sources you cannot ship, or simply due to size. The Nosource: directive tells RPM to skip a source file from the source RPM. For example:
+ </div><div class="para">
+ NoSource: 0
+ </div><div class="para">
+ This example means that the first source item should not be included in the package.
+ </div><div class="para">
+ NoSource: 3
+ </div><div class="para">
+ This example means that the third source item should not be included in the package. The NoPatch directive works similarly. In addition, do not place more than one number on any given NoSource or NoPatch directive.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ Using the Nosource: or NoPatch: directives, covered following, mean you are creating a source RPM that cannot be rebuilt unless you also have the sources or patches, respectively, that were used to create the original RPM.
+ </div><div class="para">
+ If the package contains a Nosource: or Nopatch: directive, rpmbuild will use a file-name extension of .nosrc.rpm instead of .src.rpm.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch09s03s02.html"><strong>Înapoi</strong>9.3.2. Setting build locations</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch09s03s04.html"><strong>Înainte</strong>9.3.4. Naming patches</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch09s03s04.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch09s03s04.html
new file mode 100644
index 0000000..3413fee
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch09s03s04.html
@@ -0,0 +1,42 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>9.3.4. Naming patches</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch09s03.html" title="9.3. Defining Package Information" /><link rel="prev" href="ch09s03s03.html" title="9.3.3. Naming source files" /><link rel="next" href="ch09s04.html" title="9.4. Controlling the Build" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch09s03s03.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch09s04.html"><strong>ÃŽnainte</stron
g></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id747920" class="title">Naming patches</h1></div></div></div><div class="para">
+ Patches are named similar to sources, using a similar syntax. For example:
+ </div><div class="para">
+ Patch1: telnet-client-cvs.patch
+ </div><div class="para">
+ Patch2: telnetd-0.17.diff
+ </div><div class="para">
+ Patch3: telnet-0.17-env.patch
+ </div><div class="para">
+ Patch4: telnet-0.17-issue.patch
+ </div><div class="para">
+ Patch5: telnet-0.17-sa-01-49.patch
+ </div><div class="para">
+ Patch6: telnet-0.17-env-5x.patch
+ </div><div class="para">
+ Patch10: telnet-0.17-pek.patch
+ </div><div class="para">
+ Note that you can have Patch directives are not numbered sequentially, such as the Patch10: directive in this example. In addition, you must apply each patch manually using %patch directives.
+ </div><div class="para">
+ The patch files may be individual files or compressed (with gzip) patch files.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ See the patch and diff online manual pages for more on patches.
+ </div><div class="para">
+ Patches are important because they allow you to start with pristine sources, the source code for the original application. You can then apply patches as needed to get a working application, more clearly separating the work needed to create an RPM from the original application source code.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ <a class="xref" href="ch-packaging-guidelines.html">Cap. 13, <em>Packaging Guidelines</em></a> discusses packaging guidelines and best practices. Starting from pristine sources is one of the best practices.
+ </div><div class="para">
+ Similar to the sources directives, you can define a Nopatch: directive, which defines a patch that is applied to the sources, but is not included in the source RPM.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch09s03s03.html"><strong>Înapoi</strong>9.3.3. Naming source files</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch09s04.html"><strong>Înainte</strong>9.4. Controlling the Build</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch09s04.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch09s04.html
new file mode 100644
index 0000000..89581f5
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch09s04.html
@@ -0,0 +1,162 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>9.4. Controlling the Build</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-specfiles.html" title="Cap. 9. Working with Spec Files" /><link rel="prev" href="ch09s03s04.html" title="9.3.4. Naming patches" /><link rel="next" href="ch09s04s02.html" title="9.4.2. Building the software" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch09s03s04.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch09s04s02.html"><strong>ÃŽnainte<
/strong></a></li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id519194" class="title">Controlling the Build</h1></div></div></div><div class="para">
+ After describing information about the package, the crucial step comes when you need to build the package. The spec file should contain all the commands needed to build the application or library you want to package. But, and this is the important part, most of the build process should be run from a Makefile or other conventional way to build applications. Using a build tool such as make means that you can test the application outside of the RPM system. You don’t need an RPM to build the application. Instead, you use the RPM to package the application.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ <a class="xref" href="ch-creating-rpms.html">Cap. 8, <em>Creating RPMs: An Overview</em></a> covers make and other Linux build tools.
+ </div><div class="para">
+ In RPM terms, building the package is split into four steps:
+ </div><div class="para">
+ 1.Preparing for building, including unpacking the sources
+ </div><div class="para">
+ 2.Building
+ </div><div class="para">
+ 3.Installing the application or library
+ </div><div class="para">
+ 4.Cleaning up
+ </div><div class="para">
+ The next sections cover how to control the build run by rpmbuild by defining commands within your spec files.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id519246" class="title">Preparing for the build</h1></div></div></div><div class="para">
+ The %prep section defines the commands to prepare for the build. In most cases, you can run the simple %setup macro. For example:
+ </div><div class="para">
+ %prep
+ </div><div class="para">
+ %setup -q
+ </div><div class="para">
+ This command changes to the build directory, typically /usr/src/redhat/BUILD, and then extracts the source files. This macro expects that at least one of the source files will create the necessary subdirectory under /usr/src/redhat/BUILD. This subdirectory should be named with the package name and version, such as telnet-1.0.1. If you are not using a compressed tar archive that will automatically create the right subdirectory, add the –c option to the %setup macro. The –c option creates the subdirectory for extracting the sources.
+ </div><div class="para">
+ The –q command-line option runs in quiet mode with minimal output. The –T option disables the automatic extraction of compressed tar files. You can set the name of the build subdirectory with the –n option.
+ </div><div class="para">
+ Normally, the %setup macro deletes the subdirectory prior to extracting the sources. You can disable the directory deletion with the –D option.
+ </div><div class="para">
+ Table 10-2 summarizes the %setup command-line parameters. Many of these options apply mostly for subpackages, a topic covered in <a class="xref" href="ch-advanced-packaging.html">Cap. 10, <em>Creare avansată pachete RPM</em></a> .
+ </div><div class="para">
+ Table 10-2 Command-line parameters for %setup
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Parameter
+ </div>
+
+ </td><td>
+ <div class="para">
+ Usage
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -a number
+ </div>
+
+ </td><td>
+ <div class="para">
+ Only unpack the source directive of the given number, such as –a 0 for source0:, after changing to the directory.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -b number
+ </div>
+
+ </td><td>
+ <div class="para">
+ Only unpack the source directive of the given number, such as –b 0 for source0:, before changing to the directory.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -c
+ </div>
+
+ </td><td>
+ <div class="para">
+ Create directory before unpacking, used if your sources will not create the directory as part of unpacking.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -D
+ </div>
+
+ </td><td>
+ <div class="para">
+ Do not delete the directory before unpacking.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -n name
+ </div>
+
+ </td><td>
+ <div class="para">
+ Name the directory as name.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -q
+ </div>
+
+ </td><td>
+ <div class="para">
+ Run quietly with minimal output.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -T
+ </div>
+
+ </td><td>
+ <div class="para">
+ Disable the automatic unpacking of the archives.
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ The %setup directive can automatically extract tar, zip, gzip, bzip2, pack, compress, and lzh compressed files. The tar-gzip format is most widely used, though.
+ </div><div class="para">
+ Like the %setup macro, the %patch directive applies a patch to the sources. Use this macro in your %prep section if you have patches. You need a %patch directive for each patch.
+ </div><div class="para">
+ The %patch directive accepts –p and other command-line parameters for the underlying patch command. The –p option, with a number, such as –p0, tells the patch command to remove that many slashes from the file names within the patch. A –p0 option tells the patch command to remove no slashes, a –p1 option tells patch to remove one slash, and correspondingly, one directory level from the files in the patch. You can also pass other options for the patch command.
+ </div><div class="para">
+ Use these options if you need them for the patch command when manually patching the sources. Otherwise, you can set up your %prep section as follows, for a spec file with two patches:
+ </div><div class="para">
+ %prep
+ </div><div class="para">
+ %setup –q
+ </div><div class="para">
+ %patch1
+ </div><div class="para">
+ %patch2
+ </div><div class="para">
+ Use numbers to identify which patch to apply. For example, %patch0 corresponds to the patch file named with the Patch0: directive.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ You must define a separate %patch directive for each patch. In most packages, this format, %patch1, %patch2, and so on, is used.
+ </div><div class="para">
+ The %patch directive without a number corresponds to %patch0.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ See the patch and diff online manual pages for more on patches.
+ </div><div class="para">
+ In addition to the options supported by the patch command, you can use special options to the %patch directive to control how the directive works. The –P option tells the %patch directive to apply a given patch. For example, to only apply the patch named with the Patch2: directive, use the following %patch directive:
+ </div><div class="para">
+ %patch –P 2
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ This is an uppercase P. The lowercase p performs a different function, described earlier in this section. The -P option is rarely used. Instead, patches are normally applied with %patch0, %patch1, and so on directives.
+ </div><div class="para">
+ </div><div class="para">
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch09s03s04.html"><strong>Înapoi</strong>9.3.4. Naming patches</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch09s04s02.html"><strong>Înainte</strong>9.4.2. Building the software</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch09s04s02.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch09s04s02.html
new file mode 100644
index 0000000..2e6da8e
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch09s04s02.html
@@ -0,0 +1,81 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>9.4.2. Building the software</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch09s04.html" title="9.4. Controlling the Build" /><link rel="prev" href="ch09s04.html" title="9.4. Controlling the Build" /><link rel="next" href="ch09s04s03.html" title="9.4.3. Installing the software" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch09s04.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch09s04s03.html"><strong>ÃŽnainte</strong><
/a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id569324" class="title">Building the software</h1></div></div></div><div class="para">
+ The %prep section prepares for the build, which the %build section performs. You need to fill in the %build section with all the commands necessary to build the software. In most cases, this consists simply of the following commands:
+ </div><div class="para">
+ %build
+ </div><div class="para">
+ ./configure
+ </div><div class="para">
+ make
+ </div><div class="para">
+ In this case, the %build section runs two commands, ./configure to run the configure script, and make to build the software. For most applications, this may be all you need. You can use the %configure macro in place of the call to the ./configure script. For example:
+ </div><div class="para">
+ %build
+ </div><div class="para">
+ %configure
+ </div><div class="para">
+ make
+ </div><div class="para">
+ Most spec files should use the %configure macro, since it automatically sets many environment variables that are often used within the configure script, especially path-related values such as the online manual path, the temporary directory, and so on. You can use the rpm --eval to see how the %configure macro expands. For example:
+ </div><div class="para">
+ $ rpm --eval '%configure'
+ </div><div class="para">
+ </div><div class="para">
+ CFLAGS="${CFLAGS:--O2 -march=i386 -mcpu=i686}" ; export CFLAGS ;
+ </div><div class="para">
+ CXXFLAGS="${CXXFLAGS:--O2 -march=i386 -mcpu=i686}" ; export CXXFLAGS ;
+ </div><div class="para">
+ FFLAGS="${FFLAGS:--O2 -march=i386 -mcpu=i686}" ; export FFLAGS ;
+ </div><div class="para">
+ [ -f configure.in ] && libtoolize --copy --force ;
+ </div><div class="para">
+ ./configure i386-redhat-linux \
+ </div><div class="para">
+ --prefix=/usr \
+ </div><div class="para">
+ --exec-prefix=/usr \
+ </div><div class="para">
+ --bindir=/usr/bin \
+ </div><div class="para">
+ --sbindir=/usr/sbin \
+ </div><div class="para">
+ --sysconfdir=/etc \
+ </div><div class="para">
+ --datadir=/usr/share \
+ </div><div class="para">
+ --includedir=/usr/include \
+ </div><div class="para">
+ --libdir=/usr/lib \
+ </div><div class="para">
+ --libexecdir=/usr/libexec \
+ </div><div class="para">
+ --localstatedir=/var \
+ </div><div class="para">
+ --sharedstatedir=/usr/com \
+ </div><div class="para">
+ --mandir=/usr/share/man \
+ </div><div class="para">
+ --infodir=/usr/share/info
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ The vast majority of the work of building the software should remain in the Makefile where it belongs. The commands in the spec file should invoke the targets defined in the Makefile. Don’t place too much logic in your RPM spec file as this makes it harder to test the application or library you plan to package.
+ </div><div class="para">
+ If you intend to support relocatable packages, covered in <a class="xref" href="ch-advanced-packaging.html">Cap. 10, <em>Creare avansată pachete RPM</em></a> , you will likely need to pass a --prefix option to the configure script. For example:
+ </div><div class="para">
+ %build
+ </div><div class="para">
+ ./configure --prefix=$RPM_BUILD_ROOT/usr
+ </div><div class="para">
+ make
+ </div><div class="para">
+ You can also pass other options to the configure script, as needed, for compiling the application.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch09s04.html"><strong>Înapoi</strong>9.4. Controlling the Build</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch09s04s03.html"><strong>Înainte</strong>9.4.3. Installing the software</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch09s04s03.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch09s04s03.html
new file mode 100644
index 0000000..5ec9b8b
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch09s04s03.html
@@ -0,0 +1,73 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>9.4.3. Installing the software</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch09s04.html" title="9.4. Controlling the Build" /><link rel="prev" href="ch09s04s02.html" title="9.4.2. Building the software" /><link rel="next" href="ch09s04s04.html" title="9.4.4. Cleaning up after the build" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch09s04s02.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch09s04s04.html"><strong>ÃŽnain
te</strong></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id692442" class="title">Installing the software</h1></div></div></div><div class="para">
+ The %install section should install the software built in the %build section. If your Makefile contains all the instructions to install, you can define an %install section as follows:
+ </div><div class="para">
+ %install
+ </div><div class="para">
+ make install PREFIX=$RPM_BUILD_ROOT/usr
+ </div><div class="para">
+ In most cases, you need to pass some parameter to make or install or another command to install all files into the buildroot directory, as shown in this example with the $RPM_BUILD_ROOT environment variable. You need to look within the Makefile to determine if the make variable should be PREFIX, prefix, or something else.
+ </div><div class="para">
+ Sometimes, you want to call the install command instead of make to perform the installation. For example:
+ </div><div class="para">
+ %install
+ </div><div class="para">
+ install -m755 myapp $RPM_BUILD_ROOT/usr/bin/myapp
+ </div><div class="para">
+ This example uses a hypothetical application name of myapp.
+ </div><div class="para">
+ Many packages use the %makeinstall macro, which runs the make install command. For example:
+ </div><div class="para">
+ %install
+ </div><div class="para">
+ rm -rf $RPM_BUILD_ROOT
+ </div><div class="para">
+ %makeinstall
+ </div><div class="para">
+ This example also cleans the files from the buildroot. Use the rpm --eval command to see how the %makeinstall macro expands. For example:
+ </div><div class="para">
+ $ rpm --eval '%makeinstall'
+ </div><div class="para">
+ </div><div class="para">
+ make \
+ </div><div class="para">
+ prefix=/usr \
+ </div><div class="para">
+ exec_prefix=/usr \
+ </div><div class="para">
+ bindir=/usr/bin \
+ </div><div class="para">
+ sbindir=/usr/sbin \
+ </div><div class="para">
+ sysconfdir=/etc \
+ </div><div class="para">
+ datadir=/usr/share \
+ </div><div class="para">
+ includedir=/usr/include \
+ </div><div class="para">
+ libdir=/usr/lib \
+ </div><div class="para">
+ libexecdir=/usr/libexec \
+ </div><div class="para">
+ localstatedir=/var \
+ </div><div class="para">
+ sharedstatedir=/usr/com \
+ </div><div class="para">
+ mandir=/usr/share/man \
+ </div><div class="para">
+ infodir=/usr/share/info \
+ </div><div class="para">
+ install
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ RPM 4.2 adds a %check section after the %install.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch09s04s02.html"><strong>Înapoi</strong>9.4.2. Building the software</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch09s04s04.html"><strong>Înainte</strong>9.4.4. Cleaning up after the build</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch09s04s04.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch09s04s04.html
new file mode 100644
index 0000000..2e95d85
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch09s04s04.html
@@ -0,0 +1,16 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>9.4.4. Cleaning up after the build</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch09s04.html" title="9.4. Controlling the Build" /><link rel="prev" href="ch09s04s03.html" title="9.4.3. Installing the software" /><link rel="next" href="ch09s04s05.html" title="9.4.5. Defining installation scripts" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch09s04s03.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch09s04s05.html"><strong>ÃŽ
nainte</strong></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id566787" class="title">Cleaning up after the build</h1></div></div></div><div class="para">
+ The %clean section should clean up after the build and installation, removing compiled files and other files created as part of the build. If you use a buildroot, discussed previously, then you can provide a %clean section like the following:
+ </div><div class="para">
+ %clean
+ </div><div class="para">
+ rm -rf $RPM_BUILD_ROOT
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch09s04s03.html"><strong>Înapoi</strong>9.4.3. Installing the software</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch09s04s05.html"><strong>Înainte</strong>9.4.5. Defining installation scripts</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch09s04s05.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch09s04s05.html
new file mode 100644
index 0000000..000fa19
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch09s04s05.html
@@ -0,0 +1,100 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>9.4.5. Defining installation scripts</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch09s04.html" title="9.4. Controlling the Build" /><link rel="prev" href="ch09s04s04.html" title="9.4.4. Cleaning up after the build" /><link rel="next" href="ch09s05.html" title="9.5. Filling the List of Files" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch09s04s04.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch09s05.html"><strong>ÃŽnainte</
strong></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id821253" class="title">Defining installation scripts</h1></div></div></div><div class="para">
+ In addition to the sections described previously for controlling the build of the package software, you can define more scripts in your RPM spec files. RPM supports a script run prior to installation, %pre, and a script run after installation, %post. The same concepts apply when a package is erased, or uninstalled. The %preun script is run just before the uninstall and the %postun script just after the uninstall.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ <a class="xref" href="ch-advanced-packaging.html">Cap. 10, <em>Creare avansată pachete RPM</em></a> covers triggers, another form of script that gets run when packages are installed or removed.
+ </div><div class="para">
+ Start your scripts with the RPM section marker for the given script, such as %pre for the pre-install script. Then, place the shell commands you want to run. For example, the following define %post, %preun and %postun scripts from the ypbind networking package:
+ </div><div class="para">
+ %post
+ </div><div class="para">
+ /sbin/chkconfig --add ypbind
+ </div><div class="para">
+ </div><div class="para">
+ %preun
+ </div><div class="para">
+ if [ "$1" = 0 ] ; then
+ </div><div class="para">
+ /sbin/service ypbind stop > /dev/null 2>&1
+ </div><div class="para">
+ /sbin/chkconfig --del ypbind
+ </div><div class="para">
+ fi
+ </div><div class="para">
+ exit 0
+ </div><div class="para">
+ </div><div class="para">
+ %postun
+ </div><div class="para">
+ if [ "$1" -ge 1 ]; then
+ </div><div class="para">
+ /sbin/service ypbind condrestart > /dev/null 2>&1
+ </div><div class="para">
+ fi
+ </div><div class="para">
+ exit 0
+ </div><div class="para">
+ Few packages need to perform any work prior to installation, so the %pre script is rarely used.
+ </div><div class="para">
+ In this example, the chkconfig command is called to update the runlevel information for system services after installation and prior to removal. This is an example where just installing the application, ypbind in this case, is not enough. Since this application acts as a system service, more work needs to be done to finish the installation with the %pre script or clean up the service on removal with the %preun script.
+ </div><div class="para">
+ Warning
+ </div><div class="para">
+ Do not try to write interactive scripts. Many users install RPMs automatically. In such cases, or if the user runs a graphical RPM tool, any information your scripts output will be lost. User input will not be available.
+ </div><div class="para">
+ The rpm command will pass one argument to your scripts, shown as $1 in the previous example, which holds a count of the number of versions of the package that are installed. Table 10-3 lists the counts for specific cases.
+ </div><div class="para">
+ Table 10-3 Install and uninstall script count values
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Action
+ </div>
+
+ </td><td>
+ <div class="para">
+ Count
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Install the first time
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Upgrade
+ </div>
+
+ </td><td>
+ <div class="para">
+ 2 or higher (depending on the number of versions installed)
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Remove last version of package
+ </div>
+
+ </td><td>
+ <div class="para">
+ 0
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ The previous script example accesses the count using the shell variable $1.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch09s04s04.html"><strong>Înapoi</strong>9.4.4. Cleaning up after the build</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch09s05.html"><strong>Înainte</strong>9.5. Filling the List of Files</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch09s05.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch09s05.html
new file mode 100644
index 0000000..ddc3ffc
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch09s05.html
@@ -0,0 +1,32 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>9.5. Filling the List of Files</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-specfiles.html" title="Cap. 9. Working with Spec Files" /><link rel="prev" href="ch09s04s05.html" title="9.4.5. Defining installation scripts" /><link rel="next" href="ch09s05s02.html" title="9.5.2. Naming directories of files" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch09s04s05.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch09s05s02.ht
ml"><strong>ÃŽnainte</strong></a></li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id762898" class="title">Filling the List of Files</h1></div></div></div><div class="para">
+ The %files section holds a list of all the files that RPM should install from the package. This list should be exhaustive, so that the RPM system knows exactly what your package installs. There are some options, though, to name all the files within a directory to help with packages containing hundreds of files.
+ </div><div class="para">
+ In the default case, each line under the %files section names a separate file with its full path. For example:
+ </div><div class="para">
+ %files
+ </div><div class="para">
+ /usr/X11R6/bin/xtoolwait
+ </div><div class="para">
+ /usr/X11R6/man/man1/xtoolwait.1
+ </div><div class="para">
+ This example lists two files, /usr/X11R6/bin/xtoolwait and /usr/X11R6/man/man1/xtoolwait.1, presumably an online manual files.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id868856" class="title">Using wildcards</h1></div></div></div><div class="para">
+ In addition to naming each file on a line, you can use glob-style wildcards. For example:
+ </div><div class="para">
+ %files
+ </div><div class="para">
+ /usr/X11R6/bin/xtoolwait
+ </div><div class="para">
+ /usr/X11R6/man/man1/xtoolwait.*
+ </div><div class="para">
+ This example states that all files in /usr/X11R6/man/man1 that start with xtoolwait. should be included in the package.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch09s04s05.html"><strong>Înapoi</strong>9.4.5. Defining installation scripts</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch09s05s02.html"><strong>Înainte</strong>9.5.2. Naming directories of files</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch09s05s02.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch09s05s02.html
new file mode 100644
index 0000000..63568a7
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch09s05s02.html
@@ -0,0 +1,34 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>9.5.2. Naming directories of files</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch09s05.html" title="9.5. Filling the List of Files" /><link rel="prev" href="ch09s05.html" title="9.5. Filling the List of Files" /><link rel="next" href="ch09s05s03.html" title="9.5.3. Marking files as documentation or configuration files" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch09s05.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch09s
05s03.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id868884" class="title">Naming directories of files</h1></div></div></div><div class="para">
+ In addition to using wildcard globs, you can specify whole directories as part of your package. For example:
+ </div><div class="para">
+ %files
+ </div><div class="para">
+ /usr/X11R6/bin/xtoolwait
+ </div><div class="para">
+ /etc/xtoolwait
+ </div><div class="para">
+ This example names all the files in the directory /etc/xtoolwait as part of the package. Be very careful when listing this directory. Do not include a system directory such as /usr/bin, as RPM will assume your package owns all of /usr/bin, which contains hundreds of commands. This can be a problem when you try to remove a package.
+ </div><div class="para">
+ It is OK to name a subdirectory that your package owns. For example, while /etc is a system directory, /etc/xtoolwait is a reasonable directory for the xtoolwait package to control.
+ </div><div class="para">
+ If you just want to include an empty directory in the package, and not the files within the directory, use the %dir directive in front of the directory name. For example:
+ </div><div class="para">
+ %files
+ </div><div class="para">
+ /usr/X11R6/bin/xtoolwait
+ </div><div class="para">
+ %dir /etc/xtoolwait
+ </div><div class="para">
+ This example states that the package contains the /usr/X11R6/bin/xtoolwait program and the empty directory /etc/xtoolwait.
+ </div><div class="para">
+ In addition to the straight list of files or directories, RPM provides other options, starting with marking certain files as documentation or configuration files.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch09s05.html"><strong>Înapoi</strong>9.5. Filling the List of Files</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch09s05s03.html"><strong>Înainte</strong>9.5.3. Marking files as documentation or configur...</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch09s05s03.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch09s05s03.html
new file mode 100644
index 0000000..ed841b1
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch09s05s03.html
@@ -0,0 +1,72 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>9.5.3. Marking files as documentation or configuration files</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch09s05.html" title="9.5. Filling the List of Files" /><link rel="prev" href="ch09s05s02.html" title="9.5.2. Naming directories of files" /><link rel="next" href="ch09s05s04.html" title="9.5.4. Setting file attributes" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch09s05s02.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch09s05s04.html"><strong>
ÃŽnainte</strong></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id789362" class="title">Marking files as documentation or configuration files</h1></div></div></div><div class="para">
+ RPM keeps special track of files within a package that hold documentation or configuration data. You need to identify these files with special directives.
+ </div><div class="para">
+ The %doc directive marks a file as a documentation file. For example:
+ </div><div class="para">
+ %files
+ </div><div class="para">
+ /usr/X11R6/bin/xtoolwait
+ </div><div class="para">
+ %doc /usr/X11R6/man/man1/xtoolwait.*
+ </div><div class="para">
+ This example lists all the included files in /usr/X11R6/man/man1 as documentation files.
+ </div><div class="para">
+ If you don’t include the full path to a documentation file or files, the RPM system will create a special documentation directory for the package, and place those files into that directory. For example:
+ </div><div class="para">
+ %doc README NEWS
+ </div><div class="para">
+ This example places the files README and NEWS into a newly created package-specific directory, typically a subdirectory under /usr/share/doc or /usr/doc.
+ </div><div class="para">
+ The %docdir directive names a directory that holds documentation. All files under that directory in the package will get automatically marked as documentation files. For example:
+ </div><div class="para">
+ %files
+ </div><div class="para">
+ /usr/X11R6/bin/xtoolwait
+ </div><div class="para">
+ %docdir /usr/X11R6/man/man1
+ </div><div class="para">
+ /usr/X11R6/man/man1/xtoolwait.*
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ In addition to the marked directories, the standard Linux documentation directories, such as /usr/share/man, are automatically assumed to be documentation directories.
+ </div><div class="para">
+ Similar to the %doc directive, the %config directive marks a file as configuration. For example:
+ </div><div class="para">
+ %files
+ </div><div class="para">
+ /sbin/ypbind
+ </div><div class="para">
+ %config /etc/rc.d/init.d/*
+ </div><div class="para">
+ %config /etc/yp.conf
+ </div><div class="para">
+ %doc README NEWS
+ </div><div class="para">
+ A special option to the %config directive, noreplace, tells RPM not to overwrite, or replace a configuration file. For example:
+ </div><div class="para">
+ %files
+ </div><div class="para">
+ /sbin/ypbind
+ </div><div class="para">
+ %config /etc/rc.d/init.d/*
+ </div><div class="para">
+ %config(noreplace) /etc/yp.conf
+ </div><div class="para">
+ %doc README NEWS
+ </div><div class="para">
+ Use this option to help protect local modifications. If you use %config(noreplace), the file will not overwrite an existing file that has been modified. If the file has not been modified on disk, the rpm command will overwrite the file. But, if the file has been modified on disk, the rpm command will copy the new file with an extra file-name extension of .rpmnew.
+ </div><div class="para">
+ Similarly, %config(missingok) means that the file does not have to exist on disk. You can use this modifier for files or links that are created during the %post scripts but will need to be removed if the package is removed.
+ </div><div class="para">
+ Another special modifier, %ghost, tells the rpm command that the file should not be included in the package. You can use this to name the needed attributes for a file that the program, when installed, will create. For example, you may want to ensure that a program’s log file has certain attributes.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch09s05s02.html"><strong>Înapoi</strong>9.5.2. Naming directories of files</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch09s05s04.html"><strong>Înainte</strong>9.5.4. Setting file attributes</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch09s05s04.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch09s05s04.html
new file mode 100644
index 0000000..6f97fe0
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch09s05s04.html
@@ -0,0 +1,85 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>9.5.4. Setting file attributes</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch09s05.html" title="9.5. Filling the List of Files" /><link rel="prev" href="ch09s05s03.html" title="9.5.3. Marking files as documentation or configuration files" /><link rel="next" href="ch09s05s05.html" title="9.5.5. Verifying the %files section" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch09s05s03.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n"
href="ch09s05s05.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id641334" class="title">Setting file attributes</h1></div></div></div><div class="para">
+ When your package is installed, you can control the file attributes as well as the files that get included into the package. This is very useful since most packages are installed by the root user and you don’t always want the root user owning the files.
+ </div><div class="para">
+ The %attr directive allows you to control the permissions for a particular file. The format is:
+ </div><div class="para">
+ %attr(mode, user, group) filename
+ </div><div class="para">
+ For example:
+ </div><div class="para">
+ %attr(0644, root, root) /etc/yp.conf
+ </div><div class="para">
+ This example sets the file permissions to 644, the user and the group to root. If you don’t need to specify a value, use a dash, -, to leave the setting as is for the file. For example:
+ </div><div class="para">
+ %attr(-, root, -) /etc/yp.conf
+ </div><div class="para">
+ Note that you can combine directives, one after another. For example:
+ </div><div class="para">
+ %config %attr(-, root, -) /etc/yp.conf
+ </div><div class="para">
+ You can also use spaces instead of commas as delimiters. For example:
+ </div><div class="para">
+ %attr(0700 root root) %dir /var/tux
+ </div><div class="para">
+ </div><div class="para">
+ In addition to using %attr to set the attributes for a file, you should use the %defattr directive to set the default attributes for all files in the package. For example:
+ </div><div class="para">
+ %files
+ </div><div class="para">
+ %defattr(-,root,root)
+ </div><div class="para">
+ /usr/X11R6/bin/xtoolwait
+ </div><div class="para">
+ /usr/X11R6/man/man1/xtoolwait.*
+ </div><div class="para">
+ Just about every spec file uses the %defattr directive as this directive eliminates a lot of work you need to do to set file attributes individually. In addition, using the %defattr directive is considered a best practice when creating packages.
+ </div><div class="para">
+ You can also mark files for a particular language. For example, from the tcsh shell package:
+ </div><div class="para">
+ %files
+ </div><div class="para">
+ %defattr(-,root,root)
+ </div><div class="para">
+ %doc FAQ Fixes NewThings complete.tcsh eight-bit.txt tcsh.html
+ </div><div class="para">
+ %{_bindir}/tcsh
+ </div><div class="para">
+ %{_bindir}/csh
+ </div><div class="para">
+ %{_mandir}/*/*
+ </div><div class="para">
+ %lang(de) %{_datadir}/locale/de/LC_MESSAGES/tcsh*
+ </div><div class="para">
+ %lang(el) %{_datadir}/locale/el/LC_MESSAGES/tcsh*
+ </div><div class="para">
+ %lang(en) %{_datadir}/locale/en/LC_MESSAGES/tcsh*
+ </div><div class="para">
+ %lang(es) %{_datadir}/locale/es/LC_MESSAGES/tcsh*
+ </div><div class="para">
+ %lang(et) %{_datadir}/locale/et/LC_MESSAGES/tcsh*
+ </div><div class="para">
+ %lang(fi) %{_datadir}/locale/fi/LC_MESSAGES/tcsh*
+ </div><div class="para">
+ %lang(fr) %{_datadir}/locale/fr/LC_MESSAGES/tcsh*
+ </div><div class="para">
+ %lang(it) %{_datadir}/locale/it/LC_MESSAGES/tcsh*
+ </div><div class="para">
+ %lang(ja) %{_datadir}/locale/ja/LC_MESSAGES/tcsh*
+ </div><div class="para">
+ %lang(pl) %{_datadir}/locale/pl/LC_MESSAGES/tcsh*
+ </div><div class="para">
+ %lang(ru) %{_datadir}/locale/ru/LC_MESSAGES/tcsh*
+ </div><div class="para">
+ %lang(uk) %{_datadir}/locale/uk/LC_MESSAGES/tcsh*
+ </div><div class="para">
+ This example marks certain files as only being of use with particular languages, such as ja for the Japanese text and fr for the French text.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch09s05s03.html"><strong>Înapoi</strong>9.5.3. Marking files as documentation or configur...</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch09s05s05.html"><strong>Înainte</strong>9.5.5. Verifying the %files section</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch09s05s05.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch09s05s05.html
new file mode 100644
index 0000000..feec210
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch09s05s05.html
@@ -0,0 +1,130 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>9.5.5. Verifying the %files section</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch09s05.html" title="9.5. Filling the List of Files" /><link rel="prev" href="ch09s05s04.html" title="9.5.4. Setting file attributes" /><link rel="next" href="ch09s05s06.html" title="9.5.6. Filling the list of files automatically" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch09s05s04.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch09s05s06.ht
ml"><strong>ÃŽnainte</strong></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id808054" class="title">Verifying the %files section</h1></div></div></div><div class="para">
+ You can use the %verify directive to control which tests RPM uses when verifying a package.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ See <a class="xref" href="ch-using-rpm-db.html">Cap. 4, <em>Using the RPM Database</em></a> for more on package verification.
+ </div><div class="para">
+ The %verify directive names the tests to include or not include. Table 10-4 lists the tests.
+ </div><div class="para">
+ Table 10-4 Package verification tests
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Test
+ </div>
+
+ </td><td>
+ <div class="para">
+ Usage
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ group
+ </div>
+
+ </td><td>
+ <div class="para">
+ Verifies the group of the file
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ maj
+ </div>
+
+ </td><td>
+ <div class="para">
+ Verifies the file’s major device number
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ md5
+ </div>
+
+ </td><td>
+ <div class="para">
+ Verifies the file’s MD5 checksum
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ min
+ </div>
+
+ </td><td>
+ <div class="para">
+ Verifies the file’s minor device number
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ mode
+ </div>
+
+ </td><td>
+ <div class="para">
+ Verifies the file mode, or permissions
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ mtime
+ </div>
+
+ </td><td>
+ <div class="para">
+ Verifies the file’s last modification time
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ owner
+ </div>
+
+ </td><td>
+ <div class="para">
+ Verifies the owner of the file
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ size
+ </div>
+
+ </td><td>
+ <div class="para">
+ Verifies the file’s size
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ symlink
+ </div>
+
+ </td><td>
+ <div class="para">
+ Verifies a symbolic link
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ With the %verify directive, you can name test, such as shown following:
+ </div><div class="para">
+ %verify(owner group size) /etc/yp.conf
+ </div><div class="para">
+ This example limits the tests to owner, group, and size. (The default is to perform all the tests.) You can also use the word not to specify that RPM should not run one or more tests. For example:
+ </div><div class="para">
+ %verify(not owner) /etc/yp.conf
+ </div><div class="para">
+ This example turns off just the owner test.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch09s05s04.html"><strong>Înapoi</strong>9.5.4. Setting file attributes</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch09s05s06.html"><strong>Înainte</strong>9.5.6. Filling the list of files automatically</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch09s05s06.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch09s05s06.html
new file mode 100644
index 0000000..a7fc6eb
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch09s05s06.html
@@ -0,0 +1,28 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>9.5.6. Filling the list of files automatically</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch09s05.html" title="9.5. Filling the List of Files" /><link rel="prev" href="ch09s05s05.html" title="9.5.5. Verifying the %files section" /><link rel="next" href="ch09s05s07.html" title="9.5.7. Handling RPM build errors for unpackaged files" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch09s05s05.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="c
h09s05s07.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id531945" class="title">Filling the list of files automatically</h1></div></div></div><div class="para">
+ The -f option to the %files section allows you to read in a list of file names from a file. This file is assumed to look like the contents of the %files section, holding one file name per line. You can also include the various directives for files such as %attr or %doc. For example:
+ </div><div class="para">
+ %files -f list_of_filenames.txt
+ </div><div class="para">
+ You can combine this list with filename entries, such as the following:
+ </div><div class="para">
+ %files -f xconfig_files.txt
+ </div><div class="para">
+ %defattr(-,root,root)
+ </div><div class="para">
+ /usr/X11R6/bin/xtoolwait
+ </div><div class="para">
+ /usr/X11R6/man/man1/xtoolwait.1
+ </div><div class="para">
+ This example reads in a list of file names from the file named xconfig_files.txt and also includes two additional files.
+ </div><div class="para">
+ This list of files works best if you cannot determine the file names in advance. The build may create different files based on various macro values. In addition, you may not know the final paths for the files until build time.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch09s05s05.html"><strong>Înapoi</strong>9.5.5. Verifying the %files section</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch09s05s07.html"><strong>Înainte</strong>9.5.7. Handling RPM build errors for unpackaged f...</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch09s05s07.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch09s05s07.html
new file mode 100644
index 0000000..e1b1fea
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch09s05s07.html
@@ -0,0 +1,28 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>9.5.7. Handling RPM build errors for unpackaged files</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch09s05.html" title="9.5. Filling the List of Files" /><link rel="prev" href="ch09s05s06.html" title="9.5.6. Filling the list of files automatically" /><link rel="next" href="ch09s06.html" title="9.6. Adding Change Log Entries" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch09s05s06.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch09s06.html"><s
trong>ÃŽnainte</strong></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id708744" class="title">Handling RPM build errors for unpackaged files</h1></div></div></div><div class="para">
+ Starting with RPM 4.1, rpmbuild will exit if all files in the $RPM_BUILD_ROOT directory are not found in the %files section (or in a file that lists file names used with the -f option). This is officially known as a Fascist build policy and you can turn it off with the following macros.
+ </div><div class="para">
+ The %_unpackaged_files_terminate_build macro, if set to 1, tells rpmbuild to exit if it finds files that are in the $RPM_BUILD_ROOT directory but not listed as part of the package. Set this macro to 0 to turn off the Fascist build policy. For example:
+ </div><div class="para">
+ %define _unpackaged_files_terminate_build 0
+ </div><div class="para">
+ You can also control the flag that specifies whether missing documentation files cause rpmbuild to exit. Set the %_missing_doc_files_terminate_build macro to 0 to turn off this feature:
+ </div><div class="para">
+ %define _missing_doc_files_terminate_build 0
+ </div><div class="para">
+ See the "Defining Spec File Macros" section later in the chapter for more on using macros.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ You can also store this setting in a macro file so that it applies for all packages you build. See <a class="xref" href="ch-customizing-rpm.html">Cap. 20, <em>Customizing RPM Behavior</em></a> for more on macro files.
+ </div><div class="para">
+ While the Fascist build policy may be an annoyance, it can prove very useful. Chances are your spec file has an error if you have files in the $RPM_BUILD_ROOT directory that are not listed in the %files section. The Fascist build policy helps catch these errors. In addition, since the error outputs a list of files in the $RPM_BUILD_ROOT directory that are not listed in the %files section, you can often paste this list into your %files section.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch09s05s06.html"><strong>Înapoi</strong>9.5.6. Filling the list of files automatically</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch09s06.html"><strong>Înainte</strong>9.6. Adding Change Log Entries</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch09s06.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch09s06.html
new file mode 100644
index 0000000..08903f2
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch09s06.html
@@ -0,0 +1,23 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>9.6. Adding Change Log Entries</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-specfiles.html" title="Cap. 9. Working with Spec Files" /><link rel="prev" href="ch09s05s07.html" title="9.5.7. Handling RPM build errors for unpackaged files" /><link rel="next" href="ch09s07.html" title="9.7. Defining Spec File Macros" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch09s05s07.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch0
9s07.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id708801" class="title">Adding Change Log Entries</h1></div></div></div><div class="para">
+ The change log usually appears at the end of a spec file and is marked with %changelog. It holds messages for each significant change. You should add a change log entry for each major change to the application. For example, if you download a new version of the software you are packaging, add a change log entry for the new version:
+ </div><div class="para">
+ %changelog
+ </div><div class="para">
+ * Fri Jun 21 2002 Bob Marley <marley at reggae.com>
+ </div><div class="para">
+ - Downloaded version 1.4, applied patches
+ </div><div class="para">
+ </div><div class="para">
+ * Tue May 08 2001 Peter Tosh <tosh at reggae.com> 1.3-1
+ </div><div class="para">
+ - updated to 1.3
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch09s05s07.html"><strong>Înapoi</strong>9.5.7. Handling RPM build errors for unpackaged f...</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch09s07.html"><strong>Înainte</strong>9.7. Defining Spec File Macros</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch09s07.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch09s07.html
new file mode 100644
index 0000000..eb8a1f5
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch09s07.html
@@ -0,0 +1,61 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>9.7. Defining Spec File Macros</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-specfiles.html" title="Cap. 9. Working with Spec Files" /><link rel="prev" href="ch09s06.html" title="9.6. Adding Change Log Entries" /><link rel="next" href="ch09s07s02.html" title="9.7.2. Spec file-specific macros" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch09s06.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch09s07s02.html"><strong>ÃŽ
nainte</strong></a></li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id724172" class="title">Defining Spec File Macros</h1></div></div></div><div class="para">
+ The RPM system defines a lot of handy macros so that your spec files can work regardless of where system directories are located. You simply use the macro, such as %_bindir, in place of hard-coded paths. The %_bindir macro, for example, identifies the default directory for binary executables, /usr/bin.
+ </div><div class="para">
+ Use these macros wherever possible to avoid hard-coded paths and settings.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id724189" class="title">Built-in macros</h1></div></div></div><div class="para">
+ RPM includes a host of built-in macros, including the following useful directories:
+ </div><div class="para">
+ %_prefix /usr
+ </div><div class="para">
+ %_exec_prefix %{_prefix}
+ </div><div class="para">
+ %_bindir %{_exec_prefix}/bin
+ </div><div class="para">
+ %_sbindir %{_exec_prefix}/sbin
+ </div><div class="para">
+ %_libexecdir %{_exec_prefix}/libexec
+ </div><div class="para">
+ %_datadir %{_prefix}/share
+ </div><div class="para">
+ %_sysconfdir %{_prefix}/etc
+ </div><div class="para">
+ %_sharedstatedir %{_prefix}/com
+ </div><div class="para">
+ %_localstatedir %{_prefix}/var
+ </div><div class="para">
+ %_libdir %{_exec_prefix}/lib
+ </div><div class="para">
+ %_includedir %{_prefix}/include
+ </div><div class="para">
+ %_oldincludedir /usr/include
+ </div><div class="para">
+ %_infodir %{_prefix}/info
+ </div><div class="para">
+ %_mandir %{_prefix}/man
+ </div><div class="para">
+ The example directories shown above come from the standard RPM macro file, /usr/lib/rpm/macros, instead of the Red Hat-specific file, /usr/lib/rpm/redhat/macros, which holds:
+ </div><div class="para">
+ </div><div class="para">
+ %_prefix /usr
+ </div><div class="para">
+ %_sysconfdir /etc
+ </div><div class="para">
+ %_localstatedir /var
+ </div><div class="para">
+ %_infodir /usr/share/info
+ </div><div class="para">
+ %_mandir /usr/share/man
+ </div><div class="para">
+ %_initrddir %{_sysconfdir}/rc.d/init.d
+ </div><div class="para">
+ %_defaultdocdir %{_usr}/share/doc
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch09s06.html"><strong>Înapoi</strong>9.6. Adding Change Log Entries</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch09s07s02.html"><strong>Înainte</strong>9.7.2. Spec file-specific macros</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch09s07s02.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch09s07s02.html
new file mode 100644
index 0000000..1ed3935
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch09s07s02.html
@@ -0,0 +1,148 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>9.7.2. Spec file-specific macros</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch09s07.html" title="9.7. Defining Spec File Macros" /><link rel="prev" href="ch09s07.html" title="9.7. Defining Spec File Macros" /><link rel="next" href="ch09s07s03.html" title="9.7.3. Defining new macros" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch09s07.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch09s07s03.html"><strong>ÃŽnainte</stro
ng></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id715864" class="title">Spec file-specific macros</h1></div></div></div><div class="para">
+ Most of the pre-defined RPM macros hold directory paths or architecture information. RPM also includes a set of useful macros that you can use to help debug problematic spec files and well as perform common tasks in spec files. Table 10-5 lists these debugging and special spec file macros.
+ </div><div class="para">
+ Table 10-5 Special spec-file macros
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Macro
+ </div>
+
+ </td><td>
+ <div class="para">
+ Usage
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ %dump
+ </div>
+
+ </td><td>
+ <div class="para">
+ Prints out macro values
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ %{echo:message}
+ </div>
+
+ </td><td>
+ <div class="para">
+ Prints message to stderr
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ %{error:message}
+ </div>
+
+ </td><td>
+ <div class="para">
+ Prints message to stderr and returns BADSPEC
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ %{expand:expression}
+ </div>
+
+ </td><td>
+ <div class="para">
+ Like eval, expands expression
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ %{F:file_exp}
+ </div>
+
+ </td><td>
+ <div class="para">
+ Expands file_exp to a file name
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ %global name value
+ </div>
+
+ </td><td>
+ <div class="para">
+ Defines a global macro
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ %{P:patch_exp}
+ </div>
+
+ </td><td>
+ <div class="para">
+ Expands patch_exp to a patch file name
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ %{S:source_exp}
+ </div>
+
+ </td><td>
+ <div class="para">
+ Expands source_exp to a source file name
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ %trace
+ </div>
+
+ </td><td>
+ <div class="para">
+ Toggles the printing of debugging information
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ %{uncompress:filename}
+ </div>
+
+ </td><td>
+ <div class="para">
+ Tests if file filename is compressed. If so, uncompresses and includes in the given context. If not compressed, calls cat to include file in given context.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ %undefine macro
+ </div>
+
+ </td><td>
+ <div class="para">
+ Undefines the given macro
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ %{warn:message}
+ </div>
+
+ </td><td>
+ <div class="para">
+ Prints message to stderr
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ Note
+ </div><div class="para">
+ To see the current list of macros, put a %dump at the start of your spec file.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch09s07.html"><strong>Înapoi</strong>9.7. Defining Spec File Macros</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch09s07s03.html"><strong>Înainte</strong>9.7.3. Defining new macros</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch09s07s03.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch09s07s03.html
new file mode 100644
index 0000000..3abd935
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch09s07s03.html
@@ -0,0 +1,30 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>9.7.3. Defining new macros</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch09s07.html" title="9.7. Defining Spec File Macros" /><link rel="prev" href="ch09s07s02.html" title="9.7.2. Spec file-specific macros" /><link rel="next" href="ch09s07s04.html" title="9.7.4. Specifying parameters to macros" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch09s07s02.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch09s07s04.html"><s
trong>ÃŽnainte</strong></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id605765" class="title">Defining new macros</h1></div></div></div><div class="para">
+ In addition to the built-in macros, you can define your own to make it easier to manage your packages. Define a new spec file macro with the following syntax:
+ </div><div class="para">
+ %define macro_name value
+ </div><div class="para">
+ For example:
+ </div><div class="para">
+ %define major 2
+ </div><div class="para">
+ %define minor 2
+ </div><div class="para">
+ %define patchlevel 7
+ </div><div class="para">
+ You can then use a macro with the %macro_name or %{macro_name} syntax. For example:
+ </div><div class="para">
+ Version: %{major}.%{minor}.%{patchlevel}
+ </div><div class="para">
+ You can also expand the results of running shell commands using a %(command) syntax with parenthesis instead of curly braces. For example:
+ </div><div class="para">
+ %define today %(date)
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch09s07s02.html"><strong>Înapoi</strong>9.7.2. Spec file-specific macros</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch09s07s04.html"><strong>Înainte</strong>9.7.4. Specifying parameters to macros</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch09s07s04.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch09s07s04.html
new file mode 100644
index 0000000..31694b6
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch09s07s04.html
@@ -0,0 +1,140 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>9.7.4. Specifying parameters to macros</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch09s07.html" title="9.7. Defining Spec File Macros" /><link rel="prev" href="ch09s07s03.html" title="9.7.3. Defining new macros" /><link rel="next" href="ch09s08.html" title="9.8. Creating XML Spec Files" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch09s07s03.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch09s08.html"><strong>ÃŽnainte</strong
></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id715604" class="title">Specifying parameters to macros</h1></div></div></div><div class="para">
+ Most macros perform simple text substitution. You can also pass parameters to macros, and access those parameters within your macros, similarly to how shell scripts get command-line parameters.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ <a class="xref" href="ch-scripting.html">Cap. 14, <em>Automating RPM with Scripts</em></a> covers shell scripting with RPM.
+ </div><div class="para">
+ With parameters, you can expand the normal definition of a macro to the following:
+ </div><div class="para">
+ %define macro_name(options) value
+ </div><div class="para">
+ Any text within the parenthesis is passed to getopt(3), and acts as parameters to the macro. This is performed when the macro is expanded. You can also pass options to the macro using the %macro_name syntax (without curly braces). For example:
+ </div><div class="para">
+ %foo 1 2 3
+ </div><div class="para">
+ This example passes the parameters 1, 2, and 3 to the macro foo. Inside the macro, you can use a shell script-like syntax to access the parameters through special macros. Table 10-6 lists these macros.
+ </div><div class="para">
+ Table 10-6 Parameter macros inside a macro expansion
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Macro
+ </div>
+
+ </td><td>
+ <div class="para">
+ Holds
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ %0
+ </div>
+
+ </td><td>
+ <div class="para">
+ The name of the macro
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ %*
+ </div>
+
+ </td><td>
+ <div class="para">
+ All the parameters to the macro, except for any processed options
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ %#
+ </div>
+
+ </td><td>
+ <div class="para">
+ The number of parameters
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ %1
+ </div>
+
+ </td><td>
+ <div class="para">
+ The first parameter
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ %2
+ </div>
+
+ </td><td>
+ <div class="para">
+ The second parameter
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ %3
+ </div>
+
+ </td><td>
+ <div class="para">
+ The third parameter, and so on with %4, %5 and beyond
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ %{-p}
+ </div>
+
+ </td><td>
+ <div class="para">
+ Holds -p if the -p parameter was passed to the macro; otherwise holds nothing
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ %{-p*}
+ </div>
+
+ </td><td>
+ <div class="para">
+ Holds the value passed with the -p parameter, if the -p parameter was passed to the macro; otherwise holds nothing
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ %{-p:text}
+ </div>
+
+ </td><td>
+ <div class="para">
+ Holds text if the -p parameter was passed to the macro; otherwise holds nothing
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ Note that all parameters listed in Table 10-6 hold the remaining parameters after getopt(3) processing. You can use these macros within the definition of your own macros. You can also nest macros, such as the following:
+ </div><div class="para">
+ %define mypatch() patch %{-p:-p%{-p*}}
+ </div><div class="para">
+ This macro expands to the patch command if no -p parameter was passed. If you pass a -p parameter, such as -p 1, then the macro expands to -p with the value of the -p parameter:
+ </div><div class="para">
+ patch -p1
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ This type of syntax is used heavily with the patch command.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch09s07s03.html"><strong>Înapoi</strong>9.7.3. Defining new macros</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch09s08.html"><strong>Înainte</strong>9.8. Creating XML Spec Files</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch09s08.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch09s08.html
new file mode 100644
index 0000000..e14c627
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch09s08.html
@@ -0,0 +1,132 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>9.8. Creating XML Spec Files</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-specfiles.html" title="Cap. 9. Working with Spec Files" /><link rel="prev" href="ch09s07s04.html" title="9.7.4. Specifying parameters to macros" /><link rel="next" href="ch09s09.html" title="9.9. Summary" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch09s07s04.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch09s09.html"><strong>ÃŽnainte</stro
ng></a></li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id528553" class="title">Creating XML Spec Files</h1></div></div></div><div class="para">
+ RPM spec files are text files containing structured information. It is a natural progression to write RPM spec files using XML. The tool rpmxmlbuild will build an RPM package from an XML-formatted spec file.
+ </div><div class="para">
+ For example, Listing 10-1 holds a spec file in XML format.
+ </div><div class="para">
+ Listing 10-1: An XML spec file.
+ </div><div class="para">
+ <?xml version="1.0"?>
+ </div><div class="para">
+ <spec distribution="RPM Test" vendor="rpm.org"
+ </div><div class="para">
+ name="bash" version="2.05a" release="02test"
+ </div><div class="para">
+ copyright="GPL"
+ </div><div class="para">
+ url="http://www.gnu.org/software/bash/bash.html">
+ </div><div class="para">
+ </div><div class="para">
+ <source name="%{name}-%{version}.tar.bz2"
+ </div><div class="para">
+ size="1434025" md5="c29b50db808003e39558a0f6354f4cad"
+ </div><div class="para">
+ path="%{name}-%{version}">
+ </div><div class="para">
+ </source>
+ </div><div class="para">
+ </div><div class="para">
+ <buildrequires>
+ </div><div class="para">
+ <require name="bash" />
+ </div><div class="para">
+ <require name="gcc" />
+ </div><div class="para">
+ <require name="make" />
+ </div><div class="para">
+ </buildrequires>
+ </div><div class="para">
+ </div><div class="para">
+ <!-- packages -->
+ </div><div class="para">
+ <package group="System/Base" autoreqprov="no">
+ </div><div class="para">
+ <requires>
+ </div><div class="para">
+ <require name="glibc" />
+ </div><div class="para">
+ </requires>
+ </div><div class="para">
+ <summary>The Bash package contains the bash program.</summary>
+ </div><div class="para">
+ <description>%{summary}
+ </div><div class="para">
+ Bash is the Bourne-Again SHell, which is a widely used command interpreter
+ </div><div class="para">
+ on Unix systems. Bash is a program that reads from standard input, the
+ </div><div class="para">
+ keyboard. A user types something and the program will evaluate what he has
+ </div><div class="para">
+ typed and do something with it, like running a program.</description>
+ </div><div class="para">
+ <files list="%{name}.files.lst" />
+ </div><div class="para">
+ </package>
+ </div><div class="para">
+ </div><div class="para">
+ <package name="bash-doc" group="Documentation/System/Base" autoreqprov="no">
+ </div><div class="para">
+ <requires>
+ </div><div class="para">
+ <require name="%{name}" />
+ </div><div class="para">
+ </requires>
+ </div><div class="para">
+ <summary>Documentation for the bash package.</summary>
+ </div><div class="para">
+ <description>%{summary}</description>
+ </div><div class="para">
+ <pre script="%{name}-doc.pre.sh" />
+ </div><div class="para">
+ <files list="%{name}-doc.files.lst" />
+ </div><div class="para">
+ </package>
+ </div><div class="para">
+ </div><div class="para">
+ <!-- scripts to create the package -->
+ </div><div class="para">
+ <prep script="%{name}.prep.sh">
+ </div><div class="para">
+ <setup />
+ </div><div class="para">
+ <script>echo &quot;Prep completed&quot;</script>
+ </div><div class="para">
+ </prep>
+ </div><div class="para">
+ <build script="%{name}.build.sh" />
+ </div><div class="para">
+ <install script="%{name}.install.sh" />
+ </div><div class="para">
+ <clean script="%{name}.clean.sh" />
+ </div><div class="para">
+ </div><div class="para">
+ <!-- changelog -->
+ </div><div class="para">
+ <changelog>
+ </div><div class="para">
+ <changes date="Mon Aug 26 2002" version="2.05a-02test"
+ </div><div class="para">
+ author="" author-email="">
+ </div><div class="para">
+ <change>Added setup macro to extract files</change>
+ </div><div class="para">
+ <change>Initial version ready for jbj</change>
+ </div><div class="para">
+ </changes>
+ </div><div class="para">
+ </changelog>
+ </div><div class="para">
+ </spec>
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ XML spec files are a very experimental feature. Future releases of RPM will likely provide more support for XML spec files. The format will likely change.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch09s07s04.html"><strong>Înapoi</strong>9.7.4. Specifying parameters to macros</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch09s09.html"><strong>Înainte</strong>9.9. Summary</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch09s09.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch09s09.html
new file mode 100644
index 0000000..930fe19
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch09s09.html
@@ -0,0 +1,24 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>9.9. Summary</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-specfiles.html" title="Cap. 9. Working with Spec Files" /><link rel="prev" href="ch09s08.html" title="9.8. Creating XML Spec Files" /><link rel="next" href="ch-advanced-packaging.html" title="Cap. 10. Creare avansată pachete RPM" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch09s08.html"><strong>Înapoi</strong></a></li><li class="next"><a accesskey="n" href="ch-advanced-p
ackaging.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id600275" class="title">Summary</h1></div></div></div><div class="para">
+ This chapter covers spec files, the files that define how to build packages. Start your spec file by defining package information, such as the name, version, and release number. You can also add a detailed description to help administrators decide whether to install your packages.
+ </div><div class="para">
+ You need to name all of the source and patch files used to build the package. In most cases, the source files are compressed tar archives. After naming all the sources and patches, you need to control how the rpmbuild command should build your package. This comes in four sections.
+ </div><div class="para">
+ The %prep section prepares for the build by extracting the source files and applying patches. The %build section defines the commands to build the software, normally something as simple as running a configure script and then the make command. The %install section contains the commands for installing the software. And, the %clean section provides commands to clean up after the build.
+ </div><div class="para">
+ For these sections, you can use handy RPM macros for common tasks, such as running the configure script or the make install command. You can also define scripts the rpm command should run before and after installing, as well as before and after removing the package.
+ </div><div class="para">
+ Spec files contain a listing of all the files that should go into the package, as well as where those files should be placed on the user’s hard disk.
+ </div><div class="para">
+ You can define RPM macros in your spec files to make commands that can work with different directory structures as well as simplify common commands.
+ </div><div class="para">
+ While it may seem that this chapter described a great many options for making spec files, there’s more to come. The next chapter covers advanced spec file topics such as triggers, conditional builds, and specifying dependencies.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch09s08.html"><strong>Înapoi</strong>9.8. Creating XML Spec Files</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch-advanced-packaging.html"><strong>Înainte</strong>Cap. 10. Creare avansată pachete RPM</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch10s02.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch10s02.html
new file mode 100644
index 0000000..7726be6
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch10s02.html
@@ -0,0 +1,259 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>10.2. Setarea triggerelor</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-advanced-packaging.html" title="Cap. 10. Creare avansată pachete RPM" /><link rel="prev" href="ch-advanced-packaging.html" title="Cap. 10. Creare avansată pachete RPM" /><link rel="next" href="ch10s03.html" title="10.3. Scrierea scripturilor de verificare" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-advanced-packaging.html"><strong>Înapoi</strong></a></li><li class="
next"><a accesskey="n" href="ch10s03.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id618901" class="title">Setarea triggerelor</h1></div></div></div><div class="para">
+ Triggerele oferă posibilități unui pachet de a acționa când statusul de instalare al altui pachet se schimbă. Un trigger este un script pe care îl definiți în fișierul spec al pachetului dvs. care este rulat de sistemulRPM când statusul unui anume pachet se schimbă. Dacă pachetul dvs. depindeîntr-un anume fel de alt pachet, un trigger poate permite pachetului dvs. săse ocupe de schimbările din celălalt pachet
+ </div><div class="para">
+ Triggerele nu sunt un înlocuitor pentru dependențele pachetelor. În schimb,triggerele sunt folositoare când doriți să schimbați instalarea unui pachetîn funcție de alte pachete instalate. De exemplu, dacă pachetul dvs. este unclient de mail, pachetul dvs. va avea nevoie de un agent de transfer mail, sauMTA. Linux suportă mai mulți agenți de transfer mail, cum ar fi sendmail, vmailexim, qmail și postfix
+ </div><div class="para">
+ În mod uzual un sistem va avea un agent de transfer mail instalat. În cele mai multe cazuri, pentru un client de mail nu va conta ce MTA este instalat,atâta timp cât există. (De fapt, mare parte din aceste pachete ar trebui marcate ca fiind în conflict, asigurându-ne astfel că un sistem dat poateavea doar unul.)
+ </div><div class="para">
+ Scriptul %triggerin este rulat când un anume pachet-țintă este instalat sau actualizat. Scriptul %triggerin este de asemenea rulat când pachetul dvs esteinstalat sau actualizat, cu condiția ca pachetul-țintă să fie deja instalat.La fel, scriptul %triggerun este rulat dacă pachetul-țintă este dezinstalat.Este de asemenea rulat dacă pachetul dvs. este dezinstalat și pachetul-țintăeste instalat. Scriptul %triggerpostun este rulat după ce pachetul-țintă a fostdezinstalat. Nu este rulat dacă pachetul dvs. este dezinstalat.
+ </div><div class="para">
+ Pentru a defini unul dintre aceste scripturi, este necesar să specificaținumele pachetului-țintă; de exemplu:
+ </div><div class="para">
+ %triggerin -- tcsh
+ </div><div class="para">
+ comenzi script...
+ </div><div class="para">
+ Acest exemplu setează un trigger pentru pachetul tcsh. Dacă pachetul tcsh este instalat sau actualizat, RPM va rula scriptul. Dacă pachetul dvs. este instalat sau actualizat și pachetul tcsh este instalat, RPM de asemenea va rula scriptul.
+ </div><div class="para">
+ Definiți scriptul %triggerun în mod similar:
+ </div><div class="para">
+ triggerun -- tcsh
+ </div><div class="para">
+ comenzi script...
+ </div><div class="para">
+ Puteți folosi de asemenea numere de versiune în definiția scriptului triggerpentru a rula scriptul doar în cazul unei anumite versiuni. De exemplu:
+ </div><div class="para">
+ %triggerpostun -- vixie-cron < 3.0.1-56
+ </div><div class="para">
+ /sbin/chkconfig --del crond
+ </div><div class="para">
+ /sbin/chkconfig --add crond
+ </div><div class="para">
+ Acest exemplu, din pachetul de planificare vixie-cron, rulează un triggerpost-uninstall (postdezinstalare) pentru același pachet, dar pentru versiunimai vechi. Pentru a defini scripturi trigger pentru versiuni specifice, folosiți aceeași sintaxă ca pentru dependențele requires la stabilirea versiunii și a comparațiilor.
+ </div><div class="para">
+ Triggerele sunt rulate prin /bin/sh, cel mai folosit motor de shell scripting. Folosind opțiunea -p totuși, puteți specifica un alt interpretor de scripting. De exemplu, pentru a scrie un script Perl, definiți triggerulca mai jos:
+ </div><div class="para">
+ %triggerpostun -p /usr/bin/perl -- vixie-cron < 3.0.1-56
+ </div><div class="para">
+ system("/sbin/chkconfig --del crond");
+ </div><div class="para">
+ system("/sbin/chkconfig --add crond");
+ </div><div class="para">
+ Prin subpachete, definite în cele ce urmează, puteți folosi o opțiune -npentru a lega scriptul trigger de un subpachet. De exemplu:
+ </div><div class="para">
+ %triggerpostun -n subpackage_name -- vixie-cron < 3.0.1-56
+ </div><div class="para">
+ /sbin/chkconfig --del crond
+ </div><div class="para">
+ /sbin/chkconfig --add crond
+ </div><div class="para">
+ În scripturile dvs trigger, $1, primul argument al liniei de comanda, conține numărul de instanțe ale pachetului dvs. care vor rămâne după completarea operațiunii.Al doilea argument, $2, conține numărul de instanțe ale pachetului-țintă care vor rămâne după operațiune. Astfel, dacă $2 e 0, pachetul-țintă va fi dezinstalat.
+ </div><div class="para">
+ Pachetul anonftp, menționat în <a class="xref" href="ch-dependencies.html">Cap. 5, <em>Package Dependencies</em></a>, are multe triggere. Multe dintre ele fac disponibile mai multe comenzi pentru pachetul anonftp. Acest pachet de rețea este de asemenea legat strâns de versiunea bibliotecii de C, glibc, după cum se vede în lista 11-1
+ </div><div class="para">
+ Lista 11-1: Scripturile trigger ale pachetului anonftp.
+ </div><div class="para">
+ triggerin -- glibc
+ </div><div class="para">
+ copy() { file="`ls --sort=time $1 |head -n 1`"; ln -f "$file" "$2" 2>/dev/null |
+ </div><div class="para">
+ | cp -df "$file" "$2"; }
+ </div><div class="para">
+ # Terminare versiuni mai vechi
+ </div><div class="para">
+ rm -f /var/ftp/lib/ld-* /var/ftp/lib/libc* /var/ftp/lib/libnsl* /var/ftp/lib/lib
+ </div><div class="para">
+ nss_files* &>/dev/null || :
+ </div><div class="para">
+ # Părți copie din glibc, de care este nevoie în bin.
+ </div><div class="para">
+ LIBCVER=`basename $(ls --sort=time /lib/libc-*.so |head -n 1) .so |cut -f2- -d-`
+ </div><div class="para">
+ copiere /lib/ld-${LIBCVER}.so /var/ftp/lib
+ </div><div class="para">
+ copiere /lib/libc-${LIBCVER}.so /var/ftp/lib
+ </div><div class="para">
+ copiere /lib/libnsl-${LIBCVER}.so /var/ftp/lib
+ </div><div class="para">
+ copiere /lib/libnss_files-${LIBCVER}.so /var/ftp/lib
+ </div><div class="para">
+ md5sum /var/ftp/lib/lib*-*.so /var/ftp/lib/libtermcap.so.*.*.* 2>/dev/null >/var
+ </div><div class="para">
+ /ftp/lib/libs.md5
+ </div><div class="para">
+ chmod 0400 /var/ftp/lib/libs.md5
+ </div><div class="para">
+ # Folosiți ldconfig pentru a construi legături simbolice și așa mai departe.
+ </div><div class="para">
+ [ ! -e /var/ftp/etc/ld.so.conf ] && touch /var/ftp/etc/ld.so.conf
+ </div><div class="para">
+ /sbin/ldconfig -r /var/ftp
+ </div><div class="para">
+ </div><div class="para">
+ %triggerin -- fileutils
+ </div><div class="para">
+ copy() { file="`ls --sort=time $1 |head -n 1`"; ln -f "$file" "$2" 2>/dev/null |
+ </div><div class="para">
+ | cp -df "$file" "$2"; }
+ </div><div class="para">
+ copiere /bin/ls /var/ftp/bin
+ </div><div class="para">
+ md5sum `ls /var/ftp/bin/* |grep -v bin.md5` >/var/ftp/bin/bin.md5
+ </div><div class="para">
+ chmod 0400 /var/ftp/bin/bin.md5
+ </div><div class="para">
+ </div><div class="para">
+ %triggerin -- cpio
+ </div><div class="para">
+ copy() { file="`ls --sort=time $1 |head -n 1`"; ln -f "$file" "$2" 2>/dev/null |
+ </div><div class="para">
+ | cp -df "$file" "$2"; }
+ </div><div class="para">
+ copiere /bin/cpio /var/ftp/bin
+ </div><div class="para">
+ md5sum `ls /var/ftp/bin/* |grep -v bin.md5` >/var/ftp/bin/bin.md5
+ </div><div class="para">
+ chmod 0400 /var/ftp/bin/bin.md5
+ </div><div class="para">
+ </div><div class="para">
+ %triggerin -- tar
+ </div><div class="para">
+ copy() { file="`ls --sort=time $1 |head -n 1`"; ln -f "$file" "$2" 2>/dev/null |
+ </div><div class="para">
+ | cp -df "$file" "$2"; }
+ </div><div class="para">
+ copiere /bin/tar /var/ftp/bin
+ </div><div class="para">
+ md5sum `ls /var/ftp/bin/* |grep -v bin.md5` >/var/ftp/bin/bin.md5
+ </div><div class="para">
+ chmod 0400 /var/ftp/bin/bin.md5
+ </div><div class="para">
+ </div><div class="para">
+ %triggerin -- gzip
+ </div><div class="para">
+ copy() { file="`ls --sort=time $1 |head -n 1`"; ln -f "$file" "$2" 2>/dev/null |
+ </div><div class="para">
+ | cp -df "$file" "$2"; }
+ </div><div class="para">
+ copiere /bin/gzip /var/ftp/bin
+ </div><div class="para">
+ ln -sf gzip /var/ftp/bin/zcat
+ </div><div class="para">
+ md5sum `ls /var/ftp/bin/* |grep -v bin.md5` >/var/ftp/bin/bin.md5
+ </div><div class="para">
+ chmod 0400 /var/ftp/bin/bin.md5
+ </div><div class="para">
+ </div><div class="para">
+ %triggerin -- libtermcap
+ </div><div class="para">
+ copy() { file="`ls --sort=time $1 |head -n 1`"; ln -f "$file" "$2" 2>/dev/null |
+ </div><div class="para">
+ | cp -df "$file" "$2"; }
+ </div><div class="para">
+ rm -f /var/ftp/lib/libtermcap.so.*.*.* &>/dev/null || :
+ </div><div class="para">
+ copiere '/lib/libtermcap.so.*.*.*' /var/ftp/lib
+ </div><div class="para">
+ md5sum /var/ftp/lib/lib*-*.so /var/ftp/lib/libtermcap.so.*.*.* 2>/dev/null >/var
+ </div><div class="para">
+ /ftp/lib/libs.md5
+ </div><div class="para">
+ chmod 0400 /var/ftp/lib/libs.md5
+ </div><div class="para">
+ # Folosiți ldconfig pentru a construi legături simbolice și așa mai departe.
+ </div><div class="para">
+ [ ! -e /var/ftp/etc/ld.so.conf ] && touch /var/ftp/etc/ld.so.conf
+ </div><div class="para">
+ /sbin/ldconfig -r /var/ftp
+ </div><div class="para">
+ </div><div class="para">
+ %triggerin -- ncompress
+ </div><div class="para">
+ copy() { file="`ls --sort=time $1 |head -n 1`"; ln -f "$file" "$2" 2>/dev/null |
+ </div><div class="para">
+ | cp -df "$file" "$2"; }
+ </div><div class="para">
+ copiere /usr/bin/compress /var/ftp/bin
+ </div><div class="para">
+ md5sum `ls /var/ftp/bin/* |grep -v bin.md5` >/var/ftp/bin/bin.md5
+ </div><div class="para">
+ chmod 0400 /var/ftp/bin/bin.md5
+ </div><div class="para">
+ </div><div class="para">
+ %triggerpostun -- anonftp 4.0
+ </div><div class="para">
+ if [ "$2" != 1 ] ; then
+ </div><div class="para">
+ # Utilizatorul are mai multe pachete glibc instalate. Nu putem citi
+ </div><div class="para">
+ # mintea utilizatorului, deci nu se va face nimic.
+ </div><div class="para">
+ exit 0
+ </div><div class="para">
+ fi
+ </div><div class="para">
+ copy() { file="`ls --sort=time $1 |head -n 1`"; ln -f "$file" "$2" 2>/dev/null |
+ </div><div class="para">
+ | cp -df "$file" "$2"; }
+ </div><div class="para">
+ # Terminare versiuni mai vechi
+ </div><div class="para">
+ rm -f /var/ftp/lib/ld-* /var/ftp/lib/libc* /var/ftp/lib/libnsl* /var/ftp/lib/lib
+ </div><div class="para">
+ nss_files* &>/dev/null || :
+ </div><div class="para">
+ # Părți copie din glibc, de care este nevoie în bin.
+ </div><div class="para">
+ LIBCVER=`basename /lib/libc-*.so .so | cut -f2- -d-`
+ </div><div class="para">
+ copiere /lib/ld-${LIBCVER}.so /var/ftp/lib
+ </div><div class="para">
+ copiere /lib/libc-${LIBCVER}.so /var/ftp/lib
+ </div><div class="para">
+ copiere /lib/libnsl-${LIBCVER}.so /var/ftp/lib
+ </div><div class="para">
+ copiere /lib/libnss_files-${LIBCVER}.so /var/ftp/lib
+ </div><div class="para">
+ copiere /bin/ls /var/ftp/bin
+ </div><div class="para">
+ copiere /bin/cpio /var/ftp/bin
+ </div><div class="para">
+ copiere /bin/tar /var/ftp/bin
+ </div><div class="para">
+ copiere /bin/gzip /var/ftp/bin
+ </div><div class="para">
+ ln -sf gzip /var/ftp/bin/zcat
+ </div><div class="para">
+ copiere /usr/bin/compress /var/ftp/bin
+ </div><div class="para">
+ rm -f /var/ftp/lib/libtermcap.so.*.*.* &>/dev/null || :
+ </div><div class="para">
+ copiere '/lib/libtermcap.so.*.*.*' /var/ftp/lib
+ </div><div class="para">
+ # Folosiți ldconfig pentru a construi legături simbolice și așa mai departe.
+ </div><div class="para">
+ [ ! -e /var/ftp/etc/ld.so.conf ] && touch /var/ftp/etc/ld.so.conf
+ </div><div class="para">
+ /sbin/ldconfig -r /var/ftp
+ </div><div class="para">
+ # Generare md5sum pentru verifyscript (script de verificare)
+ </div><div class="para">
+ md5sum /var/ftp/lib/lib*-*.so /var/ftp/lib/libtermcap.so.*.*.* 2>/dev/null >/var
+ </div><div class="para">
+ /ftp/lib/libs.md5
+ </div><div class="para">
+ chmod 0400 /var/ftp/lib/libs.md5
+ </div><div class="para">
+ md5sum `ls /var/ftp/bin/* |grep -v bin.md5` >/var/ftp/bin/bin.md5
+ </div><div class="para">
+ chmod 0400 /var/ftp/bin/bin.md5
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-advanced-packaging.html"><strong>Înapoi</strong>Cap. 10. Creare avansată pachete RPM</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch10s03.html"><strong>Înainte</strong>10.3. Scrierea scripturilor de verificare</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch10s03.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch10s03.html
new file mode 100644
index 0000000..e364463
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch10s03.html
@@ -0,0 +1,28 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>10.3. Scrierea scripturilor de verificare</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-advanced-packaging.html" title="Cap. 10. Creare avansată pachete RPM" /><link rel="prev" href="ch10s02.html" title="10.2. Setarea triggerelor" /><link rel="next" href="ch10s04.html" title="10.4. Crearea subpachetelor." /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch10s02.html"><strong>Înapoi</strong></a></li><li class="next"><a accesskey="n" href="ch10s04.html"><strong>Î
nainte</strong></a></li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id675453" class="title">Scrierea scripturilor de verificare</h1></div></div></div><div class="para">
+ RPM tratează automat verificarea pachetelor, controlând instalarea fișierelor corespunzătoare și testarea fișierelor pentru mărimea potrivită și alte atribute. S-ar putea să aveți nevoie de mai mult totuși pentru a vă asigura că totul este în regulă. Cu RPM, puteți:
+ </div><div class="para">
+ *Controlați testele folosite la verificarea fiecărui fișier, așa ca în<a class="xref" href="ch-specfiles.html">Cap. 9, <em>Working with Spec Files</em></a>
+ </div><div class="para">
+ *Creați un script de verificare care efectuează alte teste
+ </div><div class="para">
+ Dacă doriți să efectuați alt test pentru a verifica pachetul, ca de exemplu să verificați dacă un fișier de configurare conține o anume setare (și că acea setare este validă), puteți completa %verifyscript în fișierul spec. %verifyscript se comportă în mare parte ca și scripturile %pre sau %post, cu diferența că %verifyscript este executat în timpul verificării pachetului. Completați un %verifyscript după cum urmează:
+ </div><div class="para">
+ %verifyscript
+ </div><div class="para">
+ your script commands ....
+ </div><div class="para">
+ Acțiuni comune pentru %verifyscript ar fi verificarea unei intrări într-un fișier de configurare a sistemului, ca de exemplu un script de pornire în timpul init sau /etc/shells (care listează shellurile disponibile). Acestea sunt fișiere care aparțin altor pachete care ar putea trebui modificate corespunzător pentru ca un pachet să fie instalat cum trebuie. Dacă pachetul este într-o asemenea situație, scrieți un %verifyscript. În scriptul dvs, direcționați toate erorile spre stderr.
+ </div><div class="para">
+ Referință încrucișată
+ </div><div class="para">
+ A se vedea <a class="xref" href="ch-using-rpm-db.html">Cap. 4, <em>Using the RPM Database</em></a> pentru detalii despre verificarea pachetelor.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch10s02.html"><strong>Înapoi</strong>10.2. Setarea triggerelor</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch10s04.html"><strong>Înainte</strong>10.4. Crearea subpachetelor.</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch10s04.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch10s04.html
new file mode 100644
index 0000000..7739572
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch10s04.html
@@ -0,0 +1,110 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>10.4. Crearea subpachetelor.</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-advanced-packaging.html" title="Cap. 10. Creare avansată pachete RPM" /><link rel="prev" href="ch10s03.html" title="10.3. Scrierea scripturilor de verificare" /><link rel="next" href="ch10s04s02.html" title="10.4.2. Definirea scripturilor pentru subpachete" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch10s03.html"><strong>Înapoi</strong></a></li><li class="next"><a acces
skey="n" href="ch10s04s02.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id561520" class="title">Crearea subpachetelor.</h1></div></div></div><div class="para">
+ Un fișier spec poate defini mai multe pachete. Aceste pachete adiționale se numesc subpachete. Subpachetele există pentru a trata cazuri în care nu doriți să asociați un fișier spec cu un pachet. În schimb, puteți defini mai multe pacheteîn fișierul spec, după caz. De exemplu, poate doriți să construiți pachetele runtimeși developer împreună, sau părțile client și server al eunei aplicații folosind subpachete. De asemenea, împărțirea seturilor de documentație mari în subpachete separate este o operațiune comună.
+ </div><div class="para">
+ Folosind subpachete, aveți:
+ </div><div class="para">
+ *Un fișier spec
+ </div><div class="para">
+ *Un pachet RPM sursă
+ </div><div class="para">
+ *Un set de comenzi de construcție
+ </div><div class="para">
+ *Pachete RPM binare multiple, câte unul per pachet sau subpachet
+ </div><div class="para">
+ În majoritatea cazurilor, subpachetele sunt create doar ca mijloc de a divide fișierele produse de un pachet în pachete separate. De exemplu, veți observa de multe ori biblioteci de development și fișiere headersunt separate într-un pachet diferit de pachetul principal al aplicației.Câteodată documentația este despărțită de pachetul principal, sau aplicațiile client și server sunt împărțite în pachete separate. Până la urmă acest faptrezultă în mutarea fișierelor în subpachete și nimic mai mult.
+ </div><div class="para">
+ Pentru a defini un subpachet într-un fișier spec, începeți cu directiva %package. De exemplu:
+ </div><div class="para">
+ %package nume_subpachet
+ </div><div class="para">
+ În mod implicit numele subpachetului va fi numele pachetului, o liniuță și numele subpachetului așa cum apare în directiva %package. De exemplu:
+ </div><div class="para">
+ %package server
+ </div><div class="para">
+ Acest exemplu denumește un subpachet server care este un subpachet real inclusîn pachetul telnet. În acest caz, numele subpachetului server va fi telnet-server, adică formatul de nume este pachet-subpachet.
+ </div><div class="para">
+ Dacă nu doriți acest format de nume, puteți folosi opțiunea -n a directivei %package pentru a defini un nume complet nou, folosindurmătoarea sintaxă:
+ </div><div class="para">
+ %package -n nume_nou_subpachet
+ </div><div class="para">
+ De exemplu:
+ </div><div class="para">
+ %package –n my-telnet-server
+ </div><div class="para">
+ Cu opțiunea -n puteți specifica numele întreg al subpachetului. Sistemul RPM nu va prefixa numele cu cel al pachetului care îl include.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id776325" class="title">Furnizarea informațiilor pentru subpachete</h1></div></div></div><div class="para">
+ La definirea unui subpachet trebuie să furnizați atâtea directive legate de informații despre pachet câte aveți nevoie, incluzând cel puțin directivele Summary:,Group:, și %description.
+ </div><div class="para">
+ %package server
+ </div><div class="para">
+ Requires: xinetd
+ </div><div class="para">
+ Group: System Environment/Daemons
+ </div><div class="para">
+ Sumar: Partea server pentru protocolul de login la distanță telnet
+ </div><div class="para">
+ Directiva %description pentru subpachete necesită numele subpachetuluifolosind următoarea sintaxă
+ </div><div class="para">
+ %description subpachet
+ </div><div class="para">
+ De exemplu:
+ </div><div class="para">
+ %description server
+ </div><div class="para">
+ Telnet este un protocol popular pentru logarea la sisteme la distanță
+ </div><div class="para">
+ via internet. Pachetul telnet-server include un daemon telnet care suportă login la distanță la mașina gazdă.
+ </div><div class="para">
+ Daemonul telnet este activat implicit. Puteți dezactiva
+ </div><div class="para">
+ daemonul telnet prin editarea /etc/xinetd.d/telnet.
+ </div><div class="para">
+ Dacă ați folosit opțiunea -n cu directiva %package, trebuie să repetațiopțiunea -n cu directiva %description. De exemplu:
+ </div><div class="para">
+ %description –n my-telnet-server
+ </div><div class="para">
+ Telnet este un protocol popular pentru logarea la sisteme la distanță
+ </div><div class="para">
+ via internet. Pachetul telnet-server include un daemon telnet care suportă login la distanță la mașina gazdă.
+ </div><div class="para">
+ Daemonul telnet este activat implicit. Puteți dezactiva
+ </div><div class="para">
+ daemonul telnet prin editarea /etc/xinetd.d/telnet.
+ </div><div class="para">
+ Același concept funcționează la secțiunea %files. Aveți nevoie de o secțiune%files separată pentru fiecare subpachet. De exemplu:
+ </div><div class="para">
+ %files server
+ </div><div class="para">
+ %defattr(-,root,root)
+ </div><div class="para">
+ %{_sbindir}/in.telnetd
+ </div><div class="para">
+ %{_mandir}/man5/issue.net.5*
+ </div><div class="para">
+ %{_mandir}/man8/in.telnetd.8*
+ </div><div class="para">
+ %{_mandir}/man8/telnetd.8*
+ </div><div class="para">
+ Din nou, dacă ați folosit opțiunea -n cu directiva %package, trebuie să repetați opțiunea -n cu secțiunea %files. De exemplu:
+ </div><div class="para">
+ %files –n my-telnet-server
+ </div><div class="para">
+ %defattr(-,root,root)
+ </div><div class="para">
+ %{_sbindir}/in.telnetd
+ </div><div class="para">
+ %{_mandir}/man5/issue.net.5*
+ </div><div class="para">
+ %{_mandir}/man8/in.telnetd.8*
+ </div><div class="para">
+ %{_mandir}/man8/telnetd.8*
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch10s03.html"><strong>Înapoi</strong>10.3. Scrierea scripturilor de verificare</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch10s04s02.html"><strong>Înainte</strong>10.4.2. Definirea scripturilor pentru subpachete</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch10s04s02.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch10s04s02.html
new file mode 100644
index 0000000..d907ba8
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch10s04s02.html
@@ -0,0 +1,46 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>10.4.2. Definirea scripturilor pentru subpachete</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch10s04.html" title="10.4. Crearea subpachetelor." /><link rel="prev" href="ch10s04.html" title="10.4. Crearea subpachetelor." /><link rel="next" href="ch10s04s03.html" title="10.4.3. Construirea subpachetelor" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch10s04.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch10s04s03.html"><strong>ÃŽnainte</s
trong></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id636560" class="title">Definirea scripturilor pentru subpachete</h1></div></div></div><div class="para">
+ Așa cum definiți secțiuni %files și %description separate pentru subpachete, la fel puteți defini scripturi install si uninstallpentru subpachete. Sintaxa e asemănătoare cu cea pentru secțiunile%files și %description:
+ </div><div class="para">
+ %pre subpachet
+ </div><div class="para">
+ De exemplu, Lista 11-2 afișează scripturile de la pachetul VNC.
+ </div><div class="para">
+ Lista 11-2: scripturile install și uninstall pentru pachetul VNC.
+ </div><div class="para">
+ %post server
+ </div><div class="para">
+ if [ "$1" = 1 ]; then
+ </div><div class="para">
+ /sbin/chkconfig --add vncserver
+ </div><div class="para">
+ fi
+ </div><div class="para">
+ </div><div class="para">
+ %preun server
+ </div><div class="para">
+ if [ "$1" = 0 ]; then
+ </div><div class="para">
+ /sbin/service vncserver stop >/dev/null 2>&1
+ </div><div class="para">
+ /sbin/chkconfig --del vncserver
+ </div><div class="para">
+ fi
+ </div><div class="para">
+ </div><div class="para">
+ %postun server
+ </div><div class="para">
+ if [ "$1" -ge "1" ]; then
+ </div><div class="para">
+ /sbin/service vncserver condrestart >/dev/null 2>&1
+ </div><div class="para">
+ fi
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch10s04.html"><strong>Înapoi</strong>10.4. Crearea subpachetelor.</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch10s04s03.html"><strong>Înainte</strong>10.4.3. Construirea subpachetelor</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch10s04s03.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch10s04s03.html
new file mode 100644
index 0000000..572cb59
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch10s04s03.html
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>10.4.3. Construirea subpachetelor</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch10s04.html" title="10.4. Crearea subpachetelor." /><link rel="prev" href="ch10s04s02.html" title="10.4.2. Definirea scripturilor pentru subpachete" /><link rel="next" href="ch10s05.html" title="10.5. Creating Relocatable Packages" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch10s04s02.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch10s05.htm
l"><strong>ÃŽnainte</strong></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id725439" class="title">Construirea subpachetelor</h1></div></div></div><div class="para">
+ Secțiunile build din fișierul spec servesc un dublu scop. Aceste secțiunisunt folosite pentru construirea pachetului principal precum și a subpachetelor.Este unul din motivele pentru care există atâtea opțiuni în macroul %setup.
+ </div><div class="para">
+ Macroul %setup permite despachetarea selectivă a surselor, în contrast cu opțiunea implicită de a despacheta toate sursele. De exemplu, definiția macroului %setup următor dă comenzii rpmbuild instrucțiuni specifice pentru despachetarea unui fișier sursă:
+ </div><div class="para">
+ %setup –D- T –a 1
+ </div><div class="para">
+ In this example, the –D option disables the automatic deletion of the directory where the sources will be unpacked. This means any previous contents of this directory, perhaps for other subpackages, will be left alone. The –T option disables the automatic unpacking of the source files, and the –a 1 option specifies to only unpack the first source file. You may need to use options like these when working with subpackages. Though, in most cases, subpackages are just means to partition the package files into separate packages. In cases like this, you will likely not need any of these special %setup options.
+ </div><div class="para">
+ Referință încrucișată
+ </div><div class="para">
+ <a class="xref" href="ch-specfiles.html">Cap. 9, <em>Working with Spec Files</em></a> covers the %setup macro and lists the available options.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch10s04s02.html"><strong>Înapoi</strong>10.4.2. Definirea scripturilor pentru subpachete</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch10s05.html"><strong>Înainte</strong>10.5. Creating Relocatable Packages</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch10s05.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch10s05.html
new file mode 100644
index 0000000..1a5067a
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch10s05.html
@@ -0,0 +1,34 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>10.5. Creating Relocatable Packages</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-advanced-packaging.html" title="Cap. 10. Creare avansată pachete RPM" /><link rel="prev" href="ch10s04s03.html" title="10.4.3. Construirea subpachetelor" /><link rel="next" href="ch10s05s02.html" title="10.5.2. Define the files section" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch10s04s03.html"><strong>Înapoi</strong></a></li><li class="next"><a accesskey="n" href="ch1
0s05s02.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id785807" class="title">Creating Relocatable Packages</h1></div></div></div><div class="para">
+ A relocatable package allows a user to specify where to install the package. For example, if you build a package for Red Hat Linux, the normal directory for binary executable programs is /usr/bin. Other versions of Linux, though, may place executable programs into /opt/bin, for example. If your package forces the use of /usr/bin, then your package won’t work on these other systems.
+ </div><div class="para">
+ Referință încrucișată
+ </div><div class="para">
+ <a class="xref" href="ch-other-linuxes.html">Cap. 18, <em>Using RPM on Non-Red Hat Linuxes</em></a> covers using RPM on other versions of Linux.
+ </div><div class="para">
+ With a relocatable package, though, you allow the user to redefine the top-level directories for your package, such as changing from /usr/bin to /opt/bin in the previous example. Making relocatable packages is generally considered a good thing, as you make the user’s life easier.
+ </div><div class="para">
+ To set up a relocatable package, you need to:
+ </div><div class="para">
+ *Set up the prefix directives for the top-level directories
+ </div><div class="para">
+ *Define the files under the prefix directories
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id785850" class="title">Setting up the prefixes</h1></div></div></div><div class="para">
+ The Prefix: directive names a top-level directory as a prefix you can relocate to another directory. For example:
+ </div><div class="para">
+ Prefix: /usr
+ </div><div class="para">
+ This states that all files under /usr can be relocated to other directories by simply mapping /usr to some other directory, such as /opt, on the rpm command line when installing or upgrading the package.
+ </div><div class="para">
+ Notă
+ </div><div class="para">
+ You can define more than one Prefix: directive to list more than one top-level directory.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch10s04s03.html"><strong>Înapoi</strong>10.4.3. Construirea subpachetelor</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch10s05s02.html"><strong>Înainte</strong>10.5.2. Define the files section</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch10s05s02.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch10s05s02.html
new file mode 100644
index 0000000..07f471a
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch10s05s02.html
@@ -0,0 +1,38 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>10.5.2. Define the files section</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch10s05.html" title="10.5. Creating Relocatable Packages" /><link rel="prev" href="ch10s05.html" title="10.5. Creating Relocatable Packages" /><link rel="next" href="ch10s05s03.html" title="10.5.3. Problems creating relocatable packages" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch10s05.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch10s05s0
3.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id748780" class="title">Define the files section</h1></div></div></div><div class="para">
+ When you use a Prefix: directive in your spec file, all files in the %files section must be under the directory named with the Prefix: directive. For example, from the jikes compiler package:
+ </div><div class="para">
+ Prefix: /usr
+ </div><div class="para">
+ </div><div class="para">
+ ...
+ </div><div class="para">
+ </div><div class="para">
+ %files
+ </div><div class="para">
+ %defattr(-,root,root)
+ </div><div class="para">
+ /usr/bin/jikes
+ </div><div class="para">
+ %doc /usr/doc/jikes-%{version}/license.htm
+ </div><div class="para">
+ %doc /usr/man/man1/jikes.1*
+ </div><div class="para">
+ In this example, all the files are under the /usr directory. All files in the %files section must be located under one of the Prefix: directories. If you have more than one top-level directory, such as /usr and /etc, define more than one Prefix: directive. For example:
+ </div><div class="para">
+ Prefix: /usr
+ </div><div class="para">
+ Prefix: /etc
+ </div><div class="para">
+ Referință încrucișată
+ </div><div class="para">
+ <a class="xref" href="ch-using-rpm.html">Cap. 3, <em>Using RPM</em></a> covers how to install or upgrade packages into different directories using the --relocate and --prefix options.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch10s05.html"><strong>Înapoi</strong>10.5. Creating Relocatable Packages</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch10s05s03.html"><strong>Înainte</strong>10.5.3. Problems creating relocatable packages</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch10s05s03.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch10s05s03.html
new file mode 100644
index 0000000..36d25b0
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch10s05s03.html
@@ -0,0 +1,20 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>10.5.3. Problems creating relocatable packages</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch10s05.html" title="10.5. Creating Relocatable Packages" /><link rel="prev" href="ch10s05s02.html" title="10.5.2. Define the files section" /><link rel="next" href="ch10s06.html" title="10.6. Defining Conditional Builds" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch10s05s02.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch10s06.html"><strong>
ÃŽnainte</strong></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id763558" class="title">Problems creating relocatable packages</h1></div></div></div><div class="para">
+ Not all packages work well as relocatable packages. Some packages have files that simply must go into a certain location and are therefore not relocatable. Some packages have programs that are hard-coded to look for files in a particular location and therefore cannot be relocated elsewhere. Other packages have symbolic links that also may not be relocatable. Furthermore, your package may provide software that is referenced by other packages, in the known directories. Relocating such a package will disable other software packages, packages you may not even know about.
+ </div><div class="para">
+ If your packages face any of these problems, chances are that making the package relocatable is not a good idea.
+ </div><div class="para">
+ In addition, if you use the %doc directive with local file names, remember that RPM will make a package-specific documentation directory, normally under /usr/doc. For example:
+ </div><div class="para">
+ %doc README NEWS
+ </div><div class="para">
+ This may defeat your attempts to create a relocatable package, unless you have a Prefix: directive with /usr, because the normal location is under /usr/doc, and all files in the %files section must start with one of the directories named with Prefix: directives.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch10s05s02.html"><strong>Înapoi</strong>10.5.2. Define the files section</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch10s06.html"><strong>Înainte</strong>10.6. Defining Conditional Builds</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch10s06.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch10s06.html
new file mode 100644
index 0000000..b3c6d5f
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch10s06.html
@@ -0,0 +1,44 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>10.6. Defining Conditional Builds</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-advanced-packaging.html" title="Cap. 10. Creare avansată pachete RPM" /><link rel="prev" href="ch10s05s03.html" title="10.5.3. Problems creating relocatable packages" /><link rel="next" href="ch10s06s02.html" title="10.6.2. Using conditional blocks" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch10s05s03.html"><strong>Înapoi</strong></a></li><li class="next"><a accesskey=
"n" href="ch10s06s02.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id763596" class="title">Defining Conditional Builds</h1></div></div></div><div class="para">
+ With the ability to define macros inside spec files, and also to use macros defined elsewhere, you gain a lot of control over how your package gets built. You can go further, though, and use special directives to perform only certain commands based on certain conditions. This adds a powerful capability to your spec files, and also makes it much easier to do things like build for multiple versions of Linux or other operating systems, as well as handle various backwards-compatibility issues.
+ </div><div class="para">
+ To define conditional build commands, you need to create conditional constructs in your package’s spec file. In addition, you need to define macros that the conditional constructs use to determine whether or not to execute a set of spec file directives.
+ </div><div class="para">
+ Referință încrucișată
+ </div><div class="para">
+ See <a class="xref" href="ch-customizing-rpm.html">Cap. 20, <em>Customizing RPM Behavior</em></a> for more on macro file locations, and <a class="xref" href="ch-other-linuxes.html">Cap. 18, <em>Using RPM on Non-Red Hat Linuxes</em></a> and <a class="xref" href="ch-other-os.html">Cap. 19, <em>RPM on Other Operating Systems</em></a> for more on using RPM on other versions of Linux and other operating systems, respectively.
+ </div><div class="para">
+ RPM supports a number of ways to make parts of your spec file enabled or disabled based on certain conditions. These include conditional macros, conditional blocks, and special directives based on the system architecture.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id763642" class="title">Defining conditional macros</h1></div></div></div><div class="para">
+ You can use a special syntax to test for the existence of macros. For example:
+ </div><div class="para">
+ %{?macro_to_test: expression}
+ </div><div class="para">
+ This syntax tells RPM to expand the expression if the macro macro_to_test exists. If the macro macro_to_test does not exist, nothing will be output. You can also reverse this test. A leading exclamation point, !, tests for the non-existence of a macro:
+ </div><div class="para">
+ %{!?macro_to_test: expression}
+ </div><div class="para">
+ In this example, if the macro_to_test macro does not exist, RPM will expand the expression.
+ </div><div class="para">
+ If you want, you can omit the expression and just test for the existence of the macro. If it exists, RPM will use the value of the macro. If the macro does not exist, RPM will use nothing. For example:
+ </div><div class="para">
+ %build
+ </div><div class="para">
+ ./configure %{?_with_ldap}
+ </div><div class="para">
+ make
+ </div><div class="para">
+ In this case, if the _with_ldap macro exists, the value of that macro will get passed on the command line to the configure script. If the _with_ldap macro does not exist, nothing extra will be passed on the command line to the configure script. This is very important when creating commands to build or install packages.
+ </div><div class="para">
+ Referință încrucișată
+ </div><div class="para">
+ Many of the macros you will test this way are set up with the --with command-line parameter. See <a class="xref" href="ch-other-linuxes.html">Cap. 18, <em>Using RPM on Non-Red Hat Linuxes</em></a> for details.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch10s05s03.html"><strong>Înapoi</strong>10.5.3. Problems creating relocatable packages</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch10s06s02.html"><strong>Înainte</strong>10.6.2. Using conditional blocks</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch10s06s02.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch10s06s02.html
new file mode 100644
index 0000000..57ead1b
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch10s06s02.html
@@ -0,0 +1,60 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>10.6.2. Using conditional blocks</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch10s06.html" title="10.6. Defining Conditional Builds" /><link rel="prev" href="ch10s06.html" title="10.6. Defining Conditional Builds" /><link rel="next" href="ch10s06s03.html" title="10.6.3. Using architecture-based conditionals" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch10s06.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch10s06s03.htm
l"><strong>ÃŽnainte</strong></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id859408" class="title">Using conditional blocks</h1></div></div></div><div class="para">
+ The %if macro enables all the directives up to the %endif directive, if the condition is true. This is much like scripting languages. For example:
+ </div><div class="para">
+ %if %{old_5x}
+ </div><div class="para">
+ %define b5x 1
+ </div><div class="para">
+ %undefine b6x
+ </div><div class="para">
+ %endif
+ </div><div class="para">
+ In this case, if the %old_5x macro has a value, the test will be true and all the directives inside the block will get executed.
+ </div><div class="para">
+ A %else allows you to specify what to do if the test is not successful. For example:
+ </div><div class="para">
+ %if %{old_5x}
+ </div><div class="para">
+ %define b5x 1
+ </div><div class="para">
+ %undefine b6x
+ </div><div class="para">
+ %else
+ </div><div class="para">
+ %define b6x 1
+ </div><div class="para">
+ %undefine b5x
+ </div><div class="para">
+ %endif
+ </div><div class="para">
+ In this case, if the %old_5x macro has a value, then all the directives up to the %else will get executed. Otherwise, if the %old_5x macro has no value, the directives from the %else to the %endif will get executed.
+ </div><div class="para">
+ Again, use an exclamation point to negate the test. For example:
+ </div><div class="para">
+ %if ! %{old_5x}
+ </div><div class="para">
+ %define b5x 1
+ </div><div class="para">
+ %undefine b6x
+ </div><div class="para">
+ %endif
+ </div><div class="para">
+ You can use a && for an AND test. For example:
+ </div><div class="para">
+ %if %{old_5x} && %{old_6x}
+ </div><div class="para">
+ %{error: You cannot build for .5x and .6x at the same time}
+ </div><div class="para">
+ %quit
+ </div><div class="para">
+ %endif
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch10s06.html"><strong>Înapoi</strong>10.6. Defining Conditional Builds</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch10s06s03.html"><strong>Înainte</strong>10.6.3. Using architecture-based conditionals</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch10s06s03.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch10s06s03.html
new file mode 100644
index 0000000..45d92e0
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch10s06s03.html
@@ -0,0 +1,91 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>10.6.3. Using architecture-based conditionals</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch10s06.html" title="10.6. Defining Conditional Builds" /><link rel="prev" href="ch10s06s02.html" title="10.6.2. Using conditional blocks" /><link rel="next" href="ch10s07.html" title="10.7. Summary" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch10s06s02.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch10s07.html"><strong>ÃŽnainte</strong></a><
/li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id765399" class="title">Using architecture-based conditionals</h1></div></div></div><div class="para">
+ In addition to the general-purpose %if conditional directive, you can use special directives that test for processor architecture and operating system.
+ </div><div class="para">
+ The %ifarch directive enables all the directives up to the %endif directive, if the processor architecture matches the values you pass to the %ifarch directive. For example:
+ </div><div class="para">
+ %ifarch sparc
+ </div><div class="para">
+ %define b5x 1
+ </div><div class="para">
+ %undefine b6x
+ </div><div class="para">
+ %endif
+ </div><div class="para">
+ This block will only get executed if the processor architecture is SPARC.
+ </div><div class="para">
+ Referință încrucișată
+ </div><div class="para">
+ <a class="xref" href="ch-customizing-rpm.html">Cap. 20, <em>Customizing RPM Behavior</em></a> covers RPM architecture and operating system names.
+ </div><div class="para">
+ You can pass more than one architecture name, separated by commas or spaces. For example:
+ </div><div class="para">
+ %ifarch sparc alpha
+ </div><div class="para">
+ %define b5x 1
+ </div><div class="para">
+ %undefine b6x
+ </div><div class="para">
+ %endif
+ </div><div class="para">
+ This example tests if the processor architecture is SPARC or Alpha.
+ </div><div class="para">
+ As with the %if directive, you can also use an %else, to cover all cases where the test is not true. For example:
+ </div><div class="para">
+ %ifarch sparc alpha
+ </div><div class="para">
+ %define b5x 1
+ </div><div class="para">
+ %undefine b6x
+ </div><div class="para">
+ %else
+ </div><div class="para">
+ %define b6x 1
+ </div><div class="para">
+ %undefine b5x
+ </div><div class="para">
+ %endif
+ </div><div class="para">
+ This example tests if the processor architecture is SPARC or Alpha. If so, the directives from the %ifarch to the %else are executed. If not, the directives from the %else to the %endif are executed.
+ </div><div class="para">
+ The %ifnarch directive reverses the %ifarch test. That is, %ifnarch tests if the architecture is not one of the values listed. The following example tests if the processor architecture is not an i386 or an Alpha.
+ </div><div class="para">
+ %ifnarch i386 alpha
+ </div><div class="para">
+ %define b5x 1
+ </div><div class="para">
+ %undefine b6x
+ </div><div class="para">
+ %endif
+ </div><div class="para">
+ </div><div class="para">
+ The %ifos directive tests for the operating system. For example:
+ </div><div class="para">
+ %ifos linux
+ </div><div class="para">
+ %define b5x 1
+ </div><div class="para">
+ %undefine b6x
+ </div><div class="para">
+ %endif
+ </div><div class="para">
+ This example tests if the operating system is Linux. You can reverse the test with the %ifnos directive. For example:
+ </div><div class="para">
+ %ifnos irix
+ </div><div class="para">
+ %define b5x 1
+ </div><div class="para">
+ %undefine b6x
+ </div><div class="para">
+ %endif
+ </div><div class="para">
+ This example tests if the operating system is not Irix.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch10s06s02.html"><strong>Înapoi</strong>10.6.2. Using conditional blocks</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch10s07.html"><strong>Înainte</strong>10.7. Summary</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch10s07.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch10s07.html
new file mode 100644
index 0000000..23a37de
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch10s07.html
@@ -0,0 +1,26 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>10.7. Summary</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-advanced-packaging.html" title="Cap. 10. Creare avansată pachete RPM" /><link rel="prev" href="ch10s06s03.html" title="10.6.3. Using architecture-based conditionals" /><link rel="next" href="ch-rpmbuild.html" title="Cap. 11. Controlling the Build with rpmbuild" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch10s06s03.html"><strong>Înapoi</strong></a></li><li class="next"><
a accesskey="n" href="ch-rpmbuild.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id677037" class="title">Summary</h1></div></div></div><div class="para">
+ This chapter covers advanced topics in creating packages. Dependencies are very important. You need to specify which packages or capabilities your package requires, so the RPM system can ensure that all requirements are met before allowing users to install the package. If you do not specify the dependencies properly, then you are defeating the integrity of the RPM system.
+ </div><div class="para">
+ In addition to specifying what your package requires, it is also important to specify other dependency information. For example, if your package conflicts with another package, you need to very clearly state this. E-mail and Web server packages often conflict with other servers of the same type.
+ </div><div class="para">
+ You can specify both package dependencies as well as build dependencies. For example, you may need certain developer libraries to build your package, but not to install it. These are build dependencies.
+ </div><div class="para">
+ To help manage dependencies between packages and system configuration issues, you can set up trigger scripts. A trigger is a script in your package that gets executed when another package is installed or removed. If your package, for example, is an e-mail client program, it may need to execute a script should the e-mail server package change. This is a great usage for triggers.
+ </div><div class="para">
+ If your package has a complicated installation, the normal RPM verification won’t be sufficient. To help the RPM system ensure the integrity of all the packages, you can write a verify script in your spec file to perform any extra commands necessary to verify your package has been properly installed.
+ </div><div class="para">
+ Relocatable packages allow users to install your packages in different locations than originally planned. This is very useful when working with more than one version of Linux, or with other operating systems. For example, most Linux commands are stored in /usr/bin, at least for Red Hat Linux. Other Linux distributions, or other operating systems may specify that programs added to the original set should be stored in /opt/bin and not /usr/bin, for example. Making your package relocatable helps users in these situations.
+ </div><div class="para">
+ Conditional directives in your spec file allow you to control the build on different processor architectures and operating systems. The %if directive tests if a value is set. If so, then all the directives up to the %endif directive are executed. If you need to execute a different set of directives, use %else. In this case, if the %if test is true, RPM executes the directives up to the %else. If the test is not true, RPM executes the directives up to the %endif.
+ </div><div class="para">
+ Once you have your spec file defined, the next step is to start building packages. The next chapter covers options for the rpmbuild command and how you can use rpmbuild to make your packages.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch10s06s03.html"><strong>Înapoi</strong>10.6.3. Using architecture-based conditionals</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch-rpmbuild.html"><strong>Înainte</strong>Cap. 11. Controlling the Build with rpmbuild</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch11s02.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch11s02.html
new file mode 100644
index 0000000..6c5bf73
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch11s02.html
@@ -0,0 +1,106 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>11.2. Building RPMs Without an External Spec File</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-rpmbuild.html" title="Cap. 11. Controlling the Build with rpmbuild" /><link rel="prev" href="ch-rpmbuild.html" title="Cap. 11. Controlling the Build with rpmbuild" /><link rel="next" href="ch11s02s02.html" title="11.2.2. The expected archive structure" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-rpmbuild.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accessk
ey="n" href="ch11s02s02.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id558716" class="title">Building RPMs Without an External Spec File</h1></div></div></div><div class="para">
+ Most of the options for the rpmbuild command require an RPM spec file. This file defines all the necessary parameters for the RPM to build. If you’ve downloaded an application, though, you may not have all the information needed to build a spec file. In addition, writing the spec file is the most time-consuming task when building RPMs. If you are lucky, the provider of a given application may have already created a spec file and included the spec file within the source distribution.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id558731" class="title">Options for working with tar archives</h1></div></div></div><div class="para">
+ A special set of options aims toward building RPMs with spec files stored in tar archives, also called tarballs. Tarballs are files combined with the tar (tape archiver) utility and then optionally compressed, usually with the gzip command. Because this format is used so often for UNIX and Linux software, you can use a set of -t options to the rpmbuild command that mimic the -b options.
+ </div><div class="para">
+ The basic syntax follows:
+ </div><div class="para">
+ rpmbuild -tBuildStage compressed_tar_archive
+ </div><div class="para">
+ The -t option is a lot like the -b option covered in <a class="xref" href="ch-creating-rpms.html">Cap. 8, <em>Creating RPMs: An Overview</em></a> , except -t tells rpmbuild to build an RPM from a compressed tar archive instead of from an RPM spec file. You still need a spec file. These commands just assume that the spec file is located within the tar archive. The extra BuildStage option is a special code that tells the rpmbuild command how far to go when building. Table 12-2 lists these options:
+ </div><div class="para">
+ Table 12-2 Options for building with rpmbuild with tar archives
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Option
+ </div>
+
+ </td><td>
+ <div class="para">
+ Usage
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -ta
+ </div>
+
+ </td><td>
+ <div class="para">
+ Build all, both a binary and source RPM
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -tb
+ </div>
+
+ </td><td>
+ <div class="para">
+ Build a binary RPM
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -tc
+ </div>
+
+ </td><td>
+ <div class="para">
+ Stop after the %build section
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -tp
+ </div>
+
+ </td><td>
+ <div class="para">
+ Stop after the %prep section
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -ti
+ </div>
+
+ </td><td>
+ <div class="para">
+ Stop after the %install section
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -tl
+ </div>
+
+ </td><td>
+ <div class="para">
+ Check the listing of files for the RPM
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -ts
+ </div>
+
+ </td><td>
+ <div class="para">
+ Build a source RPM only
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ Note
+ </div><div class="para">
+ These command-line options work with a tar archive or a compressed tar archive.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-rpmbuild.html"><strong>Înapoi</strong>Cap. 11. Controlling the Build with rpmbuild</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch11s02s02.html"><strong>Înainte</strong>11.2.2. The expected archive structure</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch11s02s02.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch11s02s02.html
new file mode 100644
index 0000000..04f20c8
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch11s02s02.html
@@ -0,0 +1,30 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>11.2.2. The expected archive structure</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch11s02.html" title="11.2. Building RPMs Without an External Spec File" /><link rel="prev" href="ch11s02.html" title="11.2. Building RPMs Without an External Spec File" /><link rel="next" href="ch11s03.html" title="11.3. Working with Source RPMs" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch11s02.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="
ch11s03.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id642001" class="title">The expected archive structure</h1></div></div></div><div class="para">
+ To build a package this way, the tar archive must have enough of an expected structure, such as a configure script and a Makefile with the expected make targets. The most crucial element is that the tar archive must have the package spec file.That’s because the rpmbuild command doesn’t know how to build every program in the universe. Instead, rpmbuild expects to find a spec file to tell it what to do. If you see an error like the following, then your tar archive likely is missing the spec file:
+ </div><div class="para">
+ $ rpmbuild -tc vixie-cron*tar.gz
+ </div><div class="para">
+ error: Name field must be present in package: (main package)
+ </div><div class="para">
+ error: Version field must be present in package: (main package)
+ </div><div class="para">
+ error: Release field must be present in package: (main package)
+ </div><div class="para">
+ error: Summary field must be present in package: (main package)
+ </div><div class="para">
+ error: Group field must be present in package: (main package)
+ </div><div class="para">
+ error: License field must be present in package: (main package)
+ </div><div class="para">
+ These errors show expected tags from the missing spec file.
+ </div><div class="para">
+ </div><div class="para">
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch11s02.html"><strong>Înapoi</strong>11.2. Building RPMs Without an External Spec File</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch11s03.html"><strong>Înainte</strong>11.3. Working with Source RPMs</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch11s03.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch11s03.html
new file mode 100644
index 0000000..7321cfa
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch11s03.html
@@ -0,0 +1,206 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>11.3. Working with Source RPMs</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-rpmbuild.html" title="Cap. 11. Controlling the Build with rpmbuild" /><link rel="prev" href="ch11s02s02.html" title="11.2.2. The expected archive structure" /><link rel="next" href="ch11s03s02.html" title="11.3.2. Recompiling binaries from source RPMs" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch11s02s02.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesske
y="n" href="ch11s03s02.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id670109" class="title">Working with Source RPMs</h1></div></div></div><div class="para">
+ Most of your work with the rpmbuild command will likely be to create binary RPMs after you have the sources for an application and a spec file. You can also get a lot of mileage out of source RPMs, whether you build them or download them.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ <a class="xref" href="ch-specfiles.html">Cap. 9, <em>Working with Spec Files</em></a> covers the spec file in depth.
+ </div><div class="para">
+ Because they are RPMs themselves, source RPMs act like other RPMs. For example, you can use the rpm -i command to install a source RPM. This installs the sources provided by the source RPM, not the actual application. Normally, when you install a source RPM on a Red Hat Linux system, the package gets installed into /usr/src/redhat.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ This directory is obviously specific to Red Hat Linux. On other Linux distributions, you'll likely see directories such as /usr/src/OpenLinux for SCO (formerly Caldera) OpenLinux.
+ </div><div class="para">
+ Installing a source RPM is not exactly the same as installing a binary RPM. For example, the rpm command does not update the RPM database when you install a source RPM. In addition, listing the files in a source RPM only shows the relative paths, not the full paths.
+ </div><div class="para">
+ Once installation is complete, you can use the rpmbuild command to create a binary RPM from the sources in the source RPM, using the -b command-line options introduced in <a class="xref" href="ch-creating-rpms.html">Cap. 8, <em>Creating RPMs: An Overview</em></a> . The next sections show more shortcuts with source RPMs.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id670165" class="title">Rebuilding binary RPMS from source RPMs</h1></div></div></div><div class="para">
+ As a shortcut, you do not have to install a source RPM to create a binary RPM. Instead, you can build the binary RPM directory using the --rebuild option.
+ </div><div class="para">
+ The --rebuild option tells the rpmbuild command to rebuild a binary RPM from a source RPM file. The basic syntax is:
+ </div><div class="para">
+ rpmbuild --rebuild package.src.rpm
+ </div><div class="para">
+ This command builds a binary RPM out of a source RPM with a minimum of fuss. For example:
+ </div><div class="para">
+ $ rpmbuild --rebuild unix2dos-2.2-17.src.rpm
+ </div><div class="para">
+ Installing unix2dos-2.2-17.src.rpm
+ </div><div class="para">
+ Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.15828
+ </div><div class="para">
+ + umask 022
+ </div><div class="para">
+ + cd /usr/src/redhat/BUILD
+ </div><div class="para">
+ + LANG=C
+ </div><div class="para">
+ + export LANG
+ </div><div class="para">
+ + cd /usr/src/redhat/BUILD
+ </div><div class="para">
+ + rm -rf unix2dos-2.2
+ </div><div class="para">
+ + /bin/mkdir -p unix2dos-2.2
+ </div><div class="para">
+ + cd unix2dos-2.2
+ </div><div class="para">
+ + /usr/bin/gzip -dc /usr/src/redhat/S OURCES/unix2dos-2.2.src.tar.gz
+ </div><div class="para">
+ + tar -xf -
+ </div><div class="para">
+ + STATUS=0
+ </div><div class="para">
+ + '[' 0 -ne 0 ']'
+ </div><div class="para">
+ ++ /usr/bin/id -u
+ </div><div class="para">
+ + '[' 500 = 0 ']'
+ </div><div class="para">
+ ++ /usr/bin/id -u
+ </div><div class="para">
+ + '[' 500 = 0 ']'
+ </div><div class="para">
+ + /bin/chmod -Rf a+rX,g-w,o-w .
+ </div><div class="para">
+ + echo 'Patch #0 (unix2dos-mkstemp.patch):'
+ </div><div class="para">
+ Patch #0 (unix2dos-mkstemp.patch):
+ </div><div class="para">
+ + patch -p1 -b --suffix .sec -s
+ </div><div class="para">
+ + echo 'Patch #1 (unix2dos-2.2-segfault.patch):'
+ </div><div class="para">
+ Patch #1 (unix2dos-2.2-segfault.patch):
+ </div><div class="para">
+ + patch -p1 -b --suffix .segf -s
+ </div><div class="para">
+ + echo 'Patch #2 (unix2dos-2.2-manpage.patch):'
+ </div><div class="para">
+ Patch #2 (unix2dos-2.2-manpage.patch):
+ </div><div class="para">
+ + patch -p1 -b --suffix .man -s
+ </div><div class="para">
+ + perl -pi -e 's,^#endif.*,#endif,g;s,^#else.*,#else,g' unix2dos.c unix2dos.h
+ </div><div class="para">
+ + exit 0
+ </div><div class="para">
+ Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.60650
+ </div><div class="para">
+ + umask 022
+ </div><div class="para">
+ + cd /usr/src/redhat/BUILD
+ </div><div class="para">
+ + cd unix2dos-2.2
+ </div><div class="para">
+ + LANG=C
+ </div><div class="para">
+ + export LANG
+ </div><div class="para">
+ + gcc -O2 -march=i386 -mcpu=i686 -ounix2dos unix2dos.c
+ </div><div class="para">
+ + exit 0
+ </div><div class="para">
+ Executing(%install): /bin/sh -e /var/tmp/rpm-tmp.35128
+ </div><div class="para">
+ + umask 022
+ </div><div class="para">
+ + cd /usr/src/redhat/BUILD
+ </div><div class="para">
+ + cd unix2dos-2.2
+ </div><div class="para">
+ + LANG=C
+ </div><div class="para">
+ + export LANG
+ </div><div class="para">
+ + rm -rf /var/tmp/unix2dos-root
+ </div><div class="para">
+ + mkdir -p /var/tmp/unix2dos-root/usr/bin /var/tmp/unix2dos-
+ </div><div class="para">
+ root/usr/share/man/man1
+ </div><div class="para">
+ + install -m755 unix2dos /var/tmp/unix2dos-root/usr/bin
+ </div><div class="para">
+ + install -m444 unix2dos.1 /var/tmp/unix2dos-root/usr/share/man/man1
+ </div><div class="para">
+ + /usr/lib/rpm/redhat/brp-compress
+ </div><div class="para">
+ + /usr/lib/rpm/redhat/brp-strip
+ </div><div class="para">
+ + /usr/lib/rpm/redhat/brp-strip-comment-note
+ </div><div class="para">
+ Processing files: unix2dos-2.2-17
+ </div><div class="para">
+ Executing(%doc): /bin/sh -e /var/tmp/rpm-tmp.12033
+ </div><div class="para">
+ + umask 022
+ </div><div class="para">
+ + cd /usr/src/redhat/BUILD
+ </div><div class="para">
+ + cd unix2dos-2.2
+ </div><div class="para">
+ + DOCDIR=/var/tmp/unix2dos-root/usr/share/doc/unix2dos-2.2
+ </div><div class="para">
+ + export DOCDIR
+ </div><div class="para">
+ + rm -rf /var/tmp/unix2dos-root/usr/share/doc/unix2dos-2.2
+ </div><div class="para">
+ + /bin/mkdir -p /var/tmp/unix2dos-root/usr/share/doc/unix2dos-2.2
+ </div><div class="para">
+ + cp -pr COPYRIGHT /var/tmp/unix2dos-root/usr/share/doc/unix2dos-2.2
+ </div><div class="para">
+ + exit 0
+ </div><div class="para">
+ Finding Provides: /usr/lib/rpm/find-provides
+ </div><div class="para">
+ Finding Requires: /usr/lib/rpm/find-requires
+ </div><div class="para">
+ PreReq: rpmlib(PayloadFilesHavePrefix) <= 4.0-1 rpmlib(CompressedFileNames)
+ </div><div class="para">
+ <= 3.0.4-1
+ </div><div class="para">
+ Requires(rpmlib): rpmlib(PayloadFilesHavePrefix) <= 4.0-1
+ </div><div class="para">
+ rpmlib(CompressedFileNames) <= 3.0.4-1
+ </div><div class="para">
+ Requires: libc.so.6 libc.so.6(GLIBC_2.0) libc.so.6(GLIBC_2.1)
+ </div><div class="para">
+ Checking for unpackaged file(s): /usr/lib/rpm/check-files /var/tmp/unix2dos-root
+ </div><div class="para">
+ Wrote: /usr/src/redhat/RPMS/i386/unix2dos-2.2-17.i386.rpm
+ </div><div class="para">
+ Executing(%clean): /bin/sh -e /var/tmp/rpm-tmp.47653
+ </div><div class="para">
+ + umask 022
+ </div><div class="para">
+ + cd /usr/src/redhat/BUILD
+ </div><div class="para">
+ + cd unix2dos-2.2
+ </div><div class="para">
+ + rm -rf /var/tmp/unix2dos-root
+ </div><div class="para">
+ + exit 0
+ </div><div class="para">
+ Executing(--clean): /bin/sh -e /var/tmp/rpm-tmp.47653
+ </div><div class="para">
+ + umask 022
+ </div><div class="para">
+ + cd /usr/src/redhat/BUILD
+ </div><div class="para">
+ + rm -rf unix2dos-2.2
+ </div><div class="para">
+ + exit 0
+ </div><div class="para">
+ With the --rebuild option, the rpmbuild command installs the source RPM for you and then performs the preparation, compile, and installation stages of building a binary RPM. Unless there are errors, you should have a new binary RPM file.
+ </div><div class="para">
+ When complete, the rpmbuild --rebuild command cleans out the built files in the build directory, as if the --clean option were used. The rpmbuild --rebuild command also removes the installed sources and spec file upon completion.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch11s02s02.html"><strong>Înapoi</strong>11.2.2. The expected archive structure</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch11s03s02.html"><strong>Înainte</strong>11.3.2. Recompiling binaries from source RPMs</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch11s03s02.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch11s03s02.html
new file mode 100644
index 0000000..e1a42f6
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch11s03s02.html
@@ -0,0 +1,24 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>11.3.2. Recompiling binaries from source RPMs</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch11s03.html" title="11.3. Working with Source RPMs" /><link rel="prev" href="ch11s03.html" title="11.3. Working with Source RPMs" /><link rel="next" href="ch11s03s03.html" title="11.3.3. SRPMS? Finding source RPMs" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch11s03.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch11s03s03.html"><strong>ÃŽnain
te</strong></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id666240" class="title">Recompiling binaries from source RPMs</h1></div></div></div><div class="para">
+ If you just want to recompile the files in a source RPM, you can use the --recompile option. The --recompile option tells the rpmbuild command to recompile the binary application from a source RPM.
+ </div><div class="para">
+ For example:
+ </div><div class="para">
+ rpmbuild --recompile package.src.rpm
+ </div><div class="para">
+ This is the same as installing the source RPM and then running rpmbuild -bc --clean with the package spec file.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ There is no difference between --recompile and --rebuild in RPM 4.1. RPM 4.2 fixes this problem.
+ </div><div class="para">
+ </div><div class="para">
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch11s03.html"><strong>Înapoi</strong>11.3. Working with Source RPMs</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch11s03s03.html"><strong>Înainte</strong>11.3.3. SRPMS? Finding source RPMs</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch11s03s03.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch11s03s03.html
new file mode 100644
index 0000000..5ab543c
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch11s03s03.html
@@ -0,0 +1,14 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>11.3.3. SRPMS? Finding source RPMs</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch11s03.html" title="11.3. Working with Source RPMs" /><link rel="prev" href="ch11s03s02.html" title="11.3.2. Recompiling binaries from source RPMs" /><link rel="next" href="ch11s04.html" title="11.4. Signing Built RPMs" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch11s03s02.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch11s04.html"><strong>Ã
Žnainte</strong></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id580558" class="title">SRPMS? Finding source RPMs</h1></div></div></div><div class="para">
+ Often, source RPMs are abbreviated as SRPMs. In fact, if you see a directory named SRPM or SRPMS, chances are the directory holds source RPMs. (Red Hat uses this convention for its Linux distributions.)
+ </div><div class="para">
+ The SRPMS directories on Red Hat CD-ROMs or on the Red Hat FTP Internet site, ftp.redhat.com, indicate directories that hold source RPMs.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch11s03s02.html"><strong>Înapoi</strong>11.3.2. Recompiling binaries from source RPMs</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch11s04.html"><strong>Înainte</strong>11.4. Signing Built RPMs</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch11s04.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch11s04.html
new file mode 100644
index 0000000..0b77e10
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch11s04.html
@@ -0,0 +1,30 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>11.4. Signing Built RPMs</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-rpmbuild.html" title="Cap. 11. Controlling the Build with rpmbuild" /><link rel="prev" href="ch11s03s03.html" title="11.3.3. SRPMS? Finding source RPMs" /><link rel="next" href="ch11s04s02.html" title="11.4.2. Configuring a signature" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch11s03s03.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch11s0
4s02.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id580578" class="title">Signing Built RPMs</h1></div></div></div><div class="para">
+ Signing RPMs adds an extra level of trustworthiness to your RPMs. A digital signature helps establish that the package comes from you, really you, and not from someone masquerading as you. Unfortunately, the RPM system requires a bit of set up work before you can sign RPMs.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id580590" class="title">Checking that the GPG software is installed</h1></div></div></div><div class="para">
+ To sign packages, you need to ensure that you have the gpg command installed and configured. To check that this command is installed, use a command like the following:
+ </div><div class="para">
+ $ rpm -qf `which gpg`
+ </div><div class="para">
+ gnupg-1.0.7-6
+ </div><div class="para">
+ This shows that the command is available.
+ </div><div class="para">
+ GPG and PGP? Acronyms Explained
+ </div><div class="para">
+ The RPM documentation uses GPG and PGP pretty much interchangeably, so much so, in fact, that you may think these are typographical errors. Not so.
+ </div><div class="para">
+ PGP stands for Pretty Good Privacy. Invented by Phil Zimmerman, PGP was originally invented to encrypt e-mail to allow for private communication. Based on a public-key cryptography algorithm, PGP also supports encrypted digital signatures. These signatures allow you to verify that a package you have downloaded really comes from the vendor you think it does. You do this by using the vendor’s public key.
+ </div><div class="para">
+ GPG stands for GNU Privacy Guard, a free, open-source implementation of PGP from the GNU project. GPG aims to be compatible with the OpenPGP Internet standard as defined in RFC 2440. It started when a number of developers wanted a free implementation. One such free implementation, GPG, allows Linux vendors such as Red Hat to include PGP in their products. So, in a sense, GPG provides PGP.
+ </div><div class="para">
+ PGP has a long and somewhat troubled history as an open-source product and as a commercial product. See www.philzimmermann.com for background on PGP and its long history. See www.gnupg.org for more details on GPG.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch11s03s03.html"><strong>Înapoi</strong>11.3.3. SRPMS? Finding source RPMs</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch11s04s02.html"><strong>Înainte</strong>11.4.2. Configuring a signature</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch11s04s02.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch11s04s02.html
new file mode 100644
index 0000000..6eddc6d
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch11s04s02.html
@@ -0,0 +1,146 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>11.4.2. Configuring a signature</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch11s04.html" title="11.4. Signing Built RPMs" /><link rel="prev" href="ch11s04.html" title="11.4. Signing Built RPMs" /><link rel="next" href="ch11s04s03.html" title="11.4.3. Signing with the rpmbuild command" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch11s04.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch11s04s03.html"><strong>ÃŽnainte</s
trong></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id702533" class="title">Configuring a signature</h1></div></div></div><div class="para">
+ To configure a signature, you first need to create a new key with the gpg command, using the --gen-key option, as shown following:
+ </div><div class="para">
+ $ gpg --gen-key
+ </div><div class="para">
+ gpg (GnuPG) 1.0.7; Copyright (C) 2002 Free Software Foundation, Inc.
+ </div><div class="para">
+ This program comes with ABSOLUTELY NO WARRANTY.
+ </div><div class="para">
+ This is free software, and you are welcome to redistribute it
+ </div><div class="para">
+ under certain conditions. See the file COPYING for details.
+ </div><div class="para">
+ </div><div class="para">
+ gpg: Warning: using insecure memory!
+ </div><div class="para">
+ gpg: please see http://www.gnupg.org/faq.html for more information
+ </div><div class="para">
+ gpg: keyring `/home2/ericfj/.gnupg/secring.gpg' created
+ </div><div class="para">
+ gpg: keyring `/home2/ericfj/.gnupg/pubring.gpg' created
+ </div><div class="para">
+ Please select what kind of key you want:
+ </div><div class="para">
+ (1) DSA and ElGamal (default)
+ </div><div class="para">
+ (2) DSA (sign only)
+ </div><div class="para">
+ (4) ElGamal (sign and encrypt)
+ </div><div class="para">
+ (5) RSA (sign only)
+ </div><div class="para">
+ Your selection? 1
+ </div><div class="para">
+ DSA keypair will have 1024 bits.
+ </div><div class="para">
+ About to generate a new ELG-E keypair.
+ </div><div class="para">
+ minimum keysize is 768 bits
+ </div><div class="para">
+ default keysize is 1024 bits
+ </div><div class="para">
+ highest suggested keysize is 2048 bits
+ </div><div class="para">
+ What keysize do you want? (1024)
+ </div><div class="para">
+ </div><div class="para">
+ Requested keysize is 1024 bits
+ </div><div class="para">
+ Please specify how long the key should be valid.
+ </div><div class="para">
+ 0 = key does not expire
+ </div><div class="para">
+ <n> = key expires in n days
+ </div><div class="para">
+ <n>w = key expires in n weeks
+ </div><div class="para">
+ <n>m = key expires in n months
+ </div><div class="para">
+ <n>y = key expires in n years
+ </div><div class="para">
+ Key is valid for? (0)
+ </div><div class="para">
+ </div><div class="para">
+ You need a User-ID to identify your key; the software constructs the user id
+ </div><div class="para">
+ from Real Name, Comment and Email Address in this form:
+ </div><div class="para">
+ "Heinrich Heine (Der Dichter) <heinrichh at duesseldorf.de>"
+ </div><div class="para">
+ </div><div class="para">
+ Real name: Eric Foster-Johnson
+ </div><div class="para">
+ Email address: please_no_spam at nospam.com
+ </div><div class="para">
+ Comment: Example for Red Hat RPM Guide
+ </div><div class="para">
+ You selected this USER-ID:
+ </div><div class="para">
+ "Eric Foster-Johnson (Example for Red Hat RPM Guide) <erc at no_spam.com>"
+ </div><div class="para">
+ Change (N)ame, (C)omment, (E)mail or (O)kay/(Q)uit?
+ </div><div class="para">
+ O
+ </div><div class="para">
+ You need a Passphrase to protect your secret key.
+ </div><div class="para">
+ </div><div class="para">
+ Enter passphrase:
+ </div><div class="para">
+ We need to generate a lot of random bytes. It is a good idea to perform
+ </div><div class="para">
+ some other action (type on the keyboard, move the mouse, utilize the
+ </div><div class="para">
+ disks) during the prime generation; this gives the random number
+ </div><div class="para">
+ generator a better chance to gain enough entropy.
+ </div><div class="para">
+ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ </div><div class="para">
+ +++++++++++++++++++++++++++++++++++..+++++..++++++++++>++++++++++........+++++
+ </div><div class="para">
+ gpg: /home2/ericfj/.gnupg/trustdb.gpg: trustdb created
+ </div><div class="para">
+ public and secret key created and signed.
+ </div><div class="para">
+ key marked as ultimately trusted.
+ </div><div class="para">
+ </div><div class="para">
+ pub 1024D/01681C24 2002-11-05 Eric Foster-Johnson (Example for Red Hat RPM
+ </div><div class="para">
+ Guide) <please_no_spam at nospam.com>
+ </div><div class="para">
+ Key fingerprint = 8C14 A2E9 47D1 301B 2153 7CDF BEE5 9C10 0268 1D24
+ </div><div class="para">
+ sub 1024g/1A15D6C8 2002-11-05
+ </div><div class="para">
+ You can choose the default options for most choices. You need to enter a real name, an e-mail address, and a pass phrase. Remember the pass phrase. You will need to enter the pass phrase every time you wish to sign a package.
+ </div><div class="para">
+ Once you have a key, the next step is to set up some RPM macros. There are a number of places you can do this, but using the .rpmmacros file in your home directory is one of the easiest. Edit this file as shown in the following example:
+ </div><div class="para">
+ %_signature gpg
+ </div><div class="para">
+ %_gpg_path /home2/ericfj/.gnupg
+ </div><div class="para">
+ %_gpg_name EricFJ (Eric Key) <erc at no_spam.com>
+ </div><div class="para">
+ %_gpgbin /usr/bin/gpg
+ </div><div class="para">
+ Add lines like these to the $HOME/.rpmmacros file. (Create this file if it does not exist.)
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ <a class="xref" href="ch-customizing-rpm.html">Cap. 20, <em>Customizing RPM Behavior</em></a> covers RPM macros and the $HOME/.rpmmacros file.
+ </div><div class="para">
+ Inside the file, change the %gpg_path macro to the .gnupg directory under your home directory (or the root user’s home directory). Change the %_gpg_name macro to the name you have entered into the gpg program.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch11s04.html"><strong>Înapoi</strong>11.4. Signing Built RPMs</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch11s04s03.html"><strong>Înainte</strong>11.4.3. Signing with the rpmbuild command</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch11s04s03.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch11s04s03.html
new file mode 100644
index 0000000..1204d92
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch11s04s03.html
@@ -0,0 +1,20 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>11.4.3. Signing with the rpmbuild command</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch11s04.html" title="11.4. Signing Built RPMs" /><link rel="prev" href="ch11s04s02.html" title="11.4.2. Configuring a signature" /><link rel="next" href="ch11s04s04.html" title="11.4.4. Signing with the rpm command" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch11s04s02.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch11s04s04.html"><strong>ÃŽn
ainte</strong></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id775419" class="title">Signing with the rpmbuild command</h1></div></div></div><div class="para">
+ The --sign option tells the rpmbuild command to sign the created package. You need to have configured the RPM system for your signature as shown in the previous sections.
+ </div><div class="para">
+ When you then build an RPM, you will be prompted for your pass phrase prior to the package build. For example, the following shows this prompt (and truncates the rest of the rpmbuild messages that follow):
+ </div><div class="para">
+ $ rpmbuild -bb --sign xtoolwait-1.2.spec
+ </div><div class="para">
+ Enter pass phrase:
+ </div><div class="para">
+ Pass phrase is good.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch11s04s02.html"><strong>Înapoi</strong>11.4.2. Configuring a signature</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch11s04s04.html"><strong>Înainte</strong>11.4.4. Signing with the rpm command</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch11s04s04.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch11s04s04.html
new file mode 100644
index 0000000..9432279
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch11s04s04.html
@@ -0,0 +1,18 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>11.4.4. Signing with the rpm command</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch11s04.html" title="11.4. Signing Built RPMs" /><link rel="prev" href="ch11s04s03.html" title="11.4.3. Signing with the rpmbuild command" /><link rel="next" href="ch11s04s05.html" title="11.4.5. Verifying signatures" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch11s04s03.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch11s04s05.html"><strong>Ã
Žnainte</strong></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id775449" class="title">Signing with the rpm command</h1></div></div></div><div class="para">
+ In addition to the --sign option for the rpmbuild command, you can sign packages that have already been created using the rpm command. The --addsign and --resign options generate new signatures and insert them into the passed-in package file. The basic syntax is:
+ </div><div class="para">
+ rpm --addsign package.rpm
+ </div><div class="para">
+ rpm --resign package.rpm
+ </div><div class="para">
+ The --addsign option adds another signature to the RPM. RPM versions prior to 4.1 allowed you to sign a package with multiple keys, which causes problems for automatic verification. Because of that, use the --resign option, which removes the old signature and inserts a new signature into the package.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch11s04s03.html"><strong>Înapoi</strong>11.4.3. Signing with the rpmbuild command</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch11s04s05.html"><strong>Înainte</strong>11.4.5. Verifying signatures</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch11s04s05.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch11s04s05.html
new file mode 100644
index 0000000..e4dccc7
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch11s04s05.html
@@ -0,0 +1,102 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>11.4.5. Verifying signatures</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch11s04.html" title="11.4. Signing Built RPMs" /><link rel="prev" href="ch11s04s04.html" title="11.4.4. Signing with the rpm command" /><link rel="next" href="ch11s04s06.html" title="11.4.6. Importing public keys" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch11s04s04.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch11s04s06.html"><strong>ÃŽnai
nte</strong></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id764181" class="title">Verifying signatures</h1></div></div></div><div class="para">
+ You can verify the RPM signature to ensure that the package has not been modified since it has been signed. Verification also checks that the package is signed by the key that matches the claimed vendor.
+ </div><div class="para">
+ To verify the signature in an RPM, use the -K option to the rpm command. The basic syntax is:
+ </div><div class="para">
+ rpm -K package.rpm
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ This is the rpm command, not the rpmbuild command.
+ </div><div class="para">
+ This command accepts the options shown in Table 12-3 to turn off checking for certain types of signatures.
+ </div><div class="para">
+ Table 12-3 Options to turn off signature checking
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Option
+ </div>
+
+ </td><td>
+ <div class="para">
+ Usage
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nogpg
+ </div>
+
+ </td><td>
+ <div class="para">
+ Don’t check for GPG signatures
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nomd5
+ </div>
+
+ </td><td>
+ <div class="para">
+ Don’t check for MD5 signatures
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nopgp
+ </div>
+
+ </td><td>
+ <div class="para">
+ Don’t check for PGP signatures
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ You can also use the --checksig option, which is the same as -K. When you run this command on a package that has a verifiable key, you will see output like the following:
+ </div><div class="para">
+ # rpm -K xtoolwait-1.3-3.src.rpm
+ </div><div class="para">
+ xtoolwait-1.3-3.src.rpm: (sha1) dsa sha1 md5 gpg OK
+ </div><div class="para">
+ This verifies that the package has not been changed from when it was first signed. It also verifies that the signature matches the public key from the vendor of the package. This goes a long ways toward verifying that the package is indeed legitimate.
+ </div><div class="para">
+ To get more information, add a -v (verbose) option. For example:
+ </div><div class="para">
+ $ rpm -Kv vixie-cron-3.0.1-69.src.rpm
+ </div><div class="para">
+ vixie-cron-3.0.1-69.src.rpm:
+ </div><div class="para">
+ Header V3 DSA signature: OK, key ID db42a60e
+ </div><div class="para">
+ Header SHA1 digest: OK (ecbb244ab022ecd23114bb1d6c9bdeb74f8d9520)
+ </div><div class="para">
+ MD5 digest: OK (fb0a75eca1d526d391c36dc956c23bdd)
+ </div><div class="para">
+ V3 DSA signature: OK, key ID db42a60e
+ </div><div class="para">
+ If you run this command on a package that does not verify, you’ll see an error like the following:
+ </div><div class="para">
+ # rpm --checksig xtoolwait-1.3-3.src.rpm
+ </div><div class="para">
+ xtoolwait-1.3-3.src.rpm: (SHA1) DSA sha1 md5 (GPG) NOT OK (MISSING KEYS: GPG#db42a60e)
+ </div><div class="para">
+ Items that fail are listed in uppercase, such as DSA, while items that succeed appear in lowercase. In this example, the sha1 and md5 tests succeeded, while the DSA test failed. This failure does not necessarily mean that the package is not legitimate. This failure can mean one of three things:
+ </div><div class="para">
+ 1.The package was not properly signed in the first place. That is, it is a legitimate package but the package author did not properly sign the RPM.
+ </div><div class="para">
+ 2.The package has been modified in some way. That is, the package is not legitimate.
+ </div><div class="para">
+ 3.The RPM system has not been initialized with the public key from the package vendor.
+ </div><div class="para">
+ From this error, you don’t yet know whether the package is legitimate or not. The first step, though, is to check that you have imported the proper public key from the package vendor.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch11s04s04.html"><strong>Înapoi</strong>11.4.4. Signing with the rpm command</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch11s04s06.html"><strong>Înainte</strong>11.4.6. Importing public keys</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch11s04s06.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch11s04s06.html
new file mode 100644
index 0000000..e9dee8f
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch11s04s06.html
@@ -0,0 +1,96 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>11.4.6. Importing public keys</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch11s04.html" title="11.4. Signing Built RPMs" /><link rel="prev" href="ch11s04s05.html" title="11.4.5. Verifying signatures" /><link rel="next" href="ch11s04s07.html" title="11.4.7. Getting the Red Hat public key" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch11s04s05.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch11s04s07.html"><strong>ÃŽna
inte</strong></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id671872" class="title">Importing public keys</h1></div></div></div><div class="para">
+ The --import option to the rpm command imports the public key from a given vendor. The format for this key follows:
+ </div><div class="para">
+ The following public key can be used to verify RPM packages built and
+ </div><div class="para">
+ signed by Red Hat, Inc. using `rpm -K' using the GNU GPG package.
+ </div><div class="para">
+ Questions about this key should be sent to security at redhat.com.
+ </div><div class="para">
+ </div><div class="para">
+ -----BEGIN PGP PUBLIC KEY BLOCK-----
+ </div><div class="para">
+ Version: GnuPG v1.0.0 (GNU/Linux)
+ </div><div class="para">
+ Comment: For info see http://www.gnupg.org
+ </div><div class="para">
+ </div><div class="para">
+ mQGiBDfqVEqRBADBKr3Bl6PO8BQ0H8sJoD6p9U7Yyl7pjtZqioviPwXP+DCWd4u8
+ </div><div class="para">
+ HQzcxAZ57m8ssA1LK1Fx93coJhDzM130+p5BG9mYSPShLabR3N1KXdXAYYcowTOM
+ </div><div class="para">
+ GxdwYRGr1Spw8QydLhjVfU1VSl4xt6bupPbFJbyjkg5Z3P7BlUOUJmrx3wCgobNV
+ </div><div class="para">
+ EDGaWYJcch5z5B1of/41G8kEAKii6q7Gu/vhXXnLS6m15oNnPVybyngiw/23dKjS
+ </div><div class="para">
+ ti/PYrrL2J11P2ed0x7zm8v3gLrY0cue1iSba+8glY+p31ZPOr5ogaJw7ZARgoS8
+ </div><div class="para">
+ BwjyRymXQp+8Dete0TELKOL2/itDOPGHW07SsVWOR6cmX4VlRRcWB5KejaNvdrE5
+ </div><div class="para">
+ 4XFtOd04NMgWI63uqZc4zkRa+kwEZtmbz3tHSdWCCE+Y7YVP6IUf/w6YPQFQriWY
+ </div><div class="para">
+ FiA6fD10eB+BlIUqIw80EqjsBKmCwvKkn4jg8kibUgj4/TzQSx77uYokw1EqQ2wk
+ </div><div class="para">
+ OZoaEtcubsNMquuLCMWijYhGBBgRAgAGBQI36lRyAAoJECGRgM3bQqYOhyYAnj7h
+ </div><div class="para">
+ VDY/FJAGqmtZpwVp9IlitW5tAJ4xQApr/jNFZCTksnI+4O1765F7tA==
+ </div><div class="para">
+ =3AHZ
+ </div><div class="para">
+ -----END PGP PUBLIC KEY BLOCK-----
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ For reasons of space, this is not a complete key.
+ </div><div class="para">
+ You need to pass the name of the text file that holds the key to the rpm --import command, as shown following:
+ </div><div class="para">
+ rpm --import key_file
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ You must be logged in as the root user to import keys.
+ </div><div class="para">
+ For example:
+ </div><div class="para">
+ # rpm --checksig xtoolwait-1.3-3.src.rpm
+ </div><div class="para">
+ xtoolwait-1.3-3.src.rpm: (SHA1) DSA sha1 md5 (GPG) NOT OK (MISSING KEYS: GPG#db42a60e)
+ </div><div class="para">
+ </div><div class="para">
+ # rpm --import RPM-GPG-KEY
+ </div><div class="para">
+ </div><div class="para">
+ # rpm --checksig xtoolwait-1.3-3.src.rpm
+ </div><div class="para">
+ xtoolwait-1.3-3.src.rpm: (sha1) dsa sha1 md5 gpg OK
+ </div><div class="para">
+ This example shows an error message when trying to verify the key. Then, after importing the Red Hat public key, the verification works.
+ </div><div class="para">
+ If, after importing this key, you still have problems, you can assume there are problems with the package. Many administrators will refuse to install such packages.
+ </div><div class="para">
+ Warning
+ </div><div class="para">
+ You should be careful with packages that have signatures that do not verify.
+ </div><div class="para">
+ To list the available keys, use a command like the following:
+ </div><div class="para">
+ $ rpm -qa | grep -i gpg
+ </div><div class="para">
+ gpg-pubkey-db42a60e-37ea5438
+ </div><div class="para">
+ This example shows one key installed.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ You can erase this key as if it were a package, using the rpm -e command.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch11s04s05.html"><strong>Înapoi</strong>11.4.5. Verifying signatures</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch11s04s07.html"><strong>Înainte</strong>11.4.7. Getting the Red Hat public key</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch11s04s07.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch11s04s07.html
new file mode 100644
index 0000000..7657fbb
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch11s04s07.html
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>11.4.7. Getting the Red Hat public key</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch11s04.html" title="11.4. Signing Built RPMs" /><link rel="prev" href="ch11s04s06.html" title="11.4.6. Importing public keys" /><link rel="next" href="ch11s05.html" title="11.5. Summary" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch11s04s06.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch11s05.html"><strong>ÃŽnainte</strong></a></li></ul><di
v class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id870898" class="title">Getting the Red Hat public key</h1></div></div></div><div class="para">
+ Strangely enough, the Red Hat public key is not installed when you install Red Hat Linux 8.0. If you need the key, the Red Hat public key is available on the root directory of all Red Hat Linux CD-ROMs, as shown in the following listing:
+ </div><div class="para">
+ $ ls /mnt/cdrom/
+ </div><div class="para">
+ EULA GPL README RedHat/ RPM-GPG-KEY SRPMS/ TRANS.TBL
+ </div><div class="para">
+ Simply copy the RPM-GPG-KEY file to get the public key. Then use the rpm --import command with this key file.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ You can also download this key file from the Red Hat FTP site, at ftp://ftp.redhat.com/pub/redhat/linux/8.0/en/os/i386/.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch11s04s06.html"><strong>Înapoi</strong>11.4.6. Importing public keys</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch11s05.html"><strong>Înainte</strong>11.5. Summary</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch11s05.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch11s05.html
new file mode 100644
index 0000000..5c454eb
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch11s05.html
@@ -0,0 +1,19 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>11.5. Summary</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-rpmbuild.html" title="Cap. 11. Controlling the Build with rpmbuild" /><link rel="prev" href="ch11s04s07.html" title="11.4.7. Getting the Red Hat public key" /><link rel="next" href="ch-extra-packaging-tools.html" title="Cap. 12. Supplemental Packaging Software" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch11s04s07.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a
accesskey="n" href="ch-extra-packaging-tools.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id784940" class="title">Summary</h1></div></div></div><div class="para">
+ This chapter covers options for the rpmbuild command that allow you to achieve a finer grain of control over how the command works. For example, the --short-circuit option tells the rpmbuild command to build just the stages you ask for. This helps when you have problems in one area of building an RPM and don’t want to start over each time you try to see if the problem is solved.
+ </div><div class="para">
+ The rpmbuild command also supports a set of -t options that work like the -b options, except the -t options try to build an RPM from a tar archive of sources (a tarball) instead of an RPM spec file. In this case, the rpmbuild command tries to work without a spec file.
+ </div><div class="para">
+ The --rebuild option tells the rpmbuild command to install a source RPM, build the binary RPM, and clean out the installed source RPM. This provides quite a shortcut for installing binary RPMs from source RPMs.
+ </div><div class="para">
+ RPMs should be signed to provide an extra level of authentication. This system isn’t perfect, but it helps you verify that a package is from the person it says it is from and that the package has not been modified. You can check the signature on RPM packages you download. You can also, with some configuration, sign the packages you create.
+ </div><div class="para">
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch11s04s07.html"><strong>Înapoi</strong>11.4.7. Getting the Red Hat public key</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch-extra-packaging-tools.html"><strong>Înainte</strong>Cap. 12. Supplemental Packaging Software</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch12s02.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch12s02.html
new file mode 100644
index 0000000..49b6cb9
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch12s02.html
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>12.2. Summary</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-extra-packaging-tools.html" title="Cap. 12. Supplemental Packaging Software" /><link rel="prev" href="ch-extra-packaging-tools.html" title="Cap. 12. Supplemental Packaging Software" /><link rel="next" href="ch-packaging-guidelines.html" title="Cap. 13. Packaging Guidelines" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-extra-packaging-tools.html"><strong>ÃŽnapoi</strong><
/a></li><li class="next"><a accesskey="n" href="ch-packaging-guidelines.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id609197" class="title">Summary</h1></div></div></div><div class="para">
+ Creating RPM spec files and maintaining those files can be a difficult chore. A number of tools and add-ons for text editors have sprung up to help make this less of a chore.
+ </div><div class="para">
+ Users of the two most common Linux text editors, vi and emacs, can use add-ons that understand the RPM spec file syntax. These add-ons help reduce errors and, though the use of macros, can speed development of spec files by automating some of the tasks.
+ </div><div class="para">
+ The RUST tool provides a graphical interface for creating spec files that can simplify a lot of the work normally required.
+ </div><div class="para">
+ Once you’ve created an RPM package, you can use the rpmlint command to flag missing, incomplete, or incorrect elements in your RPMs.
+ </div><div class="para">
+ Another tool, called rpm2cpio in its various incarnations, allows you to extract files from an RPM package by taking advantage of the fact that RPM files use the cpio format internally. The rpm2cpio tools can output RPM data into the cpio format directly; you can then pipe the output to the cpio command to extract.
+ </div><div class="para">
+ After all this help in making RPMs and spec files, the next chapter covers a set of best-practice guidelines to help avoid problems when making your RPMs.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-extra-packaging-tools.html"><strong>Înapoi</strong>Cap. 12. Supplemental Packaging Software</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch-packaging-guidelines.html"><strong>Înainte</strong>Cap. 13. Packaging Guidelines</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch13s02.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch13s02.html
new file mode 100644
index 0000000..ca2f346
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch13s02.html
@@ -0,0 +1,68 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>13.2. Following Good Practices</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-packaging-guidelines.html" title="Cap. 13. Packaging Guidelines" /><link rel="prev" href="ch-packaging-guidelines.html" title="Cap. 13. Packaging Guidelines" /><link rel="next" href="ch13s02s02.html" title="13.2.2. Building" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-packaging-guidelines.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch1
3s02s02.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id563425" class="title">Following Good Practices</h1></div></div></div><div class="para">
+ Working through problems is one thing. It’s best, however, to set up an environment to help avoid problems all together. The following sections cover what are considered the best practices for creating RPMs.
+ </div><div class="para">
+ Before you make an RPM, you should plan out what you intend to build and how it will be structured. As you build the RPM, you want to watch out for things that can go wrong, and work from a known clean environment.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id713208" class="title">Preparation</h1></div></div></div><div class="para">
+ Before you start to make an RPM, you need to follow a few steps to ensure you have everything ready.
+ </div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id713220" class="title">Create a Source RPM</h1></div></div></div><div class="para">
+ Having a source RPM allows you to transfer all the sources for a package from one system to another, along with all the instructions coded in the spec file for actually building the binary package. This is very handy for keeping track of software, and it is also very important since you can regenerate the binary RPM at any time from the source RPM. In other words, make the generation of RPMs follow the RPM conventions and fit this into your normal software build process.
+ </div><div class="para">
+ This means that for each RPM you want to build, you really need two: a source and a binary RPM. This isn’t that hard to do, since you can easily make a source RPM into a binary RPM with the rpmbuild command.
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id713241" class="title">Start with Pristine Sources</h1></div></div></div><div class="para">
+ In addition to planning on making a source RPM, you should also start with pristine, unmodified sources for the application you plan to package as an RPM. Starting with pristine sources means you can reproduce the entire process and recreate the RPM from scratch if necessary. (Quality control and configuration management people really appreciate this.)
+ </div><div class="para">
+ The pristine sources should be exactly the sources you got when you downloaded the application, or acquired it in house. This doesn’t mean that you won’t have to modify the sources eventually. For that, you create patches. The key is just to start the process with unmodified sources.
+ </div><div class="para">
+ Some RPMs have nearly 100 patches that the rpmbuild command applies when building the RPM. That is a lot of patches, too many for most applications. Even so, the process is the same. Create a patch or patches for all the changes you need to make. You can easily specify patches in the spec file.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ <a class="xref" href="ch-specfiles.html">Cap. 9, <em>Working with Spec Files</em></a> covers the spec file.
+ </div><div class="para">
+ Keeping your patches separate from the original sources makes it easier to reproduce the RPM from scratch, and makes it easier to integrate a new version of the base software, since your code, in the form of patches, is separated from the base software code.
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id743310" class="title">Decide What Goes In Each Package</h1></div></div></div><div class="para">
+ You don’t have to stuff all your software into one RPM. Instead, you can often simplify your RPM by dividing it into two or three separate (but likely dependent) RPMs.
+ </div><div class="para">
+ For example, the RPM system itself has one RPM for the basic system, rpm, one for developers of the RPM system, rpm-devel, and one for those building RPMs, rpm-build. Yet another RPM provides the Python programming API, rpm-python.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ <a class="xref" href="ch-rpm-programming-python.html">Cap. 16, <em>Programming RPM with Python</em></a> covers Python programming.
+ </div><div class="para">
+ This last division is important. The Python RPM draws in as a dependency the Python system itself. Adding this into, say, the core RPM package would needlessly complicate the dependencies for that package.
+ </div><div class="para">
+ When dividing your software into RPMs, keep two main issues in mind:
+ </div><div class="para">
+ *You want to divide the software into RPMs that fit the model for users of the system.
+ </div><div class="para">
+ *You want to divide the software into RPMs such that the separate RPMs are simpler to create and manage.
+ </div><div class="para">
+ The RPM system follows these guidelines, especially the first. Few users will extend the RPM system itself, which allows RPM team to shed this functionality from the core RPM and contain it in rpm-devel. Those who build RPMs fit into a different category than those who use RPMs since just about everybody needs to use RPMs to install packages, but few users actually build RPMs. Again, the separation works from a user’s perspective.
+ </div><div class="para">
+ You also want your package divisions to make each package easier to specify. You can break particularly tough dependencies into smaller units and simplify things. If the package division doesn’t simplify things, then it may not be a good idea.
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id743372" class="title">Create a Test RPM Database</h1></div></div></div><div class="para">
+ You don’t always have to work with the system RPM database. In fact, while developing RPMs, you probably don’t want to change the system database.
+ </div><div class="para">
+ If you have a test RPM database, you can install your RPMs into this test database. To do so, use the --justdb, --dbpath, --prefix, and --badreloc options. These options allow you to install an RPM into just the database, using a different database, with a different root file location (into a test directory, for example) and handle all files that were not marked for relocation, respectively.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ The --test option when installing also allows you to just test the install, not actually perform it.
+ </div><div class="para">
+ Combined, all these options mean you can use an RPM database just set up for testing and that problems won’t impact your working Linux systems. To make this work, though, you need a test RPM database.
+ </div><div class="para">
+ To be rigorous, you should create the test RPM database from scratch from a known set of packages. This will allow you to exactly verify the behavior of your RPM under different system configurations. This is the best choice since you should install the packages under a known, and non-root, directory hierarchy to avoid having file problems with the working system.
+ </div><div class="para">
+ If you want to cheat, you can copy your real RPM database to another directory and use that. Note that in this case, the file paths in the database will point to the real file locations on disk.
+ </div><div class="para">
+ Regardless of how you create a test database, recreate the database each time you run a test, so that you are sure of a known starting state. Usually this is as simple as copying a master test RPM database into a directory you use for running tests.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-packaging-guidelines.html"><strong>Înapoi</strong>Cap. 13. Packaging Guidelines</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch13s02s02.html"><strong>Înainte</strong>13.2.2. Building</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch13s02s02.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch13s02s02.html
new file mode 100644
index 0000000..ff67c69
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch13s02s02.html
@@ -0,0 +1,32 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>13.2.2. Building</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch13s02.html" title="13.2. Following Good Practices" /><link rel="prev" href="ch13s02.html" title="13.2. Following Good Practices" /><link rel="next" href="ch13s02s02s02.html" title="13.2.2.2. Never Build RPMs as Root" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch13s02.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch13s02s02s02.html"><strong>
ÃŽnainte</strong></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id601156" class="title">Building</h1></div></div></div><div class="para">
+ Building RPMs isn’t as easy as it should be. You’ll often need to try again and again to get the rpmbuild command to create a working RPM. This section covers best practices to follow when performing the actual build of the RPM.
+ </div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id601169" class="title">Use Tools</h1></div></div></div><div class="para">
+ Using tools can help speed up the RPM-making process, as well as give you a head start in learning how RPMs work. RPM-building tools such as the Red Hat plugin for the Eclipse Integrated Development Environment have proven really helpful.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ <a class="xref" href="ch-extra-packaging-tools.html">Cap. 12, <em>Supplemental Packaging Software</em></a> covers RPM-building tools. <a class="xref" href="ch-development-tools.html">Cap. 26, <em>Linux Text Editors and Development Tools</em></a> covers the Eclipse Integrated Development Environment.
+ </div><div class="para">
+ Even though so-called real Linux hackers can make a working virtual memory system with just the cat command, don’t scoff at tools. Your time is too valuable.
+ </div><div class="para">
+ Another useful tool is the gendiff program that comes with the RPM release. The gendiff program makes it easier to create patches by avoiding the need to keep a separate directory of the original sources, The gendiff program also works on all changed files within a directory, making a patch for everything you modified.
+ </div><div class="para">
+ To work with gendiff, you need to first save a backup copy of each file you intend to edit prior to editing. Use a consistent file-name extension for the saved copies of the files, such as .orig, short for original. After you edit some files, run the gendiff command as follows:
+ </div><div class="para">
+ $ gendiff directory_name .saved_extension > patch_name.patch
+ </div><div class="para">
+ For example, if you saved the original files to a .orig extension, you can create a patch in a directory named src (short for sources) with a command like the following:
+ </div><div class="para">
+ $gendiff src .orig > mypatch.patch
+ </div><div class="para">
+ The patch file mypatch.patch will contain all the differences detected for all files in the given directory.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch13s02.html"><strong>Înapoi</strong>13.2. Following Good Practices</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch13s02s02s02.html"><strong>Înainte</strong>13.2.2.2. Never Build RPMs as Root</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch13s02s02s02.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch13s02s02s02.html
new file mode 100644
index 0000000..633a1a4
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch13s02s02s02.html
@@ -0,0 +1,16 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>13.2.2.2. Never Build RPMs as Root</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch13s02s02.html" title="13.2.2. Building" /><link rel="prev" href="ch13s02s02.html" title="13.2.2. Building" /><link rel="next" href="ch13s02s02s03.html" title="13.2.2.3. Create a Digital Signature" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch13s02s02.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch13s02s02s03.html"><strong>ÃŽnainte</strong>
</a></li></ul><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id863926" class="title">Never Build RPMs as Root</h1></div></div></div><div class="para">
+ Never, never, never build RPMs logged in as the root user. Always build your RPMS while logged in as a normal user. This is hard to remember since you must be logged in as root to install an RPM. And you’ll want to test each RPM you create to see if it can install cleanly.
+ </div><div class="para">
+ Even so, never build RPMs logged in as the root user. The RPM spec file has a number of scripts and commands. An error in any of these could cause damage to your system. This includes modifying files, removing files, or copying new contents on top of system files. The root user has permission to perform all these operations.
+ </div><div class="para">
+ To avoid all this, build your RPMs while logged in as a normal user. Any problematic scripts should generate errors.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch13s02s02.html"><strong>Înapoi</strong>13.2.2. Building</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch13s02s02s03.html"><strong>Înainte</strong>13.2.2.3. Create a Digital Signature</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch13s02s02s03.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch13s02s02s03.html
new file mode 100644
index 0000000..deedeb2
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch13s02s02s03.html
@@ -0,0 +1,18 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>13.2.2.3. Create a Digital Signature</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch13s02s02.html" title="13.2.2. Building" /><link rel="prev" href="ch13s02s02s02.html" title="13.2.2.2. Never Build RPMs as Root" /><link rel="next" href="ch13s02s02s04.html" title="13.2.2.4. Copy Smartly" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch13s02s02s02.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch13s02s02s04.html"><strong>ÃŽnaint
e</strong></a></li></ul><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id863952" class="title">Create a Digital Signature</h1></div></div></div><div class="para">
+ RPM 4.1 and later revisions place more importance on signing your packages. The rpm command will, by default, verify signatures on each package it reads.
+ </div><div class="para">
+ Therefore, you should create a digital signature for your packages, if only to meet user expectations. In addition, you should place a copy of your digital signature on your organization’s Web site and public key servers. Having multiple copies in multiple locations helps prevent malicious users from impersonating your keys.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ <a class="xref" href="ch-rpmbuild.html">Cap. 11, <em>Controlling the Build with <code class="command">rpmbuild</code></em></a> covers signing packages.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch13s02s02s02.html"><strong>Înapoi</strong>13.2.2.2. Never Build RPMs as Root</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch13s02s02s04.html"><strong>Înainte</strong>13.2.2.4. Copy Smartly</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch13s02s02s04.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch13s02s02s04.html
new file mode 100644
index 0000000..dca6d34
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch13s02s02s04.html
@@ -0,0 +1,14 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>13.2.2.4. Copy Smartly</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch13s02s02.html" title="13.2.2. Building" /><link rel="prev" href="ch13s02s02s03.html" title="13.2.2.3. Create a Digital Signature" /><link rel="next" href="ch13s02s02s05.html" title="13.2.2.5. Set Up the BuildRoot" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch13s02s02s03.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch13s02s02s05.html"><stro
ng>ÃŽnainte</strong></a></li></ul><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id711486" class="title">Copy Smartly</h1></div></div></div><div class="para">
+ Your Linux distribution probably includes more than one CD-ROM chock full of RPMs. Each of these RPMs has a spec file. You can examine these spec files and see how others choose to build their RPMs. Rather than starting from scratch, you can copy declarations from these spec files into your spec file.
+ </div><div class="para">
+ Not all these packages were made smartly. Some spec files, as you will see, are a large mess. Obviously, don’t copy these. Look for clean spec files with clear directives.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch13s02s02s03.html"><strong>Înapoi</strong>13.2.2.3. Create a Digital Signature</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch13s02s02s05.html"><strong>Înainte</strong>13.2.2.5. Set Up the BuildRoot</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch13s02s02s05.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch13s02s02s05.html
new file mode 100644
index 0000000..bc15e5e
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch13s02s02s05.html
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>13.2.2.5. Set Up the BuildRoot</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch13s02s02.html" title="13.2.2. Building" /><link rel="prev" href="ch13s02s02s04.html" title="13.2.2.4. Copy Smartly" /><link rel="next" href="ch13s02s02s06.html" title="13.2.2.6. Add changelog entries for each new version" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch13s02s02s04.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch13s02s02s06.htm
l"><strong>ÃŽnainte</strong></a></li></ul><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id711506" class="title">Set Up the BuildRoot</h1></div></div></div><div class="para">
+ A BuildRoot directive sets the location where your code will be built. The convention is for you to define a subdirectory beneath the _tmppath directory. For example:
+ </div><div class="para">
+ BuildRoot: %{_tmppath}/%{name}-buildroot
+ </div><div class="para">
+ Once set, rpmbuild defines the RPM_BUILD_ROOT environment variable to the value specified for the BuildRoot.
+ </div><div class="para">
+ With the rpmbuild command, you can use the --buildroot option to specify a directory to use to override the BuildRoot directive in the spec file.
+ </div><div class="para">
+ Using a BuildRoot set to a directory that normal users have write access to allows you to build the package logged in as a normal user. It also helps separate the contents of your package from those of other RPMs.
+ </div><div class="para">
+ Always define a BuildRoot.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch13s02s02s04.html"><strong>Înapoi</strong>13.2.2.4. Copy Smartly</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch13s02s02s06.html"><strong>Înainte</strong>13.2.2.6. Add changelog entries for each new vers...</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch13s02s02s06.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch13s02s02s06.html
new file mode 100644
index 0000000..b95e243
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch13s02s02s06.html
@@ -0,0 +1,14 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>13.2.2.6. Add changelog entries for each new version</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch13s02s02.html" title="13.2.2. Building" /><link rel="prev" href="ch13s02s02s05.html" title="13.2.2.5. Set Up the BuildRoot" /><link rel="next" href="ch13s02s02s07.html" title="13.2.2.7. Define the Group For Your Package" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch13s02s02s05.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch13s02s02s07.html
"><strong>ÃŽnainte</strong></a></li></ul><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id711542" class="title">Add changelog entries for each new version</h1></div></div></div><div class="para">
+ Each time you create a new version in RPM format, you should add an entry to the change log. This allows administrators to get a better idea about what changed from the previous version.
+ </div><div class="para">
+ The change log can help people decide whether or not to upgrade a package. A log entry about a security fix, for example, provides useful information to users.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch13s02s02s05.html"><strong>Înapoi</strong>13.2.2.5. Set Up the BuildRoot</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch13s02s02s07.html"><strong>Înainte</strong>13.2.2.7. Define the Group For Your Package</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch13s02s02s07.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch13s02s02s07.html
new file mode 100644
index 0000000..8011416
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch13s02s02s07.html
@@ -0,0 +1,14 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>13.2.2.7. Define the Group For Your Package</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch13s02s02.html" title="13.2.2. Building" /><link rel="prev" href="ch13s02s02s06.html" title="13.2.2.6. Add changelog entries for each new version" /><link rel="next" href="ch13s03.html" title="13.3. Summary" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch13s02s02s06.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch13s03.html"><strong>ÃŽnainte</
strong></a></li></ul><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id767140" class="title">Define the Group For Your Package</h1></div></div></div><div class="para">
+ Packages are categorized into groups. These group names, while not always the best, appear in the graphical tools such as the Red Hat package manager. If your application is a Linux shell program, then users will expect to find it in the System Environment/Shells group and not the Development/Languages or System Environment/Daemons groups. This is a rather small detail, but it helps users find your package in the huge array of Linux RPMs.
+ </div><div class="para">
+ The official list of RPM groups is located in /usr/share/doc/rpm-4.1/GROUPS for RPM 4.1, and similarly-named directories for other RPM versions.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch13s02s02s06.html"><strong>Înapoi</strong>13.2.2.6. Add changelog entries for each new vers...</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch13s03.html"><strong>Înainte</strong>13.3. Summary</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch13s03.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch13s03.html
new file mode 100644
index 0000000..f08db85
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch13s03.html
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>13.3. Summary</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-packaging-guidelines.html" title="Cap. 13. Packaging Guidelines" /><link rel="prev" href="ch13s02s02s07.html" title="13.2.2.7. Define the Group For Your Package" /><link rel="next" href="ch-scripting.html" title="Cap. 14. Automating RPM with Scripts" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch13s02s02s07.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accessk
ey="n" href="ch-scripting.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id767163" class="title">Summary</h1></div></div></div><div class="para">
+ This chapter covers guidelines for avoiding problems when creating RPMs and following best practices to avoid future problems as well.
+ </div><div class="para">
+ When trying to avoid common problems, your best starting point is the RPM mailing list and newsgroup.
+ </div><div class="para">
+ For best practices, you should start at the very beginning when you are planning what to build into an RPM. Always start with pristine sources and then patch as needed. Your RPM should include the pristine sources and any necessary patches. You should always create a source RPM, so that you can reproduce your RPM anywhere.
+ </div><div class="para">
+ When building RPMs, copy good examples of spec files, as this will get you going far more quickly than any other technique. Use tools to help automate parts of your RPM-building process.
+ </div><div class="para">
+ Never build RPMs when logged in as the root user.
+ </div><div class="para">
+ This chapter ends the section on building RPMs. The next section covers programming to the RPM APIs.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch13s02s02s07.html"><strong>Înapoi</strong>13.2.2.7. Define the Group For Your Package</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch-scripting.html"><strong>Înainte</strong>Cap. 14. Automating RPM with Scripts</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch14s02.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch14s02.html
new file mode 100644
index 0000000..43eacce
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch14s02.html
@@ -0,0 +1,50 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>14.2. Distinguishing Scripting Languages from Programming Languages</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-scripting.html" title="Cap. 14. Automating RPM with Scripts" /><link rel="prev" href="ch-scripting.html" title="Cap. 14. Automating RPM with Scripts" /><link rel="next" href="ch14s03.html" title="14.3. Deciding When to Program and When to Script" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-scripting.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n
" href="ch14s03.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id595512" class="title">Distinguishing Scripting Languages from Programming Languages</h1></div></div></div><div class="para">
+ Experts differ regarding what defines a scripting language and what defines a programming language. It’s clear that languages such as Python blur the old distinction between programming and scripting.
+ </div><div class="para">
+ Originally, scripting was writing small files of commands that invoked other system commands. For example, you could write a script that wraps the Linux file command. Scripts were executed by scripting-language interpreters that parsed each command one at a time and then executed the command.
+ </div><div class="para">
+ Modern scripting languages, such as Tcl, are parsed at runtime and compiled into an internal bytecode format. Once compiled, there is no real difference from a language associated with programming such as Java.
+ </div><div class="para">
+ With a scripting language
+ </div><div class="para">
+ *You generally don’t have to compile the script in advance. The scripting language interpreter may compile the program, often to an internal byte code, but you don’t have to invoke a compiler as a separate step.
+ </div><div class="para">
+ *The facilities of the language generally provide a higher level and more abstract level of interaction with the system than with programming languages. For example, writing socket-based networking code in Tcl requires a lot less code than writing the same code in a programming language such as C. Tcl provides a more abstract view of networking; therefore, your code is a lot simpler.
+ </div><div class="para">
+ *The commands in the scripting language are mostly the commands available to you on the command line. Scripting languages introduce their own commands, too.
+ </div><div class="para">
+ *The language is generally identified as a scripting language. This is more consensus than anything else. Forth is considered an interpreted programming language, while Perl is considered a scripting language.
+ </div><div class="para">
+ Table 15-1 lists some of the more common scripting and programming languages. Note that these are the generally-accepted categories for these languages, not hard and fast rules. This should not stop you, for example, from writing programs in Perl or Python. The distinctions between programming and scripting have blurred in recent years.
+ </div><div class="para">
+ Table 15-1 Common Scripting Languages and Common Programming Languages
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Scripting Languages
+ </div>
+
+ </td><td>
+ <div class="para">
+ Programming Languages
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Bash (Bourne Again shell) Csh (C shell) JavaScript Ksh (Korn shell) Lua MS-DOS batch files Perl Python Ruby Sh (Bourne shell) Tcl
+ </div>
+
+ </td><td>
+ <div class="para">
+ Assembler BASIC C C++ C# FORTRAN Forth Java LISP Modula-2, Modula-3 Oberon Pascal
+ </div>
+
+ </td></tr></tbody></table></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-scripting.html"><strong>Înapoi</strong>Cap. 14. Automating RPM with Scripts</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch14s03.html"><strong>Înainte</strong>14.3. Deciding When to Program and When to Script</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch14s03.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch14s03.html
new file mode 100644
index 0000000..d5e0a6b
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch14s03.html
@@ -0,0 +1,30 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>14.3. Deciding When to Program and When to Script</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-scripting.html" title="Cap. 14. Automating RPM with Scripts" /><link rel="prev" href="ch14s02.html" title="14.2. Distinguishing Scripting Languages from Programming Languages" /><link rel="next" href="ch14s04.html" title="14.4. Shell Scripting Basics" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch14s02.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n
" href="ch14s04.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id575715" class="title">Deciding When to Program and When to Script</h1></div></div></div><div class="para">
+ Just as the distinction between programming and scripting languages has blurred in the last few years, so have the guidelines for when you should program and when you should script. The simplest rule remains, though: Use whatever techniques make you productive. In the end, no one really cares if you call it a program or a script.
+ </div><div class="para">
+ Even so, these guidelines may help:
+ </div><div class="para">
+ *If you have to perform a lot of operations on a lot of RPMs, a program will likely perform much faster than a script that calls the rpm command over and over.
+ </div><div class="para">
+ *If the task is relatively simple, scripting generally works best.
+ </div><div class="para">
+ *If you are more experienced with a particular language, use it.
+ </div><div class="para">
+ *If you need to perform complex operations, perhaps involving transactions, a program is probably the right way to go.
+ </div><div class="para">
+ *In many cases, programming languages work better for creating graphical user interfaces, although Python and Perl offer graphical user interface toolkits, such as Perl/Tk or PyQt.
+ </div><div class="para">
+ There isn’t one right way to do it. Pick what works best for you.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ This chapter covers shell scripting. <a class="xref" href="ch-programming-c.html">Cap. 15, <em>Programming RPM with C</em></a> covers C programming. <a class="xref" href="ch-rpm-programming-python.html">Cap. 16, <em>Programming RPM with Python</em></a> covers Python scripting and programming, and <a class="xref" href="ch-programming-perl.html">Cap. 17, <em>Programming RPM with Perl</em></a> covers Perl scripting.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch14s02.html"><strong>Înapoi</strong>14.2. Distinguishing Scripting Languages from Pro...</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch14s04.html"><strong>Înainte</strong>14.4. Shell Scripting Basics</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch14s04.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch14s04.html
new file mode 100644
index 0000000..8442999
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch14s04.html
@@ -0,0 +1,26 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>14.4. Shell Scripting Basics</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-scripting.html" title="Cap. 14. Automating RPM with Scripts" /><link rel="prev" href="ch14s03.html" title="14.3. Deciding When to Program and When to Script" /><link rel="next" href="ch14s04s02.html" title="14.4.2. Running a script" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch14s03.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch14s04s02.
html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id698707" class="title">Shell Scripting Basics</h1></div></div></div><div class="para">
+ For newcomers to scripting, don’t worry. A script, in this case a shell script, is merely a text file with commands mostly the same as the commands you can type at the keyboard. I’ll point out the differences.
+ </div><div class="para">
+ The following sections quickly introduce scripting for those new to this venture.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id698724" class="title">Writing a script</h1></div></div></div><div class="para">
+ For your first venture, enter the following script into a text file:
+ </div><div class="para">
+ rpm -qa | grep rpm
+ </div><div class="para">
+ This script has a two-part command. The rpm –qa part queries all RPM packages, as covered in <a class="xref" href="ch-using-rpm.html">Cap. 3, <em>Using RPM</em></a> . The grep rpm part finds only packages with rpm in their names. This is a very simple script, but it can serve to show how to work with scripts.
+ </div><div class="para">
+ Save this file under the name listrpmpkgs, since this script lists RPM packages.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ If you’re new to Linux, you’ll notice there’s no program named Notepad.exe. There are, though, a plethora of Linux text editors to choose from. See <a class="xref" href="ch-development-tools.html">Cap. 26, <em>Linux Text Editors and Development Tools</em></a> for a listing of Linux text-editing tools.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch14s03.html"><strong>Înapoi</strong>14.3. Deciding When to Program and When to Script</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch14s04s02.html"><strong>Înainte</strong>14.4.2. Running a script</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch14s04s02.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch14s04s02.html
new file mode 100644
index 0000000..5550547
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch14s04s02.html
@@ -0,0 +1,58 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>14.4.2. Running a script</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch14s04.html" title="14.4. Shell Scripting Basics" /><link rel="prev" href="ch14s04.html" title="14.4. Shell Scripting Basics" /><link rel="next" href="ch14s04s03.html" title="14.4.3. Problems running scripts" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch14s04.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch14s04s03.html"><strong>ÃŽnainte</st
rong></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id766263" class="title">Running a script</h1></div></div></div><div class="para">
+ Once you’ve entered a script, you can run it with the sh command, as shown following, passing the name of your script to the sh command:
+ </div><div class="para">
+ $ sh listrpmpkgs
+ </div><div class="para">
+ librpm404-devel-4.0.4-8x.27
+ </div><div class="para">
+ librpm404-4.0.4-8x.27
+ </div><div class="para">
+ rpm404-python-4.0.4-8x.27
+ </div><div class="para">
+ rpm-4.1-1.06
+ </div><div class="para">
+ rpm-devel-4.1-1.06
+ </div><div class="para">
+ gnorpm-0.9-1
+ </div><div class="para">
+ rpm-python-4.1-1.06
+ </div><div class="para">
+ redhat-rpm-config-8.0-1
+ </div><div class="para">
+ rpm-build-4.1-1.06
+ </div><div class="para">
+ rpmrebuild-1.0-0
+ </div><div class="para">
+ Type the command you have placed in your script at the command line. There should be no difference in the output. For example:
+ </div><div class="para">
+ $ rpm -qa | grep rpm
+ </div><div class="para">
+ librpm404-devel-4.0.4-8x.27
+ </div><div class="para">
+ librpm404-4.0.4-8x.27
+ </div><div class="para">
+ rpm404-python-4.0.4-8x.27
+ </div><div class="para">
+ rpm-4.1-1.06
+ </div><div class="para">
+ rpm-devel-4.1-1.06
+ </div><div class="para">
+ gnorpm-0.9-1
+ </div><div class="para">
+ rpm-python-4.1-1.06
+ </div><div class="para">
+ redhat-rpm-config-8.0-1
+ </div><div class="para">
+ rpm-build-4.1-1.06
+ </div><div class="para">
+ rpmrebuild-1.0-0
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch14s04.html"><strong>Înapoi</strong>14.4. Shell Scripting Basics</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch14s04s03.html"><strong>Înainte</strong>14.4.3. Problems running scripts</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch14s04s03.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch14s04s03.html
new file mode 100644
index 0000000..b2fcb90
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch14s04s03.html
@@ -0,0 +1,16 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>14.4.3. Problems running scripts</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch14s04.html" title="14.4. Shell Scripting Basics" /><link rel="prev" href="ch14s04s02.html" title="14.4.2. Running a script" /><link rel="next" href="ch14s04s04.html" title="14.4.4. Turning a script into a command" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch14s04s02.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch14s04s04.html"><strong>ÃŽn
ainte</strong></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id792368" class="title">Problems running scripts</h1></div></div></div><div class="para">
+ The previous script example required the sh program, a Linux shell, to run the script. You also had to have the script file, such as listrpmpkgs, available. So, if you have stored the file in /home2/bin, to run the script, use the following command:
+ </div><div class="para">
+ $ sh /home2/bin/listrpmpkgs
+ </div><div class="para">
+ That’s not very convenient. Furthermore, you always have to remember where you stored the script file listrpmpkgs. To make this command work better, you can turn your script into a command.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch14s04s02.html"><strong>Înapoi</strong>14.4.2. Running a script</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch14s04s04.html"><strong>Înainte</strong>14.4.4. Turning a script into a command</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch14s04s04.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch14s04s04.html
new file mode 100644
index 0000000..d763d2c
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch14s04s04.html
@@ -0,0 +1,126 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>14.4.4. Turning a script into a command</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch14s04.html" title="14.4. Shell Scripting Basics" /><link rel="prev" href="ch14s04s03.html" title="14.4.3. Problems running scripts" /><link rel="next" href="ch14s04s05.html" title="14.4.5. Passing command-line options to your script" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch14s04s03.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch14s04s
05.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id792391" class="title">Turning a script into a command</h1></div></div></div><div class="para">
+ To turn a script into a command, do three simple things:
+ </div><div class="para">
+ 1.Add a special magic comment to the start of the file so Linux recognizes your text file as a command script.
+ </div><div class="para">
+ 2.Change the permissions on the file so that it is marked as executable.
+ </div><div class="para">
+ 3.Copy the file to a directory located in your command path.
+ </div><div class="para">
+ Shell scripts use a # to indicate a comment, text intended for human readers that can help explain the purpose of the script. By convention, Linux shells use a #! comment in the first line of a script file as a special marker that indicates the file is a shell script. The text that comes after the #! holds the name of the command that should be used to run the script. In almost all cases, that command should be /bin/sh for a shell script.
+ </div><div class="para">
+ So edit the listrpmpkgs script again, and add the magic comment so that the file reads as follows:
+ </div><div class="para">
+ #!/bin/sh
+ </div><div class="para">
+ rpm -qa | grep rpm
+ </div><div class="para">
+ Make sure the #! comment starts at the beginning of the first line.
+ </div><div class="para">
+ Next, change the permissions on the script to mark it as an executable program. Use the chmod command to do this. The chmod command changes the file permissions. To see the permissions, run the ls –l command before changing the permissions:
+ </div><div class="para">
+ $ ls -l listrpmpkgs
+ </div><div class="para">
+ -rw-rw-r-- 1 ericfj ericfj 31 Nov 7 20:02 listrpmpkgs
+ </div><div class="para">
+ The first set of characters, the -rw-rw-r--, indicate the permissions in three batches: permissions for the file owner, the owner’s group of users, and world (everyone else). The rw means read and write, and the r alone means read only for everyone not the owner and not in the owner’s group.
+ </div><div class="para">
+ To add the permission to execute the file for the file owner only, use the following command:
+ </div><div class="para">
+ $ chmod u+x listrpmpkgs
+ </div><div class="para">
+ In this command, the u stands for the user who owns the file (for historical reasons, an o stands for others, not owner). The +x means add the x permission, short for execute permission.
+ </div><div class="para">
+ After running this command, you can see the revised permissions.
+ </div><div class="para">
+ $ ls -l listrpmpkgs
+ </div><div class="para">
+ -rwxrw-r-- 1 ericfj ericfj 31 Nov 7 20:02 listrpmpkgs
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ Use the man chmod command to see more information on this command.
+ </div><div class="para">
+ You now have a command you can run locally. For example:
+ </div><div class="para">
+ $ ./listrpmpkgs
+ </div><div class="para">
+ librpm404-devel-4.0.4-8x.27
+ </div><div class="para">
+ librpm404-4.0.4-8x.27
+ </div><div class="para">
+ rpm404-python-4.0.4-8x.27
+ </div><div class="para">
+ rpm-4.1-1.06
+ </div><div class="para">
+ rpm-devel-4.1-1.06
+ </div><div class="para">
+ gnorpm-0.9-1
+ </div><div class="para">
+ rpm-python-4.1-1.06
+ </div><div class="para">
+ redhat-rpm-config-8.0-1
+ </div><div class="para">
+ rpm-build-4.1-1.06
+ </div><div class="para">
+ rpmrebuild-1.0-0
+ </div><div class="para">
+ The next step is to copy the file to a directory in your system command path. To see which directories are in your path, run the following command:
+ </div><div class="para">
+ $ echo $PATH
+ </div><div class="para">
+ /usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:/home/ericfj/bin:/usr/java/j2sdk1.4.0_01/bin
+ </div><div class="para">
+ Pick one of these directories. The /usr/local/bin directory is a common place to share locally created commands. If this is a personal command for your own use only, a directory under your home directory will be better. In this example, the /home/ericfj/bin is one such directory.
+ </div><div class="para">
+ Copy the script file to a directory in your command path, and you are ready to go.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ If you use the C shell, csh, or the T C shell, tcsh, you need to run the rehash command to tell the shell to look again at the set of commands available in your command path.
+ </div><div class="para">
+ Enter the following command:
+ </div><div class="para">
+ $ listrpmpkgs
+ </div><div class="para">
+ librpm404-devel-4.0.4-8x.27
+ </div><div class="para">
+ librpm404-4.0.4-8x.27
+ </div><div class="para">
+ rpm404-python-4.0.4-8x.27
+ </div><div class="para">
+ rpm-4.1-1.06
+ </div><div class="para">
+ rpm-devel-4.1-1.06
+ </div><div class="para">
+ gnorpm-0.9-1
+ </div><div class="para">
+ rpm-python-4.1-1.06
+ </div><div class="para">
+ redhat-rpm-config-8.0-1
+ </div><div class="para">
+ rpm-build-4.1-1.06
+ </div><div class="para">
+ rpmrebuild-1.0-0
+ </div><div class="para">
+ You have now extended the Linux command set with your own command.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ Windows users may be used to the convention that program file names end in .exe and scripts end in .bat or .cmd. When you run these programs or scripts, you don’t include the extension, exe, .bat, or .cmd. With Linux and UNIX, though, the full file name is important, so if you name your script rpminfo.bat, you must type rpminfo.bat each time you run the script. That’s why most Linux programs and scripts have no filename extension.
+ </div><div class="para">
+ If you want to share your script with others, you should give them the right to execute it as well. You can do that with the following command:
+ </div><div class="para">
+ $ chmod a+x listrpmpkgs
+ </div><div class="para">
+ In this case, the a stands for all users.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch14s04s03.html"><strong>Înapoi</strong>14.4.3. Problems running scripts</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch14s04s05.html"><strong>Înainte</strong>14.4.5. Passing command-line options to your scri...</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch14s04s05.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch14s04s05.html
new file mode 100644
index 0000000..ed8db32
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch14s04s05.html
@@ -0,0 +1,197 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>14.4.5. Passing command-line options to your script</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch14s04.html" title="14.4. Shell Scripting Basics" /><link rel="prev" href="ch14s04s04.html" title="14.4.4. Turning a script into a command" /><link rel="next" href="ch14s05.html" title="14.5. Examining RPM Files" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch14s04s04.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch14s05.html"><strong>ÃŽnainte
</strong></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id850940" class="title">Passing command-line options to your script</h1></div></div></div><div class="para">
+ The listrpmpkgs script used so far isn’t very useful. It performs one command and that’s it. We cannot customize it without writing a new script.
+ </div><div class="para">
+ One way to make a script more flexible is to allow it to use command-line options. Just like the rpm command accepts a zillion options, you can make your scripts accept options.
+ </div><div class="para">
+ Shells define special variables for the command-line options passed to the shell. Table 15-2 lists these options.
+ </div><div class="para">
+ Table 15-2: Shell variables for command-line options
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Variable
+ </div>
+
+ </td><td>
+ <div class="para">
+ Holds
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ $0
+ </div>
+
+ </td><td>
+ <div class="para">
+ The name of the script itself, from the command line
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ $1
+ </div>
+
+ </td><td>
+ <div class="para">
+ The first option
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ $2
+ </div>
+
+ </td><td>
+ <div class="para">
+ The second option
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ $3
+ </div>
+
+ </td><td>
+ <div class="para">
+ The third option
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ $4
+ </div>
+
+ </td><td>
+ <div class="para">
+ The fourth option
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ $5
+ </div>
+
+ </td><td>
+ <div class="para">
+ The fifth option
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ $6
+ </div>
+
+ </td><td>
+ <div class="para">
+ The sixth option
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ $7
+ </div>
+
+ </td><td>
+ <div class="para">
+ The seventh option
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ $8
+ </div>
+
+ </td><td>
+ <div class="para">
+ The eighth option
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ $9
+ </div>
+
+ </td><td>
+ <div class="para">
+ The ninth option
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ $*
+ </div>
+
+ </td><td>
+ <div class="para">
+ All command-line options
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ $#
+ </div>
+
+ </td><td>
+ <div class="para">
+ Holds the number of command-line options
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ Note
+ </div><div class="para">
+ Use $#argv in place of $# if you use the C shell to run your scripts.
+ </div><div class="para">
+ You can use these variables to allow the user to pass the text to search for, instead of always searching for rpm. With this addition, your new script, renamed rpmgrep, follows in Listing 15-1:
+ </div><div class="para">
+ Listing 15-1: rpmgrep
+ </div><div class="para">
+ #!/bin/sh
+ </div><div class="para">
+ </div><div class="para">
+ rpm -qa | grep $*
+ </div><div class="para">
+ This script now expects a command-line option that holds the text to search for. Mark this script as an executable; then you can run it as follows:
+ </div><div class="para">
+ $ ./rpmgrep python
+ </div><div class="para">
+ python-devel-2.2.1-17
+ </div><div class="para">
+ gnome-python2-gtkhtml2-1.99.11-8
+ </div><div class="para">
+ gnome-python2-canvas-1.99.11-8
+ </div><div class="para">
+ gnome-python2-1.99.11-8
+ </div><div class="para">
+ rpm404-python-4.0.4-8x.27
+ </div><div class="para">
+ orbit-python-1.99.0-4
+ </div><div class="para">
+ gnome-python2-bonobo-1.99.11-8
+ </div><div class="para">
+ gnome-python2-gconf-1.99.11-8
+ </div><div class="para">
+ libxslt-python-1.0.19-1
+ </div><div class="para">
+ libxml2-python-2.4.23-1
+ </div><div class="para">
+ python-optik-1.3-2
+ </div><div class="para">
+ python-2.2.1-17
+ </div><div class="para">
+ rpm-python-4.1-1.06
+ </div><div class="para">
+ mod_python-3.0.0-10
+ </div><div class="para">
+ python-tools-2.2.1-17
+ </div><div class="para">
+ If you want to make this command available, copy it to a directory in your command path as described in the preceding section.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch14s04s04.html"><strong>Înapoi</strong>14.4.4. Turning a script into a command</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch14s05.html"><strong>Înainte</strong>14.5. Examining RPM Files</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch14s05.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch14s05.html
new file mode 100644
index 0000000..5b7586d
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch14s05.html
@@ -0,0 +1,94 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>14.5. Examining RPM Files</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-scripting.html" title="Cap. 14. Automating RPM with Scripts" /><link rel="prev" href="ch14s04s05.html" title="14.4.5. Passing command-line options to your script" /><link rel="next" href="ch14s06.html" title="14.6. Querying the RPM Database" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch14s04s05.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href=
"ch14s06.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id673183" class="title">Examining RPM Files</h1></div></div></div><div class="para">
+ When you work with a lot of RPM files, you’ll find that you run the same commands over and over again for each new package you get. For example, you may want to see what capabilities a package requires. You can type in the rpm command each time, or write a short shell script with the necessary command-line options. Listing 15-2 shows this script.
+ </div><div class="para">
+ Listing 15-2: rpmdepend
+ </div><div class="para">
+ #!/bin/sh
+ </div><div class="para">
+ </div><div class="para">
+ rpm -qp --requires $*
+ </div><div class="para">
+ This script expects the name of an RPM package file. Run the command as follows:
+ </div><div class="para">
+ $ rpmdepend vim-common-6.1-14.i386.rpm
+ </div><div class="para">
+ rpmlib(PayloadFilesHavePrefix) <= 4.0-1
+ </div><div class="para">
+ rpmlib(CompressedFileNames) <= 3.0.4-1
+ </div><div class="para">
+ /bin/sh
+ </div><div class="para">
+ /usr/bin/awk
+ </div><div class="para">
+ libc.so.6
+ </div><div class="para">
+ libc.so.6(GLIBC_2.0)
+ </div><div class="para">
+ libc.so.6(GLIBC_2.1)
+ </div><div class="para">
+ Another common task I perform involves listing all the files in an RPM along with the descriptive information on the package. This can really help, since so many Linux packages have nondescriptive names such as dia and anaconda.
+ </div><div class="para">
+ Listing 15-3 shows the rpminfo script.
+ </div><div class="para">
+ Listing 15-3: rpminfo
+ </div><div class="para">
+ #!/bin/sh
+ </div><div class="para">
+ </div><div class="para">
+ rpm -qilp $* | less
+ </div><div class="para">
+ This script lists a potentially long set of lines, so the script pipes the output to the less command. For example:
+ </div><div class="para">
+ $ ./rpminfo perl-XML-Dumper-0.4-22.noarch.rpm
+ </div><div class="para">
+ Name : perl-XML-Dumper Relocations: /usr
+ </div><div class="para">
+ Version : 0.4 Vendor: Red Hat, Inc.
+ </div><div class="para">
+ Release : 22 Build Date: Tue 06 Aug 2002 01:53:30 PM CDT
+ </div><div class="para">
+ Install date: (not installed) Build Host: vegeta.devel.redhat.com
+ </div><div class="para">
+ Group : System Environment/Libraries Source RPM: perl-XML-Dumper-0.4-22.src.rpm
+ </div><div class="para">
+ Size : 10015 License: GPL
+ </div><div class="para">
+ Signature : DSA/SHA1, Tue 06 Aug 2002 02:11:39 PM CDT, Key ID fd372689897da07a
+ </div><div class="para">
+ Packager : Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla>
+ </div><div class="para">
+ URL : http://www.cpan.org
+ </div><div class="para">
+ Summary : Perl module for dumping Perl objects from/to XML
+ </div><div class="para">
+ Description :
+ </div><div class="para">
+ XML::Dumper dumps Perl data to XML format. XML::Dumper can also read
+ </div><div class="para">
+ XML data that was previously dumped by the module and convert it back
+ </div><div class="para">
+ to Perl. Perl objects are blessed back to their original packaging;
+ </div><div class="para">
+ if the modules are installed on the system where the perl objects are
+ </div><div class="para">
+ reconstituted from xml, they will behave as expected. Intuitively, if
+ </div><div class="para">
+ the perl objects are converted and reconstituted in the same
+ </div><div class="para">
+ environment, all should be well.
+ </div><div class="para">
+ /usr/lib/perl5/vendor_perl/5.8.0/XML/Dumper.pm
+ </div><div class="para">
+ /usr/share/man/man3/XML::Dumper.3pm.gz
+ </div><div class="para">
+ I use this script so that I know what files a package wants to install.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch14s04s05.html"><strong>Înapoi</strong>14.4.5. Passing command-line options to your scri...</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch14s06.html"><strong>Înainte</strong>14.6. Querying the RPM Database</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch14s06.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch14s06.html
new file mode 100644
index 0000000..dd189e1
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch14s06.html
@@ -0,0 +1,40 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>14.6. Querying the RPM Database</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-scripting.html" title="Cap. 14. Automating RPM with Scripts" /><link rel="prev" href="ch14s05.html" title="14.5. Examining RPM Files" /><link rel="next" href="ch14s06s02.html" title="14.6.2. Reading HTML documentation for a package" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch14s05.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch14s06s02.
html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id701973" class="title">Querying the RPM Database</h1></div></div></div><div class="para">
+ In addition to querying RPM files, you can script the commands you use to query the RPM database. This is most useful for the long commands with query formats, especially if you have a hard time remembering all the formats.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id793185" class="title">Querying for all packages installed at the same time</h1></div></div></div><div class="para">
+ If you want to list all the packages that were installed with the same transaction ID as a particular package, for example, you can use a script like rpmtran, in Listing 15-4.
+ </div><div class="para">
+ Listing 15-4: rpmtran
+ </div><div class="para">
+ #!/bin/sh
+ </div><div class="para">
+ </div><div class="para">
+ tid=`rpm -q --qf "%{INSTALLTID}\n" $*`
+ </div><div class="para">
+ </div><div class="para">
+ rpm -q --tid $tid
+ </div><div class="para">
+ This script uses the query format to get the transaction ID, or tid, for a particular package. It then passes this transaction ID to the rpm command to query for all packages installed with the same transaction ID.
+ </div><div class="para">
+ For example:
+ </div><div class="para">
+ $ ./rpmtran tcl
+ </div><div class="para">
+ itcl-3.2-74
+ </div><div class="para">
+ tclx-8.3-74
+ </div><div class="para">
+ tcl-8.3.3-74
+ </div><div class="para">
+ tix-8.2.0b1-74
+ </div><div class="para">
+ tkinter-2.2.1-17
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch14s05.html"><strong>Înapoi</strong>14.5. Examining RPM Files</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch14s06s02.html"><strong>Înainte</strong>14.6.2. Reading HTML documentation for a package</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch14s06s02.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch14s06s02.html
new file mode 100644
index 0000000..772199a
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch14s06s02.html
@@ -0,0 +1,35 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>14.6.2. Reading HTML documentation for a package</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch14s06.html" title="14.6. Querying the RPM Database" /><link rel="prev" href="ch14s06.html" title="14.6. Querying the RPM Database" /><link rel="next" href="ch14s07.html" title="14.7. Where to Go From Here" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch14s06.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch14s07.html"><strong>ÃŽnainte</strong>
</a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id793255" class="title">Reading HTML documentation for a package</h1></div></div></div><div class="para">
+ You can combine the rpm command with other commands as well. For example, the rpm –qd command lists the documentation files with a package. If this documentation is in HTML format, you can display this documentation in a Web browser such as Mozilla. Furthermore, by convention, the starting page for HTML documentation should be a file named index.html. Listing 15-5 combines all these factors:
+ </div><div class="para">
+ Listing 15-5: rpmmoz
+ </div><div class="para">
+ #!/bin/sh
+ </div><div class="para">
+ </div><div class="para">
+ html_file=`rpm -qd $* | grep index.html | head -n 1 `
+ </div><div class="para">
+ </div><div class="para">
+ echo "Launching Web browser with $html_file"
+ </div><div class="para">
+ </div><div class="para">
+ htmlview $html_file &
+ </div><div class="para">
+ This script searches for the documentation for a given package name, finds the first file named index.html, and launches the Web browser in the background to display this file, using the htmlview command which will likely run mozilla or your configured Web browser. When you run this command, you should see output like the following; then the Web browser should appear:
+ </div><div class="para">
+ $ ./rpmmoz rpm-devel
+ </div><div class="para">
+ Launching Web browser with /usr/share/doc/rpm-devel-4.1/apidocs/html/index.html
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ This script does not check for errors. If there are no files named index.html, the script launches the Web browser anyway. You could fix this by changing the script to validate the html_file variable prior to launching the Web browser.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch14s06.html"><strong>Înapoi</strong>14.6. Querying the RPM Database</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch14s07.html"><strong>Înainte</strong>14.7. Where to Go From Here</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch14s07.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch14s07.html
new file mode 100644
index 0000000..f02442b
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch14s07.html
@@ -0,0 +1,18 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>14.7. Where to Go From Here</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-scripting.html" title="Cap. 14. Automating RPM with Scripts" /><link rel="prev" href="ch14s06s02.html" title="14.6.2. Reading HTML documentation for a package" /><link rel="next" href="ch14s08.html" title="14.8. Summary" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch14s06s02.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch14s08.html"><stron
g>ÃŽnainte</strong></a></li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id586774" class="title">Where to Go From Here</h1></div></div></div><div class="para">
+ This chapter just introduces the basics for shell scripting. There are many more things you can do. The online manual pages for the bash or tcsh commands provide a wealth of reference information on these shells.
+ </div><div class="para">
+ A number of Web sites provide tutorials on bash, including http://pegasus.rutgers.edu/~elflord/unix/bash-tute.html and www.linuxorbit.com/modules.php?op=modload&name=Sections&file=index&req=viewarticle&artid=459. In addition, the Linux Documentation Project at www.tldp.org/guides.html provides a bash scripting guide, along with a number of bash- and shell-related how-to documents at www.tldp.org/HOWTO/HOWTO-INDEX/howtos.html.
+ </div><div class="para">
+ Teach Yourself Linux, by Steve Oualline and Eric Foster-Johnson (John Wiley & Sons, 2000), introduces a number of Linux topics, including text editors and scripting, for those new to Linux. And Graphical Applications with Tcl and Tk (Hungry Minds, Inc., 1997) by Eric Foster-Johnson, covers another scripting language, Tcl/Tk.
+ </div><div class="para">
+ Use your imagination. Any command that you run often or that is hard to type can be scripted. Furthermore, you can write complex scripts that automate some of the more tedious tasks you need to perform.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch14s06s02.html"><strong>Înapoi</strong>14.6.2. Reading HTML documentation for a package</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch14s08.html"><strong>Înainte</strong>14.8. Summary</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch14s08.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch14s08.html
new file mode 100644
index 0000000..19af216
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch14s08.html
@@ -0,0 +1,16 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>14.8. Summary</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-scripting.html" title="Cap. 14. Automating RPM with Scripts" /><link rel="prev" href="ch14s07.html" title="14.7. Where to Go From Here" /><link rel="next" href="ch-programming-c.html" title="Cap. 15. Programming RPM with C" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch14s07.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch-programming-c.htm
l"><strong>ÃŽnainte</strong></a></li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id586807" class="title">Summary</h1></div></div></div><div class="para">
+ Scripting is the art of writing a set of commands into text files to speed up your work. Programming is the art of writing a set of commands into text files, compiling the text files, and getting paid more. Choosing when to program and when to script isn’t always a clear-cut decision, but generally programs are move involved and complex, while scripts are shorter tools that automate your work. This chapter provides just a glimpse of all you can do with scripts and the RPM system.
+ </div><div class="para">
+ Scripts work very well for capturing obscure syntax options for the rpm command, especially the query formats. You can figure out a command once and then save the command as a script to save time in the future.
+ </div><div class="para">
+ Scripts aren’t the best choice for all tasks, though. In many cases, you need to write a program to accomplish your goals. The next chapter delves into the RPM C programming API, rpmlib.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch14s07.html"><strong>Înapoi</strong>14.7. Where to Go From Here</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch-programming-c.html"><strong>Înainte</strong>Cap. 15. Programming RPM with C</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch15s02.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch15s02.html
new file mode 100644
index 0000000..a8bc648
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch15s02.html
@@ -0,0 +1,34 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>15.2. The Power of popt</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-programming-c.html" title="Cap. 15. Programming RPM with C" /><link rel="prev" href="ch-programming-c.html" title="Cap. 15. Programming RPM with C" /><link rel="next" href="ch15s02s02.html" title="15.2.2. Programming with popt" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-programming-c.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch15s02
s02.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id839316" class="title">The Power of popt</h1></div></div></div><div class="para">
+ Popt provides a powerful command-line processing library, allowing the rpm command to handle a variety of options in a very flexible way. You can use popt alone as a library in its own right, or use it combined with the rpm library to handle command-line options like those of the rpm command.
+ </div><div class="para">
+ At its most basic, popt processes the command-line arguments to a C program, traditionally called argc and argv, into an option table that describes and contains all the option values.
+ </div><div class="para">
+ The main advantage popt has over simpler libraries such as getopt lies in the ability to handle complex arguments and to define aliases. The rpm command supports three different behaviors for the –i option, depending on the context (install a package, get information on a package as part of a query, and perform the install stage of a source RPM, as part of rpmbuild).
+ </div><div class="para">
+ The popt library supports both traditional UNIX short options such as –U and the longer options common for GNU programs, especially on Linux, such as --upgrade. For the popt library, you can define both short and long variants for each option. In addition, command-line options may be individual flags, such as –v for verbose, or options that expect one or more data values as arguments, such as –f, which requires a file name.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id839350" class="title">Popt aliases</h1></div></div></div><div class="para">
+ One of the most powerful features of popt is the ability to define aliases. A popt alias allows you to define one command-line option as an alias for a set of options. As its simplest, the rpm command-line options --upgrade and –U refer to the same action. You could define one as an alias for the other.
+ </div><div class="para">
+ With rpm, the file /usr/lib/rpm/rpmpopt-4.1 (for RPM version 4.1) defines over 400 lines of popt aliases to configure the rpm command-line options. For example:
+ </div><div class="para">
+ Rpm alias –requires --qf \
+ </div><div class="para">
+ "[%{REQUIRENAME} %{REQUIREFLAGS:depflags} %{REQUIREVERSION}\n]" \
+ </div><div class="para">
+ --POPTdesc=$"list capabilities required by package(s)"
+ </div><div class="para">
+ This example defines rpm --requires as really a query using the --qf or --queryformat options covered in <a class="xref" href="ch-using-rpm-db.html">Cap. 4, <em>Using the RPM Database</em></a> .
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ See <a class="xref" href="ch-customizing-rpm.html">Cap. 20, <em>Customizing RPM Behavior</em></a> for more on defining popt aliases.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-programming-c.html"><strong>Înapoi</strong>Cap. 15. Programming RPM with C</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch15s02s02.html"><strong>Înainte</strong>15.2.2. Programming with popt</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch15s02s02.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch15s02s02.html
new file mode 100644
index 0000000..bd4e10c
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch15s02s02.html
@@ -0,0 +1,297 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>15.2.2. Programming with popt</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch15s02.html" title="15.2. The Power of popt" /><link rel="prev" href="ch15s02.html" title="15.2. The Power of popt" /><link rel="next" href="ch15s02s02s02.html" title="15.2.2.2. Popt Callbacks" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch15s02.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch15s02s02s02.html"><strong>ÃŽnainte</strong></a></l
i></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id768322" class="title">Programming with popt</h1></div></div></div><div class="para">
+ To use popt in your programs, you need to fill in a table of options and then call poptGetContext. The poptGetContext function parses the command-line options and returns a poptContext, an opaque data type that you need to pass as a parameter to a number of popt functions. The poptContext holds the state of your command-line processing. This allows you to call the popt library with multiple sets of arguments. Each set will have an associate poptContext to keep all the data separate.
+ </div><div class="para">
+ The basic poptGetContext function signature follows:
+ </div><div class="para">
+ poptContext poptGetContext (const char * name,
+ </div><div class="para">
+ int argc,
+ </div><div class="para">
+ const char ** argv,
+ </div><div class="para">
+ const struct poptOption * options,
+ </div><div class="para">
+ int flags );
+ </div><div class="para">
+ All the popt functions require the popt.h include file:
+ </div><div class="para">
+ #include <popt.h>
+ </div><div class="para">
+ The flags should be a bitmask of any options you require, including those listed in Table 16-5.
+ </div><div class="para">
+ Table 16-5 Flags for poptGetContext
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Flag
+ </div>
+
+ </td><td>
+ <div class="para">
+ Meaning
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ POPT_CONTEXT_NO_EXEC
+ </div>
+
+ </td><td>
+ <div class="para">
+ Ignore executable expansions
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ POPT_CONTEXT_KEEP_FIRST
+ </div>
+
+ </td><td>
+ <div class="para">
+ Treat argv[0], the command name, as an option
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ POPT_CONTEXT_POSIXMEHARDER
+ </div>
+
+ </td><td>
+ <div class="para">
+ Do not allow options to follow arguments
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ When done with a poptContext, you should free it by calling poptFreeContext:
+ </div><div class="para">
+ poptContext poptFreeContext(poptContext context);
+ </div><div class="para">
+ The call to poptFreeContext frees up the memory allocated for the context.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ You can also fill in a poptContext from settings in a file with poptReadConfigFile:
+ </div><div class="para">
+ int poptReadConfigFile(poptContext context,
+ </div><div class="para">
+ const char * file_name);
+ </div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id624360" class="title">Filling in the Options Table</h1></div></div></div><div class="para">
+ You need to pass in a table that defines all the possible options. This table is an array of structures, where each structure defines one option. The format for a single option follows:
+ </div><div class="para">
+ struct poptOption {
+ </div><div class="para">
+ const char * longName;
+ </div><div class="para">
+ char shortName;
+ </div><div class="para">
+ int argInfo;
+ </div><div class="para">
+ void * arg;
+ </div><div class="para">
+ int val;
+ </div><div class="para">
+ const char * descrip;
+ </div><div class="para">
+ const char * argDescrip;
+ </div><div class="para">
+ };
+ </div><div class="para">
+ Going through this structure, the longName defines the long version of the option, such as "upgrade" for --upgrade. The shortName defines the short, one-character option, such as 'U' for an option of -U. You can place a null character, '\0', to specify no short option. With the rpm command, the --rebuilddb option has only a long name and not a short name, for example.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ The longName is not preceded by the double minus sign. Similarly, the shortName is not preceded by the single minus sign.
+ </div><div class="para">
+ The descrip field holds a short description of the option and the argDescrip field holds a description of the types of values it expects, or NULL if this option expects no values.
+ </div><div class="para">
+ The argInfo field holds a flag that tells the popt library how to treat the option. At the very least, you need to define the type of the option. You can also define special processing flags. Table 16-6 lists the argument types in the options table.
+ </div><div class="para">
+ Table 16-6 Popt option table argInfo argument types
+ </div><div class="informaltable"><table border="1"><colgroup><col width="33%" /><col width="33%" /><col width="33%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Type
+ </div>
+
+ </td><td>
+ <div class="para">
+ Value
+ </div>
+
+ </td><td>
+ <div class="para">
+ Meaning
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ POPT_ARG_NONE
+ </div>
+
+ </td><td>
+ <div class="para">
+ 0
+ </div>
+
+ </td><td>
+ <div class="para">
+ No argument data, just the option such as -v
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ POPT_ARG_STRING
+ </div>
+
+ </td><td>
+ <div class="para">
+ 1
+ </div>
+
+ </td><td>
+ <div class="para">
+ arg treated as string
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ POPT_ARG_INT
+ </div>
+
+ </td><td>
+ <div class="para">
+ 2
+ </div>
+
+ </td><td>
+ <div class="para">
+ arg treated as int
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ POPT_ARG_LONG
+ </div>
+
+ </td><td>
+ <div class="para">
+ 3
+ </div>
+
+ </td><td>
+ <div class="para">
+ arg treated as long
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ POPT_ARG_INCLUDE_TABLE
+ </div>
+
+ </td><td>
+ <div class="para">
+ 4
+ </div>
+
+ </td><td>
+ <div class="para">
+ arg points to a table
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ POPT_ARG_CALLBACK
+ </div>
+
+ </td><td>
+ <div class="para">
+ 5
+ </div>
+
+ </td><td>
+ <div class="para">
+ arg points to a callback function
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ POPT_ARG_INTL_DOMAIN
+ </div>
+
+ </td><td>
+ <div class="para">
+ 6
+ </div>
+
+ </td><td>
+ <div class="para">
+ sets translation domain
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ POPT_ARG_VAL
+ </div>
+
+ </td><td>
+ <div class="para">
+ 7
+ </div>
+
+ </td><td>
+ <div class="para">
+ use value of val field for arg
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ POPT_ARG_FLOAT
+ </div>
+
+ </td><td>
+ <div class="para">
+ 8
+ </div>
+
+ </td><td>
+ <div class="para">
+ arg treated as float
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ POPT_ARG_DOUBLE
+ </div>
+
+ </td><td>
+ <div class="para">
+ 9
+ </div>
+
+ </td><td>
+ <div class="para">
+ arg treated as double
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ Use these constants, from the include file popt.h, in place of the actual numbers.
+ </div><div class="para">
+ Depending on the type you define in the argInfo field, popt will interpret the generic pointer field, arg, in different ways. Using a pointer allows the popt library to automatically update your program variables based on the command-line option settings.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ You can pass NULL for the arg field. In this case, the popt library will not set any values for you.
+ </div><div class="para">
+ The POPT_ARG_NONE type indicates that this option has no argument. For example, the -v verbose option has no data. On the other hand, the POPT_ARG_STRING type indicates that the user should provide a string. For example, the -f option to the rpm command is expected to include a string argument, the name of the file to look up.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ If the argInfo argument type is POPT_ARG_NONE, the popt library will set arg to 1 if the option is present on the command line. You should pass a pointer to an int if you want this set for you.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch15s02.html"><strong>Înapoi</strong>15.2. The Power of popt</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch15s02s02s02.html"><strong>Înainte</strong>15.2.2.2. Popt Callbacks</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch15s02s02s02.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch15s02s02s02.html
new file mode 100644
index 0000000..b429e0f
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch15s02s02s02.html
@@ -0,0 +1,38 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>15.2.2.2. Popt Callbacks</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch15s02s02.html" title="15.2.2. Programming with popt" /><link rel="prev" href="ch15s02s02.html" title="15.2.2. Programming with popt" /><link rel="next" href="ch15s02s02s03.html" title="15.2.2.3. Special Option Table Flags" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch15s02s02.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch15s02s02s03.html"
><strong>ÃŽnainte</strong></a></li></ul><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id784382" class="title">Popt Callbacks</h1></div></div></div><div class="para">
+ The POPT_ARG_CALLBACK type indicates that the arg field holds a function pointer to a callback function of the following type:
+ </div><div class="para">
+ typedef void (*poptCallbackType) (poptContext con,
+ </div><div class="para">
+ enum poptCallbackReason reason,
+ </div><div class="para">
+ const struct poptOption * opt,
+ </div><div class="para">
+ const char * arg,
+ </div><div class="para">
+ const void * data);
+ </div><div class="para">
+ The callback reason will be one of the following enum values:
+ </div><div class="para">
+ enum poptCallbackReason {
+ </div><div class="para">
+ POPT_CALLBACK_REASON_PRE = 0,
+ </div><div class="para">
+ POPT_CALLBACK_REASON_POST = 1,
+ </div><div class="para">
+ POPT_CALLBACK_REASON_OPTION = 2
+ </div><div class="para">
+ };
+ </div><div class="para">
+ The data field holds the value of the descrip field in the poptOption entry. You can cheat and stuff a pointer to arbitrary data into this field.
+ </div><div class="para">
+ The callback function is most useful if you are using nested option tables. You can place your processing code for the nested options into a callback.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch15s02s02.html"><strong>Înapoi</strong>15.2.2. Programming with popt</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch15s02s02s03.html"><strong>Înainte</strong>15.2.2.3. Special Option Table Flags</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch15s02s02s03.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch15s02s02s03.html
new file mode 100644
index 0000000..c555b64
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch15s02s02s03.html
@@ -0,0 +1,26 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>15.2.2.3. Special Option Table Flags</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch15s02s02.html" title="15.2.2. Programming with popt" /><link rel="prev" href="ch15s02s02s02.html" title="15.2.2.2. Popt Callbacks" /><link rel="next" href="ch15s02s02s04.html" title="15.2.2.4. Magic Options" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch15s02s02s02.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch15s02s02s04.html"><strong>ÃŽn
ainte</strong></a></li></ul><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id680174" class="title">Special Option Table Flags</h1></div></div></div><div class="para">
+ In addition to the types in Table 16-6, you can also define special bit flags that define extra processing information for each option. Combine these bit flags with the type values using a logical OR operation:
+ </div><div class="para">
+ *The POPT_ARGFLAG_ONEDASH flag allows the longName to be used with one or two dashes, such as -upgrade or --upgrade.
+ </div><div class="para">
+ *For bitmask options, the POPT_ARGFLAG_OR, POPT_ARGFLAG_NOR, POPT_ARGFLAG_AND, POPT_ARGFLAG_NAND, and POPT_ARGFLAG_XOR type flags tell the popt library to apply the given operation, OR, NOR, AND, NAND, or XOR, to the value if set. The POPT_ARGFLAG_NOT flag tells the popt library to negate the value first.
+ </div><div class="para">
+ *You can also use the macros POPT_BIT_SET to set a bit and POPT_BIT_CLR to clear a bit.
+ </div><div class="para">
+ *The POPT_ARGFLAG_OPTIONAL flag indicates that the argument value is optional.
+ </div><div class="para">
+ *The POPT_ARGFLAG_DOC_HIDDEN flag tells popt to hide this option when displaying the help documentation. In other words, this is an internal option.
+ </div><div class="para">
+ *The rarely used POPT_ARGFLAG_STRIP flag tells popt to consume an option and ignore it. This option is rarely used.
+ </div><div class="para">
+ *The POPT_ARGFLAG_SHOW_DEFAULT flag tells popt to show the initial value of the argument for this option as a default when displaying a help message.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch15s02s02s02.html"><strong>Înapoi</strong>15.2.2.2. Popt Callbacks</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch15s02s02s04.html"><strong>Înainte</strong>15.2.2.4. Magic Options</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch15s02s02s04.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch15s02s02s04.html
new file mode 100644
index 0000000..ae18761
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch15s02s02s04.html
@@ -0,0 +1,32 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>15.2.2.4. Magic Options</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch15s02s02.html" title="15.2.2. Programming with popt" /><link rel="prev" href="ch15s02s02s03.html" title="15.2.2.3. Special Option Table Flags" /><link rel="next" href="ch15s02s02s05.html" title="15.2.2.5. Parsing the Command-Line Options" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch15s02s02s03.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="
ch15s02s02s05.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id680221" class="title">Magic Options</h1></div></div></div><div class="para">
+ With RPM programs, developers usually round out the option table with three special options: POPT_AUTOALIAS, POPT_AUTOHELP, and POPT_TABLEEND. The POPT_AUTOALIAS option sets up a table of aliases:
+ </div><div class="para">
+ #define POPT_AUTOALIAS { NULL, '\0', POPT_ARG_INCLUDE_TABLE, poptAliasOptions, \
+ </div><div class="para">
+ 0, "Options implemented via popt alias/exec:", NULL },
+ </div><div class="para">
+ This option refers to the table, poptAliasOptions. You can use the POPT_ARG_INCLUDE_TABLE argInfo type to include another table of options. These options get filled in from popt aliases. In addition, within RPM programs, another table, rpmcliAllPoptTable, holds a set of options common to all RPM programs.
+ </div><div class="para">
+ The POPT_AUTOHELP option supports standard help options. The POPT_AUTOHELP macro adds in automatic support for -?, --help, and --usage options.
+ </div><div class="para">
+ #define POPT_AUTOHELP { NULL, '\0', POPT_ARG_INCLUDE_TABLE, poptHelpOptions, \
+ </div><div class="para">
+ 0, "Help options:", NULL },
+ </div><div class="para">
+ The POPT_TABLEEND option defines an empty option to mark the end of the table. You must include an empty option to end the table, and POPT_TABLEEND makes this easy.
+ </div><div class="para">
+ #define POPT_TABLEEND { NULL, '\0', 0, 0, 0, NULL, NULL }
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ The code in Listing 16-3, in the "Running a Popt Example" section later in this chapter, shows a full option table.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch15s02s02s03.html"><strong>Înapoi</strong>15.2.2.3. Special Option Table Flags</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch15s02s02s05.html"><strong>Înainte</strong>15.2.2.5. Parsing the Command-Line Options</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch15s02s02s05.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch15s02s02s05.html
new file mode 100644
index 0000000..c44b8ab
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch15s02s02s05.html
@@ -0,0 +1,98 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>15.2.2.5. Parsing the Command-Line Options</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch15s02s02.html" title="15.2.2. Programming with popt" /><link rel="prev" href="ch15s02s02s04.html" title="15.2.2.4. Magic Options" /><link rel="next" href="ch15s02s02s06.html" title="15.2.2.6. Walking Through the Command-Line Options" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch15s02s02s04.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch15s
02s02s06.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id723268" class="title">Parsing the Command-Line Options</h1></div></div></div><div class="para">
+ Once you have set up a poptGetContext, you need to iterate over all the command-line parameters. To do this, call poptGetNextOpt:
+ </div><div class="para">
+ int poptGetNextOpt(poptContext context);
+ </div><div class="para">
+ If an error occurs, poptGetNextOpt returns a negative error code. If the context is at the end of the options, poptGetNextOpt returns –1. Table 16-7 lists the error codes:
+ </div><div class="para">
+ Table 16-7 Error codes from poptGetNextOpt
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Code
+ </div>
+
+ </td><td>
+ <div class="para">
+ Meaning
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ POPT_ERROR_NOARG
+ </div>
+
+ </td><td>
+ <div class="para">
+ Option requires an argument, but it is missing
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ POPT_ERROR_BADOPT
+ </div>
+
+ </td><td>
+ <div class="para">
+ Argument could not be parsed
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ POPT_ERROR_OPTSTOODEEP
+ </div>
+
+ </td><td>
+ <div class="para">
+ Aliases are nested too deeply
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ POPT_ERROR_BADQUOTE
+ </div>
+
+ </td><td>
+ <div class="para">
+ Start and end quotation marks don't match
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ POPT_ERROR_BADNUMBER
+ </div>
+
+ </td><td>
+ <div class="para">
+ Argument could not be converted to a number
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ POPT_ERROR_OVERFLOW
+ </div>
+
+ </td><td>
+ <div class="para">
+ Argument number was too big or too small
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ POPT_ERROR_ERRNO
+ </div>
+
+ </td><td>
+ <div class="para">
+ A system call returned an error in errno
+ </div>
+
+ </td></tr></tbody></table></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch15s02s02s04.html"><strong>Înapoi</strong>15.2.2.4. Magic Options</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch15s02s02s06.html"><strong>Înainte</strong>15.2.2.6. Walking Through the Command-Line Options</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch15s02s02s06.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch15s02s02s06.html
new file mode 100644
index 0000000..2fc0b44
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch15s02s02s06.html
@@ -0,0 +1,44 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>15.2.2.6. Walking Through the Command-Line Options</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch15s02s02.html" title="15.2.2. Programming with popt" /><link rel="prev" href="ch15s02s02s05.html" title="15.2.2.5. Parsing the Command-Line Options" /><link rel="next" href="ch15s02s03.html" title="15.2.3. Handling Errors" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch15s02s02s05.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch15s02s03.html"
><strong>ÃŽnainte</strong></a></li></ul><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id716911" class="title">Walking Through the Command-Line Options</h1></div></div></div><div class="para">
+ In normal circumstances, poptGetNextOpt parses all the options and returns –1. If your needs are simple, you can use the pointers to the variables passed in the options table, described previously. If you need some special processing for options not handled by popt, that is, options of type POPT_ARG_NONE, then poptGetNextOpt returns the single-character option.
+ </div><div class="para">
+ In this case, you can call poptGetNextOpt in a while loop. For example:
+ </div><div class="para">
+ while ((option = poptGetNextOpt(context) ) {
+ </div><div class="para">
+ /* Do something... */
+ </div><div class="para">
+ }
+ </div><div class="para">
+ Inside your while loop, you can call poptGetOptArg to get the value of the argument:
+ </div><div class="para">
+ char * poptGetOptArg(poptContext context);
+ </div><div class="para">
+ You can restart the processing of the options by calling poptResetContext:
+ </div><div class="para">
+ void poptResetContext(poptContext context);
+ </div><div class="para">
+ The popt system is just looking for arguments that start with a dash, -. In most command-line applications, you may have a number of extra arguments at the end, such as a list of file names. The popt library doesn’t process these, but can provide them to you.
+ </div><div class="para">
+ Call poptGetArg to return the next extra argument:
+ </div><div class="para">
+ char * poptGetArg(poptContext context);
+ </div><div class="para">
+ Keep calling this function until it returns NULL.
+ </div><div class="para">
+ Call poptPeekArg to look at the next argument but not mark it as being processed:
+ </div><div class="para">
+ char * poptPeekArg(poptContext context);
+ </div><div class="para">
+ Or, you can get the whole list of extra arguments by calling poptGetArgs:
+ </div><div class="para">
+ char ** poptGetArgs(poptContext context);
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch15s02s02s05.html"><strong>Înapoi</strong>15.2.2.5. Parsing the Command-Line Options</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch15s02s03.html"><strong>Înainte</strong>15.2.3. Handling Errors</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch15s02s03.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch15s02s03.html
new file mode 100644
index 0000000..f5b9b66
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch15s02s03.html
@@ -0,0 +1,40 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>15.2.3. Handling Errors</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch15s02.html" title="15.2. The Power of popt" /><link rel="prev" href="ch15s02s02s06.html" title="15.2.2.6. Walking Through the Command-Line Options" /><link rel="next" href="ch15s02s04.html" title="15.2.4. Running a popt example" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch15s02s02s06.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch15s02s04
.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id716989" class="title">Handling Errors</h1></div></div></div><div class="para">
+ Inside your while loop processing the command-line arguments, you can call poptBadOption to get the option that was bad, and poptStrerror to look up the error message associated with the error.
+ </div><div class="para">
+ For poptBadOption, you need to pass in the context, and a bitmask of flags. Normally, pass 0 for no flags or POPT_BADOPTION_NOALIAS, which tells popt to return the actual option, not a value defined in an alias. This makes poptBadOption return the option closest to, if not exactly the same as, what the user entered, which makes for better error reporting.
+ </div><div class="para">
+ The poptBadOption function signature follows:
+ </div><div class="para">
+ char * poptBadOption(poptContext context, int flags);
+ </div><div class="para">
+ Pass the error number returned by poptGetOptArg to poptStrerror to get the standard error message for that option:
+ </div><div class="para">
+ const char * poptStrerror(const int error_code);
+ </div><div class="para">
+ You can combine these and print out an error with code like the following:
+ </div><div class="para">
+ fprintf( stderr, "Error with option [%s]\n %s",
+ </div><div class="para">
+ poptBadOption(context, POPT_BADOPTION_NOALIAS),
+ </div><div class="para">
+ poptStrerror(error_code);
+ </div><div class="para">
+ To print out a usage message, call poptPrintUsage:
+ </div><div class="para">
+ void poptPrintUsage(poptContext context,
+ </div><div class="para">
+ FILE *output,
+ </div><div class="para">
+ int flags);
+ </div><div class="para">
+ This function prints out the usage help information, which is a useful function when the user has called a program with incomplete or wrong options.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch15s02s02s06.html"><strong>Înapoi</strong>15.2.2.6. Walking Through the Command-Line Options</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch15s02s04.html"><strong>Înainte</strong>15.2.4. Running a popt example</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch15s02s04.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch15s02s04.html
new file mode 100644
index 0000000..dd1b190
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch15s02s04.html
@@ -0,0 +1,231 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>15.2.4. Running a popt example</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch15s02.html" title="15.2. The Power of popt" /><link rel="prev" href="ch15s02s03.html" title="15.2.3. Handling Errors" /><link rel="next" href="ch15s02s05.html" title="15.2.5. Handling rpm command-line options" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch15s02s03.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch15s02s05.html"><strong>ÃŽnaint
e</strong></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id726371" class="title">Running a popt example</h1></div></div></div><div class="para">
+ Pulling this all together, you can use the popt1.c program, in Listing 16-3, as an example for using popt to process command-line options.
+ </div><div class="para">
+ Listing 16-3: popt1.c
+ </div><div class="para">
+ /* Processes command-line options. */
+ </div><div class="para">
+ </div><div class="para">
+ #include <stdio.h>
+ </div><div class="para">
+ #include <stdlib.h>
+ </div><div class="para">
+ </div><div class="para">
+ #include <popt.h>
+ </div><div class="para">
+ </div><div class="para">
+ /* Data values for the options. */
+ </div><div class="para">
+ static int intVal = 55;
+ </div><div class="para">
+ static int print = 0;
+ </div><div class="para">
+ </div><div class="para">
+ static char* stringVal;
+ </div><div class="para">
+ </div><div class="para">
+ </div><div class="para">
+ void callback(poptContext context,
+ </div><div class="para">
+ enum poptCallbackReason reason,
+ </div><div class="para">
+ const struct poptOption * option,
+ </div><div class="para">
+ const char * arg,
+ </div><div class="para">
+ const void * data)
+ </div><div class="para">
+ {
+ </div><div class="para">
+ switch(reason)
+ </div><div class="para">
+ {
+ </div><div class="para">
+ case POPT_CALLBACK_REASON_PRE:
+ </div><div class="para">
+ printf("\t Callback in pre setting\n"); break;
+ </div><div class="para">
+ case POPT_CALLBACK_REASON_POST:
+ </div><div class="para">
+ printf("\t Callback in post setting\n"); break;
+ </div><div class="para">
+ case POPT_CALLBACK_REASON_OPTION:
+ </div><div class="para">
+ printf("\t Callback in option setting\n"); break;
+ </div><div class="para">
+ }
+ </div><div class="para">
+ }
+ </div><div class="para">
+ </div><div class="para">
+ </div><div class="para">
+ </div><div class="para">
+ /* Set up a table of options. */
+ </div><div class="para">
+ static struct poptOption optionsTable[] = {
+ </div><div class="para">
+ { (const) "int", (char) 'i', POPT_ARG_INT, (void*) &intVal, 0,
+ </div><div class="para">
+ (const) "follow with an integer value", (const) "2, 4, 8, or 16" },
+ </div><div class="para">
+ </div><div class="para">
+ { "callback", '\0', POPT_ARG_CALLBACK|POPT_ARGFLAG_DOC_HIDDEN,
+ </div><div class="para">
+ &callback, 0, NULL, NULL },
+ </div><div class="para">
+ </div><div class="para">
+ { (const) "file", (char) 'f', POPT_ARG_STRING, (void*) &stringVal, 0,
+ </div><div class="para">
+ (const) "follow with a file name", NULL },
+ </div><div class="para">
+ </div><div class="para">
+ { (const) "print", (char) 'p', POPT_ARG_NONE, &print, 0,
+ </div><div class="para">
+ (const) "send output to the printer", NULL },
+ </div><div class="para">
+ </div><div class="para">
+ POPT_AUTOALIAS
+ </div><div class="para">
+ POPT_AUTOHELP
+ </div><div class="para">
+ POPT_TABLEEND
+ </div><div class="para">
+ };
+ </div><div class="para">
+ </div><div class="para">
+ int main(int argc, char *argv[]) {
+ </div><div class="para">
+ </div><div class="para">
+ poptContext context = poptGetContext(
+ </div><div class="para">
+ (const char*) "popt1",
+ </div><div class="para">
+ argc,
+ </div><div class="para">
+ argv,
+ </div><div class="para">
+ (const struct poptOption* ) &optionsTable,
+ </div><div class="para">
+ 0);
+ </div><div class="para">
+ </div><div class="para">
+ </div><div class="para">
+ int option = poptGetNextOpt(context);
+ </div><div class="para">
+ printf("option = %d\n", option);
+ </div><div class="para">
+ </div><div class="para">
+ /* Print out option values. */
+ </div><div class="para">
+ printf("After processing, options have values:\n");
+ </div><div class="para">
+ </div><div class="para">
+ printf("\t intVal holds %d\n", intVal);
+ </div><div class="para">
+ printf("\t print flag holds %d\n", print);
+ </div><div class="para">
+ printf("\t stringVal holds [%s]\n", stringVal);
+ </div><div class="para">
+ </div><div class="para">
+ poptFreeContext(context);
+ </div><div class="para">
+ </div><div class="para">
+ exit(0);
+ </div><div class="para">
+ }
+ </div><div class="para">
+ This example defines a callback but otherwise uses the simplest case for processing the command-line options. This program lets the popt library simply set the values into the option table. In most cases, you should avoid more complex command-line processing.
+ </div><div class="para">
+ To compile popt programs, you just need the popt library. For example:
+ </div><div class="para">
+ gcc -I/usr/include/rpm -o popt1 popt1.c -lpopt
+ </div><div class="para">
+ When you run this program, try out the different options. For example, when you set all the options, you’ll see output like the following:
+ </div><div class="para">
+ $ ./popt1 -i 42 --print -f filename1
+ </div><div class="para">
+ Callback in option setting
+ </div><div class="para">
+ Callback in option setting
+ </div><div class="para">
+ Callback in post setting
+ </div><div class="para">
+ option = -1
+ </div><div class="para">
+ After processing, options have values:
+ </div><div class="para">
+ intVal holds 42
+ </div><div class="para">
+ print flag holds 1
+ </div><div class="para">
+ stringVal holds [filename1]
+ </div><div class="para">
+ This command used two short options and one long. You can mix and match short and long options, as shown following:
+ </div><div class="para">
+ $ ./popt1 --int 42 -p --file filename1
+ </div><div class="para">
+ Callback in option setting
+ </div><div class="para">
+ Callback in option setting
+ </div><div class="para">
+ Callback in post setting
+ </div><div class="para">
+ option = -1
+ </div><div class="para">
+ After processing, options have values:
+ </div><div class="para">
+ intVal holds 42
+ </div><div class="para">
+ print flag holds 1
+ </div><div class="para">
+ stringVal holds [filename1]
+ </div><div class="para">
+ This example used a short option for print, -p, and long options for the other two options. The popt library also provides handy help and usage messages, using the option table macro POPT_AUTOALIAS. To get a help message, use --help or -?:
+ </div><div class="para">
+ $ ./popt1 --help
+ </div><div class="para">
+ Usage: popt1 [OPTION...]
+ </div><div class="para">
+ -i, --int=2, 4, 8, or 16 follow with an integer value
+ </div><div class="para">
+ -f, --file=STRING follow with a file name
+ </div><div class="para">
+ -p, --print send output to the printer
+ </div><div class="para">
+ </div><div class="para">
+ Options implemented via popt alias/exec:
+ </div><div class="para">
+ </div><div class="para">
+ Help options:
+ </div><div class="para">
+ -?, --help Show this help message
+ </div><div class="para">
+ --usage Display brief usage message
+ </div><div class="para">
+ Notice how the help descriptions from the options table are used.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ With some shells, especially the tcsh shell, you need to wrap a -? In single quotes. For example:
+ </div><div class="para">
+ $ ./popt1 '-?'
+ </div><div class="para">
+ The usage message is shorter, and you also get it for free:
+ </div><div class="para">
+ $ ./popt1 --usage
+ </div><div class="para">
+ Usage: popt1 [-i|--int 2, 4, 8, or 16] [-f|--file STRING] [-p|--print]
+ </div><div class="para">
+ [-?|--help] [--usage]
+ </div><div class="para">
+ All in all, the popt library provides a handy library for processing command-line options and aliases, covered in <a class="xref" href="ch-customizing-rpm.html">Cap. 20, <em>Customizing RPM Behavior</em></a>.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch15s02s03.html"><strong>Înapoi</strong>15.2.3. Handling Errors</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch15s02s05.html"><strong>Înainte</strong>15.2.5. Handling rpm command-line options</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch15s02s05.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch15s02s05.html
new file mode 100644
index 0000000..abcc9d1
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch15s02s05.html
@@ -0,0 +1,50 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>15.2.5. Handling rpm command-line options</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch15s02.html" title="15.2. The Power of popt" /><link rel="prev" href="ch15s02s04.html" title="15.2.4. Running a popt example" /><link rel="next" href="ch15s03.html" title="15.3. Working with RPM Files" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch15s02s04.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch15s03.html"><strong>ÃŽnainte</strong></
a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id754818" class="title">Handling rpm command-line options</h1></div></div></div><div class="para">
+ The RPM C library makes extensive use of popt for processing command-line arguments. Functions that set up the RPM library, such as rpmcliInit, which sets up the RPM command-line environment, require a table of poptOption entries that define the command-line options for your program.
+ </div><div class="para">
+ To create a simple program that handles the standard rpm command-line options, set up the following options table:
+ </div><div class="para">
+ static struct poptOption optionsTable[] = {
+ </div><div class="para">
+ </div><div class="para">
+ { NULL, '\0', POPT_ARG_INCLUDE_TABLE, rpmcliAllPoptTable, 0,
+ </div><div class="para">
+ "Common options for all rpm modes and executables:",
+ </div><div class="para">
+ NULL },
+ </div><div class="para">
+ </div><div class="para">
+ POPT_AUTOALIAS
+ </div><div class="para">
+ POPT_AUTOHELP
+ </div><div class="para">
+ POPT_TABLEEND
+ </div><div class="para">
+ };
+ </div><div class="para">
+ Then, initialize your program with a call to rpmcliInit:
+ </div><div class="para">
+ poptContext rpmcliInit(int argc, char *const argv[],
+ </div><div class="para">
+ struct poptOption * optionsTable);
+ </div><div class="para">
+ When you call rpmcliInit, it will set up all the variables for the standard rpm command-line options.
+ </div><div class="para">
+ For example, to see if the verbose flag is turned on, call rpmIsVerbose:
+ </div><div class="para">
+ int rpmIsVerbose();
+ </div><div class="para">
+ When you are done with a program that called rpmcliInit, call rpmcliFini to clean up the global data:
+ </div><div class="para">
+ poptContext rpmcliFini(poptContext context);
+ </div><div class="para">
+ The call to rpmcliFini returns NULL.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch15s02s04.html"><strong>Înapoi</strong>15.2.4. Running a popt example</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch15s03.html"><strong>Înainte</strong>15.3. Working with RPM Files</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch15s03.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch15s03.html
new file mode 100644
index 0000000..41b0f91
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch15s03.html
@@ -0,0 +1,28 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>15.3. Working with RPM Files</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-programming-c.html" title="Cap. 15. Programming RPM with C" /><link rel="prev" href="ch15s02s05.html" title="15.2.5. Handling rpm command-line options" /><link rel="next" href="ch15s03s02.html" title="15.3.2. Reading the RPM lead and signature" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch15s02s05.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" hr
ef="ch15s03s02.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id489629" class="title">Working with RPM Files</h1></div></div></div><div class="para">
+ The RPM C library provides functions to read RPM files as well as query the RPM database. Going beyond querying, you can perform all the tasks that the rpm and rpmbuild commands do, since both these commands are written in C using the RPM library. That said, some tasks are much easier than other tasks. If you are writing a complex package installation program, or a program that keeps various systems up to date with regards to package versions, you may want to look at the Python RPM API instead of the C RPM library.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ <a class="xref" href="ch-rpm-programming-python.html">Cap. 16, <em>Programming RPM with Python</em></a> covers the Python RPM API.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id489656" class="title">Opening RPM files</h1></div></div></div><div class="para">
+ When working with an RPM file from within a program, the first thing you need to do is open the file. Use Fopen:
+ </div><div class="para">
+ FD_t Fopen(const char * path,
+ </div><div class="para">
+ const char * fmode);
+ </div><div class="para">
+ Fopen works like the standard C function fopen(3).
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ The reason the RPM library wraps the input/output C library functions is to ensure portability to other operating systems. This is a fairly common technique.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch15s02s05.html"><strong>Înapoi</strong>15.2.5. Handling rpm command-line options</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch15s03s02.html"><strong>Înainte</strong>15.3.2. Reading the RPM lead and signature</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch15s03s02.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch15s03s02.html
new file mode 100644
index 0000000..3d9e53a
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch15s03s02.html
@@ -0,0 +1,90 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>15.3.2. Reading the RPM lead and signature</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch15s03.html" title="15.3. Working with RPM Files" /><link rel="prev" href="ch15s03.html" title="15.3. Working with RPM Files" /><link rel="next" href="ch15s03s03.html" title="15.3.3. Reading header information" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch15s03.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch15s03s03.html"><strong>ÃŽnainte</
strong></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id694480" class="title">Reading the RPM lead and signature</h1></div></div></div><div class="para">
+ Once you have opened an RPM file, you can start to read header information, which is the most interesting information to most RPM programs. (You may also want to read the files in the RPM payload, for example.) Before you can start reading the header, though, you must read forward in the RPM file past the lead and signature.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ <a class="xref" href="ch-rpm-overview.html">Cap. 2, <em>RPM Overview</em></a> introduces the lead and signature.
+ </div><div class="para">
+ Even if your programs don’t want to examine the lead or signature, you must read past to position the file offset properly for reading the header information. To read past the lead, call readLead:
+ </div><div class="para">
+ int readLead(FD_t fd, struct rpmlead *lead);
+ </div><div class="para">
+ The readLead function returns 0 on success or 1 on an error. It fills in an rpmlead struct:
+ </div><div class="para">
+ struct rpmlead {
+ </div><div class="para">
+ unsigned char magic[4];
+ </div><div class="para">
+ unsigned char major;
+ </div><div class="para">
+ unsigned char minor;
+ </div><div class="para">
+ short type;
+ </div><div class="para">
+ short archnum;
+ </div><div class="para">
+ char name[66];
+ </div><div class="para">
+ short osnum;
+ </div><div class="para">
+ short signature_type;
+ </div><div class="para">
+ char reserved[16];
+ </div><div class="para">
+ };
+ </div><div class="para">
+ To read past the signature, call rpmReadSignature:
+ </div><div class="para">
+ rpmRC rpmReadSignature(FD_t fd,
+ </div><div class="para">
+ Header * header,
+ </div><div class="para">
+ sigType sig_type);
+ </div><div class="para">
+ The return code is one of the values listed in Table 16-8.
+ </div><div class="para">
+ Table 16-8 Return codes from rpmReadSignature
+ </div><div class="informaltable"><table border="1"><colgroup><col width="100%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Code
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMRC_OK
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMRC_BADMAGIC
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMRC_FAIL
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMRC_BADSIZE
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMRC_SHORTREAD
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ You can do more with the signature than merely reading past it, of course. Look in the online RPM documentation for more on verifying signatures.
+ </div><div class="para">
+ After reading the signature, you can start to read the general header entries.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch15s03.html"><strong>Înapoi</strong>15.3. Working with RPM Files</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch15s03s03.html"><strong>Înainte</strong>15.3.3. Reading header information</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch15s03s03.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch15s03s03.html
new file mode 100644
index 0000000..d5918d6
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch15s03s03.html
@@ -0,0 +1,145 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>15.3.3. Reading header information</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch15s03.html" title="15.3. Working with RPM Files" /><link rel="prev" href="ch15s03s02.html" title="15.3.2. Reading the RPM lead and signature" /><link rel="next" href="ch15s03s04.html" title="15.3.4. A shortcut to header information" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch15s03s02.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch15s03s0
4.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id677133" class="title">Reading header information</h1></div></div></div><div class="para">
+ The header information includes the package name, version, pre- and post-installation scripts, and so on. To read in the RPM header, call headerRead. If successful, headerRead returns a Header object. You can then read data values from the Header.
+ </div><div class="para">
+ Header headerRead(FD_t fd,
+ </div><div class="para">
+ enum hMagic magicp);
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ When working with the RPM database, you will also use Header objects.
+ </div><div class="para">
+ The trickiest thing about calling headerRead is that you must pass a special magic number flag. This value must be HEADER_MAGIC_YES if the header has a set of magic numbers, and HEADER_MAGIC_NO if not. If you guess incorrectly, headerRead will return an error. To get around, this, you can compare the major number in the lead. For example:
+ </div><div class="para">
+ Header header = headerRead(fd, (lead.major >= 3) ?
+ </div><div class="para">
+ HEADER_MAGIC_YES : HEADER_MAGIC_NO);
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ This snippet is one of the gems you'll find when you browse the RPM source code. Use the source.
+ </div><div class="para">
+ To read values from the Header, call headerGetEntry. To call headerGetEntry, you pass in a Header and a tag ID. You get back the type of the tag, a pointer to the tag values, and a count of the number of values stored under this tag.
+ </div><div class="para">
+ int headerGetEntry(Header header,
+ </div><div class="para">
+ int_32 tag,
+ </div><div class="para">
+ hTYP_t type,
+ </div><div class="para">
+ void **pointer,
+ </div><div class="para">
+ hCNT_t data_size);
+ </div><div class="para">
+ The call to headerGetEntry returns a 1 on success, or a 0 on failure. On success, the pointer will point at the retrieved data, with the type parameter set to one of the following enum values:
+ </div><div class="para">
+ enum rpmTagType_e {
+ </div><div class="para">
+ RPM_NULL_TYPE = 0,
+ </div><div class="para">
+ RPM_CHAR_TYPE = 1,
+ </div><div class="para">
+ RPM_INT8_TYPE = 2,
+ </div><div class="para">
+ RPM_INT16_TYPE = 3,
+ </div><div class="para">
+ RPM_INT32_TYPE = 4,
+ </div><div class="para">
+ RPM_STRING_TYPE = 6,
+ </div><div class="para">
+ RPM_BIN_TYPE = 7,
+ </div><div class="para">
+ RPM_STRING_ARRAY_TYPE = 8,
+ </div><div class="para">
+ RPM_I18NSTRING_TYPE
+ </div><div class="para">
+ }
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ If the type is RPM_STRING_ARRAY_TYPE or RPM_BIN_TYPE, you must free the pointer. Call headerFreeData to free the data:
+ </div><div class="para">
+ void* headerFreeData(const void *pointer,
+ </div><div class="para">
+ rpmTagType type);
+ </div><div class="para">
+ You need to pass in the data pointer and the type flag. You can safely call headerFreeData for all types. The function will do nothing if the type is not set up to require freeing.
+ </div><div class="para">
+ When you call headerGetEntry, you must identify the tag you want from the header. This tag is an identifier for the --queryformat tags introduced in <a class="xref" href="ch-using-rpm-db.html">Cap. 4, <em>Using the RPM Database</em></a> . The file rpmlib.h lists the various tags, such as RPMTAG_NAME, RPMTAG_VERSION, and RPMTAG_RELEASE.
+ </div><div class="para">
+ The following function shows how to read a string entry from a Header:
+ </div><div class="para">
+ /* Function to read a string header entry. */
+ </div><div class="para">
+ char* readHeaderString(Header header, int_32 tag_id) {
+ </div><div class="para">
+ </div><div class="para">
+ int_32 type;
+ </div><div class="para">
+ void* pointer;
+ </div><div class="para">
+ int_32 data_size;
+ </div><div class="para">
+ </div><div class="para">
+ int header_status = headerGetEntry(header,
+ </div><div class="para">
+ tag_id,
+ </div><div class="para">
+ &type,
+ </div><div class="para">
+ &pointer,
+ </div><div class="para">
+ &data_size);
+ </div><div class="para">
+ </div><div class="para">
+ if (header_status) {
+ </div><div class="para">
+ </div><div class="para">
+ if (type == RPM_STRING_TYPE) {
+ </div><div class="para">
+ return pointer;
+ </div><div class="para">
+ }
+ </div><div class="para">
+ }
+ </div><div class="para">
+ </div><div class="para">
+ return NULL;
+ </div><div class="para">
+ }
+ </div><div class="para">
+ Pass the Header object and the ID of the tag to read. For example:
+ </div><div class="para">
+ char* name = readHeaderString(header, RPMTAG_NAME);
+ </div><div class="para">
+ char* version = readHeaderString(header, RPMTAG_VERSION);
+ </div><div class="para">
+ char* release = readHeaderString(header, RPMTAG_RELEASE);
+ </div><div class="para">
+ To just get the name, version, and release number, you can call the utility function headerNVR, which has the following function signature:
+ </div><div class="para">
+ int headerNVR(Header header,
+ </div><div class="para">
+ const char **nameptr,
+ </div><div class="para">
+ const char **versionptr,
+ </div><div class="para">
+ const char **releaseptr);
+ </div><div class="para">
+ When you are through with a header, free it by calling headerFree:
+ </div><div class="para">
+ Header headerFree(Header header);
+ </div><div class="para">
+ The call to headerFree returns NULL, so you can use the call to set the original pointer to to NULL to prevent accidental reuse. For example:
+ </div><div class="para">
+ header = headerFree(header);
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch15s03s02.html"><strong>Înapoi</strong>15.3.2. Reading the RPM lead and signature</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch15s03s04.html"><strong>Înainte</strong>15.3.4. A shortcut to header information</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch15s03s04.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch15s03s04.html
new file mode 100644
index 0000000..4327595
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch15s03s04.html
@@ -0,0 +1,28 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>15.3.4. A shortcut to header information</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch15s03.html" title="15.3. Working with RPM Files" /><link rel="prev" href="ch15s03s03.html" title="15.3.3. Reading header information" /><link rel="next" href="ch15s03s05.html" title="15.3.5. Closing RPM files" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch15s03s03.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch15s03s05.html"><strong>ÃŽnaint
e</strong></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id495118" class="title">A shortcut to header information</h1></div></div></div><div class="para">
+ You can read in a Header using the shortcut utility method rpmReadPackageFile:
+ </div><div class="para">
+ int rpmReadPackageFile(rpmts ts,
+ </div><div class="para">
+ FD_t fd,
+ </div><div class="para">
+ const char *filename,
+ </div><div class="para">
+ Header *header);
+ </div><div class="para">
+ You need to pass a transaction set to rpmReadPackageFile and an open file. The filename is just used for reporting errors. On success, rpmReadPackageFile fills in a Header object from the package file. The return value is 0 for success.
+ </div><div class="para">
+ To get the necessary transaction set, you need to create one with rpmtsCreate, covered in the "Programming with the RPM Database" section, following.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ In most cases, you should call rpmReadPackageFile in place of readLead, rpmReadSignature, and headerRead, since rpmReadPackageFile also verifies the package integrity.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch15s03s03.html"><strong>Înapoi</strong>15.3.3. Reading header information</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch15s03s05.html"><strong>Înainte</strong>15.3.5. Closing RPM files</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch15s03s05.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch15s03s05.html
new file mode 100644
index 0000000..901a0ef
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch15s03s05.html
@@ -0,0 +1,20 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>15.3.5. Closing RPM files</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch15s03.html" title="15.3. Working with RPM Files" /><link rel="prev" href="ch15s03s04.html" title="15.3.4. A shortcut to header information" /><link rel="next" href="ch15s04.html" title="15.4. Programming with the RPM Database" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch15s03s04.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch15s04.html"><
strong>ÃŽnainte</strong></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id495165" class="title">Closing RPM files</h1></div></div></div><div class="para">
+ When you’re done with an RPM file, close it with Fclose:
+ </div><div class="para">
+ int Fclose(FD_t fd);
+ </div><div class="para">
+ Fclose acts much like the standard C function fclose(3). The FD_t is an RPM data type that is very similar to a FILE pointer.
+ </div><div class="para">
+ The RPM I/O subsystem, defined with rpmio.h, includes functions that mimic (and in most cases wrap) the ANSI C stdio functions. These include: Fopen, Fclose, Fread, Fwrite, Ferror, Fflush, Fileno, and Fseek.
+ </div><div class="para">
+ These functions wrap the ANSI C stdio functions to add new features. The Fopen function, for example, supports HTTP or FTP URLs in the place of a file name, so long as you append ".ufdio" to the mode.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch15s03s04.html"><strong>Înapoi</strong>15.3.4. A shortcut to header information</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch15s04.html"><strong>Înainte</strong>15.4. Programming with the RPM Database</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch15s04.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch15s04.html
new file mode 100644
index 0000000..1853a70
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch15s04.html
@@ -0,0 +1,136 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>15.4. Programming with the RPM Database</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-programming-c.html" title="Cap. 15. Programming RPM with C" /><link rel="prev" href="ch15s03s05.html" title="15.3.5. Closing RPM files" /><link rel="next" href="ch15s04s02.html" title="15.4.2. Dependency Sets" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch15s03s05.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch15s04s02.html"><strong>ÃŽnain
te</strong></a></li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id495199" class="title">Programming with the RPM Database</h1></div></div></div><div class="para">
+ Many functions in rpmlib require a transaction set. In particular, accessing the rpm database is quite easy using a transaction set.
+ </div><div class="para">
+ Create a transaction set by calling rpmtsCreate:
+ </div><div class="para">
+ rpmts rpmtsCreate(void);
+ </div><div class="para">
+ RPM uses transaction sets to bracket operations on the RPM database. As the RPM API evolves, transaction sets will become more and more important. Transaction sets also help in that the RPM library will automatically open the RPM database as needed.
+ </div><div class="para">
+ When you are done with a transaction set, call rpmtsFree:
+ </div><div class="para">
+ rpmts rpmtsFree(rpmts ts);
+ </div><div class="para">
+ The call to rpmtsFree returns NULL.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id745314" class="title">Database iterators</h1></div></div></div><div class="para">
+ Once you have a transaction set, you can iterate over the installed packages in the RPM database by creating an iterator. To do this, call rpmtsInitIterator:
+ </div><div class="para">
+ rpmdbMatchIterator rpmtsInitIterator(const rpmts ts,
+ </div><div class="para">
+ rpmTag rpmtag,
+ </div><div class="para">
+ const void *keypointer,
+ </div><div class="para">
+ size_t keylen);
+ </div><div class="para">
+ You need to specify which tag to iterate by, which in most cases will be the package name, RPMTAG_NAME, introduced previously With the RPMTAG_NAME tag, you need to pass the name of a package to look for in the keypointer parameter. (The keypointer varies based on the tag you pass.)
+ </div><div class="para">
+ For string data, you can pass 0 for the keylen parameter. For example, this call to rpmtsInitIterator looks for all packages named sendmail.
+ </div><div class="para">
+ rpmdbMatchIterator iter;
+ </div><div class="para">
+ iter = rpmtsInitIterator(ts, RPMTAG_NAME, "sendmail", 0);
+ </div><div class="para">
+ The rpmdbMatchIterator allows you to iterate through a number of packages, in this case, all the packages that match a given name. After calling rpmtsInitIterator, the next step is to call rpmdbNextIterator:
+ </div><div class="para">
+ Header rpmdbNextIterator(rpmdbMatchIterator iter);
+ </div><div class="para">
+ This function returns the next package Header object in the iterator. The Header will be NULL if there are no more packages in the iterator.
+ </div><div class="para">
+ If the Header is not NULL, you can get entries from it, as shown previously. You can use a while loop to go through all the matching packages. For example:
+ </div><div class="para">
+ while ( (installed_header = rpmdbNextIterator(iter) ) != NULL) {
+ </div><div class="para">
+ /* Do something... */
+ </div><div class="para">
+ }
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ In future versions of the RPM library, rpmtsNextIterator, will replace rpmdbNextIterator.
+ </div><div class="para">
+ You do not need to free the Header returned by rpmdbNextIterator. Also, the next call to rpmdbNextIterator will reset the Header.
+ </div><div class="para">
+ You can customize how an iterator works by adding a pattern to the iterator with rpmdbSetIteratorRE:
+ </div><div class="para">
+ int rpmdbSetIteratorRE(rpmdbMatchIterator iter,
+ </div><div class="para">
+ rpmTag tag,
+ </div><div class="para">
+ rpmMireMode mode,
+ </div><div class="para">
+ const char * pattern);
+ </div><div class="para">
+ Calling rpmdbSetIteratorRE modifies the passed-in iterator to use the given pattern as a further test on the given tag. The mode parameter names the type of pattern used, which can be one of those listed in Table 16-9.
+ </div><div class="para">
+ Table 16-9 Types of patterns for rpmdbSetIteratorRE
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Type
+ </div>
+
+ </td><td>
+ <div class="para">
+ Meaning
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMMIRE_DEFAULT
+ </div>
+
+ </td><td>
+ <div class="para">
+ Same as regular expressions but with \., .*, and ^..$ added.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMMIRE_GLOB
+ </div>
+
+ </td><td>
+ <div class="para">
+ Glob-style patterns using fnmatch.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMMIRE_REGEX
+ </div>
+
+ </td><td>
+ <div class="para">
+ Regular expressions using regcomp.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ RPMMIRE_STRCMP
+ </div>
+
+ </td><td>
+ <div class="para">
+ String comparisons using strcmp.
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ For more on these patterns, see the online manual pages for fnmatch(3), glob(7), regcomp(3), regex(7), and strcmp(3).
+ </div><div class="para">
+ Free the iterator when done with rpmdbFreeIterator:
+ </div><div class="para">
+ rpmdbMatchIterator rpmdbFreeIterator(rpmdbMatchIterator iter);
+ </div><div class="para">
+ The call to rpmdbFreeIterator returns NULL.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch15s03s05.html"><strong>Înapoi</strong>15.3.5. Closing RPM files</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch15s04s02.html"><strong>Înainte</strong>15.4.2. Dependency Sets</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch15s04s02.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch15s04s02.html
new file mode 100644
index 0000000..85b61ad
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch15s04s02.html
@@ -0,0 +1,64 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>15.4.2. Dependency Sets</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch15s04.html" title="15.4. Programming with the RPM Database" /><link rel="prev" href="ch15s04.html" title="15.4. Programming with the RPM Database" /><link rel="next" href="ch15s05.html" title="15.5. Comparing an RPM File to an Installed Package" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch15s04.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href=
"ch15s05.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id574662" class="title">Dependency Sets</h1></div></div></div><div class="para">
+ To compare package versions, create a dependency set. The rpm command, for example, uses dependency sets to compare package versions.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ You could compare the version numbers directly, calling headerGetEntry to get the version and release tags, converting these strings to numbers and then comparing, but this would cause problems. The custom comparison is not as exact as the code in this section, especially since many packages have version numbers that are not true numbers, such as 1.12.4, with one too many decimal points. This makes the comparisons harder. In addition, there is more than just the version number to take into account. You need to deal with the Epoch value, as well as the release, too.
+ </div><div class="para">
+ To handle all the complicated logic of comparing versions, you can use the code in this section, or call rpmvercmp. Do not try to compare version numbers with custom code.
+ </div><div class="para">
+ To create a dependency set for a given package Header, call rpmdsThis. Calling rpmdsThis creates a dependency set that holds a triple of the package name, the Epoch/Version/Release information, and the flags.
+ </div><div class="para">
+ rpmds rpmdsThis(Header header,
+ </div><div class="para">
+ rpmTag tagID,
+ </div><div class="para">
+ int_32 Flags);
+ </div><div class="para">
+ For comparing packages, you can pass RPMTAG_REQUIRENAME for the tagID. The actual tagID here is ignored for the version check. What you do need, though, are flags to check whether another package is less than or equal to the Epoch/Version/Release information in this dependency set. For this task, pass the following bit flags:
+ </div><div class="para">
+ (RPMSENSE_EQUAL|RPMSENSE_LESS)
+ </div><div class="para">
+ Once you have a dependency set, you can use the handy function rpmdsNVRMatchesDep to compare the NVR, or Name, Version, Release entries in the header of one package against the data in the dependency set.
+ </div><div class="para">
+ int rpmdsNVRMatchesDep(const Header header,
+ </div><div class="para">
+ const rpmds dependency_set,
+ </div><div class="para">
+ int nopromote);
+ </div><div class="para">
+ After checking the dependencies, rpmdsNVRMatchesDep returns 1 if the dependency overlaps, or 0 otherwise. In terms of comparing packages, 1 means that the package file is as old or older than the installed package, and 0 means that the package already installed is newer. Pass 1 to prevent promoting the Epoch value in the packages during the comparison.
+ </div><div class="para">
+ The actual comparison is controlled by the call that creates the dependency set, especially the flags. Thus, passing flags of (RPMSENSE_EQUAL|RPMSENSE_LESS) to rpmdsThis set up the test as a less than or equal test.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ The RPM C API documentation marks rpmdsNVRMatchesDep as deprecated, to be replaced in the future.
+ </div><div class="para">
+ You can also call rpmVersionCompare to compare the versions of two packages:
+ </div><div class="para">
+ int rpmVersionCompare(Header header1, Header header2);
+ </div><div class="para">
+ The return value is -1 if the header1 represents an older version than header2, 0 if the two headers represent the same version, and 1 if header1 represents a newer version than header2.
+ </div><div class="para">
+ To get the name of the package from a dependency set, call rpmdsN:
+ </div><div class="para">
+ const char* rpmdsN(const rpmds dependency_set);
+ </div><div class="para">
+ You can use rpmdsN to get the name when calling rpmtsInitIterator if you are working with dependency sets when searching the RPM database.
+ </div><div class="para">
+ Free a dependency set when done by calling rpmdsFree:
+ </div><div class="para">
+ rpmds rpmdsFree(rpmds dependency_set);
+ </div><div class="para">
+ As with other free functions, rpmdsFree returns NULL.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch15s04.html"><strong>Înapoi</strong>15.4. Programming with the RPM Database</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch15s05.html"><strong>Înainte</strong>15.5. Comparing an RPM File to an Installed Packa...</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch15s05.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch15s05.html
new file mode 100644
index 0000000..7677069
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch15s05.html
@@ -0,0 +1,541 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>15.5. Comparing an RPM File to an Installed Package</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-programming-c.html" title="Cap. 15. Programming RPM with C" /><link rel="prev" href="ch15s04s02.html" title="15.4.2. Dependency Sets" /><link rel="next" href="ch15s06.html" title="15.6. Where to Go from Here" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch15s04s02.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch15s06.html"><strong>ÃŽnainte</
strong></a></li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id862528" class="title">Comparing an RPM File to an Installed Package</h1></div></div></div><div class="para">
+ You can pull together the RPM file and database discussions, shown previously, to create a number of RPM programs. A useful utility that shows the RPM C library compares a package file against installed packages, reporting whether the package in the RPM file represents a newer or older package than what was already installed.
+ </div><div class="para">
+ Listing 16-4 shows such a program.
+ </div><div class="para">
+ Listing 16-4: vercompare.c
+ </div><div class="para">
+ /* Compares a package file with an installed package,
+ </div><div class="para">
+ telling which one is newer.
+ </div><div class="para">
+ </div><div class="para">
+ Usage:
+ </div><div class="para">
+ vercompare pkg_files+
+ </div><div class="para">
+ </div><div class="para">
+ Compile as
+ </div><div class="para">
+ cc -I/usr/include/rpm -o vercompare vercompare.c -lrpm -lrpmdb -lrpmio -lpopt
+ </div><div class="para">
+ </div><div class="para">
+ */
+ </div><div class="para">
+ #include <stdlib.h>
+ </div><div class="para">
+ </div><div class="para">
+ #include <rpmcli.h>
+ </div><div class="para">
+ #include <rpmdb.h>
+ </div><div class="para">
+ #include <rpmds.h>
+ </div><div class="para">
+ #include <rpmts.h>
+ </div><div class="para">
+ </div><div class="para">
+ /* Set up a table of options using standard RPM options. */
+ </div><div class="para">
+ static struct poptOption optionsTable[] = {
+ </div><div class="para">
+ </div><div class="para">
+ { NULL, '\0', POPT_ARG_INCLUDE_TABLE, rpmcliAllPoptTable, 0,
+ </div><div class="para">
+ "Common options for all rpm modes and executables:",
+ </div><div class="para">
+ NULL },
+ </div><div class="para">
+ </div><div class="para">
+ POPT_AUTOALIAS
+ </div><div class="para">
+ POPT_AUTOHELP
+ </div><div class="para">
+ POPT_TABLEEND
+ </div><div class="para">
+ };
+ </div><div class="para">
+ </div><div class="para">
+ int main(int argc, char * argv[])
+ </div><div class="para">
+ {
+ </div><div class="para">
+ poptContext context;
+ </div><div class="para">
+ const char ** fnp;
+ </div><div class="para">
+ rpmdbMatchIterator iter;
+ </div><div class="para">
+ Header file_header, installed_header;
+ </div><div class="para">
+ rpmts ts;
+ </div><div class="para">
+ rpmds dependency_set;
+ </div><div class="para">
+ FD_t fd;
+ </div><div class="para">
+ rpmRC rpmrc;
+ </div><div class="para">
+ int rc;
+ </div><div class="para">
+ </div><div class="para">
+ context = rpmcliInit(argc, argv, optionsTable);
+ </div><div class="para">
+ if (context == NULL) {
+ </div><div class="para">
+ exit(EXIT_FAILURE);
+ </div><div class="para">
+ }
+ </div><div class="para">
+ </div><div class="para">
+ ts = rpmtsCreate();
+ </div><div class="para">
+ </div><div class="para">
+ </div><div class="para">
+ for (fnp = poptGetArgs(context); fnp && *fnp; fnp++) {
+ </div><div class="para">
+ </div><div class="para">
+ /* Read package header, continuing to next arg on failure. */
+ </div><div class="para">
+ fd = Fopen(*fnp, "r.ufdio");
+ </div><div class="para">
+ </div><div class="para">
+ if (fd == NULL || Ferror(fd)) {
+ </div><div class="para">
+ rpmError(RPMERR_OPEN, "open of %s failed: %s\n", *fnp,
+ </div><div class="para">
+ Fstrerror(fd));
+ </div><div class="para">
+ if (fd) {
+ </div><div class="para">
+ Fclose(fd);
+ </div><div class="para">
+ }
+ </div><div class="para">
+ </div><div class="para">
+ continue;
+ </div><div class="para">
+ }
+ </div><div class="para">
+ </div><div class="para">
+ rpmrc = rpmReadPackageFile(ts, fd, *fnp, &file_header);
+ </div><div class="para">
+ Fclose(fd);
+ </div><div class="para">
+ </div><div class="para">
+ if (rpmrc != RPMRC_OK) {
+ </div><div class="para">
+ rpmError(RPMERR_OPEN, "%s cannot be read\n", *fnp);
+ </div><div class="para">
+ continue;
+ </div><div class="para">
+ }
+ </div><div class="para">
+ </div><div class="para">
+ /* Generate "name <= epoch:version-release" depset for package */
+ </div><div class="para">
+ dependency_set = rpmdsThis(file_header, RPMTAG_REQUIRENAME,
+ </div><div class="para">
+ (RPMSENSE_EQUAL|RPMSENSE_LESS));
+ </div><div class="para">
+ </div><div class="para">
+ rc = -1; /* assume no package is installed. */
+ </div><div class="para">
+ </div><div class="para">
+ /* Search all installed packages with same name. */
+ </div><div class="para">
+ iter = rpmtsInitIterator(ts, RPMTAG_NAME, rpmdsN(dependency_set), 0);
+ </div><div class="para">
+ </div><div class="para">
+ while ((installed_header = rpmdbNextIterator(iter)) != NULL) {
+ </div><div class="para">
+ </div><div class="para">
+ /* Is the installed package newer than the file? */
+ </div><div class="para">
+ rc = rpmdsNVRMatchesDep(installed_header, dependency_set, 1);
+ </div><div class="para">
+ </div><div class="para">
+ switch (rc) {
+ </div><div class="para">
+ case 1:
+ </div><div class="para">
+ if ( rpmIsVerbose() )
+ </div><div class="para">
+ fprintf(stderr, "installed package is older (or same) as %s\n",
+ </div><div class="para">
+ *fnp);
+ </div><div class="para">
+ break;
+ </div><div class="para">
+ case 0:
+ </div><div class="para">
+ if ( rpmIsVerbose() )
+ </div><div class="para">
+ fprintf(stderr, "installed package is newer than %s\n",
+ </div><div class="para">
+ *fnp);
+ </div><div class="para">
+ break;
+ </div><div class="para">
+ }
+ </div><div class="para">
+ }
+ </div><div class="para">
+ </div><div class="para">
+ </div><div class="para">
+ /* Clean up. */
+ </div><div class="para">
+ iter = rpmdbFreeIterator(iter);
+ </div><div class="para">
+ </div><div class="para">
+ dependency_set = rpmdsFree(dependency_set);
+ </div><div class="para">
+ </div><div class="para">
+ if (rc < 0 && rpmIsVerbose() )
+ </div><div class="para">
+ fprintf(stderr, "no package is installed %s\n", *fnp);
+ </div><div class="para">
+ }
+ </div><div class="para">
+ </div><div class="para">
+ ts = rpmtsFree(ts);
+ </div><div class="para">
+ context = rpmcliFini(context);
+ </div><div class="para">
+ </div><div class="para">
+ return rc;
+ </div><div class="para">
+ </div><div class="para">
+ }
+ </div><div class="para">
+ The vercompare.c program shows reading in RPM package files as well as querying the RPM database. It introduces transaction sets, used extensively in the RPM API, and also dependency sets. You can use this program as a guide for making your own RPM programs.
+ </div><div class="para">
+ When you run the vercompare.c program, pass the names of one or more RPM files. The vercompare.c program will extract the package name from the files, and then query the RPM database for matching packages. For each matching package, vercompare.c checks whether the installed package is newer than the RPM file, or at the same version or older. For example, if you have installed version 1.17-1 of the jikes package (a Java compiler), you can compare the installed version against RPM files. If you have a package that has a newer version, you should see output like the following:
+ </div><div class="para">
+ $ ./vercompare -v jikes-1.18-1.i386.rpm
+ </div><div class="para">
+ installed package is older (or same) as jikes-1.18-1.i386.rpm
+ </div><div class="para">
+ Note that the output is relative to the installed package.
+ </div><div class="para">
+ If you compare against a file that has an older version of the package, you will see results like the following:
+ </div><div class="para">
+ $ ./vercompare -v jikes-1.14-1-glibc-2.2.i386.rpm
+ </div><div class="para">
+ installed package is newer than jikes-1.14-1-glibc-2.2.i386.rpm
+ </div><div class="para">
+ And, if you compare to an RPM file that holds the same package, you will see output as follows:
+ </div><div class="para">
+ $ ./vercompare -v jikes-1.17-glibc2.2-1.i386.rpm
+ </div><div class="para">
+ installed package is older (or same) as jikes-1.17-glibc2.2-1.i386.rpm
+ </div><div class="para">
+ You can change this aspect of the test by changing the flags passed to rpmdsThis.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ The vercompare.c program prints out nothing unless there is an error. Instead, it sets the program exit status based on the package version comparison. You can use this with automated tools, such as make, that check the exit status.
+ </div><div class="para">
+ If you want output from the program, pass the –v, verbose, option to the command, as shown in the previous examples.
+ </div><div class="para">
+ The RPM cli or command-line interface functions, such as rpmcliInit, are based on the command-line options expected by the rpm and rpmbuild commands. You can use these functions to provide a high level of abstraction onto the RPM system. For example, to run the query options just like the rpm command, call rpmcliQuery.
+ </div><div class="para">
+ int rpmcliQuery(rpmts transaction_set,
+ </div><div class="para">
+ QVA_t qva,
+ </div><div class="para">
+ const char **argv);
+ </div><div class="para">
+ Set the QVA_t variable to point at the global variable rpmQVKArgs, which is set up from the global option table for the query mode, rpmQueryPoptTable. Pass rpmcliQuery a set of file names or package names. You can get these names in the given format by calling poptGetArgs, introduced previously.
+ </div><div class="para">
+ To support the query options, you need the rpm query entries in your poptOption table. To get these options, add the following entry:
+ </div><div class="para">
+ { NULL, '\0', POPT_ARG_INCLUDE_TABLE, rpmQueryPoptTable, 0,
+ </div><div class="para">
+ "Query options (with -q or --query):",
+ </div><div class="para">
+ NULL },
+ </div><div class="para">
+ With the rpmQueryPoptTable options, you can make a program that works like the rpm --query command using just the following code:
+ </div><div class="para">
+ poptContext context;
+ </div><div class="para">
+ QVA_t qva = &rpmQVKArgs;
+ </div><div class="para">
+ rpmts ts;
+ </div><div class="para">
+ int ec;
+ </div><div class="para">
+ </div><div class="para">
+ </div><div class="para">
+ context = rpmcliInit(argc, argv, optionsTable);
+ </div><div class="para">
+ if (context == NULL) {
+ </div><div class="para">
+ /* Display error and exit... */
+ </div><div class="para">
+ }
+ </div><div class="para">
+ </div><div class="para">
+ ts = rpmtsCreate();
+ </div><div class="para">
+ </div><div class="para">
+ if (qva->qva_mode == 'q') {
+ </div><div class="para">
+ /* Make sure there's something to do. */
+ </div><div class="para">
+ if (qva->qva_source != RPMQV_ALL && !poptPeekArg(context)) {
+ </div><div class="para">
+ fprintf(stderr, "no arguments given for --query");
+ </div><div class="para">
+ exit(EXIT_FAILURE);
+ </div><div class="para">
+ }
+ </div><div class="para">
+ </div><div class="para">
+ ec = rpmcliQuery(ts, qva, (const char **) poptGetArgs(context));
+ </div><div class="para">
+ }
+ </div><div class="para">
+ </div><div class="para">
+ ts = rpmtsFree(ts);
+ </div><div class="para">
+ </div><div class="para">
+ context = rpmcliFini(context);
+ </div><div class="para">
+ This code supports all the query options just like the rpm command. That's both good and bad. If you wanted everything exactly like the rpm command, chances are you could use the rpm command as is. But if you need to add RPM query support into your programs, this is probably the easiest way to do it.
+ </div><div class="para">
+ With a small additional set of code, you can add support for all the --verify options to your program. You need to include the --verify command-line option definitions, which come from the global rpmVerifyPoptTable table:
+ </div><div class="para">
+ /* Add in --verify options. */
+ </div><div class="para">
+ { NULL, '\0', POPT_ARG_INCLUDE_TABLE, rpmVerifyPoptTable, 0,
+ </div><div class="para">
+ "Verify options (with -V or --verify):",
+ </div><div class="para">
+ NULL },
+ </div><div class="para">
+ You can then check for the verify mode, and support the options, with code like the following:
+ </div><div class="para">
+ if (qva->qva_mode == 'V') {
+ </div><div class="para">
+ rpmVerifyFlags verifyFlags = VERIFY_ALL;
+ </div><div class="para">
+ </div><div class="para">
+ /* Verify flags are negated from query flags. */
+ </div><div class="para">
+ verifyFlags &= ~qva->qva_flags;
+ </div><div class="para">
+ qva->qva_flags = (rpmQueryFlags) verifyFlags;
+ </div><div class="para">
+ </div><div class="para">
+ /* Make sure there's something to do. */
+ </div><div class="para">
+ if (qva->qva_source != RPMQV_ALL && !poptPeekArg(context)) {
+ </div><div class="para">
+ fprintf(stderr, "no arguments given for --verify");
+ </div><div class="para">
+ exit(EXIT_FAILURE);
+ </div><div class="para">
+ }
+ </div><div class="para">
+ </div><div class="para">
+ ec = rpmcliVerify(ts, qva, (const char **)
+ </div><div class="para">
+ poptGetArgs(context));
+ </div><div class="para">
+ }
+ </div><div class="para">
+ The workhorse function in this code is rpmcliVerify, a high-level function that performs all the --verify work done by the rpm command.
+ </div><div class="para">
+ int rpmcliVerify(rpmts transaction_set,
+ </div><div class="para">
+ QVA_t qva,
+ </div><div class="para">
+ const char **argv);
+ </div><div class="para">
+ Again, set the QVA_t variable to point at the global variable rpmQVKArgs, which is set up from the global option table for the query mode, rpmQueryPoptTable.
+ </div><div class="para">
+ Putting this all together, Listing 16-5 shows a program that performs the same as the rpm command for the --query and --verify options.
+ </div><div class="para">
+ Listing 16-5: rpmq.c
+ </div><div class="para">
+ /*
+ </div><div class="para">
+ rpm --query and --verify modes in standalone program.
+ </div><div class="para">
+ </div><div class="para">
+ Compile as
+ </div><div class="para">
+ cc -I/usr/include/rpm -o rpmq rpmq.c -lrpm -lrpmdb -lrpmio -lpopt
+ </div><div class="para">
+ </div><div class="para">
+ See option usage by invoking
+ </div><div class="para">
+ ./rpmq --help
+ </div><div class="para">
+ */
+ </div><div class="para">
+ #include <stdlib.h>
+ </div><div class="para">
+ </div><div class="para">
+ #include <rpmcli.h>
+ </div><div class="para">
+ #include <rpmdb.h>
+ </div><div class="para">
+ #include <rpmds.h>
+ </div><div class="para">
+ #include <rpmts.h>
+ </div><div class="para">
+ </div><div class="para">
+ /* Set up a table of options. */
+ </div><div class="para">
+ static struct poptOption optionsTable[] = {
+ </div><div class="para">
+ </div><div class="para">
+ { NULL, '\0', POPT_ARG_INCLUDE_TABLE, rpmcliAllPoptTable, 0,
+ </div><div class="para">
+ "Common options for all rpm modes and executables:",
+ </div><div class="para">
+ NULL },
+ </div><div class="para">
+ </div><div class="para">
+ { NULL, '\0', POPT_ARG_INCLUDE_TABLE, rpmQueryPoptTable, 0,
+ </div><div class="para">
+ "Query options (with -q or --query):",
+ </div><div class="para">
+ NULL },
+ </div><div class="para">
+ </div><div class="para">
+ /* Add in --verify options. */
+ </div><div class="para">
+ { NULL, '\0', POPT_ARG_INCLUDE_TABLE, rpmVerifyPoptTable, 0,
+ </div><div class="para">
+ "Verify options (with -V or --verify):",
+ </div><div class="para">
+ NULL },
+ </div><div class="para">
+ </div><div class="para">
+ POPT_AUTOALIAS
+ </div><div class="para">
+ POPT_AUTOHELP
+ </div><div class="para">
+ POPT_TABLEEND
+ </div><div class="para">
+ };
+ </div><div class="para">
+ </div><div class="para">
+ </div><div class="para">
+ int main(int argc, char * argv[])
+ </div><div class="para">
+ {
+ </div><div class="para">
+ poptContext context;
+ </div><div class="para">
+ QVA_t qva = &rpmQVKArgs;
+ </div><div class="para">
+ rpmts ts;
+ </div><div class="para">
+ int ec;
+ </div><div class="para">
+ </div><div class="para">
+ </div><div class="para">
+ context = rpmcliInit(argc, argv, optionsTable);
+ </div><div class="para">
+ if (context == NULL) {
+ </div><div class="para">
+ poptPrintUsage(context, stderr, 0);
+ </div><div class="para">
+ exit(EXIT_FAILURE);
+ </div><div class="para">
+ }
+ </div><div class="para">
+ </div><div class="para">
+ ts = rpmtsCreate();
+ </div><div class="para">
+ </div><div class="para">
+ /* Check for query mode. */
+ </div><div class="para">
+ if (qva->qva_mode == 'q') {
+ </div><div class="para">
+ /* Make sure there's something to do. */
+ </div><div class="para">
+ if (qva->qva_source != RPMQV_ALL && !poptPeekArg(context)) {
+ </div><div class="para">
+ fprintf(stderr, "no arguments given for --query");
+ </div><div class="para">
+ exit(EXIT_FAILURE);
+ </div><div class="para">
+ }
+ </div><div class="para">
+ </div><div class="para">
+ ec = rpmcliQuery(ts, qva, (const char **) poptGetArgs(context));
+ </div><div class="para">
+ }
+ </div><div class="para">
+ /* Check for verify mode. */
+ </div><div class="para">
+ else if (qva->qva_mode == 'V') {
+ </div><div class="para">
+ rpmVerifyFlags verifyFlags = VERIFY_ALL;
+ </div><div class="para">
+ </div><div class="para">
+ /* Verify flags are negated from query flags. */
+ </div><div class="para">
+ verifyFlags &= ~qva->qva_flags;
+ </div><div class="para">
+ qva->qva_flags = (rpmQueryFlags) verifyFlags;
+ </div><div class="para">
+ </div><div class="para">
+ /* Make sure there's something to do. */
+ </div><div class="para">
+ if (qva->qva_source != RPMQV_ALL && !poptPeekArg(context)) {
+ </div><div class="para">
+ fprintf(stderr, "no arguments given for --verify");
+ </div><div class="para">
+ exit(EXIT_FAILURE);
+ </div><div class="para">
+ }
+ </div><div class="para">
+ </div><div class="para">
+ ec = rpmcliVerify(ts, qva, (const char **) poptGetArgs(context));
+ </div><div class="para">
+ }
+ </div><div class="para">
+ else {
+ </div><div class="para">
+ poptPrintUsage(context, stderr, 0);
+ </div><div class="para">
+ exit(EXIT_FAILURE);
+ </div><div class="para">
+ }
+ </div><div class="para">
+ </div><div class="para">
+ ts = rpmtsFree(ts);
+ </div><div class="para">
+ </div><div class="para">
+ context = rpmcliFini(context);
+ </div><div class="para">
+ </div><div class="para">
+ return ec;
+ </div><div class="para">
+ }
+ </div><div class="para">
+ There is not a lot of code in rpmq.c, as this program is mostly calling the high-level functions for the rpm command-line interface.
+ </div><div class="para">
+ When you run the rpmq program, it performs the same tasks as the rpm command with the --query (or -q) and --verify (or -V) command-line options.
+ </div><div class="para">
+ For example, rpmq supports query formats:
+ </div><div class="para">
+ $ ./rpmq -q --qf "%{NAME} %{INSTALLTID:date}\n" jikes
+ </div><div class="para">
+ jikes Fri 25 Oct 2002 06:49:38 PM CDT
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch15s04s02.html"><strong>Înapoi</strong>15.4.2. Dependency Sets</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch15s06.html"><strong>Înainte</strong>15.6. Where to Go from Here</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch15s06.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch15s06.html
new file mode 100644
index 0000000..8e9b054
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch15s06.html
@@ -0,0 +1,18 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>15.6. Where to Go from Here</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-programming-c.html" title="Cap. 15. Programming RPM with C" /><link rel="prev" href="ch15s05.html" title="15.5. Comparing an RPM File to an Installed Package" /><link rel="next" href="ch15s07.html" title="15.7. Summary" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch15s05.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch15s07.html"><strong>ÃŽ
nainte</strong></a></li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id576724" class="title">Where to Go from Here</h1></div></div></div><div class="para">
+ There is a lot more you can do with the RPM library; you're limited only by your imagination. The best way to get started is to follow the examples in this chapter and then try out some RPM programs on your own. After working with the RPM library for a while, you can delve into other RPM topics.
+ </div><div class="para">
+ The RPM Web site, at www.rpm.org, has most of the available documentation on the RPM system. This site also includes official RPM released software.
+ </div><div class="para">
+ One of the best ways to help find out about how to perform RPM tasks is to look at the source code for the rpm program itself. For this, download the rpm-src source RPM, too. To see the rpm command-line interface functions in action, look especially at tools/rpmcache.c and tools/rpmgraph.c, two relatively short RPM files that show how to take advantage of a number of short cuts. The source code for the Python and Perl bindings can also provide extra hints about the purposes of the RPM API calls.
+ </div><div class="para">
+ The RPM Web site also has a cross-referenced set of HTML pages on the RPM programming API. The pages for version 4.1 of RPM are available at www.rpm.org/rpmapi-4.1/. A good starting page is www.rpm.org/rpmapi-4.1/modules.html, which lists a number of modules within the overall RPM library. This extra level of organization can help you locate the functions you need.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch15s05.html"><strong>Înapoi</strong>15.5. Comparing an RPM File to an Installed Packa...</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch15s07.html"><strong>Înainte</strong>15.7. Summary</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch15s07.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch15s07.html
new file mode 100644
index 0000000..e0d7277
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch15s07.html
@@ -0,0 +1,20 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>15.7. Summary</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-programming-c.html" title="Cap. 15. Programming RPM with C" /><link rel="prev" href="ch15s06.html" title="15.6. Where to Go from Here" /><link rel="next" href="ch-rpm-programming-python.html" title="Cap. 16. Programming RPM with Python" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch15s06.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch-rpm-
programming-python.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id576758" class="title">Summary</h1></div></div></div><div class="para">
+ Everything you can do with RPM you can program in C. That’s because the source code for the entire RPM system is available. In addition, the rpm and rpmbuild programs make use of a published API, called rpmlib, to access RPM functionality. You can use this library yourself.
+ </div><div class="para">
+ The popt library, short for parse options, provides a lot of handy utilities for parsing very complex command-line options. You can use popt inside your own programs, even if you don’t use the rest of the RPM functionality.
+ </div><div class="para">
+ Most RPM programs start up by calling rpmcliInit, which sets up RPM variables for the large set of command-line options supported by most RPM commands.
+ </div><div class="para">
+ Call rpmReadPackageFile to read in the Header object from a package file. You can also get Header objects for the packages installed in a system by initializing an iterator to iterate over a set of packages that meet a certain criteria.
+ </div><div class="para">
+ This chapter covers a fairly low level of access to RPM functionality. The next chapter, on Python programming, shows a higher level of abstraction for working with RPM.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch15s06.html"><strong>Înapoi</strong>15.6. Where to Go from Here</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch-rpm-programming-python.html"><strong>Înainte</strong>Cap. 16. Programming RPM with Python</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch16s02.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch16s02.html
new file mode 100644
index 0000000..2532fe7
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch16s02.html
@@ -0,0 +1,100 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>16.2. The Python API Hierarchy</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-rpm-programming-python.html" title="Cap. 16. Programming RPM with Python" /><link rel="prev" href="ch-rpm-programming-python.html" title="Cap. 16. Programming RPM with Python" /><link rel="next" href="ch16s03.html" title="16.3. Programming with the RPM Database" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-rpm-programming-python.html"><strong>ÃŽnapoi</strong></a></li><li
class="next"><a accesskey="n" href="ch16s03.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id635631" class="title">The Python API Hierarchy</h1></div></div></div><div class="para">
+ The RPM Python API provides a high-level abstraction into RPM functionality divided into logical areas. Table 17-1 lists the main RPM types. In most cases, you need to begin with rpm and create a transaction set.
+ </div><div class="para">
+ Table 17-1 Python types for RPM usage
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Class
+ </div>
+
+ </td><td>
+ <div class="para">
+ Covers
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpm
+ </div>
+
+ </td><td>
+ <div class="para">
+ RPM base module into RPM API
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpmts
+ </div>
+
+ </td><td>
+ <div class="para">
+ Transaction sets
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpmte
+ </div>
+
+ </td><td>
+ <div class="para">
+ Transaction elements, a package in a transaction set
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpmmi
+ </div>
+
+ </td><td>
+ <div class="para">
+ Match iterators, used for querying the RPM database
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Rpmds
+ </div>
+
+ </td><td>
+ <div class="para">
+ Dependency set
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Rpmfi
+ </div>
+
+ </td><td>
+ <div class="para">
+ File into set
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Header
+ </div>
+
+ </td><td>
+ <div class="para">
+ A package header
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ In general, the RPM Python API is well-integrated into the standard Python API. For example, you use the Python os class to read in RPM package files.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ The examples in this chapter use the RPM 4.1 Python API. The API in previous versions is significantly different from the 4.1 version.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-rpm-programming-python.html"><strong>Înapoi</strong>Cap. 16. Programming RPM with Python</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch16s03.html"><strong>Înainte</strong>16.3. Programming with the RPM Database</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch16s03.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch16s03.html
new file mode 100644
index 0000000..5d0efb0
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch16s03.html
@@ -0,0 +1,80 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>16.3. Programming with the RPM Database</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-rpm-programming-python.html" title="Cap. 16. Programming RPM with Python" /><link rel="prev" href="ch16s02.html" title="16.2. The Python API Hierarchy" /><link rel="next" href="ch16s03s02.html" title="16.3.2. Querying the RPM database" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch16s02.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch16s03s
02.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id698781" class="title">Programming with the RPM Database</h1></div></div></div><div class="para">
+ Compared to the RPM C API, discussed in <a class="xref" href="ch-programming-c.html">Cap. 15, <em>Programming RPM with C</em></a> , the Python API is much simpler and requires many fewer programming statements to get your job done.
+ </div><div class="para">
+ Just about every Python RPM script needs a transaction set. Create a transaction set with rpm.TransactionSet:
+ </div><div class="para">
+ import rpm
+ </div><div class="para">
+ </div><div class="para">
+ ts = rpm.TransactionSet()
+ </div><div class="para">
+ The transaction set will automatically open the RPM database if needed.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ The code examples in this chapter follow the Red Hat conventions for naming variables, such as ts for a transaction set. This is to make it easier to read the Python examples in the RPM sources, along with Red Hat installer programs written in Python.
+ </div><div class="para">
+ You will need a transaction set in just about every Python script that accesses RPM functionality.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id821727" class="title">Accessing the RPM database</h1></div></div></div><div class="para">
+ Transaction sets provide a number of methods for working with the RPM database at the database level. Use these methods if you need to interact with the database as a whole, as opposed to accessing individual packages in the database. For example, you can initialize or rebuild the RPM database with these methods. You can also use a handy trick for accessing another RPM database instead of the default system database.
+ </div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id821741" class="title">Setting the Database Location</h1></div></div></div><div class="para">
+ A transaction set will open the RPM database assuming the default location. To specify a different RPM database location, call addMacro, as shown following:
+ </div><div class="para">
+ rpm.addMacro("_dbpath", path_to_rpm_database)
+ </div><div class="para">
+ You can work with more than one RPM database by setting the _dbpath macro, creating a transaction set, and then removing the macro. After doing this, you can create another transaction set for the default RPM database, allowing your script to work with more than one database. For example:
+ </div><div class="para">
+ # Open the rpmdb-redhat database
+ </div><div class="para">
+ rpm.addMacro("_dbpath", "/usr/lib/rpmdb/i386-redhat-linux/redhat")
+ </div><div class="para">
+ solvets = rpm.TransactionSet()
+ </div><div class="para">
+ solvets.openDB()
+ </div><div class="para">
+ rpm.delMacro("_dbpath")
+ </div><div class="para">
+ </div><div class="para">
+ # Open default database
+ </div><div class="para">
+ ts = rpm.TransactionSet()
+ </div><div class="para">
+ This example uses the rpmdb-redhat package, which holds a database of all Red Hat Linux packages. The explicit call to openDB opens the RPM database. In most Python scripts, though, you do not want to call openDB. Instead, a transaction set will open the database as needed.
+ </div><div class="para">
+ The call to delMacro removes the _dbpath macro, allowing the next call to TransactionSet to use the default RPM database.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ Do not call closeDB on a transaction set. This method does indeed close the RPM database, but it also disables the ability to automatically open the RPM database as needed.
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id820140" class="title">Initializing, Rebuilding, and Verifying the Database</h1></div></div></div><div class="para">
+ The transaction set provides an initDB method to initialize a new RPM database. This acts like the rpm --initdb command.
+ </div><div class="para">
+ ts.initDB()
+ </div><div class="para">
+ The rebuildDB method regenerates the RPM database indices, like the rpm --rebuilddb command:
+ </div><div class="para">
+ ts.rebuildDB()
+ </div><div class="para">
+ The rebuildDB method regenerates the RPM database indices, like the rpm --rebuilddb command.
+ </div><div class="para">
+ The verifyDB method checks that the RPM database and indices are readable by the Berkeley DB library:
+ </div><div class="para">
+ ts.verifyDB()
+ </div><div class="para">
+ Calling this method is the same as running the db_verify command on each of the database files in /var/lib/rpm.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ See <a class="xref" href="ch-using-rpm-db.html">Cap. 4, <em>Using the RPM Database</em></a> for more on initializing, rebuilding, and verifying RPM databases.
+ </div><div class="para">
+ Once you have a transaction set, you can start querying the RPM database.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch16s02.html"><strong>Înapoi</strong>16.2. The Python API Hierarchy</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch16s03s02.html"><strong>Înainte</strong>16.3.2. Querying the RPM database</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch16s03s02.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch16s03s02.html
new file mode 100644
index 0000000..c2610da
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch16s03s02.html
@@ -0,0 +1,130 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>16.3.2. Querying the RPM database</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch16s03.html" title="16.3. Programming with the RPM Database" /><link rel="prev" href="ch16s03.html" title="16.3. Programming with the RPM Database" /><link rel="next" href="ch16s03s03.html" title="16.3.3. Examining the package header" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch16s03.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch16s03s03.
html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id820199" class="title">Querying the RPM database</h1></div></div></div><div class="para">
+ Call dbMatch on a transaction set to create a match iterator. As with the C API, a match iterator allows your code to iterate over the packages that match a given criteria.
+ </div><div class="para">
+ A call to dbMatch with no parameters means to set up a match iterator to go over the entire set of installed packages. The basic format follows:
+ </div><div class="para">
+ import rpm
+ </div><div class="para">
+ </div><div class="para">
+ ts = rpm.TransactionSet()
+ </div><div class="para">
+ </div><div class="para">
+ mi = ts.dbMatch()
+ </div><div class="para">
+ for h in mi:
+ </div><div class="para">
+ # Do something with header object...
+ </div><div class="para">
+ In this example, the call to dbMatch returns a match iterator. The for loop iterates over the match iterator, returning one header each time.
+ </div><div class="para">
+ In addition to this syntax, you can call next on the match iterator to get the next entry, a header object that represents one package. For example:
+ </div><div class="para">
+ import rpm
+ </div><div class="para">
+ </div><div class="para">
+ ts = rpm.TransactionSet()
+ </div><div class="para">
+ </div><div class="para">
+ mi = ts.dbMatch()
+ </div><div class="para">
+ while mi:
+ </div><div class="para">
+ h = mi.next()
+ </div><div class="para">
+ # Do something with the header object
+ </div><div class="para">
+ The explicit call to next on the match iterator will likely no longer be supported in a future version of the RPM Python API, since the PEP-234 (Python Enhancement Proposal) calls for one means or the other for iterating, but not both.
+ </div><div class="para">
+ For example, Listing 17-1 shows a Python script to print out the name, version, and release information for all installed packages.
+ </div><div class="para">
+ Listing 17-1: rpmqa.py
+ </div><div class="para">
+ #!/usr/bin/python
+ </div><div class="para">
+ </div><div class="para">
+ # Acts like rpm -qa and lists the names of all the installed packages.
+ </div><div class="para">
+ # Usage:
+ </div><div class="para">
+ # python rpmqa.py
+ </div><div class="para">
+ </div><div class="para">
+ import rpm
+ </div><div class="para">
+ </div><div class="para">
+ ts = rpm.TransactionSet()
+ </div><div class="para">
+ </div><div class="para">
+ mi = ts.dbMatch()
+ </div><div class="para">
+ for h in mi:
+ </div><div class="para">
+ </div><div class="para">
+ print "%s-%s-%s" % (h['name'], h['version'], h['release'])
+ </div><div class="para">
+ When you call this script, you should see output like the following, truncated for space:
+ </div><div class="para">
+ $ python rpmqa.py
+ </div><div class="para">
+ libbonoboui-2.0.1-2
+ </div><div class="para">
+ attr-2.0.8-3
+ </div><div class="para">
+ dhclient-3.0pl1-9
+ </div><div class="para">
+ file-3.37-8
+ </div><div class="para">
+ hdparm-5.2-1
+ </div><div class="para">
+ ksymoops-2.4.5-1
+ </div><div class="para">
+ imlib-1.9.13-9
+ </div><div class="para">
+ logwatch-2.6-8
+ </div><div class="para">
+ mtr-0.49-7
+ </div><div class="para">
+ openssh-clients-3.4p1-2
+ </div><div class="para">
+ pax-3.0-4
+ </div><div class="para">
+ python-optik-1.3-2
+ </div><div class="para">
+ dump-0.4b28-4
+ </div><div class="para">
+ sendmail-8.12.5-7
+ </div><div class="para">
+ sudo-1.6.6-1
+ </div><div class="para">
+ mkbootdisk-1.4.8-1
+ </div><div class="para">
+ telnet-0.17-23
+ </div><div class="para">
+ usbutils-0.9-7
+ </div><div class="para">
+ wvdial-1.53-7
+ </div><div class="para">
+ docbook-dtds-1.0-14
+ </div><div class="para">
+ urw-fonts-2.0-26
+ </div><div class="para">
+ db4-utils-4.0.14-14
+ </div><div class="para">
+ libogg-devel-1.0-1
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ If you set the execute permission on this script, you can skip the explicit call to the python command. For example:
+ </div><div class="para">
+ $ ./rpmqa.pyr
+ </div><div class="para">
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch16s03.html"><strong>Înapoi</strong>16.3. Programming with the RPM Database</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch16s03s03.html"><strong>Înainte</strong>16.3.3. Examining the package header</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch16s03s03.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch16s03s03.html
new file mode 100644
index 0000000..e5daad4
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch16s03s03.html
@@ -0,0 +1,60 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>16.3.3. Examining the package header</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch16s03.html" title="16.3. Programming with the RPM Database" /><link rel="prev" href="ch16s03s02.html" title="16.3.2. Querying the RPM database" /><link rel="next" href="ch16s03s03s02.html" title="16.3.3.2. Printing Header Information with sprintf" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch16s03s02.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n"
href="ch16s03s03s02.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id731419" class="title">Examining the package header</h1></div></div></div><div class="para">
+ The code in Listing 17-1 introduces the package header object, an object of the hdr class. This represents a package header, and contains entries such as the name, version, pre- and post-installation scripts, and triggers.
+ </div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id731431" class="title">The hdr Class</h1></div></div></div><div class="para">
+ You can access each entry in the header using Python's dictionary syntax. This is much more convenient than calling headerGetEntry in C programs. The basic syntax to access header entries follows:
+ </div><div class="para">
+ value = h['tag_name']
+ </div><div class="para">
+ For example, to get the package name, use the following code:
+ </div><div class="para">
+ name = h['name']
+ </div><div class="para">
+ You can also use a set of predefined RPMTAG_ constants that match the C API. These constants are defined in the rpm module. For example:
+ </div><div class="para">
+ name = h[rpm.RPMTAG_NAME]
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ Using the rpm constants such as rpm.RPMTAG_NAME is faster than using the strings such as 'name'.
+ </div><div class="para">
+ For header entries that hold an array of strings, such as the list of files in the package, the data returned is a Python list. For example:
+ </div><div class="para">
+ print "Files:"
+ </div><div class="para">
+ files = h['FILENAMES']
+ </div><div class="para">
+ for name in files:
+ </div><div class="para">
+ print name
+ </div><div class="para">
+ You can use file info sets to achieve more compact code. For example:
+ </div><div class="para">
+ print "Files:"
+ </div><div class="para">
+ fi = h.fiFromHeader()
+ </div><div class="para">
+ print fi
+ </div><div class="para">
+ The requires, provides, obsoletes, and conflicts information each appear as three separate but related lists for each set of information, with three lists for the requires information, three for the provides information, and so on. You can extract this information using Python dependency sets using the simple code following:
+ </div><div class="para">
+ print h.dsFromHeader('providename')
+ </div><div class="para">
+ print h.dsFromHeader('requirename')
+ </div><div class="para">
+ print h.dsFromHeader('obsoletename')
+ </div><div class="para">
+ print h.dsFromHeader('conflictname')
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ The rpminfo.py script in Listing 17-3 shows how to print out this information.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch16s03s02.html"><strong>Înapoi</strong>16.3.2. Querying the RPM database</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch16s03s03s02.html"><strong>Înainte</strong>16.3.3.2. Printing Header Information with sprintf</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch16s03s03s02.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch16s03s03s02.html
new file mode 100644
index 0000000..5d05bb2
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch16s03s03s02.html
@@ -0,0 +1,34 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>16.3.3.2. Printing Header Information with sprintf</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch16s03s03.html" title="16.3.3. Examining the package header" /><link rel="prev" href="ch16s03s03.html" title="16.3.3. Examining the package header" /><link rel="next" href="ch16s03s04.html" title="16.3.4. Querying for specific packages" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch16s03s03.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch16s0
3s04.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id535041" class="title">Printing Header Information with sprintf</h1></div></div></div><div class="para">
+ In addition to using the Python dictionary syntax, you can use the sprintf method on a header to format data using a syntax exactly the same as the query format tags supported by the rpm command.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ <a class="xref" href="ch-using-rpm-db.html">Cap. 4, <em>Using the RPM Database</em></a> covers query formats.
+ </div><div class="para">
+ The basic syntax is as follows:
+ </div><div class="para">
+ h.sprintf("%{tag_name}")
+ </div><div class="para">
+ You can also use special formatting additions to the tag name. For example:
+ </div><div class="para">
+ print "Header signature: ", h.sprintf("%{DSAHEADER:pgpsig}")
+ </div><div class="para">
+ print "%-20s: %s" % ('Installed on', h.sprintf("%{INSTALLTID:date}") )
+ </div><div class="para">
+ You can combine this information into functions that print out header entries with specific formatting. For example:
+ </div><div class="para">
+ def nvr(h):
+ </div><div class="para">
+ return h.sprintf("%{NAME}-%{VERSION}-%{RELEASE}")
+ </div><div class="para">
+ Note that you only really need to use sprintf when you need the format modifiers, such as date on %{INSTALLTID:date}. In most other cases, Python’s string-handling functions will work better.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch16s03s03.html"><strong>Înapoi</strong>16.3.3. Examining the package header</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch16s03s04.html"><strong>Înainte</strong>16.3.4. Querying for specific packages</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch16s03s04.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch16s03s04.html
new file mode 100644
index 0000000..b57025f
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch16s03s04.html
@@ -0,0 +1,59 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>16.3.4. Querying for specific packages</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch16s03.html" title="16.3. Programming with the RPM Database" /><link rel="prev" href="ch16s03s03s02.html" title="16.3.3.2. Printing Header Information with sprintf" /><link rel="next" href="ch16s03s05.html" title="16.3.5. Printing information on packages" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch16s03s03s02.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a acce
sskey="n" href="ch16s03s05.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id777725" class="title">Querying for specific packages</h1></div></div></div><div class="para">
+ When you call dbMatch on a transaction set object, passing no parameters means to iterate over the entire set of installed packages in the RPM database. You can also query for specific packages using dbMatch. To do so, you need to pass the name of a tag in the header, as well as the value for that tag that you are looking for. The basic syntax follows:
+ </div><div class="para">
+ mi = ts.dbMatch(tag_name, value)
+ </div><div class="para">
+ For example, to query for all packages named sendmail, use code like the following:
+ </div><div class="para">
+ mi = ts.dbMatch('name', 'sendmail')
+ </div><div class="para">
+ The call to dbMatch returns an rpmdbMatchIterator. You can query on any of the tags in the header, but by far the most common query is by name.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ Some matches are fast and some are much slower. If you try to match on a tag that is indexed in the RPM database, the matches will perform much faster than for those tags that are not indexes. To determine which tags are indexed, look at the files in /var/lib/rpm. For example, Name and Requirename are files in /var/lib/rpm. These tags are indexed and will therefore match quickly.
+ </div><div class="para">
+ Listing 17-2 shows an example Python script which queries for a particular package name and then prints out the name, version, and release for all matching packages.
+ </div><div class="para">
+ Listing 17-2: rpmq.py
+ </div><div class="para">
+ #!/usr/bin/python
+ </div><div class="para">
+ </div><div class="para">
+ # Acts like rpm -q and lists the N-V-R for installed
+ </div><div class="para">
+ # packages that match a given name.
+ </div><div class="para">
+ # Usage:
+ </div><div class="para">
+ # python rpmq.py package_name
+ </div><div class="para">
+ </div><div class="para">
+ import rpm, sys
+ </div><div class="para">
+ </div><div class="para">
+ ts = rpm.TransactionSet()
+ </div><div class="para">
+ </div><div class="para">
+ mi = ts.dbMatch( 'name', sys.argv[1] )
+ </div><div class="para">
+ for h in mi:
+ </div><div class="para">
+ </div><div class="para">
+ print "%s-%s-%s" % (h['name'], h['version'], h['release'])
+ </div><div class="para">
+ When you call this script, you need to pass the name of a package to query, which the python interpreter will store in sys,argv[1] in the call to dbMatch. For example:
+ </div><div class="para">
+ $ python rpmq.py sendmail
+ </div><div class="para">
+ sendmail-8.12.5-7
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch16s03s03s02.html"><strong>Înapoi</strong>16.3.3.2. Printing Header Information with sprintf</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch16s03s05.html"><strong>Înainte</strong>16.3.5. Printing information on packages</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch16s03s05.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch16s03s05.html
new file mode 100644
index 0000000..899d86b
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch16s03s05.html
@@ -0,0 +1,180 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>16.3.5. Printing information on packages</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch16s03.html" title="16.3. Programming with the RPM Database" /><link rel="prev" href="ch16s03s04.html" title="16.3.4. Querying for specific packages" /><link rel="next" href="ch16s03s06.html" title="16.3.6. Refining queries" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch16s03s04.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch16s03s06.html"><
strong>ÃŽnainte</strong></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id691970" class="title">Printing information on packages</h1></div></div></div><div class="para">
+ You can create the equivalent of the rpm –qi command with a small number of Python commands. Listing 17-3 shows an example. This script queries for a particular package name, as shown previously in Listing 17-2. Once a package is found, though, rpminfo.py prints out a lot more information, similar to the output from the rpm –qi command.
+ </div><div class="para">
+ Listing 17-3: rpminfo.py
+ </div><div class="para">
+ #!/usr/bin/python
+ </div><div class="para">
+ </div><div class="para">
+ # Lists information on installed package listed on command line.
+ </div><div class="para">
+ # Usage:
+ </div><div class="para">
+ # python rpminfo.py package_name
+ </div><div class="para">
+ </div><div class="para">
+ import rpm, sys
+ </div><div class="para">
+ </div><div class="para">
+ def printEntry(header, label, format, extra):
+ </div><div class="para">
+ value = header.sprintf(format).strip()
+ </div><div class="para">
+ </div><div class="para">
+ print "%-20s: %s %s" % (label, value, extra)
+ </div><div class="para">
+ </div><div class="para">
+ </div><div class="para">
+ def printHeader(h):
+ </div><div class="para">
+ </div><div class="para">
+ if h[rpm.RPMTAG_SOURCEPACKAGE]:
+ </div><div class="para">
+ extra = " source package"
+ </div><div class="para">
+ else:
+ </div><div class="para">
+ extra = " binary package"
+ </div><div class="para">
+ </div><div class="para">
+ printEntry(h, 'Package', "%{NAME}-%{VERSION}-%{RELEASE}", extra)
+ </div><div class="para">
+ </div><div class="para">
+ printEntry(h, 'Group', "%{GROUP}", '')
+ </div><div class="para">
+ printEntry(h, 'Summary', "%{Summary}", '')
+ </div><div class="para">
+ printEntry(h, 'Arch-OS-Platform', "%{ARCH}-%{OS}-%{PLATFORM}", '')
+ </div><div class="para">
+ </div><div class="para">
+ printEntry(h, 'Vendor', "%{Vendor}", '')
+ </div><div class="para">
+ printEntry(h, 'URL', "%{URL}", '')
+ </div><div class="para">
+ printEntry(h, 'Size', "%{Size}", '')
+ </div><div class="para">
+ printEntry(h, 'Installed on', "%{INSTALLTID:date}", '')
+ </div><div class="para">
+ </div><div class="para">
+ print h['description']
+ </div><div class="para">
+ </div><div class="para">
+ print "Files:"
+ </div><div class="para">
+ fi = h.fiFromHeader()
+ </div><div class="para">
+ print fi
+ </div><div class="para">
+ </div><div class="para">
+ # Dependencies
+ </div><div class="para">
+ print "Provides:"
+ </div><div class="para">
+ print h.dsFromHeader('providename')
+ </div><div class="para">
+ print "Requires:"
+ </div><div class="para">
+ print h.dsFromHeader('requirename')
+ </div><div class="para">
+ </div><div class="para">
+ if h.dsFromHeader('obsoletename'):
+ </div><div class="para">
+ print "Obsoletes:"
+ </div><div class="para">
+ print h.dsFromHeader('obsoletename')
+ </div><div class="para">
+ </div><div class="para">
+ if h.dsFromHeader('conflictname'):
+ </div><div class="para">
+ print "Conflicts:"
+ </div><div class="para">
+ print h.dsFromHeader('conflictname')
+ </div><div class="para">
+ </div><div class="para">
+ </div><div class="para">
+ ts = rpm.TransactionSet()
+ </div><div class="para">
+ </div><div class="para">
+ mi = ts.dbMatch( 'name', sys.argv[1] )
+ </div><div class="para">
+ for h in mi:
+ </div><div class="para">
+ </div><div class="para">
+ printHeader(h)
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ You should be able to simplify this script. The extensive use of the sprintf method is for illustration more than efficiency. You generally only need to call sprintf when you need a format modifier for a tag. In the rpminfo.py script, sprintf was also used to ensure that all entries are text, which allows for calling strip.
+ </div><div class="para">
+ The printEntry function takes in a header sprintf tag value in the format of "%{NAME}". You can also pass in more complex values with multiple header entries, such as "%{NAME}-%{VERSION}".
+ </div><div class="para">
+ When you run this script, you need to pass the name of a package. You'll see output like the following:
+ </div><div class="para">
+ $ python rpminfo.py jikes
+ </div><div class="para">
+ Package : jikes-1.18-1 binary package
+ </div><div class="para">
+ Group : Development/Languages
+ </div><div class="para">
+ Summary : java source to bytecode compiler
+ </div><div class="para">
+ Arch-OS-Platform : i386-Linux-(none)
+ </div><div class="para">
+ Vendor : (none)
+ </div><div class="para">
+ URL : http://ibm.com/developerworks/opensource/jikes
+ </div><div class="para">
+ Size : 2853672
+ </div><div class="para">
+ Installed on : Mon Dec 2 20:10:13 2002
+ </div><div class="para">
+ The IBM Jikes compiler translates Java source files to bytecode. It
+ </div><div class="para">
+ also supports incremental compilation and automatic makefile
+ </div><div class="para">
+ generation,and is maintained by the Jikes Project:
+ </div><div class="para">
+ http://ibm.com/developerworks/opensource/jikes/
+ </div><div class="para">
+ </div><div class="para">
+ Files:
+ </div><div class="para">
+ /usr/bin/jikes
+ </div><div class="para">
+ /usr/doc/jikes-1.18/license.htm
+ </div><div class="para">
+ /usr/man/man1/jikes.1.gz
+ </div><div class="para">
+ </div><div class="para">
+ Provides:
+ </div><div class="para">
+ P jikes
+ </div><div class="para">
+ P jikes = 1.18-1
+ </div><div class="para">
+ </div><div class="para">
+ Requires:
+ </div><div class="para">
+ R ld-linux.so.2
+ </div><div class="para">
+ R libc.so.6
+ </div><div class="para">
+ R libc.so.6(GLIBC_2.0)
+ </div><div class="para">
+ R libc.so.6(GLIBC_2.1)
+ </div><div class="para">
+ R libc.so.6(GLIBC_2.1.3)
+ </div><div class="para">
+ R libm.so.6
+ </div><div class="para">
+ R libstdc++-libc6.2-2.so.3
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch16s03s04.html"><strong>Înapoi</strong>16.3.4. Querying for specific packages</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch16s03s06.html"><strong>Înainte</strong>16.3.6. Refining queries</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch16s03s06.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch16s03s06.html
new file mode 100644
index 0000000..5f7d37c
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch16s03s06.html
@@ -0,0 +1,157 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>16.3.6. Refining queries</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch16s03.html" title="16.3. Programming with the RPM Database" /><link rel="prev" href="ch16s03s05.html" title="16.3.5. Printing information on packages" /><link rel="next" href="ch16s04.html" title="16.4. Reading Package Files" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch16s03s05.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch16s04.html"><s
trong>ÃŽnainte</strong></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id852196" class="title">Refining queries</h1></div></div></div><div class="para">
+ The pattern method on a match iterator allows you to refine a query. This narrows an existing iterator to only show the packages you desire. The basic syntax follows:
+ </div><div class="para">
+ mi.pattern(tag_name, mode, pattern)
+ </div><div class="para">
+ The two main uses of the pattern method are to query on more than one tag, such as the version and name, or to narrow the results of a query, using the rich set of pattern modes. The mode parameter names the type of pattern used, which can be one of those listed in Table 17-2.
+ </div><div class="para">
+ Table 17-2 Pattern modes for the pattern method
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Type
+ </div>
+
+ </td><td>
+ <div class="para">
+ Meaning
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpm.RPMMIRE_DEFAULT
+ </div>
+
+ </td><td>
+ <div class="para">
+ Same as regular expressions, but with \., .*, and ^..$ added
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpm.RPMMIRE_GLOB
+ </div>
+
+ </td><td>
+ <div class="para">
+ Glob-style patterns using fnmatch
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpm.RPMMIRE_REGEX
+ </div>
+
+ </td><td>
+ <div class="para">
+ Regular expressions using regcomp
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpm.RPMMIRE_STRCMP
+ </div>
+
+ </td><td>
+ <div class="para">
+ String comparisons using strcmp
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ For more on these patterns, see the online manual pages for fnmatch(3), glob(7), regcomp(3), regex(7), and strcmp(3). The pattern method calls rpmdbSetIteratorRE from the C API, covered in the “Database Iterators†section in <a class="xref" href="ch-programming-c.html">Cap. 15, <em>Programming RPM with C</em></a> .
+ </div><div class="para">
+ To query for all packages starting with py, for example, you can use code like the following:
+ </div><div class="para">
+ import rpm
+ </div><div class="para">
+ </div><div class="para">
+ ts = rpm.TransactionSet()
+ </div><div class="para">
+ </div><div class="para">
+ mi = ts.dbMatch()
+ </div><div class="para">
+ </div><div class="para">
+ mi.pattern('name', rpm.RPMMIRE_GLOB, 'py*' )
+ </div><div class="para">
+ </div><div class="para">
+ for h in mi:
+ </div><div class="para">
+ # Do something with the header...
+ </div><div class="para">
+ Listing 17-4 shows an example for glob-based querying.
+ </div><div class="para">
+ Listing 17-4: rpmglob.py
+ </div><div class="para">
+ #!/usr/bin/python
+ </div><div class="para">
+ </div><div class="para">
+ # Acts like rpm -q and lists the N-V-R for installed packages
+ </div><div class="para">
+ # that match a given name using a glob-like syntax
+ </div><div class="para">
+ #
+ </div><div class="para">
+ # Usage:
+ </div><div class="para">
+ # python rpmglob.py "package_fragment*"
+ </div><div class="para">
+ </div><div class="para">
+ import rpm, sys
+ </div><div class="para">
+ </div><div class="para">
+ ts = rpm.TransactionSet()
+ </div><div class="para">
+ </div><div class="para">
+ mi = ts.dbMatch()
+ </div><div class="para">
+ </div><div class="para">
+ if not mi:
+ </div><div class="para">
+ print "No packages found."
+ </div><div class="para">
+ else:
+ </div><div class="para">
+ mi.pattern('name', rpm.RPMMIRE_GLOB, sys.argv[1] )
+ </div><div class="para">
+ </div><div class="para">
+ for h in mi:
+ </div><div class="para">
+ </div><div class="para">
+ print "%s-%s-%s" % (h['name'], h['version'], h['release'])
+ </div><div class="para">
+ When you run this script, you’ll see output like the following:
+ </div><div class="para">
+ $ python rpmglob.py "py*"
+ </div><div class="para">
+ pyxf86config-0.3.1-2
+ </div><div class="para">
+ python-devel-2.2.1-17
+ </div><div class="para">
+ pygtk2-devel-1.99.12-7
+ </div><div class="para">
+ pygtk2-libglade-1.99.12-7
+ </div><div class="para">
+ pygtk2-1.99.12-7
+ </div><div class="para">
+ pyOpenSSL-0.5.0.91-1
+ </div><div class="para">
+ python-optik-1.3-2
+ </div><div class="para">
+ python-docs-2.2.1-17
+ </div><div class="para">
+ python-2.2.1-17
+ </div><div class="para">
+ python-tools-2.2.1-17
+ </div><div class="para">
+ In addition to working with the RPM database, the Python API also provides access to RPM files.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch16s03s05.html"><strong>Înapoi</strong>16.3.5. Printing information on packages</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch16s04.html"><strong>Înainte</strong>16.4. Reading Package Files</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch16s04.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch16s04.html
new file mode 100644
index 0000000..1a45c3a
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch16s04.html
@@ -0,0 +1,87 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>16.4. Reading Package Files</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-rpm-programming-python.html" title="Cap. 16. Programming RPM with Python" /><link rel="prev" href="ch16s03s06.html" title="16.3.6. Refining queries" /><link rel="next" href="ch16s04s02.html" title="16.4.2. Setting the verification flags" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch16s03s06.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch1
6s04s02.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id662373" class="title">Reading Package Files</h1></div></div></div><div class="para">
+ As you would expect, the Python API includes methods for working with RPM package files in addition to installed RPM packages. Most of these methods require a header object, which you can read from an RPM package file.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id662386" class="title">Reading headers from package files</h1></div></div></div><div class="para">
+ Like the C function rpmReadPackageFile, the Python API provides a convenient way to read in a header object from an RPM package file. The hdrFromFdno method reads an RPM header from an open file descriptor. The basic syntax is:
+ </div><div class="para">
+ h = ts.hdrFromFdno(fdno)
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ The hdrFromFdno method uses Python’s low-level file descriptors instead of the higher-level Python file objects. In the RPM C library, an FD_t is a FILE**. This could be bound to a Python class, but that is outside the scope of this chapter.
+ </div><div class="para">
+ The following example shows a function that opens a file, reads in the RPM header, and then closes the file:
+ </div><div class="para">
+ def readRpmHeader(ts, filename):
+ </div><div class="para">
+ """ Read an rpm header. """
+ </div><div class="para">
+ fd = os.open(filename, os.O_RDONLY)
+ </div><div class="para">
+ </div><div class="para">
+ h = ts.hdrFromFdno(fd)
+ </div><div class="para">
+ </div><div class="para">
+ os.close(fd)
+ </div><div class="para">
+ return h
+ </div><div class="para">
+ </div><div class="para">
+ ts = rpm.TransactionSet()
+ </div><div class="para">
+ </div><div class="para">
+ h = readRpmHeader( ts, 'n-r-v.rpm' )
+ </div><div class="para">
+ The hdrFromFdno method raises a number of exceptions based on issues detected with the package files. The following example shows these exceptions:
+ </div><div class="para">
+ def readRpmHeader(ts, filename):
+ </div><div class="para">
+ """ Read an rpm header. """
+ </div><div class="para">
+ fd = os.open(filename, os.O_RDONLY)
+ </div><div class="para">
+ </div><div class="para">
+ h = None
+ </div><div class="para">
+ tryL
+ </div><div class="para">
+ h = ts.hdrFromFdno(fd)
+ </div><div class="para">
+ except rpm.error, e:
+ </div><div class="para">
+ if str(e) == "public key not available":
+ </div><div class="para">
+ print str(e)
+ </div><div class="para">
+ if str(e) == "public key not trusted":
+ </div><div class="para">
+ print str(e)
+ </div><div class="para">
+ if str(e) == "error reading package header":
+ </div><div class="para">
+ print str(e)
+ </div><div class="para">
+ h = None
+ </div><div class="para">
+ </div><div class="para">
+ </div><div class="para">
+ os.close(fd)
+ </div><div class="para">
+ return h
+ </div><div class="para">
+ </div><div class="para">
+ ts = rpm.TransactionSet()
+ </div><div class="para">
+ </div><div class="para">
+ h = readRpmHeader( ts, 'n-r-v.rpm' )
+ </div><div class="para">
+ You can decide in your code whether the exceptions should stop processing or not.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch16s03s06.html"><strong>Înapoi</strong>16.3.6. Refining queries</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch16s04s02.html"><strong>Înainte</strong>16.4.2. Setting the verification flags</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch16s04s02.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch16s04s02.html
new file mode 100644
index 0000000..3babbbb
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch16s04s02.html
@@ -0,0 +1,130 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>16.4.2. Setting the verification flags</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch16s04.html" title="16.4. Reading Package Files" /><link rel="prev" href="ch16s04.html" title="16.4. Reading Package Files" /><link rel="next" href="ch16s05.html" title="16.5. Dependency Comparisons" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch16s04.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch16s05.html"><strong>ÃŽnainte</strong></a></l
i></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id701246" class="title">Setting the verification flags</h1></div></div></div><div class="para">
+ Starting with rpm 4.1, package files are verified automatically, which can cause problems, especially if you are working with older packages, or packages without proper digital signatures.
+ </div><div class="para">
+ In most cases, the automatic verification is an advantage, since you can have greater confidence in the package files. However, you can call setVSFlags on a transaction set to change the default behavior.
+ </div><div class="para">
+ ts.setVSFlags(flags)
+ </div><div class="para">
+ For example, if you have problems with old packages that do not have proper signatures, you can use code like the following to ignore such checks:
+ </div><div class="para">
+ # Set to not verify DSA signatures.
+ </div><div class="para">
+ ts.setVSFlags(rpm.RPMVSF_NODSA)
+ </div><div class="para">
+ Table 17-3 lists the flags you can pass to setVSFlags on a transaction set. These flags are bitmasks. You can or them together for more than one setting. You must do a binary or. Do not use the Python or keyword. Use | instead, for a binary or operation.
+ </div><div class="para">
+ Table 17-3 Flags for setVSFlags
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Flag
+ </div>
+
+ </td><td>
+ <div class="para">
+ Meaning
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpm.RPMVSF_NEEDPAYLOAD
+ </div>
+
+ </td><td>
+ <div class="para">
+ Leave the file handle positions at the beginning of the payload.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpm.RPMVSF_NOHDRCHK
+ </div>
+
+ </td><td>
+ <div class="para">
+ Don’t check the RPM database header.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpm.RPMVSF_ NODSA
+ </div>
+
+ </td><td>
+ <div class="para">
+ Don’t check the header and payload DSA signatures.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpm.RPMVSF_ NODSAHEADER
+ </div>
+
+ </td><td>
+ <div class="para">
+ Don’t check the header DSA signature.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpm.RPMVSF_ NOMD5
+ </div>
+
+ </td><td>
+ <div class="para">
+ Don’t check the header and payload MD5 digests.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpm.RPMVSF_ NORSA
+ </div>
+
+ </td><td>
+ <div class="para">
+ Don’t check the header and payload RSA signatures.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpm.RPMVSF_ NOSHA1HEADER
+ </div>
+
+ </td><td>
+ <div class="para">
+ Don’t check the header SHA1 digest.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpm._RPMVSF_NODIGESTS
+ </div>
+
+ </td><td>
+ <div class="para">
+ Convenience to not check digests.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpm._RPMVSF_NOSIGNATURES
+ </div>
+
+ </td><td>
+ <div class="para">
+ Convenience to not check signatures.
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ To turn off all checks, you can pass –1 to setVSFlags:
+ </div><div class="para">
+ ts.setVSFlasgs(-1)
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch16s04.html"><strong>Înapoi</strong>16.4. Reading Package Files</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch16s05.html"><strong>Înainte</strong>16.5. Dependency Comparisons</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch16s05.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch16s05.html
new file mode 100644
index 0000000..c329be3
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch16s05.html
@@ -0,0 +1,92 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>16.5. Dependency Comparisons</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-rpm-programming-python.html" title="Cap. 16. Programming RPM with Python" /><link rel="prev" href="ch16s04s02.html" title="16.4.2. Setting the verification flags" /><link rel="next" href="ch16s06.html" title="16.6. Installing and Upgrading Packages" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch16s04s02.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="
n" href="ch16s06.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id653738" class="title">Dependency Comparisons</h1></div></div></div><div class="para">
+ Dependency sets, first introduced in <a class="xref" href="ch-programming-c.html">Cap. 15, <em>Programming RPM with C</em></a> on C programming, allow you to compare the dependencies between two packages. One of the most common uses for this is to compare a package file against a version on disk to see if the package file holds a newer version of a package than the one installed.
+ </div><div class="para">
+ You can call dsOfHeader on a header object to get the default dependency set for the header. Armed with dependency sets from two headers, you can compare the sets to see which package is newer using simple code like the following:
+ </div><div class="para">
+ file_h = ts.hdrFromFdno(fd)
+ </div><div class="para">
+ file_ds = file_h.dsOfHeader()
+ </div><div class="para">
+ inst_ds = inst_h.dsOfHeader()
+ </div><div class="para">
+ if file_ds.EVR() >= inst_ds.EVR():
+ </div><div class="para">
+ print "Package file is same or newer, OK to upgrade."
+ </div><div class="para">
+ else:
+ </div><div class="para">
+ print "Package file is older than installed version."
+ </div><div class="para">
+ Pulling this all together, Listing 17-5 provides a Python script that compares a package file against an installed package, reporting on which is newer.
+ </div><div class="para">
+ Listing 17-5: vercompare.py
+ </div><div class="para">
+ #!/usr/bin/python
+ </div><div class="para">
+ </div><div class="para">
+ # Reads in package header, compares to installed package.
+ </div><div class="para">
+ # Usage:
+ </div><div class="para">
+ # python vercompare.py rpm_file.rpm
+ </div><div class="para">
+ #
+ </div><div class="para">
+ </div><div class="para">
+ import rpm, os, sys
+ </div><div class="para">
+ </div><div class="para">
+ def readRpmHeader(ts, filename):
+ </div><div class="para">
+ """ Read an rpm header. """
+ </div><div class="para">
+ fd = os.open(filename, os.O_RDONLY)
+ </div><div class="para">
+ </div><div class="para">
+ h = ts.hdrFromFdno(fd)
+ </div><div class="para">
+ </div><div class="para">
+ os.close(fd)
+ </div><div class="para">
+ return h
+ </div><div class="para">
+ </div><div class="para">
+ </div><div class="para">
+ ts = rpm.TransactionSet()
+ </div><div class="para">
+ h = readRpmHeader( ts, sys.argv[1] )
+ </div><div class="para">
+ </div><div class="para">
+ pkg_ds = h.dsOfHeader()
+ </div><div class="para">
+ </div><div class="para">
+ for inst_h in ts.dbMatch('name', h['name']):
+ </div><div class="para">
+ inst_ds = inst_h.dsOfHeader()
+ </div><div class="para">
+ </div><div class="para">
+ if pkg_ds.EVR() >= inst_ds.EVR():
+ </div><div class="para">
+ print "Package file is same or newer, OK to upgrade."
+ </div><div class="para">
+ else:
+ </div><div class="para">
+ print "Package file is older than installed version."
+ </div><div class="para">
+ Cross-Reference
+ </div><div class="para">
+ The Python script in Listing 17-5 is essentially the same as the longer C program vercompare.c in Listing 16-4 in <a class="xref" href="ch-programming-c.html">Cap. 15, <em>Programming RPM with C</em></a> .
+ </div><div class="para">
+ This script takes in a package file name on the command line, loads in the header for that package, and looks up all packages of the same name installed in the RPM database. For each match, this script compares the packages to see which is newer.
+ </div><div class="para">
+ You can modify this script, for example, to print out a message if a package isn't installed.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch16s04s02.html"><strong>Înapoi</strong>16.4.2. Setting the verification flags</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch16s06.html"><strong>Înainte</strong>16.6. Installing and Upgrading Packages</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch16s06.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch16s06.html
new file mode 100644
index 0000000..e3973e9
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch16s06.html
@@ -0,0 +1,39 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>16.6. Installing and Upgrading Packages</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-rpm-programming-python.html" title="Cap. 16. Programming RPM with Python" /><link rel="prev" href="ch16s05.html" title="16.5. Dependency Comparisons" /><link rel="next" href="ch16s06s02.html" title="16.6.2. Transaction elements" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch16s05.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch16s06s02.html
"><strong>ÃŽnainte</strong></a></li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id802708" class="title">Installing and Upgrading Packages</h1></div></div></div><div class="para">
+ With the RPM system, you have a lot of choices. You can install or upgrade packages with the rpm command. You can install or upgrade packages with special programs you write using the C API. And you can install or upgrade packages using the Python API. If you are writing a special program to install or upgrade packages, the Python API makes this task much easier. As with the C API, most of your work needs to be part of a transaction set.
+ </div><div class="para">
+ To install or upgrade a package, you need to create a transaction set, build up the transaction with packages, which are stored as transaction elements within the transaction set, check for unresolved dependencies, reorder the transaction set based on the dependencies, and then run the transaction set. Running the transaction set installs or upgrades the packages. The following sections cover these steps.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id615216" class="title">Building up the transaction set</h1></div></div></div><div class="para">
+ Package installs and upgrades need to be performed within the context of a transaction set. To install or upgrade a set of packages, you need to call addInstall with the package headers to install or upgrade. The basic syntax follows:
+ </div><div class="para">
+ ts.addInstall(header, key_data, mode)
+ </div><div class="para">
+ When you call addInstall, you pass the header object along with arbitrary callback key data and a mode flag. The mode flag should be 'i' to install a package, 'u' to upgrade a package, or 'a' as a special code to make a package available for transaction checks but not install or upgrade the package. The 'a' flag is rarely used. In most cases, you should use 'u', just as in most cases, you should install packages with rpm –U instead of rpm –i.
+ </div><div class="para">
+ The key_data parameter will get passed to the transaction set run callback, covered in the “Running the Transaction†section later in this chapter.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ To remove packages instead of install or upgrade, call addErase instead of addInstall:
+ </div><div class="para">
+ ts.addErase(package_name)
+ </div><div class="para">
+ To set up a package to be upgraded or installed, you can use code like the following:
+ </div><div class="para">
+ h = readRpmHeader( ts, sys.argv[1] )
+ </div><div class="para">
+ </div><div class="para">
+ ts.addInstall(h, sys.argv[1], 'u')
+ </div><div class="para">
+ This example expects a package file name on the command line (accessed with sys.argv[1]), and reads in the package header using the readRpmHeader function introduced previously.
+ </div><div class="para">
+ The call to addInstall adds the header object (and the associated RPM package file) for an upgrade with the 'u' mode flag. The name of the package file, from sys.argv[1], is passed as the arbitrary data for the transaction set run callback function.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch16s05.html"><strong>Înapoi</strong>16.5. Dependency Comparisons</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch16s06s02.html"><strong>Înainte</strong>16.6.2. Transaction elements</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch16s06s02.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch16s06s02.html
new file mode 100644
index 0000000..2d4da52
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch16s06s02.html
@@ -0,0 +1,203 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>16.6.2. Transaction elements</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch16s06.html" title="16.6. Installing and Upgrading Packages" /><link rel="prev" href="ch16s06.html" title="16.6. Installing and Upgrading Packages" /><link rel="next" href="ch16s06s03.html" title="16.6.3. Checking and reordering the transaction elements" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch16s06.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="
n" href="ch16s06s03.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id615284" class="title">Transaction elements</h1></div></div></div><div class="para">
+ Transaction sets are made up of transaction elements. A transaction element makes up one part of a transaction and holds one package per operation (install or remove) in each transaction set. That is, there is one transaction element per package per operation in the transaction set. You can iterate over a transaction set to get each transaction element. Once you have a transaction element, you can call methods on each element to check entries in the header as well as get dependency sets for the package.
+ </div><div class="para">
+ Table 17-4 lists the informational methods you can call on a transaction element. Most of the methods listed in Table 17-4 return a single value.
+ </div><div class="para">
+ Table 17-4 Informational methods on transaction sets
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Method
+ </div>
+
+ </td><td>
+ <div class="para">
+ Returns
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ A
+ </div>
+
+ </td><td>
+ <div class="para">
+ Returns package architecture
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ E
+ </div>
+
+ </td><td>
+ <div class="para">
+ Returns package epoch
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ O
+ </div>
+
+ </td><td>
+ <div class="para">
+ Returns package operating system
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ R
+ </div>
+
+ </td><td>
+ <div class="para">
+ Returns package release number
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ V
+ </div>
+
+ </td><td>
+ <div class="para">
+ Returns package version
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ N
+ </div>
+
+ </td><td>
+ <div class="para">
+ Returns package name
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ NEVR
+ </div>
+
+ </td><td>
+ <div class="para">
+ Returns package name-epoch-version-release
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ DS
+ </div>
+
+ </td><td>
+ <div class="para">
+ Returns the package dependency set for a given tag
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ FI
+ </div>
+
+ </td><td>
+ <div class="para">
+ Returns the file info set for the package
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ For more complex checking, the DS method returns the package dependency set for a given tag:
+ </div><div class="para">
+ ds = te.DS(tag_name)
+ </div><div class="para">
+ Pass one of 'Providename', 'Requirename', 'Obsoletename', or 'Conflictname' for the tag name. For example:
+ </div><div class="para">
+ ds = te.DS('Requirename')
+ </div><div class="para">
+ The FI method returns the file info set for the package:
+ </div><div class="para">
+ fi = te.FI(tag_name)
+ </div><div class="para">
+ For the FI method, you must pass a tag name of 'Basenames'.
+ </div><div class="para">
+ As an example, Listing 17-6 shows how to iterate through a transaction set to get transaction elements.
+ </div><div class="para">
+ Listing 17-6: te.py
+ </div><div class="para">
+ #!/usr/bin/python
+ </div><div class="para">
+ </div><div class="para">
+ # Adds all package files on command line to a transaction
+ </div><div class="para">
+ # and prints out the transaction elements.
+ </div><div class="para">
+ # Usage:
+ </div><div class="para">
+ # python te.py rpm_file1.rpm rpm_file2.rpm ...
+ </div><div class="para">
+ #
+ </div><div class="para">
+ import rpm, os, sys
+ </div><div class="para">
+ </div><div class="para">
+ def readRpmHeader(ts, filename):
+ </div><div class="para">
+ """ Read an rpm header. """
+ </div><div class="para">
+ fd = os.open(filename, os.O_RDONLY)
+ </div><div class="para">
+ </div><div class="para">
+ h = ts.hdrFromFdno(fd)
+ </div><div class="para">
+ </div><div class="para">
+ os.close(fd)
+ </div><div class="para">
+ return h
+ </div><div class="para">
+ </div><div class="para">
+ </div><div class="para">
+ ts = rpm.TransactionSet()
+ </div><div class="para">
+ </div><div class="para">
+ # Set to not verify DSA signatures.
+ </div><div class="para">
+ ts.setVSFlags(rpm._RPMVSF_NOSIGNATURES)
+ </div><div class="para">
+ </div><div class="para">
+ for filename in sys.argv[1:]:
+ </div><div class="para">
+ h = readRpmHeader(ts, filename)
+ </div><div class="para">
+ print "Installing %s-%s-%s" % (h['name'], h['version'], h['release'])
+ </div><div class="para">
+ ts.addInstall(h, filename, 'i')
+ </div><div class="para">
+ </div><div class="para">
+ print "This will install:"
+ </div><div class="para">
+ for te in ts:
+ </div><div class="para">
+ print "%s-%s-%s" % (te.N(), te.V(), te.R() )
+ </div><div class="para">
+ </div><div class="para">
+ ts.check()
+ </div><div class="para">
+ ts.order()
+ </div><div class="para">
+ </div><div class="para">
+ print "This will install:"
+ </div><div class="para">
+ for te in ts:
+ </div><div class="para">
+ print "%s-%s-%s" % (te.N(), te.V(), te.R() )
+ </div><div class="para">
+ The te.py script sets up a transaction and then prints out the elements, never completing the transaction. The purpose here is just to show what is in the transaction. The second set of printed output shows the results of the check and order methods, covered in the following section.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch16s06.html"><strong>Înapoi</strong>16.6. Installing and Upgrading Packages</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch16s06s03.html"><strong>Înainte</strong>16.6.3. Checking and reordering the transaction e...</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch16s06s03.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch16s06s03.html
new file mode 100644
index 0000000..5c8eb37
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch16s06s03.html
@@ -0,0 +1,42 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>16.6.3. Checking and reordering the transaction elements</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch16s06.html" title="16.6. Installing and Upgrading Packages" /><link rel="prev" href="ch16s06s02.html" title="16.6.2. Transaction elements" /><link rel="next" href="ch16s06s03s02.html" title="16.6.3.2. Transaction Check Method Callbacks" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch16s06s02.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch16s
06s03s02.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id702889" class="title">Checking and reordering the transaction elements</h1></div></div></div><div class="para">
+ After you have called addInstall or addErase for each of the packages you want to install, upgrade, or remove, you need to call two methods to verify the transaction set and order all the elements properly. These two methods are check and order.
+ </div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id649726" class="title">Checking the Dependencies</h1></div></div></div><div class="para">
+ The check method checks the dependencies in a transaction set.
+ </div><div class="para">
+ unresolved_dependencies = ts.check()
+ </div><div class="para">
+ It returns None if all dependencies are resolved, or a complex tuple for each unresolved dependency. In general, if the check method returns anything but None, you cannot perform the transaction.
+ </div><div class="para">
+ On a dependency failure, check returns a complex tuple of the dependency information in the following format:
+ </div><div class="para">
+ ((N,V,R), (reqN, reqV), needsFlags, suggestedPackage, sense)
+ </div><div class="para">
+ The first element is a tuple of the name, version, and release of the package you are trying to install. The next tuple holds the required name and required version or conflicting name and version. The version will be None if the dependency is a shared library or other file.
+ </div><div class="para">
+ The needs flags tell you about the requirement or conflict. The value is a bitmask that can contain the following bit settings: rpm.RPMSENSE_EQUAL, rpm.RPMSENSE_GREATER, and rpm.RPMSENSE_LESS. This tells you if the dependency is for a version of a package greater than 4.1, for example.
+ </div><div class="para">
+ The suggested package names a package that solves the dependency. The packages considered are those for which you call addInstall with a flag of 'a'. This value will be None if there is no known package to solve this dependency.
+ </div><div class="para">
+ You can tell whether the dependency is a conflict or a requirement based on the sense value, one of rpm.RPMSENSE_CONFLICTS or rpm.RPMSENSE_REQUIRES.
+ </div><div class="para">
+ For example, the following tuple shows a required package:
+ </div><div class="para">
+ (('eruby-devel', '0.9.8', '2'), ('eruby-libs', '0.9.8'), 8, None, 0)
+ </div><div class="para">
+ The following tuple shows a required shared library:
+ </div><div class="para">
+ (('jpilot', '0.97', '1'), ('libpisock.so.3', None), 0, None, 0)
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ This tuple format will likely change in future versions of RPM. This example shows the format in RPM 4.1. With each RPM release, check the online documentation on the Python API to look for changes.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch16s06s02.html"><strong>Înapoi</strong>16.6.2. Transaction elements</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch16s06s03s02.html"><strong>Înainte</strong>16.6.3.2. Transaction Check Method Callbacks</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch16s06s03s02.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch16s06s03s02.html
new file mode 100644
index 0000000..a2ef021
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch16s06s03s02.html
@@ -0,0 +1,64 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>16.6.3.2. Transaction Check Method Callbacks</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch16s06s03.html" title="16.6.3. Checking and reordering the transaction elements" /><link rel="prev" href="ch16s06s03.html" title="16.6.3. Checking and reordering the transaction elements" /><link rel="next" href="ch16s06s03s03.html" title="16.6.3.3. Reordering the Transaction Set" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch16s06s03.html"><strong>ÃŽnapoi</strong></a></li><
li class="next"><a accesskey="n" href="ch16s06s03s03.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id649806" class="title">Transaction Check Method Callbacks</h1></div></div></div><div class="para">
+ You can pass an optional callback function to the call to check. This callback gets called for each unresolved dependency in the transaction set. You can use this callback to try to automatically bring in required packages, for example.
+ </div><div class="para">
+ The basic syntax for the transaction check callback is:
+ </div><div class="para">
+ def checkCallback(ts, TagN, N, EVR, Flags):
+ </div><div class="para">
+ # Do something…
+ </div><div class="para">
+ You can use a check callback to automatically bring in packages that are required into a transaction set. You can bring in packages from the Red Hat RPM database package, which contains a database of all Red Hat packages, the rpmdb-redhat package. You can open the database from this package by using the trick described previously for opening transactions to more than one RPM database at a time. Simply set the _dbpath macro to "/usr/lib/rpmdb/i386-redhat-linux/redhat", or the location of your rpmdb-redhat database, and create a transaction set. Your check callback can then search this extra database and add packages from that database into the current, real RPM database.
+ </div><div class="para">
+ Your check callback can also attempt to find package files to resolve dependencies, from a disk directory or network archive for example. The following code shows a stub check callback that you can fill in to try to resolve dependencies. This callback sets up a format for finding unresolved packages in another RPM database, or elsewhere. You need to fill in the skeleton with the algorithm you want to actually resolve the dependencies.
+ </div><div class="para">
+ def checkCallback(ts, TagN, N, EVR, Flags):
+ </div><div class="para">
+ </div><div class="para">
+ if TagN == rpm.RPMTAG_REQUIRENAME:
+ </div><div class="para">
+ prev = ""
+ </div><div class="para">
+ Nh = None
+ </div><div class="para">
+ </div><div class="para">
+ if N[0] == '/':
+ </div><div class="para">
+ dbitag = 'basenames'
+ </div><div class="para">
+ else:
+ </div><div class="para">
+ dbitag = 'providename'
+ </div><div class="para">
+ </div><div class="para">
+ # What do you need to do.
+ </div><div class="para">
+ if EVR:
+ </div><div class="para">
+ print "Must find package [", N, "-", EVR, "]"
+ </div><div class="para">
+ else:
+ </div><div class="para">
+ print "Must find file [", N, "]"
+ </div><div class="para">
+ </div><div class="para">
+ if resolved:
+ </div><div class="para">
+ # ts.addIntall(h, h, 'i')
+ </div><div class="para">
+ </div><div class="para">
+ return -1
+ </div><div class="para">
+ </div><div class="para">
+ return 1
+ </div><div class="para">
+ Depending on the values passed to the callback, your code must either find a package itself or a package that provides a given file or capability to resolve the dependency. If you have another RPM database to look at, such as the rpmdb-redhat database, you can use dbMatch to find the necessary packages in that database. If, however, you are working with a directory of RPM files, you need to build up file names from the package name, version, and release.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch16s06s03.html"><strong>Înapoi</strong>16.6.3. Checking and reordering the transaction e...</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch16s06s03s03.html"><strong>Înainte</strong>16.6.3.3. Reordering the Transaction Set</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch16s06s03s03.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch16s06s03s03.html
new file mode 100644
index 0000000..030abd6
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch16s06s03s03.html
@@ -0,0 +1,16 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>16.6.3.3. Reordering the Transaction Set</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch16s06s03.html" title="16.6.3. Checking and reordering the transaction elements" /><link rel="prev" href="ch16s06s03s02.html" title="16.6.3.2. Transaction Check Method Callbacks" /><link rel="next" href="ch16s06s04.html" title="16.6.4. Running the transaction" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch16s06s03s02.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a
accesskey="n" href="ch16s06s04.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id651769" class="title">Reordering the Transaction Set</h1></div></div></div><div class="para">
+ You can add packages to a transaction set in any order. The order method reorders the transaction set to ensure that packages get installed or removed in the right order. The order method orders by a topological sort using the dependencies relations between objects with dependency comparisons.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ You must call check prior to order.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch16s06s03s02.html"><strong>Înapoi</strong>16.6.3.2. Transaction Check Method Callbacks</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch16s06s04.html"><strong>Înainte</strong>16.6.4. Running the transaction</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch16s06s04.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch16s06s04.html
new file mode 100644
index 0000000..94fef82
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch16s06s04.html
@@ -0,0 +1,210 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>16.6.4. Running the transaction</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch16s06.html" title="16.6. Installing and Upgrading Packages" /><link rel="prev" href="ch16s06s03s03.html" title="16.6.3.3. Reordering the Transaction Set" /><link rel="next" href="ch16s06s04s02.html" title="16.6.4.2. Coding A Sample Callback" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch16s06s03s03.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" hre
f="ch16s06s04s02.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id651793" class="title">Running the transaction</h1></div></div></div><div class="para">
+ After setting up the transaction set, perform the transaction by calling run. You need to provide two parameters:
+ </div><div class="para">
+ ts.run(callback, client_data)
+ </div><div class="para">
+ The callback parameter must be a Python function. The client_data is any data you want to pass to the callback. There may be more than one package in the transaction set, so this data should not be specific to a particular package.
+ </div><div class="para">
+ Warning
+ </div><div class="para">
+ You must not pass None as the client_data or you will get a Python error.
+ </div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id651821" class="title">Transaction run Method Callbacks</h1></div></div></div><div class="para">
+ The callback you pass to the run method on a transaction set is essential. Your callback must work properly, or the transaction will fail. You must provide a callback.
+ </div><div class="para">
+ Your callback will get called a number of times, mostly as a means to report progress. If you are writing a graphical user interface, for example, you can use the progress callbacks to update a visual progress meter.
+ </div><div class="para">
+ The basic syntax for the transaction set run callback is:
+ </div><div class="para">
+ def runCallback(reason, amount, total, key, client_data):
+ </div><div class="para">
+ # Do your stuff...
+ </div><div class="para">
+ The key is the data you provided in the call to the addInstall method. The client_data is the data you passed to the run method.
+ </div><div class="para">
+ Each time your callback is called, the transaction set will provide a reason flag. Table 17-5 lists the values for the reason parameter.
+ </div><div class="para">
+ Table 17-5 Transaction set run callback reason values
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Value
+ </div>
+
+ </td><td>
+ <div class="para">
+ Reason
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpm.RPMCALLBACK_UNKNOWN
+ </div>
+
+ </td><td>
+ <div class="para">
+ Unknown problem
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpm.RPMCALLBACK_INST_PROGRESS
+ </div>
+
+ </td><td>
+ <div class="para">
+ Progress for installation
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpm.RPMCALLBACK_INST_START
+ </div>
+
+ </td><td>
+ <div class="para">
+ Start of installation
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpm.RPMCALLBACK_INST_OPEN_FILE
+ </div>
+
+ </td><td>
+ <div class="para">
+ Callback should open package file
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpm.RPMCALLBACK_INST_CLOSE_FILE
+ </div>
+
+ </td><td>
+ <div class="para">
+ Callback should close package file
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpm.RPMCALLBACK_TRANS_PROGRESS
+ </div>
+
+ </td><td>
+ <div class="para">
+ Transaction progress
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpm.RPMCALLBACK_TRANS_START
+ </div>
+
+ </td><td>
+ <div class="para">
+ Transaction start
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpm.RPMCALLBACK_TRANS_STOP
+ </div>
+
+ </td><td>
+ <div class="para">
+ Transaction stop
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpm.RPMCALLBACK_UNINST_PROGRESS
+ </div>
+
+ </td><td>
+ <div class="para">
+ Uninstallation progress
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpm.RPMCALLBACK_UNINST_START
+ </div>
+
+ </td><td>
+ <div class="para">
+ Uninstallation start
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpm.RPMCALLBACK_UNINST_STOP
+ </div>
+
+ </td><td>
+ <div class="para">
+ Uninstallation stop
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpm.RPMCALLBACK_REPACKAGE_PROGRESS
+ </div>
+
+ </td><td>
+ <div class="para">
+ Repackaging progress
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpm.RPMCALLBACK_REPACKAGE_START
+ </div>
+
+ </td><td>
+ <div class="para">
+ Repackaging start
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpm.RPMCALLBACK_REPACKAGE_STOP
+ </div>
+
+ </td><td>
+ <div class="para">
+ Repackaging stop
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpm.RPMCALLBACK_UNPACK_ERROR
+ </div>
+
+ </td><td>
+ <div class="para">
+ Error unpacking package file
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ rpm.RPMCALLBACK_CPIO_ERROR
+ </div>
+
+ </td><td>
+ <div class="para">
+ cpio error getting package payload
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ Your callback must handle at least two cases: a reason value of rpm.RPMCALLBACK_INST_OPEN_FILE and rpm.RPMCALLBACK_INST_CLOSE_FILE.
+ </div><div class="para">
+ With the reason of rpm.RPMCALLBACK_INST_OPEN_FILE, you must open the RPM package file and return a file descriptor for the file. You need to keep this file descriptor in a global-scope or otherwise-accessible variable, because with the reason of rpm.RPMCALLBACK_INST_CLOSE_FILE, you must close this file.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch16s06s03s03.html"><strong>Înapoi</strong>16.6.3.3. Reordering the Transaction Set</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch16s06s04s02.html"><strong>Înainte</strong>16.6.4.2. Coding A Sample Callback</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch16s06s04s02.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch16s06s04s02.html
new file mode 100644
index 0000000..c1a82d0
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch16s06s04s02.html
@@ -0,0 +1,40 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>16.6.4.2. Coding A Sample Callback</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch16s06s04.html" title="16.6.4. Running the transaction" /><link rel="prev" href="ch16s06s04.html" title="16.6.4. Running the transaction" /><link rel="next" href="ch16s06s04s03.html" title="16.6.4.3. Upgrading A Package" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch16s06s04.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch16s06s04s03.html"><s
trong>ÃŽnainte</strong></a></li></ul><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id567507" class="title">Coding A Sample Callback</h1></div></div></div><div class="para">
+ The following code shows a valid sample callback for upgrading and installing packages.
+ </div><div class="para">
+ # Global file descriptor for the callback.
+ </div><div class="para">
+ rpmtsCallback_fd = None
+ </div><div class="para">
+ </div><div class="para">
+ </div><div class="para">
+ def runCallback(reason, amount, total, key, client_data):
+ </div><div class="para">
+ </div><div class="para">
+ global rpmtsCallback_fd
+ </div><div class="para">
+ </div><div class="para">
+ if reason == rpm.RPMCALLBACK_INST_OPEN_FILE:
+ </div><div class="para">
+ print "Opening file. ", reason, amount, total, key, client_data
+ </div><div class="para">
+ rpmtsCallback_fd = os.open(client_data, os.O_RDONLY)
+ </div><div class="para">
+ return rpmtsCallback_fd
+ </div><div class="para">
+ elif reason == rpm.RPMCALLBACK_INST_START:
+ </div><div class="para">
+ print "Closing file. ", reason, amount, total, key, client_data
+ </div><div class="para">
+ os.close(rpmtsCallback_fd)
+ </div><div class="para">
+ This callback assumes that the call to addInstall passed client data of the package file name. This callback ignores the client_data passed to the run method, but this is a perfect slot for passing an object. You can use this, for example, to avoid having a global variable for the file descriptor.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch16s06s04.html"><strong>Înapoi</strong>16.6.4. Running the transaction</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch16s06s04s03.html"><strong>Înainte</strong>16.6.4.3. Upgrading A Package</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch16s06s04s03.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch16s06s04s03.html
new file mode 100644
index 0000000..436ea22
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch16s06s04s03.html
@@ -0,0 +1,236 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>16.6.4.3. Upgrading A Package</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch16s06s04.html" title="16.6.4. Running the transaction" /><link rel="prev" href="ch16s06s04s02.html" title="16.6.4.2. Coding A Sample Callback" /><link rel="next" href="ch16s07.html" title="16.7. Where to Go from Here" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch16s06s04s02.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch16s07.html"><strong
>ÃŽnainte</strong></a></li></ul><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id844006" class="title">Upgrading A Package</h1></div></div></div><div class="para">
+ Listing 17-7 shows a simple Python script to upgrade or install a package.
+ </div><div class="para">
+ Listing 17-7: rpmupgrade.py
+ </div><div class="para">
+ #!/usr/bin/python
+ </div><div class="para">
+ </div><div class="para">
+ # Upgrades packages passed on the command line.
+ </div><div class="para">
+ # Usage:
+ </div><div class="para">
+ # python rpmupgrade.py rpm_file1.rpm rpm_file2.rpm ...
+ </div><div class="para">
+ #
+ </div><div class="para">
+ import rpm, os, sys
+ </div><div class="para">
+ </div><div class="para">
+ # Global file descriptor for the callback.
+ </div><div class="para">
+ rpmtsCallback_fd = None
+ </div><div class="para">
+ </div><div class="para">
+ </div><div class="para">
+ def runCallback(reason, amount, total, key, client_data):
+ </div><div class="para">
+ </div><div class="para">
+ global rpmtsCallback_fd
+ </div><div class="para">
+ </div><div class="para">
+ if reason == rpm.RPMCALLBACK_INST_OPEN_FILE:
+ </div><div class="para">
+ print "Opening file. ", reason, amount, total, key, client_data
+ </div><div class="para">
+ rpmtsCallback_fd = os.open(key, os.O_RDONLY)
+ </div><div class="para">
+ return rpmtsCallback_fd
+ </div><div class="para">
+ elif reason == rpm.RPMCALLBACK_INST_START:
+ </div><div class="para">
+ print "Closing file. ", reason, amount, total, key, client_data
+ </div><div class="para">
+ os.close(rpmtsCallback_fd)
+ </div><div class="para">
+ </div><div class="para">
+ </div><div class="para">
+ def checkCallback(ts, TagN, N, EVR, Flags):
+ </div><div class="para">
+ </div><div class="para">
+ if TagN == rpm.RPMTAG_REQUIRENAME:
+ </div><div class="para">
+ prev = ""
+ </div><div class="para">
+ Nh = None
+ </div><div class="para">
+ </div><div class="para">
+ if N[0] == '/':
+ </div><div class="para">
+ dbitag = 'basenames'
+ </div><div class="para">
+ else:
+ </div><div class="para">
+ dbitag = 'providename'
+ </div><div class="para">
+ </div><div class="para">
+ # What do you need to do.
+ </div><div class="para">
+ if EVR:
+ </div><div class="para">
+ print "Must find package [", N, "-", EVR, "]"
+ </div><div class="para">
+ else:
+ </div><div class="para">
+ print "Must find file [", N, "]"
+ </div><div class="para">
+ </div><div class="para">
+ if resolved:
+ </div><div class="para">
+ # ts.addIntall(h, h, 'i')
+ </div><div class="para">
+ </div><div class="para">
+ return -1
+ </div><div class="para">
+ </div><div class="para">
+ return 1
+ </div><div class="para">
+ </div><div class="para">
+ </div><div class="para">
+ </div><div class="para">
+ def readRpmHeader(ts, filename):
+ </div><div class="para">
+ """ Read an rpm header. """
+ </div><div class="para">
+ fd = os.open(filename, os.O_RDONLY)
+ </div><div class="para">
+ </div><div class="para">
+ h = ts.hdrFromFdno(fd)
+ </div><div class="para">
+ </div><div class="para">
+ os.close(fd)
+ </div><div class="para">
+ return h
+ </div><div class="para">
+ </div><div class="para">
+ </div><div class="para">
+ ts = rpm.TransactionSet()
+ </div><div class="para">
+ </div><div class="para">
+ # Set to not verify DSA signatures.
+ </div><div class="para">
+ ts.setVSFlags(-1)
+ </div><div class="para">
+ </div><div class="para">
+ for filename in sys.argv[1:]:
+ </div><div class="para">
+ h = readRpmHeader(ts, filename)
+ </div><div class="para">
+ print "Upgrading %s-%s-%s" % (h['name'], h['version'], h['release'])
+ </div><div class="para">
+ ts.addInstall(h, filename, 'u')
+ </div><div class="para">
+ </div><div class="para">
+ </div><div class="para">
+ unresolved_dependencies = ts.check(checkCallback)
+ </div><div class="para">
+ </div><div class="para">
+ if not unresolved_dependencies:
+ </div><div class="para">
+ ts.order()
+ </div><div class="para">
+ </div><div class="para">
+ print "This upgrade will install:"
+ </div><div class="para">
+ for te in ts:
+ </div><div class="para">
+ print "%s-%s-%s" % (te.N(), te.V(), te.R())
+ </div><div class="para">
+ </div><div class="para">
+ print "Running transaction (final step)..."
+ </div><div class="para">
+ ts.run(runCallback, 1)
+ </div><div class="para">
+ else:
+ </div><div class="para">
+ print "Error: Unresolved dependencies, transaction failed."
+ </div><div class="para">
+ print unresolved_dependencies
+ </div><div class="para">
+ This script expects the name of an RPM package file on the command line, and attempts to upgrade the package. (This will also install new packages.)
+ </div><div class="para">
+ When you run the rpmupgrade.py script, you should see output like the following:
+ </div><div class="para">
+ # rpm -q jikes
+ </div><div class="para">
+ jikes-1.17-1
+ </div><div class="para">
+ </div><div class="para">
+ # python rpmupgrade.py jikes-1.18-1.i386.rpm
+ </div><div class="para">
+ Upgrading jikes-1.18-1
+ </div><div class="para">
+ This upgrade will install:
+ </div><div class="para">
+ jikes-1.18-1
+ </div><div class="para">
+ jikes-1.17-1
+ </div><div class="para">
+ Running transaction (final step)...
+ </div><div class="para">
+ Opening file. 4 0 0 jikes-1.18-1.i386.rpm 1
+ </div><div class="para">
+ Closing file. 2 0 2854204 jikes-1.18-1.i386.rpm 1
+ </div><div class="para">
+ </div><div class="para">
+ # rpm -q jikes
+ </div><div class="para">
+ jikes-1.18-1
+ </div><div class="para">
+ This example shows that the package was upgraded after running the rpmupgrade.py script. Note that with an upgrade, the original package, jikes-1.17-1 in this case, is also added to the transaction set. With an install, this is not the case. That’s because the original package is removed as part of the transaction.
+ </div><div class="para">
+ If you run this script as a non-root user, you will likely see an error like the following:
+ </div><div class="para">
+ $ python rpmupgrade.py jikes-1.18-1.i386.rpm
+ </div><div class="para">
+ Upgrading jikes-1.18-1
+ </div><div class="para">
+ This upgrade will install:
+ </div><div class="para">
+ jikes-1.18-1
+ </div><div class="para">
+ jikes-1.17-1
+ </div><div class="para">
+ Running transaction (final step)...
+ </div><div class="para">
+ error: cannot get exclusive lock on /var/lib/rpm/Packages
+ </div><div class="para">
+ error: cannot open Packages index using db3 - Operation not permitted (1)
+ </div><div class="para">
+ error: cannot open Packages database in /var/lib/rpm
+ </div><div class="para">
+ If a package has a dependency on a file such as a shared library, you will see output like the following:
+ </div><div class="para">
+ # python rpmupgrade.py jikes-1.17-glibc2.2-1.i386.rpm jpilot-0_97-1_i386.rpm
+ </div><div class="para">
+ Upgrading jikes-1.17-1
+ </div><div class="para">
+ Upgrading jpilot-0.97-1
+ </div><div class="para">
+ Must find file [ libpisock.so.3 ]
+ </div><div class="para">
+ Error: Unresolved dependencies, transaction failed.
+ </div><div class="para">
+ (('jpilot', '0.97', '1'), ('libpisock.so.3', None), 0, None, 0)
+ </div><div class="para">
+ If a package has a dependency on another package, you will see output like the following:
+ </div><div class="para">
+ # python rpmupgrade.py eruby-devel-0.9.8-2.i386.rpm
+ </div><div class="para">
+ Upgrading eruby-devel-0.9.8-2
+ </div><div class="para">
+ Must find package [ eruby-libs - 0.9.8 ]
+ </div><div class="para">
+ Error: Unresolved dependencies, transaction failed.
+ </div><div class="para">
+ (('eruby-devel', '0.9.8', '2'), ('eruby-libs', '0.9.8'), 8, None, 0)
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch16s06s04s02.html"><strong>Înapoi</strong>16.6.4.2. Coding A Sample Callback</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch16s07.html"><strong>Înainte</strong>16.7. Where to Go from Here</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch16s07.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch16s07.html
new file mode 100644
index 0000000..a477cde
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch16s07.html
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>16.7. Where to Go from Here</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-rpm-programming-python.html" title="Cap. 16. Programming RPM with Python" /><link rel="prev" href="ch16s06s04s03.html" title="16.6.4.3. Upgrading A Package" /><link rel="next" href="ch16s08.html" title="16.8. Summary" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch16s06s04s03.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch16s08.html"><stron
g>ÃŽnainte</strong></a></li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id588092" class="title">Where to Go from Here</h1></div></div></div><div class="para">
+ The RPM bindings for Python are documented along with the C programming API. On a Red Hat Linux system, look in the file /usr/share/doc/rpm-devel-4.1/apidocs/html/group__python.html to see the start of the Python-specific documentation.
+ </div><div class="para">
+ Note that much of this online documentation covers the C functions that provide the Python bindings, not the Python API itself. But, if you examine the online information on objects listed as classes, such as rpmts, you can find the Python-specific documentation.
+ </div><div class="para">
+ Furthermore, if you look into the .c files that make up the Python bindings, you can find PyMethodDef structure tables. These tables provide useful glimpses into the Python API.
+ </div><div class="para">
+ To learn more about programming in Python, install the python-docs package. The python-docs package has a large set of online documentation for Python, including the official Python Tutorial. With Red Hat Linux, start at /usr/share/doc/python-docs-2.2.1/html/tut/tut.html.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ Other tutorials are available at http://diveintopython.org for the Dive Into Python tutorial for experienced programmers, and at http://py.vaults.ca/parnassus/apyllo.py/935043691.636055170 for the Vaults of Parnassus listing of tutorials.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch16s06s04s03.html"><strong>Înapoi</strong>16.6.4.3. Upgrading A Package</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch16s08.html"><strong>Înainte</strong>16.8. Summary</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch16s08.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch16s08.html
new file mode 100644
index 0000000..6a6870d
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch16s08.html
@@ -0,0 +1,20 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>16.8. Summary</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-rpm-programming-python.html" title="Cap. 16. Programming RPM with Python" /><link rel="prev" href="ch16s07.html" title="16.7. Where to Go from Here" /><link rel="next" href="ch-programming-perl.html" title="Cap. 17. Programming RPM with Perl" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch16s07.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="c
h-programming-perl.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id802812" class="title">Summary</h1></div></div></div><div class="para">
+ This chapter introduces the high-level RPM API for Python programming. You can use this API from Python scripts to perform RPM functionality, just as you can write C programs using the RPM C API covered in <a class="xref" href="ch-programming-c.html">Cap. 15, <em>Programming RPM with C</em></a> .
+ </div><div class="para">
+ In general, the Python API is simpler and requires fewer code statements than the corresponding functionality in the C API.
+ </div><div class="para">
+ Just about all of your work with the Python API requires a transaction set, which you can get by calling rpm.TransactionSet.
+ </div><div class="para">
+ To query the RPM database, call dbMatch on the transaction set object. To install or upgrade packages, call addInstall, check, order, and run on the transaction set.
+ </div><div class="para">
+ The next chapter switches to another language for accessing the RPM system: Perl. With the rich set of APIs, you can write your RPM programs in C, Python, Perl, or any language that can call on code written in one of these languages.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch16s07.html"><strong>Înapoi</strong>16.7. Where to Go from Here</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch-programming-perl.html"><strong>Înainte</strong>Cap. 17. Programming RPM with Perl</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch17s02.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch17s02.html
new file mode 100644
index 0000000..b6f27a4
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch17s02.html
@@ -0,0 +1,24 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>17.2. Working with RPM Files</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-programming-perl.html" title="Cap. 17. Programming RPM with Perl" /><link rel="prev" href="ch-programming-perl.html" title="Cap. 17. Programming RPM with Perl" /><link rel="next" href="ch17s02s02.html" title="17.2.2. Listing tags from the package" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-programming-perl.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a acce
sskey="n" href="ch17s02s02.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id532269" class="title">Working with RPM Files</h1></div></div></div><div class="para">
+ The RPM2 module provides a top-level object, RPM2, that acts as an entry point into the module. From the RPM2 object, you either open the RPM database, covered in the "Programming with the RPM Database" section, or open an RPM package file, covered here.
+ </div><div class="para">
+ The first step in working with an RPM file is to open the file inside a Perl script.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id675588" class="title">Opening package files</h1></div></div></div><div class="para">
+ The open_package subroutine opens an RPM package file and returns a header object (an RPM2::Header). The basic syntax follows:
+ </div><div class="para">
+ my $header = RPM2->open_package( $filename );
+ </div><div class="para">
+ For example:
+ </div><div class="para">
+ my $header = RPM2->open_package("jikes-1.14-1-glibc-2.2.i386.rpm");
+ </div><div class="para">
+ After you’ve opened a package, you can perform a number of query operations on the header object returned by the open_package subroutine.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-programming-perl.html"><strong>Înapoi</strong>Cap. 17. Programming RPM with Perl</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch17s02s02.html"><strong>Înainte</strong>17.2.2. Listing tags from the package</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch17s02s02.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch17s02s02.html
new file mode 100644
index 0000000..3223332
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch17s02s02.html
@@ -0,0 +1,61 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>17.2.2. Listing tags from the package</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch17s02.html" title="17.2. Working with RPM Files" /><link rel="prev" href="ch17s02.html" title="17.2. Working with RPM Files" /><link rel="next" href="ch17s02s03.html" title="17.2.3. Convenience methods" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch17s02.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch17s02s03.html"><strong>ÃŽnainte</strong>
</a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id675617" class="title">Listing tags from the package</h1></div></div></div><div class="para">
+ Each RPM package has information stored under a variety of tags, such as the package name under the NAME tag and the package long description under the DESCRIPTION tag.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ These are the same tags introduced with the --queryformat option to the rpm command discussed in <a class="xref" href="ch-using-rpm-db.html">Cap. 4, <em>Using the RPM Database</em></a> .
+ </div><div class="para">
+ The tag subroutine returns the value of a given tag. For example, to get the name of the package, use the NAME tag:
+ </div><div class="para">
+ use RPM2;
+ </div><div class="para">
+ </div><div class="para">
+ my $header = RPM2->open_package("jikes-1.14-1-glibc-2.2.i386.rpm" );
+ </div><div class="para">
+ </div><div class="para">
+ print $header->tag("NAME"), "\n";
+ </div><div class="para">
+ Pulling this together, Listing 18-1 shows example script that lists the name and one-line short summary of a package file.
+ </div><div class="para">
+ Listing 18-1: rpmsum.pl
+ </div><div class="para">
+ #!/usr/bin/perl
+ </div><div class="para">
+ </div><div class="para">
+ #
+ </div><div class="para">
+ # Lists summary from an RPM package file
+ </div><div class="para">
+ # Usage:
+ </div><div class="para">
+ # rpmsum.pl package_name.rpm
+ </div><div class="para">
+ #
+ </div><div class="para">
+ use strict;
+ </div><div class="para">
+ use RPM2;
+ </div><div class="para">
+ </div><div class="para">
+ my $header = RPM2->open_package( $ARGV[0] );
+ </div><div class="para">
+ </div><div class="para">
+ print $header->tag("NAME"), ": ", $header->tag("SUMMARY"), "\n";
+ </div><div class="para">
+ Enter this script and name the file rpmsum.pl.
+ </div><div class="para">
+ When you run this script, you need to pass the name of a package file on the command line. For example:
+ </div><div class="para">
+ $ ./rpmsum.pl jikes-1.14-1-glibc-2.2.i386.rpm
+ </div><div class="para">
+ jikes: java source to bytecode compiler
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch17s02.html"><strong>Înapoi</strong>17.2. Working with RPM Files</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch17s02s03.html"><strong>Înainte</strong>17.2.3. Convenience methods</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch17s02s03.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch17s02s03.html
new file mode 100644
index 0000000..2eb44ae
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch17s02s03.html
@@ -0,0 +1,14 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>17.2.3. Convenience methods</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch17s02.html" title="17.2. Working with RPM Files" /><link rel="prev" href="ch17s02s02.html" title="17.2.2. Listing tags from the package" /><link rel="next" href="ch17s02s04.html" title="17.2.4. Listing the name and version" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch17s02s02.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch17s02s04.html"><
strong>ÃŽnainte</strong></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id811528" class="title">Convenience methods</h1></div></div></div><div class="para">
+ The RPM2 module includes convenience methods for all RPM tags. This means you can use the method name in place of tag("NAME"). For example:
+ </div><div class="para">
+ print $header->name(), ": ", $header->summary(), "\n";
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch17s02s02.html"><strong>Înapoi</strong>17.2.2. Listing tags from the package</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch17s02s04.html"><strong>Înainte</strong>17.2.4. Listing the name and version</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch17s02s04.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch17s02s04.html
new file mode 100644
index 0000000..fe2abba
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch17s02s04.html
@@ -0,0 +1,24 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>17.2.4. Listing the name and version</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch17s02.html" title="17.2. Working with RPM Files" /><link rel="prev" href="ch17s02s03.html" title="17.2.3. Convenience methods" /><link rel="next" href="ch17s02s05.html" title="17.2.5. Checking whether the package is a source package" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch17s02s03.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch17s02s
05.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id811545" class="title">Listing the name and version</h1></div></div></div><div class="para">
+ The RPM2 module provides a handy subroutine for getting the NAME, VERSION, RELEASE, and EPOCH tags, often abbreviated as NVRE. The subroutine, as_nvre, returns a single string with these values in the standard format, with the values separated by minus signs.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ Usually, the EPOCH tag has no value. If there is an EPOCH value, you will see it output first, and then a colon, and then the name, version, and release values. For example:
+ </div><div class="para">
+ 5:redhat-config-httpd-1.0.1-13
+ </div><div class="para">
+ In this case, the EPOCH value is 5.
+ </div><div class="para">
+ You can call this subroutine on any header object, or any package object to get the full name of the package. For example:
+ </div><div class="para">
+ print $header->as_nvre(), "\n";
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch17s02s03.html"><strong>Înapoi</strong>17.2.3. Convenience methods</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch17s02s05.html"><strong>Înainte</strong>17.2.5. Checking whether the package is a source ...</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch17s02s05.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch17s02s05.html
new file mode 100644
index 0000000..7a0a0d5
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch17s02s05.html
@@ -0,0 +1,49 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>17.2.5. Checking whether the package is a source package</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch17s02.html" title="17.2. Working with RPM Files" /><link rel="prev" href="ch17s02s04.html" title="17.2.4. Listing the name and version" /><link rel="next" href="ch17s03.html" title="17.3. Programming with the RPM Database" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch17s02s04.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch17s03.html"><stro
ng>ÃŽnainte</strong></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id768239" class="title">Checking whether the package is a source package</h1></div></div></div><div class="para">
+ Another handy subroutine tells you if an RPM file represents a source RPM or a binary RPM. The is_source_package subroutine returns a true value if the package is a source package, and a false value otherwise.
+ </div><div class="para">
+ The rpmpkg.pl script, shown in Listing 18-2, shows how to use the as_nvre and is_source_package subroutines.
+ </div><div class="para">
+ Listing 18-2: rpmpkg.pl
+ </div><div class="para">
+ #!/usr/bin/perl
+ </div><div class="para">
+ </div><div class="para">
+ #
+ </div><div class="para">
+ # Queries RPM package file and prints
+ </div><div class="para">
+ # out name and whether this is a source pkg.
+ </div><div class="para">
+ # Usage:
+ </div><div class="para">
+ # rpmpkg.pl package_name
+ </div><div class="para">
+ #
+ </div><div class="para">
+ use strict;
+ </div><div class="para">
+ use RPM2;
+ </div><div class="para">
+ </div><div class="para">
+ my $header = RPM2->open_package( $ARGV[0] );
+ </div><div class="para">
+ </div><div class="para">
+ if ( $header->is_source_package() ) {
+ </div><div class="para">
+ print "Source package ", $header->as_nvre(), "\n";
+ </div><div class="para">
+ } else {
+ </div><div class="para">
+ print $header->as_nvre(), "\n";
+ </div><div class="para">
+ }
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch17s02s04.html"><strong>Înapoi</strong>17.2.4. Listing the name and version</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch17s03.html"><strong>Înainte</strong>17.3. Programming with the RPM Database</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch17s03.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch17s03.html
new file mode 100644
index 0000000..affcf69
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch17s03.html
@@ -0,0 +1,28 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>17.3. Programming with the RPM Database</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-programming-perl.html" title="Cap. 17. Programming RPM with Perl" /><link rel="prev" href="ch17s02s05.html" title="17.2.5. Checking whether the package is a source package" /><link rel="next" href="ch17s03s02.html" title="17.3.2. Finding packages" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch17s02s05.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n"
href="ch17s03s02.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id668261" class="title">Programming with the RPM Database</h1></div></div></div><div class="para">
+ In addition to providing query routines for RPM files, you can also access the RPM database with the RPM2 package.
+ </div><div class="para">
+ To access the RPM database, your Perl script must first open the database.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id668276" class="title">Opening the database</h1></div></div></div><div class="para">
+ Open the RPM database with a call to open_rpm_db on the RPM2 object. For example:
+ </div><div class="para">
+ my $rpm_db = RPM2->open_rpm_db();
+ </div><div class="para">
+ You can also specify the directory where the RPM database resides. This is most useful for accessing a database in a non-standard location. For example:
+ </div><div class="para">
+ my $rpm_db = RPM2->open_rpm_db( "-path" => "/var/lib/rpm" );
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ The -path is normally used as a Perl bareword but is shown here as a string.
+ </div><div class="para">
+ Once you have an RPM database object, you can call one of the find subroutines to find packages in most of the same ways as supported by the rpm –q command.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch17s02s05.html"><strong>Înapoi</strong>17.2.5. Checking whether the package is a source ...</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch17s03s02.html"><strong>Înainte</strong>17.3.2. Finding packages</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch17s03s02.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch17s03s02.html
new file mode 100644
index 0000000..bf14ac1
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch17s03s02.html
@@ -0,0 +1,14 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>17.3.2. Finding packages</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch17s03.html" title="17.3. Programming with the RPM Database" /><link rel="prev" href="ch17s03.html" title="17.3. Programming with the RPM Database" /><link rel="next" href="ch17s03s03.html" title="17.3.3. Iterating over packages" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch17s03.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch17s03s03.html"
><strong>ÃŽnainte</strong></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id561077" class="title">Finding packages</h1></div></div></div><div class="para">
+ The find_by_name subroutine finds a package or packages by name. It returns a Perl list of the entries found. For example, if you installed more than one version of a package, find_by_name would return a list of all the packages at the different versions.
+ </div><div class="para">
+ Similar to find_by_name, find_by_name_iter returns an iterator to iterate over the packages that match the query. The iterator approach is usually more efficient.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch17s03.html"><strong>Înapoi</strong>17.3. Programming with the RPM Database</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch17s03s03.html"><strong>Înainte</strong>17.3.3. Iterating over packages</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch17s03s03.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch17s03s03.html
new file mode 100644
index 0000000..d05a677
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch17s03s03.html
@@ -0,0 +1,68 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>17.3.3. Iterating over packages</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch17s03.html" title="17.3. Programming with the RPM Database" /><link rel="prev" href="ch17s03s02.html" title="17.3.2. Finding packages" /><link rel="next" href="ch17s03s04.html" title="17.3.4. Additional query subroutines" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch17s03s02.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch17s03s04.html"><st
rong>ÃŽnainte</strong></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id561097" class="title">Iterating over packages</h1></div></div></div><div class="para">
+ Iterators are important in the RPM2 package because they provide a more efficient interface to potentially large sets of packages, and because iterators more closely match the underlying C API. Furthermore, iterators are very easy to use. Simply call the next subroutine to move ahead to the next element, that is, the next package.
+ </div><div class="para">
+ For example:
+ </div><div class="para">
+ my $pkg_iter = $rpm_db->find_by_name_iter( "kernel" );
+ </div><div class="para">
+ </div><div class="para">
+ while (my $pkg = $pkg_iter->next() ) {
+ </div><div class="para">
+ </div><div class="para">
+ # Do something ...
+ </div><div class="para">
+ }
+ </div><div class="para">
+ Listing 18-3 shows a script that acts much like the rpm –q command, without any other command-line options.
+ </div><div class="para">
+ Listing 18-3: rpmname.pl
+ </div><div class="para">
+ #!/usr/bin/perl
+ </div><div class="para">
+ </div><div class="para">
+ #
+ </div><div class="para">
+ # Queries RPM database for given package.
+ </div><div class="para">
+ # Usage:
+ </div><div class="para">
+ # rpmname.pl package_name
+ </div><div class="para">
+ #
+ </div><div class="para">
+ use strict;
+ </div><div class="para">
+ use RPM2;
+ </div><div class="para">
+ </div><div class="para">
+ my $rpm_db = RPM2->open_rpm_db( "−path" => "/var/lib/rpm" );
+ </div><div class="para">
+ </div><div class="para">
+ my $pkg_iter = $rpm_db->find_by_name_iter( $ARGV[0] );
+ </div><div class="para">
+ </div><div class="para">
+ while (my $pkg = $pkg_iter->next() ) {
+ </div><div class="para">
+ </div><div class="para">
+ print $pkg->tag("NAME"), "-", $pkg->tag("VERSION"), "\n";
+ </div><div class="para">
+ }
+ </div><div class="para">
+ </div><div class="para">
+ $rpm_db->close_rpm_db();
+ </div><div class="para">
+ When you run this script, you need to pass the name of a package to query. For example:
+ </div><div class="para">
+ $ ./rpmname.pl kernel
+ </div><div class="para">
+ kernel-2.4.18
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch17s03s02.html"><strong>Înapoi</strong>17.3.2. Finding packages</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch17s03s04.html"><strong>Înainte</strong>17.3.4. Additional query subroutines</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch17s03s04.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch17s03s04.html
new file mode 100644
index 0000000..87c17c8
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch17s03s04.html
@@ -0,0 +1,231 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>17.3.4. Additional query subroutines</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch17s03.html" title="17.3. Programming with the RPM Database" /><link rel="prev" href="ch17s03s03.html" title="17.3.3. Iterating over packages" /><link rel="next" href="ch17s03s05.html" title="17.3.5. Getting information on packages" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch17s03s03.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch17s03s05
.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id671970" class="title">Additional query subroutines</h1></div></div></div><div class="para">
+ The find_by_name_iter subroutine finds a package by its name. The RPM2 module also supports a number of other query routines, listed in Table 18-1.
+ </div><div class="para">
+ Table 18-1 RPM2 module query routines
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Routine
+ </div>
+
+ </td><td>
+ <div class="para">
+ Usage
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ find_all()
+ </div>
+
+ </td><td>
+ <div class="para">
+ Returns a list with all the packages in the database
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ find_all_iter()
+ </div>
+
+ </td><td>
+ <div class="para">
+ Returns an iterator over all the packages in the database
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ find_by_file($filename)
+ </div>
+
+ </td><td>
+ <div class="para">
+ Finds all packages that own the given file, returning a list
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ find_by_file_iter($filename)
+ </div>
+
+ </td><td>
+ <div class="para">
+ Finds all packages that own the given file, returning an iterator
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ find_by_name($package_name)
+ </div>
+
+ </td><td>
+ <div class="para">
+ Finds all packages with the given name, returning a list
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ find_by_name_iter($package_name)
+ </div>
+
+ </td><td>
+ <div class="para">
+ Finds all packages with the given name, returning an iterator
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ find_by_provides($capability)
+ </div>
+
+ </td><td>
+ <div class="para">
+ Finds all packages that provide the given capability, returning a list
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ find_by_provides_iter($capability)
+ </div>
+
+ </td><td>
+ <div class="para">
+ Finds all packages that provide the given capability, returning an iterator
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ find_by_requires($capability)
+ </div>
+
+ </td><td>
+ <div class="para">
+ Finds all packages that require the given capability, returning a list
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ find_by_requires_iter($capability)
+ </div>
+
+ </td><td>
+ <div class="para">
+ Finds all packages that require the given capability, returning an iterator
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ To verify the find routines, you can try the following script and compare the results with the rpm command. Listing 18-4 shows the script that finds what package provides a capability and also which packages require the capability.
+ </div><div class="para">
+ Listing 18-4: rpmprovides.pl
+ </div><div class="para">
+ #!/usr/bin/perl
+ </div><div class="para">
+ </div><div class="para">
+ #
+ </div><div class="para">
+ # Queries RPM database for given package,
+ </div><div class="para">
+ # listing what it provides and what other
+ </div><div class="para">
+ # packages require the capability.
+ </div><div class="para">
+ #
+ </div><div class="para">
+ # Usage:
+ </div><div class="para">
+ # rpmprovides.pl package_name
+ </div><div class="para">
+ #
+ </div><div class="para">
+ use strict;
+ </div><div class="para">
+ use RPM2;
+ </div><div class="para">
+ </div><div class="para">
+ my $rpm_db = RPM2->open_rpm_db();
+ </div><div class="para">
+ </div><div class="para">
+ my $pkg_iter = $rpm_db->find_by_provides_iter( $ARGV[0] );
+ </div><div class="para">
+ </div><div class="para">
+ print "Provides: ", $ARGV[0], "\n";
+ </div><div class="para">
+ </div><div class="para">
+ while (my $pkg = $pkg_iter->next() ) {
+ </div><div class="para">
+ print "\t", $pkg->as_nvre(), "\n";
+ </div><div class="para">
+ }
+ </div><div class="para">
+ </div><div class="para">
+ </div><div class="para">
+ # Now, what packages require this capability.
+ </div><div class="para">
+ </div><div class="para">
+ my $pkg_iter2 = $rpm_db->find_by_requires_iter( $ARGV[0] );
+ </div><div class="para">
+ </div><div class="para">
+ print "Requires: ", $ARGV[0], "\n";
+ </div><div class="para">
+ while (my $pkg2 = $pkg_iter2->next() ) {
+ </div><div class="para">
+ print "\t", $pkg2->as_nvre(), "\n";
+ </div><div class="para">
+ }
+ </div><div class="para">
+ </div><div class="para">
+ $rpm_db->close_rpm_db();
+ </div><div class="para">
+ When you run this script with the name of a capability, you'll see output like the following:
+ </div><div class="para">
+ $ ./rpmprovides.pl httpd
+ </div><div class="para">
+ Provides: httpd
+ </div><div class="para">
+ httpd-2.0.40-8
+ </div><div class="para">
+ Requires: httpd
+ </div><div class="para">
+ mod_perl-1.99_05-3
+ </div><div class="para">
+ 5:redhat-config-httpd-1.0.1-13
+ </div><div class="para">
+ mod_python-3.0.0-10
+ </div><div class="para">
+ 1:mod_ssl-2.0.40-8
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ The 5: in 5:redhat-config-httpd-1.0.1-13 and 1: in 1:mod_ssl-2.0.40-8 represent the EPOCH tag value.
+ </div><div class="para">
+ To verify this script, run the rpm -q command to see if you get the same packages listed. For example:
+ </div><div class="para">
+ $ rpm -q --whatprovides httpd
+ </div><div class="para">
+ httpd-2.0.40-8
+ </div><div class="para">
+ </div><div class="para">
+ $ rpm -q --whatrequires httpd
+ </div><div class="para">
+ mod_perl-1.99_05-3
+ </div><div class="para">
+ redhat-config-httpd-1.0.1-13
+ </div><div class="para">
+ mod_python-3.0.0-10
+ </div><div class="para">
+ mod_ssl-2.0.40-8
+ </div><div class="para">
+ In both cases, you see the same packages listed. You can use this technique to verify your scripts.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ The find_by_provides_iter subroutine requires the name of a package, such as bash. You cannot pass a file name, such as /bin/bash, to get the name of the package that provides this capability (a file, really).
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch17s03s03.html"><strong>Înapoi</strong>17.3.3. Iterating over packages</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch17s03s05.html"><strong>Înainte</strong>17.3.5. Getting information on packages</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch17s03s05.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch17s03s05.html
new file mode 100644
index 0000000..073c004
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch17s03s05.html
@@ -0,0 +1,167 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>17.3.5. Getting information on packages</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch17s03.html" title="17.3. Programming with the RPM Database" /><link rel="prev" href="ch17s03s04.html" title="17.3.4. Additional query subroutines" /><link rel="next" href="ch17s03s05s02.html" title="17.3.5.2. Handling String Array Tags" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch17s03s04.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch17s
03s05s02.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id638984" class="title">Getting information on packages</h1></div></div></div><div class="para">
+ The tag, as_nvre, and is_source_package subroutines that worked on header objects read from RPM files, shown previously, also work with package entries returned from the RPM database.
+ </div><div class="para">
+ For example, Listing 18-5 shows a script, rpminfo.pl, that prints out descriptive information about a given package.
+ </div><div class="para">
+ Listing 18-5: rpminfo.pl
+ </div><div class="para">
+ #!/usr/bin/perl
+ </div><div class="para">
+ </div><div class="para">
+ #
+ </div><div class="para">
+ # Queries RPM database for given package and prints info.
+ </div><div class="para">
+ # Usage:
+ </div><div class="para">
+ # rpminfo.pl package_name
+ </div><div class="para">
+ #
+ </div><div class="para">
+ use strict;
+ </div><div class="para">
+ use RPM2;
+ </div><div class="para">
+ </div><div class="para">
+ my $rpm_db = RPM2->open_rpm_db( "-path" => "/var/lib/rpm" );
+ </div><div class="para">
+ </div><div class="para">
+ my $pkg_iter = $rpm_db->find_by_name_iter( $ARGV[0] );
+ </div><div class="para">
+ </div><div class="para">
+ while (my $pkg = $pkg_iter->next() ) {
+ </div><div class="para">
+ </div><div class="para">
+ printInfo( $pkg );
+ </div><div class="para">
+ }
+ </div><div class="para">
+ </div><div class="para">
+ $rpm_db->close_rpm_db();
+ </div><div class="para">
+ </div><div class="para">
+ </div><div class="para">
+ # Prints info on one package.
+ </div><div class="para">
+ sub printInfo {
+ </div><div class="para">
+ my($pkg) = shift;
+ </div><div class="para">
+ </div><div class="para">
+ print $pkg->as_nvre(), ", ", $pkg->tag("ARCH"), ", ",
+ </div><div class="para">
+ $pkg->tag("OS"), ", ", $pkg->tag("PLATFORM"), "\n";
+ </div><div class="para">
+ </div><div class="para">
+ print $pkg->tag("SUMMARY"), "\n";
+ </div><div class="para">
+ print "Group: ", $pkg->tag("GROUP"), "\n";
+ </div><div class="para">
+ print $pkg->tag("DESCRIPTION"), "\n";
+ </div><div class="para">
+ print "Vendor: ", $pkg->tag("VENDOR"), ", ", $pkg->tag("URL"), "\n";
+ </div><div class="para">
+ print "Size: ", $pkg->tag("SIZE"), "\n";
+ </div><div class="para">
+ }
+ </div><div class="para">
+ When you run this script, you’ll see output like the following:
+ </div><div class="para">
+ $ ./rpminfo.pl XFree86
+ </div><div class="para">
+ XFree86-4.2.0-72, i386, linux, i386-redhat-linux-gnu
+ </div><div class="para">
+ The basic fonts, programs and docs for an X workstation.
+ </div><div class="para">
+ Group: User Interface/X
+ </div><div class="para">
+ XFree86 is an open source implementation of the X Window System. It
+ </div><div class="para">
+ provides the basic low level functionality which full fledged
+ </div><div class="para">
+ graphical user interfaces (GUIs) such as GNOME and KDE are designed
+ </div><div class="para">
+ upon.
+ </div><div class="para">
+ Vendor: Red Hat, Inc., http://www.xfree86.org
+ </div><div class="para">
+ Size: 30552239
+ </div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id572550" class="title">Listing the Installed Date</h1></div></div></div><div class="para">
+ The installed date is a number value representing the number of seconds since the start of the UNIX epoch, January 1, 1970, which predates the start of the Linux epoch by about 20 years. So, when you get the value of the INSTALLTIME tag, you’ll see a meaningless number.
+ </div><div class="para">
+ To make sense of this number, pass the value to the Perl localtime function. Listing 18-6 shows an example of this.
+ </div><div class="para">
+ Listing 18-6: rpmdate.pl
+ </div><div class="para">
+ #!/usr/bin/perl
+ </div><div class="para">
+ </div><div class="para">
+ #
+ </div><div class="para">
+ # Queries RPM database for given package,
+ </div><div class="para">
+ # prints out name, vendor, and date installed.
+ </div><div class="para">
+ # Usage:
+ </div><div class="para">
+ # rpmdate.pl package_name
+ </div><div class="para">
+ #
+ </div><div class="para">
+ use strict;
+ </div><div class="para">
+ use RPM2;
+ </div><div class="para">
+ </div><div class="para">
+ my $rpm_db = RPM2->open_rpm_db();
+ </div><div class="para">
+ </div><div class="para">
+ my $pkg_iter = $rpm_db->find_by_name_iter( $ARGV[0] );
+ </div><div class="para">
+ </div><div class="para">
+ while (my $pkg = $pkg_iter->next() ) {
+ </div><div class="para">
+ </div><div class="para">
+ printDate( $pkg );
+ </div><div class="para">
+ }
+ </div><div class="para">
+ </div><div class="para">
+ $rpm_db->close_rpm_db();
+ </div><div class="para">
+ </div><div class="para">
+ </div><div class="para">
+ </div><div class="para">
+ # Prints installation data for one package.
+ </div><div class="para">
+ sub printDate {
+ </div><div class="para">
+ my($pkg) = shift;
+ </div><div class="para">
+ </div><div class="para">
+ my $date = localtime( $pkg->tag("INSTALLTIME") );
+ </div><div class="para">
+ </div><div class="para">
+ printf("%-20s %-17s %s\n", $pkg->as_nvre(), $pkg->tag("VENDOR"), $date);
+ </div><div class="para">
+ }
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ The printf function in this script can do something the rpm command cannot do. Even with the --queryformat option, you cannot group multiple items and then set the size; with Perl, you can. Simply assign the multiple values to a string, or use the handy as_nvre subroutine, which gathers up to four tags together into one string.
+ </div><div class="para">
+ When you pass the name of a package to this script, you’ll see the date the package was installed. For example:
+ </div><div class="para">
+ $ ./rpmdate.pl kernel
+ </div><div class="para">
+ kernel-2.4.18-14 Red Hat, Inc. Sat Oct 5 12:29:58 2002
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch17s03s04.html"><strong>Înapoi</strong>17.3.4. Additional query subroutines</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch17s03s05s02.html"><strong>Înainte</strong>17.3.5.2. Handling String Array Tags</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch17s03s05s02.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch17s03s05s02.html
new file mode 100644
index 0000000..997f9fc
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch17s03s05s02.html
@@ -0,0 +1,77 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>17.3.5.2. Handling String Array Tags</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch17s03s05.html" title="17.3.5. Getting information on packages" /><link rel="prev" href="ch17s03s05.html" title="17.3.5. Getting information on packages" /><link rel="next" href="ch17s03s05s03.html" title="17.3.5.3. Listing the Files In A Package" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch17s03s05.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" h
ref="ch17s03s05s03.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id586670" class="title">Handling String Array Tags</h1></div></div></div><div class="para">
+ Not only is the date stored in a format that adds complication to your script. A number of tags are string arrays, not scalar strings. This means you may see output that is all mashed together.
+ </div><div class="para">
+ To help deal with this, the following subroutine takes in an array of strings and returns a string that is built using a passed-in delimiter:
+ </div><div class="para">
+ sub arrayToString {
+ </div><div class="para">
+ my($sep) = shift;
+ </div><div class="para">
+ my(@array) = @_;
+ </div><div class="para">
+ my($str);
+ </div><div class="para">
+ </div><div class="para">
+ $str = $array[0];
+ </div><div class="para">
+ </div><div class="para">
+ for ( $i = 1; $i < $#array; $i++ )
+ </div><div class="para">
+ {
+ </div><div class="para">
+ $str = $str . $sep . $array[$i];
+ </div><div class="para">
+ }
+ </div><div class="para">
+ </div><div class="para">
+ return $str;
+ </div><div class="para">
+ }
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ Show your Perl expertise and earn extra points by implementing the arrayToString subroutine as a single Perl statement that uses the join function.
+ </div><div class="para">
+ The following list shows the tags that are an array of strings:
+ </div><div class="para">
+ *BASENAMES
+ </div><div class="para">
+ *CHANGELOGNAME
+ </div><div class="para">
+ *CHANGELOGTEXT
+ </div><div class="para">
+ *DIRNAMES
+ </div><div class="para">
+ *FILEGROUPNAME
+ </div><div class="para">
+ *FILELANGS
+ </div><div class="para">
+ *FILELINKTOS
+ </div><div class="para">
+ *FILEMD5S
+ </div><div class="para">
+ *FILEUSERNAME
+ </div><div class="para">
+ *OLDFILENAMES
+ </div><div class="para">
+ *PROVIDENAME
+ </div><div class="para">
+ *PROVIDEVERSION
+ </div><div class="para">
+ *REQUIRENAME
+ </div><div class="para">
+ *REQUIREVERSION
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ <a class="xref" href="ch-using-rpm-db.html">Cap. 4, <em>Using the RPM Database</em></a> covers more on these tags.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch17s03s05.html"><strong>Înapoi</strong>17.3.5. Getting information on packages</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch17s03s05s03.html"><strong>Înainte</strong>17.3.5.3. Listing the Files In A Package</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch17s03s05s03.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch17s03s05s03.html
new file mode 100644
index 0000000..f74c01e
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch17s03s05s03.html
@@ -0,0 +1,103 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>17.3.5.3. Listing the Files In A Package</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch17s03s05.html" title="17.3.5. Getting information on packages" /><link rel="prev" href="ch17s03s05s02.html" title="17.3.5.2. Handling String Array Tags" /><link rel="next" href="ch17s03s06.html" title="17.3.6. Comparing versions" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch17s03s05s02.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch17s03s0
6.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id560060" class="title">Listing the Files In A Package</h1></div></div></div><div class="para">
+ The files subroutine provides a list of all the files in a package. Listing 18-7 shows how to access this list.
+ </div><div class="para">
+ Listing 18-7: rpmfiles.pl
+ </div><div class="para">
+ #!/usr/bin/perl
+ </div><div class="para">
+ </div><div class="para">
+ #
+ </div><div class="para">
+ # Queries RPM database for given package,
+ </div><div class="para">
+ # prints out the files in the package.
+ </div><div class="para">
+ # Usage:
+ </div><div class="para">
+ # rpmfiles.pl package_name
+ </div><div class="para">
+ #
+ </div><div class="para">
+ use strict;
+ </div><div class="para">
+ use RPM2;
+ </div><div class="para">
+ </div><div class="para">
+ my $rpm_db = RPM2->open_rpm_db();
+ </div><div class="para">
+ </div><div class="para">
+ my $pkg_iter = $rpm_db->find_by_name_iter( $ARGV[0] );
+ </div><div class="para">
+ </div><div class="para">
+ while (my $pkg = $pkg_iter->next() ) {
+ </div><div class="para">
+ </div><div class="para">
+ printFiles( $pkg );
+ </div><div class="para">
+ }
+ </div><div class="para">
+ </div><div class="para">
+ $rpm_db->close_rpm_db();
+ </div><div class="para">
+ </div><div class="para">
+ </div><div class="para">
+ </div><div class="para">
+ # Prints installation data for one package.
+ </div><div class="para">
+ sub printFiles {
+ </div><div class="para">
+ my($pkg) = shift;
+ </div><div class="para">
+ </div><div class="para">
+ my $files = arrayToString("\n", $pkg->files() );
+ </div><div class="para">
+ </div><div class="para">
+ print "Files:\n", $files, "\n";
+ </div><div class="para">
+ }
+ </div><div class="para">
+ </div><div class="para">
+ sub arrayToString {
+ </div><div class="para">
+ my($sep) = shift;
+ </div><div class="para">
+ my(@array) = @_;
+ </div><div class="para">
+ my($str);
+ </div><div class="para">
+ </div><div class="para">
+ $str = $array[0];
+ </div><div class="para">
+ </div><div class="para">
+ for ( my $i = 1; $i < $#array; $i++ )
+ </div><div class="para">
+ {
+ </div><div class="para">
+ $str = $str . $sep . $array[$i];
+ </div><div class="para">
+ }
+ </div><div class="para">
+ </div><div class="para">
+ return $str;
+ </div><div class="para">
+ }
+ </div><div class="para">
+ When you run this script, you’ll see output like the following:
+ </div><div class="para">
+ $ ./rpmfiles.pl jikes
+ </div><div class="para">
+ Files:
+ </div><div class="para">
+ /usr/bin/jikes
+ </div><div class="para">
+ /usr/doc/jikes-1.17/license.htm
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch17s03s05s02.html"><strong>Înapoi</strong>17.3.5.2. Handling String Array Tags</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch17s03s06.html"><strong>Înainte</strong>17.3.6. Comparing versions</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch17s03s06.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch17s03s06.html
new file mode 100644
index 0000000..2ff2401
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch17s03s06.html
@@ -0,0 +1,102 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>17.3.6. Comparing versions</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch17s03.html" title="17.3. Programming with the RPM Database" /><link rel="prev" href="ch17s03s05s03.html" title="17.3.5.3. Listing the Files In A Package" /><link rel="next" href="ch17s03s07.html" title="17.3.7. Closing the database" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch17s03s05s03.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch17s0
3s07.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id616861" class="title">Comparing versions</h1></div></div></div><div class="para">
+ The RPM2 module overrides the spaceship operator, <=>, to perform version comparisons between packages. The script in Listing 18-8 shows how to compare all local RPM files against the newest installed version of the same package, if the package is installed.
+ </div><div class="para">
+ Listing 18-8: rpmver.pl
+ </div><div class="para">
+ #!/usr/bin/perl -w
+ </div><div class="para">
+ </div><div class="para">
+ #
+ </div><div class="para">
+ # Compare versions of all *.rpm files against the
+ </div><div class="para">
+ # latest packages installed (if installed)
+ </div><div class="para">
+ #
+ </div><div class="para">
+ # Usage:
+ </div><div class="para">
+ # rpmver.pl
+ </div><div class="para">
+ # This script looks for all *.rpm files.
+ </div><div class="para">
+ #
+ </div><div class="para">
+ use strict;
+ </div><div class="para">
+ use RPM2;
+ </div><div class="para">
+ </div><div class="para">
+ my $rpm_db = RPM2->open_rpm_db();
+ </div><div class="para">
+ </div><div class="para">
+ for my $filename (<*.rpm>) {
+ </div><div class="para">
+ my $h = RPM2->open_package( $filename );
+ </div><div class="para">
+ </div><div class="para">
+ # Ensure we compare against the newest
+ </div><div class="para">
+ # package of the given name.
+ </div><div class="para">
+ my ($installed) =
+ </div><div class="para">
+ sort { $b <=> $a } $rpm_db->find_by_name($h->name);
+ </div><div class="para">
+ </div><div class="para">
+ if (not $installed) {
+ </div><div class="para">
+ printf "Package %s not installed.\n", $h->as_nvre;
+ </div><div class="para">
+ } else {
+ </div><div class="para">
+ my ($result) = ($h <=> $installed);
+ </div><div class="para">
+ </div><div class="para">
+ if ($result < 0) {
+ </div><div class="para">
+ printf "Installed package %s newer than file %s\n",
+ </div><div class="para">
+ $installed->as_nvre,
+ </div><div class="para">
+ $h->as_nvre;
+ </div><div class="para">
+ } else {
+ </div><div class="para">
+ printf "File %s newer than installed package %s\n",
+ </div><div class="para">
+ $h->as_nvre,
+ </div><div class="para">
+ $installed->as_nvre;
+ </div><div class="para">
+ }
+ </div><div class="para">
+ }
+ </div><div class="para">
+ }
+ </div><div class="para">
+ The sort { $a <=> $b } in front of the find_by_name call sorts all the packages of that name by the version number, so that the comparison is performed against the newest installed version of the package. The ($h <=> $installed) compares the header from the RPM file on disk against the newest installed version of the package.
+ </div><div class="para">
+ When you run this script, you’ll see output like the following, depending on which RPM files you have in the local directory:
+ </div><div class="para">
+ $ perl rpmver.pl
+ </div><div class="para">
+ Package acroread-4.0-0 not installed.
+ </div><div class="para">
+ Package canvas-7.0b2.0-1 not installed.
+ </div><div class="para">
+ Installed package jikes-1.18-1 newer than file jikes-1.14-1
+ </div><div class="para">
+ Installed package SDL-1.2.4-5 newer than file SDL-0.9.9-4
+ </div><div class="para">
+ Package ted-2.8-1 not installed.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch17s03s05s03.html"><strong>Înapoi</strong>17.3.5.3. Listing the Files In A Package</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch17s03s07.html"><strong>Înainte</strong>17.3.7. Closing the database</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch17s03s07.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch17s03s07.html
new file mode 100644
index 0000000..265544f
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch17s03s07.html
@@ -0,0 +1,16 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>17.3.7. Closing the database</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch17s03.html" title="17.3. Programming with the RPM Database" /><link rel="prev" href="ch17s03s06.html" title="17.3.6. Comparing versions" /><link rel="next" href="ch17s04.html" title="17.4. Where to Go from Here" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch17s03s06.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch17s04.html"><strong>ÃŽnainte
</strong></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id800754" class="title">Closing the database</h1></div></div></div><div class="para">
+ When you are done with the RPM database, call close_rpm_db, as shown following:
+ </div><div class="para">
+ $rpm_db->close_rpm_db();
+ </div><div class="para">
+ Note that this call is not necessary, as the RPM2 module will close the database when the object, in this case $rpm_db, goes out of scope.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch17s03s06.html"><strong>Înapoi</strong>17.3.6. Comparing versions</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch17s04.html"><strong>Înainte</strong>17.4. Where to Go from Here</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch17s04.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch17s04.html
new file mode 100644
index 0000000..c4699c1
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch17s04.html
@@ -0,0 +1,28 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>17.4. Where to Go from Here</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-programming-perl.html" title="Cap. 17. Programming RPM with Perl" /><link rel="prev" href="ch17s03s07.html" title="17.3.7. Closing the database" /><link rel="next" href="ch17s05.html" title="17.5. Summary" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch17s03s07.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch17s05.html"><strong>ÃŽnainte</str
ong></a></li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id800776" class="title">Where to Go from Here</h1></div></div></div><div class="para">
+ One of the strengths of Perl is that there are so many add-on packages available. In addition, Perl is really strong in text processing. You can combine these strengths to provide cleaner output for RPM database queries, for example, avoiding the complex syntax for the --queryformat option to the rpm command. Perl can do more than the --queryformat option allows. For example, you can combine multiple values together into a Perl string and then format the output. The --queryformat option only allows formatting on each value individually, not groups of values.
+ </div><div class="para">
+ In addition, you can combine one of the Perl templating modules, such as Text::Template or HTML::Template, to create an HTML page for a given package. You could use Perl to create formatted HTML pages for all the installed packages on your system, with HTML links to cross-reference all the dependencies.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ Download these modules from the CPAN site, www.cpan.org.
+ </div><div class="para">
+ This chapter covers the RPM2 module. Right now, the RPM2 module supports only querying packages and the RPM database. Future versions will likely add the ability to install, update, and remove packages.
+ </div><div class="para">
+ In addition to this module, you can find an RPM module with RPM::Header and RPM::Database classes. Another module, RPM::Specfile, provides the ability to turn Perl modules, such as those stored on CPAN, into RPM packages. The RPM::Specfile module helps create an RPM spec file for a Perl module.
+ </div><div class="para">
+ The Perl-RPM-Perlonly bundle provides an alternative version of the RPM::Header module written entirely in Perl with no usage of the C rpm library. This makes RPM access much easier on platforms for which you don’t have the RPM system.
+ </div><div class="para">
+ The RPM-Tools bundle includes RPM::Update, which compares the packages installed on your system (listed by calling rpm –qa) with the packages available on another system, that may be available only with a network link. This module can also update packages that are older than the designated master system. RPM::Make, also part of the RPM-Tools bundle, helps create RPM packages from a Perl script. This module does not support all the spec file options described in <a class="xref" href="ch-specfiles.html">Cap. 9, <em>Working with Spec Files</em></a> , but it can help you make simple packages.
+ </div><div class="para">
+ You can download all these modules from the CPAN site.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch17s03s07.html"><strong>Înapoi</strong>17.3.7. Closing the database</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch17s05.html"><strong>Înainte</strong>17.5. Summary</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch17s05.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch17s05.html
new file mode 100644
index 0000000..06db5a3
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch17s05.html
@@ -0,0 +1,18 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>17.5. Summary</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-programming-perl.html" title="Cap. 17. Programming RPM with Perl" /><link rel="prev" href="ch17s04.html" title="17.4. Where to Go from Here" /><link rel="next" href="ch-other-linuxes.html" title="Cap. 18. Using RPM on Non-Red Hat Linuxes" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch17s04.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch-ot
her-linuxes.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id564616" class="title">Summary</h1></div></div></div><div class="para">
+ This chapter introduces the RPM2 add-on module to allow Perl scripts to access information on RPM package files and in the RPM database. To access an RPM file and query information about that file, you need to call the open_package subroutine. Once you’ve opened the file, you can call the tag, as_nvre, is_source_package, and files subroutines on the header object to query data about the package.
+ </div><div class="para">
+ To access the RPM database, call open_rpm_db. Once you’ve opened the database, you can call one of the find subroutines, such as find_by_name or find_by_name_iter, to search for packages. The subroutines that have names ending with _iter, such as find_by_name_iter, return an iterator object to iterate over the packages found. The other find subroutines, such as find_by_name, return a Perl list of the packages found.
+ </div><div class="para">
+ You can then call the tag, as_nvre, and files subroutines on the package objects to query information about the packages.
+ </div><div class="para">
+ When you are done with the RPM database, call close_rpm_db.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch17s04.html"><strong>Înapoi</strong>17.4. Where to Go from Here</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch-other-linuxes.html"><strong>Înainte</strong>Cap. 18. Using RPM on Non-Red Hat Linuxes</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch18s02.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch18s02.html
new file mode 100644
index 0000000..6ab2fb8
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch18s02.html
@@ -0,0 +1,56 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>18.2. Handling Problems Building RPMs</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-other-linuxes.html" title="Cap. 18. Using RPM on Non-Red Hat Linuxes" /><link rel="prev" href="ch-other-linuxes.html" title="Cap. 18. Using RPM on Non-Red Hat Linuxes" /><link rel="next" href="ch18s02s02.html" title="18.2.2. Dealing with automatic dependency generation" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-other-linuxes.html"><strong>ÃŽnapoi</strong></a></li><li
class="next"><a accesskey="n" href="ch18s02s02.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id638408" class="title">Handling Problems Building RPMs</h1></div></div></div><div class="para">
+ Given all these differences, how can you create RPMs while avoiding problems? With some work setting things up, you can create an RPM build environment that solves most vendor issues. This depends on taking a methodical approach to building your packages and using techniques to avoid vendor issues wherever possible.
+ </div><div class="para">
+ When building RPMs, you will face many of the same problems@@mdand solutions@@mdas when installing RPMs. For example, due to the different ways Linux vendors divide software into packages, your RPMs will likely have issues defining the proper dependencies. There are also a number of issues that apply only when building RPMs.
+ </div><div class="para">
+ The following sections cover the main issues when building RPMs.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id638432" class="title">Writing distribution-specific packages</h1></div></div></div><div class="para">
+ One of the ways around all the differences between Linux distributions in RPM usage is to define distribution-specific packages. To do this, you create a separate package on each Linux distribution you support.
+ </div><div class="para">
+ That’s a lot of work. If possible, fit the differences into macros and use a single spec file to reduce some of this work. This technique works up to a point. Sometimes, your spec file becomes too complicated and you may decide that it is easier to create multiple spec files, one per Linux distribution.
+ </div><div class="para">
+ One way to help make vendor-specific packages, or to see which RPM macros are defined on a given Linux distribution, is to look for an RPM that contains the distribution-specific RPM configuration. For example, on Red Hat Linux systems, the Red Hat RPM configuration is defined by the redhat-rpm-config package.
+ </div><div class="para">
+ You can list the files in this package to see where Red Hat defines macros specific to their Linux distribution.
+ </div><div class="para">
+ $ rpm -ql redhat-rpm-config
+ </div><div class="para">
+ /usr/lib/rpm/redhat
+ </div><div class="para">
+ /usr/lib/rpm/redhat/brp-compress
+ </div><div class="para">
+ /usr/lib/rpm/redhat/brp-redhat
+ </div><div class="para">
+ /usr/lib/rpm/redhat/brp-sparc64-linux
+ </div><div class="para">
+ /usr/lib/rpm/redhat/brp-strip
+ </div><div class="para">
+ /usr/lib/rpm/redhat/brp-strip-comment-note
+ </div><div class="para">
+ /usr/lib/rpm/redhat/brp-strip-shared
+ </div><div class="para">
+ /usr/lib/rpm/redhat/find-lang.sh
+ </div><div class="para">
+ /usr/lib/rpm/redhat/find-provides
+ </div><div class="para">
+ /usr/lib/rpm/redhat/find-requires
+ </div><div class="para">
+ /usr/lib/rpm/redhat/macros
+ </div><div class="para">
+ /usr/lib/rpm/redhat/perl.prov
+ </div><div class="para">
+ /usr/lib/rpm/redhat/perl.req
+ </div><div class="para">
+ /usr/lib/rpm/redhat/rpmrc
+ </div><div class="para">
+ These files, such as /usr/lib/rpm/redhat/macros, show you what is specific to a given Linux distribution. You can then look at the macros defined in these files to identify settings for a particular distribution, in this case, Red Hat. Armed with this knowledge, you can better create portable RPM spec files.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-other-linuxes.html"><strong>Înapoi</strong>Cap. 18. Using RPM on Non-Red Hat Linuxes</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch18s02s02.html"><strong>Înainte</strong>18.2.2. Dealing with automatic dependency generat...</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch18s02s02.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch18s02s02.html
new file mode 100644
index 0000000..d4f2b8e
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch18s02s02.html
@@ -0,0 +1,30 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>18.2.2. Dealing with automatic dependency generation</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch18s02.html" title="18.2. Handling Problems Building RPMs" /><link rel="prev" href="ch18s02.html" title="18.2. Handling Problems Building RPMs" /><link rel="next" href="ch18s02s03.html" title="18.2.3. Dealing with different macros" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch18s02.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch18s02s03.htm
l"><strong>ÃŽnainte</strong></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id675066" class="title">Dealing with automatic dependency generation</h1></div></div></div><div class="para">
+ One of the features in RPM 4.x is the automatic generation of dependencies. For a variety of reasons including different package layouts, different directory structures, or different versions of RPM, you may need to disable some or all of automatic generation of dependencies.
+ </div><div class="para">
+ You can disable the automatic generation of dependencies by placing the following directive in your spec file:
+ </div><div class="para">
+ Autoreq: 0
+ </div><div class="para">
+ If you do so, you need to use the Requires: tag to manually define all requirements. This is not a good solution to the issue of automatic dependencies however. Most likely, you will need to override the %{__find_requires} and %{__find_provides} macros in order to filter out any unwanted dependencies.
+ </div><div class="para">
+ These two macros resolve to shell scripts that perform the automated dependency checks, as you can see with the rpm --eval command:
+ </div><div class="para">
+ $ rpm --eval "%__find_provides"
+ </div><div class="para">
+ /usr/lib/rpm/find-provides
+ </div><div class="para">
+ rpm --eval "%__find_requires"
+ </div><div class="para">
+ /usr/lib/rpm/find-requires
+ </div><div class="para">
+ You can override these scripts to filter out any dependencies that cause problems for your packages.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch18s02.html"><strong>Înapoi</strong>18.2. Handling Problems Building RPMs</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch18s02s03.html"><strong>Înainte</strong>18.2.3. Dealing with different macros</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch18s02s03.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch18s02s03.html
new file mode 100644
index 0000000..686fcbb
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch18s02s03.html
@@ -0,0 +1,16 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>18.2.3. Dealing with different macros</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch18s02.html" title="18.2. Handling Problems Building RPMs" /><link rel="prev" href="ch18s02s02.html" title="18.2.2. Dealing with automatic dependency generation" /><link rel="next" href="ch18s02s04.html" title="18.2.4. Making relocatable packages" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch18s02s02.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" h
ref="ch18s02s04.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id795251" class="title">Dealing with different macros</h1></div></div></div><div class="para">
+ Different Linux vendors define different macros in their RPM setup. This may mean not only different values for the macros, but different macro names as well. Because of this, it is best to define your own local set of macros when building RPMs.
+ </div><div class="para">
+ As much as possible, depend on your own RPM macros. You can define your macros in terms of vendor-specific macros using conditional statements in your spec files, a topic covered in <a class="xref" href="ch-advanced-packaging.html">Cap. 10, <em>Creare avansată pachete RPM</em></a> . You can also read examples in the “Build Environment and Macros†section of this chapter.
+ </div><div class="para">
+ This really boils down to creating a disciplined RPM build environment.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch18s02s02.html"><strong>Înapoi</strong>18.2.2. Dealing with automatic dependency generat...</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch18s02s04.html"><strong>Înainte</strong>18.2.4. Making relocatable packages</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch18s02s04.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch18s02s04.html
new file mode 100644
index 0000000..d372e52
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch18s02s04.html
@@ -0,0 +1,24 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>18.2.4. Making relocatable packages</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch18s02.html" title="18.2. Handling Problems Building RPMs" /><link rel="prev" href="ch18s02s03.html" title="18.2.3. Dealing with different macros" /><link rel="next" href="ch18s02s05.html" title="18.2.5. Creating an RPM build environment" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch18s02s03.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch18
s02s05.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id795278" class="title">Making relocatable packages</h1></div></div></div><div class="para">
+ You should aim to make your packages relocatable so that users can install your packages into any directory. This makes it easier to deal with the locations chosen by different Linux distributions, such as /usr, /usr/local, or /opt, for installing add-on software.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ <a class="xref" href="ch-specfiles.html">Cap. 9, <em>Working with Spec Files</em></a> covers the spec file format. <a class="xref" href="ch-advanced-packaging.html">Cap. 10, <em>Creare avansată pachete RPM</em></a> covers making relocatable packages.
+ </div><div class="para">
+ You can use the %{_bindir} macro in your spec files, which will help create per-distribution packages using the right settings.
+ </div><div class="para">
+ In addition, you can define macros in your spec files that define the location for dependencies. You can then use the --define option to the rpmbuild command to define values for your macros that specify the locations for the dependencies.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ This technique of setting up Linux distribution-specific macros can help solve a lot of problems with cross-platform RPMs.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch18s02s03.html"><strong>Înapoi</strong>18.2.3. Dealing with different macros</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch18s02s05.html"><strong>Înainte</strong>18.2.5. Creating an RPM build environment</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch18s02s05.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch18s02s05.html
new file mode 100644
index 0000000..c388c35
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch18s02s05.html
@@ -0,0 +1,44 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>18.2.5. Creating an RPM build environment</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch18s02.html" title="18.2. Handling Problems Building RPMs" /><link rel="prev" href="ch18s02s04.html" title="18.2.4. Making relocatable packages" /><link rel="next" href="ch18s02s05s02.html" title="18.2.5.2. Build environment and macros" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch18s02s04.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch18s0
2s05s02.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id803339" class="title">Creating an RPM build environment</h1></div></div></div><div class="para">
+ If you start with the idea that you want to build RPMs for multiple versions of Linux, you can set up an RPM build environment that cleanly separates most vendor-specific issues.
+ </div><div class="para">
+ The key issues with the build environment are:
+ </div><div class="para">
+ *Detecting the vendors
+ </div><div class="para">
+ *Using macros to define a clean build process
+ </div><div class="para">
+ *Handling different dependencies
+ </div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id803366" class="title">Detecting Vendors</h1></div></div></div><div class="para">
+ To make a clean build environment, you need to be able to detect the Linux vendor and make build settings based on this vendor. To help with this, many Linux vendors install a special file with the vendor name, or a special package with the vendor name. You can query for either of these.
+ </div><div class="para">
+ For files, the convention follows:
+ </div><div class="para">
+ /etc/vendor-release
+ </div><div class="para">
+ For example:
+ </div><div class="para">
+ $ more /etc/redhat-release
+ </div><div class="para">
+ Red Hat Linux release 8.0 (Psyche)
+ </div><div class="para">
+ For packages, the convention is vendor-release for a package name. For example:
+ </div><div class="para">
+ $ rpm -q redhat-release
+ </div><div class="para">
+ redhat-release-8.0-8
+ </div><div class="para">
+ You can use either approach or simply define a macro for the vendor and use the --define option to set the macro. For example:
+ </div><div class="para">
+ # rpmbuild –ba --define 'linuxVendor suse'
+ </div><div class="para">
+ With this definition, you can use the macro %linuxVendor inside your spec files. It is generally easier, though, if your scripts can automatically detect the Linux vendor instead of having to define it manually. The manual approach works, though, if it becomes too much effort to detect the vendor automatically.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch18s02s04.html"><strong>Înapoi</strong>18.2.4. Making relocatable packages</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch18s02s05s02.html"><strong>Înainte</strong>18.2.5.2. Build environment and macros</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch18s02s05s02.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch18s02s05s02.html
new file mode 100644
index 0000000..d0fa05f
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch18s02s05s02.html
@@ -0,0 +1,83 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>18.2.5.2. Build environment and macros</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch18s02s05.html" title="18.2.5. Creating an RPM build environment" /><link rel="prev" href="ch18s02s05.html" title="18.2.5. Creating an RPM build environment" /><link rel="next" href="ch18s02s05s03.html" title="18.2.5.3. Compatibility and Glue Packages" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch18s02s05.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey=
"n" href="ch18s02s05s03.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id571418" class="title">Build environment and macros</h1></div></div></div><div class="para">
+ Once you can detect the Linux vendor, you can create macros based on the differences between Linux distributions that affect your applications.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ <a class="xref" href="ch-customizing-rpm.html">Cap. 20, <em>Customizing RPM Behavior</em></a> covers RPM macros.
+ </div><div class="para">
+ The macros that specifically help you with platform differences include the %if .. %endif conditional. You can use this in combination with special macros you define. In addition, command-line options such as --with, --without, and --target allow you to control features and the build target within an RPM.
+ </div><div class="para">
+ The %if macro allows you to specify a condition within your spec file. For example:
+ </div><div class="para">
+ %if %{old_5x} && %{old_6x}
+ </div><div class="para">
+ %{error: You cannot build for .5x and .6x at the same time}
+ </div><div class="para">
+ %quit
+ </div><div class="para">
+ %endif
+ </div><div class="para">
+ </div><div class="para">
+ %if %{old_5x}
+ </div><div class="para">
+ %define b5x 1
+ </div><div class="para">
+ %undefine b6x
+ </div><div class="para">
+ %endif
+ </div><div class="para">
+ </div><div class="para">
+ %if %{old_6x}
+ </div><div class="para">
+ %define b6x 1
+ </div><div class="para">
+ %undefine b5x
+ </div><div class="para">
+ %endif
+ </div><div class="para">
+ You can also use %if to control settings such as the Requires:, as shown in the following example:
+ </div><div class="para">
+ %if %{build6x}
+ </div><div class="para">
+ Requires: util-linux, pam >= 0.66-5
+ </div><div class="para">
+ %else
+ </div><div class="para">
+ Requires: util-linux, pam >= 0.75-37, /etc/pam.d/system-auth
+ </div><div class="para">
+ %endif
+ </div><div class="para">
+ </div><div class="para">
+ The --with command-line option defines a special macro starting with _with_. For example, the following command-line option defines a feature to use:
+ </div><div class="para">
+ $ rpmbuild –bc --with ssh filename.spec
+ </div><div class="para">
+ This example defines the macro _with_ssh to --with-ssh. This format was specially designed to work with GNU configure. You can use this for conditional builds for platform-dependent issues.
+ </div><div class="para">
+ The --without command-line option similarly defines a macro starting with _without_. The convention is that this option defines a feature the code should not use.
+ </div><div class="para">
+ You can combine --with and --without to turn on and off features referenced in your spec files. For example:
+ </div><div class="para">
+ ./configure %{?_with_ssh}
+ </div><div class="para">
+ This will pass the following command line if the _with_ssh macro is defined:
+ </div><div class="para">
+ ./configure --with-ssh
+ </div><div class="para">
+ If this option is not defined, the command will be:
+ </div><div class="para">
+ ./configure
+ </div><div class="para">
+ The --target option sets the spec file macros %_target, %_target_arch, and %_target_os . For example:
+ </div><div class="para">
+ $ rpmbuild -bc --target ppc-ibm-aix /usr/src/redhat/SPECS/jikes.spec
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch18s02s05.html"><strong>Înapoi</strong>18.2.5. Creating an RPM build environment</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch18s02s05s03.html"><strong>Înainte</strong>18.2.5.3. Compatibility and Glue Packages</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch18s02s05s03.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch18s02s05s03.html
new file mode 100644
index 0000000..3b90820
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch18s02s05s03.html
@@ -0,0 +1,32 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>18.2.5.3. Compatibility and Glue Packages</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch18s02s05.html" title="18.2.5. Creating an RPM build environment" /><link rel="prev" href="ch18s02s05s02.html" title="18.2.5.2. Build environment and macros" /><link rel="next" href="ch18s02s05s04.html" title="18.2.5.4. Dealing with Signatures" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch18s02s05s02.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" h
ref="ch18s02s05s04.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id861454" class="title">Compatibility and Glue Packages</h1></div></div></div><div class="para">
+ Not all Linux distributions are the same. Macros alone won’t provide work-arounds for all the differences. You can, though, get a lot of mileage from compatibility and glue packages.
+ </div><div class="para">
+ A compatibility package provides a legacy API on newer systems that no longer support the legacy API. By convention, compatibility packages are named with a leading compat- to signify their purpose.
+ </div><div class="para">
+ For example:
+ </div><div class="para">
+ $ rpm -q --qf "%{description}" compat-libstdc++
+ </div><div class="para">
+ The compat-libstdc++ package contains compatibility Standard C++
+ </div><div class="para">
+ Using a compatibility package allows you to create programs that use a least-common-denominator approach, programming to the oldest but most common APIs. As some Linux distributions eliminate the old APIs, compatibility packages can provide the missing APIs.
+ </div><div class="para">
+ Similarly, a glue package provides a dependency that exists on some Linux distributions but not others. It glues together your package with the Linux distribution that is missing an essential capability.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ A key point in both of these approaches is to separate the compatibility and glue packages from your main application packages. The application packages should be as clean of vendor issues as possible. Instruct your users to install the compatibility or glue packages as needed (based on their Linux distribution) along with the main application package or packages.
+ </div><div class="para">
+ With all this discussion of RPM and Linux differences, you might think that Linux is one big mess. That’s not true. Linux maintains a high degree of compatibility among Linux distributions as well as among processor architectures. Most programs originally created for Linux on Intel-based architectures compile cleanly on Linux versions running on other processor architectures such as MIPS, SPARC, and ARM.
+ </div><div class="para">
+ The main differences lie in how Linux vendors split up the huge number of files associated with Linux into RPM packages as well as which versions of tools like C compilers the vendors ship.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch18s02s05s02.html"><strong>Înapoi</strong>18.2.5.2. Build environment and macros</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch18s02s05s04.html"><strong>Înainte</strong>18.2.5.4. Dealing with Signatures</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch18s02s05s04.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch18s02s05s04.html
new file mode 100644
index 0000000..f423481
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch18s02s05s04.html
@@ -0,0 +1,13 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>18.2.5.4. Dealing with Signatures</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch18s02s05.html" title="18.2.5. Creating an RPM build environment" /><link rel="prev" href="ch18s02s05s03.html" title="18.2.5.3. Compatibility and Glue Packages" /><link rel="next" href="ch18s03.html" title="18.3. Dealing with Non-RPM-Based Linux Versions" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch18s02s05s03.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a acce
sskey="n" href="ch18s03.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id861520" class="title">Dealing with Signatures</h1></div></div></div><div class="para">
+ With SUSE Linux, or any Linux based on UnitedLinux 1.0, the RPM packages are signed with OpenPGP version 4, not 3, as used in RPM 4.1. This means that you must use some other, non-RPM means to extract the signatures from an RPM package, and then verify these signatures with gpg.
+ </div><div class="para">
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch18s02s05s03.html"><strong>Înapoi</strong>18.2.5.3. Compatibility and Glue Packages</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch18s03.html"><strong>Înainte</strong>18.3. Dealing with Non-RPM-Based Linux Versions</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch18s03.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch18s03.html
new file mode 100644
index 0000000..078f151
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch18s03.html
@@ -0,0 +1,18 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>18.3. Dealing with Non-RPM-Based Linux Versions</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-other-linuxes.html" title="Cap. 18. Using RPM on Non-Red Hat Linuxes" /><link rel="prev" href="ch18s02s05s04.html" title="18.2.5.4. Dealing with Signatures" /><link rel="next" href="ch18s04.html" title="18.4. Standardizing RPMs" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch18s02s05s04.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch18s04.h
tml"><strong>ÃŽnainte</strong></a></li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id861540" class="title">Dealing with Non-RPM-Based Linux Versions</h1></div></div></div><div class="para">
+ The main Linux distributions that don’t support RPM are the Debian GNU/Linux family and Slackware Linux. To help with these distributions, you can use a package-conversion tool called alien.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id554032" class="title">Handling non-RPM packages with alien</h1></div></div></div><div class="para">
+ Alien is a package that supports conversions between RPM and so-called alien package formats such as the dpkg (Debian GNU/Linux), slp (Stampede Linux), and tgz (Slackware Linux) formats.
+ </div><div class="para">
+ You can use alien on your RPM-based Linux system to convert RPMs to some other format, such as the Debian dpkg. You can also use alien to convert other package formats into RPMs, depending on which way you need to go.
+ </div><div class="para">
+ </div><div class="para">
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch18s02s05s04.html"><strong>Înapoi</strong>18.2.5.4. Dealing with Signatures</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch18s04.html"><strong>Înainte</strong>18.4. Standardizing RPMs</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch18s04.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch18s04.html
new file mode 100644
index 0000000..aa016b7
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch18s04.html
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>18.4. Standardizing RPMs</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-other-linuxes.html" title="Cap. 18. Using RPM on Non-Red Hat Linuxes" /><link rel="prev" href="ch18s03.html" title="18.3. Dealing with Non-RPM-Based Linux Versions" /><link rel="next" href="ch18s04s02.html" title="18.4.2. RPM adoption" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch18s03.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch18s04s
02.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id554060" class="title">Standardizing RPMs</h1></div></div></div><div class="para">
+ RPM is being considered as part of the Linux Standard Base, or LSB, 1.3. This will define a standard packaging format for Linux distributions, and over time reduce the RPM differences between distributions.
+ </div><div class="para">
+ In addition, other efforts are underway to help unify the diverse Linux distributions, including the Filesystem Hierarchy Standard and the adoption of RPM by many Linux vendors.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id554078" class="title">Filesystem Hierarchy Standard</h1></div></div></div><div class="para">
+ The FHS, or Filesystem Hierarchy Standard, defines the purpose of all the upper-level directories on Linux systems, such as /var and /usr/bin. This standard, along with the Linux Standard Base, or LSB, is driving Linux distributions to a greater degree of similarity.
+ </div><div class="para">
+ The FHS helps by specifying where applications should get installed and which directories should be left to local administrators to manage. The FHS also defines the purpose of all Linux directories, giving vendors and application writers a better idea of where they should install their packages.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ See www.linuxbase.org for more on the LSB. See www.pathname.com/fhs/ for more on the FHS.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch18s03.html"><strong>Înapoi</strong>18.3. Dealing with Non-RPM-Based Linux Versions</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch18s04s02.html"><strong>Înainte</strong>18.4.2. RPM adoption</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch18s04s02.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch18s04s02.html
new file mode 100644
index 0000000..36e5486
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch18s04s02.html
@@ -0,0 +1,16 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>18.4.2. RPM adoption</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch18s04.html" title="18.4. Standardizing RPMs" /><link rel="prev" href="ch18s04.html" title="18.4. Standardizing RPMs" /><link rel="next" href="ch18s05.html" title="18.5. Summary" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch18s04.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch18s05.html"><strong>ÃŽnainte</strong></a></li></ul><div class="se
ct2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id554106" class="title">RPM adoption</h1></div></div></div><div class="para">
+ RPM has been adopted by a large number of Linux distributions. In addition, standardization efforts, both for RPM and for filesystem locations, are making Linux systems less varied.
+ </div><div class="para">
+ This means that over time, many of the RPM-related differences between Linux distributions will fade away, making it easier to create cross-platform RPMs.
+ </div><div class="para">
+ </div><div class="para">
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch18s04.html"><strong>Înapoi</strong>18.4. Standardizing RPMs</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch18s05.html"><strong>Înainte</strong>18.5. Summary</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch18s05.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch18s05.html
new file mode 100644
index 0000000..0ad517f
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch18s05.html
@@ -0,0 +1,20 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>18.5. Summary</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-other-linuxes.html" title="Cap. 18. Using RPM on Non-Red Hat Linuxes" /><link rel="prev" href="ch18s04s02.html" title="18.4.2. RPM adoption" /><link rel="next" href="ch-other-os.html" title="Cap. 19. RPM on Other Operating Systems" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch18s04s02.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch-other-
os.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id574399" class="title">Summary</h1></div></div></div><div class="para">
+ This chapter covers differences in RPM versions between various Linux distributions, and techniques you can use to get around these differences. Each Linux vendor packages software differently, even if the vendor uses RPM. This can cause problems unless you write your spec files carefully.
+ </div><div class="para">
+ Inside your RPM spec files, you can use conditional elements as well as platform-based macro definitions to help create RPMs for multiple packages.
+ </div><div class="para">
+ Some of the best conventions are to split the software in your applications from any compatibility or glue packages, separate packages that provide missing features for various flavors of Linux.
+ </div><div class="para">
+ Standardization efforts such as the Linux Standard Base and Filesystem Hierarchy Standard are bringing Linux vendors closer and closer together. Widespread adoption of RPM by most Linux distributions also helps.
+ </div><div class="para">
+ While this chapter covers RPM on other Linux distributions, the next chapter tackles RPM outside of Linux.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch18s04s02.html"><strong>Înapoi</strong>18.4.2. RPM adoption</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch-other-os.html"><strong>Înainte</strong>Cap. 19. RPM on Other Operating Systems</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch19s02.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch19s02.html
new file mode 100644
index 0000000..44ab841
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch19s02.html
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>19.2. Bootstrapping RPM On Other Operating Systems</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-other-os.html" title="Cap. 19. RPM on Other Operating Systems" /><link rel="prev" href="ch-other-os.html" title="Cap. 19. RPM on Other Operating Systems" /><link rel="next" href="ch19s02s02.html" title="19.2.2. Extracting the software" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-other-os.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch19
s02s02.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id719483" class="title">Bootstrapping RPM On Other Operating Systems</h1></div></div></div><div class="para">
+ If you cannot find a version of RPM that has been ported to your platform, you can port it yourself. The RPM system usually isn’t that hard to port to any platform that can appear like Unix or Linux systems, such as any platform that supports POSIX system calls or something like these system calls.
+ </div><div class="para">
+ Don’t be dismayed by the sheer size of the RPM package. Much of the RPM system was carefully designed to run across multiple platforms, so file access is abstracted to special portability routines. For example, RPM has been ported to both AmigaOS and BeOS, two non-Unix operating systems.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id719502" class="title">Downloading the RPM software</h1></div></div></div><div class="para">
+ To bootstrap RPM on another operating system, download the RPM source code from the main RPM site.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ You can download the RPM source code from ftp://ftp.rpm.org/pub/rpm/dist/.
+ </div><div class="para">
+ Note that you probably do not want to download an RPM of the sources, since your platform won’t have RPM available. In most cases, you’ll want to download a tarred compressed archive, such as rpm-4.1.tar.gz for RPM version 4.1.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-other-os.html"><strong>Înapoi</strong>Cap. 19. RPM on Other Operating Systems</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch19s02s02.html"><strong>Înainte</strong>19.2.2. Extracting the software</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch19s02s02.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch19s02s02.html
new file mode 100644
index 0000000..951e1b8
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch19s02s02.html
@@ -0,0 +1,26 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>19.2.2. Extracting the software</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch19s02.html" title="19.2. Bootstrapping RPM On Other Operating Systems" /><link rel="prev" href="ch19s02.html" title="19.2. Bootstrapping RPM On Other Operating Systems" /><link rel="next" href="ch19s02s03.html" title="19.2.3. Reading the INSTALL file" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch19s02.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n"
href="ch19s02s03.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id719527" class="title">Extracting the software</h1></div></div></div><div class="para">
+ If the system you plan to port RPM doesn’t have the tar and gzip commands available, or something that supports these formats, then you need to find a way to extract the software.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ Programs such as WinZip on Windows support extracting .tar.gz files. Your platform may have a similar program.
+ </div><div class="para">
+ One way is to port the gzip and tar commands to your platform.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ You can download the sources for tar and gzip from www.gnu.org.
+ </div><div class="para">
+ Another way is to extract the sources on a platform with these commands available, such as a Linux platform. Then, create a file using a format supported by your operating system and transfer the files to the other system.
+ </div><div class="para">
+ Once you have the RPM source code available on your target system, and all the files are extracted, you are ready to start porting. The first step is really simple: read.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch19s02.html"><strong>Înapoi</strong>19.2. Bootstrapping RPM On Other Operating Systems</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch19s02s03.html"><strong>Înainte</strong>19.2.3. Reading the INSTALL file</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch19s02s03.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch19s02s03.html
new file mode 100644
index 0000000..31a5d31
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch19s02s03.html
@@ -0,0 +1,16 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>19.2.3. Reading the INSTALL file</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch19s02.html" title="19.2. Bootstrapping RPM On Other Operating Systems" /><link rel="prev" href="ch19s02s02.html" title="19.2.2. Extracting the software" /><link rel="next" href="ch19s02s04.html" title="19.2.4. Libraries required by RPM" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch19s02s02.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch19s
02s04.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id801110" class="title">Reading the INSTALL file</h1></div></div></div><div class="para">
+ In the main RPM source directory, you will see two very important files: README and INSTALL. Read them both. (You would be surprised at how many times people need to be told this.)
+ </div><div class="para">
+ Of the two, the INSTALL file has much more detailed information on installing RPM on a new system. The INSTALL file describes the libraries required by RPM, provides tips on compiling RPM, and describes some of the set up work necessary after compiling the RPM system.
+ </div><div class="para">
+ Some of the hardest parts of the RPM system to port, though, may be in the database, compression, and encryption calls, used as libraries by the RPM system.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch19s02s02.html"><strong>Înapoi</strong>19.2.2. Extracting the software</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch19s02s04.html"><strong>Înainte</strong>19.2.4. Libraries required by RPM</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch19s02s04.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch19s02s04.html
new file mode 100644
index 0000000..61daf3a
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch19s02s04.html
@@ -0,0 +1,96 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>19.2.4. Libraries required by RPM</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch19s02.html" title="19.2. Bootstrapping RPM On Other Operating Systems" /><link rel="prev" href="ch19s02s03.html" title="19.2.3. Reading the INSTALL file" /><link rel="next" href="ch19s02s05.html" title="19.2.5. Tools for building RPM" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch19s02s03.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch19s02
s05.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id801135" class="title">Libraries required by RPM</h1></div></div></div><div class="para">
+ Rather than invent everything from scratch, the RPM system makes use of a number of libraries, including those listed in Table 20-2.
+ </div><div class="para">
+ Table 20-2 Libraries used by RPM
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Library
+ </div>
+
+ </td><td>
+ <div class="para">
+ Purpose
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Berkeley DB
+ </div>
+
+ </td><td>
+ <div class="para">
+ RPM database, using db1 and db3
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ bzip2
+ </div>
+
+ </td><td>
+ <div class="para">
+ Compression
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ gettext
+ </div>
+
+ </td><td>
+ <div class="para">
+ International text lookup
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ gpg
+ </div>
+
+ </td><td>
+ <div class="para">
+ For digital signatures
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ gzip
+ </div>
+
+ </td><td>
+ <div class="para">
+ Compression
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ popt
+ </div>
+
+ </td><td>
+ <div class="para">
+ Processing command-line options
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ zlib
+ </div>
+
+ </td><td>
+ <div class="para">
+ Compression
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ Read through the INSTALL file to find out where you can download versions of these libraries. You may find that each library has its own set of dependencies, all of which you need to port to your target platform.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch19s02s03.html"><strong>Înapoi</strong>19.2.3. Reading the INSTALL file</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch19s02s05.html"><strong>Înainte</strong>19.2.5. Tools for building RPM</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch19s02s05.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch19s02s05.html
new file mode 100644
index 0000000..d430413
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch19s02s05.html
@@ -0,0 +1,70 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>19.2.5. Tools for building RPM</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch19s02.html" title="19.2. Bootstrapping RPM On Other Operating Systems" /><link rel="prev" href="ch19s02s04.html" title="19.2.4. Libraries required by RPM" /><link rel="next" href="ch19s02s06.html" title="19.2.6. Compiling RPM" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch19s02s04.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch19s02s06.html
"><strong>ÃŽnainte</strong></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id556206" class="title">Tools for building RPM</h1></div></div></div><div class="para">
+ In addition to the libraries listed in Table 20-2, RPM requires a number of GNU utilities for building RPM, including those listed in Table 20-3.
+ </div><div class="para">
+ Table 20-3 Tools used to build RPM
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Tool
+ </div>
+
+ </td><td>
+ <div class="para">
+ Usage
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Autoconf
+ </div>
+
+ </td><td>
+ <div class="para">
+ Builds configure scripts
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Automake
+ </div>
+
+ </td><td>
+ <div class="para">
+ Used with autoconf
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ GNU make
+ </div>
+
+ </td><td>
+ <div class="para">
+ Used to control building the sources
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ Libtool
+ </div>
+
+ </td><td>
+ <div class="para">
+ Used by the autogen.sh script
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ In addition to all this, RPM works best with the GNU C compiler, GCC, and the GNU make program, gnumake, or simply gmake.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ The source code for all the GNU tools is available at www.gnu.org.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch19s02s04.html"><strong>Înapoi</strong>19.2.4. Libraries required by RPM</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch19s02s06.html"><strong>Înainte</strong>19.2.6. Compiling RPM</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch19s02s06.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch19s02s06.html
new file mode 100644
index 0000000..cbe79d2
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch19s02s06.html
@@ -0,0 +1,40 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>19.2.6. Compiling RPM</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch19s02.html" title="19.2. Bootstrapping RPM On Other Operating Systems" /><link rel="prev" href="ch19s02s05.html" title="19.2.5. Tools for building RPM" /><link rel="next" href="ch19s02s07.html" title="19.2.7. Handling problems" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch19s02s05.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch19s02s07.htm
l"><strong>ÃŽnainte</strong></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id859734" class="title">Compiling RPM</h1></div></div></div><div class="para">
+ After downloading the RPM sources, extracting all the files and installing all the prerequisite libraries, you are ready to start compiling RPM.
+ </div><div class="para">
+ RPM includes quite a few subsystems, such as popt for parsing command-line options. Each of these subsystems requires some configuration. Most of this configuration is automated through the use of the autogen.sh script and the autoconf/automake tool used to create configure scripts.
+ </div><div class="para">
+ The autogen.sh script is a Bourne shell script that checks for specific versions of necessary tools and libraries. After checking dependencies, the autogen.sh script calls different autogen.sh scripts in the beecrypt, libelf, popt, and zlib directories. When done with that task, the autogen.sh script calls configure.
+ </div><div class="para">
+ Pass a command-line option of --noconfigure to disable the call to configure.
+ </div><div class="para">
+ Edit the autogen.sh script if you are using different versions of the necessary tools. The autogen.sh script is coded to require the specific versions of these tools as were used originally to build the RPM package. In addition, your system may have libraries stored in different locations than those expected by the autogen.sh, so it's a good idea to edit this script and verify all the assumptions.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ One really big assumption in this script is that you have a Unix-like operating system. If not, you will need to determine how to set up the Makefiles manually. This requires a lot of trial and error while you edit the Makefiles and then see if you can build the software. Fix each problem that arises and try again.
+ </div><div class="para">
+ When you are done with the autogen.sh script, you can use the following basic commands to create system-specific Makefiles, compile RPM and install the commands:
+ </div><div class="para">
+ $ ./configure
+ </div><div class="para">
+ $ make
+ </div><div class="para">
+ $ make install
+ </div><div class="para">
+ The configure script takes the Makefile.in files and uses these files as templates to create custom versions of Makefile.in files, tuned to your system. (The automake system starts with a Makefile.am file, creates an expanded Makefile.in file, and finally results in a Makefile tuned to your system.) If all else fails, you can copy each Makefile.in file to Makefile and then edit the Makefile to make one that will work on your system.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ See the GNU site, at www.gnu.org, for more on the autoconf and automake tools.
+ </div><div class="para">
+ If the make install step fails, you can manually copy the RPM executables and scripts to a directory for system commands.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch19s02s05.html"><strong>Înapoi</strong>19.2.5. Tools for building RPM</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch19s02s07.html"><strong>Înainte</strong>19.2.7. Handling problems</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch19s02s07.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch19s02s07.html
new file mode 100644
index 0000000..dd9a34e
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch19s02s07.html
@@ -0,0 +1,30 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>19.2.7. Handling problems</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch19s02.html" title="19.2. Bootstrapping RPM On Other Operating Systems" /><link rel="prev" href="ch19s02s06.html" title="19.2.6. Compiling RPM" /><link rel="next" href="ch19s03.html" title="19.3. Setting Up the RPM System" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch19s02s06.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch19s03.html"><stron
g>ÃŽnainte</strong></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id498178" class="title">Handling problems</h1></div></div></div><div class="para">
+ If RPM fails to compile or install, you can still work around many issues. The key is to find out what went wrong, fix the problem, and try again. You may go through this loop many times before RPM successfully compiles and installs.
+ </div><div class="para">
+ Most problems can be solved by changing the configuration settings. If possible, change the inputs to the configure command to specify C compiler options, and so on, that you discover you need. You can then run the basic commands to build RPM again, but with any special options you discovered are necessary:
+ </div><div class="para">
+ $ ./configure –any_options_set_here
+ </div><div class="para">
+ $ make
+ </div><div class="para">
+ $ make install
+ </div><div class="para">
+ If you take this approach, you avoid having to edit a number of Makefiles (one in each source code subdirectory) by hand. You also have an easier time of switching to different command-line options as you determine more solutions to the compilation problems.
+ </div><div class="para">
+ If this won’t work, though, you can edit the Makefile.am file or the generated Makefile directly to add whatever settings are needed. For example, you may need to specify additional directories for libraries, or some C compiler compatibility option.
+ </div><div class="para">
+ As you discover problems, remember you are not alone in porting RPM. Check the RPM mailing list, where the question of getting RPM going on other platforms comes up frequently.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ For details on viewing the RPM mailing list archives and signing up for the list, see www.rpm.org/mailing_list/.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch19s02s06.html"><strong>Înapoi</strong>19.2.6. Compiling RPM</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch19s03.html"><strong>Înainte</strong>19.3. Setting Up the RPM System</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch19s03.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch19s03.html
new file mode 100644
index 0000000..af847f5
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch19s03.html
@@ -0,0 +1,178 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>19.3. Setting Up the RPM System</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-other-os.html" title="Cap. 19. RPM on Other Operating Systems" /><link rel="prev" href="ch19s02s07.html" title="19.2.7. Handling problems" /><link rel="next" href="ch19s03s02.html" title="19.3.2. Creating the RPM environment" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch19s02s07.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch19s03s02.html
"><strong>ÃŽnainte</strong></a></li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id498237" class="title">Setting Up the RPM System</h1></div></div></div><div class="para">
+ Once you have RPM available on your platform, you need to set up the RPM system. This includes setting up the RPM database and creating an RPM environment.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id498249" class="title">Setting up the RPM database</h1></div></div></div><div class="para">
+ After you have the RPM system available on your platform, you need to set up the RPM database. This usually involves two steps:
+ </div><div class="para">
+ *Initializing an empty RPM database
+ </div><div class="para">
+ *Populating the database with packages, especially for dependencies
+ </div><div class="para">
+ Both steps are necessary.
+ </div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id850293" class="title">Initializing an Empty RPM Database</h1></div></div></div><div class="para">
+ After you have the RPM system installed on your platform, the next big step is to create an RPM database for your platform. You can make an empty database with the rpm --initdb command, as shown following:
+ </div><div class="para">
+ # mkdir /var/lib/rpm
+ </div><div class="para">
+ # rpm --initdb
+ </div><div class="para">
+ The first command creates the default directory for the RPM database.
+ </div><div class="para">
+ You may need to pass command-line options to specify a non-default location of the RPM database, such as the following:
+ </div><div class="para">
+ # rpm --dbpath /location/of/your/rpm/database --initdb
+ </div><div class="para">
+ Use a command like this one if you don’t want to place the RPM database in its default location.
+ </div><div class="para">
+ In addition, use the –v option to add more verbose output. This is very useful if errors occur. Use the --root option to specify a different root directory for RPM operations. Use the --rcfile option to specify a non-default set of rc files and the --macros option to specify a non-default set of macros.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ <a class="xref" href="ch-customizing-rpm.html">Cap. 20, <em>Customizing RPM Behavior</em></a> covers RPM customization.
+ </div><div class="para">
+ Initializing the RPM database creates the necessary structure for an empty database. You can then fill, or populate, the database with packages. In most cases, all you need to do is install packages to populate the RPM database, as each installed package gets added to the database.
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id850354" class="title">Handling Dependencies for Packages Installed Without RPM</h1></div></div></div><div class="para">
+ Each time you install a package, you populate the RPM database. This works well, as long as you have already installed all the dependencies for the packages you want to install.
+ </div><div class="para">
+ On an operating system that is based on RPM, such as Red Hat Linux, all packages (except for some bootstrapping code) are installed with RPM. That means nearly everything on the system is defined in the RPM database. The RPM database then has a full knowledge of what you have installed and can properly handle dependencies. Thus, a failure to find a dependency means that you have not installed the requisite package that provides the needed capability.
+ </div><div class="para">
+ On an operating system that is not based on RPM, however, such as Solaris or IRIX, most packages have already been installed by some means other than RPM.. That’s because these operating systems use different native package-management techniques and different package formats.
+ </div><div class="para">
+ It is very likely that RPM packages you want to install have dependencies that come from non-RPM packages. For example, the rpm program on Windows depends on the cygwin environment, yet this environment needs to be installed with a Windows setup.exe program, not with the rpm command.
+ </div><div class="para">
+ To get around this problem, you need to populate the new RPM database with a package or packages that reflect the current system in order to properly handle dependencies. The main way to do this is to set up a virtual package.
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id752824" class="title">Setting Up A Virtual Package</h1></div></div></div><div class="para">
+ You can get around the problem of pre-existing software by building a virtual package that lists the system libraries at mdinstalled without RPM at mdin an RPM package. This way, the rpm command will find that the dependencies are installed, even if they were not really installed with RPM. You need to do this for all capabilities and system libraries installed outside of RPM control.
+ </div><div class="para">
+ To help create such a virtual package, use the vpkg-provides.sh script from the scripts directory. The vpkg-provides.sh script searches a list of directories for shared libraries and interpreters (such as shells). The vpkg-provides.sh script then creates a spec file that lists all the files found, files that are managed outside of RPM. You can use this spec file to create an RPM and install the RPM using the rpm command to populate the RPM database.
+ </div><div class="para">
+ The RPM spec file created by the vpkg-provides.sh doesn’t really install any files, as all the files are already installed. Instead it makes a package that claims ownership for all these files so that RPM dependencies can function properly.
+ </div><div class="para">
+ The vpkg-provides.sh script accepts three main command-line options: --spec_header, --ignore_dirs, and --no_verify.
+ </div><div class="para">
+ The --spec_header option tells the script the name of the RPM spec file it should use as a header for the spec file it will produce. You need to provide the path to the file. For example:
+ </div><div class="para">
+ # sh vpkg-provides.sh --spec_header /path/to/spec/file
+ </div><div class="para">
+ You need to provide a spec file header to make a complete spec file. This header should contain the Summary, Name, Version, and Release settings, at least. <a class="xref" href="ch-specfiles.html">Cap. 9, <em>Working with Spec Files</em></a> covers these spec file tags.
+ </div><div class="para">
+ The --ignore_dirs option tells the vpkg-provides.sh script to ignore certain directories. You need to pass a list of egrep search patterns that identify the directories to ignore. Separate each pattern with a pipe character, |.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ The egrep command may not be available on your system. It may be easier to edit the vpkg-provides.sh script and manually specify the directories to ignore.
+ </div><div class="para">
+ The --no_verify option tells the vpkg-provides.sh script to skip the step of creating a script to verify checksums of all files in the package.
+ </div><div class="para">
+ In addition to these main command-line options, you can also pass the following options to the vpkg-provides.sh script.
+ </div><div class="para">
+ The --shlib_dirs option tells the vpkg-provides.sh script the directories to look for shared libraries. Pass a colon-delimited list of directories. For example:
+ </div><div class="para">
+ # sh vpkg-provides.sh --spec_header /path/to/spec/file \
+ </div><div class="para">
+ --shlib_dirs "/bin:/usr/bin:/sbin:/usr/sbin:/usr/ucb:/usr/bsd"
+ </div><div class="para">
+ The --interp_dirs option tells the vpkg-provides.sh script which directories to look in to find interpreters such as sh, bash, perl, wish (Tcl/Tk), and awk. The --interps option tells the vpkg-provides.sh script the names of the interpreter commands. Both these options expect a colon-delimited list.
+ </div><div class="para">
+ The --find_provides option tells the vpkg-provides.sh script the name of the find-provides script to use, defaulting to /usr/lib/rpm/find-provides.
+ </div><div class="para">
+ The vpkg-provides.sh script defines specific directories to look in for shared libraries and interpreters under various operating systems. You will most likely need to edit this section.
+ </div><div class="para">
+ In fact, if you are working with a non-Unix system, or if you experience problems running the vpkg-provides.sh script, you can edit the file to remove the problematic commands. You can also create a new script in a scripting language supported on your system. The vpkg-provides.sh script is a Linux shell script. Linux and Unix systems should be able to run the script, but non-Unix systems likely won’t have the commands and may also not support shell scripts at all. In an effort to be generic, the vpkg-provides.sh script does a lot of work. You can limit this by explicitly specifying directories and commands, for example. And, if all else fails, you can create a virtual package manually (covered in the following section).
+ </div><div class="para">
+ When complete, the vpkg-provides.sh script outputs a spec file, using the header you provided, and outputs a set of Provides: lines to specify what the package provides. It then outputs some empty definitions for the prep, build, install, and clean sections of the spec file.
+ </div><div class="para">
+ For example, you can run the vpkg-provides.sh script with a command like the following:
+ </div><div class="para">
+ $ sh ./vpkg-provides.sh --spec_header my_header.spec --find_provides ./find-provides --no_verify
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ If you run this script as a non-root user, you may get a number of permission errors as the vpkg-provides.sh script searches through system directories.
+ </div><div class="para">
+ The script will then output your spec file header along with output like that shown in Listing 20-1.
+ </div><div class="para">
+ Listing 20-1: Output from the vpkg-provides.sh script
+ </div><div class="para">
+ Provides: /bin/sh
+ </div><div class="para">
+ Provides: /bin/csh
+ </div><div class="para">
+ Provides: /bin/ksh
+ </div><div class="para">
+ Provides: /bin/perl
+ </div><div class="para">
+ Provides: /bin/awk
+ </div><div class="para">
+ Provides: /bin/nawk
+ </div><div class="para">
+ Provides: /bin/oawk
+ </div><div class="para">
+ Provides: /usr/bin/sh
+ </div><div class="para">
+ Provides: /usr/bin/csh
+ </div><div class="para">
+ Provides: /usr/bin/ksh
+ </div><div class="para">
+ Provides: /usr/bin/perl
+ </div><div class="para">
+ Provides: /usr/bin/awk
+ </div><div class="para">
+ Provides: /usr/bin/nawk
+ </div><div class="para">
+ Provides: /usr/bin/oawk
+ </div><div class="para">
+ Provides: /sbin/sh
+ </div><div class="para">
+ Provides: /usr/dt/bin/dtksh
+ </div><div class="para">
+ Provides: /usr/xpg4/bin/sh
+ </div><div class="para">
+ Provides: /usr/xpg4/bin/awk
+ </div><div class="para">
+ %prep
+ </div><div class="para">
+ # nothing to do
+ </div><div class="para">
+ %build
+ </div><div class="para">
+ # nothing to do
+ </div><div class="para">
+ %install
+ </div><div class="para">
+ # nothing to do
+ </div><div class="para">
+ %clean
+ </div><div class="para">
+ # nothing to do
+ </div><div class="para">
+ %files
+ </div><div class="para">
+ # no files in a virtual package
+ </div><div class="para">
+ The vpkg-provides.sh script also outputs a package description that explains how the package was created. This is important so that you know this is a virtual package.
+ </div><div class="para">
+ When done, use the rpmbuild command to create an RPM from the generated spec file.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ <a class="xref" href="ch-creating-rpms.html">Cap. 8, <em>Creating RPMs: An Overview</em></a> covers how to run the rpmbuild command, and <a class="xref" href="ch-specfiles.html">Cap. 9, <em>Working with Spec Files</em></a> covers spec files in detail.
+ </div></div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id793008" class="title">Creating a Virtual Package Manually</h1></div></div></div><div class="para">
+ Even on Unix-like systems you may experience troubles with the vpkg-provides.sh script. That’s simply because the vpkg-provides.sh script assumes a number of Unix and GNU utilities are available. In most cases, it will work best if you can fix what went wrong and run the vpkg-provides.sh script again.
+ </div><div class="para">
+ If all else fails, though, you can create a virtual package spec file manually. Create a spec file starting with the Summary, Name, Version, and Release settings.
+ </div><div class="para">
+ Looking at the output shown in Listing 20-1, you can create a Provides: statement for each shared library on your system, and each interpreter, such as shells. Add each statement to your spec file. For example:
+ </div><div class="para">
+ Provides: libgen.so
+ </div><div class="para">
+ Copy the prep, build, install, and clean sections exactly as they are in Listing 20-1. You can now run the rpmbuild command to create a virtual package. Install this package.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch19s02s07.html"><strong>Înapoi</strong>19.2.7. Handling problems</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch19s03s02.html"><strong>Înainte</strong>19.3.2. Creating the RPM environment</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch19s03s02.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch19s03s02.html
new file mode 100644
index 0000000..5e4d7fa
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch19s03s02.html
@@ -0,0 +1,53 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>19.3.2. Creating the RPM environment</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch19s03.html" title="19.3. Setting Up the RPM System" /><link rel="prev" href="ch19s03.html" title="19.3. Setting Up the RPM System" /><link rel="next" href="ch19s04.html" title="19.4. Creating Non-Linux RPMS" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch19s03.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch19s04.html"><strong>ÃŽnainte</stron
g></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id793043" class="title">Creating the RPM environment</h1></div></div></div><div class="para">
+ The RPM environment is made up of a large number of RPM settings and macro definitions. Run the rpm --showrc command to see the current environment settings on Linux:
+ </div><div class="para">
+ $ rpm –showrc
+ </div><div class="para">
+ ARCHITECTURE AND OS:
+ </div><div class="para">
+ build arch : i386
+ </div><div class="para">
+ compatible build archs: i686 i586 i486 i386 noarch
+ </div><div class="para">
+ build os : Linux
+ </div><div class="para">
+ compatible build os's : Linux
+ </div><div class="para">
+ install arch : i686
+ </div><div class="para">
+ install os : Linux
+ </div><div class="para">
+ compatible archs : i686 i586 i486 i386 noarch
+ </div><div class="para">
+ compatible os's : Linux
+ </div><div class="para">
+ </div><div class="para">
+ RPMRC VALUES:
+ </div><div class="para">
+ macrofiles : /usr/lib/rpm/macros:/usr/lib/rpm/i686-linux/macros:/etc/
+ </div><div class="para">
+ rpm/macros.specspo:/etc/rpm/macros.db1:/etc/rpm/macros.cdb:/etc/rpm/macros:/etc/
+ </div><div class="para">
+ rpm/i686-linux/macros:~/.rpmmacros
+ </div><div class="para">
+ optflags : -O2 -march=i686
+ </div><div class="para">
+ This output was truncated for space. As you can see, there are a lot of expected settings. You need to set up these same settings and macros, but with the proper values for the new system on which you are running RPM.
+ </div><div class="para">
+ The files rpmrc.in and macros.in serve as the default templates used to create the rc and macro settings, respectively. These files are modified by the configure script to include values specific to the local operating system. You can edit these files as needed for your system, prior to installing RPM. That is, edit these files between calling the make command and the make install command.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ <a class="xref" href="ch-customizing-rpm.html">Cap. 20, <em>Customizing RPM Behavior</em></a> covers how to customize the RPM settings and macros, along with the popt aliases.
+ </div><div class="para">
+ The INSTALL file in the RPM sources also describes some modifications you may want to make to the macros.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch19s03.html"><strong>Înapoi</strong>19.3. Setting Up the RPM System</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch19s04.html"><strong>Înainte</strong>19.4. Creating Non-Linux RPMS</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch19s04.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch19s04.html
new file mode 100644
index 0000000..58a9f39
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch19s04.html
@@ -0,0 +1,40 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>19.4. Creating Non-Linux RPMS</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-other-os.html" title="Cap. 19. RPM on Other Operating Systems" /><link rel="prev" href="ch19s03s02.html" title="19.3.2. Creating the RPM environment" /><link rel="next" href="ch19s04s02.html" title="19.4.2. Cross-building packages" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch19s03s02.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch19s04s0
2.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id512935" class="title">Creating Non-Linux RPMS</h1></div></div></div><div class="para">
+ Once you have RPM set up on a system, you should be able to create RPMs using the rpmbuild command on that system.
+ </div><div class="para">
+ Warning
+ </div><div class="para">
+ Do not build RPM packages logged in as a root or Administrator user. If something goes wrong, rpmbuild could destroy files in your system. Remember that spec files can define a number of commands and shell scripts. Any of these could have an error that could cause major damage when run as a root user.
+ </div><div class="para">
+ Before building RPMs with the rpmbuild command, though, you may want to customize the build environment to better reflect your system. You may also find it is too difficult to build most RPMs on the non-Linux system and instead focus on cross-building packages, should the rpmbuild command not work on the target systems.
+ </div><div class="para">
+ This section covers topics related to building RPMs on or for non-Linux systems.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id612860" class="title">Setting up a build environment</h1></div></div></div><div class="para">
+ In RPM terms, your build environment consists of the directories where you build RPMs, as well as the rc and macro settings that define all of the variables in an RPM-based system. To set up your build environment, you need to ensure that all the rc and macro settings reflect the true environment on your non-Linux system.
+ </div><div class="para">
+ The rpm --showrc command, discussed previously in the "Creating the RPM Environment" section, lists the settings for your system. You can use this command to verify all the settings.
+ </div><div class="para">
+ You may want to change some settings, such as the top directory where RPMs are built. By default, this setting is something like the following:
+ </div><div class="para">
+ _topdir %{_usrsrc}/redhat
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ See <a class="xref" href="ch-customizing-rpm.html">Cap. 20, <em>Customizing RPM Behavior</em></a> for more on how to customize the rc and macro settings.
+ </div><div class="para">
+ In most cases the _topdir setting on Red Hat Linux systems map to the /usr/src/redhat directory. Your system may not even have a /usr/src directory. Also you may not want to build RPMs in a redhat directory, which may cause confusion if you are building on a non-Red Hat Linux system.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ See <a class="xref" href="ch-other-linuxes.html">Cap. 18, <em>Using RPM on Non-Red Hat Linuxes</em></a> for more information on setting up a build environment for RPMs. <a class="xref" href="ch-other-linuxes.html">Cap. 18, <em>Using RPM on Non-Red Hat Linuxes</em></a> focuses on other Linux systems, but many of the same techniques apply.
+ </div><div class="para">
+ With a build environment set up, you should be able to create RPMs with the rpmbuild command. If this doesn’t work, or is too difficult, then you can try cross-building packages.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch19s03s02.html"><strong>Înapoi</strong>19.3.2. Creating the RPM environment</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch19s04s02.html"><strong>Înainte</strong>19.4.2. Cross-building packages</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch19s04s02.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch19s04s02.html
new file mode 100644
index 0000000..19a78fb
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch19s04s02.html
@@ -0,0 +1,64 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>19.4.2. Cross-building packages</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch19s04.html" title="19.4. Creating Non-Linux RPMS" /><link rel="prev" href="ch19s04.html" title="19.4. Creating Non-Linux RPMS" /><link rel="next" href="ch19s05.html" title="19.5. Summary" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch19s04.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch19s05.html"><strong>ÃŽnainte</strong></a></li></ul><div
class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id612929" class="title">Cross-building packages</h1></div></div></div><div class="para">
+ You may find that it is too difficult to create RPMs on a given platform. It may be easier to build the RPMs on another platform, such as a Linux system, as if it were on the target platform. This is called cross-building packages, since you are building a package on one system specifically designed for another.
+ </div><div class="para">
+ In most cases, the target platform is quite different from the system where you cross-build packages. Otherwise, you would likely just build the RPMs on the target platform.
+ </div><div class="para">
+ The key issues with cross-building are the following:
+ </div><div class="para">
+ *You must compile any executables with a cross compiler for the proper target platform.
+ </div><div class="para">
+ *You must set the target platform in the RPMs you build.
+ </div><div class="para">
+ *You must manage dependencies, and likely need to turn off the automatic generation of dependencies.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ Setting up a cross-building environment is oftentimes more work than it is worth. If you can compile applications and build packages on the target system, do that. The cross-building option should be used only if you really cannot build packages on the target system. For example, many handheld or small-format computers lack the processor performance or memory to compile applications. These are good candidates for cross-building.
+ </div><div class="para">
+ To compile executables for another platform, especially a platform with a different processor architecture, you need a cross compiler. A cross compiler runs on one system and produces executables for another.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ Cross compilers are heavily used when working with embedded and small device systems. The embedded system may not have the processor power to compile applications, or it may simply be inconvenient to compile applications on the embedded system.
+ </div><div class="para">
+ The Linux gcc compiler can act as a cross compiler if you install the right gcc add-on packages. See the GNU site for more on the gcc compiler.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ You can download GCC and other GNU software from www.gnu.org.
+ </div><div class="para">
+ In addition to compiling for the target platform, you need to ensure that the RPM is marked as being for the target architecture. If not, the rpm command will fail when trying to install the RPM on the target system.
+ </div><div class="para">
+ You can set the target architecture with the --target option to the rpmbuild command. For example:
+ </div><div class="para">
+ rpmbuild –bi --target arm-sharp-linux
+ </div><div class="para">
+ This specifies a target CPU architecture of ARM, the vendor Sharp (which just happens to make an ARM-based Linux device) and the operating system of Linux. The basic format is:
+ </div><div class="para">
+ cpu-vendor-os
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ See <a class="xref" href="ch-rpmbuild.html">Cap. 11, <em>Controlling the Build with <code class="command">rpmbuild</code></em></a> for more on using the --target option to the rpmbuild command.
+ </div><div class="para">
+ You must also turn off or correct any automatically generated dependencies in RPMs you build for other platforms. That is, any dependencies based on the operating system or architecture of the system you are cross-building on will likely not be found, or be found in a different location or format, on the target platform.
+ </div><div class="para">
+ This is where the handy RPM feature of automatically building the dependencies does not work to your advantage. You can turn off this feature, however.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ See <a class="xref" href="ch-other-linuxes.html">Cap. 18, <em>Using RPM on Non-Red Hat Linuxes</em></a> for information on how to turn off the automatic generation of dependencies.
+ </div><div class="para">
+ You should turn off the automatically building of dependencies for any packages you cross build.
+ </div><div class="para">
+ Using these techniques, you can build packages on one system for use on another, very different system. Due to the difficulties, you should only go this route if it becomes too difficult to use the rpmbuild command on the target systems.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch19s04.html"><strong>Înapoi</strong>19.4. Creating Non-Linux RPMS</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch19s05.html"><strong>Înainte</strong>19.5. Summary</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch19s05.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch19s05.html
new file mode 100644
index 0000000..e7f6bcd
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch19s05.html
@@ -0,0 +1,24 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>19.5. Summary</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-other-os.html" title="Cap. 19. RPM on Other Operating Systems" /><link rel="prev" href="ch19s04s02.html" title="19.4.2. Cross-building packages" /><link rel="next" href="ch-customizing-rpm.html" title="Cap. 20. Customizing RPM Behavior" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch19s04s02.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch-c
ustomizing-rpm.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id680716" class="title">Summary</h1></div></div></div><div class="para">
+ With its superior package-management capabilities, especially for automated installations and upgrades, you may want to use RPM on non-Linux platforms. As the experience of many developers has shown, you can indeed use RPM on non-Linux platforms.
+ </div><div class="para">
+ The rpm.org site maintains a listing of operating systems where developers have ported RPM. If you are lucky, you can download RPM for your operating system and start working right away. If you are not lucky, you will need to port RPM to your target system.
+ </div><div class="para">
+ If RPM has been ported to your architecture, download the package and follow the installation instructions. If RPM has not been ported to your architecture, download the RPM sources and all prerequisite libraries. You may need to port each library to your architecture before you can even begin to port RPM.
+ </div><div class="para">
+ The RPM sources use a configured build process that also requires some prerequisite tools. You need to get or port these to your architecture as well. Whew.
+ </div><div class="para">
+ Once everything is in place, you can start the port of RPM. In many cases, you just need to figure out how to get RPM to compile and everything will fall into place. In other cases, you will need to work on each RPM subsystem to get it to build and run.
+ </div><div class="para">
+ After you have RPM for your system, you need to initialize the RPM database with the rpm --initdb command. You can then start to populate your RPM database. Because a large number of libraries have already been installed on your system, you may need to create a virtual package that claims to provide these files. Installing such a virtual package will allow you to install other RPMs that may be dependent on system libraries.
+ </div><div class="para">
+ Much of porting RPM to another platform depends on the RPM environment and how you need to customize that environment. The next chapter shows how to customize your RPM environment, on Linux or on other operating systems.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch19s04s02.html"><strong>Înapoi</strong>19.4.2. Cross-building packages</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch-customizing-rpm.html"><strong>Înainte</strong>Cap. 20. Customizing RPM Behavior</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch20s02.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch20s02.html
new file mode 100644
index 0000000..f547c7b
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch20s02.html
@@ -0,0 +1,49 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>20.2. Configuring RPM Settings</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-customizing-rpm.html" title="Cap. 20. Customizing RPM Behavior" /><link rel="prev" href="ch-customizing-rpm.html" title="Cap. 20. Customizing RPM Behavior" /><link rel="next" href="ch20s02s02.html" title="20.2.2. Locating the rpmrc files" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-customizing-rpm.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n"
href="ch20s02s02.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id558152" class="title">Configuring RPM Settings</h1></div></div></div><div class="para">
+ RPM includes hundreds of settings based on your current system architecture, environment, and which version of the RPM system you have installed. The old settings, called rc or rpmrc settings, are gradually being phased out by the newer, more consistent and more powerful macros.
+ </div><div class="para">
+ You can still edit the rc settings, but in most cases you should edit macros instead.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id558168" class="title">Viewing the current settings</h1></div></div></div><div class="para">
+ To view the current settings, use the --showrc command-line option:
+ </div><div class="para">
+ $ rpm –showrc
+ </div><div class="para">
+ ARCHITECTURE AND OS:
+ </div><div class="para">
+ build arch : i386
+ </div><div class="para">
+ compatible build archs: i686 i586 i486 i386 noarch
+ </div><div class="para">
+ build os : Linux
+ </div><div class="para">
+ compatible build os's : Linux
+ </div><div class="para">
+ install arch : i686
+ </div><div class="para">
+ install os : Linux
+ </div><div class="para">
+ compatible archs : i686 i586 i486 i386 noarch
+ </div><div class="para">
+ compatible os's : Linux
+ </div><div class="para">
+ </div><div class="para">
+ RPMRC VALUES:
+ </div><div class="para">
+ macrofiles : /usr/lib/rpm/macros:/usr/lib/rpm/i686-linux/macros:/etc/
+ </div><div class="para">
+ rpm/macros.specspo:/etc/rpm/macros.db1:/etc/rpm/macros.cdb:/etc/rpm/macros:/etc/
+ </div><div class="para">
+ rpm/i686-linux/macros:~/.rpmmacros
+ </div><div class="para">
+ optflags : -O2 -march=i686
+ </div><div class="para">
+ This command displays the architecture and operating system information first, and then lists all the rpmrc values, shown here truncated for space.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-customizing-rpm.html"><strong>Înapoi</strong>Cap. 20. Customizing RPM Behavior</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch20s02s02.html"><strong>Înainte</strong>20.2.2. Locating the rpmrc files</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch20s02s02.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch20s02s02.html
new file mode 100644
index 0000000..4ad61a3
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch20s02s02.html
@@ -0,0 +1,82 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>20.2.2. Locating the rpmrc files</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch20s02.html" title="20.2. Configuring RPM Settings" /><link rel="prev" href="ch20s02.html" title="20.2. Configuring RPM Settings" /><link rel="next" href="ch20s02s03.html" title="20.2.3. Changing settings" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch20s02.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch20s02s03.html"><strong>ÃŽnainte</stron
g></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id681418" class="title">Locating the rpmrc files</h1></div></div></div><div class="para">
+ The --showrc option reads in all the rpmrc files from the various locations. By default, this is /usr/lib/rpm/rpmrc, /etc/rpm/rpmrc, and a file named .rpmrc (with a leading period) in your home directory.
+ </div><div class="para">
+ These files are read in the order given, so that the later files can override settings in the earlier files.
+ </div><div class="para">
+ The uses for these files are listed in Table 21-3.
+ </div><div class="para">
+ Table 21-3 Uses for the rpmrc files
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ File
+ </div>
+
+ </td><td>
+ <div class="para">
+ Holds
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ /usr/lib/rpm/rpmrc
+ </div>
+
+ </td><td>
+ <div class="para">
+ RPM standard settings
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ /etc/rpm/rpmrc
+ </div>
+
+ </td><td>
+ <div class="para">
+ Per-system configuration
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ $HOME/.rpmrc
+ </div>
+
+ </td><td>
+ <div class="para">
+ Per-user configuration
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ Note
+ </div><div class="para">
+ The file /usr/lib/rpm/rpmrc gets overwritten each time you upgrade RPM. Do not customize this file.
+ </div><div class="para">
+ You can override this list of files by calling the rpm or rpmbuild commands with the --rcfile option. This option expects a semicolon at nddelimited list of files to read in, in order. For example, if you are working on a 686-architecture Intel platform, you can create a file with the following setting:
+ </div><div class="para">
+ optflags: i686 -g
+ </div><div class="para">
+ Note that this disables optimization, so it is not a good setting. (The use of this value will make the result more visible.)
+ </div><div class="para">
+ If you name this file .rpmnew and place it in your home directory, you can configure an alternate set of files with the --rcfile option and then evaluate the new optflags setting. For example:
+ </div><div class="para">
+ $ rpm --eval "%{optflags}"
+ </div><div class="para">
+ -O2 -march=i386 -mcpu=i686
+ </div><div class="para">
+ $ rpm --rcfile $HOME/.rpmnew --eval "%{optflags}"
+ </div><div class="para">
+ -g
+ </div><div class="para">
+ This example shows the value before and after changing the configuration files.
+ </div><div class="para">
+ When you use the --rcfile option, only the first file listed must exist. The rest of the files are optional. When you use the --rcfile option, however, the file /usr/lib/rpm/rpmrc is read first, and then the list of files you provide with the --rcfile option. The file /usr/lib/rpm/rpmrc is always used.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch20s02.html"><strong>Înapoi</strong>20.2. Configuring RPM Settings</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch20s02s03.html"><strong>Înainte</strong>20.2.3. Changing settings</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch20s02s03.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch20s02s03.html
new file mode 100644
index 0000000..9b7425d
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch20s02s03.html
@@ -0,0 +1,36 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>20.2.3. Changing settings</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch20s02.html" title="20.2. Configuring RPM Settings" /><link rel="prev" href="ch20s02s02.html" title="20.2.2. Locating the rpmrc files" /><link rel="next" href="ch20s02s03s02.html" title="20.2.3.2. Setting the Architecture Values" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch20s02s02.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch20s02s03s02
.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id860734" class="title">Changing settings</h1></div></div></div><div class="para">
+ You can edit the per-user or per-system rc files to change the settings. The format of the rpmrc files is fairly simple but contains a few exceptions. The most basic format is:
+ </div><div class="para">
+ setting: value
+ </div><div class="para">
+ The settings get more complicated as the rpmrc syntax supports defining settings for multiple architectures at once. In that case, the typical format is:
+ </div><div class="para">
+ setting: uname: value
+ </div><div class="para">
+ The uname portion is replaced by a value that comes from the uname(2) system call, for example, i686 on a 686-class Intel architecture machine.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ In most cases, your best bet is to copy an existing setting and modify it, rather than remembering all the exceptions.
+ </div><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id860773" class="title">Setting the optflags</h1></div></div></div><div class="para">
+ One exception to the rule is the optflags setting, which controls C compiler options for optimization. The format for the optflags setting is:
+ </div><div class="para">
+ setting: arch value
+ </div><div class="para">
+ There is no colon after the architecture. For example:
+ </div><div class="para">
+ optflags: i686 -O2 -march=i686
+ </div><div class="para">
+ optflags: alphaev5 -O2 -mieee -mcpu=ev5
+ </div><div class="para">
+ This example sets the optimization flags for an i686 system to -O2 -march=i686 and an alphaev5 system to -O2 -mieee -mcpu=ev5. If your system is running on a 686-class processor, you will get one set of optimization flags. If your system is running on a V5 Alpha processor, you will get a different set.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch20s02s02.html"><strong>Înapoi</strong>20.2.2. Locating the rpmrc files</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch20s02s03s02.html"><strong>Înainte</strong>20.2.3.2. Setting the Architecture Values</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch20s02s03s02.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch20s02s03s02.html
new file mode 100644
index 0000000..2d1c530
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch20s02s03s02.html
@@ -0,0 +1,88 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>20.2.3.2. Setting the Architecture Values</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch20s02s03.html" title="20.2.3. Changing settings" /><link rel="prev" href="ch20s02s03.html" title="20.2.3. Changing settings" /><link rel="next" href="ch20s03.html" title="20.3. Adding Popt Aliases" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch20s02s03.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch20s03.html"><strong>ÃŽnainte</strong></a><
/li></ul><div class="sect3"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id668343" class="title">Setting the Architecture Values</h1></div></div></div><div class="para">
+ The arch_canon setting builds up a table of mappings between architecture names and the numbers used internally. The following example shows the Intel and SPARC architecture settings to 1 and 3 internally.
+ </div><div class="para">
+ arch_canon: athlon: athlon 1
+ </div><div class="para">
+ arch_canon: i686: i686 1
+ </div><div class="para">
+ arch_canon: i586: i586 1
+ </div><div class="para">
+ arch_canon: i486: i486 1
+ </div><div class="para">
+ arch_canon: i386: i386 1
+ </div><div class="para">
+ </div><div class="para">
+ arch_canon: sparc: sparc 3
+ </div><div class="para">
+ arch_canon: sun4: sparc 3
+ </div><div class="para">
+ arch_canon: sun4m: sparc 3
+ </div><div class="para">
+ arch_canon: sun4c: sparc 3
+ </div><div class="para">
+ arch_canon: sun4d: sparc 3
+ </div><div class="para">
+ arch_canon: sparcv9: sparcv9 3
+ </div><div class="para">
+ The arch_compat setting builds a table of compatible architectures. The format is:
+ </div><div class="para">
+ arch_compat: arch: compatible_with
+ </div><div class="para">
+ This sets the given architecture arch as being compatible with another architecture.
+ </div><div class="para">
+ For example:
+ </div><div class="para">
+ arch_compat: athlon: i686
+ </div><div class="para">
+ This setting indicates that an athlon architecture is compatible with an i686. The table gets built up further with the following Intel-architecture compatibilities:
+ </div><div class="para">
+ arch_compat: i686: i586
+ </div><div class="para">
+ arch_compat: i586: i486
+ </div><div class="para">
+ arch_compat: i486: i386
+ </div><div class="para">
+ arch_compat: i386: noarch
+ </div><div class="para">
+ The os_canon setting defines a table of operating system labels and internal numeric values. The basic syntax is:
+ </div><div class="para">
+ os_canon: arch: name value
+ </div><div class="para">
+ The arch comes from the uname(2) call. The name provides an RPM name for that operating system, and the value defines an internal numeric ID for that OS, for example:
+ </div><div class="para">
+ os_canon: Linux: Linux 1
+ </div><div class="para">
+ os_canon: HP-UX: hpux10 6
+ </div><div class="para">
+ The buildarchtranslate setting defines the operating system settings to use as the build architecture. This value translates information from the uname(2) call to a value used by the arch_canon setting. For example:
+ </div><div class="para">
+ buildarchtranslate: athlon: i386
+ </div><div class="para">
+ buildarchtranslate: i686: i386
+ </div><div class="para">
+ buildarchtranslate: i586: i386
+ </div><div class="para">
+ buildarchtranslate: i486: i386
+ </div><div class="para">
+ buildarchtranslate: i386: i386
+ </div><div class="para">
+ </div><div class="para">
+ buildarchtranslate: sun4c: sparc
+ </div><div class="para">
+ buildarchtranslate: sun4d: sparc
+ </div><div class="para">
+ buildarchtranslate: sun4m: sparc
+ </div><div class="para">
+ buildarchtranslate: sparcv9: sparc
+ </div><div class="para">
+ buildarchtranslate: sun4u: sparc64
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch20s02s03.html"><strong>Înapoi</strong>20.2.3. Changing settings</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch20s03.html"><strong>Înainte</strong>20.3. Adding Popt Aliases</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch20s03.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch20s03.html
new file mode 100644
index 0000000..4a7e492
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch20s03.html
@@ -0,0 +1,92 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>20.3. Adding Popt Aliases</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-customizing-rpm.html" title="Cap. 20. Customizing RPM Behavior" /><link rel="prev" href="ch20s02s03s02.html" title="20.2.3.2. Setting the Architecture Values" /><link rel="next" href="ch20s03s02.html" title="20.3.2. Customizing popt aliases" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch20s02s03s02.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" hr
ef="ch20s03s02.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id804344" class="title">Adding Popt Aliases</h1></div></div></div><div class="para">
+ Popt provides a powerful library and RPM subsystem for handling the very complex RPM command-line options. You can customize your RPM usage by defining popt aliases for complex command-line arguments to the rpm or rpmbuild commands. A popt alias is a command-line option that expands to other command-line options.
+ </div><div class="para">
+ This technique is used internally to define quite a few command-line options to the rpm and rpmbuild commands in terms of other, more complex options. Many of these aliases define simple command-line options in place of more complex query format options.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ <a class="xref" href="ch-using-rpm-db.html">Cap. 4, <em>Using the RPM Database</em></a> covers the query format.
+ </div><div class="para">
+ For example, the following entry defines the --requires and –R command-line options to the rpm command:
+ </div><div class="para">
+ rpm alias --requires --qf \
+ </div><div class="para">
+ "[%{REQUIRENAME} %{REQUIREFLAGS:depflags} %{REQUIREVERSION}\n]" \
+ </div><div class="para">
+ --POPTdesc=$"list capabilities required by package(s)"
+ </div><div class="para">
+ rpm alias -R --requires
+ </div><div class="para">
+ These options are set in the file /usr/lib/rpm/rpmpopt-4.1.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ This is specific to RPM 4.1. Other releases of RPM use the same naming format but with the current RPM version number, such as 4.2 and so on.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id692629" class="title">Defining aliases</h1></div></div></div><div class="para">
+ Defining aliases is pretty easy. The basic syntax is:
+ </div><div class="para">
+ command_name alias option expansion
+ </div><div class="para">
+ To create an alias for the rpm command, you use rpm for the command_name.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ The command_name must be the name passed to the C poptGetContext function, covered in <a class="xref" href="ch-programming-c.html">Cap. 15, <em>Programming RPM with C</em></a> .
+ </div><div class="para">
+ Follow this with alias and then the option. You will need separate aliases for the long and short options. The expansion defines the alias in terms of other already-defined command-line parameters.
+ </div><div class="para">
+ You can define some complex aliases, such as the following one to display information about a package:
+ </div><div class="para">
+ rpm alias --info --qf 'Name : %-27{NAME} Relocations: %|PREFIXES?{[%{PREFIXES} ]}:{(not relocateable)}|\n\
+ </div><div class="para">
+ Version : %-27{VERSION} Vendor: %{VENDOR}\n\
+ </div><div class="para">
+ Release : %-27{RELEASE} Build Date: %{BUILDTIME:date}\n\
+ </div><div class="para">
+ Install date: %|INSTALLTIME?{%-27{INSTALLTIME:date}}:{(not installed) }| Build Host: %{BUILDHOST}\n\
+ </div><div class="para">
+ Group : %-27{GROUP} Source RPM: %{SOURCERPM}\n\
+ </div><div class="para">
+ Size : %-27{SIZE}%|LICENSE?{ License: %{LICENSE}}|\n\
+ </div><div class="para">
+ Signature : %|DSAHEADER?{%{DSAHEADER:pgpsig}}:{%|RSAHEADER?{%{RSAHEADER:pgpsig}}:{%|SIGGPG?{%{SIGGPG:pgpsig}}:{%|SIGPGP?{%{SIGPGP:pgpsig}}:{(none)}|}|}|}|\n\
+ </div><div class="para">
+ %|PACKAGER?{Packager : %{PACKAGER}\n}|\
+ </div><div class="para">
+ %|URL?{URL : %{URL}\n}|\
+ </div><div class="para">
+ Summary : %{SUMMARY}\n\
+ </div><div class="para">
+ Description :\n%{DESCRIPTION}\n' \
+ </div><div class="para">
+ --POPTdesc=$"list descriptive information from package(s)"
+ </div><div class="para">
+ Popt aliases get evaluated into Linux commands, so you can use pipes and other aspects of Linux shells in your aliases.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ Look closely at the examples in the /usr/lib/rpm/rpmpopt-4.1 file. This is the most complete set of popt alias examples for RPM commands.
+ </div><div class="para">
+ You can also define aliases that can set RPM macros, such as the following alias for setting the path to the RPM database:
+ </div><div class="para">
+ rpm alias --dbpath --define '_dbpath !#:+'
+ </div><div class="para">
+ In this example, !#:+ was defined to behave like a shell history-editing command. With popt, this means to grab the next command-line parameter and place it into the command defined for the alias.
+ </div><div class="para">
+ To support the --help and --usage options, you can define the --POPTdesc and --POPTargs options to the alias as shown in the previous examples. These options also support internationalization.
+ </div><div class="para">
+ All together, the popt alias setting is very close to the popt option table entries used with the C programming API.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ <a class="xref" href="ch-programming-c.html">Cap. 15, <em>Programming RPM with C</em></a> shows how to program with the popt library.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch20s02s03s02.html"><strong>Înapoi</strong>20.2.3.2. Setting the Architecture Values</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch20s03s02.html"><strong>Înainte</strong>20.3.2. Customizing popt aliases</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch20s03s02.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch20s03s02.html
new file mode 100644
index 0000000..cadad41
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch20s03s02.html
@@ -0,0 +1,36 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>20.3.2. Customizing popt aliases</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch20s03.html" title="20.3. Adding Popt Aliases" /><link rel="prev" href="ch20s03.html" title="20.3. Adding Popt Aliases" /><link rel="next" href="ch20s04.html" title="20.4. Summary" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch20s03.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch20s04.html"><strong>ÃŽnainte</strong></a></li></ul><div class="
sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id811776" class="title">Customizing popt aliases</h1></div></div></div><div class="para">
+ Like RPM macros and settings, popt aliases are defined in a cascading set of files. The official RPM aliases are defined in /usr/lib/rpm/rpmpopt-4.1 for rpm 4.1.
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ Do not modify this file! The RPM system depends on this file for proper functioning. Incorrect changes might disable many options to the rpm command.
+ </div><div class="para">
+ Store per-system popt aliases in /etc/popt. Store per-user aliases in $HOME/.popt (with a leading period).
+ </div><div class="para">
+ Note
+ </div><div class="para">
+ These files are shared by all applications that use popt.
+ </div><div class="para">
+ For example, you can define an alias for rpm -qa that executes faster than the normal query all packages command, by turning off the tests for digest signature verification. To do so, add the following line to a file named .popt in your home directory:
+ </div><div class="para">
+ rpm alias --qall -qa --nodigest --nosignature
+ </div><div class="para">
+ Once you set up this alias, you can run the following command in place of rpm -qa:
+ </div><div class="para">
+ $ rpm --qall
+ </div><div class="para">
+ This should execute about one-third to one-half faster than the normal rpm -qa command.
+ </div><div class="para">
+ Warning
+ </div><div class="para">
+ Turning off the signature and digest tests means you are ignoring important information that pertains to the integrity of your system. That is why the alias shown here does not override the normal -qa option, and instead defines a new --qall option
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch20s03.html"><strong>Înapoi</strong>20.3. Adding Popt Aliases</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch20s04.html"><strong>Înainte</strong>20.4. Summary</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch20s04.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch20s04.html
new file mode 100644
index 0000000..095037e
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch20s04.html
@@ -0,0 +1,14 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>20.4. Summary</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-customizing-rpm.html" title="Cap. 20. Customizing RPM Behavior" /><link rel="prev" href="ch20s03s02.html" title="20.3.2. Customizing popt aliases" /><link rel="next" href="ch-command-reference.html" title="Cap. 21. RPM Command Reference" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch20s03s02.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch-
command-reference.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id880084" class="title">Summary</h1></div></div></div><div class="para">
+ This chapter shows the many ways you can customize RPM usage for your system or your own personal environment. You can define RPM macros, which is the preferred way to make RPM settings. Or you can set RPM values in the older rpmrc files, which are now mostly replaced by RPM macros.
+ </div><div class="para">
+ Using popt, the powerful command-line option parser, you can define aliases to add simple options that popt expands into whatever you define. Many of the rpm command-line options are defined this way.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch20s03s02.html"><strong>Înapoi</strong>20.3.2. Customizing popt aliases</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch-command-reference.html"><strong>Înainte</strong>Cap. 21. RPM Command Reference</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch21s02.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch21s02.html
new file mode 100644
index 0000000..e3f9523
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch21s02.html
@@ -0,0 +1,98 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>21.2. The rpmbuild Command</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-command-reference.html" title="Cap. 21. RPM Command Reference" /><link rel="prev" href="ch-command-reference.html" title="Cap. 21. RPM Command Reference" /><link rel="next" href="ch21s02s02.html" title="21.2.2. Building from a compressed tar archive" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-command-reference.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a
accesskey="n" href="ch21s02s02.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id797785" class="title">The rpmbuild Command</h1></div></div></div><div class="para">
+ The rpmbuild command builds RPMs. Most of the options are duplicated. The options that begin with –b build from a spec file, and the options that begin with –t build from a compressed tar archive, commonly called a tarball.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id568724" class="title">Building from a spec file</h1></div></div></div><div class="para">
+ Table A-8 lists the rpmbuild options for building RPMs from a spec file.
+ </div><div class="para">
+ Table A-8 Options for building RPMs from a spec file
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Option
+ </div>
+
+ </td><td>
+ <div class="para">
+ Usage
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -ba
+ </div>
+
+ </td><td>
+ <div class="para">
+ Build all, both a binary and source RPM
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -bb
+ </div>
+
+ </td><td>
+ <div class="para">
+ Build a binary RPM
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -bc
+ </div>
+
+ </td><td>
+ <div class="para">
+ Build (compile) the program but do not make the full RPM, by executing the build commands through the %build section and stopping
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -bp
+ </div>
+
+ </td><td>
+ <div class="para">
+ Prepare for building a binary RPM, by executing the build commands through the %prep section and stopping
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -bi
+ </div>
+
+ </td><td>
+ <div class="para">
+ Execute the build commands through the %install section and stop
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -bl
+ </div>
+
+ </td><td>
+ <div class="para">
+ Check the listing of files for the RPM
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -bs
+ </div>
+
+ </td><td>
+ <div class="para">
+ Build a source RPM only
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ Each of these options requires the name of a spec file at the end of the command line.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-command-reference.html"><strong>Înapoi</strong>Cap. 21. RPM Command Reference</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch21s02s02.html"><strong>Înainte</strong>21.2.2. Building from a compressed tar archive</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch21s02s02.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch21s02s02.html
new file mode 100644
index 0000000..b430b92
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch21s02s02.html
@@ -0,0 +1,96 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>21.2.2. Building from a compressed tar archive</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch21s02.html" title="21.2. The rpmbuild Command" /><link rel="prev" href="ch21s02.html" title="21.2. The rpmbuild Command" /><link rel="next" href="ch21s02s03.html" title="21.2.3. Rebuilding RPMs from source RPMs" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch21s02.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch21s02s03.html"><strong>ÃŽnainte
</strong></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id615022" class="title">Building from a compressed tar archive</h1></div></div></div><div class="para">
+ Table A-9 lists the rpmbuild options for working with a compressed tar archive.
+ </div><div class="para">
+ Table A-9 Options for building RPMs from a compressed tar archive
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Option
+ </div>
+
+ </td><td>
+ <div class="para">
+ Usage
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -ta
+ </div>
+
+ </td><td>
+ <div class="para">
+ Build all, both a binary and source RPM
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -tb
+ </div>
+
+ </td><td>
+ <div class="para">
+ Build a binary RPM
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -tc
+ </div>
+
+ </td><td>
+ <div class="para">
+ Build (compile) the program but do not make the full RPM, by executing the build commands through the %build section and stopping
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -tp
+ </div>
+
+ </td><td>
+ <div class="para">
+ Prepare for building a binary RPM, by executing the build commands through the %prep section and stopping
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -ti
+ </div>
+
+ </td><td>
+ <div class="para">
+ Execute the build commands through the %install section and stop
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -tl
+ </div>
+
+ </td><td>
+ <div class="para">
+ Check the listing of files for the RPM
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -ts
+ </div>
+
+ </td><td>
+ <div class="para">
+ Build a source RPM only
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ Each of these options requires the name of a compressed tar archive at the end of the command line. The tar archive must contain a valid spec file inside the archive.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch21s02.html"><strong>Înapoi</strong>21.2. The rpmbuild Command</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch21s02s03.html"><strong>Înainte</strong>21.2.3. Rebuilding RPMs from source RPMs</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch21s02s03.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch21s02s03.html
new file mode 100644
index 0000000..dea5c76
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch21s02s03.html
@@ -0,0 +1,46 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>21.2.3. Rebuilding RPMs from source RPMs</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch21s02.html" title="21.2. The rpmbuild Command" /><link rel="prev" href="ch21s02s02.html" title="21.2.2. Building from a compressed tar archive" /><link rel="next" href="ch21s02s04.html" title="21.2.4. Customizing the build" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch21s02s02.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch21s02s04.html"><
strong>ÃŽnainte</strong></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id729563" class="title">Rebuilding RPMs from source RPMs</h1></div></div></div><div class="para">
+ You can use the rpmbuild command to rebuild an RPM from a source RPM with the options listed in Table A-10.
+ </div><div class="para">
+ Table A-10 Options for rebuilding RPMs from source RPMs
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Option
+ </div>
+
+ </td><td>
+ <div class="para">
+ Usage
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --rebuild
+ </div>
+
+ </td><td>
+ <div class="para">
+ Rebuild binary RPM from source RPM
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --recompile
+ </div>
+
+ </td><td>
+ <div class="para">
+ Recompile binary RPM from source RPM
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ Each of these options requires the name of a source RPM file on the end of the command line.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch21s02s02.html"><strong>Înapoi</strong>21.2.2. Building from a compressed tar archive</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch21s02s04.html"><strong>Înainte</strong>21.2.4. Customizing the build</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch21s02s04.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch21s02s04.html
new file mode 100644
index 0000000..641e8ae
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch21s02s04.html
@@ -0,0 +1,235 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>21.2.4. Customizing the build</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch21s02.html" title="21.2. The rpmbuild Command" /><link rel="prev" href="ch21s02s03.html" title="21.2.3. Rebuilding RPMs from source RPMs" /><link rel="next" href="ch-specfile-syntax.html" title="Cap. 22. Spec File Syntax" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch21s02s03.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch-specfile-syntax.h
tml"><strong>ÃŽnainte</strong></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id754337" class="title">Customizing the build</h1></div></div></div><div class="para">
+ You can customize the rpmbuild command with the options listed in Table A-11.
+ </div><div class="para">
+ Table A-11 Extra build options for the rpmbuild command
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Option
+ </div>
+
+ </td><td>
+ <div class="para">
+ Usage
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -?, --help
+ </div>
+
+ </td><td>
+ <div class="para">
+ Print the popt help information for all the command-line options
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --buildroot directory
+ </div>
+
+ </td><td>
+ <div class="para">
+ Override the default root directory for building with directory.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --clean
+ </div>
+
+ </td><td>
+ <div class="para">
+ Remove the build tree after building
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -D, --define 'macro value'
+ </div>
+
+ </td><td>
+ <div class="para">
+ Define the given macro to hold the given value
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --dbpath path_to_rpm_db
+ </div>
+
+ </td><td>
+ <div class="para">
+ Use the given directory for the RPM database instead of the default
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -E, --eval expression
+ </div>
+
+ </td><td>
+ <div class="para">
+ Print the evaluation of the given expression
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --macros file:file:file
+ </div>
+
+ </td><td>
+ <div class="para">
+ Read the given colon-separated files as the macro files to define RPM macros; only the first file must exist
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --nobuild
+ </div>
+
+ </td><td>
+ <div class="para">
+ Don't really build anything, which really tests the spec file
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --pipe command
+ </div>
+
+ </td><td>
+ <div class="para">
+ Pipe the output of the rpm command to the given command
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --quiet
+ </div>
+
+ </td><td>
+ <div class="para">
+ Provide less output, normally show only errors
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --rcfile file:file:file
+ </div>
+
+ </td><td>
+ <div class="para">
+ Read the given colon-separated files as the rc files to define RPM settings; only the first file must exist
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --rmsource
+ </div>
+
+ </td><td>
+ <div class="para">
+ Remove the sources after the build
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --rmspec
+ </div>
+
+ </td><td>
+ <div class="para">
+ Remove the spec file after the build
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --root directory
+ </div>
+
+ </td><td>
+ <div class="para">
+ Use directory as the top-level directory instead of /
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --short-circuit
+ </div>
+
+ </td><td>
+ <div class="para">
+ With the -bc or -bi options, jumps directly to the given stage and just executes that stage
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --showrc
+ </div>
+
+ </td><td>
+ <div class="para">
+ Print the rpmrc and macro configuration and exit
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --sign
+ </div>
+
+ </td><td>
+ <div class="para">
+ Sign the package with a GPG signature
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --target platform
+ </div>
+
+ </td><td>
+ <div class="para">
+ Build for the given platform. May not work if you don't have the other platform build commands, such as cross compilers, set up. Can work for Intel platforms with i386, i686, and so on.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -v, --verbose
+ </div>
+
+ </td><td>
+ <div class="para">
+ Provide more verbose output
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ -vv
+ </div>
+
+ </td><td>
+ <div class="para">
+ Provide even more verbose output, including debugging information
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ --version
+ </div>
+
+ </td><td>
+ <div class="para">
+ Print the RPM version and exit
+ </div>
+
+ </td></tr></tbody></table></div><div class="para">
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch21s02s03.html"><strong>Înapoi</strong>21.2.3. Rebuilding RPMs from source RPMs</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch-specfile-syntax.html"><strong>Înainte</strong>Cap. 22. Spec File Syntax</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch22s02.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch22s02.html
new file mode 100644
index 0000000..68caaf6
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch22s02.html
@@ -0,0 +1,166 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>22.2. Macros</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-specfile-syntax.html" title="Cap. 22. Spec File Syntax" /><link rel="prev" href="ch-specfile-syntax.html" title="Cap. 22. Spec File Syntax" /><link rel="next" href="ch22s02s02.html" title="22.2.2. Conditional macros" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-specfile-syntax.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch22s02s02.html"
><strong>ÃŽnainte</strong></a></li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id653594" class="title">Macros</h1></div></div></div><div class="para">
+ You can define macros in your spec files to help control how the package gets built. The following section describes these macros.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id653606" class="title">Variable definition macros</h1></div></div></div><div class="para">
+ The %define macro allows you to define new macros from within your spec file. A common usage is to define top-level directories with %define macros at the top of a spec file and then reference these directories throughout the file. For example:
+ </div><div class="para">
+ %define_bindir/bin
+ </div><div class="para">
+ This allows you to change the setting in one place, which is very handy for directory paths used throughout your spec files.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ See the section on Defining Macros in Spec Files in <a class="xref" href="ch-specfile-syntax.html">Cap. 22, <em>Spec File Syntax</em></a> for more on this subject.
+ </div><div class="para">
+ You can use this syntax for other things that may commonly change, such as version numbers. For example:
+ </div><div class="para">
+ %define major 2
+ </div><div class="para">
+ %define minor 2
+ </div><div class="para">
+ %define patchlevel 7
+ </div><div class="para">
+ Version: %{major}.%{minor}.%{patchlevel}
+ </div><div class="para">
+ Table B-1 lists more special macros used within spec files.
+ </div><div class="para">
+ Table B-1 Special spec file macros
+ </div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><tbody><tr><td>
+ <div class="para">
+ Macro
+ </div>
+
+ </td><td>
+ <div class="para">
+ Usage
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ %dump
+ </div>
+
+ </td><td>
+ <div class="para">
+ Prints out macro values
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ %{echo:message}
+ </div>
+
+ </td><td>
+ <div class="para">
+ Prints message to stderr
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ %{error:message}
+ </div>
+
+ </td><td>
+ <div class="para">
+ Prints message to stderr and returns BADSPEC
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ %{expand:expression}
+ </div>
+
+ </td><td>
+ <div class="para">
+ Like eval, expands expression
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ %{F:file_exp}
+ </div>
+
+ </td><td>
+ <div class="para">
+ Expands file_exp to a file name
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ %global name value
+ </div>
+
+ </td><td>
+ <div class="para">
+ Defines a global macro
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ %{P:patch_exp}
+ </div>
+
+ </td><td>
+ <div class="para">
+ Expands patch_exp to a patch file name
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ %{S:source_exp}
+ </div>
+
+ </td><td>
+ <div class="para">
+ Expands source_exp to a source file name
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ %trace
+ </div>
+
+ </td><td>
+ <div class="para">
+ Toggles the printing of debugging information
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ %{uncompress:filename}
+ </div>
+
+ </td><td>
+ <div class="para">
+ Tests if file filename is compressed. If so, uncompresses and includes in the given context. If not compressed, calls cat to include file in given context.
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ %undefine macro
+ </div>
+
+ </td><td>
+ <div class="para">
+ Undefines the given macro
+ </div>
+
+ </td></tr><tr><td>
+ <div class="para">
+ %{warn:message}
+ </div>
+
+ </td><td>
+ <div class="para">
+ Prints message to stderr
+ </div>
+
+ </td></tr></tbody></table></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-specfile-syntax.html"><strong>Înapoi</strong>Cap. 22. Spec File Syntax</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch22s02s02.html"><strong>Înainte</strong>22.2.2. Conditional macros</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch22s02s02.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch22s02s02.html
new file mode 100644
index 0000000..b6179e5
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch22s02s02.html
@@ -0,0 +1,66 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>22.2.2. Conditional macros</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch22s02.html" title="22.2. Macros" /><link rel="prev" href="ch22s02.html" title="22.2. Macros" /><link rel="next" href="ch22s02s03.html" title="22.2.3. Built-in macros" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch22s02.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch22s02s03.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect2"><di
v class="titlepage"><div><div keep-together.within-column="always"><h1 id="id675993" class="title">Conditional macros</h1></div></div></div><div class="para">
+ You can use a special syntax to test for the existence of macros. For example:
+ </div><div class="para">
+ %{?macro_to_test: expression}
+ </div><div class="para">
+ This syntax tells RPM to expand the expression if macro_to_test exists, otherwise ignore. A leading exclamation point, !, tests for the non-existence of a macro:
+ </div><div class="para">
+ %{!?macro_to_test: expression}
+ </div><div class="para">
+ In this example, if the macro_to_test macro does not exist, then expand the expression.
+ </div><div class="para">
+ The %if macro performs an if test much like scripting languages. For example:
+ </div><div class="para">
+ %if %{old_5x}
+ </div><div class="para">
+ %define b5x 1
+ </div><div class="para">
+ %undefine b6x
+ </div><div class="para">
+ %endif
+ </div><div class="para">
+ A %else allows you to specify what to do if the test is not successful. For example:
+ </div><div class="para">
+ %if %{old_5x}
+ </div><div class="para">
+ %define b5x 1
+ </div><div class="para">
+ %undefine b6x
+ </div><div class="para">
+ %else
+ </div><div class="para">
+ %define b6x 1
+ </div><div class="para">
+ %undefine b5x
+ </div><div class="para">
+ %endif
+ </div><div class="para">
+ Again, use an exclamation point to negate the test. For example:
+ </div><div class="para">
+ %if ! %{old_5x}
+ </div><div class="para">
+ %define b5x 1
+ </div><div class="para">
+ %undefine b6x
+ </div><div class="para">
+ %endif
+ </div><div class="para">
+ You can use a && for an and test. For example:
+ </div><div class="para">
+ %if %{old_5x} && %{old_6x}
+ </div><div class="para">
+ %{error: You cannot build for .5x and .6x at the same time}
+ </div><div class="para">
+ %quit
+ </div><div class="para">
+ %endif
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch22s02.html"><strong>Înapoi</strong>22.2. Macros</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch22s02s03.html"><strong>Înainte</strong>22.2.3. Built-in macros</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch22s02s03.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch22s02s03.html
new file mode 100644
index 0000000..72b1ea9
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch22s02s03.html
@@ -0,0 +1,40 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>22.2.3. Built-in macros</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch22s02.html" title="22.2. Macros" /><link rel="prev" href="ch22s02s02.html" title="22.2.2. Conditional macros" /><link rel="next" href="ch22s03.html" title="22.3. Build Sections" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch22s02s02.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch22s03.html"><strong>ÃŽnainte</strong></a></li></ul><div class=
"sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id721464" class="title">Built-in macros</h1></div></div></div><div class="para">
+ The following macros are built into RPM and can help allow you to place your files in the right locations:
+ </div><div class="para">
+ %_prefix /usr
+ </div><div class="para">
+ %_exec_prefix %{_prefix}
+ </div><div class="para">
+ %_bindir %{_exec_prefix}/bin
+ </div><div class="para">
+ %_sbindir %{_exec_prefix}/sbin
+ </div><div class="para">
+ %_libexecdir %{_exec_prefix}/libexec
+ </div><div class="para">
+ %_datadir %{_prefix}/share
+ </div><div class="para">
+ %_sysconfdir %{_prefix}/etc
+ </div><div class="para">
+ %_sharedstatedir %{_prefix}/com
+ </div><div class="para">
+ %_localstatedir %{_prefix}/var
+ </div><div class="para">
+ %_libdir %{_exec_prefix}/lib
+ </div><div class="para">
+ %_includedir %{_prefix}/include
+ </div><div class="para">
+ %_oldincludedir /usr/include
+ </div><div class="para">
+ %_infodir %{_prefix}/info
+ </div><div class="para">
+ %_mandir %{_prefix}/man
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch22s02s02.html"><strong>Înapoi</strong>22.2.2. Conditional macros</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch22s03.html"><strong>Înainte</strong>22.3. Build Sections</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch22s03.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch22s03.html
new file mode 100644
index 0000000..6005efa
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch22s03.html
@@ -0,0 +1,18 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>22.3. Build Sections</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-specfile-syntax.html" title="Cap. 22. Spec File Syntax" /><link rel="prev" href="ch22s02s03.html" title="22.2.3. Built-in macros" /><link rel="next" href="ch22s03s02.html" title="22.3.2. Build" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch22s02s03.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch22s03s02.html"><strong>ÃŽnainte</strong></a><
/li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id641171" class="title">Build Sections</h1></div></div></div><div class="para">
+ After providing information about the package, you need to define the build stages, as described in <a class="xref" href="ch-specfiles.html">Cap. 9, <em>Working with Spec Files</em></a> and <a class="xref" href="ch-rpmbuild.html">Cap. 11, <em>Controlling the Build with <code class="command">rpmbuild</code></em></a>.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id641190" class="title">Build preparation</h1></div></div></div><div class="para">
+ The build preparation section sets the stage for the build. Usually this section has a %setup command. For example:
+ </div><div class="para">
+ %prep
+ </div><div class="para">
+ %setup -q
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch22s02s03.html"><strong>Înapoi</strong>22.2.3. Built-in macros</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch22s03s02.html"><strong>Înainte</strong>22.3.2. Build</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch22s03s02.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch22s03s02.html
new file mode 100644
index 0000000..fc85394
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch22s03s02.html
@@ -0,0 +1,18 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>22.3.2. Build</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch22s03.html" title="22.3. Build Sections" /><link rel="prev" href="ch22s03.html" title="22.3. Build Sections" /><link rel="next" href="ch22s03s03.html" title="22.3.3. Installation" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch22s03.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch22s03s03.html"><strong>ÃŽnainte</strong></a></li></ul><div clas
s="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id641211" class="title">Build</h1></div></div></div><div class="para">
+ The build section describes how to build the library or application. In most cases, the majority of the instructions are in the Makefile created by the prep section, leaving a build section something like the following:
+ </div><div class="para">
+ %build
+ </div><div class="para">
+ %configure
+ </div><div class="para">
+ make
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch22s03.html"><strong>Înapoi</strong>22.3. Build Sections</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch22s03s03.html"><strong>Înainte</strong>22.3.3. Installation</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch22s03s03.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch22s03s03.html
new file mode 100644
index 0000000..a9dab0c
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch22s03s03.html
@@ -0,0 +1,18 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>22.3.3. Installation</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch22s03.html" title="22.3. Build Sections" /><link rel="prev" href="ch22s03s02.html" title="22.3.2. Build" /><link rel="next" href="ch22s03s04.html" title="22.3.4. Clean up" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch22s03s02.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch22s03s04.html"><strong>ÃŽnainte</strong></a></li></ul><div class="se
ct2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id641237" class="title">Installation</h1></div></div></div><div class="para">
+ After building, the installation section holds the commands to install the library or application. For example:
+ </div><div class="para">
+ %install
+ </div><div class="para">
+ rm -rf %{buildroot}
+ </div><div class="para">
+ %makeinstall
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch22s03s02.html"><strong>Înapoi</strong>22.3.2. Build</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch22s03s04.html"><strong>Înainte</strong>22.3.4. Clean up</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch22s03s04.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch22s03s04.html
new file mode 100644
index 0000000..77aea0c
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch22s03s04.html
@@ -0,0 +1,16 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>22.3.4. Clean up</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch22s03.html" title="22.3. Build Sections" /><link rel="prev" href="ch22s03s03.html" title="22.3.3. Installation" /><link rel="next" href="ch22s03s05.html" title="22.3.5. Install and uninstall scripts" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch22s03s03.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch22s03s05.html"><strong>ÃŽnainte</strong>
</a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id641261" class="title">Clean up</h1></div></div></div><div class="para">
+ The clean up section usually calls the make clean command to clean up the built files. For example:
+ </div><div class="para">
+ %clean
+ </div><div class="para">
+ rm -rf %{buildroot}
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch22s03s03.html"><strong>Înapoi</strong>22.3.3. Installation</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch22s03s05.html"><strong>Înainte</strong>22.3.5. Install and uninstall scripts</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch22s03s05.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch22s03s05.html
new file mode 100644
index 0000000..d5d893e
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch22s03s05.html
@@ -0,0 +1,40 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>22.3.5. Install and uninstall scripts</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch22s03.html" title="22.3. Build Sections" /><link rel="prev" href="ch22s03s04.html" title="22.3.4. Clean up" /><link rel="next" href="ch22s04.html" title="22.4. File Tags" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch22s03s04.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch22s04.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect2"
><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id673962" class="title">Install and uninstall scripts</h1></div></div></div><div class="para">
+ RPM packages can run scripts prior to installation with %pre, and after installation with %post. You can also run scripts prior to an uninstall with %preun and after an uninstall with %postun. For example:
+ </div><div class="para">
+ %post
+ </div><div class="para">
+ /sbin/chkconfig --add ypbind
+ </div><div class="para">
+ </div><div class="para">
+ %preun
+ </div><div class="para">
+ if [ "$1" = 0 ] ; then
+ </div><div class="para">
+ /sbin/service ypbind stop > /dev/null 2>&1
+ </div><div class="para">
+ /sbin/chkconfig --del ypbind
+ </div><div class="para">
+ fi
+ </div><div class="para">
+ exit 0
+ </div><div class="para">
+ </div><div class="para">
+ %postun
+ </div><div class="para">
+ if [ "$1" -ge 1 ]; then
+ </div><div class="para">
+ /sbin/service ypbind condrestart > /dev/null 2>&1
+ </div><div class="para">
+ fi
+ </div><div class="para">
+ exit 0
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch22s03s04.html"><strong>Înapoi</strong>22.3.4. Clean up</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch22s04.html"><strong>Înainte</strong>22.4. File Tags</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch22s04.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch22s04.html
new file mode 100644
index 0000000..118bbaa
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch22s04.html
@@ -0,0 +1,50 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>22.4. File Tags</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-specfile-syntax.html" title="Cap. 22. Spec File Syntax" /><link rel="prev" href="ch22s03s05.html" title="22.3.5. Install and uninstall scripts" /><link rel="next" href="ch22s05.html" title="22.5. The Change Log" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch22s03s05.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch22s05.html"><strong>ÃŽnaint
e</strong></a></li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id674035" class="title">File Tags</h1></div></div></div><div class="para">
+ The %files tag lists the files your package should install. For example:
+ </div><div class="para">
+ %files
+ </div><div class="para">
+ %defattr(-,root,root)
+ </div><div class="para">
+ /usr/X11R6/bin/xtoolwait
+ </div><div class="para">
+ /usr/X11R6/man/man1/xtoolwait.*
+ </div><div class="para">
+ You should mark configuration and documentation files with %config and %doc, respectively. For example:
+ </div><div class="para">
+ %files
+ </div><div class="para">
+ %defattr(-,root,root)
+ </div><div class="para">
+ /sbin/ypbind
+ </div><div class="para">
+ %{_mandir}/*/*
+ </div><div class="para">
+ %config /etc/rc.d/init.d/*
+ </div><div class="para">
+ %config /etc/yp.conf
+ </div><div class="para">
+ %dir /var/yp
+ </div><div class="para">
+ %dir /var/yp/binding
+ </div><div class="para">
+ %doc README NEWS
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id786867" class="title">Making relocatable packages</h1></div></div></div><div class="para">
+ You can make a relocatable package by setting up one or more Prefix tags. For example:
+ </div><div class="para">
+ Prefix: /usr
+ </div><div class="para">
+ Prefix: /etc
+ </div><div class="para">
+ Each file in the %files section must then start with one of the prefixes you provided. With this, installers can easily relocate the package with a command like the following:
+ </div><div class="para">
+ # rpm --relocate /etc=/usr/etc file_name.rpm
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch22s03s05.html"><strong>Înapoi</strong>22.3.5. Install and uninstall scripts</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch22s05.html"><strong>Înainte</strong>22.5. The Change Log</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch22s05.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch22s05.html
new file mode 100644
index 0000000..bbbe5b8
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch22s05.html
@@ -0,0 +1,23 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>22.5. The Change Log</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-specfile-syntax.html" title="Cap. 22. Spec File Syntax" /><link rel="prev" href="ch22s04.html" title="22.4. File Tags" /><link rel="next" href="ch-rpm-evolution.html" title="Cap. 23. RPM Feature Evolution" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch22s04.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch-rpm-evolution.html"><strong>ÃŽnaint
e</strong></a></li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id786897" class="title">The Change Log</h1></div></div></div><div class="para">
+ The change log usually appears at the end of a spec file. It holds messages for each significant change. For example:
+ </div><div class="para">
+ %changelog
+ </div><div class="para">
+ * Fri Jun 21 2002 Bob Marley <marley at redhat.com>
+ </div><div class="para">
+ - automated rebuild
+ </div><div class="para">
+ </div><div class="para">
+ * Tue May 08 2001 Peter Tosh <tosh at redhat.com> 1.3-1
+ </div><div class="para">
+ - updated to 1.3
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch22s04.html"><strong>Înapoi</strong>22.4. File Tags</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch-rpm-evolution.html"><strong>Înainte</strong>Cap. 23. RPM Feature Evolution</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch25s02.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch25s02.html
new file mode 100644
index 0000000..f96acbe
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch25s02.html
@@ -0,0 +1,16 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>25.2. Accessing RPM Mailing Lists and Newsgroups</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-online-resources.html" title="Cap. 25. RPM Resources" /><link rel="prev" href="ch-online-resources.html" title="Cap. 25. RPM Resources" /><link rel="next" href="ch-development-tools.html" title="Cap. 26. Linux Text Editors and Development Tools" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-online-resources.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a access
key="n" href="ch-development-tools.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id626131" class="title">Accessing RPM Mailing Lists and Newsgroups</h1></div></div></div><div class="para">
+ The RPM mailing list provides the best source of technical RPM information. You can post questions and get quick, useful responses. If you are working with RPM, you should subscribe to this mailing list. For details on viewing the RPM mailing list archives and signing up for the list, see www.rpm.org/mailing_list/.
+ </div><div class="para">
+ To help avoid unwanted commercial e-mail (in other words, spam), you need to register with a user name and password to subscribe to the mailing list or view the archives.
+ </div><div class="para">
+ A Usenet newsgroup, named linux.redhat.rpm, also provides a forum for asking RPM-related questions. You can read this newsgroup with any newsreading program.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-online-resources.html"><strong>Înapoi</strong>Cap. 25. RPM Resources</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch-development-tools.html"><strong>Înainte</strong>Cap. 26. Linux Text Editors and Development Tools</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch26s02.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch26s02.html
new file mode 100644
index 0000000..993e0b3
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch26s02.html
@@ -0,0 +1,18 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>26.2. Programming Text Editors</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-development-tools.html" title="Cap. 26. Linux Text Editors and Development Tools" /><link rel="prev" href="ch-development-tools.html" title="Cap. 26. Linux Text Editors and Development Tools" /><link rel="next" href="ch26s03.html" title="26.3. Integrated Development Environments for C Programming" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-development-tools.html"><stro
ng>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch26s03.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id562822" class="title">Programming Text Editors</h1></div></div></div><div class="para">
+ In addition to general-purpose text editors, Linux sports a large number of text editors with special features for programming, such as syntax highlighting. The extended version of vi, called vim, includes a number of add-ons that can help you with C programming tasks. Emacs also includes a wide array of features to help programming. Both of these editors can act as development environments with a bit of configuration. As mentioned previously, both come with most Linux distributions.
+ </div><div class="para">
+ I also like an editor called nedit and another one called jedit. The jedit editor is written in Java, so that it runs the same on Windows and Linux, a big win if you must work on multiple platforms. (Emacs and vim have versions that work on Windows, too, along with Linux.) If you use jedit, you must have a Java runtime environment installed.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ Download nedit from www.nedit.org. Download jedit from www.jedit.org. Download Java runtime environments from Sun at http://java.sun.com/j2se/downloads.html or IBM at www.ibm.com/java/jdk/ and select the IBM Developer Kit for Linux.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-development-tools.html"><strong>Înapoi</strong>Cap. 26. Linux Text Editors and Development Tools</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch26s03.html"><strong>Înainte</strong>26.3. Integrated Development Environments for C P...</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch26s03.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch26s03.html
new file mode 100644
index 0000000..036b72f
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch26s03.html
@@ -0,0 +1,24 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>26.3. Integrated Development Environments for C Programming</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-development-tools.html" title="Cap. 26. Linux Text Editors and Development Tools" /><link rel="prev" href="ch26s02.html" title="26.2. Programming Text Editors" /><link rel="next" href="ch26s04.html" title="26.4. Integrated Development Environments for Python Programming" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch26s02.html"><strong>ÃŽnapoi</strong></a></li><li class="n
ext"><a accesskey="n" href="ch26s04.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id612643" class="title">Integrated Development Environments for C Programming</h1></div></div></div><div class="para">
+ If you want more of a graphical environment, Red Hat Linux ships with KDevelop, an IDE for C and C++ programming.
+ </div><div class="para">
+ Anjuta provides a GTK/GNOME-based IDE, an alternative to the KDE-based KDevelop. KDevelop, however, supports KDE, GNOME, Qt, and text-mode C and C++ applications.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ Download Anjuta from www.anjuta.org.
+ </div><div class="para">
+ The Eclipse IDE, while mostly used for Java development, has a C and C++ mode called CDT, for C/C++ Development Tools. Eclipse is important because Red Hat provides an RPM-building plug-in to Eclipse.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ Download Anjuta from www.anjuta.org. Download Eclipse from www.eclipse.org and the Eclipse CDT from www.eclipse.org/tools/downloads.html.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch26s02.html"><strong>Înapoi</strong>26.2. Programming Text Editors</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch26s04.html"><strong>Înainte</strong>26.4. Integrated Development Environments for Pyt...</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch26s04.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch26s04.html
new file mode 100644
index 0000000..3df24d9
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch26s04.html
@@ -0,0 +1,32 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>26.4. Integrated Development Environments for Python Programming</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-development-tools.html" title="Cap. 26. Linux Text Editors and Development Tools" /><link rel="prev" href="ch26s03.html" title="26.3. Integrated Development Environments for C Programming" /><link rel="next" href="ch-licensing.html" title="Cap. 27. Licensing RPM" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch26s03.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a
accesskey="n" href="ch-licensing.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id659945" class="title">Integrated Development Environments for Python Programming</h1></div></div></div><div class="para">
+ As with C programs, Python scripts are made up of text files holding Python commands, so you need a text editor or some sort of development environment for creating Python programs. Any of the tools listed so far will work fine for developing Python applications. The key requirement is the ability to control tabs and indenting, since this is crucial to Python syntax.
+ </div><div class="para">
+ IDLE, a graphical console and editor, supports creating Python applications. This is considered part of Python. IDLE requires the Python-tools package.
+ </div><div class="para">
+ In addition, you can choose from Python-focused tools such as Bicycle Repair Man, a refactoring tool, or Boa Constructor and Black Adder, two Python IDEs.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ Boa Constructor is available from http://boa-constructor.sourceforge.net. Black Adder is a commercial tool available at www.thekompany.com.
+ </div><div class="para">
+ The Eclipse IDE, mentioned previously, supports a number of Python add-ons. Combined with the C and C++ tools, and plug-ins for building RPMs, Eclipse brings together most everything you need for Python development on Linux.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ Eclipse is available at www.eclipse.org, and Python add-ons at http://sourceforge.net/projects/pyeclipse, http://sourceforge.net/projects/pe4eclipse, or http://www.kalab.com/freeware/pythoneclipse/pythoneclipse.htm.
+ </div><div class="para">
+ This is really just the tip of the iceberg when it comes to Python tools. You can find many more available on the Internet.
+ </div><div class="para">
+ Cross Reference
+ </div><div class="para">
+ A large listing of Python editing tools appears at http://www.python.org/cgi-bin/moinmoin/PythonEditors.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch26s03.html"><strong>Înapoi</strong>26.3. Integrated Development Environments for C P...</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch-licensing.html"><strong>Înainte</strong>Cap. 27. Licensing RPM</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html
new file mode 100644
index 0000000..9e5f687
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html
@@ -0,0 +1,35 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Ghid RPM</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><meta name="description" content="O scurtă trecere în revistă și un sumar al subiectului și scopului cărții, în mod tradițional nu mai lung(ă) de un paragraf. Notă: trecerea în revistă va apărea pe prima pagină a cărții și în câmpul #description al fișierului spec aparținând RPM-ului cărții" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="next" href="ch-intro-packaging.html" title="Introducing Package Management" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"></li><li class="next"><a accesskey="n" href="ch-intro-packaging.html"><strong>ÃŽnainte</strong></a></li></ul><div xml:lang="ro" class="book" id="id489891" lang="ro"><div class="titlepage"><div><div class="producttitle" font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-siz
e="12pt" text-align="center"><span class="productname">Schiță Documentație Fedora</span> <span class="productnumber"></span></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><h1 id="id489891" class="title">Ghid RPM</h1></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><h2 class="subtitle">scurt descriptor</h2></div><p class="edition">Ediție 0</p><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><h3 class="corpauthor">
+ <span class="inlinemediaobject"><object data="Common_Content/images/title_logo.svg" type="image/svg+xml"> Logo</object></span>
+
+ </h3></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><div xml:lang="ro" class="authorgroup" lang="ro"><div class="author"><h3 class="author"><span class="firstname">Eric</span> <span class="surname">Foster-Johnson</span></h3></div><div class="author"><h3 class="author"><span class="firstname">Stuart</span> <span class="surname">Ellis</span></h3><code class="email"><a class="email" href="mailto:stuart at elsn.org">stuart at elsn.org</a></code></div><div class="author"><h3 class="author"><span class="firstname">Ben</span> <span class="surname">Cotton</span></h3><code class="email"><a class="email" href="mailto:bcotton at fedoraproject.org">bcotton at fedoraproject.org</a></code></div></div></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><p class="copyright">Copyright © 2005,2010 Red Hat, Inc. and others</p></div><hr /><div font-family="sans-serif,Symbol,ZapfDin
gbats" font-weight="bold" font-size="12pt" text-align="center"><div id="id883131" class="legalnotice"><h1 class="legalnotice"></h1><div class="para">
+ Copyright <span class="trademark"></span>© 2005,2010 Red Hat, Inc. and others.
+ </div><div class="para">
+ The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at <a href="http://creativecommons.org/licenses/by-sa/3.0/">http://creativecommons.org/licenses/by-sa/3.0/</a>. The original authors of this document, and Red Hat, designate the Fedora Project as the "Attribution Party" for purposes of CC-BY-SA. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version.
+ </div><div class="para">
+ Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
+ </div><div class="para">
+ Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, MetaMatrix, Fedora, the Infinity Logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.
+ </div><div class="para">
+ For guidelines on the permitted uses of the Fedora trademarks, refer to <a href="https://fedoraproject.org/wiki/Legal:Trademark_guidelines">https://fedoraproject.org/wiki/Legal:Trademark_guidelines</a>.
+ </div><div class="para">
+ <span class="trademark">Linux</span>® is the registered trademark of Linus Torvalds in the United States and other countries.
+ </div><div class="para">
+ <span class="trademark">Java</span>® is a registered trademark of Oracle and/or its affiliates.
+ </div><div class="para">
+ <span class="trademark">XFS</span>® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
+ </div><div class="para">
+ <span class="trademark">MySQL</span>® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
+ </div><div class="para">
+ All other trademarks are the property of their respective owners.
+ </div></div></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><div class="abstract"><h6>Rezumat</h6><div class="para">
+ O scurtă trecere în revistă și un sumar al subiectului și scopului cărții, în mod tradițional nu mai lung(ă) de un paragraf. Notă: trecerea în revistă va apărea pe prima pagină a cărții și în câmpul #description al fișierului spec aparținând RPM-ului cărții
+ </div></div></div></div><hr /></div><div class="toc"><dl><dt><span class="preface"><a href="ch-intro-packaging.html">Introducing Package Management</a></span></dt><dd><dl><dt><span class="sect1"><a href="ch-intro-packaging.html#id569409">1. Installing, Removing, and Upgrading Applications</a></span></dt><dt><span class="sect1"><a href="pr01s02.html">2. Overcoming the Installation Obstacles</a></span></dt><dd><dl><dt><span class="sect2"><a href="pr01s02.html#id610110">2.1. Application-level utilities</a></span></dt><dt><span class="sect2"><a href="pr01s02s02.html">2.2. Built-in system utilities</a></span></dt></dl></dd><dt><span class="sect1"><a href="pr01s03.html">3. Linux Software Management Tools: Packages</a></span></dt><dt><span class="sect1"><a href="pr01s04.html">4. Summary</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-intro-rpm.html">1. Introduction to RPM</a></span></dt><dd><dl><dt><span class="sect1"><a href="ch-intro-rpm.html#id897385">1.1. The N
eed for Linux Package Management Systems</a></span></dt><dt><span class="sect1"><a href="ch01s02.html">1.2. RPM Design Goals</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch01s02.html#id620200">1.2.1. Ease of use</a></span></dt><dt><span class="sect2"><a href="ch01s02s02.html">1.2.2. Package-oriented focus</a></span></dt><dt><span class="sect2"><a href="ch01s02s03.html">1.2.3. Package upgradability</a></span></dt><dt><span class="sect2"><a href="ch01s02s04.html">1.2.4. Package interdependencies</a></span></dt><dt><span class="sect2"><a href="ch01s02s05.html">1.2.5. Query capabilities</a></span></dt><dt><span class="sect2"><a href="ch01s02s06.html">1.2.6. Package verification</a></span></dt><dt><span class="sect2"><a href="ch01s02s07.html">1.2.7. Multiple architectures</a></span></dt><dt><span class="sect2"><a href="ch01s02s08.html">1.2.8. Pristine sources</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch01s03.html">1.3. RPM Terminology</a></span></dt><dt
><span class="sect1"><a href="ch01s04.html">1.4. Summary</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-rpm-overview.html">2. RPM Overview</a></span></dt><dd><dl><dt><span class="sect1"><a href="ch-rpm-overview.html#id860916">2.1. Understanding the Package File</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch-rpm-overview.html#id580488">2.1.1. RPM file format</a></span></dt><dt><span class="sect2"><a href="ch-rpm-overview.html#id800106">2.1.2. Binary RPMs and Source RPMs</a></span></dt><dt><span class="sect2"><a href="ch-rpm-overview.html#id847399">2.1.3. Source RPMs</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch02s02.html">2.2. Querying the RPM Database</a></span></dt><dt><span class="sect1"><a href="ch02s03.html">2.3. Running RPM Commands</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch02s03.html#id854435">2.3.1. Working with the <code class="command">rpm</code> command</a></span></dt><dt><span class="sect2"><a href="ch02s0
3s02.html">2.3.2. Other RPM commands</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch02s04.html">2.4. Summary</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-using-rpm.html">3. Using RPM</a></span></dt><dd><dl><dt><span class="sect1"><a href="ch-using-rpm.html#id557035">3.1. The <code class="command">rpm</code> Command</a></span></dt><dt><span class="sect1"><a href="ch03s02.html">3.2. Upgrading and Installing Software</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch03s02.html#id778012">3.2.1. Upgrading with the <code class="command">rpm</code> command</a></span></dt><dt><span class="sect2"><a href="ch03s02s02.html">3.2.2. Upgrading packages</a></span></dt><dt><span class="sect2"><a href="ch03s02s03.html">3.2.3. Freshening up</a></span></dt><dt><span class="sect2"><a href="ch03s02s04.html">3.2.4. Installing Packages</a></span></dt><dt><span class="sect2"><a href="ch03s02s05.html">3.2.5. Installing Over the Internet</a></span></dt><dt><span
class="sect2"><a href="ch03s02s06.html">3.2.6. Installing source RPMs</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch03s03.html">3.3. Removing Software</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch03s03.html#id780124">3.3.1. Checking that the package has been removed</a></span></dt><dt><span class="sect2"><a href="ch03s03s02.html">3.3.2. Removing multiple packages at a time</a></span></dt><dt><span class="sect2"><a href="ch03s03s03.html">3.3.3. Options when removing packages</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch03s04.html">3.4. Other <code class="command">rpm</code> Command Options</a></span></dt><dt><span class="sect1"><a href="ch03s05.html">3.5. Summary</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-using-rpm-db.html">4. Using the RPM Database</a></span></dt><dd><dl><dt><span class="section"><a href="ch-using-rpm-db.html#RPM_Guide-Using_RPM_DB-querying_database">4.1. Querying the RPM Database</a></span></dt>
<dd><dl><dt><span class="section"><a href="ch-using-rpm-db.html#id669857">4.1.1. Querying packages</a></span></dt><dt><span class="section"><a href="ch-using-rpm-db.html#RPM_Guide-Using_RPM_DB-query_everything">4.1.2. Querying everything</a></span></dt><dt><span class="section"><a href="ch-using-rpm-db.html#RPM_Guide-Using_RPM_DB-refining_query">4.1.3. Refining the query</a></span></dt><dt><span class="section"><a href="ch-using-rpm-db.html#RPM_Guide-Using_RPM_DB-which_package">4.1.4. Finding which packages own files</a></span></dt></dl></dd><dt><span class="section"><a href="RPM_Guide-Using_RPM_DB-getting_information.html">4.2. Getting Information on Packages</a></span></dt><dd><dl><dt><span class="section"><a href="RPM_Guide-Using_RPM_DB-getting_information.html#RPM_Guide-USing_RPM_DB-getting_information-describing_packages">4.2.1. Describing packages</a></span></dt><dt><span class="section"><a href="RPM_Guide-Using_RPM_DB-package_groups.html">4.2.2. Package groups</a></sp
an></dt><dt><span class="section"><a href="ch04s02s03.html">4.2.3. Listing the files in a package</a></span></dt><dt><span class="section"><a href="RPM_Guide-Using_RPM_DB-listing_conf_files.html">4.2.4. Listing the configuration files for a package</a></span></dt><dt><span class="section"><a href="ch04s02s05.html">4.2.5. Listing the documentation files for a package</a></span></dt><dt><span class="section"><a href="RPM_Guide-Using_RPM_DB-file_state.html">4.2.6. Listing the state of the files in a package</a></span></dt><dt><span class="section"><a href="RPM_Guide-Using_RPM_DB-listing_scripts.html">4.2.7. Listing the scripts in a package</a></span></dt><dt><span class="section"><a href="RPM_Guide-Using_RPM_DB-Listing_changed.html">4.2.8. Listing what has changed</a></span></dt><dt><span class="section"><a href="RPM_Guide-Using_RPM_DB-Combining_queries.html">4.2.9. Combining queries</a></span></dt><dt><span class="section"><a href="RPM_Guide-Using_RPM_DB-Cusomt_queries.html">4
.2.10. Creating custom queries</a></span></dt><dt><span class="section"><a href="RPM_Guide-Using_RPM_DB-Query_format_tags.html">4.2.11. Working With Query Format Tags</a></span></dt><dt><span class="section"><a href="RPM_Guide-Using_RPM_DB-Querying_for_package_information.html">4.2.12. Querying for Package Information</a></span></dt><dt><span class="section"><a href="RPM_Guide-Using_RPM_DB-Formatting_arrays.html">4.2.13. Formatting Arrays</a></span></dt><dt><span class="section"><a href="RPM_Guide-Using_RPM_DB-Special_formatting.html">4.2.14. Special Formatting</a></span></dt><dt><span class="section"><a href="RPM_Guide-Using_RPM_DB-querying_pacakge_dependencies.html">4.2.15. Querying for Package Dependencies</a></span></dt><dt><span class="section"><a href="RPM-Guide-Using_RPM_DB-Querying_file_information.html">4.2.16. Querying for File Information</a></span></dt><dt><span class="section"><a href="RPM_Guide-Using_RPM_DB-Other_Query_Format_Tags.html">4.2.17. Other Query Form
at Tags</a></span></dt></dl></dd><dt><span class="section"><a href="ch04s03.html">4.3. Other queries</a></span></dt><dt><span class="section"><a href="RPM_Guide-Using_RPM_DB-Getting_information_on_package_files.html">4.4. Getting Information on Package Files</a></span></dt><dd><dl><dt><span class="section"><a href="RPM_Guide-Using_RPM_DB-Getting_information_on_package_files.html#RPM_Guide_Using_RPM_DB-Querying_package_files_remotely">4.4.1. Querying Package Files Remotely</a></span></dt><dt><span class="section"><a href="RPM-Guide-Using_RPM-DB-verifying_packages.html">4.4.2. Verifying Installed RPM Packages</a></span></dt><dt><span class="section"><a href="RPM_GUide-Using_RPM_DB-working_with_RPM_db.html">4.4.3. Working With the RPM Database</a></span></dt><dt><span class="section"><a href="RPM_Guide-Using_RPM_DB-summary.html">4.4.4. Summary</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-dependencies.html">5. Package Dependencies</a></span></dt><dd><
dl><dt><span class="sect1"><a href="ch-dependencies.html#id652095">5.1. Understanding the Dependency Concept</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch-dependencies.html#id662448">5.1.1. Capabilities</a></span></dt><dt><span class="sect2"><a href="ch-dependencies.html#id702044">5.1.2. Version dependencies</a></span></dt><dt><span class="sect2"><a href="ch-dependencies.html#id702074">5.1.3. Conflicts</a></span></dt><dt><span class="sect2"><a href="ch-dependencies.html#id735748">5.1.4. Obsoletes</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch05s02.html">5.2. Checking for Dependencies</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch05s02.html#id675733">5.2.1. Determining the capabilities a package requires</a></span></dt><dt><span class="sect2"><a href="ch05s02s02.html">5.2.2. Determining the capabilities a package provides</a></span></dt><dt><span class="sect2"><a href="ch05s02s03.html">5.2.3. Checking for conflicts</a></span></dt><dt><sp
an class="sect2"><a href="ch05s02s04.html">5.2.4. Determining which packages require a certain capability</a></span></dt><dt><span class="sect2"><a href="ch05s02s05.html">5.2.5. Determining which package provides a certain capability</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch05s03.html">5.3. Triggers</a></span></dt><dt><span class="sect1"><a href="ch05s04.html">5.4. Summary</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-transactions.html">6. Transactions</a></span></dt><dd><dl><dt><span class="sect1"><a href="ch-transactions.html#id810029">6.1. Understanding Transactions</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch-transactions.html#id726466">6.1.1. When do you need transactions?</a></span></dt><dt><span class="sect2"><a href="ch-transactions.html#id794653">6.1.2. Backing out of transactions</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch06s02.html">6.2. Transactions with the rpm Command</a></span></dt><dd><dl><dt>
<span class="sect2"><a href="ch06s02.html#id817275">6.2.1. Transaction IDs</a></span></dt><dt><span class="sect2"><a href="ch06s02s02.html">6.2.2. Rolling Back Transactions</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch06s03.html">6.3. Saving Old Packages</a></span></dt><dt><span class="sect1"><a href="ch06s04.html">6.4. Summary</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-management-software.html">7. RPM Management Software</a></span></dt><dd><dl><dt><span class="sect1"><a href="ch-management-software.html#id650152">7.1. Locating RPMs</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch-management-software.html#id801673">7.1.1. rpmfind and rpm2html</a></span></dt><dt><span class="sect2"><a href="ch-management-software.html#id703003">7.1.2. RPM Sites On the Internet</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch07s02.html">7.2. Graphical RPM Management</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch07s02.html#id7
59907">7.2.1. Nautilus</a></span></dt><dt><span class="sect2"><a href="ch07s02s02.html">7.2.2. Red Hat Package Management</a></span></dt><dt><span class="sect2"><a href="ch07s02s03.html">7.2.3. KPackage</a></span></dt><dt><span class="sect2"><a href="ch07s02s04.html">7.2.4. Gnome-RPM</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch07s03.html">7.3. Extending RPM Management</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch07s03.html#id567232">7.3.1. AutoRPM</a></span></dt><dt><span class="sect2"><a href="ch07s03s02.html">7.3.2. AutoUpdate</a></span></dt><dt><span class="sect2"><a href="ch07s03s03.html">7.3.3. The Red Hat Network and up2date</a></span></dt><dt><span class="sect2"><a href="ch07s03s04.html">7.3.4. Current</a></span></dt><dt><span class="sect2"><a href="ch07s03s05.html">7.3.5. urpmi and RpmDrake</a></span></dt><dt><span class="sect2"><a href="ch07s03s06.html">7.3.6. apt-rpm</a></span></dt><dt><span class="sect2"><a href="ch07s03s07.html">7.3.7
. The poldek</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch07s04.html">7.4. Summary</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-creating-rpms.html">8. Creating RPMs: An Overview</a></span></dt><dd><dl><dt><span class="sect1"><a href="ch-creating-rpms.html#id851471">8.1. Preparing to Build RPMs</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch-creating-rpms.html#id765745">8.1.1. Planning what you want to build</a></span></dt><dt><span class="sect2"><a href="ch-creating-rpms.html#id553544">8.1.2. Gathering the software to package</a></span></dt><dt><span class="sect2"><a href="ch-creating-rpms.html#id582471">8.1.3. Creating a reproducible build of the software</a></span></dt><dt><span class="sect2"><a href="ch-creating-rpms.html#id571720">8.1.4. Planning for Upgrades</a></span></dt><dt><span class="sect2"><a href="ch-creating-rpms.html#id870930">8.1.5. Outlining Any Dependencies</a></span></dt></dl></dd><dt><span class="sect1"><a href=
"ch08s02.html">8.2. Building RPMs</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch08s02.html#id823716">8.2.1. Setting up the directory structure</a></span></dt><dt><span class="sect2"><a href="ch08s02s02.html">8.2.2. Placing your sources into the directory structure</a></span></dt><dt><span class="sect2"><a href="ch08s02s03.html">8.2.3. Creating the spec file</a></span></dt><dt><span class="sect2"><a href="ch08s02s04.html">8.2.4. Building RPMs with the rpmbuild command</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch08s03.html">8.3. Verifying Your RPMS</a></span></dt><dt><span class="sect1"><a href="ch08s04.html">8.4. Summary</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-specfiles.html">9. Working with Spec Files</a></span></dt><dd><dl><dt><span class="sect1"><a href="ch-specfiles.html#id638671">9.1. Reading Spec Files</a></span></dt><dt><span class="sect1"><a href="ch09s02.html">9.2. Writing Spec Files</a></span></dt><dd><dl><dt><span
class="sect2"><a href="ch09s02.html#id686530">9.2.1. Comments</a></span></dt><dt><span class="sect2"><a href="ch09s02s02.html">9.2.2. Storing spec files on disk</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch09s03.html">9.3. Defining Package Information</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch09s03.html#id562505">9.3.1. Describing the package</a></span></dt><dt><span class="sect2"><a href="ch09s03s02.html">9.3.2. Setting build locations</a></span></dt><dt><span class="sect2"><a href="ch09s03s03.html">9.3.3. Naming source files</a></span></dt><dt><span class="sect2"><a href="ch09s03s04.html">9.3.4. Naming patches</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch09s04.html">9.4. Controlling the Build</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch09s04.html#id519246">9.4.1. Preparing for the build</a></span></dt><dt><span class="sect2"><a href="ch09s04s02.html">9.4.2. Building the software</a></span></dt><dt><span class="sec
t2"><a href="ch09s04s03.html">9.4.3. Installing the software</a></span></dt><dt><span class="sect2"><a href="ch09s04s04.html">9.4.4. Cleaning up after the build</a></span></dt><dt><span class="sect2"><a href="ch09s04s05.html">9.4.5. Defining installation scripts</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch09s05.html">9.5. Filling the List of Files</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch09s05.html#id868856">9.5.1. Using wildcards</a></span></dt><dt><span class="sect2"><a href="ch09s05s02.html">9.5.2. Naming directories of files</a></span></dt><dt><span class="sect2"><a href="ch09s05s03.html">9.5.3. Marking files as documentation or configuration files</a></span></dt><dt><span class="sect2"><a href="ch09s05s04.html">9.5.4. Setting file attributes</a></span></dt><dt><span class="sect2"><a href="ch09s05s05.html">9.5.5. Verifying the %files section</a></span></dt><dt><span class="sect2"><a href="ch09s05s06.html">9.5.6. Filling the list of files
automatically</a></span></dt><dt><span class="sect2"><a href="ch09s05s07.html">9.5.7. Handling RPM build errors for unpackaged files</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch09s06.html">9.6. Adding Change Log Entries</a></span></dt><dt><span class="sect1"><a href="ch09s07.html">9.7. Defining Spec File Macros</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch09s07.html#id724189">9.7.1. Built-in macros</a></span></dt><dt><span class="sect2"><a href="ch09s07s02.html">9.7.2. Spec file-specific macros</a></span></dt><dt><span class="sect2"><a href="ch09s07s03.html">9.7.3. Defining new macros</a></span></dt><dt><span class="sect2"><a href="ch09s07s04.html">9.7.4. Specifying parameters to macros</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch09s08.html">9.8. Creating XML Spec Files</a></span></dt><dt><span class="sect1"><a href="ch09s09.html">9.9. Summary</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-advanced-packaging.html">
10. Creare avansată pachete RPM</a></span></dt><dd><dl><dt><span class="sect1"><a href="ch-advanced-packaging.html#id662011">10.1. Definirea dependențelor pachetelor</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch-advanced-packaging.html#id507149">10.1.1. Numirea dependențelor</a></span></dt><dt><span class="sect2"><a href="ch-advanced-packaging.html#id666574">10.1.2. Setarea premiselor</a></span></dt><dt><span class="sect2"><a href="ch-advanced-packaging.html#id666618">10.1.3. Numirea dependențelor de construcție</a></span></dt><dt><span class="sect2"><a href="ch-advanced-packaging.html#id666660">10.1.4. Generarea automată de dependențe</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch10s02.html">10.2. Setarea triggerelor</a></span></dt><dt><span class="sect1"><a href="ch10s03.html">10.3. Scrierea scripturilor de verificare</a></span></dt><dt><span class="sect1"><a href="ch10s04.html">10.4. Crearea subpachetelor.</a></span></dt><dd><dl><dt><span
class="sect2"><a href="ch10s04.html#id776325">10.4.1. Furnizarea informațiilor pentru subpachete</a></span></dt><dt><span class="sect2"><a href="ch10s04s02.html">10.4.2. Definirea scripturilor pentru subpachete</a></span></dt><dt><span class="sect2"><a href="ch10s04s03.html">10.4.3. Construirea subpachetelor</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch10s05.html">10.5. Creating Relocatable Packages</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch10s05.html#id785850">10.5.1. Setting up the prefixes</a></span></dt><dt><span class="sect2"><a href="ch10s05s02.html">10.5.2. Define the files section</a></span></dt><dt><span class="sect2"><a href="ch10s05s03.html">10.5.3. Problems creating relocatable packages</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch10s06.html">10.6. Defining Conditional Builds</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch10s06.html#id763642">10.6.1. Defining conditional macros</a></span></dt><dt><span cl
ass="sect2"><a href="ch10s06s02.html">10.6.2. Using conditional blocks</a></span></dt><dt><span class="sect2"><a href="ch10s06s03.html">10.6.3. Using architecture-based conditionals</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch10s07.html">10.7. Summary</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-rpmbuild.html">11. Controlling the Build with <code class="command">rpmbuild</code></a></span></dt><dd><dl><dt><span class="sect1"><a href="ch-rpmbuild.html#id441726">11.1. Building RPMs with the rpmbuild Command</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch-rpmbuild.html#id554393">11.1.1. Customizing the build</a></span></dt><dt><span class="sect2"><a href="ch-rpmbuild.html#id658328">11.1.2. Testing the build</a></span></dt><dt><span class="sect2"><a href="ch-rpmbuild.html#id658349">11.1.3. Debugging the build</a></span></dt><dt><span class="sect2"><a href="ch-rpmbuild.html#id620879">11.1.4. Cleaning up</a></span></dt><dt><span class="s
ect2"><a href="ch-rpmbuild.html#id617777">11.1.5. Building for other platforms</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch11s02.html">11.2. Building RPMs Without an External Spec File</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch11s02.html#id558731">11.2.1. Options for working with tar archives</a></span></dt><dt><span class="sect2"><a href="ch11s02s02.html">11.2.2. The expected archive structure</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch11s03.html">11.3. Working with Source RPMs</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch11s03.html#id670165">11.3.1. Rebuilding binary RPMS from source RPMs</a></span></dt><dt><span class="sect2"><a href="ch11s03s02.html">11.3.2. Recompiling binaries from source RPMs</a></span></dt><dt><span class="sect2"><a href="ch11s03s03.html">11.3.3. SRPMS? Finding source RPMs</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch11s04.html">11.4. Signing Built RPMs</a></span></dt><dd><d
l><dt><span class="sect2"><a href="ch11s04.html#id580590">11.4.1. Checking that the GPG software is installed</a></span></dt><dt><span class="sect2"><a href="ch11s04s02.html">11.4.2. Configuring a signature</a></span></dt><dt><span class="sect2"><a href="ch11s04s03.html">11.4.3. Signing with the rpmbuild command</a></span></dt><dt><span class="sect2"><a href="ch11s04s04.html">11.4.4. Signing with the rpm command</a></span></dt><dt><span class="sect2"><a href="ch11s04s05.html">11.4.5. Verifying signatures</a></span></dt><dt><span class="sect2"><a href="ch11s04s06.html">11.4.6. Importing public keys</a></span></dt><dt><span class="sect2"><a href="ch11s04s07.html">11.4.7. Getting the Red Hat public key</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch11s05.html">11.5. Summary</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-extra-packaging-tools.html">12. Supplemental Packaging Software</a></span></dt><dd><dl><dt><span class="sect1"><a href="ch-extra-pa
ckaging-tools.html#id804948">12.1. Packaging Aids</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch-extra-packaging-tools.html#id643503">12.1.1. Using VIM spec plugins to improve spec file editing</a></span></dt><dt><span class="sect2"><a href="ch-extra-packaging-tools.html#id622758">12.1.2. Adding functions with emacs rpm-spec-mode</a></span></dt><dt><span class="sect2"><a href="ch-extra-packaging-tools.html#id559610">12.1.3. Validating and debugging spec files with rpmlint</a></span></dt><dt><span class="sect2"><a href="ch-extra-packaging-tools.html#id820477">12.1.4. Generating the %files section with RUST</a></span></dt><dt><span class="sect2"><a href="ch-extra-packaging-tools.html#id568330">12.1.5. setup.sh and MakeRPM.pl</a></span></dt><dt><span class="sect2"><a href="ch-extra-packaging-tools.html#id568375">12.1.6. Manipulating Package Files with rpm2cpio</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch12s02.html">12.2. Summary</a></span></dt></dl><
/dd><dt><span class="chapter"><a href="ch-packaging-guidelines.html">13. Packaging Guidelines</a></span></dt><dd><dl><dt><span class="sect1"><a href="ch-packaging-guidelines.html#id699628">13.1. Avoiding Common Problems</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch-packaging-guidelines.html#id629009">13.1.1. Scan the mailing lists</a></span></dt><dt><span class="sect2"><a href="ch-packaging-guidelines.html#id487576">13.1.2. Use rpmbuild</a></span></dt><dt><span class="sect2"><a href="ch-packaging-guidelines.html#id491901">13.1.3. Don’t try to defeat the system</a></span></dt><dt><span class="sect2"><a href="ch-packaging-guidelines.html#id491926">13.1.4. Turn off automatic dependency generation</a></span></dt><dt><span class="sect2"><a href="ch-packaging-guidelines.html#id661809">13.1.5. Don't list directories in %files</a></span></dt><dt><span class="sect2"><a href="ch-packaging-guidelines.html#id563382">13.1.6. Handling circular dependencies</a></span></dt></
dl></dd><dt><span class="sect1"><a href="ch13s02.html">13.2. Following Good Practices</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch13s02.html#id713208">13.2.1. Preparation</a></span></dt><dt><span class="sect2"><a href="ch13s02s02.html">13.2.2. Building</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch13s03.html">13.3. Summary</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-scripting.html">14. Automating RPM with Scripts</a></span></dt><dd><dl><dt><span class="sect1"><a href="ch-scripting.html#id642750">14.1. Scripting</a></span></dt><dt><span class="sect1"><a href="ch14s02.html">14.2. Distinguishing Scripting Languages from Programming Languages</a></span></dt><dt><span class="sect1"><a href="ch14s03.html">14.3. Deciding When to Program and When to Script</a></span></dt><dt><span class="sect1"><a href="ch14s04.html">14.4. Shell Scripting Basics</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch14s04.html#id698724">14.4.1. Writi
ng a script</a></span></dt><dt><span class="sect2"><a href="ch14s04s02.html">14.4.2. Running a script</a></span></dt><dt><span class="sect2"><a href="ch14s04s03.html">14.4.3. Problems running scripts</a></span></dt><dt><span class="sect2"><a href="ch14s04s04.html">14.4.4. Turning a script into a command</a></span></dt><dt><span class="sect2"><a href="ch14s04s05.html">14.4.5. Passing command-line options to your script</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch14s05.html">14.5. Examining RPM Files</a></span></dt><dt><span class="sect1"><a href="ch14s06.html">14.6. Querying the RPM Database</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch14s06.html#id793185">14.6.1. Querying for all packages installed at the same time</a></span></dt><dt><span class="sect2"><a href="ch14s06s02.html">14.6.2. Reading HTML documentation for a package</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch14s07.html">14.7. Where to Go From Here</a></span></dt><dt><s
pan class="sect1"><a href="ch14s08.html">14.8. Summary</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-programming-c.html">15. Programming RPM with C</a></span></dt><dd><dl><dt><span class="sect1"><a href="ch-programming-c.html#id676692">15.1. Programming with the C Library</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch-programming-c.html#id609132">15.1.1. Setting Up a C Programming Environment</a></span></dt><dt><span class="sect2"><a href="ch-programming-c.html#id658946">15.1.2. Setting Up the RPM Programming Environment</a></span></dt><dt><span class="sect2"><a href="ch-programming-c.html#id658982">15.1.3. Using the RPM Library</a></span></dt><dt><span class="sect2"><a href="ch-programming-c.html#id571017">15.1.4. Compiling and Linking RPM Programs</a></span></dt><dt><span class="sect2"><a href="ch-programming-c.html#id786003">15.1.5. Getting information on your RPM environment</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch15s02.ht
ml">15.2. The Power of popt</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch15s02.html#id839350">15.2.1. Popt aliases</a></span></dt><dt><span class="sect2"><a href="ch15s02s02.html">15.2.2. Programming with popt</a></span></dt><dt><span class="sect2"><a href="ch15s02s03.html">15.2.3. Handling Errors</a></span></dt><dt><span class="sect2"><a href="ch15s02s04.html">15.2.4. Running a popt example</a></span></dt><dt><span class="sect2"><a href="ch15s02s05.html">15.2.5. Handling rpm command-line options</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch15s03.html">15.3. Working with RPM Files</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch15s03.html#id489656">15.3.1. Opening RPM files</a></span></dt><dt><span class="sect2"><a href="ch15s03s02.html">15.3.2. Reading the RPM lead and signature</a></span></dt><dt><span class="sect2"><a href="ch15s03s03.html">15.3.3. Reading header information</a></span></dt><dt><span class="sect2"><a href="ch15s03s04.h
tml">15.3.4. A shortcut to header information</a></span></dt><dt><span class="sect2"><a href="ch15s03s05.html">15.3.5. Closing RPM files</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch15s04.html">15.4. Programming with the RPM Database</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch15s04.html#id745314">15.4.1. Database iterators</a></span></dt><dt><span class="sect2"><a href="ch15s04s02.html">15.4.2. Dependency Sets</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch15s05.html">15.5. Comparing an RPM File to an Installed Package</a></span></dt><dt><span class="sect1"><a href="ch15s06.html">15.6. Where to Go from Here</a></span></dt><dt><span class="sect1"><a href="ch15s07.html">15.7. Summary</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-rpm-programming-python.html">16. Programming RPM with Python</a></span></dt><dd><dl><dt><span class="sect1"><a href="ch-rpm-programming-python.html#id754566">16.1. Setting Up a Python Developm
ent Environment</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch-rpm-programming-python.html#id639412">16.1.1. Installing the base Python packages</a></span></dt><dt><span class="sect2"><a href="ch-rpm-programming-python.html#id639641">16.1.2. Using Python for graphics</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch16s02.html">16.2. The Python API Hierarchy</a></span></dt><dt><span class="sect1"><a href="ch16s03.html">16.3. Programming with the RPM Database</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch16s03.html#id821727">16.3.1. Accessing the RPM database</a></span></dt><dt><span class="sect2"><a href="ch16s03s02.html">16.3.2. Querying the RPM database</a></span></dt><dt><span class="sect2"><a href="ch16s03s03.html">16.3.3. Examining the package header</a></span></dt><dt><span class="sect2"><a href="ch16s03s04.html">16.3.4. Querying for specific packages</a></span></dt><dt><span class="sect2"><a href="ch16s03s05.html">16.3.5. Printing inf
ormation on packages</a></span></dt><dt><span class="sect2"><a href="ch16s03s06.html">16.3.6. Refining queries</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch16s04.html">16.4. Reading Package Files</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch16s04.html#id662386">16.4.1. Reading headers from package files</a></span></dt><dt><span class="sect2"><a href="ch16s04s02.html">16.4.2. Setting the verification flags</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch16s05.html">16.5. Dependency Comparisons</a></span></dt><dt><span class="sect1"><a href="ch16s06.html">16.6. Installing and Upgrading Packages</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch16s06.html#id615216">16.6.1. Building up the transaction set</a></span></dt><dt><span class="sect2"><a href="ch16s06s02.html">16.6.2. Transaction elements</a></span></dt><dt><span class="sect2"><a href="ch16s06s03.html">16.6.3. Checking and reordering the transaction elements</a></span></dt
><dt><span class="sect2"><a href="ch16s06s04.html">16.6.4. Running the transaction</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch16s07.html">16.7. Where to Go from Here</a></span></dt><dt><span class="sect1"><a href="ch16s08.html">16.8. Summary</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-programming-perl.html">17. Programming RPM with Perl</a></span></dt><dd><dl><dt><span class="sect1"><a href="ch-programming-perl.html#id747785">17.1. Getting and Using the Perl RPM Modules</a></span></dt><dt><span class="sect1"><a href="ch17s02.html">17.2. Working with RPM Files</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch17s02.html#id675588">17.2.1. Opening package files</a></span></dt><dt><span class="sect2"><a href="ch17s02s02.html">17.2.2. Listing tags from the package</a></span></dt><dt><span class="sect2"><a href="ch17s02s03.html">17.2.3. Convenience methods</a></span></dt><dt><span class="sect2"><a href="ch17s02s04.html">17.2.4. Listing t
he name and version</a></span></dt><dt><span class="sect2"><a href="ch17s02s05.html">17.2.5. Checking whether the package is a source package</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch17s03.html">17.3. Programming with the RPM Database</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch17s03.html#id668276">17.3.1. Opening the database</a></span></dt><dt><span class="sect2"><a href="ch17s03s02.html">17.3.2. Finding packages</a></span></dt><dt><span class="sect2"><a href="ch17s03s03.html">17.3.3. Iterating over packages</a></span></dt><dt><span class="sect2"><a href="ch17s03s04.html">17.3.4. Additional query subroutines</a></span></dt><dt><span class="sect2"><a href="ch17s03s05.html">17.3.5. Getting information on packages</a></span></dt><dt><span class="sect2"><a href="ch17s03s06.html">17.3.6. Comparing versions</a></span></dt><dt><span class="sect2"><a href="ch17s03s07.html">17.3.7. Closing the database</a></span></dt></dl></dd><dt><span class="sect1
"><a href="ch17s04.html">17.4. Where to Go from Here</a></span></dt><dt><span class="sect1"><a href="ch17s05.html">17.5. Summary</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-other-linuxes.html">18. Using RPM on Non-Red Hat Linuxes</a></span></dt><dd><dl><dt><span class="sect1"><a href="ch-other-linuxes.html#id492534">18.1. Troubleshooting RPM Installation Issues</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch-other-linuxes.html#id578601">18.1.1. Dealing with RPM versions</a></span></dt><dt><span class="sect2"><a href="ch-other-linuxes.html#id743717">18.1.2. Dealing with divisions of software into packages</a></span></dt><dt><span class="sect2"><a href="ch-other-linuxes.html#id841602">18.1.3. Dealing with dependency issues</a></span></dt><dt><span class="sect2"><a href="ch-other-linuxes.html#id556728">18.1.4. Dealing with install locations</a></span></dt><dt><span class="sect2"><a href="ch-other-linuxes.html#id638386">18.1.5. When all else fails,
rebuild from the source package</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch18s02.html">18.2. Handling Problems Building RPMs</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch18s02.html#id638432">18.2.1. Writing distribution-specific packages</a></span></dt><dt><span class="sect2"><a href="ch18s02s02.html">18.2.2. Dealing with automatic dependency generation</a></span></dt><dt><span class="sect2"><a href="ch18s02s03.html">18.2.3. Dealing with different macros</a></span></dt><dt><span class="sect2"><a href="ch18s02s04.html">18.2.4. Making relocatable packages</a></span></dt><dt><span class="sect2"><a href="ch18s02s05.html">18.2.5. Creating an RPM build environment</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch18s03.html">18.3. Dealing with Non-RPM-Based Linux Versions</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch18s03.html#id554032">18.3.1. Handling non-RPM packages with alien</a></span></dt></dl></dd><dt><span class="sect1"
><a href="ch18s04.html">18.4. Standardizing RPMs</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch18s04.html#id554078">18.4.1. Filesystem Hierarchy Standard</a></span></dt><dt><span class="sect2"><a href="ch18s04s02.html">18.4.2. RPM adoption</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch18s05.html">18.5. Summary</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-other-os.html">19. RPM on Other Operating Systems</a></span></dt><dd><dl><dt><span class="sect1"><a href="ch-other-os.html#id715002">19.1. Running RPM on Other Operating Systems</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch-other-os.html#id742916">19.1.1. Getting RPM for your system</a></span></dt><dt><span class="sect2"><a href="ch-other-os.html#id719450">19.1.2. Running RPM on Windows</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch19s02.html">19.2. Bootstrapping RPM On Other Operating Systems</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch19s0
2.html#id719502">19.2.1. Downloading the RPM software</a></span></dt><dt><span class="sect2"><a href="ch19s02s02.html">19.2.2. Extracting the software</a></span></dt><dt><span class="sect2"><a href="ch19s02s03.html">19.2.3. Reading the INSTALL file</a></span></dt><dt><span class="sect2"><a href="ch19s02s04.html">19.2.4. Libraries required by RPM</a></span></dt><dt><span class="sect2"><a href="ch19s02s05.html">19.2.5. Tools for building RPM</a></span></dt><dt><span class="sect2"><a href="ch19s02s06.html">19.2.6. Compiling RPM</a></span></dt><dt><span class="sect2"><a href="ch19s02s07.html">19.2.7. Handling problems</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch19s03.html">19.3. Setting Up the RPM System</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch19s03.html#id498249">19.3.1. Setting up the RPM database</a></span></dt><dt><span class="sect2"><a href="ch19s03s02.html">19.3.2. Creating the RPM environment</a></span></dt></dl></dd><dt><span class="sect
1"><a href="ch19s04.html">19.4. Creating Non-Linux RPMS</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch19s04.html#id612860">19.4.1. Setting up a build environment</a></span></dt><dt><span class="sect2"><a href="ch19s04s02.html">19.4.2. Cross-building packages</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch19s05.html">19.5. Summary</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-customizing-rpm.html">20. Customizing RPM Behavior</a></span></dt><dd><dl><dt><span class="sect1"><a href="ch-customizing-rpm.html#id773884">20.1. Customizing with RPM Macros</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch-customizing-rpm.html#id820436">20.1.1. Defining macros</a></span></dt><dt><span class="sect2"><a href="ch-customizing-rpm.html#id721750">20.1.2. Customizing Macros</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch20s02.html">20.2. Configuring RPM Settings</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch20s02.html
#id558168">20.2.1. Viewing the current settings</a></span></dt><dt><span class="sect2"><a href="ch20s02s02.html">20.2.2. Locating the rpmrc files</a></span></dt><dt><span class="sect2"><a href="ch20s02s03.html">20.2.3. Changing settings</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch20s03.html">20.3. Adding Popt Aliases</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch20s03.html#id692629">20.3.1. Defining aliases</a></span></dt><dt><span class="sect2"><a href="ch20s03s02.html">20.3.2. Customizing popt aliases</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch20s04.html">20.4. Summary</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-command-reference.html">21. RPM Command Reference</a></span></dt><dd><dl><dt><span class="sect1"><a href="ch-command-reference.html#id695500">21.1. The rpm Command</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch-command-reference.html#id561909">21.1.1. Upgrade, freshen, and install options</
a></span></dt><dt><span class="sect2"><a href="ch-command-reference.html#id578909">21.1.2. Erase options</a></span></dt><dt><span class="sect2"><a href="ch-command-reference.html#id717458">21.1.3. Signature options</a></span></dt><dt><span class="sect2"><a href="ch-command-reference.html#id794197">21.1.4. Verify options</a></span></dt><dt><span class="sect2"><a href="ch-command-reference.html#id693385">21.1.5. Database options</a></span></dt><dt><span class="sect2"><a href="ch-command-reference.html#id558887">21.1.6. Miscellaneous options</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch21s02.html">21.2. The rpmbuild Command</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch21s02.html#id568724">21.2.1. Building from a spec file</a></span></dt><dt><span class="sect2"><a href="ch21s02s02.html">21.2.2. Building from a compressed tar archive</a></span></dt><dt><span class="sect2"><a href="ch21s02s03.html">21.2.3. Rebuilding RPMs from source RPMs</a></span></dt
><dt><span class="sect2"><a href="ch21s02s04.html">21.2.4. Customizing the build</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-specfile-syntax.html">22. Spec File Syntax</a></span></dt><dd><dl><dt><span class="sect1"><a href="ch-specfile-syntax.html#id654084">22.1. Package Information Tags</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch-specfile-syntax.html#id722547">22.1.1. Comments</a></span></dt><dt><span class="sect2"><a href="ch-specfile-syntax.html#id857248">22.1.2. Build settings</a></span></dt><dt><span class="sect2"><a href="ch-specfile-syntax.html#id857280">22.1.3. Dependency tags</a></span></dt><dt><span class="sect2"><a href="ch-specfile-syntax.html#id699217">22.1.4. Source files</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch22s02.html">22.2. Macros</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch22s02.html#id653606">22.2.1. Variable definition macros</a></span></dt><dt><span class="sect2"><a href="ch2
2s02s02.html">22.2.2. Conditional macros</a></span></dt><dt><span class="sect2"><a href="ch22s02s03.html">22.2.3. Built-in macros</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch22s03.html">22.3. Build Sections</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch22s03.html#id641190">22.3.1. Build preparation</a></span></dt><dt><span class="sect2"><a href="ch22s03s02.html">22.3.2. Build</a></span></dt><dt><span class="sect2"><a href="ch22s03s03.html">22.3.3. Installation</a></span></dt><dt><span class="sect2"><a href="ch22s03s04.html">22.3.4. Clean up</a></span></dt><dt><span class="sect2"><a href="ch22s03s05.html">22.3.5. Install and uninstall scripts</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch22s04.html">22.4. File Tags</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch22s04.html#id786867">22.4.1. Making relocatable packages</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch22s05.html">22.5. The Change Log</a></span></dt>
</dl></dd><dt><span class="chapter"><a href="ch-rpm-evolution.html">23. RPM Feature Evolution</a></span></dt><dt><span class="chapter"><a href="ch-package-structure.html">24. RPM Package File Structure</a></span></dt><dd><dl><dt><span class="sect1"><a href="ch-package-structure.html#id856787">24.1. The Package File</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch-package-structure.html#id582395">24.1.1. The file identifier</a></span></dt><dt><span class="sect2"><a href="ch-package-structure.html#id843773">24.1.2. The signature</a></span></dt><dt><span class="sect2"><a href="ch-package-structure.html#id674921">24.1.3. The header</a></span></dt><dt><span class="sect2"><a href="ch-package-structure.html#id800907">24.1.4. The payload</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-online-resources.html">25. RPM Resources</a></span></dt><dd><dl><dt><span class="sect1"><a href="ch-online-resources.html#id701853">25.1. Finding RPM Sites</a></span>
</dt><dd><dl><dt><span class="sect2"><a href="ch-online-resources.html#id667310">25.1.1. The main rpm.org site</a></span></dt><dt><span class="sect2"><a href="ch-online-resources.html#id562433">25.1.2. RPM locator sites</a></span></dt><dt><span class="sect2"><a href="ch-online-resources.html#id798080">25.1.3. RPM tools sites</a></span></dt><dt><span class="sect2"><a href="ch-online-resources.html#id626076">25.1.4. Programming sites</a></span></dt><dt><span class="sect2"><a href="ch-online-resources.html#id626107">25.1.5. Sites related to RPM</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch25s02.html">25.2. Accessing RPM Mailing Lists and Newsgroups</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-development-tools.html">26. Linux Text Editors and Development Tools</a></span></dt><dd><dl><dt><span class="sect1"><a href="ch-development-tools.html#id496359">26.1. General Text Editors</a></span></dt><dt><span class="sect1"><a href="ch26s02.html">26.2. P
rogramming Text Editors</a></span></dt><dt><span class="sect1"><a href="ch26s03.html">26.3. Integrated Development Environments for C Programming</a></span></dt><dt><span class="sect1"><a href="ch26s04.html">26.4. Integrated Development Environments for Python Programming</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-licensing.html">27. Licensing RPM</a></span></dt><dd><dl><dt><span class="sect1"><a href="ch-licensing.html#id573888">27.1. The GNU General Public License</a></span></dt></dl></dd><dt><span class="appendix"><a href="appe-Publican-Revision_History.html">A. Istoria reviziilor</a></span></dt><dt><span class="index"><a href="ix01.html">Index</a></span></dt></dl></div></div><ul class="docnav"><li class="previous"></li><li class="next"><a accesskey="n" href="ch-intro-packaging.html"><strong>ÃŽnainte</strong>Introducing Package Management</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ix01.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ix01.html
new file mode 100644
index 0000000..79b8dd7
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ix01.html
@@ -0,0 +1,10 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Index</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="index.html" title="Ghid RPM" /><link rel="prev" href="appe-Publican-Revision_History.html" title="Anexa A. Istoria reviziilor" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="appe-Publican-Revision_History.html"><strong>ÃŽnapoi</strong></a></li><li class="next"></li></ul><div class="index" id="id629475"><div class="titlepage"><div><div><h2 class="title">Index</h2></div></div></di
v><div class="index"></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="appe-Publican-Revision_History.html"><strong>Înapoi</strong>Anexa A. Istoria reviziilor</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/pr01s02.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/pr01s02.html
new file mode 100644
index 0000000..0a4d86a
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/pr01s02.html
@@ -0,0 +1,20 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2. Overcoming the Installation Obstacles</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-intro-packaging.html" title="Introducing Package Management" /><link rel="prev" href="ch-intro-packaging.html" title="Introducing Package Management" /><link rel="next" href="pr01s02s02.html" title="2.2. Built-in system utilities" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-intro-packaging.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="pr
01s02s02.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id610087" class="title">Overcoming the Installation Obstacles</h1></div></div></div><div class="para">
+ None of the tasks you must perform to install, upgrade, or uninstall applications are especially difficult. However, these steps quickly become daunting when you consider all the files that must be managed. A full Fedora installation provides around 3,000 executable commands and over 160,000 total files (some other Linux distributions are even larger!). Obviously, managing all these files by hand, although theoretically possible, is not technically feasible. On a smaller scale, even management of single applications is not practical. The Postfix e-mail server application, for example, consists of around 275 files scattered in a dozen or so different directories. Imagine trying to remember and manually remove all of those files (and only those files) to uninstall Postfix from your system!
+ </div><div class="para">
+ All the steps needed to manage software on Unix or Linux systems are hardly unique to Unix; all operating systems have similar procedures that must be followed to make software usable on the system. For this reason, many approaches have been adopted toward software installation, uninstallation, and upgrading.
+ </div><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id610110" class="title">Application-level utilities</h1></div></div></div><div class="para">
+ Some operating systems, such as MS-DOS, have supplied absolutely no built-in tools for software management. Installation of applications on such systems occurs in one of two ways: software is installed manually, using file-copy utilities to put all the application files in the appropriate places on the system, or software is installed using a custom-written installation application (as is usually the case for MS-DOS applications).
+ </div><div class="para">
+ Once installed, software can be uninstalled in one of two ways: you can manually delete each file installed for the application (assuming you can even remember them all), or the application might come with a custom uninstallation utility that can be run to remove the application. Upgrading an already installed application on such a system uses a similar procedure. If the application comes with an installation utility capable of handling application upgrades, you can use the utility to perform the upgrade. Otherwise, the software must be manually upgraded using the procedure described previously.
+ </div><div class="note"><div class="admonition_header"><h2>Current Windows Versions</h2></div><div class="admonition"><div class="para">
+ Current versions of Windows, such as Windows XP, have a central database of installed applications.
+ </div></div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-intro-packaging.html"><strong>Înapoi</strong>Introducing Package Management</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="pr01s02s02.html"><strong>Înainte</strong>2.2. Built-in system utilities</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/pr01s02s02.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/pr01s02s02.html
new file mode 100644
index 0000000..6c31c2c
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/pr01s02s02.html
@@ -0,0 +1,24 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.2. Built-in system utilities</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="pr01s02.html" title="2. Overcoming the Installation Obstacles" /><link rel="prev" href="pr01s02.html" title="2. Overcoming the Installation Obstacles" /><link rel="next" href="pr01s03.html" title="3. Linux Software Management Tools: Packages" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="pr01s02.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="pr01
s03.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect2"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id570514" class="title">Built-in system utilities</h1></div></div></div><div class="para">
+ Other operating systems have come with built-in utilities that a system administrator can use to manage the system’s software. These utilities can be run to install the software on the system; typically, they take some of the work out of manually installing software, dealing with issues such as figuring out which files need to be put where on the system. Once installed, these utilities typically track the files that have been installed. This knowledge can usually be used to uninstall those applications automatically. Since the software knows which files are associated with the application, it can be told to uninstall the application, and it can find and delete all the files that belong to that application.
+ </div><div class="para">
+ These built-in utilities typically come in two different forms. One type focuses on managing the installation process, providing custom utilities that can be used to perform the otherwise manual tasks of compiling software and copying files into their final locations. The three major freely available Berkeley Unix, or BSD, operating systems, NetBSD, FreeBSD, and OpenBSD, for example, ship with a software-management system called, variously, ports (FreeBSD and OpenBSD) or packages (NetBSD).
+ </div><div class="para">
+ The ports system is composed of extensions to the normal Unix software-compilation utilities that help it automate and track many of the steps of a standard source-code compilation. When using ports, you still download source code, unarchive it, configure it, compile it, and install it, but the ports software automates many of these steps. Furthermore, the ports system does limited tracking of the files it installs. Although it does not offer more advanced features (such as an interface to search all installed files to see what application supplied that file) or the ability to upgrade installed applications, it does provide the ability to uninstall applications that are installed using ports. These sorts of limitations are typical of management applications that function as the ports system does, by enhancing the compilation and installation phases of application installation. The packages system on NetBSD has similar limitations.
+ </div><div class="para">
+ Other system-management utilities focus less attention on compiling an application for installation and more attention on the files that must be installed on the system after the application has been compiled.
+ </div><div class="para">
+ For example, the standard System V Unix package-management software supplied with most commercial Unix systems (Sun's Solaris, for example) devotes no attention to management of software compilation at all. Instead, it tracks the individual files associated with each application in a system database.
+ </div><div class="para">
+ To install software using the System V tools, you must compile the software. After compiling the software in the standard fashion, prepare a list of the files from that compilation that need to be installed on the system. Be certain to state where the files need to be installed and what permissions and ownerships they need to have once installed. Then run a series of commands that look at this list, find the files listed in it, and archive them into one file, along with a copy of this list that specifies where they should be installed and the ownerships and permissions. This single archive file can then be transferred to other machines, where a System V software-management command can be used to install it. This System V installation command (typically called <code class="command">pkgadd</code>) unpacks the archive, copies the files into their final destinations based on the enclosed listing, and sets permissions and ownerships on the files as specified by the listing. Fin
ally, this <code class="command">pkgadd</code> command registers the list of freshly installed files into a system-wide database of installed files.
+ </div><div class="para">
+ Such a system offers several advantages over manual software installation. Software can now be installed and uninstalled easily, and the system-wide database of installed files can be readily searched to locate installed applications and files. However, this sort of system also has severe limitations; it is far less flexible in the software-configuration stages than software such as the FreeBSD ports system, which offers great control over the software-compilation stage of software installation.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="pr01s02.html"><strong>Înapoi</strong>2. Overcoming the Installation Obstacles</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="pr01s03.html"><strong>Înainte</strong>3. Linux Software Management Tools: Packages</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/pr01s03.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/pr01s03.html
new file mode 100644
index 0000000..b0c9c1e
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/pr01s03.html
@@ -0,0 +1,50 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3. Linux Software Management Tools: Packages</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-intro-packaging.html" title="Introducing Package Management" /><link rel="prev" href="pr01s02s02.html" title="2.2. Built-in system utilities" /><link rel="next" href="pr01s04.html" title="4. Summary" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="pr01s02s02.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="pr01s04.html"><strong>ÃŽnainte</strong></
a></li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id666432" class="title">Linux Software Management Tools: Packages</h1></div></div></div><div class="para">
+ Initially, Linux had neither type of software-management tool. In the early days of Linux, you installed Linux by cross-compiling it under a different operating system (Minix), then manually installing the compiled Linux programs into the appropriate locations to produce a working system. As Linux has matured, however, it has acquired software-management tools that have made software installation, removal, and upgrade significantly easier than in the early days. The exact software-management tool used on modern Linux systems varies from distribution to distribution, but both approaches to system management can be found in the tools used by various distributions.
+ </div><div class="para">
+ The Gentoo Linux (<a href="http://www.gentoo.org/">http://www.gentoo.org/</a>) distribution, for example, uses a software-management system called Portage, which is very similar to the FreeBSD ports system. Like ports, Portage provides great control over software compilation and installation, providing a collection of scripts that automate much of the basic work of downloading and compiling software.
+ </div><div class="para">
+ At the other end of the spectrum, the now-defunct deepLinux distribution used a software-management system called <code class="command">deep-package</code>. <code class="command">deep-package</code> was intended to be a complete reimplementation of the Solaris <code class="command">pkgadd</code> utility and its helpers. Like the Solaris <code class="command">pkgadd</code> software, <code class="command">deep-package</code> paid no attention to half of the question of how to manage software, focusing entirely on software installation and tracking issues while entirely ignoring the initial compilation of the software.
+ </div><div class="para">
+ More typically, however, Linux software-management tools use an approach somewhere between the two extremes represented by Portage and deep-package. Most Linux software-management tools provide software that manages the compilation of software, similarly to the FreeBSD ports tools. However, these software-management tools typically produce packages from the software they compile. Much like the archives produced by the System V software-management tools, packages are simply archive files that contain two things: a collection of related files, which together have a common use, and a script that provides all the metadata about those files necessary to install and manage those files.
+ </div><div class="para">
+ Typically, packages represent applications. For example, a Postfix package contains the 275 files that make up Postfix and a script that specifies where on the system those 275 files need to be placed, as well as what permissions and ownership those files need. A single command can then take this Postfix package file, extract its 275 archived files, and use the script to place those files correctly on the system.
+ </div><div class="para">
+ In addition, most Linux software-management tools have a database component that tracks files and applications that have been installed using the package-management software, helping the package manager do its job of easing the management of installed software.
+ </div><div class="para">
+ In the case of a full Fedora installation, this package-management software maintains a database of information regarding all 160,000 files on the system; as applications are installed on the system, this database is updated with information regarding the new application and the locations of its component files. This database is the key component, making it possible to manage the system. Since this database remembers which 275 files compose the Postfix application, it ensures that I can uninstall Postfix with a single command that accesses this database, without my having to remember the locations of all 275 files that make up the Postfix application.
+ </div><div class="para">
+ A wide variety of software-management tools are available for Linux to help lessen the work involved with installing, removing, and upgrading applications installed on the system. This book focuses on one of these tools, the RPM Package Management software, or RPM.
+ </div><div class="note"><div class="admonition_header"><h2>Change of Name</h2></div><div class="admonition"><div class="para">
+ RPM was originally called Red Hat Package Manager. After adoption by other Linux distributions, the name has changed to simply the RPM Package Manager. The RPM initials remain the same.
+ </div></div></div><div class="para">
+ As the original name implies, RPM was developed by Red Hat, Inc., the major Linux distributor in the United States. Even though the original name seems to point to a Red Hat-only solution, most Linux distributions use the RPM software. The RPM software provides a foundation needed by Linux system administrators throughout the world. You can even use RPM on other operating systems, both Linux and non-Linux, as covered in <a class="xref" href="ch-other-linuxes.html">Cap. 18, <em>Using RPM on Non-Red Hat Linuxes</em></a> and <a class="xref" href="ch-other-os.html">Cap. 19, <em>RPM on Other Operating Systems</em></a>, respectively.
+ </div><div class="para">
+ The RPM system provides all of the features needed to manage applications, including a database of installed packages with their version numbers, the ability to install, remove, and update packages, and the ability to recompile an application from a source code RPM package.
+ </div><div class="para">
+ The remaining chapters in Part I go into depth on what you can do with RPM packages and the commands you need to work with the RPM system:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ <a class="xref" href="ch-intro-rpm.html">Cap. 1, <em>Introduction to RPM</em></a> provides an overview of the RPM system, exploring what it was designed for and where it has weaknesses.
+ </div></li><li class="listitem"><div class="para">
+ <a class="xref" href="ch-rpm-overview.html">Cap. 2, <em>RPM Overview</em></a> discusses the technical details of how the RPM system works, where the database of packages gets stored, and what commands should be available for working with RPM packages.
+ </div></li><li class="listitem"><div class="para">
+ <a class="xref" href="ch-using-rpm.html">Cap. 3, <em>Using RPM</em></a> continues the discussion by covering the three major tasks you need to perform with RPM packages: installing software, removing software, and upgrading software you have already installed.
+ </div></li><li class="listitem"><div class="para">
+ <a class="xref" href="ch-using-rpm-db.html">Cap. 4, <em>Using the RPM Database</em></a> covers the RPM database, how it works, where it resides, and how you can use it to better manage your system.
+ </div></li><li class="listitem"><div class="para">
+ <a class="xref" href="ch-dependencies.html">Cap. 5, <em>Package Dependencies</em></a> delves into package dependencies, a very important concept. Most major applications depend on a number of other packages. Sometimes these dependencies get very complex, with one package depending on particular versions of other packages. With thousands of packages on your system, this can lead to a big mess. This chapter helps you to sort through the issues.
+ </div></li><li class="listitem"><div class="para">
+ <a class="xref" href="ch-transactions.html">Cap. 6, <em>Transactions</em></a> covers the important issue of transactions, so that you can ensure your system gets updated in an orderly manner and so that you can roll back changes if something does not work out.
+ </div></li><li class="listitem"><div class="para">
+ <a class="xref" href="ch-management-software.html">Cap. 7, <em>RPM Management Software</em></a> introduces a host of tools that can help you find RPM packages as well as manage the packages on your system. This includes graphical interfaces on top of the RPM system and special Internet search sites devoted just to RPM packages.
+ </div></li></ol></div><div class="para">
+ Later chapters cover creating RPM packages, programming with RPM, and extending the functionality provided by the base RPM system.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="pr01s02s02.html"><strong>Înapoi</strong>2.2. Built-in system utilities</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="pr01s04.html"><strong>Înainte</strong>4. Summary</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/pr01s04.html b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/pr01s04.html
new file mode 100644
index 0000000..dd9773d
--- /dev/null
+++ b/public_html/ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/pr01s04.html
@@ -0,0 +1,14 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>4. Summary</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.6" /><meta name="package" content="Fedora_Draft_Documentation-RPM_Guide-0.1-ro-0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.RPM_Guide');
+ </script><link rel="home" href="index.html" title="Ghid RPM" /><link rel="up" href="ch-intro-packaging.html" title="Introducing Package Management" /><link rel="prev" href="pr01s03.html" title="3. Linux Software Management Tools: Packages" /><link rel="next" href="ch-intro-rpm.html" title="Cap. 1. Introduction to RPM" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="pr01s03.html"><strong>ÃŽnapoi</strong></a></li><li class="next"><a accesskey="n" href="ch-intro-rp
m.html"><strong>ÃŽnainte</strong></a></li></ul><div class="sect1"><div class="titlepage"><div><div keep-together.within-column="always"><h1 id="id608928" class="title">Summary</h1></div></div></div><div class="para">
+ Modern operating systems have large complex sets of applications, resulting in thousands of files to keep track of for upgrades, installation, and removal of packages. All this complexity has lead Linux vendors to develop a variety of package-management tools.
+ </div><div class="para">
+ This chapter briefly introduced the RPM Package Manager, or RPM for short. The next chapter provides an overview of the RPM system, showing how all the parts fit together.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="pr01s03.html"><strong>Înapoi</strong>3. Linux Software Management Tools: Packages</a></li><li class="up"><a accesskey="u" href="#"><strong>Sus</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Acasă</strong></a></li><li class="next"><a accesskey="n" href="ch-intro-rpm.html"><strong>Înainte</strong>Cap. 1. Introduction to RPM</a></li></ul></body></html>
diff --git a/public_html/ro/Fedora_Draft_Documentation/0.1/pdf/RPM_Guide/Fedora_Draft_Documentation-0.1-RPM_Guide-ro.pdf b/public_html/ro/Fedora_Draft_Documentation/0.1/pdf/RPM_Guide/Fedora_Draft_Documentation-0.1-RPM_Guide-ro.pdf
new file mode 100644
index 0000000..a99fda1
Binary files /dev/null and b/public_html/ro/Fedora_Draft_Documentation/0.1/pdf/RPM_Guide/Fedora_Draft_Documentation-0.1-RPM_Guide-ro.pdf differ
diff --git a/public_html/ro/Site_Statistics.html b/public_html/ro/Site_Statistics.html
new file mode 100644
index 0000000..5501668
--- /dev/null
+++ b/public_html/ro/Site_Statistics.html
@@ -0,0 +1,419 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
+ <link rel="stylesheet" href="../interactive.css" type="text/css" />
+ <title>Statistics</title>
+</head>
+<body class="toc_embeded">
+<div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div>
+<div>
+<h1 class="producttitle">Statistics</h1>
+<p>
+</p>
+<table class="stats">
+ <tr>
+ <th>Language</th>
+ <th>Code</th>
+ <th>Products</th>
+ <th>Books</th>
+ <th>Versions</th>
+ <th>Packages</th>
+ </tr>
+
+ <tr>
+ <td>English</td>
+ <td>en-US</td>
+ <td>4</td>
+ <td>33</td>
+ <td>17</td>
+ <td>102</td>
+ </tr>
+
+ <tr>
+ <td>Spanish</td>
+ <td>es-ES</td>
+ <td>3</td>
+ <td>18</td>
+ <td>12</td>
+ <td>59</td>
+ </tr>
+
+ <tr>
+ <td>Dutch</td>
+ <td>nl-NL</td>
+ <td>1</td>
+ <td>17</td>
+ <td>8</td>
+ <td>51</td>
+ </tr>
+
+ <tr>
+ <td>Italian</td>
+ <td>it-IT</td>
+ <td>3</td>
+ <td>13</td>
+ <td>12</td>
+ <td>38</td>
+ </tr>
+
+ <tr>
+ <td>Polish</td>
+ <td>pl-PL</td>
+ <td>3</td>
+ <td>10</td>
+ <td>11</td>
+ <td>37</td>
+ </tr>
+
+ <tr>
+ <td>Portuguese</td>
+ <td>pt-PT</td>
+ <td>2</td>
+ <td>12</td>
+ <td>11</td>
+ <td>32</td>
+ </tr>
+
+ <tr>
+ <td>Chinese</td>
+ <td>zh-CN</td>
+ <td>3</td>
+ <td>12</td>
+ <td>12</td>
+ <td>31</td>
+ </tr>
+
+ <tr>
+ <td>Ukrainian</td>
+ <td>uk-UA</td>
+ <td>3</td>
+ <td>12</td>
+ <td>11</td>
+ <td>27</td>
+ </tr>
+
+ <tr>
+ <td>German</td>
+ <td>de-DE</td>
+ <td>2</td>
+ <td>8</td>
+ <td>11</td>
+ <td>25</td>
+ </tr>
+
+ <tr>
+ <td>Japanese</td>
+ <td>ja-JP</td>
+ <td>4</td>
+ <td>9</td>
+ <td>12</td>
+ <td>25</td>
+ </tr>
+
+ <tr>
+ <td>Swedish</td>
+ <td>sv-SE</td>
+ <td>2</td>
+ <td>7</td>
+ <td>9</td>
+ <td>25</td>
+ </tr>
+
+ <tr>
+ <td>Russian</td>
+ <td>ru-RU</td>
+ <td>3</td>
+ <td>12</td>
+ <td>10</td>
+ <td>24</td>
+ </tr>
+
+ <tr>
+ <td>Serbian</td>
+ <td>sr-RS</td>
+ <td>2</td>
+ <td>9</td>
+ <td>9</td>
+ <td>24</td>
+ </tr>
+
+ <tr>
+ <td>Portuguese</td>
+ <td>pt-BR</td>
+ <td>2</td>
+ <td>8</td>
+ <td>8</td>
+ <td>23</td>
+ </tr>
+
+ <tr>
+ <td>French</td>
+ <td>fr-FR</td>
+ <td>2</td>
+ <td>7</td>
+ <td>7</td>
+ <td>19</td>
+ </tr>
+
+ <tr>
+ <td>Finnish</td>
+ <td>fi-FI</td>
+ <td>1</td>
+ <td>5</td>
+ <td>9</td>
+ <td>18</td>
+ </tr>
+
+ <tr>
+ <td>Serbian</td>
+ <td>sr-Latn-RS</td>
+ <td>2</td>
+ <td>8</td>
+ <td>7</td>
+ <td>16</td>
+ </tr>
+
+ <tr>
+ <td>Greek</td>
+ <td>el-GR</td>
+ <td>2</td>
+ <td>4</td>
+ <td>5</td>
+ <td>12</td>
+ </tr>
+
+ <tr>
+ <td>Czech</td>
+ <td>cs-CZ</td>
+ <td>1</td>
+ <td>4</td>
+ <td>4</td>
+ <td>9</td>
+ </tr>
+
+ <tr>
+ <td>Chinese</td>
+ <td>zh-TW</td>
+ <td>1</td>
+ <td>7</td>
+ <td>3</td>
+ <td>7</td>
+ </tr>
+
+ <tr>
+ <td>Catalan</td>
+ <td>ca-ES</td>
+ <td>1</td>
+ <td>4</td>
+ <td>3</td>
+ <td>6</td>
+ </tr>
+
+ <tr>
+ <td>Marathi</td>
+ <td>mr-IN</td>
+ <td>1</td>
+ <td>4</td>
+ <td>4</td>
+ <td>6</td>
+ </tr>
+
+ <tr>
+ <td>Gujarati</td>
+ <td>gu-IN</td>
+ <td>1</td>
+ <td>4</td>
+ <td>3</td>
+ <td>5</td>
+ </tr>
+
+ <tr>
+ <td>Norwegian Bokmal</td>
+ <td>nb-NO</td>
+ <td>1</td>
+ <td>2</td>
+ <td>3</td>
+ <td>5</td>
+ </tr>
+
+ <tr>
+ <td>Hindi</td>
+ <td>hi-IN</td>
+ <td>1</td>
+ <td>4</td>
+ <td>2</td>
+ <td>4</td>
+ </tr>
+
+ <tr>
+ <td>Hungarian</td>
+ <td>hu-HU</td>
+ <td>1</td>
+ <td>2</td>
+ <td>2</td>
+ <td>4</td>
+ </tr>
+
+ <tr>
+ <td>Indonesian</td>
+ <td>id-ID</td>
+ <td>1</td>
+ <td>2</td>
+ <td>3</td>
+ <td>4</td>
+ </tr>
+
+ <tr>
+ <td>Malayalam</td>
+ <td>ml-IN</td>
+ <td>1</td>
+ <td>3</td>
+ <td>2</td>
+ <td>4</td>
+ </tr>
+
+ <tr>
+ <td>Assamese</td>
+ <td>as-IN</td>
+ <td>1</td>
+ <td>3</td>
+ <td>2</td>
+ <td>3</td>
+ </tr>
+
+ <tr>
+ <td>Bulgarian</td>
+ <td>bg-BG</td>
+ <td>1</td>
+ <td>2</td>
+ <td>2</td>
+ <td>3</td>
+ </tr>
+
+ <tr>
+ <td>Danish</td>
+ <td>da-DK</td>
+ <td>2</td>
+ <td>3</td>
+ <td>2</td>
+ <td>3</td>
+ </tr>
+
+ <tr>
+ <td>Kannada</td>
+ <td>kn-IN</td>
+ <td>1</td>
+ <td>3</td>
+ <td>2</td>
+ <td>3</td>
+ </tr>
+
+ <tr>
+ <td>Oriya</td>
+ <td>or-IN</td>
+ <td>1</td>
+ <td>3</td>
+ <td>2</td>
+ <td>3</td>
+ </tr>
+
+ <tr>
+ <td>Telugu</td>
+ <td>te-IN</td>
+ <td>1</td>
+ <td>3</td>
+ <td>2</td>
+ <td>3</td>
+ </tr>
+
+ <tr>
+ <td>Bengali</td>
+ <td>bn-IN</td>
+ <td>1</td>
+ <td>2</td>
+ <td>2</td>
+ <td>2</td>
+ </tr>
+
+ <tr>
+ <td>Persian</td>
+ <td>fa-IR</td>
+ <td>2</td>
+ <td>2</td>
+ <td>2</td>
+ <td>2</td>
+ </tr>
+
+ <tr>
+ <td>Korean</td>
+ <td>ko-KR</td>
+ <td>1</td>
+ <td>1</td>
+ <td>2</td>
+ <td>2</td>
+ </tr>
+
+ <tr>
+ <td>Panjabi</td>
+ <td>pa-IN</td>
+ <td>1</td>
+ <td>2</td>
+ <td>2</td>
+ <td>2</td>
+ </tr>
+
+ <tr>
+ <td>Slovak</td>
+ <td>sk-SK</td>
+ <td>1</td>
+ <td>1</td>
+ <td>2</td>
+ <td>2</td>
+ </tr>
+
+ <tr>
+ <td>Bosnian</td>
+ <td>bs-BA</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ </tr>
+
+ <tr>
+ <td>Hebrew</td>
+ <td>he-IL</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ </tr>
+
+ <tr>
+ <td>Romanian</td>
+ <td>ro</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ </tr>
+
+ <tr>
+ <td>Tamil</td>
+ <td>ta-IN</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ </tr>
+
+</table>
+<div class="totals">
+ <b>Total Languages: </b>43<br />
+ <b>Total Packages: </b>674
+</div>
+</body>
+</html>
+
diff --git a/public_html/ro/opds-Fedora.xml b/public_html/ro/opds-Fedora.xml
new file mode 100644
index 0000000..a1fd06f
--- /dev/null
+++ b/public_html/ro/opds-Fedora.xml
@@ -0,0 +1,1257 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<feed xmlns="http://www.w3.org/2005/Atom"
+ xmlns:dc="http://purl.org/dc/terms/"
+ xmlns:opds="http://opds-spec.org/2010/catalog">
+ <link rel="self" href="http://docs.fedoraproject.org/ro/opds-Fedora.xml" type="application/atom+xml;type=feed;profile=opds-catalog"/>
+ <id>http://docs.fedoraproject.org/ro/opds-Fedora.xml</id>
+ <title>Fedora</title>
+ <subtitle>Fedora</subtitle>
+ <updated>2011-08-22T23:04:52</updated>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+
+ <entry>
+ <title>FreeIPA Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/15/epub/FreeIPA_Guide/Fedora-15-FreeIPA_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2011-07-22</updated>
+ <dc:language>ro</dc:language>
+ <category label="15" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Managing Identity and Authorization Policies for Linux-Based Enterprise Networks
+</summary>
+ <content type="text">Identity and policy management — for both users and machines — is a core function for almost any enterprise environment. IPA provides a way to create an identity domain that allows machines to enroll to a domain and immediately access identity information reuqired for single sign-on and authentication services, as well as policy settings that govern authorization and access. This manual covers all aspects of installing, configuring, and managing IPA domains, including both servers and clients. This guide is intended for IT and systems administrators.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/15/epub/FreeIPA_Guide/Fedora-15-FreeIPA_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
+ <title>Release Notes</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/15/epub/Release_Notes/Fedora-15-Release_Notes-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2011-06-04</updated>
+ <dc:language>ro</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Release Notes for Fedora 15
+</summary>
+ <content type="text">This document details the release notes for Fedora 15.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/15/epub/Release_Notes/Fedora-15-Release_Notes-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
+ <title>Technical Notes</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/15/epub/Technical_Notes/Fedora-15-Technical_Notes-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2011-06-12</updated>
+ <dc:language>ro</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>All changes in Fedora 15
+</summary>
+ <content type="text">This document lists all changed packages between Fedora 14 and Fedora 15. The packages are listed according to their RPM group. There is a complete index at the end to permit the reader to locate a specific package by name.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/15/epub/Technical_Notes/Fedora-15-Technical_Notes-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
+ <title>Accessibility Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/14/epub/Accessibility_Guide/Fedora-14-Accessibility_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-11-02</updated>
+ <dc:language>ro</dc:language>
+ <category label="14" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Using Fedora with a visual, hearing, or mobility impairment
+</summary>
+ <content type="text">This document describes some of the hardware devices, applications, and utilities available to assist people with disabilities to use a computer with the Fedora operating system.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/14/epub/Accessibility_Guide/Fedora-14-Accessibility_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
+ <title>Amateur Radio Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/14/epub/Amateur_Radio_Guide/Fedora-14-Amateur_Radio_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-11-18</updated>
+ <dc:language>ro</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>A guide for users of Fedora amateur radio software
+</summary>
+ <content type="text">Fedora includes a wide range of applications relevant to amateur radio operators. This guide describes the use of some of those applications</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/14/epub/Amateur_Radio_Guide/Fedora-14-Amateur_Radio_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
+ <title>Burning ISO images to disc</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/14/epub/Burning_ISO_images_to_disc/Fedora-14-Burning_ISO_images_to_disc-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-11-01</updated>
+ <dc:language>ro</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>How to download ISO images and create CD and DVD media
+</summary>
+ <content type="text">How to download ISO images and create CD and DVD media</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/14/epub/Burning_ISO_images_to_disc/Fedora-14-Burning_ISO_images_to_disc-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
+ <title>Deployment Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2011-01-28</updated>
+ <dc:language>ro</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Deployment, configuration and administration of Fedora 14
+</summary>
+ <content type="text">The Deployment Guide documents relevant information regarding the deployment, configuration and administration of Fedora 14.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
+ <title>Fedora Live Images</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/14/epub/Fedora_Live_Images/Fedora-14-Fedora_Live_Images-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-10-20</updated>
+ <dc:language>ro</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>How to use the Fedora live image
+</summary>
+ <content type="text">How to use the Fedora live image</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/14/epub/Fedora_Live_Images/Fedora-14-Fedora_Live_Images-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
+ <title>Installation Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/14/epub/Installation_Guide/Fedora-14-Installation_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-10-27</updated>
+ <dc:language>ro</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Installing Fedora 14 on x86, AMD64, and Intel 64 architectures
+</summary>
+ <content type="text">Provides documentation for the installation process.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/14/epub/Installation_Guide/Fedora-14-Installation_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
+ <title>Musicians Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/14/epub/Musicians_Guide/Fedora-14-Musicians_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-11-02</updated>
+ <dc:language>ro</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>A guide to Fedora Linux's audio creation and music capabilities.
+</summary>
+ <content type="text">This document explores some audio-creation and music activities possible with Fedora Linux. Computer audio concepts are explained, and a selection of programs are demonstrated with tutorials showing typical usage.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/14/epub/Musicians_Guide/Fedora-14-Musicians_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
+ <title>Power Management Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/14/epub/Power_Management_Guide/Fedora-14-Power_Management_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-11-01</updated>
+ <dc:language>ro</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Managing power consumption on Fedora
+</summary>
+ <content type="text">This document explains how to manage power consumption on Fedora 14 systems effectively. The following sections discuss different techniques that lower power consumption (for both server and laptop), and how each technique affects the overall performance of your system. Please note: This document is still under development, is subject to heavy change, and is provided here as a preview. The content and instructions contained within should not be considered complete, and should be used with caution.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/14/epub/Power_Management_Guide/Fedora-14-Power_Management_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
+ <title>Release Notes</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/14/epub/Release_Notes/Fedora-14-Release_Notes-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-11-16</updated>
+ <dc:language>ro</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Release Notes for Fedora 14
+</summary>
+ <content type="text">This document details the release notes for Fedora 14.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/14/epub/Release_Notes/Fedora-14-Release_Notes-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
+ <title>Security Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/14/epub/Security_Guide/Fedora-14-Security_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-11-02</updated>
+ <dc:language>ro</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>A Guide to Securing Fedora Linux
+</summary>
+ <content type="text">The Fedora Security Guide is designed to assist users of Fedora in learning the processes and practices of securing workstations and servers against local and remote intrusion, exploitation, and malicious activity. Focused on Fedora Linux but detailing concepts and techniques valid for all Linux systems, the Fedora Security Guide details the planning and the tools involved in creating a secured computing environment for the data center, workplace, and home. With proper administrative knowledge, vigilance, and tools, systems running Linux can be both fully functional and secured from most common intrusion and exploit methods.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/14/epub/Security_Guide/Fedora-14-Security_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
+ <title>Software Management Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/14/epub/Software_Management_Guide/Fedora-14-Software_Management_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2011-01-14</updated>
+ <dc:language>ro</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>The definitive guide for software management
+</summary>
+ <content type="text">This manual is dedicated to software management in Fedora. The reader will learn the skills necessary to be able to install, remove, and update software in his or her system. This manual is designed for all technical levels: from users of Fedora desktop, to system administrators and Fedora developers.\n</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/14/epub/Software_Management_Guide/Fedora-14-Software_Management_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
+ <title>Storage Administration Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/14/epub/Storage_Administration_Guide/Fedora-14-Storage_Administration_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-11-01</updated>
+ <dc:language>ro</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Deploying and configuring single-node storage in Fedora
+</summary>
+ <content type="text">This guide provides instructions on how to effectively manage storage devices and file systems on Fedora 14 and later. It is intended for use by system administrators with basic to intermediate knowledge of Red Hat Enterprise Linux or Fedora.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/14/epub/Storage_Administration_Guide/Fedora-14-Storage_Administration_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
+ <title>User Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/14/epub/User_Guide/Fedora-14-User_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-10-31</updated>
+ <dc:language>ro</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Using Fedora 14 for common desktop computing tasks
+</summary>
+ <content type="text">The Fedora User Guide is focused on the end-user looking to accomplish standard desktop computer user tasks, such as browsing the web, reading and sending email, and doing office productivity work.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/14/epub/User_Guide/Fedora-14-User_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
+ <title>Accessibility Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/13/epub/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-07-23</updated>
+ <dc:language>ro</dc:language>
+ <category label="13" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary></summary>
+ <content type="text"></content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/13/epub/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
+ <title>Burning ISO images to disc</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/13/epub/Burning_ISO_images_to_disc/Fedora-13-Burning_ISO_images_to_disc-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-07-23</updated>
+ <dc:language>ro</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary></summary>
+ <content type="text"></content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/13/epub/Burning_ISO_images_to_disc/Fedora-13-Burning_ISO_images_to_disc-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
+ <title>Fedora Live Images</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/13/epub/Fedora_Live_Images/Fedora-13-Fedora_Live_Images-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-07-27</updated>
+ <dc:language>ro</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary></summary>
+ <content type="text"></content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/13/epub/Fedora_Live_Images/Fedora-13-Fedora_Live_Images-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
+ <title>Installation Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/13/epub/Installation_Guide/Fedora-13-Installation_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-05-22</updated>
+ <dc:language>ro</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary></summary>
+ <content type="text"></content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/13/epub/Installation_Guide/Fedora-13-Installation_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
+ <title>Installation Quick Start Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/13/epub/Installation_Quick_Start_Guide/Fedora-13-Installation_Quick_Start_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-05-22</updated>
+ <dc:language>ro</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary></summary>
+ <content type="text"></content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/13/epub/Installation_Quick_Start_Guide/Fedora-13-Installation_Quick_Start_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
+ <title>Managing Confined Services</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/13/epub/Managing_Confined_Services/Fedora-13-Managing_Confined_Services-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-05-22</updated>
+ <dc:language>ro</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary></summary>
+ <content type="text"></content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/13/epub/Managing_Confined_Services/Fedora-13-Managing_Confined_Services-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
+ <title>Release Notes</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/13/epub/Release_Notes/Fedora-13-Release_Notes-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-05-22</updated>
+ <dc:language>ro</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary></summary>
+ <content type="text"></content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/13/epub/Release_Notes/Fedora-13-Release_Notes-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
+ <title>SELinux FAQ</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/13/epub/SELinux_FAQ/Fedora-13-SELinux_FAQ-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-11-10</updated>
+ <dc:language>ro</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Frequently-asked questions about Security Enhanced Linux
+</summary>
+ <content type="text">This FAQ answers many questions about Security-Enhanced Linux. The information in this FAQ is valuable for those who are new to SELinux. This FAQ is, however, not designed to provide full coverage of SELinux. For detailed guides and instructions on understanding and using SELinux, please read the SELinux User Guide and Managing Confined Services Guide first. They are available at http://docs.fedoraproject.org</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/13/epub/SELinux_FAQ/Fedora-13-SELinux_FAQ-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
+ <title>Security-Enhanced Linux</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/13/epub/Security-Enhanced_Linux/Fedora-13-Security-Enhanced_Linux-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-05-22</updated>
+ <dc:language>ro</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary></summary>
+ <content type="text"></content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/13/epub/Security-Enhanced_Linux/Fedora-13-Security-Enhanced_Linux-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
+ <title>Security Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/13/epub/Security_Guide/Fedora-13-Security_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-07-23</updated>
+ <dc:language>ro</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary></summary>
+ <content type="text"></content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/13/epub/Security_Guide/Fedora-13-Security_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
+ <title>Technical Notes</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/13/epub/Technical_Notes/Fedora-13-Technical_Notes-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-05-22</updated>
+ <dc:language>ro</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary></summary>
+ <content type="text"></content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/13/epub/Technical_Notes/Fedora-13-Technical_Notes-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
+ <title>User Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/13/epub/User_Guide/Fedora-13-User_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-05-22</updated>
+ <dc:language>ro</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary></summary>
+ <content type="text"></content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/13/epub/User_Guide/Fedora-13-User_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
+ <title>Virtualization Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/13/epub/Virtualization_Guide/Fedora-13-Virtualization_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-05-22</updated>
+ <dc:language>ro</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary></summary>
+ <content type="text"></content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/13/epub/Virtualization_Guide/Fedora-13-Virtualization_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
+ <title>Wireless Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/13/epub/Wireless_Guide/Fedora-13-Wireless_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-05-22</updated>
+ <dc:language>ro</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary></summary>
+ <content type="text"></content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/13/epub/Wireless_Guide/Fedora-13-Wireless_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
+ <title>Accessibility Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/12/epub/Accessibility_Guide/Fedora-12-Accessibility_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-05-22</updated>
+ <dc:language>ro</dc:language>
+ <category label="12" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary></summary>
+ <content type="text"></content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/12/epub/Accessibility_Guide/Fedora-12-Accessibility_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
+ <title>Burning ISO images to disc</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/12/epub/Burning_ISO_images_to_disc/Fedora-12-Burning_ISO_images_to_disc-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-05-22</updated>
+ <dc:language>ro</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary></summary>
+ <content type="text"></content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/12/epub/Burning_ISO_images_to_disc/Fedora-12-Burning_ISO_images_to_disc-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
+ <title>Deployment Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/12/epub/Deployment_Guide/Fedora-12-Deployment_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-05-22</updated>
+ <dc:language>ro</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary></summary>
+ <content type="text"></content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/12/epub/Deployment_Guide/Fedora-12-Deployment_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
+ <title>Fedora Live images</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/12/epub/Fedora_Live_images/Fedora-12-Fedora_Live_images-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-05-22</updated>
+ <dc:language>ro</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary></summary>
+ <content type="text"></content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/12/epub/Fedora_Live_images/Fedora-12-Fedora_Live_images-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
+ <title>Installation Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/12/epub/Installation_Guide/Fedora-12-Installation_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-05-22</updated>
+ <dc:language>ro</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary></summary>
+ <content type="text"></content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/12/epub/Installation_Guide/Fedora-12-Installation_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
+ <title>Installation Quick Start Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/12/epub/Installation_Quick_Start_Guide/Fedora-12-Installation_Quick_Start_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-05-22</updated>
+ <dc:language>ro</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary></summary>
+ <content type="text"></content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/12/epub/Installation_Quick_Start_Guide/Fedora-12-Installation_Quick_Start_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
+ <title>Managing Confined Services</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/12/epub/Managing_Confined_Services/Fedora-12-Managing_Confined_Services-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-05-22</updated>
+ <dc:language>ro</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary></summary>
+ <content type="text"></content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/12/epub/Managing_Confined_Services/Fedora-12-Managing_Confined_Services-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
+ <title>Release Notes</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/12/epub/Release_Notes/Fedora-12-Release_Notes-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-05-22</updated>
+ <dc:language>ro</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary></summary>
+ <content type="text"></content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/12/epub/Release_Notes/Fedora-12-Release_Notes-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
+ <title>Security-Enhanced Linux</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/12/epub/Security-Enhanced_Linux/Fedora-12-Security-Enhanced_Linux-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-05-22</updated>
+ <dc:language>ro</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary></summary>
+ <content type="text"></content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/12/epub/Security-Enhanced_Linux/Fedora-12-Security-Enhanced_Linux-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
+ <title>Security Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/12/epub/Security_Guide/Fedora-12-Security_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-05-22</updated>
+ <dc:language>ro</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary></summary>
+ <content type="text"></content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/12/epub/Security_Guide/Fedora-12-Security_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
+ <title>User Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/12/epub/User_Guide/Fedora-12-User_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-05-22</updated>
+ <dc:language>ro</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary></summary>
+ <content type="text"></content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/12/epub/User_Guide/Fedora-12-User_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
+ <title>Virtualization Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/12/epub/Virtualization_Guide/Fedora-12-Virtualization_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-05-22</updated>
+ <dc:language>ro</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary></summary>
+ <content type="text"></content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/12/epub/Virtualization_Guide/Fedora-12-Virtualization_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
+ <title>Wireless Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/12/epub/Wireless_Guide/Fedora-12-Wireless_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-05-22</updated>
+ <dc:language>ro</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary></summary>
+ <content type="text"></content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/12/epub/Wireless_Guide/Fedora-12-Wireless_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
+ <title>Burning ISO images to disc</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/11/epub/Burning_ISO_images_to_disc/Fedora-11-Burning_ISO_images_to_disc-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2009-11-17</updated>
+ <dc:language>ro</dc:language>
+ <category label="11" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary></summary>
+ <content type="text"></content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/11/epub/Burning_ISO_images_to_disc/Fedora-11-Burning_ISO_images_to_disc-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
+ <title>Fedora Live images</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/11/epub/Fedora_Live_images/Fedora-11-Fedora_Live_images-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2009-11-17</updated>
+ <dc:language>ro</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary></summary>
+ <content type="text"></content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/11/epub/Fedora_Live_images/Fedora-11-Fedora_Live_images-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
+ <title>Installation Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/11/epub/Installation_Guide/Fedora-11-Installation_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2009-11-17</updated>
+ <dc:language>ro</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary></summary>
+ <content type="text"></content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/11/epub/Installation_Guide/Fedora-11-Installation_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
+ <title>Installation Quick Start Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/11/epub/Installation_Quick_Start_Guide/Fedora-11-Installation_Quick_Start_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2009-11-17</updated>
+ <dc:language>ro</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary></summary>
+ <content type="text"></content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/11/epub/Installation_Quick_Start_Guide/Fedora-11-Installation_Quick_Start_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
+ <title>Release Notes</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/11/epub/Release_Notes/Fedora-11-Release_Notes-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2009-11-17</updated>
+ <dc:language>ro</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary></summary>
+ <content type="text"></content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/11/epub/Release_Notes/Fedora-11-Release_Notes-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
+ <title>Security-Enhanced Linux</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/11/epub/Security-Enhanced_Linux/Fedora-11-Security-Enhanced_Linux-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2009-11-17</updated>
+ <dc:language>ro</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary></summary>
+ <content type="text"></content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/11/epub/Security-Enhanced_Linux/Fedora-11-Security-Enhanced_Linux-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
+ <title>Security Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/11/epub/Security_Guide/Fedora-11-Security_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2009-11-17</updated>
+ <dc:language>ro</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary></summary>
+ <content type="text"></content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/11/epub/Security_Guide/Fedora-11-Security_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
+ <title>User Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/11/epub/User_Guide/Fedora-11-User_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2009-11-17</updated>
+ <dc:language>ro</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary></summary>
+ <content type="text"></content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/11/epub/User_Guide/Fedora-11-User_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
+ <title>Fedora Live Images</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/10/epub/Fedora_Live_Images/Fedora-10-Fedora_Live_Images-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2009-06-08</updated>
+ <dc:language>ro</dc:language>
+ <category label="10" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary></summary>
+ <content type="text"></content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/10/epub/Fedora_Live_Images/Fedora-10-Fedora_Live_Images-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
+ <title>Installation Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/10/epub/Installation_Guide/Fedora-10-Installation_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2009-06-08</updated>
+ <dc:language>ro</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary></summary>
+ <content type="text"></content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/10/epub/Installation_Guide/Fedora-10-Installation_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
+ <title>Making Fedora Discs</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/10/epub/Making_Fedora_Discs/Fedora-10-Making_Fedora_Discs-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2009-06-08</updated>
+ <dc:language>ro</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary></summary>
+ <content type="text"></content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/10/epub/Making_Fedora_Discs/Fedora-10-Making_Fedora_Discs-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
+ <title>Release Notes</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/10/epub/Release_Notes/Fedora-10-Release_Notes-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2009-06-08</updated>
+ <dc:language>ro</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary></summary>
+ <content type="text"></content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/10/epub/Release_Notes/Fedora-10-Release_Notes-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
+ <title>Fedora Live Images</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/9/epub/Fedora_Live_Images/Fedora-9-Fedora_Live_Images-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2008-11-24</updated>
+ <dc:language>ro</dc:language>
+ <category label="9" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary></summary>
+ <content type="text"></content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/9/epub/Fedora_Live_Images/Fedora-9-Fedora_Live_Images-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
+ <title>Installation Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/9/epub/Installation_Guide/Fedora-9-Installation_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2008-11-24</updated>
+ <dc:language>ro</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary></summary>
+ <content type="text"></content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/9/epub/Installation_Guide/Fedora-9-Installation_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
+ <title>Making Fedora Discs</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/9/epub/Making_Fedora_Discs/Fedora-9-Making_Fedora_Discs-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2008-11-24</updated>
+ <dc:language>ro</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary></summary>
+ <content type="text"></content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/9/epub/Making_Fedora_Discs/Fedora-9-Making_Fedora_Discs-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
+ <title>Release Notes</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/9/epub/Release_Notes/Fedora-9-Release_Notes-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2008-11-24</updated>
+ <dc:language>ro</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary></summary>
+ <content type="text"></content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/9/epub/Release_Notes/Fedora-9-Release_Notes-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
+ <title>Fedora Live Images</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/8/epub/Fedora_Live_Images/Fedora-8-Fedora_Live_Images-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2008-05-13</updated>
+ <dc:language>ro</dc:language>
+ <category label="8" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary></summary>
+ <content type="text"></content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/8/epub/Fedora_Live_Images/Fedora-8-Fedora_Live_Images-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
+ <title>Installation Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/8/epub/Installation_Guide/Fedora-8-Installation_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2008-05-13</updated>
+ <dc:language>ro</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary></summary>
+ <content type="text"></content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/8/epub/Installation_Guide/Fedora-8-Installation_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
+ <title>Making Fedora Discs</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/8/epub/Making_Fedora_Discs/Fedora-8-Making_Fedora_Discs-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2008-05-13</updated>
+ <dc:language>ro</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary></summary>
+ <content type="text"></content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/8/epub/Making_Fedora_Discs/Fedora-8-Making_Fedora_Discs-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
+ <title>Release Notes</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/8/epub/Release_Notes/Fedora-8-Release_Notes-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2008-05-13</updated>
+ <dc:language>ro</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary></summary>
+ <content type="text"></content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/8/epub/Release_Notes/Fedora-8-Release_Notes-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
+ <title>SELinux FAQ</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/8/epub/SELinux_FAQ/Fedora-8-SELinux_FAQ-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2008-05-13</updated>
+ <dc:language>ro</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary></summary>
+ <content type="text"></content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/8/epub/SELinux_FAQ/Fedora-8-SELinux_FAQ-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
+ <title>Installation Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/7/epub/Installation_Guide/Fedora-7-Installation_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2007-11-07</updated>
+ <dc:language>ro</dc:language>
+ <category label="7" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary></summary>
+ <content type="text"></content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/7/epub/Installation_Guide/Fedora-7-Installation_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
+ <title>Making Fedora Discs</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/7/epub/Making_Fedora_Discs/Fedora-7-Making_Fedora_Discs-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2007-11-07</updated>
+ <dc:language>ro</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary></summary>
+ <content type="text"></content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/7/epub/Making_Fedora_Discs/Fedora-7-Making_Fedora_Discs-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
+ <title>Release Notes</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/7/epub/Release_Notes/Fedora-7-Release_Notes-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2007-11-07</updated>
+ <dc:language>ro</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary></summary>
+ <content type="text"></content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/7/epub/Release_Notes/Fedora-7-Release_Notes-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
+ <title>Amateur Radio Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/0.1/epub/Amateur_Radio_Guide/Fedora-0.1-Amateur_Radio_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-11-16</updated>
+ <dc:language>ro</dc:language>
+ <category label="0.1" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>A guide for users of Fedora amateur radio software
+</summary>
+ <content type="text">Fedora includes a wide range of applications relevant to amateur radio operators. This guide describes the use of some of those applications</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/0.1/epub/Amateur_Radio_Guide/Fedora-0.1-Amateur_Radio_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+</feed>
diff --git a/public_html/ro/opds-Fedora_Contributor_Documentation.xml b/public_html/ro/opds-Fedora_Contributor_Documentation.xml
new file mode 100644
index 0000000..6e649b4
--- /dev/null
+++ b/public_html/ro/opds-Fedora_Contributor_Documentation.xml
@@ -0,0 +1,73 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<feed xmlns="http://www.w3.org/2005/Atom"
+ xmlns:dc="http://purl.org/dc/terms/"
+ xmlns:opds="http://opds-spec.org/2010/catalog">
+ <link rel="self" href="http://docs.fedoraproject.org/ro/opds-Fedora_Contributor_Documentation.xml" type="application/atom+xml;type=feed;profile=opds-catalog"/>
+ <id>http://docs.fedoraproject.org/ro/opds-Fedora_Contributor_Documentation.xml</id>
+ <title>Fedora Contributor Documentation</title>
+ <subtitle>Fedora Contributor Documentation</subtitle>
+ <updated>2011-08-22T23:04:52</updated>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+
+ <entry>
+ <title>Fedora Elections Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-11-23</updated>
+ <dc:language>ro</dc:language>
+ <category label="1" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Fedora Elections Guide
+</summary>
+ <content type="text">This book covers procedural information for the use the Fedora Elections software</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
+ <title>Translation Quick Start Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Translation_Quick_Start_Guide/Fedora_Contributor_Documentation-1-Translation_Quick_Start_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-11-02</updated>
+ <dc:language>ro</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Quick start guide to providing translations on the Fedora Project
+</summary>
+ <content type="text">This guide is a fast, simple, step-by-step set of instructions for translating Fedora Project software and documents.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Translation_Quick_Start_Guide/Fedora_Contributor_Documentation-1-Translation_Quick_Start_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
+ <title>Publican Users Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-07-07</updated>
+ <dc:language>ro</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary></summary>
+ <content type="text"></content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <link type="image/png" rel="http://opds-spec.org/image/thumbnail" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/html/Users_Guide/images/cover_thumbnail.png"/>
+ <link type="image/png" rel="http://opds-spec.org/cover" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/html/Users_Guide/images/cover_thumbnail.png"/>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+</feed>
diff --git a/public_html/ro/opds-Fedora_Core.xml b/public_html/ro/opds-Fedora_Core.xml
new file mode 100644
index 0000000..12f8f66
--- /dev/null
+++ b/public_html/ro/opds-Fedora_Core.xml
@@ -0,0 +1,195 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<feed xmlns="http://www.w3.org/2005/Atom"
+ xmlns:dc="http://purl.org/dc/terms/"
+ xmlns:opds="http://opds-spec.org/2010/catalog">
+ <link rel="self" href="http://docs.fedoraproject.org/ro/opds-Fedora_Core.xml" type="application/atom+xml;type=feed;profile=opds-catalog"/>
+ <id>http://docs.fedoraproject.org/ro/opds-Fedora_Core.xml</id>
+ <title>Fedora Core</title>
+ <subtitle>Fedora Core</subtitle>
+ <updated>2011-08-22T23:04:52</updated>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+
+ <entry>
+ <title>Installation Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Core/6/epub/Installation_Guide/Fedora_Core-6-Installation_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2007-05-30</updated>
+ <dc:language>ro</dc:language>
+ <category label="6" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary></summary>
+ <content type="text"></content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Core/6/epub/Installation_Guide/Fedora_Core-6-Installation_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
+ <title>Making Fedora Discs</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Core/6/epub/Making_Fedora_Discs/Fedora_Core-6-Making_Fedora_Discs-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2007-05-30</updated>
+ <dc:language>ro</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary></summary>
+ <content type="text"></content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Core/6/epub/Making_Fedora_Discs/Fedora_Core-6-Making_Fedora_Discs-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
+ <title>Release Notes</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Core/6/epub/Release_Notes/Fedora_Core-6-Release_Notes-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2007-05-30</updated>
+ <dc:language>ro</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary></summary>
+ <content type="text"></content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Core/6/epub/Release_Notes/Fedora_Core-6-Release_Notes-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
+ <title>User Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Core/6/epub/User_Guide/Fedora_Core-6-User_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2007-05-30</updated>
+ <dc:language>ro</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary></summary>
+ <content type="text"></content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Core/6/epub/User_Guide/Fedora_Core-6-User_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
+ <title>Installation Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Core/5/epub/Installation_Guide/Fedora_Core-5-Installation_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2006-10-23</updated>
+ <dc:language>ro</dc:language>
+ <category label="5" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary></summary>
+ <content type="text"></content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Core/5/epub/Installation_Guide/Fedora_Core-5-Installation_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
+ <title>Release Notes</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Core/5/epub/Release_Notes/Fedora_Core-5-Release_Notes-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2006-10-23</updated>
+ <dc:language>ro</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary></summary>
+ <content type="text"></content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Core/5/epub/Release_Notes/Fedora_Core-5-Release_Notes-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
+ <title>SELinux FAQ</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Core/5/epub/SELinux_FAQ/Fedora_Core-5-SELinux_FAQ-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2006-10-23</updated>
+ <dc:language>ro</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary></summary>
+ <content type="text"></content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Core/5/epub/SELinux_FAQ/Fedora_Core-5-SELinux_FAQ-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
+ <title>Software Management Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Core/5/epub/Software_Management_Guide/Fedora_Core-5-Software_Management_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-06-06</updated>
+ <dc:language>ro</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary></summary>
+ <content type="text"></content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Core/5/epub/Software_Management_Guide/Fedora_Core-5-Software_Management_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
+ <title>Software Management Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Core/4/epub/Software_Management_Guide/Fedora_Core-4-Software_Management_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-06-06</updated>
+ <dc:language>ro</dc:language>
+ <category label="4" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary></summary>
+ <content type="text"></content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Core/4/epub/Software_Management_Guide/Fedora_Core-4-Software_Management_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
+ <title>Software Management Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Core/3/epub/Software_Management_Guide/Fedora_Core-3-Software_Management_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-06-06</updated>
+ <dc:language>ro</dc:language>
+ <category label="3" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary></summary>
+ <content type="text"></content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Core/3/epub/Software_Management_Guide/Fedora_Core-3-Software_Management_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+</feed>
diff --git a/public_html/ro/opds-Fedora_Draft_Documentation.xml b/public_html/ro/opds-Fedora_Draft_Documentation.xml
new file mode 100644
index 0000000..6acc11f
--- /dev/null
+++ b/public_html/ro/opds-Fedora_Draft_Documentation.xml
@@ -0,0 +1,110 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<feed xmlns="http://www.w3.org/2005/Atom"
+ xmlns:dc="http://purl.org/dc/terms/"
+ xmlns:opds="http://opds-spec.org/2010/catalog">
+ <link rel="self" href="http://docs.fedoraproject.org/ro/opds-Fedora_Draft_Documentation.xml" type="application/atom+xml;type=feed;profile=opds-catalog"/>
+ <id>http://docs.fedoraproject.org/ro/opds-Fedora_Draft_Documentation.xml</id>
+ <title>Schiță Documentație Fedora</title>
+ <subtitle>Schiță Documentație Fedora</subtitle>
+ <updated>2011-08-22T23:04:52</updated>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+
+ <entry>
+ <title>OpenSSH Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.2/epub/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2011-04-03</updated>
+ <dc:language>ro</dc:language>
+ <category label="0.2" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Using and configuring OpenSSH on Fedora
+</summary>
+ <content type="text">The Fedora OpenSSH Guide assists both new and experienced users to understand, use, configure, and secure the OpenSSH implementation of SSH (Secure Shell) in Fedora.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.2/epub/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
+ <title>Amateur Radio Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Amateur_Radio_Guide/Fedora_Draft_Documentation-0.1-Amateur_Radio_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-11-16</updated>
+ <dc:language>ro</dc:language>
+ <category label="0.1" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>A guide for users of Fedora amateur radio software
+</summary>
+ <content type="text">Fedora includes a wide range of applications relevant to amateur radio operators. This guide describes the use of some of those applications</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Amateur_Radio_Guide/Fedora_Draft_Documentation-0.1-Amateur_Radio_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
+ <title>Cloud Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Cloud_Guide/Fedora_Draft_Documentation-0.1-Cloud_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2011-06-23</updated>
+ <dc:language>ro</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Fedora in the cloud.
+</summary>
+ <content type="text">A short overview and summary of the book's subject and purpose, traditionally no more than one paragraph long. Note: the abstract will appear in the front matter of your book and will also be placed in the description field of the book's RPM spec file.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Cloud_Guide/Fedora_Draft_Documentation-0.1-Cloud_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
+ <title>Documentation Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Documentation_Guide/Fedora_Draft_Documentation-0.1-Documentation_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2011-06-13</updated>
+ <dc:language>ro</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>A how-to guide for creating and maintaining documentation for Fedora.
+</summary>
+ <content type="text"></content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Documentation_Guide/Fedora_Draft_Documentation-0.1-Documentation_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
+ <title>Ghid RPM</title>
+ <id>http://docs.fedoraproject.org/ro/Fedora_Draft_Documentation/0.1/epub/RPM_Guide/Fedora_Draft_Documentation-0.1-RPM_Guide-ro.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2011-08-22</updated>
+ <dc:language>ro</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>scurt descriptor
+</summary>
+ <content type="text">O scurtă trecere în revistă și un sumar al subiectului și scopului cărții, în mod tradițional nu mai lung(ă) de un paragraf. Notă: trecerea în revistă va apărea pe prima pagină a cărții și în câmpul #description al fișierului spec aparținând RPM-ului cărții</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/ro/Fedora_Draft_Documentation/0.1/epub/RPM_Guide/Fedora_Draft_Documentation-0.1-RPM_Guide-ro.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+</feed>
diff --git a/public_html/ro/opds.xml b/public_html/ro/opds.xml
new file mode 100644
index 0000000..2f3869c
--- /dev/null
+++ b/public_html/ro/opds.xml
@@ -0,0 +1,47 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<feed xmlns="http://www.w3.org/2005/Atom"
+ xmlns:dc="http://purl.org/dc/terms/"
+ xmlns:opds="http://opds-spec.org/2010/catalog">
+ <link rel="self" href="http://docs.fedoraproject.org/ro/opds.xml" type="application/atom+xml;type=feed;profile=opds-catalog"/>
+ <link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
+ <id>http://docs.fedoraproject.org/ro/opds.xml</id>
+ <title>Product List</title>
+ <updated>2011-08-22T23:04:52</updated>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+
+ <entry>
+ <title>Fedora</title>
+ <id>http://docs.fedoraproject.org/ro/Fedora/opds-Fedora.xml</id>
+ <updated>2011-08-22T23:04:52</updated>
+ <dc:language>ro</dc:language>
+ <content type="text"></content>
+ <link type="application/atom+xml" href="opds-Fedora.xml"/>
+ </entry>
+ <entry>
+ <title>Fedora Contributor Documentation</title>
+ <id>http://docs.fedoraproject.org/ro/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
+ <updated>2011-08-22T23:04:52</updated>
+ <dc:language>ro</dc:language>
+ <content type="text"></content>
+ <link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
+ </entry>
+ <entry>
+ <title>Fedora Core</title>
+ <id>http://docs.fedoraproject.org/ro/Fedora_Core/opds-Fedora_Core.xml</id>
+ <updated>2011-08-22T23:04:52</updated>
+ <dc:language>ro</dc:language>
+ <content type="text"></content>
+ <link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
+ </entry>
+ <entry>
+ <title>Schiță Documentație Fedora</title>
+ <id>http://docs.fedoraproject.org/ro/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
+ <updated>2011-08-22T23:04:52</updated>
+ <dc:language>ro</dc:language>
+ <content type="text"></content>
+ <link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
+ </entry>
+</feed>
diff --git a/public_html/ro/toc.html b/public_html/ro/toc.html
new file mode 100644
index 0000000..6268fa9
--- /dev/null
+++ b/public_html/ro/toc.html
@@ -0,0 +1,1179 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
+ <link rel="stylesheet" href="../interactive.css" type="text/css" />
+ <script type="text/javascript" src="../toc.js"></script>
+ <title>toc nav</title>
+</head>
+<body class="tocnav" onload="hideNoJS();getCookie();checkCookie();checkMenu();">
+<div id="closemenu" class="closemenu visible">
+ <a href="#" title="Hide Menu" onclick="hideMenu();" ><img src="../images/close.png"/></a>
+</div>
+<div id="openmenu" class="openmenu hidden">
+ <a href="#" title="Show Menu" onclick="showMenu();"><img src="../images/open.png"/></a>
+</div>
+<div id="outer" class="outer visible">
+<h1>
+ <a style="background-image:url(images/web_logo.png)" href="index.html" onclick="window.top.location='index.html'" ><span>Welcome</span></a>
+</h1>
+<div class="tocnavwrap">
+ <p/>
+ <div class="lang">
+ <div class="reset">
+ <a href="#" title="collapse document navigation" onclick="clearCookie();">collapse all</a>
+ </div>
+ <select id="langselect" class="langselect" onchange="loadToc();">
+ <option disabled="disabled" value="">Language</option>
+ <option value="as-IN">অসমীয়া</option>
+ <option value="bg-BG">българÑки</option>
+ <option value="bn-IN">বাংলা</option>
+ <option value="bs-BA">Bosanski</option>
+ <option value="ca-ES">Català </option>
+ <option value="cs-CZ">Čeština</option>
+ <option value="da-DK">Dansk</option>
+ <option value="de-DE">Deutsch</option>
+ <option value="el-GR">Ελληνικά</option>
+ <option value="en-US">English</option>
+ <option value="es-ES">Español</option>
+ <option value="fa-IR">Ùارسی</option>
+ <option value="fi-FI">Suomi</option>
+ <option value="fr-FR">Français</option>
+ <option value="gu-IN">ગà«àªœàª°àª¾àª¤à«€</option>
+ <option value="he-IL">עברית</option>
+ <option value="hi-IN">हिनà¥à¤¦à¥€</option>
+ <option value="hu-HU">Magyar</option>
+ <option value="id-ID">Indonesia</option>
+ <option value="it-IT">Italiano</option>
+ <option value="ja-JP">日本語</option>
+ <option value="kn-IN">ಕನà³à²¨à²¡</option>
+ <option value="ko-KR">í•œêµì–´</option>
+ <option value="ml-IN">മലയാളം</option>
+ <option value="mr-IN">मराठी</option>
+ <option value="nb-NO">Norsk (bokmål)</option>
+ <option value="nl-NL">Nederlands</option>
+ <option value="or-IN">ଓଡ଼ିଆ</option>
+ <option value="pa-IN">ਪੰਜਾਬੀ</option>
+ <option value="pl-PL">Polski</option>
+ <option value="pt-BR">Português Brasileiro</option>
+ <option value="pt-PT">Português</option>
+ <option selected="selected" value="ro">Romanian</option>
+ <option value="ru-RU">РуÑÑкий</option>
+ <option value="sk-SK">SlovenÅ¡Äina</option>
+ <option value="sr-Latn-RS">Srpski (latinica)</option>
+ <option value="sr-RS">СрпÑки</option>
+ <option value="sv-SE">Svenska</option>
+ <option value="ta-IN">தமிழà¯</option>
+ <option value="te-IN">తెలà±à°—à±</option>
+ <option value="uk-UA">УкраїнÑька</option>
+ <option value="zh-CN">简体ä¸æ–‡</option>
+ <option value="zh-TW">ç¹é«”ä¸æ–‡</option>
+ </select>
+ </div>
+ <div class="hidden" id="nocookie">
+ The Navigation Menu below will automatically collapse when pages are loaded. Enable cookies to fix the Navigation Menu functionality.
+ </div>
+ <div class="product collapsed" onclick="toggle(event, 'Fedora');work=1;">
+ <span class="product">Fedora</span>
+ <div id='Fedora' class="versions hidden">
+ <div id='Fedora.15' class="version collapsed" onclick="toggle(event, 'Fedora.15.books');">
+ <span class="version">15</span>
+ <div id='Fedora.15.books' class="books hidden">
+ <div id='Fedora.15' class="version collapsed untranslated" onclick="toggle(event, 'Fedora.15.untrans_books');">
+ <span class="version">Untranslated</span>
+ <div id='Fedora.15.untrans_books' class="books hidden">
+ <div id='Fedora.15.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.15.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora/15/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora/15/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora.15.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/15/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/15/html/Deployment_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/15/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/15/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ <div id='Fedora.15.Fedora_Live_Images' class="book collapsed" onclick="toggle(event, 'Fedora.15.Fedora_Live_Images.types');">
+ <a class="type" href="../en-US/Fedora/15/html/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/Fedora/15/html/Fedora_Live_Images/index.html'"><span class="book">Fedora Live Images</span></a>
+ <div id='Fedora.15.Fedora_Live_Images.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/15/html/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/15/html/Fedora_Live_Images/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/15/html-single/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/15/html-single/Fedora_Live_Images/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/15/pdf/Fedora_Live_Images/" onclick="window.top.location='../en-US/./Fedora/15/pdf/Fedora_Live_Images/';return false;">pdf</a>
+ </div>
+ </div>
+ <div id='Fedora.15.FreeIPA_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.15.FreeIPA_Guide.types');">
+ <a class="type" href="../en-US/Fedora/15/html/FreeIPA_Guide/index.html" onclick="window.top.location='../en-US/Fedora/15/html/FreeIPA_Guide/index.html'"><span class="book">FreeIPA Guide</span></a>
+ <div id='Fedora.15.FreeIPA_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/15/epub/FreeIPA_Guide/Fedora-15-FreeIPA_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/15/html/FreeIPA_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/15/html/FreeIPA_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/15/html-single/FreeIPA_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/15/html-single/FreeIPA_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/15/pdf/FreeIPA_Guide/Fedora-15-FreeIPA_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/15/pdf/FreeIPA_Guide/Fedora-15-FreeIPA_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ <div id='Fedora.15.Installation_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.15.Installation_Guide.types');">
+ <a class="type" href="../en-US/Fedora/15/html/Installation_Guide/index.html" onclick="window.top.location='../en-US/Fedora/15/html/Installation_Guide/index.html'"><span class="book">Installation Guide</span></a>
+ <div id='Fedora.15.Installation_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/15/html/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/15/html/Installation_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/15/html-single/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/15/html-single/Installation_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ <div id='Fedora.15.Musicians_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.15.Musicians_Guide.types');">
+ <a class="type" href="../en-US/Fedora/15/html/Musicians_Guide/index.html" onclick="window.top.location='../en-US/Fedora/15/html/Musicians_Guide/index.html'"><span class="book">Musicians Guide</span></a>
+ <div id='Fedora.15.Musicians_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/15/html/Musicians_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/15/html/Musicians_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/15/html-single/Musicians_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/15/html-single/Musicians_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/15/pdf/Musicians_Guide/Fedora-15-Musicians_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/15/pdf/Musicians_Guide/Fedora-15-Musicians_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ <div id='Fedora.15.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.15.Release_Notes.types');">
+ <a class="type" href="../en-US/Fedora/15/html/Release_Notes/index.html" onclick="window.top.location='../en-US/Fedora/15/html/Release_Notes/index.html'"><span class="book">Release Notes</span></a>
+ <div id='Fedora.15.Release_Notes.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/15/epub/Release_Notes/Fedora-15-Release_Notes-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/15/html/Release_Notes/index.html" onclick="window.top.location='../en-US/./Fedora/15/html/Release_Notes/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/15/html-single/Release_Notes/index.html" onclick="window.top.location='../en-US/./Fedora/15/html-single/Release_Notes/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/15/pdf/Release_Notes/Fedora-15-Release_Notes-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/15/pdf/Release_Notes/Fedora-15-Release_Notes-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ <div id='Fedora.15.Resource_Management_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.15.Resource_Management_Guide.types');">
+ <a class="type" href="../en-US/Fedora/15/html/Resource_Management_Guide/index.html" onclick="window.top.location='../en-US/Fedora/15/html/Resource_Management_Guide/index.html'"><span class="book">Resource Management Guide</span></a>
+ <div id='Fedora.15.Resource_Management_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/15/html/Resource_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/15/html/Resource_Management_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/15/html-single/Resource_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/15/html-single/Resource_Management_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/15/pdf/Resource_Management_Guide/Fedora-15-Resource_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/15/pdf/Resource_Management_Guide/Fedora-15-Resource_Management_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ <div id='Fedora.15.Technical_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.15.Technical_Notes.types');">
+ <a class="type" href="../en-US/Fedora/15/html/Technical_Notes/index.html" onclick="window.top.location='../en-US/Fedora/15/html/Technical_Notes/index.html'"><span class="book">Technical Notes</span></a>
+ <div id='Fedora.15.Technical_Notes.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/15/epub/Technical_Notes/Fedora-15-Technical_Notes-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/15/html/Technical_Notes/index.html" onclick="window.top.location='../en-US/./Fedora/15/html/Technical_Notes/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/15/html-single/Technical_Notes/index.html" onclick="window.top.location='../en-US/./Fedora/15/html-single/Technical_Notes/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/15/pdf/Technical_Notes/Fedora-15-Technical_Notes-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/15/pdf/Technical_Notes/Fedora-15-Technical_Notes-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ </div>
+ </div>
+ </div>
+ </div>
+ <div id='Fedora.14' class="version collapsed" onclick="toggle(event, 'Fedora.14.books');">
+ <span class="version">14</span>
+ <div id='Fedora.14.books' class="books hidden">
+ <div id='Fedora.14' class="version collapsed untranslated" onclick="toggle(event, 'Fedora.14.untrans_books');">
+ <span class="version">Untranslated</span>
+ <div id='Fedora.14.untrans_books' class="books hidden">
+ <div id='Fedora.14.Accessibility_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.14.Accessibility_Guide.types');">
+ <a class="type" href="../en-US/Fedora/14/html/Accessibility_Guide/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Accessibility_Guide/index.html'"><span class="book">Accessibility Guide</span></a>
+ <div id='Fedora.14.Accessibility_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/14/epub/Accessibility_Guide/Fedora-14-Accessibility_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/14/html/Accessibility_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html/Accessibility_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/14/html-single/Accessibility_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html-single/Accessibility_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/14/pdf/Accessibility_Guide/Fedora-14-Accessibility_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Accessibility_Guide/Fedora-14-Accessibility_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ <div id='Fedora.14.Amateur_Radio_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.14.Amateur_Radio_Guide.types');">
+ <a class="type" href="../en-US/Fedora/14/html/Amateur_Radio_Guide/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Amateur_Radio_Guide/index.html'"><span class="book">Amateur Radio Guide</span></a>
+ <div id='Fedora.14.Amateur_Radio_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/14/epub/Amateur_Radio_Guide/Fedora-14-Amateur_Radio_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/14/html/Amateur_Radio_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html/Amateur_Radio_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/14/html-single/Amateur_Radio_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html-single/Amateur_Radio_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/14/pdf/Amateur_Radio_Guide/Fedora-14-Amateur_Radio_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Amateur_Radio_Guide/Fedora-14-Amateur_Radio_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ <div id='Fedora.14.Burning_ISO_images_to_disc' class="book collapsed" onclick="toggle(event, 'Fedora.14.Burning_ISO_images_to_disc.types');">
+ <a class="type" href="../en-US/Fedora/14/html/Burning_ISO_images_to_disc/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Burning_ISO_images_to_disc/index.html'"><span class="book">Burning ISO images to disc</span></a>
+ <div id='Fedora.14.Burning_ISO_images_to_disc.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/14/epub/Burning_ISO_images_to_disc/Fedora-14-Burning_ISO_images_to_disc-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/14/html/Burning_ISO_images_to_disc/index.html" onclick="window.top.location='../en-US/./Fedora/14/html/Burning_ISO_images_to_disc/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/14/html-single/Burning_ISO_images_to_disc/index.html" onclick="window.top.location='../en-US/./Fedora/14/html-single/Burning_ISO_images_to_disc/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/14/pdf/Burning_ISO_images_to_disc/Fedora-14-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Burning_ISO_images_to_disc/Fedora-14-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ <div id='Fedora.14.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.14.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora.14.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html/Deployment_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/14/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ <div id='Fedora.14.Fedora_Live_Images' class="book collapsed" onclick="toggle(event, 'Fedora.14.Fedora_Live_Images.types');">
+ <a class="type" href="../en-US/Fedora/14/html/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Fedora_Live_Images/index.html'"><span class="book">Fedora Live Images</span></a>
+ <div id='Fedora.14.Fedora_Live_Images.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/14/epub/Fedora_Live_Images/Fedora-14-Fedora_Live_Images-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/14/html/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/14/html/Fedora_Live_Images/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/14/html-single/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/14/html-single/Fedora_Live_Images/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/14/pdf/Fedora_Live_Images/Fedora-14-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Fedora_Live_Images/Fedora-14-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ <div id='Fedora.14.Installation_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.14.Installation_Guide.types');">
+ <a class="type" href="../en-US/Fedora/14/html/Installation_Guide/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Installation_Guide/index.html'"><span class="book">Installation Guide</span></a>
+ <div id='Fedora.14.Installation_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/14/epub/Installation_Guide/Fedora-14-Installation_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/14/html/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html/Installation_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/14/html-single/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html-single/Installation_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/14/pdf/Installation_Guide/Fedora-14-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Installation_Guide/Fedora-14-Installation_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ <div id='Fedora.14.Musicians_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.14.Musicians_Guide.types');">
+ <a class="type" href="../en-US/Fedora/14/html/Musicians_Guide/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Musicians_Guide/index.html'"><span class="book">Musicians Guide</span></a>
+ <div id='Fedora.14.Musicians_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/14/epub/Musicians_Guide/Fedora-14-Musicians_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/14/html/Musicians_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html/Musicians_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/14/html-single/Musicians_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html-single/Musicians_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/14/pdf/Musicians_Guide/Fedora-14-Musicians_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Musicians_Guide/Fedora-14-Musicians_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ <div id='Fedora.14.Power_Management_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.14.Power_Management_Guide.types');">
+ <a class="type" href="../en-US/Fedora/14/html/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Power_Management_Guide/index.html'"><span class="book">Power Management Guide</span></a>
+ <div id='Fedora.14.Power_Management_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/14/epub/Power_Management_Guide/Fedora-14-Power_Management_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/14/html/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html/Power_Management_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/14/html-single/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html-single/Power_Management_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/14/pdf/Power_Management_Guide/Fedora-14-Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Power_Management_Guide/Fedora-14-Power_Management_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ <div id='Fedora.14.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.14.Release_Notes.types');">
+ <a class="type" href="../en-US/Fedora/14/html/Release_Notes/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Release_Notes/index.html'"><span class="book">Release Notes</span></a>
+ <div id='Fedora.14.Release_Notes.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/14/epub/Release_Notes/Fedora-14-Release_Notes-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/14/html/Release_Notes/index.html" onclick="window.top.location='../en-US/./Fedora/14/html/Release_Notes/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/14/html-single/Release_Notes/index.html" onclick="window.top.location='../en-US/./Fedora/14/html-single/Release_Notes/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/14/pdf/Release_Notes/Fedora-14-Release_Notes-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Release_Notes/Fedora-14-Release_Notes-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ <div id='Fedora.14.Security_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.14.Security_Guide.types');">
+ <a class="type" href="../en-US/Fedora/14/html/Security_Guide/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Security_Guide/index.html'"><span class="book">Security Guide</span></a>
+ <div id='Fedora.14.Security_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/14/epub/Security_Guide/Fedora-14-Security_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/14/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html/Security_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/14/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html-single/Security_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/14/pdf/Security_Guide/Fedora-14-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Security_Guide/Fedora-14-Security_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ <div id='Fedora.14.Software_Management_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.14.Software_Management_Guide.types');">
+ <a class="type" href="../en-US/Fedora/14/html/Software_Management_Guide/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Software_Management_Guide/index.html'"><span class="book">Software Management Guide</span></a>
+ <div id='Fedora.14.Software_Management_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/14/epub/Software_Management_Guide/Fedora-14-Software_Management_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/14/html/Software_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html/Software_Management_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/14/html-single/Software_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html-single/Software_Management_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/14/pdf/Software_Management_Guide/Fedora-14-Software_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Software_Management_Guide/Fedora-14-Software_Management_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ <div id='Fedora.14.Storage_Administration_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.14.Storage_Administration_Guide.types');">
+ <a class="type" href="../en-US/Fedora/14/html/Storage_Administration_Guide/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Storage_Administration_Guide/index.html'"><span class="book">Storage Administration Guide</span></a>
+ <div id='Fedora.14.Storage_Administration_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/14/epub/Storage_Administration_Guide/Fedora-14-Storage_Administration_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/14/html/Storage_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html/Storage_Administration_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/14/html-single/Storage_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html-single/Storage_Administration_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/14/pdf/Storage_Administration_Guide/Fedora-14-Storage_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Storage_Administration_Guide/Fedora-14-Storage_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ <div id='Fedora.14.User_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.14.User_Guide.types');">
+ <a class="type" href="../en-US/Fedora/14/html/User_Guide/index.html" onclick="window.top.location='../en-US/Fedora/14/html/User_Guide/index.html'"><span class="book">User Guide</span></a>
+ <div id='Fedora.14.User_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/14/epub/User_Guide/Fedora-14-User_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/14/html/User_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html/User_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/14/html-single/User_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html-single/User_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/14/pdf/User_Guide/Fedora-14-User_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/User_Guide/Fedora-14-User_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ </div>
+ </div>
+ </div>
+ </div>
+ <div id='Fedora.13' class="version collapsed" onclick="toggle(event, 'Fedora.13.books');">
+ <span class="version">13</span>
+ <div id='Fedora.13.books' class="books hidden">
+ <div id='Fedora.13' class="version collapsed untranslated" onclick="toggle(event, 'Fedora.13.untrans_books');">
+ <span class="version">Untranslated</span>
+ <div id='Fedora.13.untrans_books' class="books hidden">
+ <div id='Fedora.13.Accessibility_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.13.Accessibility_Guide.types');">
+ <a class="type" href="../en-US/Fedora/13/html/Accessibility_Guide/index.html" onclick="window.top.location='../en-US/Fedora/13/html/Accessibility_Guide/index.html'"><span class="book">Accessibility Guide</span></a>
+ <div id='Fedora.13.Accessibility_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/13/epub/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/13/html/Accessibility_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/13/html/Accessibility_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/13/html-single/Accessibility_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/13/html-single/Accessibility_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ <div id='Fedora.13.Burning_ISO_images_to_disc' class="book collapsed" onclick="toggle(event, 'Fedora.13.Burning_ISO_images_to_disc.types');">
+ <a class="type" href="../en-US/Fedora/13/html/Burning_ISO_images_to_disc/index.html" onclick="window.top.location='../en-US/Fedora/13/html/Burning_ISO_images_to_disc/index.html'"><span class="book">Burning ISO images to disc</span></a>
+ <div id='Fedora.13.Burning_ISO_images_to_disc.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/13/epub/Burning_ISO_images_to_disc/Fedora-13-Burning_ISO_images_to_disc-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/13/html/Burning_ISO_images_to_disc/index.html" onclick="window.top.location='../en-US/./Fedora/13/html/Burning_ISO_images_to_disc/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/13/html-single/Burning_ISO_images_to_disc/index.html" onclick="window.top.location='../en-US/./Fedora/13/html-single/Burning_ISO_images_to_disc/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/13/pdf/Burning_ISO_images_to_disc/Fedora-13-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/13/pdf/Burning_ISO_images_to_disc/Fedora-13-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ <div id='Fedora.13.Fedora_Live_Images' class="book collapsed" onclick="toggle(event, 'Fedora.13.Fedora_Live_Images.types');">
+ <a class="type" href="../en-US/Fedora/13/html/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/Fedora/13/html/Fedora_Live_Images/index.html'"><span class="book">Fedora Live Images</span></a>
+ <div id='Fedora.13.Fedora_Live_Images.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/13/epub/Fedora_Live_Images/Fedora-13-Fedora_Live_Images-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/13/html/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/13/html/Fedora_Live_Images/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/13/html-single/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/13/html-single/Fedora_Live_Images/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/13/pdf/Fedora_Live_Images/Fedora-13-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/13/pdf/Fedora_Live_Images/Fedora-13-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ <div id='Fedora.13.Installation_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.13.Installation_Guide.types');">
+ <a class="type" href="../en-US/Fedora/13/html/Installation_Guide/index.html" onclick="window.top.location='../en-US/Fedora/13/html/Installation_Guide/index.html'"><span class="book">Installation Guide</span></a>
+ <div id='Fedora.13.Installation_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/13/epub/Installation_Guide/Fedora-13-Installation_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/13/html/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/13/html/Installation_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/13/html-single/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/13/html-single/Installation_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/13/pdf/Installation_Guide/Fedora-13-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/13/pdf/Installation_Guide/Fedora-13-Installation_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ <div id='Fedora.13.Installation_Quick_Start_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.13.Installation_Quick_Start_Guide.types');">
+ <a class="type" href="../en-US/Fedora/13/html/Installation_Quick_Start_Guide/index.html" onclick="window.top.location='../en-US/Fedora/13/html/Installation_Quick_Start_Guide/index.html'"><span class="book">Installation Quick Start Guide</span></a>
+ <div id='Fedora.13.Installation_Quick_Start_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/13/epub/Installation_Quick_Start_Guide/Fedora-13-Installation_Quick_Start_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/13/html/Installation_Quick_Start_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/13/html/Installation_Quick_Start_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/13/html-single/Installation_Quick_Start_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/13/html-single/Installation_Quick_Start_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/13/pdf/Installation_Quick_Start_Guide/Fedora-13-Installation_Quick_Start_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/13/pdf/Installation_Quick_Start_Guide/Fedora-13-Installation_Quick_Start_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ <div id='Fedora.13.Managing_Confined_Services' class="book collapsed" onclick="toggle(event, 'Fedora.13.Managing_Confined_Services.types');">
+ <a class="type" href="../en-US/Fedora/13/html/Managing_Confined_Services/index.html" onclick="window.top.location='../en-US/Fedora/13/html/Managing_Confined_Services/index.html'"><span class="book">Managing Confined Services</span></a>
+ <div id='Fedora.13.Managing_Confined_Services.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/13/epub/Managing_Confined_Services/Fedora-13-Managing_Confined_Services-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/13/html/Managing_Confined_Services/index.html" onclick="window.top.location='../en-US/./Fedora/13/html/Managing_Confined_Services/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/13/html-single/Managing_Confined_Services/index.html" onclick="window.top.location='../en-US/./Fedora/13/html-single/Managing_Confined_Services/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/13/pdf/Managing_Confined_Services/Fedora-13-Managing_Confined_Services-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/13/pdf/Managing_Confined_Services/Fedora-13-Managing_Confined_Services-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ <div id='Fedora.13.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.13.Release_Notes.types');">
+ <a class="type" href="../en-US/Fedora/13/html/Release_Notes/index.html" onclick="window.top.location='../en-US/Fedora/13/html/Release_Notes/index.html'"><span class="book">Release Notes</span></a>
+ <div id='Fedora.13.Release_Notes.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/13/epub/Release_Notes/Fedora-13-Release_Notes-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/13/html/Release_Notes/index.html" onclick="window.top.location='../en-US/./Fedora/13/html/Release_Notes/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/13/html-single/Release_Notes/index.html" onclick="window.top.location='../en-US/./Fedora/13/html-single/Release_Notes/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/13/pdf/Release_Notes/Fedora-13-Release_Notes-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/13/pdf/Release_Notes/Fedora-13-Release_Notes-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ <div id='Fedora.13.SELinux_FAQ' class="book collapsed" onclick="toggle(event, 'Fedora.13.SELinux_FAQ.types');">
+ <a class="type" href="../en-US/Fedora/13/html/SELinux_FAQ/index.html" onclick="window.top.location='../en-US/Fedora/13/html/SELinux_FAQ/index.html'"><span class="book">SELinux FAQ</span></a>
+ <div id='Fedora.13.SELinux_FAQ.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/13/epub/SELinux_FAQ/Fedora-13-SELinux_FAQ-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/13/html/SELinux_FAQ/index.html" onclick="window.top.location='../en-US/./Fedora/13/html/SELinux_FAQ/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/13/html-single/SELinux_FAQ/index.html" onclick="window.top.location='../en-US/./Fedora/13/html-single/SELinux_FAQ/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/13/pdf/SELinux_FAQ/Fedora-13-SELinux_FAQ-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/13/pdf/SELinux_FAQ/Fedora-13-SELinux_FAQ-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ <div id='Fedora.13.Security-Enhanced_Linux' class="book collapsed" onclick="toggle(event, 'Fedora.13.Security-Enhanced_Linux.types');">
+ <a class="type" href="../en-US/Fedora/13/html/Security-Enhanced_Linux/index.html" onclick="window.top.location='../en-US/Fedora/13/html/Security-Enhanced_Linux/index.html'"><span class="book">Security-Enhanced Linux</span></a>
+ <div id='Fedora.13.Security-Enhanced_Linux.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/13/epub/Security-Enhanced_Linux/Fedora-13-Security-Enhanced_Linux-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/13/html/Security-Enhanced_Linux/index.html" onclick="window.top.location='../en-US/./Fedora/13/html/Security-Enhanced_Linux/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/13/html-single/Security-Enhanced_Linux/index.html" onclick="window.top.location='../en-US/./Fedora/13/html-single/Security-Enhanced_Linux/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/13/pdf/Security-Enhanced_Linux/Fedora-13-Security-Enhanced_Linux-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/13/pdf/Security-Enhanced_Linux/Fedora-13-Security-Enhanced_Linux-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ <div id='Fedora.13.Security_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.13.Security_Guide.types');">
+ <a class="type" href="../en-US/Fedora/13/html/Security_Guide/index.html" onclick="window.top.location='../en-US/Fedora/13/html/Security_Guide/index.html'"><span class="book">Security Guide</span></a>
+ <div id='Fedora.13.Security_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/13/epub/Security_Guide/Fedora-13-Security_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/13/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/13/html/Security_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/13/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/13/html-single/Security_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/13/pdf/Security_Guide/Fedora-13-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/13/pdf/Security_Guide/Fedora-13-Security_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ <div id='Fedora.13.Technical_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.13.Technical_Notes.types');">
+ <a class="type" href="../en-US/Fedora/13/html/Technical_Notes/index.html" onclick="window.top.location='../en-US/Fedora/13/html/Technical_Notes/index.html'"><span class="book">Technical Notes</span></a>
+ <div id='Fedora.13.Technical_Notes.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/13/epub/Technical_Notes/Fedora-13-Technical_Notes-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/13/html/Technical_Notes/index.html" onclick="window.top.location='../en-US/./Fedora/13/html/Technical_Notes/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/13/html-single/Technical_Notes/index.html" onclick="window.top.location='../en-US/./Fedora/13/html-single/Technical_Notes/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/13/pdf/Technical_Notes/Fedora-13-Technical_Notes-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/13/pdf/Technical_Notes/Fedora-13-Technical_Notes-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ <div id='Fedora.13.User_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.13.User_Guide.types');">
+ <a class="type" href="../en-US/Fedora/13/html/User_Guide/index.html" onclick="window.top.location='../en-US/Fedora/13/html/User_Guide/index.html'"><span class="book">User Guide</span></a>
+ <div id='Fedora.13.User_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/13/epub/User_Guide/Fedora-13-User_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/13/html/User_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/13/html/User_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/13/html-single/User_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/13/html-single/User_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/13/pdf/User_Guide/Fedora-13-User_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/13/pdf/User_Guide/Fedora-13-User_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ <div id='Fedora.13.Virtualization_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.13.Virtualization_Guide.types');">
+ <a class="type" href="../en-US/Fedora/13/html/Virtualization_Guide/index.html" onclick="window.top.location='../en-US/Fedora/13/html/Virtualization_Guide/index.html'"><span class="book">Virtualization Guide</span></a>
+ <div id='Fedora.13.Virtualization_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/13/epub/Virtualization_Guide/Fedora-13-Virtualization_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/13/html/Virtualization_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/13/html/Virtualization_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/13/html-single/Virtualization_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/13/html-single/Virtualization_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/13/pdf/Virtualization_Guide/Fedora-13-Virtualization_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/13/pdf/Virtualization_Guide/Fedora-13-Virtualization_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ <div id='Fedora.13.Wireless_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.13.Wireless_Guide.types');">
+ <a class="type" href="../en-US/Fedora/13/html/Wireless_Guide/index.html" onclick="window.top.location='../en-US/Fedora/13/html/Wireless_Guide/index.html'"><span class="book">Wireless Guide</span></a>
+ <div id='Fedora.13.Wireless_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/13/epub/Wireless_Guide/Fedora-13-Wireless_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/13/html/Wireless_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/13/html/Wireless_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/13/html-single/Wireless_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/13/html-single/Wireless_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/13/pdf/Wireless_Guide/Fedora-13-Wireless_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/13/pdf/Wireless_Guide/Fedora-13-Wireless_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ </div>
+ </div>
+ </div>
+ </div>
+ <div id='Fedora.12' class="version collapsed" onclick="toggle(event, 'Fedora.12.books');">
+ <span class="version">12</span>
+ <div id='Fedora.12.books' class="books hidden">
+ <div id='Fedora.12' class="version collapsed untranslated" onclick="toggle(event, 'Fedora.12.untrans_books');">
+ <span class="version">Untranslated</span>
+ <div id='Fedora.12.untrans_books' class="books hidden">
+ <div id='Fedora.12.Accessibility_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.12.Accessibility_Guide.types');">
+ <a class="type" href="../en-US/Fedora/12/html/Accessibility_Guide/index.html" onclick="window.top.location='../en-US/Fedora/12/html/Accessibility_Guide/index.html'"><span class="book">Accessibility Guide</span></a>
+ <div id='Fedora.12.Accessibility_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/12/epub/Accessibility_Guide/Fedora-12-Accessibility_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/12/html/Accessibility_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/12/html/Accessibility_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/12/html-single/Accessibility_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/12/html-single/Accessibility_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/12/pdf/Accessibility_Guide/Fedora-12-Accessibility_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/12/pdf/Accessibility_Guide/Fedora-12-Accessibility_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ <div id='Fedora.12.Burning_ISO_images_to_disc' class="book collapsed" onclick="toggle(event, 'Fedora.12.Burning_ISO_images_to_disc.types');">
+ <a class="type" href="../en-US/Fedora/12/html/Burning_ISO_images_to_disc/index.html" onclick="window.top.location='../en-US/Fedora/12/html/Burning_ISO_images_to_disc/index.html'"><span class="book">Burning ISO images to disc</span></a>
+ <div id='Fedora.12.Burning_ISO_images_to_disc.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/12/epub/Burning_ISO_images_to_disc/Fedora-12-Burning_ISO_images_to_disc-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/12/html/Burning_ISO_images_to_disc/index.html" onclick="window.top.location='../en-US/./Fedora/12/html/Burning_ISO_images_to_disc/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/12/html-single/Burning_ISO_images_to_disc/index.html" onclick="window.top.location='../en-US/./Fedora/12/html-single/Burning_ISO_images_to_disc/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/12/pdf/Burning_ISO_images_to_disc/Fedora-12-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/12/pdf/Burning_ISO_images_to_disc/Fedora-12-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ <div id='Fedora.12.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.12.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora/12/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora/12/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora.12.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/12/epub/Deployment_Guide/Fedora-12-Deployment_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/12/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/12/html/Deployment_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/12/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/12/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/12/pdf/Deployment_Guide/Fedora-12-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/12/pdf/Deployment_Guide/Fedora-12-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ <div id='Fedora.12.Fedora_Live_images' class="book collapsed" onclick="toggle(event, 'Fedora.12.Fedora_Live_images.types');">
+ <a class="type" href="../en-US/Fedora/12/html/Fedora_Live_images/index.html" onclick="window.top.location='../en-US/Fedora/12/html/Fedora_Live_images/index.html'"><span class="book">Fedora Live images</span></a>
+ <div id='Fedora.12.Fedora_Live_images.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/12/epub/Fedora_Live_images/Fedora-12-Fedora_Live_images-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/12/html/Fedora_Live_images/index.html" onclick="window.top.location='../en-US/./Fedora/12/html/Fedora_Live_images/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/12/html-single/Fedora_Live_images/index.html" onclick="window.top.location='../en-US/./Fedora/12/html-single/Fedora_Live_images/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/12/pdf/Fedora_Live_images/Fedora-12-Fedora_Live_images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/12/pdf/Fedora_Live_images/Fedora-12-Fedora_Live_images-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ <div id='Fedora.12.Installation_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.12.Installation_Guide.types');">
+ <a class="type" href="../en-US/Fedora/12/html/Installation_Guide/index.html" onclick="window.top.location='../en-US/Fedora/12/html/Installation_Guide/index.html'"><span class="book">Installation Guide</span></a>
+ <div id='Fedora.12.Installation_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/12/epub/Installation_Guide/Fedora-12-Installation_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/12/html/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/12/html/Installation_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/12/html-single/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/12/html-single/Installation_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/12/pdf/Installation_Guide/Fedora-12-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/12/pdf/Installation_Guide/Fedora-12-Installation_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ <div id='Fedora.12.Installation_Quick_Start_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.12.Installation_Quick_Start_Guide.types');">
+ <a class="type" href="../en-US/Fedora/12/html/Installation_Quick_Start_Guide/index.html" onclick="window.top.location='../en-US/Fedora/12/html/Installation_Quick_Start_Guide/index.html'"><span class="book">Installation Quick Start Guide</span></a>
+ <div id='Fedora.12.Installation_Quick_Start_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/12/epub/Installation_Quick_Start_Guide/Fedora-12-Installation_Quick_Start_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/12/html/Installation_Quick_Start_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/12/html/Installation_Quick_Start_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/12/html-single/Installation_Quick_Start_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/12/html-single/Installation_Quick_Start_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/12/pdf/Installation_Quick_Start_Guide/Fedora-12-Installation_Quick_Start_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/12/pdf/Installation_Quick_Start_Guide/Fedora-12-Installation_Quick_Start_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ <div id='Fedora.12.Managing_Confined_Services' class="book collapsed" onclick="toggle(event, 'Fedora.12.Managing_Confined_Services.types');">
+ <a class="type" href="../en-US/Fedora/12/html/Managing_Confined_Services/index.html" onclick="window.top.location='../en-US/Fedora/12/html/Managing_Confined_Services/index.html'"><span class="book">Managing Confined Services</span></a>
+ <div id='Fedora.12.Managing_Confined_Services.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/12/epub/Managing_Confined_Services/Fedora-12-Managing_Confined_Services-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/12/html/Managing_Confined_Services/index.html" onclick="window.top.location='../en-US/./Fedora/12/html/Managing_Confined_Services/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/12/html-single/Managing_Confined_Services/index.html" onclick="window.top.location='../en-US/./Fedora/12/html-single/Managing_Confined_Services/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/12/pdf/Managing_Confined_Services/Fedora-12-Managing_Confined_Services-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/12/pdf/Managing_Confined_Services/Fedora-12-Managing_Confined_Services-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ <div id='Fedora.12.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.12.Release_Notes.types');">
+ <a class="type" href="../en-US/Fedora/12/html/Release_Notes/index.html" onclick="window.top.location='../en-US/Fedora/12/html/Release_Notes/index.html'"><span class="book">Release Notes</span></a>
+ <div id='Fedora.12.Release_Notes.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/12/epub/Release_Notes/Fedora-12-Release_Notes-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/12/html/Release_Notes/index.html" onclick="window.top.location='../en-US/./Fedora/12/html/Release_Notes/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/12/html-single/Release_Notes/index.html" onclick="window.top.location='../en-US/./Fedora/12/html-single/Release_Notes/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/12/pdf/Release_Notes/Fedora-12-Release_Notes-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/12/pdf/Release_Notes/Fedora-12-Release_Notes-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ <div id='Fedora.12.Security-Enhanced_Linux' class="book collapsed" onclick="toggle(event, 'Fedora.12.Security-Enhanced_Linux.types');">
+ <a class="type" href="../en-US/Fedora/12/html/Security-Enhanced_Linux/index.html" onclick="window.top.location='../en-US/Fedora/12/html/Security-Enhanced_Linux/index.html'"><span class="book">Security-Enhanced Linux</span></a>
+ <div id='Fedora.12.Security-Enhanced_Linux.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/12/epub/Security-Enhanced_Linux/Fedora-12-Security-Enhanced_Linux-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/12/html/Security-Enhanced_Linux/index.html" onclick="window.top.location='../en-US/./Fedora/12/html/Security-Enhanced_Linux/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/12/html-single/Security-Enhanced_Linux/index.html" onclick="window.top.location='../en-US/./Fedora/12/html-single/Security-Enhanced_Linux/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/12/pdf/Security-Enhanced_Linux/Fedora-12-Security-Enhanced_Linux-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/12/pdf/Security-Enhanced_Linux/Fedora-12-Security-Enhanced_Linux-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ <div id='Fedora.12.Security_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.12.Security_Guide.types');">
+ <a class="type" href="../en-US/Fedora/12/html/Security_Guide/index.html" onclick="window.top.location='../en-US/Fedora/12/html/Security_Guide/index.html'"><span class="book">Security Guide</span></a>
+ <div id='Fedora.12.Security_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/12/epub/Security_Guide/Fedora-12-Security_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/12/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/12/html/Security_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/12/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/12/html-single/Security_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/12/pdf/Security_Guide/Fedora-12-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/12/pdf/Security_Guide/Fedora-12-Security_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ <div id='Fedora.12.User_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.12.User_Guide.types');">
+ <a class="type" href="../en-US/Fedora/12/html/User_Guide/index.html" onclick="window.top.location='../en-US/Fedora/12/html/User_Guide/index.html'"><span class="book">User Guide</span></a>
+ <div id='Fedora.12.User_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/12/epub/User_Guide/Fedora-12-User_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/12/html/User_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/12/html/User_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/12/html-single/User_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/12/html-single/User_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/12/pdf/User_Guide/Fedora-12-User_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/12/pdf/User_Guide/Fedora-12-User_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ <div id='Fedora.12.Virtualization_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.12.Virtualization_Guide.types');">
+ <a class="type" href="../en-US/Fedora/12/html/Virtualization_Guide/index.html" onclick="window.top.location='../en-US/Fedora/12/html/Virtualization_Guide/index.html'"><span class="book">Virtualization Guide</span></a>
+ <div id='Fedora.12.Virtualization_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/12/epub/Virtualization_Guide/Fedora-12-Virtualization_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/12/html/Virtualization_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/12/html/Virtualization_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/12/html-single/Virtualization_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/12/html-single/Virtualization_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/12/pdf/Virtualization_Guide/Fedora-12-Virtualization_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/12/pdf/Virtualization_Guide/Fedora-12-Virtualization_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ <div id='Fedora.12.Wireless_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.12.Wireless_Guide.types');">
+ <a class="type" href="../en-US/Fedora/12/html/Wireless_Guide/index.html" onclick="window.top.location='../en-US/Fedora/12/html/Wireless_Guide/index.html'"><span class="book">Wireless Guide</span></a>
+ <div id='Fedora.12.Wireless_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/12/epub/Wireless_Guide/Fedora-12-Wireless_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/12/html/Wireless_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/12/html/Wireless_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/12/html-single/Wireless_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/12/html-single/Wireless_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/12/pdf/Wireless_Guide/Fedora-12-Wireless_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/12/pdf/Wireless_Guide/Fedora-12-Wireless_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ </div>
+ </div>
+ </div>
+ </div>
+ <div id='Fedora.11' class="version collapsed" onclick="toggle(event, 'Fedora.11.books');">
+ <span class="version">11</span>
+ <div id='Fedora.11.books' class="books hidden">
+ <div id='Fedora.11' class="version collapsed untranslated" onclick="toggle(event, 'Fedora.11.untrans_books');">
+ <span class="version">Untranslated</span>
+ <div id='Fedora.11.untrans_books' class="books hidden">
+ <div id='Fedora.11.Burning_ISO_images_to_disc' class="book collapsed" onclick="toggle(event, 'Fedora.11.Burning_ISO_images_to_disc.types');">
+ <a class="type" href="../en-US/Fedora/11/html/Burning_ISO_images_to_disc/index.html" onclick="window.top.location='../en-US/Fedora/11/html/Burning_ISO_images_to_disc/index.html'"><span class="book">Burning ISO images to disc</span></a>
+ <div id='Fedora.11.Burning_ISO_images_to_disc.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/11/epub/Burning_ISO_images_to_disc/Fedora-11-Burning_ISO_images_to_disc-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/11/html/Burning_ISO_images_to_disc/index.html" onclick="window.top.location='../en-US/./Fedora/11/html/Burning_ISO_images_to_disc/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/11/html-single/Burning_ISO_images_to_disc/index.html" onclick="window.top.location='../en-US/./Fedora/11/html-single/Burning_ISO_images_to_disc/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/11/pdf/Burning_ISO_images_to_disc/Fedora-11-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/Burning_ISO_images_to_disc/Fedora-11-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ <div id='Fedora.11.Fedora_Live_images' class="book collapsed" onclick="toggle(event, 'Fedora.11.Fedora_Live_images.types');">
+ <a class="type" href="../en-US/Fedora/11/html/Fedora_Live_images/index.html" onclick="window.top.location='../en-US/Fedora/11/html/Fedora_Live_images/index.html'"><span class="book">Fedora Live images</span></a>
+ <div id='Fedora.11.Fedora_Live_images.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/11/epub/Fedora_Live_images/Fedora-11-Fedora_Live_images-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/11/html/Fedora_Live_images/index.html" onclick="window.top.location='../en-US/./Fedora/11/html/Fedora_Live_images/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/11/html-single/Fedora_Live_images/index.html" onclick="window.top.location='../en-US/./Fedora/11/html-single/Fedora_Live_images/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/11/pdf/Fedora_Live_images/Fedora-11-Fedora_Live_images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/Fedora_Live_images/Fedora-11-Fedora_Live_images-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ <div id='Fedora.11.Installation_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.11.Installation_Guide.types');">
+ <a class="type" href="../en-US/Fedora/11/html/Installation_Guide/index.html" onclick="window.top.location='../en-US/Fedora/11/html/Installation_Guide/index.html'"><span class="book">Installation Guide</span></a>
+ <div id='Fedora.11.Installation_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/11/epub/Installation_Guide/Fedora-11-Installation_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/11/html/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html/Installation_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/11/html-single/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html-single/Installation_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/11/pdf/Installation_Guide/Fedora-11-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/Installation_Guide/Fedora-11-Installation_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ <div id='Fedora.11.Installation_Quick_Start_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.11.Installation_Quick_Start_Guide.types');">
+ <a class="type" href="../en-US/Fedora/11/html/Installation_Quick_Start_Guide/index.html" onclick="window.top.location='../en-US/Fedora/11/html/Installation_Quick_Start_Guide/index.html'"><span class="book">Installation Quick Start Guide</span></a>
+ <div id='Fedora.11.Installation_Quick_Start_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/11/epub/Installation_Quick_Start_Guide/Fedora-11-Installation_Quick_Start_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/11/html/Installation_Quick_Start_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html/Installation_Quick_Start_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/11/html-single/Installation_Quick_Start_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html-single/Installation_Quick_Start_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/11/pdf/Installation_Quick_Start_Guide/Fedora-11-Installation_Quick_Start_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/Installation_Quick_Start_Guide/Fedora-11-Installation_Quick_Start_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ <div id='Fedora.11.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.11.Release_Notes.types');">
+ <a class="type" href="../en-US/Fedora/11/html/Release_Notes/index.html" onclick="window.top.location='../en-US/Fedora/11/html/Release_Notes/index.html'"><span class="book">Release Notes</span></a>
+ <div id='Fedora.11.Release_Notes.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/11/epub/Release_Notes/Fedora-11-Release_Notes-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/11/html/Release_Notes/index.html" onclick="window.top.location='../en-US/./Fedora/11/html/Release_Notes/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/11/html-single/Release_Notes/index.html" onclick="window.top.location='../en-US/./Fedora/11/html-single/Release_Notes/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/11/pdf/Release_Notes/Fedora-11-Release_Notes-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/Release_Notes/Fedora-11-Release_Notes-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ <div id='Fedora.11.Security-Enhanced_Linux' class="book collapsed" onclick="toggle(event, 'Fedora.11.Security-Enhanced_Linux.types');">
+ <a class="type" href="../en-US/Fedora/11/html/Security-Enhanced_Linux/index.html" onclick="window.top.location='../en-US/Fedora/11/html/Security-Enhanced_Linux/index.html'"><span class="book">Security-Enhanced Linux</span></a>
+ <div id='Fedora.11.Security-Enhanced_Linux.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/11/epub/Security-Enhanced_Linux/Fedora-11-Security-Enhanced_Linux-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/11/html/Security-Enhanced_Linux/index.html" onclick="window.top.location='../en-US/./Fedora/11/html/Security-Enhanced_Linux/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/11/html-single/Security-Enhanced_Linux/index.html" onclick="window.top.location='../en-US/./Fedora/11/html-single/Security-Enhanced_Linux/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/11/pdf/Security-Enhanced_Linux/Fedora-11-Security-Enhanced_Linux-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/Security-Enhanced_Linux/Fedora-11-Security-Enhanced_Linux-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ <div id='Fedora.11.Security_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.11.Security_Guide.types');">
+ <a class="type" href="../en-US/Fedora/11/html/Security_Guide/index.html" onclick="window.top.location='../en-US/Fedora/11/html/Security_Guide/index.html'"><span class="book">Security Guide</span></a>
+ <div id='Fedora.11.Security_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/11/epub/Security_Guide/Fedora-11-Security_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/11/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html/Security_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/11/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html-single/Security_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ <div id='Fedora.11.User_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.11.User_Guide.types');">
+ <a class="type" href="../en-US/Fedora/11/html/User_Guide/index.html" onclick="window.top.location='../en-US/Fedora/11/html/User_Guide/index.html'"><span class="book">User Guide</span></a>
+ <div id='Fedora.11.User_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/11/epub/User_Guide/Fedora-11-User_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/11/html/User_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html/User_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/11/html-single/User_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html-single/User_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/11/pdf/User_Guide/Fedora-11-User_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/User_Guide/Fedora-11-User_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ </div>
+ </div>
+ </div>
+ </div>
+ <div id='Fedora.10' class="version collapsed" onclick="toggle(event, 'Fedora.10.books');">
+ <span class="version">10</span>
+ <div id='Fedora.10.books' class="books hidden">
+ <div id='Fedora.10' class="version collapsed untranslated" onclick="toggle(event, 'Fedora.10.untrans_books');">
+ <span class="version">Untranslated</span>
+ <div id='Fedora.10.untrans_books' class="books hidden">
+ <div id='Fedora.10.Fedora_Live_Images' class="book collapsed" onclick="toggle(event, 'Fedora.10.Fedora_Live_Images.types');">
+ <a class="type" href="../en-US/Fedora/10/html/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/Fedora/10/html/Fedora_Live_Images/index.html'"><span class="book">Fedora Live Images</span></a>
+ <div id='Fedora.10.Fedora_Live_Images.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/10/epub/Fedora_Live_Images/Fedora-10-Fedora_Live_Images-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/10/html/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/10/html/Fedora_Live_Images/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/10/html-single/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/10/html-single/Fedora_Live_Images/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/10/pdf/Fedora_Live_Images/Fedora-10-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/10/pdf/Fedora_Live_Images/Fedora-10-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ <div id='Fedora.10.Installation_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.10.Installation_Guide.types');">
+ <a class="type" href="../en-US/Fedora/10/html/Installation_Guide/index.html" onclick="window.top.location='../en-US/Fedora/10/html/Installation_Guide/index.html'"><span class="book">Installation Guide</span></a>
+ <div id='Fedora.10.Installation_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/10/epub/Installation_Guide/Fedora-10-Installation_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/10/html/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/10/html/Installation_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/10/html-single/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/10/html-single/Installation_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/10/pdf/Installation_Guide/Fedora-10-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/10/pdf/Installation_Guide/Fedora-10-Installation_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ <div id='Fedora.10.Making_Fedora_Discs' class="book collapsed" onclick="toggle(event, 'Fedora.10.Making_Fedora_Discs.types');">
+ <a class="type" href="../en-US/Fedora/10/html/Making_Fedora_Discs/index.html" onclick="window.top.location='../en-US/Fedora/10/html/Making_Fedora_Discs/index.html'"><span class="book">Making Fedora Discs</span></a>
+ <div id='Fedora.10.Making_Fedora_Discs.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/10/epub/Making_Fedora_Discs/Fedora-10-Making_Fedora_Discs-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/10/html/Making_Fedora_Discs/index.html" onclick="window.top.location='../en-US/./Fedora/10/html/Making_Fedora_Discs/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/10/html-single/Making_Fedora_Discs/index.html" onclick="window.top.location='../en-US/./Fedora/10/html-single/Making_Fedora_Discs/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/10/pdf/Making_Fedora_Discs/Fedora-10-Making_Fedora_Discs-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/10/pdf/Making_Fedora_Discs/Fedora-10-Making_Fedora_Discs-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ <div id='Fedora.10.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.10.Release_Notes.types');">
+ <a class="type" href="../en-US/Fedora/10/html/Release_Notes/index.html" onclick="window.top.location='../en-US/Fedora/10/html/Release_Notes/index.html'"><span class="book">Release Notes</span></a>
+ <div id='Fedora.10.Release_Notes.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/10/epub/Release_Notes/Fedora-10-Release_Notes-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/10/html/Release_Notes/index.html" onclick="window.top.location='../en-US/./Fedora/10/html/Release_Notes/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/10/html-single/Release_Notes/index.html" onclick="window.top.location='../en-US/./Fedora/10/html-single/Release_Notes/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/10/pdf/Release_Notes/Fedora-10-Release_Notes-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/10/pdf/Release_Notes/Fedora-10-Release_Notes-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ </div>
+ </div>
+ </div>
+ </div>
+ <div id='Fedora.9' class="version collapsed" onclick="toggle(event, 'Fedora.9.books');">
+ <span class="version">9</span>
+ <div id='Fedora.9.books' class="books hidden">
+ <div id='Fedora.9' class="version collapsed untranslated" onclick="toggle(event, 'Fedora.9.untrans_books');">
+ <span class="version">Untranslated</span>
+ <div id='Fedora.9.untrans_books' class="books hidden">
+ <div id='Fedora.9.Fedora_Live_Images' class="book collapsed" onclick="toggle(event, 'Fedora.9.Fedora_Live_Images.types');">
+ <a class="type" href="../en-US/Fedora/9/html/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/Fedora/9/html/Fedora_Live_Images/index.html'"><span class="book">Fedora Live Images</span></a>
+ <div id='Fedora.9.Fedora_Live_Images.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/9/epub/Fedora_Live_Images/Fedora-9-Fedora_Live_Images-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/9/html/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/9/html/Fedora_Live_Images/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/9/html-single/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/9/html-single/Fedora_Live_Images/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/9/pdf/Fedora_Live_Images/Fedora-9-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/9/pdf/Fedora_Live_Images/Fedora-9-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ <div id='Fedora.9.Installation_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.9.Installation_Guide.types');">
+ <a class="type" href="../en-US/Fedora/9/html/Installation_Guide/index.html" onclick="window.top.location='../en-US/Fedora/9/html/Installation_Guide/index.html'"><span class="book">Installation Guide</span></a>
+ <div id='Fedora.9.Installation_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/9/epub/Installation_Guide/Fedora-9-Installation_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/9/html/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/9/html/Installation_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/9/html-single/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/9/html-single/Installation_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/9/pdf/Installation_Guide/Fedora-9-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/9/pdf/Installation_Guide/Fedora-9-Installation_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ <div id='Fedora.9.Making_Fedora_Discs' class="book collapsed" onclick="toggle(event, 'Fedora.9.Making_Fedora_Discs.types');">
+ <a class="type" href="../en-US/Fedora/9/html/Making_Fedora_Discs/index.html" onclick="window.top.location='../en-US/Fedora/9/html/Making_Fedora_Discs/index.html'"><span class="book">Making Fedora Discs</span></a>
+ <div id='Fedora.9.Making_Fedora_Discs.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/9/epub/Making_Fedora_Discs/Fedora-9-Making_Fedora_Discs-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/9/html/Making_Fedora_Discs/index.html" onclick="window.top.location='../en-US/./Fedora/9/html/Making_Fedora_Discs/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/9/html-single/Making_Fedora_Discs/index.html" onclick="window.top.location='../en-US/./Fedora/9/html-single/Making_Fedora_Discs/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/9/pdf/Making_Fedora_Discs/Fedora-9-Making_Fedora_Discs-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/9/pdf/Making_Fedora_Discs/Fedora-9-Making_Fedora_Discs-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ <div id='Fedora.9.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.9.Release_Notes.types');">
+ <a class="type" href="../en-US/Fedora/9/html/Release_Notes/index.html" onclick="window.top.location='../en-US/Fedora/9/html/Release_Notes/index.html'"><span class="book">Release Notes</span></a>
+ <div id='Fedora.9.Release_Notes.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/9/epub/Release_Notes/Fedora-9-Release_Notes-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/9/html/Release_Notes/index.html" onclick="window.top.location='../en-US/./Fedora/9/html/Release_Notes/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/9/html-single/Release_Notes/index.html" onclick="window.top.location='../en-US/./Fedora/9/html-single/Release_Notes/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/9/pdf/Release_Notes/Fedora-9-Release_Notes-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/9/pdf/Release_Notes/Fedora-9-Release_Notes-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ </div>
+ </div>
+ </div>
+ </div>
+ <div id='Fedora.8' class="version collapsed" onclick="toggle(event, 'Fedora.8.books');">
+ <span class="version">8</span>
+ <div id='Fedora.8.books' class="books hidden">
+ <div id='Fedora.8' class="version collapsed untranslated" onclick="toggle(event, 'Fedora.8.untrans_books');">
+ <span class="version">Untranslated</span>
+ <div id='Fedora.8.untrans_books' class="books hidden">
+ <div id='Fedora.8.Fedora_Live_Images' class="book collapsed" onclick="toggle(event, 'Fedora.8.Fedora_Live_Images.types');">
+ <a class="type" href="../en-US/Fedora/8/html/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/Fedora/8/html/Fedora_Live_Images/index.html'"><span class="book">Fedora Live Images</span></a>
+ <div id='Fedora.8.Fedora_Live_Images.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/8/epub/Fedora_Live_Images/Fedora-8-Fedora_Live_Images-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/8/html/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/8/html/Fedora_Live_Images/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/8/html-single/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/8/html-single/Fedora_Live_Images/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/8/pdf/Fedora_Live_Images/Fedora-8-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/8/pdf/Fedora_Live_Images/Fedora-8-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ <div id='Fedora.8.Installation_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.8.Installation_Guide.types');">
+ <a class="type" href="../en-US/Fedora/8/html/Installation_Guide/index.html" onclick="window.top.location='../en-US/Fedora/8/html/Installation_Guide/index.html'"><span class="book">Installation Guide</span></a>
+ <div id='Fedora.8.Installation_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/8/epub/Installation_Guide/Fedora-8-Installation_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/8/html/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/8/html/Installation_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/8/html-single/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/8/html-single/Installation_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-8-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-8-Installation_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ <div id='Fedora.8.Making_Fedora_Discs' class="book collapsed" onclick="toggle(event, 'Fedora.8.Making_Fedora_Discs.types');">
+ <a class="type" href="../en-US/Fedora/8/html/Making_Fedora_Discs/index.html" onclick="window.top.location='../en-US/Fedora/8/html/Making_Fedora_Discs/index.html'"><span class="book">Making Fedora Discs</span></a>
+ <div id='Fedora.8.Making_Fedora_Discs.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/8/epub/Making_Fedora_Discs/Fedora-8-Making_Fedora_Discs-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/8/html/Making_Fedora_Discs/index.html" onclick="window.top.location='../en-US/./Fedora/8/html/Making_Fedora_Discs/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/8/html-single/Making_Fedora_Discs/index.html" onclick="window.top.location='../en-US/./Fedora/8/html-single/Making_Fedora_Discs/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/8/pdf/Making_Fedora_Discs/Fedora-8-Making_Fedora_Discs-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/8/pdf/Making_Fedora_Discs/Fedora-8-Making_Fedora_Discs-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ <div id='Fedora.8.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.8.Release_Notes.types');">
+ <a class="type" href="../en-US/Fedora/8/html/Release_Notes/index.html" onclick="window.top.location='../en-US/Fedora/8/html/Release_Notes/index.html'"><span class="book">Release Notes</span></a>
+ <div id='Fedora.8.Release_Notes.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/8/epub/Release_Notes/Fedora-8-Release_Notes-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/8/html/Release_Notes/index.html" onclick="window.top.location='../en-US/./Fedora/8/html/Release_Notes/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/8/html-single/Release_Notes/index.html" onclick="window.top.location='../en-US/./Fedora/8/html-single/Release_Notes/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/8/pdf/Release_Notes/Fedora-8-Release_Notes-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/8/pdf/Release_Notes/Fedora-8-Release_Notes-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ <div id='Fedora.8.SELinux_FAQ' class="book collapsed" onclick="toggle(event, 'Fedora.8.SELinux_FAQ.types');">
+ <a class="type" href="../en-US/Fedora/8/html/SELinux_FAQ/index.html" onclick="window.top.location='../en-US/Fedora/8/html/SELinux_FAQ/index.html'"><span class="book">SELinux FAQ</span></a>
+ <div id='Fedora.8.SELinux_FAQ.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/8/epub/SELinux_FAQ/Fedora-8-SELinux_FAQ-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/8/html/SELinux_FAQ/index.html" onclick="window.top.location='../en-US/./Fedora/8/html/SELinux_FAQ/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/8/html-single/SELinux_FAQ/index.html" onclick="window.top.location='../en-US/./Fedora/8/html-single/SELinux_FAQ/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/8/pdf/SELinux_FAQ/Fedora-8-SELinux_FAQ-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/8/pdf/SELinux_FAQ/Fedora-8-SELinux_FAQ-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ </div>
+ </div>
+ </div>
+ </div>
+ <div id='Fedora.7' class="version collapsed" onclick="toggle(event, 'Fedora.7.books');">
+ <span class="version">7</span>
+ <div id='Fedora.7.books' class="books hidden">
+ <div id='Fedora.7' class="version collapsed untranslated" onclick="toggle(event, 'Fedora.7.untrans_books');">
+ <span class="version">Untranslated</span>
+ <div id='Fedora.7.untrans_books' class="books hidden">
+ <div id='Fedora.7.Installation_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.7.Installation_Guide.types');">
+ <a class="type" href="../en-US/Fedora/7/html/Installation_Guide/index.html" onclick="window.top.location='../en-US/Fedora/7/html/Installation_Guide/index.html'"><span class="book">Installation Guide</span></a>
+ <div id='Fedora.7.Installation_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/7/epub/Installation_Guide/Fedora-7-Installation_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/7/html/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/7/html/Installation_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/7/html-single/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/7/html-single/Installation_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/7/pdf/Installation_Guide/Fedora-7-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/7/pdf/Installation_Guide/Fedora-7-Installation_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ <div id='Fedora.7.Making_Fedora_Discs' class="book collapsed" onclick="toggle(event, 'Fedora.7.Making_Fedora_Discs.types');">
+ <a class="type" href="../en-US/Fedora/7/html/Making_Fedora_Discs/index.html" onclick="window.top.location='../en-US/Fedora/7/html/Making_Fedora_Discs/index.html'"><span class="book">Making Fedora Discs</span></a>
+ <div id='Fedora.7.Making_Fedora_Discs.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/7/epub/Making_Fedora_Discs/Fedora-7-Making_Fedora_Discs-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/7/html/Making_Fedora_Discs/index.html" onclick="window.top.location='../en-US/./Fedora/7/html/Making_Fedora_Discs/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/7/html-single/Making_Fedora_Discs/index.html" onclick="window.top.location='../en-US/./Fedora/7/html-single/Making_Fedora_Discs/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/7/pdf/Making_Fedora_Discs/Fedora-7-Making_Fedora_Discs-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/7/pdf/Making_Fedora_Discs/Fedora-7-Making_Fedora_Discs-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ <div id='Fedora.7.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.7.Release_Notes.types');">
+ <a class="type" href="../en-US/Fedora/7/html/Release_Notes/index.html" onclick="window.top.location='../en-US/Fedora/7/html/Release_Notes/index.html'"><span class="book">Release Notes</span></a>
+ <div id='Fedora.7.Release_Notes.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/7/epub/Release_Notes/Fedora-7-Release_Notes-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/7/html/Release_Notes/index.html" onclick="window.top.location='../en-US/./Fedora/7/html/Release_Notes/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/7/html-single/Release_Notes/index.html" onclick="window.top.location='../en-US/./Fedora/7/html-single/Release_Notes/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/7/pdf/Release_Notes/Fedora-7-Release_Notes-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/7/pdf/Release_Notes/Fedora-7-Release_Notes-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ </div>
+ </div>
+ </div>
+ </div>
+ <div id='Fedora.0.1' class="version collapsed" onclick="toggle(event, 'Fedora.0.1.books');"> <div id='Fedora.0.1.books' class="books">
+ <div id='Fedora.0.1' class="version collapsed untranslated" onclick="toggle(event, 'Fedora.0.1.untrans_books');">
+ <span class="version">Untranslated</span>
+ <div id='Fedora.0.1.untrans_books' class="books hidden">
+ <div id='Fedora.0.1.Amateur_Radio_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.0.1.Amateur_Radio_Guide.types');">
+ <a class="type" href="../en-US/Fedora/0.1/html/Amateur_Radio_Guide/index.html" onclick="window.top.location='../en-US/Fedora/0.1/html/Amateur_Radio_Guide/index.html'"><span class="book">Amateur Radio Guide</span></a>
+ <div id='Fedora.0.1.Amateur_Radio_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/0.1/epub/Amateur_Radio_Guide/Fedora-0.1-Amateur_Radio_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/0.1/html/Amateur_Radio_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/0.1/html/Amateur_Radio_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/0.1/html-single/Amateur_Radio_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/0.1/html-single/Amateur_Radio_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/0.1/pdf/Amateur_Radio_Guide/Fedora_Draft_Documentation-0.1-Amateur_Radio_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/0.1/pdf/Amateur_Radio_Guide/Fedora_Draft_Documentation-0.1-Amateur_Radio_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ </div>
+ </div>
+ </div>
+ </div>
+ </div>
+ </div>
+ <div class="product collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation');work=1;">
+ <span class="product">Fedora Contributor Documentation</span>
+ <div id='Fedora_Contributor_Documentation' class="versions hidden">
+ <div id='Fedora_Contributor_Documentation.1' class="version collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.books');"> <div id='Fedora_Contributor_Documentation.1.books' class="books">
+ <div id='Fedora_Contributor_Documentation.1' class="version collapsed untranslated" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.untrans_books');">
+ <span class="version">Untranslated</span>
+ <div id='Fedora_Contributor_Documentation.1.untrans_books' class="books hidden">
+ <div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Fedora_Elections_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html'"><span class="book">Fedora Elections Guide</span></a>
+ <div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ <div id='Fedora_Contributor_Documentation.1.Translation_Quick_Start_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Translation_Quick_Start_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Contributor_Documentation/1/html/Translation_Quick_Start_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Contributor_Documentation/1/html/Translation_Quick_Start_Guide/index.html'"><span class="book">Translation Quick Start Guide</span></a>
+ <div id='Fedora_Contributor_Documentation.1.Translation_Quick_Start_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Translation_Quick_Start_Guide/Fedora_Contributor_Documentation-1-Translation_Quick_Start_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Translation_Quick_Start_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Translation_Quick_Start_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Translation_Quick_Start_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Translation_Quick_Start_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Translation_Quick_Start_Guide/Fedora_Contributor_Documentation-1-Translation_Quick_Start_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Translation_Quick_Start_Guide/Fedora_Contributor_Documentation-1-Translation_Quick_Start_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ <div id='Fedora_Contributor_Documentation.1.Users_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Users_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Contributor_Documentation/1/html/Users_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Contributor_Documentation/1/html/Users_Guide/index.html'"><span class="book">Publican Users Guide</span></a>
+ <div id='Fedora_Contributor_Documentation.1.Users_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ </div>
+ </div>
+ </div>
+ </div>
+ </div>
+ </div>
+ <div class="product collapsed" onclick="toggle(event, 'Fedora_Core');work=1;">
+ <span class="product">Fedora Core</span>
+ <div id='Fedora_Core' class="versions hidden">
+ <div id='Fedora_Core.6' class="version collapsed" onclick="toggle(event, 'Fedora_Core.6.books');">
+ <span class="version">6</span>
+ <div id='Fedora_Core.6.books' class="books hidden">
+ <div id='Fedora_Core.6' class="version collapsed untranslated" onclick="toggle(event, 'Fedora_Core.6.untrans_books');">
+ <span class="version">Untranslated</span>
+ <div id='Fedora_Core.6.untrans_books' class="books hidden">
+ <div id='Fedora_Core.6.Installation_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Core.6.Installation_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Core/6/html/Installation_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Core/6/html/Installation_Guide/index.html'"><span class="book">Installation Guide</span></a>
+ <div id='Fedora_Core.6.Installation_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora_Core/6/epub/Installation_Guide/Fedora_Core-6-Installation_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Core/6/html/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Core/6/html/Installation_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora_Core/6/html-single/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Core/6/html-single/Installation_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora_Core/6/pdf/Installation_Guide/Fedora_Core-6-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Core/6/pdf/Installation_Guide/Fedora_Core-6-Installation_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ <div id='Fedora_Core.6.Making_Fedora_Discs' class="book collapsed" onclick="toggle(event, 'Fedora_Core.6.Making_Fedora_Discs.types');">
+ <a class="type" href="../en-US/Fedora_Core/6/html/Making_Fedora_Discs/index.html" onclick="window.top.location='../en-US/Fedora_Core/6/html/Making_Fedora_Discs/index.html'"><span class="book">Making Fedora Discs</span></a>
+ <div id='Fedora_Core.6.Making_Fedora_Discs.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora_Core/6/epub/Making_Fedora_Discs/Fedora_Core-6-Making_Fedora_Discs-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Core/6/html/Making_Fedora_Discs/index.html" onclick="window.top.location='../en-US/./Fedora_Core/6/html/Making_Fedora_Discs/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora_Core/6/html-single/Making_Fedora_Discs/index.html" onclick="window.top.location='../en-US/./Fedora_Core/6/html-single/Making_Fedora_Discs/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora_Core/6/pdf/Making_Fedora_Discs/Fedora_Core-6-Making_Fedora_Discs-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Core/6/pdf/Making_Fedora_Discs/Fedora_Core-6-Making_Fedora_Discs-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ <div id='Fedora_Core.6.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora_Core.6.Release_Notes.types');">
+ <a class="type" href="../en-US/Fedora_Core/6/html/Release_Notes/index.html" onclick="window.top.location='../en-US/Fedora_Core/6/html/Release_Notes/index.html'"><span class="book">Release Notes</span></a>
+ <div id='Fedora_Core.6.Release_Notes.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora_Core/6/epub/Release_Notes/Fedora_Core-6-Release_Notes-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Core/6/html/Release_Notes/index.html" onclick="window.top.location='../en-US/./Fedora_Core/6/html/Release_Notes/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora_Core/6/html-single/Release_Notes/index.html" onclick="window.top.location='../en-US/./Fedora_Core/6/html-single/Release_Notes/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora_Core/6/pdf/Release_Notes/Fedora_Core-6-Release_Notes-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Core/6/pdf/Release_Notes/Fedora_Core-6-Release_Notes-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ <div id='Fedora_Core.6.User_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Core.6.User_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Core/6/html/User_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Core/6/html/User_Guide/index.html'"><span class="book">User Guide</span></a>
+ <div id='Fedora_Core.6.User_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora_Core/6/epub/User_Guide/Fedora_Core-6-User_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Core/6/html/User_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Core/6/html/User_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora_Core/6/html-single/User_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Core/6/html-single/User_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora_Core/6/pdf/User_Guide/Fedora_Core-6-User_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Core/6/pdf/User_Guide/Fedora_Core-6-User_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ </div>
+ </div>
+ </div>
+ </div>
+ <div id='Fedora_Core.5' class="version collapsed" onclick="toggle(event, 'Fedora_Core.5.books');">
+ <span class="version">5</span>
+ <div id='Fedora_Core.5.books' class="books hidden">
+ <div id='Fedora_Core.5' class="version collapsed untranslated" onclick="toggle(event, 'Fedora_Core.5.untrans_books');">
+ <span class="version">Untranslated</span>
+ <div id='Fedora_Core.5.untrans_books' class="books hidden">
+ <div id='Fedora_Core.5.Installation_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Core.5.Installation_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Core/5/html/Installation_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Core/5/html/Installation_Guide/index.html'"><span class="book">Installation Guide</span></a>
+ <div id='Fedora_Core.5.Installation_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora_Core/5/epub/Installation_Guide/Fedora_Core-5-Installation_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Core/5/html/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Core/5/html/Installation_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora_Core/5/html-single/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Core/5/html-single/Installation_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora_Core/5/pdf/Installation_Guide/Fedora_Core-5-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Core/5/pdf/Installation_Guide/Fedora_Core-5-Installation_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ <div id='Fedora_Core.5.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora_Core.5.Release_Notes.types');">
+ <a class="type" href="../en-US/Fedora_Core/5/html/Release_Notes/index.html" onclick="window.top.location='../en-US/Fedora_Core/5/html/Release_Notes/index.html'"><span class="book">Release Notes</span></a>
+ <div id='Fedora_Core.5.Release_Notes.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora_Core/5/epub/Release_Notes/Fedora_Core-5-Release_Notes-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Core/5/html/Release_Notes/index.html" onclick="window.top.location='../en-US/./Fedora_Core/5/html/Release_Notes/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora_Core/5/html-single/Release_Notes/index.html" onclick="window.top.location='../en-US/./Fedora_Core/5/html-single/Release_Notes/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora_Core/5/pdf/Release_Notes/Fedora_Core-5-Release_Notes-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Core/5/pdf/Release_Notes/Fedora_Core-5-Release_Notes-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ <div id='Fedora_Core.5.SELinux_FAQ' class="book collapsed" onclick="toggle(event, 'Fedora_Core.5.SELinux_FAQ.types');">
+ <a class="type" href="../en-US/Fedora_Core/5/html/SELinux_FAQ/index.html" onclick="window.top.location='../en-US/Fedora_Core/5/html/SELinux_FAQ/index.html'"><span class="book">SELinux FAQ</span></a>
+ <div id='Fedora_Core.5.SELinux_FAQ.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora_Core/5/epub/SELinux_FAQ/Fedora_Core-5-SELinux_FAQ-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Core/5/html/SELinux_FAQ/index.html" onclick="window.top.location='../en-US/./Fedora_Core/5/html/SELinux_FAQ/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora_Core/5/html-single/SELinux_FAQ/index.html" onclick="window.top.location='../en-US/./Fedora_Core/5/html-single/SELinux_FAQ/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora_Core/5/pdf/SELinux_FAQ/Fedora_Core-5-SELinux_FAQ-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Core/5/pdf/SELinux_FAQ/Fedora_Core-5-SELinux_FAQ-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ <div id='Fedora_Core.5.Software_Management_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Core.5.Software_Management_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Core/5/html/Software_Management_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Core/5/html/Software_Management_Guide/index.html'"><span class="book">Software Management Guide</span></a>
+ <div id='Fedora_Core.5.Software_Management_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora_Core/5/epub/Software_Management_Guide/Fedora_Core-5-Software_Management_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Core/5/html/Software_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Core/5/html/Software_Management_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora_Core/5/html-single/Software_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Core/5/html-single/Software_Management_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora_Core/5/pdf/Software_Management_Guide/Fedora_Core-5-Software_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Core/5/pdf/Software_Management_Guide/Fedora_Core-5-Software_Management_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ </div>
+ </div>
+ </div>
+ </div>
+ <div id='Fedora_Core.4' class="version collapsed" onclick="toggle(event, 'Fedora_Core.4.books');">
+ <span class="version">4</span>
+ <div id='Fedora_Core.4.books' class="books hidden">
+ <div id='Fedora_Core.4' class="version collapsed untranslated" onclick="toggle(event, 'Fedora_Core.4.untrans_books');">
+ <span class="version">Untranslated</span>
+ <div id='Fedora_Core.4.untrans_books' class="books hidden">
+ <div id='Fedora_Core.4.Installation_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Core.4.Installation_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Core/4/html/Installation_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Core/4/html/Installation_Guide/index.html'"><span class="book">Installation Guide</span></a>
+ <div id='Fedora_Core.4.Installation_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora_Core/4/html/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Core/4/html/Installation_Guide/index.html';return false;">html</a>
+ </div>
+ </div>
+ <div id='Fedora_Core.4.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora_Core.4.Release_Notes.types');">
+ <a class="type" href="../en-US/Fedora_Core/4/html/Release_Notes/index.html" onclick="window.top.location='../en-US/Fedora_Core/4/html/Release_Notes/index.html'"><span class="book">Release Notes</span></a>
+ <div id='Fedora_Core.4.Release_Notes.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora_Core/4/html/Release_Notes/index.html" onclick="window.top.location='../en-US/./Fedora_Core/4/html/Release_Notes/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora_Core/4/html-single/Release_Notes/index.html" onclick="window.top.location='../en-US/./Fedora_Core/4/html-single/Release_Notes/index.html';return false;">html-single</a>
+ </div>
+ </div>
+ <div id='Fedora_Core.4.Software_Management_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Core.4.Software_Management_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Core/4/html/Software_Management_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Core/4/html/Software_Management_Guide/index.html'"><span class="book">Software Management Guide</span></a>
+ <div id='Fedora_Core.4.Software_Management_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora_Core/4/epub/Software_Management_Guide/Fedora_Core-4-Software_Management_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Core/4/html/Software_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Core/4/html/Software_Management_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora_Core/4/html-single/Software_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Core/4/html-single/Software_Management_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora_Core/4/pdf/Software_Management_Guide/Fedora_Core-4-Software_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Core/4/pdf/Software_Management_Guide/Fedora_Core-4-Software_Management_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ </div>
+ </div>
+ </div>
+ </div>
+ <div id='Fedora_Core.3' class="version collapsed" onclick="toggle(event, 'Fedora_Core.3.books');">
+ <span class="version">3</span>
+ <div id='Fedora_Core.3.books' class="books hidden">
+ <div id='Fedora_Core.3' class="version collapsed untranslated" onclick="toggle(event, 'Fedora_Core.3.untrans_books');">
+ <span class="version">Untranslated</span>
+ <div id='Fedora_Core.3.untrans_books' class="books hidden">
+ <div id='Fedora_Core.3.Release_Notes_for_32-bit_x86_Systems' class="book collapsed" onclick="toggle(event, 'Fedora_Core.3.Release_Notes_for_32-bit_x86_Systems.types');">
+ <a class="type" href="../en-US/Fedora_Core/3/html/Release_Notes_for_32-bit_x86_Systems/index.html" onclick="window.top.location='../en-US/Fedora_Core/3/html/Release_Notes_for_32-bit_x86_Systems/index.html'"><span class="book">Release Notes for 32-bit x86 Systems</span></a>
+ <div id='Fedora_Core.3.Release_Notes_for_32-bit_x86_Systems.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora_Core/3/html/Release_Notes_for_32-bit_x86_Systems/index.html" onclick="window.top.location='../en-US/./Fedora_Core/3/html/Release_Notes_for_32-bit_x86_Systems/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora_Core/3/html-single/Release_Notes_for_32-bit_x86_Systems/index.html" onclick="window.top.location='../en-US/./Fedora_Core/3/html-single/Release_Notes_for_32-bit_x86_Systems/index.html';return false;">html-single</a>
+ </div>
+ </div>
+ <div id='Fedora_Core.3.Release_Notes_for_64-bit_x86_Systems' class="book collapsed" onclick="toggle(event, 'Fedora_Core.3.Release_Notes_for_64-bit_x86_Systems.types');">
+ <a class="type" href="../en-US/Fedora_Core/3/html/Release_Notes_for_64-bit_x86_Systems/index.html" onclick="window.top.location='../en-US/Fedora_Core/3/html/Release_Notes_for_64-bit_x86_Systems/index.html'"><span class="book">Release Notes for 64-bit x86 Systems</span></a>
+ <div id='Fedora_Core.3.Release_Notes_for_64-bit_x86_Systems.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora_Core/3/html/Release_Notes_for_64-bit_x86_Systems/index.html" onclick="window.top.location='../en-US/./Fedora_Core/3/html/Release_Notes_for_64-bit_x86_Systems/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora_Core/3/html-single/Release_Notes_for_64-bit_x86_Systems/index.html" onclick="window.top.location='../en-US/./Fedora_Core/3/html-single/Release_Notes_for_64-bit_x86_Systems/index.html';return false;">html-single</a>
+ </div>
+ </div>
+ <div id='Fedora_Core.3.SELinux_FAQ' class="book collapsed" onclick="toggle(event, 'Fedora_Core.3.SELinux_FAQ.types');">
+ <a class="type" href="../en-US/Fedora_Core/3/html/SELinux_FAQ/index.html" onclick="window.top.location='../en-US/Fedora_Core/3/html/SELinux_FAQ/index.html'"><span class="book">SELinux FAQ</span></a>
+ <div id='Fedora_Core.3.SELinux_FAQ.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora_Core/3/html/SELinux_FAQ/index.html" onclick="window.top.location='../en-US/./Fedora_Core/3/html/SELinux_FAQ/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora_Core/3/html-single/SELinux_FAQ/index.html" onclick="window.top.location='../en-US/./Fedora_Core/3/html-single/SELinux_FAQ/index.html';return false;">html-single</a>
+ </div>
+ </div>
+ <div id='Fedora_Core.3.Software_Management_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Core.3.Software_Management_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Core/3/html/Software_Management_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Core/3/html/Software_Management_Guide/index.html'"><span class="book">Software Management Guide</span></a>
+ <div id='Fedora_Core.3.Software_Management_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora_Core/3/epub/Software_Management_Guide/Fedora_Core-3-Software_Management_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Core/3/html/Software_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Core/3/html/Software_Management_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora_Core/3/html-single/Software_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Core/3/html-single/Software_Management_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora_Core/3/pdf/Software_Management_Guide/Fedora_Core-3-Software_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Core/3/pdf/Software_Management_Guide/Fedora_Core-3-Software_Management_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ </div>
+ </div>
+ </div>
+ </div>
+ <div id='Fedora_Core.2' class="version collapsed" onclick="toggle(event, 'Fedora_Core.2.books');">
+ <span class="version">2</span>
+ <div id='Fedora_Core.2.books' class="books hidden">
+ <div id='Fedora_Core.2' class="version collapsed untranslated" onclick="toggle(event, 'Fedora_Core.2.untrans_books');">
+ <span class="version">Untranslated</span>
+ <div id='Fedora_Core.2.untrans_books' class="books hidden">
+ <div id='Fedora_Core.2.Release_Notes_for_32-bit_x86_Systems' class="book collapsed" onclick="toggle(event, 'Fedora_Core.2.Release_Notes_for_32-bit_x86_Systems.types');">
+ <a class="type" href="../en-US/Fedora_Core/2/html/Release_Notes_for_32-bit_x86_Systems/index.html" onclick="window.top.location='../en-US/Fedora_Core/2/html/Release_Notes_for_32-bit_x86_Systems/index.html'"><span class="book">Release Notes for 32-bit x86 Systems</span></a>
+ <div id='Fedora_Core.2.Release_Notes_for_32-bit_x86_Systems.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora_Core/2/html/Release_Notes_for_32-bit_x86_Systems/index.html" onclick="window.top.location='../en-US/./Fedora_Core/2/html/Release_Notes_for_32-bit_x86_Systems/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora_Core/2/html-single/Release_Notes_for_32-bit_x86_Systems/index.html" onclick="window.top.location='../en-US/./Fedora_Core/2/html-single/Release_Notes_for_32-bit_x86_Systems/index.html';return false;">html-single</a>
+ </div>
+ </div>
+ <div id='Fedora_Core.2.Release_Notes_for_64-bit_x86_Systems' class="book collapsed" onclick="toggle(event, 'Fedora_Core.2.Release_Notes_for_64-bit_x86_Systems.types');">
+ <a class="type" href="../en-US/Fedora_Core/2/html/Release_Notes_for_64-bit_x86_Systems/index.html" onclick="window.top.location='../en-US/Fedora_Core/2/html/Release_Notes_for_64-bit_x86_Systems/index.html'"><span class="book">Release Notes for 64-bit x86 Systems</span></a>
+ <div id='Fedora_Core.2.Release_Notes_for_64-bit_x86_Systems.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora_Core/2/html/Release_Notes_for_64-bit_x86_Systems/index.html" onclick="window.top.location='../en-US/./Fedora_Core/2/html/Release_Notes_for_64-bit_x86_Systems/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora_Core/2/html-single/Release_Notes_for_64-bit_x86_Systems/index.html" onclick="window.top.location='../en-US/./Fedora_Core/2/html-single/Release_Notes_for_64-bit_x86_Systems/index.html';return false;">html-single</a>
+ </div>
+ </div>
+ <div id='Fedora_Core.2.SELinux_FAQ' class="book collapsed" onclick="toggle(event, 'Fedora_Core.2.SELinux_FAQ.types');">
+ <a class="type" href="../en-US/Fedora_Core/2/html/SELinux_FAQ/index.html" onclick="window.top.location='../en-US/Fedora_Core/2/html/SELinux_FAQ/index.html'"><span class="book">SELinux FAQ</span></a>
+ <div id='Fedora_Core.2.SELinux_FAQ.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora_Core/2/html/SELinux_FAQ/index.html" onclick="window.top.location='../en-US/./Fedora_Core/2/html/SELinux_FAQ/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora_Core/2/html-single/SELinux_FAQ/index.html" onclick="window.top.location='../en-US/./Fedora_Core/2/html-single/SELinux_FAQ/index.html';return false;">html-single</a>
+ </div>
+ </div>
+ </div>
+ </div>
+ </div>
+ </div>
+ <div id='Fedora_Core.1' class="version collapsed" onclick="toggle(event, 'Fedora_Core.1.books');">
+ <span class="version">1</span>
+ <div id='Fedora_Core.1.books' class="books hidden">
+ <div id='Fedora_Core.1' class="version collapsed untranslated" onclick="toggle(event, 'Fedora_Core.1.untrans_books');">
+ <span class="version">Untranslated</span>
+ <div id='Fedora_Core.1.untrans_books' class="books hidden">
+ <div id='Fedora_Core.1.Release_Notes_for_32-bit_x86_Systems' class="book collapsed" onclick="toggle(event, 'Fedora_Core.1.Release_Notes_for_32-bit_x86_Systems.types');">
+ <a class="type" href="../en-US/Fedora_Core/1/html/Release_Notes_for_32-bit_x86_Systems/index.html" onclick="window.top.location='../en-US/Fedora_Core/1/html/Release_Notes_for_32-bit_x86_Systems/index.html'"><span class="book">Release Notes for 32-bit x86 Systems</span></a>
+ <div id='Fedora_Core.1.Release_Notes_for_32-bit_x86_Systems.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora_Core/1/html/Release_Notes_for_32-bit_x86_Systems/index.html" onclick="window.top.location='../en-US/./Fedora_Core/1/html/Release_Notes_for_32-bit_x86_Systems/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora_Core/1/html-single/Release_Notes_for_32-bit_x86_Systems/index.html" onclick="window.top.location='../en-US/./Fedora_Core/1/html-single/Release_Notes_for_32-bit_x86_Systems/index.html';return false;">html-single</a>
+ </div>
+ </div>
+ <div id='Fedora_Core.1.Release_Notes_for_64-bit_x86_Systems' class="book collapsed" onclick="toggle(event, 'Fedora_Core.1.Release_Notes_for_64-bit_x86_Systems.types');">
+ <a class="type" href="../en-US/Fedora_Core/1/html/Release_Notes_for_64-bit_x86_Systems/index.html" onclick="window.top.location='../en-US/Fedora_Core/1/html/Release_Notes_for_64-bit_x86_Systems/index.html'"><span class="book">Release Notes for 64-bit x86 Systems</span></a>
+ <div id='Fedora_Core.1.Release_Notes_for_64-bit_x86_Systems.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora_Core/1/html/Release_Notes_for_64-bit_x86_Systems/index.html" onclick="window.top.location='../en-US/./Fedora_Core/1/html/Release_Notes_for_64-bit_x86_Systems/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora_Core/1/html-single/Release_Notes_for_64-bit_x86_Systems/index.html" onclick="window.top.location='../en-US/./Fedora_Core/1/html-single/Release_Notes_for_64-bit_x86_Systems/index.html';return false;">html-single</a>
+ </div>
+ </div>
+ </div>
+ </div>
+ </div>
+ </div>
+ </div>
+ </div>
+ <div class="product collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation');work=1;">
+ <span class="product">Schiță Documentație Fedora</span>
+ <div id='Fedora_Draft_Documentation' class="versions hidden">
+ <div id='Fedora_Draft_Documentation.0.2' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.2.books');"> <div id='Fedora_Draft_Documentation.0.2.books' class="books">
+ <div id='Fedora_Draft_Documentation.0.2' class="version collapsed untranslated" onclick="toggle(event, 'Fedora_Draft_Documentation.0.2.untrans_books');">
+ <span class="version">Untranslated</span>
+ <div id='Fedora_Draft_Documentation.0.2.untrans_books' class="books hidden">
+ <div id='Fedora_Draft_Documentation.0.2.OpenSSH_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.2.OpenSSH_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html'"><span class="book">OpenSSH Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.2.OpenSSH_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.2/epub/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ </div>
+ </div>
+ </div>
+ </div>
+ <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');"> <div id='Fedora_Draft_Documentation.0.1.books' class="books">
+ <div id='Fedora_Draft_Documentation.0.1.RPM_Guide' class="book collapsed">
+ <a class="type" href="Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html" onclick="window.top.location='./Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html'"><span class="book">Ghid RPM</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.RPM_Guide.types' class="types" onclick="work=0;">
+ <a class="type" href="./Fedora_Draft_Documentation/0.1/epub/RPM_Guide/Fedora_Draft_Documentation-0.1-RPM_Guide-ro.epub" >epub</a>
+ <a class="type" href="./Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html" onclick="window.top.location='./Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html';return false;">html</a>
+ <a class="type" href="./Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/index.html" onclick="window.top.location='./Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="./Fedora_Draft_Documentation/0.1/pdf/RPM_Guide/Fedora_Draft_Documentation-0.1-RPM_Guide-ro.pdf" onclick="window.top.location='./Fedora_Draft_Documentation/0.1/pdf/RPM_Guide/Fedora_Draft_Documentation-0.1-RPM_Guide-ro.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ <div id='Fedora_Draft_Documentation.0.1' class="version collapsed untranslated" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.untrans_books');">
+ <span class="version">Untranslated</span>
+ <div id='Fedora_Draft_Documentation.0.1.untrans_books' class="books hidden">
+ <div id='Fedora_Draft_Documentation.0.1.Amateur_Radio_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Amateur_Radio_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Amateur_Radio_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Amateur_Radio_Guide/index.html'"><span class="book">Amateur Radio Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Amateur_Radio_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Amateur_Radio_Guide/Fedora_Draft_Documentation-0.1-Amateur_Radio_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Amateur_Radio_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Amateur_Radio_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Amateur_Radio_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Amateur_Radio_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Amateur_Radio_Guide/Fedora_Draft_Documentation-0.1-Amateur_Radio_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Amateur_Radio_Guide/Fedora_Draft_Documentation-0.1-Amateur_Radio_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ <div id='Fedora_Draft_Documentation.0.1.Cloud_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Cloud_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Cloud_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Cloud_Guide/index.html'"><span class="book">Cloud Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Cloud_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Cloud_Guide/Fedora_Draft_Documentation-0.1-Cloud_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Cloud_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Cloud_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Cloud_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Cloud_Guide/index.html';return false;">html-single</a>
+ </div>
+ </div>
+ <div id='Fedora_Draft_Documentation.0.1.Documentation_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Documentation_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Documentation_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Documentation_Guide/index.html'"><span class="book">Documentation Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Documentation_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Documentation_Guide/Fedora_Draft_Documentation-0.1-Documentation_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Documentation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Documentation_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Documentation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Documentation_Guide/index.html';return false;">html-single</a>
+ </div>
+ </div>
+ <div id='Fedora_Draft_Documentation.0.1.Musicians_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Musicians_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Musicians_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Musicians_Guide/index.html'"><span class="book">Musicians Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Musicians_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Musicians_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Musicians_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Musicians_Guide/Fedora_Draft_Documentation-0.1-Musicians_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Musicians_Guide/Fedora_Draft_Documentation-0.1-Musicians_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
+ </div>
+ </div>
+ </div>
+ </div>
+ </div>
+ </div>
+ <div class="nocookie" id="nojs">
+ <p>The Navigation Menu above requires JavaScript to function.</p><p>Enable JavaScript to allow the Navigation Menu to function.</p><p>Disable CSS to view the Navigation options without JavaScript enabled</p>
+ </div>
+ <div class="bottom_links">
+ <a href="../toc.html" onclick="window.top.location='../toc.html'" >Map</a>
+ <a href="./Site_Statistics.html" onclick="window.top.location='./Site_Statistics.html'" >Statistics</a>
+ <a href="./Site_Tech.html" onclick="window.top.location='./Site_Tech.html'" >Tech</a>
+ </div>
+</div>
+</div>
+</body>
+</html>
+
diff --git a/public_html/ru-RU/Site_Statistics.html b/public_html/ru-RU/Site_Statistics.html
index 1317e7e..1513901 100644
--- a/public_html/ru-RU/Site_Statistics.html
+++ b/public_html/ru-RU/Site_Statistics.html
@@ -392,6 +392,15 @@
</tr>
<tr>
+ <td>Romanian</td>
+ <td>ro</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ </tr>
+
+ <tr>
<td>Tamil</td>
<td>ta-IN</td>
<td>1</td>
@@ -402,8 +411,8 @@
</table>
<div class="totals">
- <b>Ð’Ñего Ñзыков: </b>42<br />
- <b>Ð’Ñего пакетов: </b>673
+ <b>Ð’Ñего Ñзыков: </b>43<br />
+ <b>Ð’Ñего пакетов: </b>674
</div>
</body>
</html>
diff --git a/public_html/ru-RU/opds-Fedora.xml b/public_html/ru-RU/opds-Fedora.xml
index 236dcce..914c9bb 100644
--- a/public_html/ru-RU/opds-Fedora.xml
+++ b/public_html/ru-RU/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ru-RU/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2011-08-17T11:44:28</updated>
+ <updated>2011-08-22T23:04:52</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ru-RU/opds-Fedora_Contributor_Documentation.xml b/public_html/ru-RU/opds-Fedora_Contributor_Documentation.xml
index 669ad5a..8c67526 100644
--- a/public_html/ru-RU/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/ru-RU/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ru-RU/opds-Fedora_Contributor_Documentation.xml</id>
<title>Ð”Ð¾ÐºÑƒÐ¼ÐµÐ½Ñ‚Ð°Ñ†Ð¸Ñ ÑƒÑ‡Ð°Ñтника Fedora</title>
<subtitle>Ð”Ð¾ÐºÑƒÐ¼ÐµÐ½Ñ‚Ð°Ñ†Ð¸Ñ ÑƒÑ‡Ð°Ñтника Fedora</subtitle>
- <updated>2011-08-17T11:44:28</updated>
+ <updated>2011-08-22T23:04:52</updated>
<!--author>
<name></name>
<uri></uri>
@@ -14,7 +14,7 @@
<entry>
<title>Fedora Elections Guide</title>
- <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub</id>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub</id>
<!--author>
<name></name>
<uri></uri>
@@ -26,7 +26,7 @@
<summary>Fedora Elections Guide
</summary>
<content type="text">This book covers procedural information for the use the Fedora Elections software</content>
- <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub">
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub">
<dc:format>application/epub+zip</dc:format>
</link>
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
diff --git a/public_html/ru-RU/opds-Fedora_Core.xml b/public_html/ru-RU/opds-Fedora_Core.xml
index 3b68d20..5816ded 100644
--- a/public_html/ru-RU/opds-Fedora_Core.xml
+++ b/public_html/ru-RU/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ru-RU/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2011-08-17T11:44:28</updated>
+ <updated>2011-08-22T23:04:52</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ru-RU/opds-Fedora_Draft_Documentation.xml b/public_html/ru-RU/opds-Fedora_Draft_Documentation.xml
index c418105..ee75455 100644
--- a/public_html/ru-RU/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/ru-RU/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ru-RU/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2011-08-17T11:44:28</updated>
+ <updated>2011-08-22T23:04:52</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ru-RU/opds.xml b/public_html/ru-RU/opds.xml
index 967d6b4..fc28bf3 100644
--- a/public_html/ru-RU/opds.xml
+++ b/public_html/ru-RU/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/ru-RU/opds.xml</id>
<title>Product List</title>
- <updated>2011-08-17T11:44:28</updated>
+ <updated>2011-08-22T23:04:52</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/ru-RU/Fedora/opds-Fedora.xml</id>
- <updated>2011-08-17T11:44:28</updated>
+ <updated>2011-08-22T23:04:52</updated>
<dc:language>ru-RU</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Ð”Ð¾ÐºÑƒÐ¼ÐµÐ½Ñ‚Ð°Ñ†Ð¸Ñ ÑƒÑ‡Ð°Ñтника Fedora</title>
<id>http://docs.fedoraproject.org/ru-RU/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2011-08-17T11:44:28</updated>
+ <updated>2011-08-22T23:04:52</updated>
<dc:language>ru-RU</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/ru-RU/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2011-08-17T11:44:28</updated>
+ <updated>2011-08-22T23:04:52</updated>
<dc:language>ru-RU</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/ru-RU/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2011-08-17T11:44:28</updated>
+ <updated>2011-08-22T23:04:52</updated>
<dc:language>ru-RU</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/ru-RU/toc.html b/public_html/ru-RU/toc.html
index 543cf95..bc21113 100644
--- a/public_html/ru-RU/toc.html
+++ b/public_html/ru-RU/toc.html
@@ -58,6 +58,7 @@
<option value="pl-PL">Polski</option>
<option value="pt-BR">Português Brasileiro</option>
<option value="pt-PT">Português</option>
+ <option value="ro">Romanian</option>
<option selected="selected" value="ru-RU">РуÑÑкий</option>
<option value="sk-SK">SlovenÅ¡Äina</option>
<option value="sr-Latn-RS">Srpski (latinica)</option>
@@ -288,7 +289,7 @@
<a class="type" href="./Fedora/13/epub/Accessibility_Guide/Fedora-13-Accessibility_Guide-ru-RU.epub" >epub</a>
<a class="type" href="./Fedora/13/html/Accessibility_Guide/index.html" onclick="window.top.location='./Fedora/13/html/Accessibility_Guide/index.html';return false;">html</a>
<a class="type" href="./Fedora/13/html-single/Accessibility_Guide/index.html" onclick="window.top.location='./Fedora/13/html-single/Accessibility_Guide/index.html';return false;">html-single</a>
- <a class="type" href="./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-ru-RU.pdf" onclick="window.top.location='./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-ru-RU.pdf';return false;">pdf</a>
+ <a class="type" href="./Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-ru-RU.pdf" onclick="window.top.location='./Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-ru-RU.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.13.Burning_ISO_images_to_disc' class="book collapsed">
@@ -608,7 +609,7 @@
<a class="type" href="../en-US/./Fedora/11/epub/Security_Guide/Fedora-11-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/11/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/11/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.11.User_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.11.User_Guide.types');">
@@ -737,7 +738,7 @@
<a class="type" href="../en-US/./Fedora/8/epub/Installation_Guide/Fedora-8-Installation_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/8/html/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/8/html/Installation_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/8/html-single/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/8/html-single/Installation_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-9-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-9-Installation_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-8-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-8-Installation_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.8.Making_Fedora_Discs' class="book collapsed" onclick="toggle(event, 'Fedora.8.Making_Fedora_Discs.types');">
@@ -846,7 +847,7 @@
<div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Fedora_Elections_Guide.types');">
<a class="type" href="../en-US/Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html'"><span class="book">Fedora Elections Guide</span></a>
<div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide.types' class="types hidden" onclick="work=0;">
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
@@ -858,7 +859,7 @@
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/sk-SK/Site_Statistics.html b/public_html/sk-SK/Site_Statistics.html
index e17799c..5501668 100644
--- a/public_html/sk-SK/Site_Statistics.html
+++ b/public_html/sk-SK/Site_Statistics.html
@@ -392,6 +392,15 @@
</tr>
<tr>
+ <td>Romanian</td>
+ <td>ro</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ </tr>
+
+ <tr>
<td>Tamil</td>
<td>ta-IN</td>
<td>1</td>
@@ -402,8 +411,8 @@
</table>
<div class="totals">
- <b>Total Languages: </b>42<br />
- <b>Total Packages: </b>673
+ <b>Total Languages: </b>43<br />
+ <b>Total Packages: </b>674
</div>
</body>
</html>
diff --git a/public_html/sk-SK/opds-Fedora.xml b/public_html/sk-SK/opds-Fedora.xml
index bd7593e..03b2358 100644
--- a/public_html/sk-SK/opds-Fedora.xml
+++ b/public_html/sk-SK/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sk-SK/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2011-08-17T11:44:28</updated>
+ <updated>2011-08-22T23:04:52</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sk-SK/opds-Fedora_Contributor_Documentation.xml b/public_html/sk-SK/opds-Fedora_Contributor_Documentation.xml
index 570491e..55ec853 100644
--- a/public_html/sk-SK/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/sk-SK/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sk-SK/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2011-08-17T11:44:28</updated>
+ <updated>2011-08-22T23:04:52</updated>
<!--author>
<name></name>
<uri></uri>
@@ -14,7 +14,7 @@
<entry>
<title>Fedora Elections Guide</title>
- <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub</id>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub</id>
<!--author>
<name></name>
<uri></uri>
@@ -26,7 +26,7 @@
<summary>Fedora Elections Guide
</summary>
<content type="text">This book covers procedural information for the use the Fedora Elections software</content>
- <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub">
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub">
<dc:format>application/epub+zip</dc:format>
</link>
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
diff --git a/public_html/sk-SK/opds-Fedora_Core.xml b/public_html/sk-SK/opds-Fedora_Core.xml
index 2a3ac5f..77770b3 100644
--- a/public_html/sk-SK/opds-Fedora_Core.xml
+++ b/public_html/sk-SK/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sk-SK/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2011-08-17T11:44:28</updated>
+ <updated>2011-08-22T23:04:52</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sk-SK/opds-Fedora_Draft_Documentation.xml b/public_html/sk-SK/opds-Fedora_Draft_Documentation.xml
index 2047114..82c8e57 100644
--- a/public_html/sk-SK/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/sk-SK/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sk-SK/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2011-08-17T11:44:28</updated>
+ <updated>2011-08-22T23:04:52</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sk-SK/opds.xml b/public_html/sk-SK/opds.xml
index a595f7d..5ff789d 100644
--- a/public_html/sk-SK/opds.xml
+++ b/public_html/sk-SK/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/sk-SK/opds.xml</id>
<title>Product List</title>
- <updated>2011-08-17T11:44:28</updated>
+ <updated>2011-08-22T23:04:52</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/sk-SK/Fedora/opds-Fedora.xml</id>
- <updated>2011-08-17T11:44:28</updated>
+ <updated>2011-08-22T23:04:52</updated>
<dc:language>sk-SK</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/sk-SK/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2011-08-17T11:44:28</updated>
+ <updated>2011-08-22T23:04:52</updated>
<dc:language>sk-SK</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/sk-SK/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2011-08-17T11:44:28</updated>
+ <updated>2011-08-22T23:04:52</updated>
<dc:language>sk-SK</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/sk-SK/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2011-08-17T11:44:28</updated>
+ <updated>2011-08-22T23:04:52</updated>
<dc:language>sk-SK</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/sk-SK/toc.html b/public_html/sk-SK/toc.html
index a8d437e..a0f3979 100644
--- a/public_html/sk-SK/toc.html
+++ b/public_html/sk-SK/toc.html
@@ -58,6 +58,7 @@
<option value="pl-PL">Polski</option>
<option value="pt-BR">Português Brasileiro</option>
<option value="pt-PT">Português</option>
+ <option value="ro">Romanian</option>
<option value="ru-RU">РуÑÑкий</option>
<option selected="selected" value="sk-SK">SlovenÅ¡Äina</option>
<option value="sr-Latn-RS">Srpski (latinica)</option>
@@ -292,7 +293,7 @@
<a class="type" href="../en-US/./Fedora/13/epub/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/13/html/Accessibility_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/13/html/Accessibility_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/13/html-single/Accessibility_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/13/html-single/Accessibility_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.13.Burning_ISO_images_to_disc' class="book collapsed" onclick="toggle(event, 'Fedora.13.Burning_ISO_images_to_disc.types');">
@@ -609,7 +610,7 @@
<a class="type" href="../en-US/./Fedora/11/epub/Security_Guide/Fedora-11-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/11/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/11/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.11.User_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.11.User_Guide.types');">
@@ -747,7 +748,7 @@
<a class="type" href="../en-US/./Fedora/8/epub/Installation_Guide/Fedora-8-Installation_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/8/html/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/8/html/Installation_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/8/html-single/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/8/html-single/Installation_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-9-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-9-Installation_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-8-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-8-Installation_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.8.Making_Fedora_Discs' class="book collapsed" onclick="toggle(event, 'Fedora.8.Making_Fedora_Discs.types');">
@@ -838,7 +839,7 @@
<div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Fedora_Elections_Guide.types');">
<a class="type" href="../en-US/Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html'"><span class="book">Fedora Elections Guide</span></a>
<div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide.types' class="types hidden" onclick="work=0;">
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
@@ -859,7 +860,7 @@
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/sr-Latn-RS/Site_Statistics.html b/public_html/sr-Latn-RS/Site_Statistics.html
index e17799c..5501668 100644
--- a/public_html/sr-Latn-RS/Site_Statistics.html
+++ b/public_html/sr-Latn-RS/Site_Statistics.html
@@ -392,6 +392,15 @@
</tr>
<tr>
+ <td>Romanian</td>
+ <td>ro</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ </tr>
+
+ <tr>
<td>Tamil</td>
<td>ta-IN</td>
<td>1</td>
@@ -402,8 +411,8 @@
</table>
<div class="totals">
- <b>Total Languages: </b>42<br />
- <b>Total Packages: </b>673
+ <b>Total Languages: </b>43<br />
+ <b>Total Packages: </b>674
</div>
</body>
</html>
diff --git a/public_html/sr-Latn-RS/opds-Fedora.xml b/public_html/sr-Latn-RS/opds-Fedora.xml
index 7139d51..80224a5 100644
--- a/public_html/sr-Latn-RS/opds-Fedora.xml
+++ b/public_html/sr-Latn-RS/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sr-Latn-RS/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2011-08-17T11:44:28</updated>
+ <updated>2011-08-22T23:04:53</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sr-Latn-RS/opds-Fedora_Contributor_Documentation.xml b/public_html/sr-Latn-RS/opds-Fedora_Contributor_Documentation.xml
index 2fa70d8..c0841b4 100644
--- a/public_html/sr-Latn-RS/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/sr-Latn-RS/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sr-Latn-RS/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2011-08-17T11:44:28</updated>
+ <updated>2011-08-22T23:04:53</updated>
<!--author>
<name></name>
<uri></uri>
@@ -14,7 +14,7 @@
<entry>
<title>Fedora Elections Guide</title>
- <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub</id>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub</id>
<!--author>
<name></name>
<uri></uri>
@@ -26,7 +26,7 @@
<summary>Fedora Elections Guide
</summary>
<content type="text">This book covers procedural information for the use the Fedora Elections software</content>
- <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub">
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub">
<dc:format>application/epub+zip</dc:format>
</link>
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
diff --git a/public_html/sr-Latn-RS/opds-Fedora_Core.xml b/public_html/sr-Latn-RS/opds-Fedora_Core.xml
index fd7d72f..c187bae 100644
--- a/public_html/sr-Latn-RS/opds-Fedora_Core.xml
+++ b/public_html/sr-Latn-RS/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sr-Latn-RS/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2011-08-17T11:44:28</updated>
+ <updated>2011-08-22T23:04:53</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sr-Latn-RS/opds-Fedora_Draft_Documentation.xml b/public_html/sr-Latn-RS/opds-Fedora_Draft_Documentation.xml
index 366887e..3aec906 100644
--- a/public_html/sr-Latn-RS/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/sr-Latn-RS/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sr-Latn-RS/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2011-08-17T11:44:28</updated>
+ <updated>2011-08-22T23:04:53</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sr-Latn-RS/opds.xml b/public_html/sr-Latn-RS/opds.xml
index e58772c..a01c8f5 100644
--- a/public_html/sr-Latn-RS/opds.xml
+++ b/public_html/sr-Latn-RS/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/sr-Latn-RS/opds.xml</id>
<title>Product List</title>
- <updated>2011-08-17T11:44:29</updated>
+ <updated>2011-08-22T23:04:53</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/sr-Latn-RS/Fedora/opds-Fedora.xml</id>
- <updated>2011-08-17T11:44:28</updated>
+ <updated>2011-08-22T23:04:53</updated>
<dc:language>sr-Latn-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/sr-Latn-RS/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2011-08-17T11:44:28</updated>
+ <updated>2011-08-22T23:04:53</updated>
<dc:language>sr-Latn-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/sr-Latn-RS/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2011-08-17T11:44:28</updated>
+ <updated>2011-08-22T23:04:53</updated>
<dc:language>sr-Latn-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/sr-Latn-RS/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2011-08-17T11:44:28</updated>
+ <updated>2011-08-22T23:04:53</updated>
<dc:language>sr-Latn-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/sr-Latn-RS/toc.html b/public_html/sr-Latn-RS/toc.html
index 0cee1fe..1144d7b 100644
--- a/public_html/sr-Latn-RS/toc.html
+++ b/public_html/sr-Latn-RS/toc.html
@@ -58,6 +58,7 @@
<option value="pl-PL">Polski</option>
<option value="pt-BR">Português Brasileiro</option>
<option value="pt-PT">Português</option>
+ <option value="ro">Romanian</option>
<option value="ru-RU">РуÑÑкий</option>
<option value="sk-SK">SlovenÅ¡Äina</option>
<option selected="selected" value="sr-Latn-RS">Srpski (latinica)</option>
@@ -319,7 +320,7 @@
<a class="type" href="../en-US/./Fedora/13/epub/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/13/html/Accessibility_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/13/html/Accessibility_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/13/html-single/Accessibility_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/13/html-single/Accessibility_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.13.Installation_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.13.Installation_Guide.types');">
@@ -609,7 +610,7 @@
<a class="type" href="../en-US/./Fedora/11/epub/Security_Guide/Fedora-11-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/11/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/11/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.11.User_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.11.User_Guide.types');">
@@ -838,7 +839,7 @@
<div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Fedora_Elections_Guide.types');">
<a class="type" href="../en-US/Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html'"><span class="book">Fedora Elections Guide</span></a>
<div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide.types' class="types hidden" onclick="work=0;">
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
@@ -859,7 +860,7 @@
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/sr-RS/Site_Statistics.html b/public_html/sr-RS/Site_Statistics.html
index e17799c..5501668 100644
--- a/public_html/sr-RS/Site_Statistics.html
+++ b/public_html/sr-RS/Site_Statistics.html
@@ -392,6 +392,15 @@
</tr>
<tr>
+ <td>Romanian</td>
+ <td>ro</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ </tr>
+
+ <tr>
<td>Tamil</td>
<td>ta-IN</td>
<td>1</td>
@@ -402,8 +411,8 @@
</table>
<div class="totals">
- <b>Total Languages: </b>42<br />
- <b>Total Packages: </b>673
+ <b>Total Languages: </b>43<br />
+ <b>Total Packages: </b>674
</div>
</body>
</html>
diff --git a/public_html/sr-RS/opds-Fedora.xml b/public_html/sr-RS/opds-Fedora.xml
index f49af81..7f650f9 100644
--- a/public_html/sr-RS/opds-Fedora.xml
+++ b/public_html/sr-RS/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sr-RS/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2011-08-17T11:44:29</updated>
+ <updated>2011-08-22T23:04:53</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sr-RS/opds-Fedora_Contributor_Documentation.xml b/public_html/sr-RS/opds-Fedora_Contributor_Documentation.xml
index 61f5b8e..f925193 100644
--- a/public_html/sr-RS/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/sr-RS/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sr-RS/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2011-08-17T11:44:29</updated>
+ <updated>2011-08-22T23:04:53</updated>
<!--author>
<name></name>
<uri></uri>
@@ -14,7 +14,7 @@
<entry>
<title>Fedora Elections Guide</title>
- <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub</id>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub</id>
<!--author>
<name></name>
<uri></uri>
@@ -26,7 +26,7 @@
<summary>Fedora Elections Guide
</summary>
<content type="text">This book covers procedural information for the use the Fedora Elections software</content>
- <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub">
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub">
<dc:format>application/epub+zip</dc:format>
</link>
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
diff --git a/public_html/sr-RS/opds-Fedora_Core.xml b/public_html/sr-RS/opds-Fedora_Core.xml
index eb79549..c5df762 100644
--- a/public_html/sr-RS/opds-Fedora_Core.xml
+++ b/public_html/sr-RS/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sr-RS/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2011-08-17T11:44:29</updated>
+ <updated>2011-08-22T23:04:53</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sr-RS/opds-Fedora_Draft_Documentation.xml b/public_html/sr-RS/opds-Fedora_Draft_Documentation.xml
index 8cd23c4..940b4af 100644
--- a/public_html/sr-RS/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/sr-RS/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sr-RS/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2011-08-17T11:44:29</updated>
+ <updated>2011-08-22T23:04:53</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sr-RS/opds.xml b/public_html/sr-RS/opds.xml
index 8e36a82..438eed8 100644
--- a/public_html/sr-RS/opds.xml
+++ b/public_html/sr-RS/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/sr-RS/opds.xml</id>
<title>Product List</title>
- <updated>2011-08-17T11:44:29</updated>
+ <updated>2011-08-22T23:04:53</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/sr-RS/Fedora/opds-Fedora.xml</id>
- <updated>2011-08-17T11:44:29</updated>
+ <updated>2011-08-22T23:04:53</updated>
<dc:language>sr-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/sr-RS/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2011-08-17T11:44:29</updated>
+ <updated>2011-08-22T23:04:53</updated>
<dc:language>sr-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/sr-RS/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2011-08-17T11:44:29</updated>
+ <updated>2011-08-22T23:04:53</updated>
<dc:language>sr-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/sr-RS/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2011-08-17T11:44:29</updated>
+ <updated>2011-08-22T23:04:53</updated>
<dc:language>sr-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/sr-RS/toc.html b/public_html/sr-RS/toc.html
index 5cda7e5..9e59800 100644
--- a/public_html/sr-RS/toc.html
+++ b/public_html/sr-RS/toc.html
@@ -58,6 +58,7 @@
<option value="pl-PL">Polski</option>
<option value="pt-BR">Português Brasileiro</option>
<option value="pt-PT">Português</option>
+ <option value="ro">Romanian</option>
<option value="ru-RU">РуÑÑкий</option>
<option value="sk-SK">SlovenÅ¡Äina</option>
<option value="sr-Latn-RS">Srpski (latinica)</option>
@@ -319,7 +320,7 @@
<a class="type" href="../en-US/./Fedora/13/epub/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/13/html/Accessibility_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/13/html/Accessibility_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/13/html-single/Accessibility_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/13/html-single/Accessibility_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.13.Installation_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.13.Installation_Guide.types');">
@@ -609,7 +610,7 @@
<a class="type" href="../en-US/./Fedora/11/epub/Security_Guide/Fedora-11-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/11/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/11/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.11.User_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.11.User_Guide.types');">
@@ -847,7 +848,7 @@
<div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Fedora_Elections_Guide.types');">
<a class="type" href="../en-US/Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html'"><span class="book">Fedora Elections Guide</span></a>
<div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide.types' class="types hidden" onclick="work=0;">
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
@@ -868,7 +869,7 @@
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/sv-SE/Site_Statistics.html b/public_html/sv-SE/Site_Statistics.html
index e17799c..5501668 100644
--- a/public_html/sv-SE/Site_Statistics.html
+++ b/public_html/sv-SE/Site_Statistics.html
@@ -392,6 +392,15 @@
</tr>
<tr>
+ <td>Romanian</td>
+ <td>ro</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ </tr>
+
+ <tr>
<td>Tamil</td>
<td>ta-IN</td>
<td>1</td>
@@ -402,8 +411,8 @@
</table>
<div class="totals">
- <b>Total Languages: </b>42<br />
- <b>Total Packages: </b>673
+ <b>Total Languages: </b>43<br />
+ <b>Total Packages: </b>674
</div>
</body>
</html>
diff --git a/public_html/sv-SE/opds-Fedora.xml b/public_html/sv-SE/opds-Fedora.xml
index 2bae953..45333ce 100644
--- a/public_html/sv-SE/opds-Fedora.xml
+++ b/public_html/sv-SE/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sv-SE/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2011-08-17T11:44:29</updated>
+ <updated>2011-08-22T23:04:53</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sv-SE/opds-Fedora_Contributor_Documentation.xml b/public_html/sv-SE/opds-Fedora_Contributor_Documentation.xml
index ed416d8..a9a83f0 100644
--- a/public_html/sv-SE/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/sv-SE/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sv-SE/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2011-08-17T11:44:29</updated>
+ <updated>2011-08-22T23:04:53</updated>
<!--author>
<name></name>
<uri></uri>
@@ -14,7 +14,7 @@
<entry>
<title>Fedora Elections Guide</title>
- <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub</id>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub</id>
<!--author>
<name></name>
<uri></uri>
@@ -26,7 +26,7 @@
<summary>Fedora Elections Guide
</summary>
<content type="text">This book covers procedural information for the use the Fedora Elections software</content>
- <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub">
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub">
<dc:format>application/epub+zip</dc:format>
</link>
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
diff --git a/public_html/sv-SE/opds-Fedora_Core.xml b/public_html/sv-SE/opds-Fedora_Core.xml
index 7d7457d..2644de7 100644
--- a/public_html/sv-SE/opds-Fedora_Core.xml
+++ b/public_html/sv-SE/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sv-SE/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2011-08-17T11:44:29</updated>
+ <updated>2011-08-22T23:04:53</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sv-SE/opds-Fedora_Draft_Documentation.xml b/public_html/sv-SE/opds-Fedora_Draft_Documentation.xml
index e518e2d..ee105a8 100644
--- a/public_html/sv-SE/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/sv-SE/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sv-SE/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2011-08-17T11:44:29</updated>
+ <updated>2011-08-22T23:04:53</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sv-SE/opds.xml b/public_html/sv-SE/opds.xml
index f9696c8..6a65c67 100644
--- a/public_html/sv-SE/opds.xml
+++ b/public_html/sv-SE/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/sv-SE/opds.xml</id>
<title>Product List</title>
- <updated>2011-08-17T11:44:29</updated>
+ <updated>2011-08-22T23:04:53</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/sv-SE/Fedora/opds-Fedora.xml</id>
- <updated>2011-08-17T11:44:29</updated>
+ <updated>2011-08-22T23:04:53</updated>
<dc:language>sv-SE</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/sv-SE/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2011-08-17T11:44:29</updated>
+ <updated>2011-08-22T23:04:53</updated>
<dc:language>sv-SE</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/sv-SE/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2011-08-17T11:44:29</updated>
+ <updated>2011-08-22T23:04:53</updated>
<dc:language>sv-SE</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/sv-SE/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2011-08-17T11:44:29</updated>
+ <updated>2011-08-22T23:04:53</updated>
<dc:language>sv-SE</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/sv-SE/toc.html b/public_html/sv-SE/toc.html
index fceae7d..3a716f7 100644
--- a/public_html/sv-SE/toc.html
+++ b/public_html/sv-SE/toc.html
@@ -58,6 +58,7 @@
<option value="pl-PL">Polski</option>
<option value="pt-BR">Português Brasileiro</option>
<option value="pt-PT">Português</option>
+ <option value="ro">Romanian</option>
<option value="ru-RU">РуÑÑкий</option>
<option value="sk-SK">SlovenÅ¡Äina</option>
<option value="sr-Latn-RS">Srpski (latinica)</option>
@@ -327,7 +328,7 @@
<a class="type" href="../en-US/./Fedora/13/epub/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/13/html/Accessibility_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/13/html/Accessibility_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/13/html-single/Accessibility_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/13/html-single/Accessibility_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.13.Installation_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.13.Installation_Guide.types');">
@@ -608,7 +609,7 @@
<a class="type" href="../en-US/./Fedora/11/epub/Security_Guide/Fedora-11-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/11/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/11/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.11.User_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.11.User_Guide.types');">
@@ -737,7 +738,7 @@
<a class="type" href="../en-US/./Fedora/8/epub/Installation_Guide/Fedora-8-Installation_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/8/html/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/8/html/Installation_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/8/html-single/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/8/html-single/Installation_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-9-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-9-Installation_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-8-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-8-Installation_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.8.Making_Fedora_Discs' class="book collapsed" onclick="toggle(event, 'Fedora.8.Making_Fedora_Discs.types');">
@@ -819,7 +820,7 @@
<a class="type" href="../en-US/./Fedora/7/epub/Installation_Guide/Fedora-8-Installation_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/7/html/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/7/html/Installation_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/7/html-single/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/7/html-single/Installation_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/7/pdf/Installation_Guide/Fedora-9-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/7/pdf/Installation_Guide/Fedora-9-Installation_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/7/pdf/Installation_Guide/Fedora-8-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/7/pdf/Installation_Guide/Fedora-8-Installation_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.7.Making_Fedora_Discs' class="book collapsed" onclick="toggle(event, 'Fedora.7.Making_Fedora_Discs.types');">
@@ -882,7 +883,7 @@
<div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Fedora_Elections_Guide.types');">
<a class="type" href="../en-US/Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html'"><span class="book">Fedora Elections Guide</span></a>
<div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide.types' class="types hidden" onclick="work=0;">
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
@@ -903,7 +904,7 @@
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/ta-IN/Site_Statistics.html b/public_html/ta-IN/Site_Statistics.html
index e17799c..5501668 100644
--- a/public_html/ta-IN/Site_Statistics.html
+++ b/public_html/ta-IN/Site_Statistics.html
@@ -392,6 +392,15 @@
</tr>
<tr>
+ <td>Romanian</td>
+ <td>ro</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ </tr>
+
+ <tr>
<td>Tamil</td>
<td>ta-IN</td>
<td>1</td>
@@ -402,8 +411,8 @@
</table>
<div class="totals">
- <b>Total Languages: </b>42<br />
- <b>Total Packages: </b>673
+ <b>Total Languages: </b>43<br />
+ <b>Total Packages: </b>674
</div>
</body>
</html>
diff --git a/public_html/ta-IN/opds-Fedora.xml b/public_html/ta-IN/opds-Fedora.xml
index 654d615..fbd14a6 100644
--- a/public_html/ta-IN/opds-Fedora.xml
+++ b/public_html/ta-IN/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ta-IN/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2011-08-17T11:44:29</updated>
+ <updated>2011-08-22T23:04:53</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ta-IN/opds-Fedora_Contributor_Documentation.xml b/public_html/ta-IN/opds-Fedora_Contributor_Documentation.xml
index e30b659..95c32d3 100644
--- a/public_html/ta-IN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/ta-IN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ta-IN/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2011-08-17T11:44:29</updated>
+ <updated>2011-08-22T23:04:53</updated>
<!--author>
<name></name>
<uri></uri>
@@ -14,7 +14,7 @@
<entry>
<title>Fedora Elections Guide</title>
- <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub</id>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub</id>
<!--author>
<name></name>
<uri></uri>
@@ -26,7 +26,7 @@
<summary>Fedora Elections Guide
</summary>
<content type="text">This book covers procedural information for the use the Fedora Elections software</content>
- <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub">
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub">
<dc:format>application/epub+zip</dc:format>
</link>
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
diff --git a/public_html/ta-IN/opds-Fedora_Core.xml b/public_html/ta-IN/opds-Fedora_Core.xml
index 25e9f84..57ff665 100644
--- a/public_html/ta-IN/opds-Fedora_Core.xml
+++ b/public_html/ta-IN/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ta-IN/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2011-08-17T11:44:29</updated>
+ <updated>2011-08-22T23:04:53</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ta-IN/opds-Fedora_Draft_Documentation.xml b/public_html/ta-IN/opds-Fedora_Draft_Documentation.xml
index 471a8bf..86add50 100644
--- a/public_html/ta-IN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/ta-IN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ta-IN/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2011-08-17T11:44:29</updated>
+ <updated>2011-08-22T23:04:53</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ta-IN/opds.xml b/public_html/ta-IN/opds.xml
index 83d42eb..987363f 100644
--- a/public_html/ta-IN/opds.xml
+++ b/public_html/ta-IN/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/ta-IN/opds.xml</id>
<title>Product List</title>
- <updated>2011-08-17T11:44:29</updated>
+ <updated>2011-08-22T23:04:54</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/ta-IN/Fedora/opds-Fedora.xml</id>
- <updated>2011-08-17T11:44:29</updated>
+ <updated>2011-08-22T23:04:53</updated>
<dc:language>ta-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/ta-IN/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2011-08-17T11:44:29</updated>
+ <updated>2011-08-22T23:04:53</updated>
<dc:language>ta-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/ta-IN/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2011-08-17T11:44:29</updated>
+ <updated>2011-08-22T23:04:53</updated>
<dc:language>ta-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/ta-IN/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2011-08-17T11:44:29</updated>
+ <updated>2011-08-22T23:04:53</updated>
<dc:language>ta-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/ta-IN/toc.html b/public_html/ta-IN/toc.html
index 3b2972c..c872390 100644
--- a/public_html/ta-IN/toc.html
+++ b/public_html/ta-IN/toc.html
@@ -58,6 +58,7 @@
<option value="pl-PL">Polski</option>
<option value="pt-BR">Português Brasileiro</option>
<option value="pt-PT">Português</option>
+ <option value="ro">Romanian</option>
<option value="ru-RU">РуÑÑкий</option>
<option value="sk-SK">SlovenÅ¡Äina</option>
<option value="sr-Latn-RS">Srpski (latinica)</option>
@@ -292,7 +293,7 @@
<a class="type" href="../en-US/./Fedora/13/epub/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/13/html/Accessibility_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/13/html/Accessibility_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/13/html-single/Accessibility_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/13/html-single/Accessibility_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.13.Burning_ISO_images_to_disc' class="book collapsed" onclick="toggle(event, 'Fedora.13.Burning_ISO_images_to_disc.types');">
@@ -609,7 +610,7 @@
<a class="type" href="../en-US/./Fedora/11/epub/Security_Guide/Fedora-11-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/11/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/11/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.11.User_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.11.User_Guide.types');">
@@ -738,7 +739,7 @@
<a class="type" href="../en-US/./Fedora/8/epub/Installation_Guide/Fedora-8-Installation_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/8/html/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/8/html/Installation_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/8/html-single/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/8/html-single/Installation_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-9-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-9-Installation_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-8-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-8-Installation_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.8.Making_Fedora_Discs' class="book collapsed" onclick="toggle(event, 'Fedora.8.Making_Fedora_Discs.types');">
@@ -838,7 +839,7 @@
<div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Fedora_Elections_Guide.types');">
<a class="type" href="../en-US/Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html'"><span class="book">Fedora Elections Guide</span></a>
<div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide.types' class="types hidden" onclick="work=0;">
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
@@ -859,7 +860,7 @@
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/te-IN/Site_Statistics.html b/public_html/te-IN/Site_Statistics.html
index e17799c..5501668 100644
--- a/public_html/te-IN/Site_Statistics.html
+++ b/public_html/te-IN/Site_Statistics.html
@@ -392,6 +392,15 @@
</tr>
<tr>
+ <td>Romanian</td>
+ <td>ro</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ </tr>
+
+ <tr>
<td>Tamil</td>
<td>ta-IN</td>
<td>1</td>
@@ -402,8 +411,8 @@
</table>
<div class="totals">
- <b>Total Languages: </b>42<br />
- <b>Total Packages: </b>673
+ <b>Total Languages: </b>43<br />
+ <b>Total Packages: </b>674
</div>
</body>
</html>
diff --git a/public_html/te-IN/opds-Fedora.xml b/public_html/te-IN/opds-Fedora.xml
index 746d9ad..bcfaba8 100644
--- a/public_html/te-IN/opds-Fedora.xml
+++ b/public_html/te-IN/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/te-IN/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2011-08-17T11:44:29</updated>
+ <updated>2011-08-22T23:04:54</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/te-IN/opds-Fedora_Contributor_Documentation.xml b/public_html/te-IN/opds-Fedora_Contributor_Documentation.xml
index b90f686..2c35a1d 100644
--- a/public_html/te-IN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/te-IN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/te-IN/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2011-08-17T11:44:29</updated>
+ <updated>2011-08-22T23:04:54</updated>
<!--author>
<name></name>
<uri></uri>
@@ -14,7 +14,7 @@
<entry>
<title>Fedora Elections Guide</title>
- <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub</id>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub</id>
<!--author>
<name></name>
<uri></uri>
@@ -26,7 +26,7 @@
<summary>Fedora Elections Guide
</summary>
<content type="text">This book covers procedural information for the use the Fedora Elections software</content>
- <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub">
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub">
<dc:format>application/epub+zip</dc:format>
</link>
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
diff --git a/public_html/te-IN/opds-Fedora_Core.xml b/public_html/te-IN/opds-Fedora_Core.xml
index 409fd6c..0287702 100644
--- a/public_html/te-IN/opds-Fedora_Core.xml
+++ b/public_html/te-IN/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/te-IN/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2011-08-17T11:44:29</updated>
+ <updated>2011-08-22T23:04:54</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/te-IN/opds-Fedora_Draft_Documentation.xml b/public_html/te-IN/opds-Fedora_Draft_Documentation.xml
index 29f20af..05182b5 100644
--- a/public_html/te-IN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/te-IN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/te-IN/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2011-08-17T11:44:29</updated>
+ <updated>2011-08-22T23:04:54</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/te-IN/opds.xml b/public_html/te-IN/opds.xml
index f0be98b..8900aca 100644
--- a/public_html/te-IN/opds.xml
+++ b/public_html/te-IN/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/te-IN/opds.xml</id>
<title>Product List</title>
- <updated>2011-08-17T11:44:29</updated>
+ <updated>2011-08-22T23:04:54</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/te-IN/Fedora/opds-Fedora.xml</id>
- <updated>2011-08-17T11:44:29</updated>
+ <updated>2011-08-22T23:04:54</updated>
<dc:language>te-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/te-IN/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2011-08-17T11:44:29</updated>
+ <updated>2011-08-22T23:04:54</updated>
<dc:language>te-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/te-IN/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2011-08-17T11:44:29</updated>
+ <updated>2011-08-22T23:04:54</updated>
<dc:language>te-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/te-IN/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2011-08-17T11:44:29</updated>
+ <updated>2011-08-22T23:04:54</updated>
<dc:language>te-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/te-IN/toc.html b/public_html/te-IN/toc.html
index ce3ab01..dbfed79 100644
--- a/public_html/te-IN/toc.html
+++ b/public_html/te-IN/toc.html
@@ -58,6 +58,7 @@
<option value="pl-PL">Polski</option>
<option value="pt-BR">Português Brasileiro</option>
<option value="pt-PT">Português</option>
+ <option value="ro">Romanian</option>
<option value="ru-RU">РуÑÑкий</option>
<option value="sk-SK">SlovenÅ¡Äina</option>
<option value="sr-Latn-RS">Srpski (latinica)</option>
@@ -292,7 +293,7 @@
<a class="type" href="../en-US/./Fedora/13/epub/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/13/html/Accessibility_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/13/html/Accessibility_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/13/html-single/Accessibility_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/13/html-single/Accessibility_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.13.Burning_ISO_images_to_disc' class="book collapsed" onclick="toggle(event, 'Fedora.13.Burning_ISO_images_to_disc.types');">
@@ -609,7 +610,7 @@
<a class="type" href="../en-US/./Fedora/11/epub/Security_Guide/Fedora-11-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/11/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/11/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.11.User_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.11.User_Guide.types');">
@@ -738,7 +739,7 @@
<a class="type" href="../en-US/./Fedora/8/epub/Installation_Guide/Fedora-8-Installation_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/8/html/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/8/html/Installation_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/8/html-single/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/8/html-single/Installation_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-9-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-9-Installation_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-8-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-8-Installation_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.8.Making_Fedora_Discs' class="book collapsed" onclick="toggle(event, 'Fedora.8.Making_Fedora_Discs.types');">
@@ -838,7 +839,7 @@
<div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Fedora_Elections_Guide.types');">
<a class="type" href="../en-US/Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html'"><span class="book">Fedora Elections Guide</span></a>
<div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide.types' class="types hidden" onclick="work=0;">
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
@@ -859,7 +860,7 @@
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/toc.html b/public_html/toc.html
index 0c79253..a4a53e4 100644
--- a/public_html/toc.html
+++ b/public_html/toc.html
@@ -75,6 +75,8 @@
<li><a href="#Português">Português</a></li>
+ <li><a href="#Romanian">Romanian</a></li>
+
<li><a href="#РуÑÑкий">РуÑÑкий</a></li>
<li><a href="#SlovenÅ¡Äina">SlovenÅ¡Äina</a></li>
@@ -1592,7 +1594,7 @@
<a class="type" href="./en-US/Fedora/13/html-single/Accessibility_Guide/index.html">html-single</a>
- <a class="type" href="./en-US/Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-en-US.pdf">pdf</a>
+ <a class="type" href="./en-US/Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.pdf">pdf</a>
</div>
</div>
@@ -2093,7 +2095,7 @@
<a class="type" href="./en-US/Fedora/11/html-single/Security_Guide/index.html">html-single</a>
- <a class="type" href="./en-US/Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf">pdf</a>
+ <a class="type" href="./en-US/Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf">pdf</a>
</div>
</div>
@@ -2267,7 +2269,7 @@
<a class="type" href="./en-US/Fedora/8/html-single/Installation_Guide/index.html">html-single</a>
- <a class="type" href="./en-US/Fedora/8/pdf/Installation_Guide/Fedora-9-Installation_Guide-en-US.pdf">pdf</a>
+ <a class="type" href="./en-US/Fedora/8/pdf/Installation_Guide/Fedora-8-Installation_Guide-en-US.pdf">pdf</a>
</div>
</div>
@@ -2395,7 +2397,7 @@
<span id="Fedora_Elections_Guide" class="book">Fedora Elections Guide</span>
<div class="types">
- <a class="type" href="./en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub">epub</a>
+ <a class="type" href="./en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub">epub</a>
<a class="type" href="./en-US/Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html">html</a>
@@ -2431,7 +2433,7 @@
<a class="type" href="./en-US/Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html">html-single</a>
- <a class="type" href="./en-US/Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf">pdf</a>
+ <a class="type" href="./en-US/Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf">pdf</a>
</div>
</div>
@@ -2985,7 +2987,7 @@
<a class="type" href="./es-ES/Fedora/13/html-single/Accessibility_Guide/index.html">html-single</a>
- <a class="type" href="./es-ES/Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-es-ES.pdf">pdf</a>
+ <a class="type" href="./es-ES/Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-es-ES.pdf">pdf</a>
</div>
</div>
@@ -3411,7 +3413,7 @@
<a class="type" href="./es-ES/Fedora/11/html-single/Security_Guide/index.html">html-single</a>
- <a class="type" href="./es-ES/Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-es-ES.pdf">pdf</a>
+ <a class="type" href="./es-ES/Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-es-ES.pdf">pdf</a>
</div>
</div>
@@ -6416,7 +6418,7 @@
<a class="type" href="./nl-NL/Fedora/13/html-single/Accessibility_Guide/index.html">html-single</a>
- <a class="type" href="./nl-NL/Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-nl-NL.pdf">pdf</a>
+ <a class="type" href="./nl-NL/Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-nl-NL.pdf">pdf</a>
</div>
</div>
@@ -8678,6 +8680,35 @@
</div>
+ <div class="perlang" id="Romanian">
+ <h2>Romanian (ro)</h2>
+
+ <div class="product">
+ <span id="Fedora_Draft_Documentation" class="product">Schiță Documentație Fedora</span>
+ <div class="versions">
+ <div class="books">
+
+ <div class="book">
+ <span id="RPM_Guide" class="book">Ghid RPM</span>
+ <div class="types">
+
+ <a class="type" href="./ro/Fedora_Draft_Documentation/0.1/epub/RPM_Guide/Fedora_Draft_Documentation-0.1-RPM_Guide-ro.epub">epub</a>
+
+ <a class="type" href="./ro/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html">html</a>
+
+ <a class="type" href="./ro/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/index.html">html-single</a>
+
+ <a class="type" href="./ro/Fedora_Draft_Documentation/0.1/pdf/RPM_Guide/Fedora_Draft_Documentation-0.1-RPM_Guide-ro.pdf">pdf</a>
+
+ </div>
+ </div>
+
+ </div>
+ </div>
+ </div>
+
+ </div>
+
<div class="perlang" id="РуÑÑкий">
<h2>РуÑÑкий (ru-RU)</h2>
@@ -8744,7 +8775,7 @@
<a class="type" href="./ru-RU/Fedora/13/html-single/Accessibility_Guide/index.html">html-single</a>
- <a class="type" href="./ru-RU/Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-ru-RU.pdf">pdf</a>
+ <a class="type" href="./ru-RU/Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-ru-RU.pdf">pdf</a>
</div>
</div>
diff --git a/public_html/uk-UA/Site_Statistics.html b/public_html/uk-UA/Site_Statistics.html
index acd7a20..ced50e2 100644
--- a/public_html/uk-UA/Site_Statistics.html
+++ b/public_html/uk-UA/Site_Statistics.html
@@ -392,6 +392,15 @@
</tr>
<tr>
+ <td>Romanian</td>
+ <td>ro</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ </tr>
+
+ <tr>
<td>Tamil</td>
<td>ta-IN</td>
<td>1</td>
@@ -402,8 +411,8 @@
</table>
<div class="totals">
- <b>Загалом мов: </b>42<br />
- <b>Загалом пакунків: </b>673
+ <b>Загалом мов: </b>43<br />
+ <b>Загалом пакунків: </b>674
</div>
</body>
</html>
diff --git a/public_html/uk-UA/opds-Fedora.xml b/public_html/uk-UA/opds-Fedora.xml
index 7fef51e..b16e43a 100644
--- a/public_html/uk-UA/opds-Fedora.xml
+++ b/public_html/uk-UA/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/uk-UA/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2011-08-17T11:44:30</updated>
+ <updated>2011-08-22T23:04:54</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/uk-UA/opds-Fedora_Contributor_Documentation.xml b/public_html/uk-UA/opds-Fedora_Contributor_Documentation.xml
index e6d5cce..313c909 100644
--- a/public_html/uk-UA/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/uk-UA/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/uk-UA/opds-Fedora_Contributor_Documentation.xml</id>
<title>Ð”Ð¾ÐºÑƒÐ¼ÐµÐ½Ñ‚Ð°Ñ†Ñ–Ñ Ð´Ð»Ñ ÑƒÑ‡Ð°Ñника розробки Fedora</title>
<subtitle>Ð”Ð¾ÐºÑƒÐ¼ÐµÐ½Ñ‚Ð°Ñ†Ñ–Ñ Ð´Ð»Ñ ÑƒÑ‡Ð°Ñника розробки Fedora</subtitle>
- <updated>2011-08-17T11:44:30</updated>
+ <updated>2011-08-22T23:04:54</updated>
<!--author>
<name></name>
<uri></uri>
@@ -14,7 +14,7 @@
<entry>
<title>Fedora Elections Guide</title>
- <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub</id>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub</id>
<!--author>
<name></name>
<uri></uri>
@@ -26,7 +26,7 @@
<summary>Fedora Elections Guide
</summary>
<content type="text">This book covers procedural information for the use the Fedora Elections software</content>
- <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub">
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub">
<dc:format>application/epub+zip</dc:format>
</link>
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
diff --git a/public_html/uk-UA/opds-Fedora_Core.xml b/public_html/uk-UA/opds-Fedora_Core.xml
index 7141cec..81ff0b3 100644
--- a/public_html/uk-UA/opds-Fedora_Core.xml
+++ b/public_html/uk-UA/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/uk-UA/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2011-08-17T11:44:30</updated>
+ <updated>2011-08-22T23:04:54</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/uk-UA/opds-Fedora_Draft_Documentation.xml b/public_html/uk-UA/opds-Fedora_Draft_Documentation.xml
index 10c1894..9fe4c86 100644
--- a/public_html/uk-UA/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/uk-UA/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/uk-UA/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2011-08-17T11:44:30</updated>
+ <updated>2011-08-22T23:04:54</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/uk-UA/opds.xml b/public_html/uk-UA/opds.xml
index 07c39ba..14e980c 100644
--- a/public_html/uk-UA/opds.xml
+++ b/public_html/uk-UA/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/uk-UA/opds.xml</id>
<title>Product List</title>
- <updated>2011-08-17T11:44:30</updated>
+ <updated>2011-08-22T23:04:54</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/uk-UA/Fedora/opds-Fedora.xml</id>
- <updated>2011-08-17T11:44:30</updated>
+ <updated>2011-08-22T23:04:54</updated>
<dc:language>uk-UA</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Ð”Ð¾ÐºÑƒÐ¼ÐµÐ½Ñ‚Ð°Ñ†Ñ–Ñ Ð´Ð»Ñ ÑƒÑ‡Ð°Ñника розробки Fedora</title>
<id>http://docs.fedoraproject.org/uk-UA/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2011-08-17T11:44:30</updated>
+ <updated>2011-08-22T23:04:54</updated>
<dc:language>uk-UA</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/uk-UA/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2011-08-17T11:44:30</updated>
+ <updated>2011-08-22T23:04:54</updated>
<dc:language>uk-UA</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/uk-UA/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2011-08-17T11:44:30</updated>
+ <updated>2011-08-22T23:04:54</updated>
<dc:language>uk-UA</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/uk-UA/toc.html b/public_html/uk-UA/toc.html
index 5b2954d..fe95093 100644
--- a/public_html/uk-UA/toc.html
+++ b/public_html/uk-UA/toc.html
@@ -58,6 +58,7 @@
<option value="pl-PL">Polski</option>
<option value="pt-BR">Português Brasileiro</option>
<option value="pt-PT">Português</option>
+ <option value="ro">Romanian</option>
<option value="ru-RU">РуÑÑкий</option>
<option value="sk-SK">SlovenÅ¡Äina</option>
<option value="sr-Latn-RS">Srpski (latinica)</option>
@@ -608,7 +609,7 @@
<a class="type" href="../en-US/./Fedora/11/epub/Security_Guide/Fedora-11-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/11/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/11/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.11.User_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.11.User_Guide.types');">
@@ -755,7 +756,7 @@
<a class="type" href="../en-US/./Fedora/8/epub/Installation_Guide/Fedora-8-Installation_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/8/html/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/8/html/Installation_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/8/html-single/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/8/html-single/Installation_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-9-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-9-Installation_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-8-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-8-Installation_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.8.SELinux_FAQ' class="book collapsed" onclick="toggle(event, 'Fedora.8.SELinux_FAQ.types');">
@@ -846,7 +847,7 @@
<div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Fedora_Elections_Guide.types');">
<a class="type" href="../en-US/Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html'"><span class="book">Fedora Elections Guide</span></a>
<div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide.types' class="types hidden" onclick="work=0;">
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
@@ -858,7 +859,7 @@
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/zh-CN/Site_Statistics.html b/public_html/zh-CN/Site_Statistics.html
index e17799c..5501668 100644
--- a/public_html/zh-CN/Site_Statistics.html
+++ b/public_html/zh-CN/Site_Statistics.html
@@ -392,6 +392,15 @@
</tr>
<tr>
+ <td>Romanian</td>
+ <td>ro</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ </tr>
+
+ <tr>
<td>Tamil</td>
<td>ta-IN</td>
<td>1</td>
@@ -402,8 +411,8 @@
</table>
<div class="totals">
- <b>Total Languages: </b>42<br />
- <b>Total Packages: </b>673
+ <b>Total Languages: </b>43<br />
+ <b>Total Packages: </b>674
</div>
</body>
</html>
diff --git a/public_html/zh-CN/opds-Fedora.xml b/public_html/zh-CN/opds-Fedora.xml
index 90ee28c..dec3a15 100644
--- a/public_html/zh-CN/opds-Fedora.xml
+++ b/public_html/zh-CN/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/zh-CN/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2011-08-17T11:44:30</updated>
+ <updated>2011-08-22T23:04:54</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/zh-CN/opds-Fedora_Contributor_Documentation.xml b/public_html/zh-CN/opds-Fedora_Contributor_Documentation.xml
index 131c0d5..9f73c1b 100644
--- a/public_html/zh-CN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/zh-CN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/zh-CN/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2011-08-17T11:44:30</updated>
+ <updated>2011-08-22T23:04:54</updated>
<!--author>
<name></name>
<uri></uri>
@@ -14,7 +14,7 @@
<entry>
<title>Fedora Elections Guide</title>
- <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub</id>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub</id>
<!--author>
<name></name>
<uri></uri>
@@ -26,7 +26,7 @@
<summary>Fedora Elections Guide
</summary>
<content type="text">This book covers procedural information for the use the Fedora Elections software</content>
- <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub">
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub">
<dc:format>application/epub+zip</dc:format>
</link>
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
diff --git a/public_html/zh-CN/opds-Fedora_Core.xml b/public_html/zh-CN/opds-Fedora_Core.xml
index 921955f..d99fac3 100644
--- a/public_html/zh-CN/opds-Fedora_Core.xml
+++ b/public_html/zh-CN/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/zh-CN/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2011-08-17T11:44:30</updated>
+ <updated>2011-08-22T23:04:54</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/zh-CN/opds-Fedora_Draft_Documentation.xml b/public_html/zh-CN/opds-Fedora_Draft_Documentation.xml
index 7827380..29f16c9 100644
--- a/public_html/zh-CN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/zh-CN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/zh-CN/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2011-08-17T11:44:30</updated>
+ <updated>2011-08-22T23:04:54</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/zh-CN/opds.xml b/public_html/zh-CN/opds.xml
index 6523f98..ad3994c 100644
--- a/public_html/zh-CN/opds.xml
+++ b/public_html/zh-CN/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/zh-CN/opds.xml</id>
<title>Product List</title>
- <updated>2011-08-17T11:44:30</updated>
+ <updated>2011-08-22T23:04:54</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/zh-CN/Fedora/opds-Fedora.xml</id>
- <updated>2011-08-17T11:44:30</updated>
+ <updated>2011-08-22T23:04:54</updated>
<dc:language>zh-CN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/zh-CN/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2011-08-17T11:44:30</updated>
+ <updated>2011-08-22T23:04:54</updated>
<dc:language>zh-CN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/zh-CN/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2011-08-17T11:44:30</updated>
+ <updated>2011-08-22T23:04:54</updated>
<dc:language>zh-CN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/zh-CN/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2011-08-17T11:44:30</updated>
+ <updated>2011-08-22T23:04:54</updated>
<dc:language>zh-CN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/zh-CN/toc.html b/public_html/zh-CN/toc.html
index 0ff87c3..1f772d5 100644
--- a/public_html/zh-CN/toc.html
+++ b/public_html/zh-CN/toc.html
@@ -58,6 +58,7 @@
<option value="pl-PL">Polski</option>
<option value="pt-BR">Português Brasileiro</option>
<option value="pt-PT">Português</option>
+ <option value="ro">Romanian</option>
<option value="ru-RU">РуÑÑкий</option>
<option value="sk-SK">SlovenÅ¡Äina</option>
<option value="sr-Latn-RS">Srpski (latinica)</option>
@@ -606,7 +607,7 @@
<a class="type" href="../en-US/./Fedora/11/epub/Security_Guide/Fedora-11-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/11/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/11/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.11.User_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.11.User_Guide.types');">
@@ -724,7 +725,7 @@
<a class="type" href="../en-US/./Fedora/10/epub/Security_Guide/Fedora-11-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/10/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/10/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/10/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/10/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/10/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/10/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/10/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/10/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.10.User_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.10.User_Guide.types');">
@@ -825,7 +826,7 @@
<a class="type" href="../en-US/./Fedora/8/epub/Installation_Guide/Fedora-8-Installation_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/8/html/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/8/html/Installation_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/8/html-single/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/8/html-single/Installation_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-9-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-9-Installation_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-8-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-8-Installation_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.8.SELinux_FAQ' class="book collapsed" onclick="toggle(event, 'Fedora.8.SELinux_FAQ.types');">
@@ -916,7 +917,7 @@
<div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Fedora_Elections_Guide.types');">
<a class="type" href="../en-US/Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html'"><span class="book">Fedora Elections Guide</span></a>
<div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide.types' class="types hidden" onclick="work=0;">
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
@@ -928,7 +929,7 @@
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/zh-TW/Site_Statistics.html b/public_html/zh-TW/Site_Statistics.html
index e17799c..5501668 100644
--- a/public_html/zh-TW/Site_Statistics.html
+++ b/public_html/zh-TW/Site_Statistics.html
@@ -392,6 +392,15 @@
</tr>
<tr>
+ <td>Romanian</td>
+ <td>ro</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ <td>1</td>
+ </tr>
+
+ <tr>
<td>Tamil</td>
<td>ta-IN</td>
<td>1</td>
@@ -402,8 +411,8 @@
</table>
<div class="totals">
- <b>Total Languages: </b>42<br />
- <b>Total Packages: </b>673
+ <b>Total Languages: </b>43<br />
+ <b>Total Packages: </b>674
</div>
</body>
</html>
diff --git a/public_html/zh-TW/opds-Fedora.xml b/public_html/zh-TW/opds-Fedora.xml
index a5e36bd..60348c0 100644
--- a/public_html/zh-TW/opds-Fedora.xml
+++ b/public_html/zh-TW/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/zh-TW/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2011-08-17T11:44:30</updated>
+ <updated>2011-08-22T23:04:54</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/zh-TW/opds-Fedora_Contributor_Documentation.xml b/public_html/zh-TW/opds-Fedora_Contributor_Documentation.xml
index e026bb8..ae21408 100644
--- a/public_html/zh-TW/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/zh-TW/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/zh-TW/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2011-08-17T11:44:30</updated>
+ <updated>2011-08-22T23:04:54</updated>
<!--author>
<name></name>
<uri></uri>
@@ -14,7 +14,7 @@
<entry>
<title>Fedora Elections Guide</title>
- <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub</id>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub</id>
<!--author>
<name></name>
<uri></uri>
@@ -26,7 +26,7 @@
<summary>Fedora Elections Guide
</summary>
<content type="text">This book covers procedural information for the use the Fedora Elections software</content>
- <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub">
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub">
<dc:format>application/epub+zip</dc:format>
</link>
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
diff --git a/public_html/zh-TW/opds-Fedora_Core.xml b/public_html/zh-TW/opds-Fedora_Core.xml
index f6555c0f..aa9ee4b 100644
--- a/public_html/zh-TW/opds-Fedora_Core.xml
+++ b/public_html/zh-TW/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/zh-TW/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2011-08-17T11:44:30</updated>
+ <updated>2011-08-22T23:04:54</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/zh-TW/opds-Fedora_Draft_Documentation.xml b/public_html/zh-TW/opds-Fedora_Draft_Documentation.xml
index ccc698b..232ccd8 100644
--- a/public_html/zh-TW/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/zh-TW/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/zh-TW/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2011-08-17T11:44:30</updated>
+ <updated>2011-08-22T23:04:54</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/zh-TW/opds.xml b/public_html/zh-TW/opds.xml
index b53f9f2..5fd8936 100644
--- a/public_html/zh-TW/opds.xml
+++ b/public_html/zh-TW/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/zh-TW/opds.xml</id>
<title>Product List</title>
- <updated>2011-08-17T11:44:30</updated>
+ <updated>2011-08-22T23:04:54</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/zh-TW/Fedora/opds-Fedora.xml</id>
- <updated>2011-08-17T11:44:30</updated>
+ <updated>2011-08-22T23:04:54</updated>
<dc:language>zh-TW</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/zh-TW/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2011-08-17T11:44:30</updated>
+ <updated>2011-08-22T23:04:54</updated>
<dc:language>zh-TW</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/zh-TW/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2011-08-17T11:44:30</updated>
+ <updated>2011-08-22T23:04:54</updated>
<dc:language>zh-TW</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/zh-TW/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2011-08-17T11:44:30</updated>
+ <updated>2011-08-22T23:04:54</updated>
<dc:language>zh-TW</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/zh-TW/toc.html b/public_html/zh-TW/toc.html
index 867b78f..d00823a 100644
--- a/public_html/zh-TW/toc.html
+++ b/public_html/zh-TW/toc.html
@@ -58,6 +58,7 @@
<option value="pl-PL">Polski</option>
<option value="pt-BR">Português Brasileiro</option>
<option value="pt-PT">Português</option>
+ <option value="ro">Romanian</option>
<option value="ru-RU">РуÑÑкий</option>
<option value="sk-SK">SlovenÅ¡Äina</option>
<option value="sr-Latn-RS">Srpski (latinica)</option>
@@ -292,7 +293,7 @@
<a class="type" href="../en-US/./Fedora/13/epub/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/13/html/Accessibility_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/13/html/Accessibility_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/13/html-single/Accessibility_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/13/html-single/Accessibility_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.13.Burning_ISO_images_to_disc' class="book collapsed" onclick="toggle(event, 'Fedora.13.Burning_ISO_images_to_disc.types');">
@@ -609,7 +610,7 @@
<a class="type" href="../en-US/./Fedora/11/epub/Security_Guide/Fedora-11-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/11/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/11/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/11/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.11.User_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.11.User_Guide.types');">
@@ -738,7 +739,7 @@
<a class="type" href="../en-US/./Fedora/8/epub/Installation_Guide/Fedora-8-Installation_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/8/html/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/8/html/Installation_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/8/html-single/Installation_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/8/html-single/Installation_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-9-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-9-Installation_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-8-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/8/pdf/Installation_Guide/Fedora-8-Installation_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.8.Making_Fedora_Discs' class="book collapsed" onclick="toggle(event, 'Fedora.8.Making_Fedora_Discs.types');">
@@ -838,7 +839,7 @@
<div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Fedora_Elections_Guide.types');">
<a class="type" href="../en-US/Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html'"><span class="book">Fedora Elections Guide</span></a>
<div id='Fedora_Contributor_Documentation.1.Fedora_Elections_Guide.types' class="types hidden" onclick="work=0;">
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
@@ -859,7 +860,7 @@
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1.6-Users_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
More information about the docs-commits
mailing list