10 More Discussions You Might Find Interesting
1. Solaris
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
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
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
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
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
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
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
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
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
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
ghc-pkg(1) General Commands Manual ghc-pkg(1)
NAME
ghc-pkg - GHC Haskell Cabal package manager
SYNOPSIS
ghc-pkg action [OPTION]...
DESCRIPTION
A package is a library of Haskell modules known to the compiler. The ghc-pkg tool allows adding or removing them from a package database.
By default, the system-wide package database is modified, but alternatively the user's local package database or another specified file can
be used.
To make a package available for ghc, ghc-pkg can be used to register it. Unregistering it removes it from the database. Also, packages
can be hidden, to make ghc ignore the package by default, without uninstalling it. Exposing a package makes a hidden package available.
Additionally, ghc-pkg has various commands to query the package database.
Where a package name is required, the package can be named in full including the version number (e.g. network-1.0), or without the version
number. Naming a package without the version number matches all versions of the package; the specified action will be applied to all the
matching packages. A package specifier that matches all version of the package can also be written pkg-*, to make it clearer that multiple
packages are being matched.
ACTIONS
register filename|-
Register the package using the specified installed package description.
update filename|-
Register the package, overwriting any other package with the same name.
unregister pkg-id
Unregister the specified package.
expose pkg-id
Expose the specified package.
hide pkg-id
Hide the specified package
list [pkg]...
List registered packages in the global database, and also the user database if --user is given. If a package name is given all the
registered versions will be listed in ascending order. Accepts the --simple-output flag.
dot Generate a graph of the package dependencies in a form suitable for input for the graphviz tools. For example, to generate a PDF of
the dependency graph:
dot tred dot -Tpdf >pkgs.pdf
find-module module
List registered packages exposing module module in the global database, and also the user database if --user is given. All the reg-
istered versions will be listed in ascending order. Accepts the --simple-output flag.
latest pkg-id
Prints the highest registered version of a package.
check Check the consistency of package dependencies and list broken packages. Accepts the --simple-output flag.
describe pkg
Give the registered description for the specified package. The description is returned in precisely the syntax required by ghc-pkg
register.
field pkg field
Extract the specified field of the package description for the specified package. Accepts comma-separated multiple fields.
dump Dump the registered description for every package. This is like ghc-pkg describe '*', expect that it is intended to be used by tools
that parse the results, rather than humans.
recache
Regenerate the package database cache. This command should only be necessary if you added a package to the database by dropping a
file into the database directory manyally. By default, the global DB is recached; to recache a different DB use --user or --pack-
age-conf as appropriate.
OPTIONS
When asked to modify a database (register, unregister, update, hide, expose, and also check), ghc-pkg modifies the global database by
default. Specifying --user causes it to act on the user database, or --package-conf can be used to act on another database entirely. When
multiple of these options are given, the rightmost one is used as the database to act upon.
Commands that query the package database (list, latest, describe, field) operate on the list of databases specified by the flags
--user, --global, and --package-conf. If none of these flags are given, the default is --global --user.
--user Use the current user's package database.
--global
Use the global package database.
-f FILE, --package-conf=FILE
Use the specified package config file.
--global-conf=FILE
Location of the global package config.
--force
Ignore missing dependencies, directories, and libraries.
--force-files
Ignore missing directories and libraries only.
-g, --auto-ghc-libs
Automatically build libs for GHCi (with register).
-?, --help
Display a help message and exit.
-V, --version
Output version information and exit.
--simple-output
Print output in easy-to-parse format for some commands.
--names-only
Only print package names, not versions; can only be used with list --simple-output.
--ignore-case
Ignore case for substring matching.
ENVIRONMENT VARIABLES
GHC_PACKAGE_PATH
The GHC_PACKAGE_PATH environment variable may be set to a :-separated list of files containing package databases. This list of pack-
age databases is used by ghc and ghc-pkg, with earlier databases in the list overriding later ones. This order was chosen to match
the behaviour of the PATH environment variable; think of it as a list of package databases that are searched left-to-right for pack-
ages.
If GHC_PACKAGE_PATH ends in a separator, then the default user and system package databases are appended, in that order. e.g. to
augment the usual set of packages with a database of your own, you could say:
export GHC_PACKAGE_PATH=$HOME/.my-ghc-packages.conf:
To check whether your GHC_PACKAGE_PATH setting is doing the right thing, ghc-pkg list will list all the databases in use, in the
reverse order they are searched.
FILES
Both of these locations are changed for Debian. Upstream still keeps these under /usr. Some programs may refer to that, but look in /var
instead.
/var/lib/ghc/package.conf
Global package.conf file.
/var/lib/ghc/package.conf.d/
Directory for library specific package.conf files. These are added to the global registry.
SEE ALSO
ghc(1), runghc(1), hugs(1).
AUTHOR
This manual page was written by Kari Pahula <kaol@debian.org>, for the Debian project (and may be used by others).
2010-01-27 ghc-pkg(1)