10 More Discussions You Might Find Interesting
1. Red Hat
Hello,
Is it possible to specify a list of files to be included in an RPM package (section "% files") according to some condtions. For example, if a particular condition is true, do not include the file "X". If not include it.
Thank you for your help.
Regards (1 Reply)
Discussion started by: louzorios
1 Replies
2. Red Hat
After checking the dependencies from below command:-
yum deplist gcc
Update:-
Now when I tried to install the very first dependency , it gave the below error, I guess something is wrong with YUM server itself :P
... (1 Reply)
Discussion started by: manish131081
1 Replies
3. Red Hat
Hi Guys,
I am trying to test installation of a local rpm to my RHEL5 server. I am expecting it to fail as a previous version of the same package name exists. On using rpm -i this behaves as expected but yum install does not pick up the conflict. Here is the element of my SPEC file with the... (5 Replies)
Discussion started by: gazza-o
5 Replies
4. Fedora
Hi Guys I want to know whether is it possible to automatically Install a RPM package after installing OS.
Basically we have have one rpm package which we want to install as part of OS installation . Please Suggest (3 Replies)
Discussion started by: mr_deb
3 Replies
5. UNIX for Dummies Questions & Answers
Hi all,
I have to automate server installation. For this its needed to install 2 - 3 different RPMs. Is there any way of creating a single rpm from these two rpms?
How the spec file will look like?
thanks... (0 Replies)
Discussion started by: zing_foru
0 Replies
6. UNIX for Dummies Questions & Answers
I'm trying to install mysql on a server, but I keep getting an error. Can anyone offer any help?
Below I've listed a bunch of info that you might find helpful.
Here are the commands I'm using.
$ ls
MySQL-client-community-5.1.35-0.rhel3.i386.rpm... (2 Replies)
Discussion started by: wsetchell
2 Replies
7. UNIX for Dummies Questions & Answers
Running FC5 on a Dell desktop. When I compile a LaTex file, it goes fine but
only outlines blank boxes where figs should be. When I send the figs.eps
and Tex file to a friend, his compiles and imbeds the fig. in the text of the
DVI output using my files without add'nl control cards. I conclude... (1 Reply)
Discussion started by: blann
1 Replies
8. SuSE
Hi,
I have got few RPM's from rpmfind.net ( mainly gcc ).
But it seems to be src files instead of the image.
so I think we have to build the src files according to target machine using rpmbuild.
Can any one help me with
1) Various options of rpm build that have to be taken care
2)... (3 Replies)
Discussion started by: Sivaswami
3 Replies
9. Solaris
while building in solaris and going for dynamic linking
whats the difference or advantage or disadvantage in
using RPATH vs while linking package and dependency libraries
i need a little explanation about this RPATH option specially and the difference with normal linking using -L (0 Replies)
Discussion started by: mobydick
0 Replies
10. Shell Programming and Scripting
Hi ,
I am tryin to install expect rpm on my linux machine.
I have the source file expect-5.42.1-1.src.rpm
I am doin this
rpm -ivh expect-5.42.1-1.src.rpm
But I am gettin this error
warning: expect-5.42.1-1.src.rpm: V3 DSA signature : NOKEY, key ID db42a60e
error: cannot... (1 Reply)
Discussion started by: eamani_sun
1 Replies
build(1) General Commands Manual build(1)
NAME
build - build SuSE Linux RPMs in a chroot environment
SYNOPSIS
build [--clean|--no-init] [--rpms path1:path2:...] [--arch arch1:arch2:...] [--root buildroot] [specfile|srcrpm]
build --help
build --verify
DESCRIPTION
build is a tool to build SuSE Linux RPMs in a safe and clean way. build will install a minimal SuSE Linux as build system into some direc-
tory and will chroot to this system to compile the package. This way you don't risk to corrupt your working system (due to a broken spec
file for example), even if the package does not use BuildRoot.
build searches the spec file for a BuildRequires: line; if such a line is found, all the specified rpms are installed. Otherwise a selec-
tion of default packages are used. Note that build doesn't automatically resolve missing dependencies, so the specified rpms have to be
sufficient for the build.
If a spec file is specified on the command line, build will use this file and all other files in the directory for building the package. If
a srcrpm is specified, build automatically unpacks it for the build. If neither is given, build will use all the specfiles in the current
directory.
OPTIONS
--clean
remove the build system and reinitialize it from scratch.
--no-init
skip the build system initialization and start with build immediately.
--list-state
list rpms that would be used to create a fresh build root. Does not create the build root or perform a build.
--rpms path1:path2:path3...
Where build can find the SuSE Linux RPMs needed to create the build system. This option overrides the BUILD_RPMS environment vari-
able.
--arch arch1:arch2:arch3...
What architectures to select from the RPMs. build automatically sets this to a sensible value for your host if you don't specify
this option.
--root buildroot
Specifies where the build system is set up. Overrides the BUILD_ROOT enviroment variable.
--useusedforbuild
Tell build not to do dependency expansion, but to extract the list of packages to install from "# usedforbuild" lines or, if none
are found, from all "BuildRequires" lines. This option is useful if you want to re-build a package from a srcrpm with exactly the
same packages used for the srcrpm build.
--norootforbuild
--help Print a short help text.
--verify
verify the files in an existing build system.
.spec FILE OPTIONS
The build command interprets some special control comments in the specfile:
# norootforbuild
# needsrootforbuild
build uses either user root or user abuild in the build system to do the build. For non-SUSE distros as well as since SUSE 10.2,
the default build user is abuild. For 10.2 and before, the default build user is root. These two flags in the spec file allow to
deviate from the defaults and force-set the build user to abuild and root (for # norootforbuild and # needsrootforbuild respec-
tively.
# needsbinariesforbuild
provide the binary rpms that have been used to set up the build root in /.build.binaries within the build root.
ENVIRONMENT
BUILD_ROOT
The directory where build should install the chrooted build system. "/var/tmp/build-root" is used by default.
BUILD_RPMS
Where build can find the SuSE Linux RPMs. build needs them to create the build system. "/media/dvd/suse" is the default value
which will do the trick if you have the SuSE Linux DVD mounted.
BUILD_RPM_BUILD_STAGE
The rpm build stage (-ba, -bb, ...). This is just passed through to rpm, check the rpm manpage for a complete list and descrip-
tions. "-ba" is the default. You can use this to add more options to RPM.
SEE ALSO
rpm(1),
Maximum RPM:
http://www.rpm.org/max-rpm/
cross distribution packaging:
http://en.opensuse.org/Build_Service/cross_distribution_package_how_to
SUSE packaging standards and guidelines:
http://en.opensuse.org/Packaging
(c) 1997-2008 SuSE Linux AG Nuernberg, Germany build(1)