Displaying Solaris IPS package dependency graphs


 
Thread Tools Search this Thread
Operating Systems Solaris Displaying Solaris IPS package dependency graphs
# 1  
Old 02-07-2014
Question Displaying Solaris IPS package dependency graphs

What do people think of this tool? pkgtree - for displaying a visual representation of Solaris IPS package dependencies.
Login or Register to Ask a Question

Previous Thread | Next Thread

9 More Discussions You Might Find Interesting

1. Solaris

Solaris 11 - Automatically update local IPS repository

Hi guys, I've got a local IPS repository on server 1 (local server in the basement) and a second one on server 2 in another data center. Both servers act as repository servers for their locations. The publisher list is like this pkg publisher PUBLISHER TYPE STATUS... (4 Replies)
Discussion started by: dheitepriem
4 Replies

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

3. Solaris

Updating my Solaris 11 IPS

Hi experts, I have an X86 as my IPS server running ( uname -a SunOS 5.11 11.1 i86pc i386 i86pc). the IPS has the following package version: prdb01b:~# pkg list -fa entire NAME (PUBLISHER) VERSION IFO entire ... (0 Replies)
Discussion started by: afadaghi
0 Replies

4. Solaris

Solaris IPS problems

Hi guys, long time no see Today I installed Oracle Solaris 11.11 in virtualbox. My machine needs to be bulletproof for our production databases but :D First problem is that I can't install anything using IPS where publisher is solars, default freeware repo for Oracle Solaris. I need... (9 Replies)
Discussion started by: solaris_user
9 Replies

5. Solaris

Package installation in Solaris 11

I have Solaris-11 and installed few non global zones inside it. I saw many of the packages are not installed in non global zone after installing it. root@pos_ddr01 # pkg list | wc -l 479 root@pos_ddr01 # root@pos_ddr01-zkmq01:~# pkg list | wc -l 206 root@pos_ddr01-zkmq01:~# I can... (1 Reply)
Discussion started by: solaris_1977
1 Replies

6. Solaris

solaris 11 - creating a second IPS repo

I need some help getting a IPS repo setup for custom internal packages. we already have an IPS for the oracle solaris package. what I want is a repo called BOB that can be used for packages internal to company BOB. I think I have created a repo called BOB, but it's not setup in the network... (1 Reply)
Discussion started by: robsonde
1 Replies

7. Solaris

Solaris 11 - custom publisher IPS

Hi all, we are starting to build some basic infrastructure for using solaris 11. I have built an IPS of solaris packages from the DVD images. what I want to do next is create a repository of custom packages. so in that case I want a publisher of "my-company-name" and not solaris. can... (1 Reply)
Discussion started by: robsonde
1 Replies

8. UNIX for Dummies Questions & Answers

How to assign multiple IPs to Aggregated interface in Solaris 10?

I have 2 physical interfaces (bnx0 and bnx1) aggregated into aggr1. I need to assign second IP, and normally I know how to do it to physical interface (i.e. bnx0:1) however same trick (aggr1:1) is not working. Is there any way to do it? (0 Replies)
Discussion started by: bratan
0 Replies

9. UNIX for Advanced & Expert Users

How to find dependancies of .dstream package (Solaris) & .rpm package( linux)

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
Login or Register to Ask a Question
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 speci- fications, 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.11 4 Oct 1996 depend(4)