{"id":47,"date":"2008-03-08T00:37:00","date_gmt":"2008-03-07T17:37:00","guid":{"rendered":"http:\/\/www.jfdesignnet.com\/?p=47"},"modified":"2008-03-08T00:37:00","modified_gmt":"2008-03-07T17:37:00","slug":"rpm-build-environment-structure","status":"publish","type":"post","link":"https:\/\/www.jfdesignnet.com\/?p=47","title":{"rendered":"RPM build environment structure"},"content":{"rendered":"
\"\"<\/a>In order to safely build RPM<\/span>S, we are going to setup a build environment. By default, the build environment is in \/usr\/src<\/span>\/rpm<\/span> and requires you to be logged as root to build RPM<\/span>S. This is dangerous because while you are logged as a superuser, you have too much potential to harm your system and a failed attempt to build a RPM<\/span> could damage your system. To create a build environment, you will first need to create a set of directories in your home folder (write them as I do as it is case sensitive). Below is an example of my build directories.<\/div>\n
\/home\/jfdesign<\/span>\/src<\/span>\/rpm<\/span>\/RPM<\/span>S\/noarch
(this is where multi architecture rpm<\/span>s will be created)
\/home\/jfdesign<\/span>\/src<\/span>\/rpm<\/span>\/RPM<\/span>S\/i586
(this is where i586 rpm<\/span>s will be created)
\/home\/jfdesign<\/span>\/src<\/span>\/rpm<\/span>\/RPM<\/span>S\/i686
(this is where i686 rpm<\/span>s will be created)
\/home\/jfdesign<\/span>\/src<\/span>\/rpm<\/span>\/RPM<\/span>S\/i486
(this is where i486 rpm<\/span>s will be created)
\/home\/jfdesign<\/span>\/src<\/span>\/rpm<\/span>\/RPM<\/span>S\/i386
(this is where i386 rpm<\/span>s will be created)
\/home\/jfdesign<\/span>\/src<\/span>\/rpm<\/span>\/RPM<\/span>S\/athlon
(this is where athlon rpm<\/span>s will be created)
\/home\/jfdesign<\/span>\/src<\/span>\/rpm<\/span>\/BUILD
(this is where the source files are installed during the build process)
\/home\/jfdesign<\/span>\/src<\/span>\/rpm<\/span>\/SRPM<\/span>S
(this is where the source rpm<\/span>s will be created)
\/home\/jfdesign<\/span>\/src<\/span>\/rpm<\/span>\/SOURCES
(this is where you will place the source codes of the RPM<\/span> to be built)
\/home\/jfdesign<\/span>\/src<\/span>\/rpm<\/span>\/SPECS
(this is where you will place the spec file of the RPM<\/span> to be built)
\/home\/jfdesign<\/span>\/src<\/span>\/tmp
(this is where the build process takes place and error logs are created)<\/span><\/pre>\n
This command will create the directory structure:<\/p>\n
cd<\/span> ~
mkdir -p src<\/span>\/rpm<\/span>\/RPM<\/span>S\/i386
mkdir -p src<\/span>\/rpm<\/span>\/RPM<\/span>S\/i486
mkdir -p src<\/span>\/rpm<\/span>\/RPM<\/span>S\/i586
mkdir -p src<\/span>\/rpm<\/span>\/RPM<\/span>S\/i686
mkdir -p src<\/span>\/rpm<\/span>\/RPM<\/span>S\/noarch
mkdir -p src<\/span>\/rpm<\/span>\/RPM<\/span>S\/athlon
mkdir -p src<\/span>\/rpm<\/span>\/SRPM<\/span>S
mkdir -p src<\/span>\/rpm<\/span>\/SOURCES
mkdir -p src<\/span>\/rpm<\/span>\/SPECS
mkdir -p src<\/span>\/rpm<\/span>\/BUILD
mkdir -p src<\/span>\/tmp<\/span><\/pre>\n
Once we have all the directories setup, we need to create two files to let the system know that we will be using our own build environment. The two files must be placed in your home directory (my files are in \/home\/jfdesign<\/span><\/strong>). Use a plaintext editor such as SCiTE or KWrite to create these files. The first file is called .rpm<\/span>rc<\/strong> (do not forget the dot at the start of the name as it is a hidden file). Place the following content in this file.<\/div>\n
buildarchtranslate: i386: i586
buildarchtranslate: i486: i586
buildarchtranslate: i586: i586<\/span>
buildarchtranslate: i686: i586<\/span><\/pre>\n
 The second file is called .rpm<\/span>macros<\/strong> (do not forget the dot at the start of the name as it is a hidden file). Place the following content in this file (do not forget to remove my name and put yours in it).<\/div>\n

<\/span>%_topdir        \/home\/<\/span>jfdesign<\/span>\/<\/span>src<\/span>\/<\/span>rpm<\/span>
<\/span><\/p>\n
%_tmppath    \/home\/<\/span>jfdesign<\/span>\/<\/span>src<\/span>\/tmp

%distribution    KLIXs
%vendor        Kreators
%distsuffix    klixs2007<\/span><\/pre>\n
Now   our system is ready to build rpm<\/span>s.<\/p>\n","protected":false},"excerpt":{"rendered":"
In order to safely build RPMS, we are going to setup a build environment. By default, the build environment is in \/usr\/src\/rpm and requires you to be logged as root to build RPMS. This is dangerous because while you are logged as a superuser, you have too much potential to harm your system and a […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[17,9],"tags":[],"_links":{"self":[{"href":"https:\/\/www.jfdesignnet.com\/index.php?rest_route=\/wp\/v2\/posts\/47"}],"collection":[{"href":"https:\/\/www.jfdesignnet.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.jfdesignnet.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.jfdesignnet.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.jfdesignnet.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=47"}],"version-history":[{"count":0,"href":"https:\/\/www.jfdesignnet.com\/index.php?rest_route=\/wp\/v2\/posts\/47\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.jfdesignnet.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=47"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.jfdesignnet.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=47"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.jfdesignnet.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=47"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}