pkg - updateable packages


 
Thread Tools Search this Thread
Operating Systems Solaris pkg - updateable packages
# 1  
Old 03-13-2008
pkg - updateable packages

Hello,
I'm creating some installation packages for Solaris 9 and I wonder whether or not the Solaris pkg system support update operation.

Creating Solaris Packages says
Quote:
The package tools allow you to install, update and remove software easily
But I havent found out how update works.

Like in debian packages, I'd like to detect in the "preinstall" script that it is an update and not a new install of the package.

Thanks for your advices,
regards,
Tex.
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Solaris

Pkg update 11.2

Got a repo server with a combined 11.2/11.3 repository. I want to update latest security patches on server A (which is 11.2). I dont want to upgrade to 11.3 (app reasons). If I do pkg update all - is there any danger this will happen? If so, how to proceed? (2 Replies)
Discussion started by: psychocandy
2 Replies

2. Solaris

# pkg publisher gives bash: pkg: command not found

This is the operating system im using Oracle Solaris 10 9/10 s10s_u9wos_14a SPARC I need to install some packages by setting local repository While i run the below command # pkg publisher command returns bash: pkg: command not found while looking for /usr/bin/pkg i get bash:... (2 Replies)
Discussion started by: babinlonston
2 Replies

3. Solaris

Pkg update from a local repos

I have a local repos on my dev/tst server. pkg server is online and I can query against it on the local server and any LDOMS and zones hosted on the same server. I have another identical Solaris server that should be accessing the pkg repos via the local network. showmount -e from the local (but... (0 Replies)
Discussion started by: os2mac
0 Replies

4. Solaris

Pkg problem, one zone trying pkg.Oracle.com on port 1008

Hi Solaris Experts, The pkg utility on one of my non-global zones has stopped working, it's trying to connect to port 1008 at pkg.oracle.com I was using pkg successfully from this zone, but now it's showing this error: lzone1 $ pkg search xterm pkg: Some repositories failed to respond... (4 Replies)
Discussion started by: ad101
4 Replies

5. Solaris

How extract SUNWexplo.7.1.pkg & SUNWexplu.7.1.pkg from install_stb.sh?

Hi all, Could please guideas how to extract SUNWexplo.7.2.pkg & SUNWexplu.7.2.pkg from install_stb.sh. I need to upgrade my Sun Explorer to 7.2 version from 7.1 . This what written in read me file about its installation: The Lightweight Availability Collection Tool (LWACT) is no... (1 Reply)
Discussion started by: manalisharmabe
1 Replies

6. Slackware

Find Slackware Packages - packages.acl.org.ua

Hi! Let me introduce a project for find and download Slackware packages and browse Slackware repositories. The site provides following features: * Large, daily updated database with RPM, DEB, TGZ, TXZ packages for well-known repositories of the Slackware, Fedora, CentOS, RHEL, Debian,... (2 Replies)
Discussion started by: lystor
2 Replies

7. Solaris

137481-02 pkg

can anyone download this solaris pkg and email to me, it wont let me download it anymore from sunsolve. 137481-02 (1 Reply)
Discussion started by: dan7225
1 Replies

8. Solaris

pkg-get errors

To day i installed boltpkg, hiow ever when i run either a pkg-get install or a pkg-get -u pkg-get re turns the following errors. pkg-get -u WARNING: no catalog file for site ftp.sunfreeware.com Updating catalog file first Getting catalog... ld.so.1: wget: fatal: libssl.so.0.9.8: open... (3 Replies)
Discussion started by: FloridaBSD
3 Replies

9. Solaris

How to remove a pkg ,urgent!!

HI all, I would like to know, how we can remove a package? I know that pkgrm will do the job ,but specifying the right kinda package is important.. And i dont know how to figure that one out? Eg:if i have installed a pkg called virtualbox, If i do, pkgrm SUNWvirtualbox ,it says "no such file... (2 Replies)
Discussion started by: wrapster
2 Replies

10. Solaris

pkgadd pkg to an new directory

hi guys, I am wondering instead installing to the default directory, how can I install a package using pkgadd command to a specified directory? I am using solaris 9, thanks (1 Reply)
Discussion started by: fedora
1 Replies
Login or Register to Ask a Question
PKG_INSTALL.CONF(5)					      BSD File Formats Manual					       PKG_INSTALL.CONF(5)

NAME
pkg_install.conf -- configuration file for package installation tools DESCRIPTION
The file pkg_install.conf contains system defaults for the package installation tools as a list of variable-value pairs. Each line has the format VARIABLE=VALUE. If the value consists of more than one line, each line is prefixed with VARIABLE=. The current value of a variable can be checked by running pkg_admin config-var VARIABLE Some variables are overriden by environmental variables of the same name. Those are marked by (*). The following variables are supported: ACCEPTABLE_LICENSES Space-separated list of licenses packages are allowed to carry. License names are case-sensitive. ACTIVE_FTP Force the use of active FTP. CACHE_INDEX Cache directory listenings in memory. This avoids retransfers of the large directory index for HTTP and is enabled by default. CERTIFICATE_ANCHOR_PKGS Path to the file containing the certificates used for validating binary packages. A package is trusted when a certificate chain ends in one of the certificates contained in this file. The certificates must be PEM-encoded. CERTIFICATE_ANCHOR_PKGVULN Analogous to CERTIFICATE_ANCHOR_PKGS. The pkg-vulnerabilities is trusted when a certificate chain ends in one of the certificates contained in this file. CERTIFICATE_CHAIN Path to a file containing additional certificates that can be used for completing certificate chains when validating binary packages or pkg-vulnerabilities files. CHECK_LICENSE Check the license conditions of packages before installing them. Supported values are: no The check is not performed. yes The check is performed if the package has license conditions set. always Passing the license check is required. Missing license conditions are considered an error. CHECK_END_OF_FILE During vulnerability checks, consider packages that have reached end-of-life as vulnerable. This option is enabled by default. CHECK_VULNERABILITIES Check for vulnerabilities when installing packages. Supported values are: never No check is performed. always Passing the vulnerability check is required. A missing pkg-vulnerabilities file is considered an error. interactive The user is always asked to confirm installation of vulnerable packages. CONFIG_CACHE_CONNECTIONS Limit the global connection cache to this value. For FTP this is the number of sessions without active command. For HTTP this is the number of connections open with keep-alive. CONFIG_CACHE_CONNECTIONS_HOST Like CONFIG_CACHE_CONNECTIONS, but limit the number of connections to the host as well. See fetch(3) for further details DEFAULT_ACCEPTABLE_LICENSES Space-separated list of common Free and Open Source licenses packages are allowed to carry. The default value contains all OSI approved licenses in pkgsrc on the date pkg_install was released. License names are case-sensitive. GPG Path to gpg(1), which can be used to verify the signature in the pkg-vulnerabilities file when running pkg_admin check-pkg-vulnerabilities -s or pkg_admin fetch-pkg-vulnerabilities -s It can also be used to verify and sign binary packages. GPG_KEYRING_PKGVULN Non-default keyring to use for verifying GPG signatures of pkg-vulnerabilities. GPG_KEYRING_SIGN Non-default keyring to use for signing packages with GPG. GPG_KEYRING_VERIFY Non-default keyring to use for verifying GPG signature of packages. GPG_SIGN_AS User-id to use for signing packages. IGNORE_PROXY Use direct connections and ignore FTP_PROXY and HTTP_PROXY. IGNORE_URL One line per advisory which should be ignored when running pkg_admin audit The URL from the pkg-vulnerabilities file should be used as value. PKG_DBDIR (*) Location of the packages database. This option is always overriden by the argument of the -K option. PKG_PATH (*) Search path for packages. The entries are separated by semicolon. Each entry specifies a directory or URL to search for packages. PKG_REFCOUNT_DBDIR (*) Location of the package reference counts database directory. The default value is ${PKG_DBDIR}.refcount. PKGVULNDIR Directory name in which the pkg-vulnerabilities file resides. Default is ${PKG_DBDIR}. PKGVULNURL URL which is used for updating the local pkg-vulnerabilities file when running pkg_admin fetch-pkg-vulnerabilities The default location is ftp.NetBSD.org using HTTP. Note: Usually, only the compression type should be changed. Currently supported are uncompressed files and files compressed by bzip2(1) (.bz2) or gzip(1) (.gz). VERBOSE_NETIO Log details of network IO to stderr. VERIFIED_INSTALLATION Set trust level used when installation. Supported values are: never No signature checks are performed. always A valid signature is required. If the binary package can not be verified, the installation is terminated trusted A valid signature is required. If the binary package can not be verified, the user is asked interactively. interactive The user is always asked interactively when installing a package. FILES
/etc/pkg_install.conf Default location for the file described in this manual page. SEE ALSO
pkg_add(1), pkg_admin(1) pkg_create(1), pkg_delete(1), pkg_info(1) BSD
November 13, 2010 BSD