Sponsored Content
Operating Systems Solaris Package creation problems with Source files Post 302660143 by Kathirvel G on Friday 22nd of June 2012 06:28:31 AM
Old 06-22-2012
Package creation problems with Source files

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 what is the problem i am facing is when i install the package using "pkgadd -d /directory" the output shows its successfully installed. I dont know where the package is installed and "lsof command" doesnt show any output.

Please help me to find where i am going wrong. I willing to give more updates on this on your query.

Thanks,
G.Kathirvel
 

9 More Discussions You Might Find Interesting

1. UNIX Desktop Questions & Answers

Solaris 10 - Compiling package from source? Different from pkgadd?

Hey everyone, I'm using a SPARC based Solaris 10 5/09 machine and want to install PHP support to it. I already have mysql and apache( came with OS, just started the proccess) installed, so this is the last thing before I can get to learning development :) However, there's something I'm not sure... (1 Reply)
Discussion started by: agummad
1 Replies

2. AIX

How to compile a package in AIX when we download its source?

How to compile a package surce in AIX when we download its source? (2 Replies)
Discussion started by: johnveslin
2 Replies

3. 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

4. Solaris

Solaris10 Package Creation with variable

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

5. Windows & DOS: Issues & Discussions

Problems With User Creation Script

Hello everyone, I've been attempting to make a program which creates user accounts from a file which contains the usernames required. It also checks if the directory of the username exists in the C:\Users directory and then is going to give the option to delete the directory, or rename it, this... (1 Reply)
Discussion started by: charlieabee
1 Replies

6. Solaris

SysV package creation, how to predefine DESTDIR

Hi Solaris experts How to predefine the DESTDIR in a Solaris package? Thanks (1 Reply)
Discussion started by: ./hari.sh
1 Replies

7. AIX

XVFB Source package for AIX

Please send me link for XVFB Source package for AIX (3 Replies)
Discussion started by: prathap.g
3 Replies

8. AIX

PowerVM/lpar creation problems

Hi, I'm a newbie to PowerVM and LPARs ( I work with VmWare and Oracle VM Server for Sparc) .recently we purchased an 8202-e4b server, with two enclosures for add'l disk capacity. it is licensed for PowerVM standard,came preloaded as such, AIX 7.1. I've set up HMC v8.2, and run it through a VM on... (30 Replies)
Discussion started by: computron
30 Replies

9. Solaris

IPS custom package user source

Hello guys, I'm new to this forum and got a question which may be quite uncommon. I created a custom IPS package (using this How to) with some software I have to install frequently to different Solaris 11 zones (MongoDB to be precise). This software will be installed under "/opt/mongodb" and... (1 Reply)
Discussion started by: dheitepriem
1 Replies
pkgmk(1)							   User Commands							  pkgmk(1)

NAME
pkgmk - produce an installable package SYNOPSIS
pkgmk [-o] [-a arch] [-b base_src_dir] [-d device] [-f prototype] [-l limit] [-p pstamp] [-r root_path] [-v version] [variable=value...] [pkginst] DESCRIPTION
The pkgmk utility produces an installable package to be used as input to the pkgadd(1M) command. The package contents will be in directory structure format. The command uses the package prototype(4) file as input and creates a pkgmap(4) file. The contents for each entry in the prototype file is copied to the appropriate output location. Information concerning the contents (checksum, file size, modification date) is computed and stored in the pkgmap file, along with attribute information specified in the prototype file. pkgmk searches for the files listed in the prototype(4) file as described in the following conditions. Note: If a prototype file contains the explicit location of the file to include in the package, then the following search explanations do not apply. 1. If neither -b nor -r options are specified, the file name component of each file path listed in the prototype(4) file is expected to be found in the same directory as the prototype(4) file 2. If -b is specified as a relative path (without a leading "/"), then base_src_dir is prepended to the relative file paths from the pro- totype(4) file. The resulting path is searched for in the root_path directories. If a root_path is not specified, it defaults to "/". 3. If -b is specified as an absolute path (with a leading "/"), then base_src_dir is prepended to the relative paths from the prototype(4) file and the result is the location of the file. root_path is not searched. 4. If -r is specified, then full file paths are used from the prototype(4) file. Relative paths have base_src_dir prepended. If base_src_dir is not specified, it defaults to "". The resulting path is searched for in each directory of the root_path. If you created your prototype file using "pkgproto a/relative/path" or "pkgproto a/relative/path=install/path", then you should use the -r root_path option to specify the location of a/relative/path so that pkgmk can correctly locate your source files. OPTIONS
The following options are supported: -a arch Overrides the architecture information provided in the pkginfo(4) file with arch. -b base_src_dir Prepends the indicated base_src_dir to locate relocatable objects on the source machine. Use this option to search for all objects in the prototype file. pkgmk expects to find the objects in /base_src_dir or to locate the objects by use of the -b and -r options, respectively. -d device Creates the package on device. device can be an absolute directory pathname or the identifiers for a floppy disk or remov- able disk (for example, /dev/diskette). The default device is the installation spool directory (/var/spool/pkg). -f prototype Uses the file prototype as input to the command. The default prototype filename is [Pp]rototype. -l limit Specifies the maximum size in 512 byte blocks of the output device as limit. By default, if the output file is a directory or a mountable device, pkgmk will employ the df(1M) command to dynamically calculate the amount of available space on the output device. This option is useful in conjunction with pkgtrans(1) to create a package with a datastream format. -o Overwrites the same instance; package instance will be overwritten if it already exists. -p pstamp Overrides the production stamp definition in the pkginfo(4) file with pstamp. -r root_path Uses the indicated root_path with the source pathname appended to locate objects on the source machine, using a comma (,) as the separator for the path elements. If this option is specified, look for the full destination path in each of the directories specified. If neither -b nor -r is specified, look for the leaf filename in the current directory. -v version Overrides the version information provided in the pkginfo(4) file with version. variable=value Places the indicated variable in the packaging environment. (See prototype(4) for definitions of variable specifications.) OPERANDS
The following operand is supported: pkginst A package designation by its instance. An instance can be the package abbreviation or a specific instance (for example, inst.1 or inst.2). All instances of a package can be requested by inst.*. The asterisk character (*) is a special character to some shells and may need to be escaped. In the C-Shell, "*" must be surrounded by single quotes (') or preceded by a backslash (). EXIT STATUS
The following exit values are returned: 0 Successful completion. >0 An error occurred. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ SEE ALSO
pkgparam(1), pkgproto(1), pkgtrans(1), uname(1), df(1M), pkgadd(1M), pkginfo(4), pkgmap(4), prototype(4), attributes(5) Application Packaging Developer's Guide NOTES
Architecture information is provided on the command line with the -a option or in the prototype(4) file. If no architecture information is supplied, pkgmk uses the output of uname -m (see uname(1)). Version information is provided on the command line with the -v option or in the pkginfo(4) file. If no version information is supplied, a default based on the current date will be provided. Command line definitions for both architecture and version override the prototype(4) definitions. SunOS 5.10 10 Jan 2001 pkgmk(1)
All times are GMT -4. The time now is 02:00 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy