Sponsored Content
Top Forums UNIX for Advanced & Expert Users Debian Package Management "Inside" Question Post 302931195 by sea on Sunday 11th of January 2015 06:36:54 PM
Old 01-11-2015
I dont know dkpg, but with the aim to bring some light onto the question, here's was i would conclude in a simple way.
So, what i say now, might be technical incorrect but is thought to get a raw draft of the greater image.

There are 3 package types.
1) compiled (i386/x86_64, ..., any ARCH specific)
2) copy files (noarch, scripts)
3) devel/debug and source packages (they are NOT the same, and usualy are not 'usable' for regular users)

Obviously, everything that needs to be compiles, needs to be labeled which ARCH is was compiled for.
A packaging system, such as dkpg/apt-get/rpm/aur... offer various tasks to simplify the process of getting sourcecode into a working package for the system.
This includes the use of macros inside of the (on redhat systems its calledSmilie specfiles (for rpm packages, dont know the proper term for apt-get-configuration-deb-files.

For RPM specfiles, if one doesnt pass a certing option within that file, the packaging system automaticly assumes that the packages supports the same arch as the host system is.
This said, it also adds the according string to the package, usualy at the right place, unless manualy modified.
In specfiles, the required option to add would be: BuildArch: noarch if you want to make a package of scripts, images, html docs or manpages or just anything that doesnt need to be compiled to be usefull.

I dont know much about dkpg based systems, but i would assume, when you end up having both, 32 and (as in: or) 64 bit packages, there is somewhere an error in your settings or scripts.

Usualy, but not always, an applications requires only 1 kind of an arch dependency.
This said, here are some questions:

When did it last work?
What did you change since?
Were there any other improvements? ("damages")
Did you copy paste code?
Changed code or project configuration?

Hope this helps
 

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

"Process management" question

This one will show how "wet behind the ears" I am but here it goes... Suppose my boss wants me to run an app every day from the command line. The command line statement looks like this: $> my_executable_program -my_parameter file > my_outfile Let's say that one day, I do this: $>... (1 Reply)
Discussion started by: alan
1 Replies

2. Debian

Debian: doubt in "top" %CPU and "sar" output

Hi All, I am running my application on a dual cpu debian linux 3.0 (2.4.19 kernel). For my application: <sar -U ALL> CPU %user %nice %system %idle ... 10:58:04 0 153.10 0.00 38.76 0.00 10:58:04 1 3.88 0.00 4.26 ... (0 Replies)
Discussion started by: jaduks
0 Replies

3. UNIX and Linux Applications

A question/problem about oracle "tns listener" and "enterprise manager"

hi, I have * an IBM P550 machine, * an AIX 5.3 running on it and * an oracle database, already installed on it. The problem (or question of my own) is: Oracle tns listener, "CT_LISTENER", and the enterprise manager (EM) of the instance, which is uniq instance and called... (0 Replies)
Discussion started by: talipk
0 Replies

4. UNIX for Advanced & Expert Users

A question/problem about oracle "tns listener" and "enterprise manager"

hi, I have a problem about the Oracle related components. I'm not able to find any answer yet, and waiting for your responses... Here is the configuration of my system: * an IBM P550 machine, * an AIX 5.3 running on it and * an oracle database, already installed on it. The problem (or... (1 Reply)
Discussion started by: talipk
1 Replies

5. AIX

mkinstallp package creation failing "no such file: ./usr/lpp/<package name>/inst_root"

Hello, I'm trying to build a (bff) package from an already installed program (clam antivirus) using mkinstallp. However, mkinstallp fails with "no such file: ./usr/lpp/<package name>/inst_root" I'm not sure why all files get created ok except for these particular ones. Any help would be... (2 Replies)
Discussion started by: omonte
2 Replies

6. Shell Programming and Scripting

awk command to replace ";" with "|" and ""|" at diferent places in line of file

Hi, I have line in input file as below: 3G_CENTRAL;INDONESIA_(M)_TELKOMSEL;SPECIAL_WORLD_GRP_7_FA_2_TELKOMSEL My expected output for line in the file must be : "1-Radon1-cMOC_deg"|"LDIndex"|"3G_CENTRAL|INDONESIA_(M)_TELKOMSEL"|LAST|"SPECIAL_WORLD_GRP_7_FA_2_TELKOMSEL" Can someone... (7 Replies)
Discussion started by: shis100
7 Replies

7. Shell Programming and Scripting

Failure: if grep "$Var" "$line" inside while read line loop

Hi everybody, I am new at Unix/Bourne shell scripting and with my youngest experiences, I will not become very old with it :o My code: #!/bin/sh set -e set -u export IFS= optl="Optl" LOCSTORCLI="/opt/lsi/storcli/storcli" ($LOCSTORCLI /c0 /vall show | grep RAID | cut -d " "... (5 Replies)
Discussion started by: Subsonic66
5 Replies

8. Shell Programming and Scripting

Bash script - Print an ascii file using specific font "Latin Modern Mono 12" "regular" "9"

Hello. System : opensuse leap 42.3 I have a bash script that build a text file. I would like the last command doing : print_cmd -o page-left=43 -o page-right=22 -o page-top=28 -o page-bottom=43 -o font=LatinModernMono12:regular:9 some_file.txt where : print_cmd ::= some printing... (1 Reply)
Discussion started by: jcdole
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)
All times are GMT -4. The time now is 10:35 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy