Mac OS X 10.4: Optional Installs may install previous versions of certain application


 
Thread Tools Search this Thread
Operating Systems OS X (Apple) OS X Support RSS Mac OS X 10.4: Optional Installs may install previous versions of certain application
# 1  
Old 09-27-2008
Mac OS X 10.4: Optional Installs may install previous versions of certain application

If you want to install items found in the Optional Installs package on the Mac OS X 10.4 Tiger discs, make sure that you only install from a disc with the same version of Mac OS X that's on your computer, such as Mac OS X 10.4 or 10.4.2. Otherwise, you may end up installing previous versions of certain applications, which can cause applications to become unresponsive.

More from Apple OS X Support ...
Login or Register to Ask a Question

Previous Thread | Next Thread

3 More Discussions You Might Find Interesting

1. Linux

Tinycore not saving application installs

So I installed tinycore on a 32 mb flash drive using unetbootin a little while ago. I tried booting into it and the unetbooting screen appeared. I selected tinycore and everything booted fine. I installed a few things like perl and links, and continued on. When I booted into it again, none of these... (1 Reply)
Discussion started by: a sandwhich
1 Replies

2. Shell Programming and Scripting

making code compatible to previous bash versions

First let me explain the scenario I have tywo files as usual file1.txt (it has n rows and 8 columns) $1 $2 $3 $4 $5 $6 $7 $8 Code: 1234567|iufgt|iuoy|iout|white |black |red |90879 1234567|iufgt|iuoy|iout|green |pink |blue |90879... (3 Replies)
Discussion started by: s.deepak
3 Replies

3. Shell Programming and Scripting

Need a script to delete previous versions of files

Hi. I need a script (either bash or perl) that can delete previous versions of files. For instance, from our continuous build process I get directories such as build5_dev_1.21 build5_dev_1.22 build5_dev_1.23 build5_dev_1.24 I need a script that I can run every night (using "at"... (6 Replies)
Discussion started by: jbsimon000
6 Replies
Login or Register to Ask a Question
MAVEN(1)							   User Commands							  MAVEN(1)

NAME
Maven - Installs a POM file into /usr/share/maven-repo. SYNOPSIS
mh_installpom [option]... [pom] DESCRIPTION
Installs the POM file in /usr/share/maven-repo, at the correct location for Maven. Before installing the POM, it prepares it with mh_cleanpom. debian/maven.rules is used to alter the version properties for the library and its dependencies. Prefer to use mh_installpoms as it reuses the information in debian/$package.poms and avoids repetition. Where [pom] is the location of the POM file to install. GroupId, artifactId and version will be extracted from this file. OPTIONS
-h --help: show this text -V --version: show the version -p<package> --package=<package>: name of the Debian package which will contain this POM file -h --has-package-version: flag that indicates that this POM has the same version as the package, this helps packagers of depending packages -o --no-parent: don't inherit from a parent POM -k --keep-pom-version: keep the original version of the POM but convert all other versions in dependencies and plugins. If there is a parent POM, keeps its version except when the parent is already registered in the Maven repository -e<version>, --set-version=<version>: set the version for the POM, do not use the version declared in the POM file. -r<rules> --rules=<rules>: path to the file containing the rules to apply when cleaning the POM. Optional, the default location is debian/maven.rules -u<rules> --published-rules=<rules>: path to the file containing the extra rules to publish in the property debian.mavenRules in the cleaned POM. Optional, the default location is debian/maven.pub- lishedRules -i<rules> --ignore-rules=<rules>: path to the file containing the rules used to remove certain dependencies from the cleaned POM Optional, the default location is debian/maven.ignoreRules -c<rules> --clean-ignore-rules=<rules>: path to the file containing the rules use to remove certain dependencies from the cleaned POM, in addition to the ignore rules specified previously. This is useful in situations such as when the Maven clean target requires more dependencies or plugins to ignore than the build target. All rules defined in clean-ignore-rules will be added to the existing rules in ignore-rules. Optional, the default location is debian/maven.cleanIgnoreRules -s --no-rules: don't apply any rules for converting versions, do not even convert versions to the default 'debian' version --no-publish-used-rule: don't publish the rule used to transform a POM's own attributes in debian.mavenRules --keep-elements=<elem1,elem2>: keep the elements listed here even if they are normally removed by the clean operation. Such elements are build,reports,reporting,prerequisites,profiles. -m<repo root>--maven-repo=<repo root>: location of the Maven repository, used to force the versions of the Maven plugins used in the current POM file with the versions found in the repository -v --verbose: show more information while running -n --no-act: don't actually do anything, just print the results -ignore-pom: read the POM but don't install it See also: mh_installpoms(1), mh_cleanpom(1) Maven Repo Helper version 1.7.1 January 2012 MAVEN(1)