02-15-2013
SysV package creation, how to predefine DESTDIR
Hi Solaris experts
How to predefine the DESTDIR in a Solaris package?
Thanks
7 More Discussions You Might Find Interesting
1. Programming
My question is: what's the best way to implement mutual exclusion for a shared memory segment. I want to ensure that while updating a shared memory segment that another process will not get read part of the segment before and the other part after the update. (I also want to ensure that the update... (3 Replies)
Discussion started by: otheus
3 Replies
2. AIX
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
3. Shell Programming and Scripting
Hi Experts,
I wish to insert predefined text in front of every line and this needs to be in a loop because it is always expanding.
Before :
11111111
22222222
33333333
44444444
55555555
77777777
88888888
00000000
To be Inserted :
a=
b= (2 Replies)
Discussion started by: masayangbata
2 Replies
4. UNIX for Advanced & Expert Users
Friends,
Please let meknow, How we can find the dependancies of .dstream package & .rpm package before installation ?
For AIX, We can use the inutoc . command to create the .toc file for the bff package, What about Solaris & Linux ? (0 Replies)
Discussion started by: yb4779
0 Replies
5. Solaris
Dear All,
I am trying to build a solaris package with a variable, so that it can be installed with an environment. The prototype file contains the variables for user and group that can be parameterised during the package installation. The following is the prototype file and the error when ... (2 Replies)
Discussion started by: sanchan
2 Replies
6. Solaris
Hi,
I am creating "LSOF" solaris package from solaris "source" files. I have compiled the source file and with that i created prototype file also. Then using pkgmk command i can make the package .
In the package i am having (pkginfo pkgmap reloc) two file and one directory respectively
But... (3 Replies)
Discussion started by: Kathirvel G
3 Replies
7. SCO
Hello,
I wonder if anybody could help. I'm running SCO Xenix under Qemu on Xubuntu 16.04. I created a SYSV floppy image, but the files on it are poorly displayed when I mounted it under Xenix.
I tried to create and format this image under Ubuntu as well as under Xenix.
How could I create a... (6 Replies)
Discussion started by: Neelix
6 Replies
depend(4) File Formats depend(4)
NAME
depend - software dependencies file
DESCRIPTION
depend is an ASCII file used to specify information concerning software dependencies for a particular package. The file is created by a
software developer.
Each entry in the depend file describes a single software package. The instance of the package is described after the entry line by giving
the package architecture and/or version. The format of each entry and subsequent instance definition is:
type pkg name
(arch)version
(arch)version
...
The fields are:
type Defines the dependency type. Must be one of the following characters:
P Indicates a prerequisite for installation; for example, the referenced package or versions must be installed.
I Implies that the existence of the indicated package or version is incompatible.
R Indicates a reverse dependency. Instead of defining the package's own dependencies, this designates that another
package depends on this one. This type should be used only when an old package does not have a depend file, but
relies on the newer package nonetheless. Therefore, the present package should not be removed if the designated
old package is still on the system since, if it is removed, the old package will no longer work.
pkg Indicates the package abbreviation.
name Specifies the full package name.
(arch)version Specifies a particular instance of the software. A version name cannot begin with a left parenthesis. The instance specifi-
cations, both (arch) and version, are completely optional, but each (arch)version pair must begin on a new line that begins
with white space. A null version set equates to any version of the indicated package.
EXAMPLES
Example 1: Sample of depend file
Here are the contents of a sample depend file, for the SUNWftpr (FTP Server) package, stored in /var/sadm/pkg/SUNWftpr/install:
P SUNWcar Core Architecture, (Root)
P SUNWkvm Core Architecture, (Kvm)
P SUNWcsr Core Solaris, (Root)
P SUNWcsu Core Solaris, (Usr)
P SUNWcsd Core Solaris Devices
P SUNWcsl Core Solaris Libraries
R SUNWftpu FTP Server, (Usr)
SEE ALSO
pkginfo(4)
Application Packaging Developer's Guide
SunOS 5.10 4 Oct 1996 depend(4)