Sponsored Content
The Lounge What is on Your Mind? Is it bad to Install the Whole Repository? Post 302826963 by Danneskjold on Thursday 27th of June 2013 04:02:29 PM
Old 06-27-2013
Is it bad to Install the Whole Repository?

Hey Guys,
This week I installed Solaris for the first time, (trying to fix my ZFS array with some movies on it) and I noticed that unlike Linux or FreeBSD, their package management application almost encourages installing whole categories of software at a time. Theirs even a keyboard shortcut for selecting a category - like "Drivers" or "Web Services." It got me thinking, is there any harm in just installing an entire repository like that? Disk space & bandwidth aren't so scarce in most cases to make the few tens of gig's matter and it can be such a pain to have to install a new utility or library every 4 minutes when changing things up . . . . And also, if one installed everything beforehand, they wouldn't have worry about installation troubles on a tool or such during a downtime.

Now granted . . . Solaris has at most 1/10th the packages as FreeBSD or Mint . . . . but it's till something to think about. Who doesn't want three versions of every every slideshow application ever written AND the braille typesetting tools in 40 languages on the same laptop? Well. I'm gonna give it a try and see anyhow.
 

10 More Discussions You Might Find Interesting

1. SuSE

Best Repository for SUSE 10.1 install?

I've made a few attempts at an OpenSuse10.1 clean install using a boot.iso and network repository install dir. I've succesfully done a few network installs before and know what I'm doing with the procedure, however I seem to be getting problems with the connection to the remote repository. It's... (0 Replies)
Discussion started by: Mark Ward
0 Replies

2. UNIX for Advanced & Expert Users

Script to search a bad record in a file then put the record in the bad file

I need to write a script that can find a bad record (for example: there is date field colom but value provided in the file for this field is N/A) then script shoud searches this pattern and then insert the whole record into the bad file. Example: File1 Name designation dateOfJoining... (1 Reply)
Discussion started by: shilendrajadon
1 Replies

3. Shell Programming and Scripting

Script to search a bad record in a file then put the record in the bad file

I need to write a script that can find a bad record (for example: there is date field colom but value provided in the file for this field is N/A) then script shoud searches this pattern and then insert the whole record into the bad file. Example: File1 Name designation dateOfJoining... (2 Replies)
Discussion started by: shilendrajadon
2 Replies

4. AIX

bos.rte.5.2.0.10 - Failure to Install (/usr/lib/methods/cfgsf bad permissions)

I have a RS/6000 B80 which just had a disk failure; I've added a new drive and am in the process of rebuilding. I have reinstalled AIX 5.2 and am now looking to begin updating. (fyi this will be the second time I have attempted to rebuild this machine, the first time i installed ML 5200-10 and... (1 Reply)
Discussion started by: wesiman
1 Replies

5. Linux

install macbook pro fedora10 ???((<<if can install, how to install? >> ))

If may install can Tells everybody ??? (0 Replies)
Discussion started by: kzBSD
0 Replies

6. Shell Programming and Scripting

Why I get bad bad substitution when using eval?

Why I get bad replace when using eval? $ map0=( "0" "0000" "0") $ i=0 $ eval echo \${map$i} 0000 $ a=`eval echo \${map$i}` !!!error happens!!! bash: ${map$i}: bad substitution How to resolve it ? Thanks! (5 Replies)
Discussion started by: 915086731
5 Replies

7. Red Hat

Trying to install boost 1.4.1 without success maybe yum repository is wrong

Hi I following the tutorial to install boost 1.4.1 in centos 5.6 32 bit But without success maybe it doesn't find it in my repository in yum , but also when I compile the lib It doesn't find the libs . The tutorial link: Compiling gearman on CentOS 5.6 - gearman | Google Groups the error... (1 Reply)
Discussion started by: umen
1 Replies

8. Red Hat

Yum cannot install from repository

Hi guys, thanks for you help on this issue. I built a dvd repository on my server and when I try to install a package from it, I get this error ftp://10.0.0.12/pub/Packages/httpd-2.2.15-26.el6.x86_64.rpm: PYCURL ERROR 9 - "Server denied you to change to the given directory" I will... (2 Replies)
Discussion started by: cjashu
2 Replies

9. Red Hat

Error: Cannot retrieve repository metadata (repomd.xml) for repository: InstallMedia.

Most of my commands are returning this error on RHEL 6 64 bit: Also I tried installing many sofwtares, but it fails to correctly work. For example I treid installing dos2unix: # rpm -ivh dos2unix-5.3.3-5.ram0.98.src.rpm 1:dos2unix warning: user mockbuild does not... (0 Replies)
Discussion started by: India_2014
0 Replies

10. SuSE

Repository out of date.

I get this message when attempting to update OpenSUSE 42.2: Error building the cache: Warning: Repository 'Main Update Repository' appears to be outdated. Consider using a different mirror or server. Nothing to do. What's happening? (2 Replies)
Discussion started by: geos0xAA55
2 Replies
PKG(7)						       BSD Miscellaneous Information Manual						    PKG(7)

NAME
pkg -- a utility for manipulating packages SYNOPSIS
pkg <command> pkg add [-f] <pkg.txz> pkg -N pkg bootstrap [-f] DESCRIPTION
pkg is the package management tool. It is used to manage local packages installed from ports(7) and install/upgrade packages from remote repositories. To avoid backwards incompatibility issues, the actual pkg(8) tool is not installed in the base system. The first time invoked, pkg will bootstrap the real pkg(8) from a remote repository. pkg <command> If pkg(8) is not installed yet, it will be fetched, have its signature verified, installed, and then have the original command forwarded to it. If already installed, the command requested will be forwarded to the real pkg(8). pkg add [-f] <pkg.txz> Install pkg(8) from a local package instead of fetching from remote. If a pkg.txz.sig file exists and signature checking is enabled, then the signature will be verified before installing the package. If the -f flag is specified, then pkg(8) will be installed regardless if it is already installed. pkg -N Do not bootstrap, just determine if pkg(8) is actually installed or not. Returns 0 and the number of packages installed if it is, otherwise 1. pkg bootstrap [-f] Attempt to bootstrap and do not forward anything to pkg(8) after it is installed. If the -f flag is specified, then pkg(8) will be fetched and installed regardless if it is already installed. CONFIGURATION
Configuration varies in whether it is in a repository configuration file or the global configuration file. Repository configuration can be stored in /etc/pkg/FreeBSD.conf in the following format: FreeBSD: { url: "pkg+http://pkg.FreeBSD.org/${ABI}/latest", mirror_type: "srv", signature_type: "none", fingerprints: "/usr/share/keys/pkg", enabled: yes } url Refer to PACKAGESITE in ENVIRONMENT mirror_type Refer to MIRROR_TYPE in ENVIRONMENT signature_type Refer to SIGNATURE_TYPE in ENVIRONMENT fingerprints Refer to FINGERPRINTS in ENVIRONMENT enabled Defines whether this repository should be used or not. Valid values are yes, true, 1, no, false, 0. Global configuration can be stored in /usr/local/etc/pkg.conf in the following format: PACKAGESITE: "pkg+http://pkg.FreeBSD.org/${ABI}/latest", MIRROR_TYPE: "srv", SIGNATURE_TYPE: "none", FINGERPRINTS: "/usr/share/keys/pkg", ASSUME_ALWAYS_YES: "yes" REPOS_DIR: ["/etc/pkg", "/usr/local/etc/pkg/repos"] Reference ENVIRONMENT for each variable. ENVIRONMENT
The following environment variables can be set to override the settings from the pkg.conf file used. MIRROR_TYPE This defines which mirror type should be used. Valid values are SRV, HTTP, NONE. ABI This defines the ABI for the package to be installed. Default ABI is determined from /bin/sh. ASSUME_ALWAYS_YES If set, no confirmation will be asked when bootstrapping pkg(8). SIGNATURE_TYPE If set to FINGERPRINTS then a signature will be required and validated against known certificate fingerprints when boot- strapping pkg(8). FINGERPRINTS If SIGNATURE_TYPE is set to FINGERPRINTS this value should be set to the directory path where known fingerprints are located. PACKAGESITE The URL that pkg(8) and other packages will be fetched from. REPOS_DIR Comma-separated list of directories that should be searched for repository configuration files. FILES
Configuration is read from the files in the listed order. This path can be changed by setting REPOS_DIR. The last enabled repository is the one used for bootstrapping pkg(8). /usr/local/etc/pkg.conf /etc/pkg/FreeBSD.conf /usr/local/etc/pkg/repos/*.conf EXAMPLES
Some examples are listed here. The full list of available commands are available in pkg(8) once it is bootstrapped. Search for a package: $ pkg search perl Install a package: % pkg install perl List installed packages: $ pkg info Upgrade from remote repository: % pkg upgrade List non-automatic packages: $ pkg query -e '%a = 0' %o List automatic packages: $ pkg query -e '%a = 1' %o Delete an installed package: % pkg delete perl Remove unneeded dependencies: % pkg autoremove Change a package from automatic to non-automatic, which will prevent autoremove from removing it: % pkg set -A 0 perl Change a package from non-automatic to automatic, which will make autoremove allow it be removed once nothing depends on it: % pkg set -A 1 perl Create package file from an installed package: % pkg create -o /usr/ports/packages/All perl Determine which package installed a file: $ pkg which /usr/local/bin/perl Audit installed packages for security advisories: $ pkg audit Check installed packages for checksum mismatches: # pkg check -s -a Check for missing dependencies: # pkg check -d -a SEE ALSO
ports(7), pkg(8) HISTORY
The pkg command first appeared in FreeBSD 9.1. It became the default package tool in FreeBSD 10.0, replacing the pkg_install suite of tools pkg_add(1), pkg_info(1) and pkg_create(1). BSD
December 12, 2013 BSD
All times are GMT -4. The time now is 11:11 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy