# HG changeset patch # User Padraig O'Briain # Date 1239302006 -3600 # Node ID 37317ca76af31725a14078b65c48abaf0dae3c26 # Parent 4a3a17ce4334dfe4a9252111cc93d81a1aa050b5 7745 PM Help requires changes first revision 7924 Release notes link should be in PM Online Help diff -r 4a3a17ce4334 -r 37317ca76af3 src/gui/Makefile --- a/src/gui/Makefile Thu Apr 09 08:23:57 2009 +0100 +++ b/src/gui/Makefile Thu Apr 09 19:33:26 2009 +0100 @@ -133,8 +133,12 @@ STATICHELPFILES = \ $(HELP_LOCALES:%=help/%/legal.xml) \ + $(HELP_LOCALES:%=help/%/other-trademarks.xml) \ + $(HELP_LOCALES:%=help/%/sun-trademarks.xml) \ $(C_ONLY_HELP_LOCALES:%=help/%/figures/update_all.png) \ - $(C_ONLY_HELP_LOCALES:%=help/%/figures/package_manager.png) + $(C_ONLY_HELP_LOCALES:%=help/%/figures/pm_pkglist.png) \ + $(C_ONLY_HELP_LOCALES:%=help/%/figures/pm_store.png) \ + $(C_ONLY_HELP_LOCALES:%=help/%/figures/wi_start.png) STATICSPFILES = \ $(SP_LOCALES:%=data/startpagebase/%/startpage_star.png) \ diff -r 4a3a17ce4334 -r 37317ca76af3 src/gui/help/C/figures/package_manager.png Binary file src/gui/help/C/figures/package_manager.png has changed diff -r 4a3a17ce4334 -r 37317ca76af3 src/gui/help/C/figures/pm_pkglist.png Binary file src/gui/help/C/figures/pm_pkglist.png has changed diff -r 4a3a17ce4334 -r 37317ca76af3 src/gui/help/C/figures/pm_store.png Binary file src/gui/help/C/figures/pm_store.png has changed diff -r 4a3a17ce4334 -r 37317ca76af3 src/gui/help/C/figures/update_all.png Binary file src/gui/help/C/figures/update_all.png has changed diff -r 4a3a17ce4334 -r 37317ca76af3 src/gui/help/C/figures/wi_start.png Binary file src/gui/help/C/figures/wi_start.png has changed diff -r 4a3a17ce4334 -r 37317ca76af3 src/gui/help/C/legal.xml --- a/src/gui/help/C/legal.xml Thu Apr 09 08:23:57 2009 +0100 +++ b/src/gui/help/C/legal.xml Thu Apr 09 19:33:26 2009 +0100 @@ -1,37 +1,37 @@ - - - -Sun Microsystems, Inc. has intellectual property rights relating to technology embodied in the product that is described in this document. In particular, and without limitation, these intellectual -property rights may include one or more U.S. patents or pending patent applications in the U.S. and in other countries.U.S. Government Rights – Commercial software. Government users are subject to the Sun Microsystems, Inc. standard license agreement and applicable provisions of the FAR and its supplements. -This distribution may include materials developed by third parties. -Parts of the product may be derived from Berkeley BSD systems, licensed from the University of California. UNIX is a registered trademark in the U.S. and other countries, exclusively -licensed through X/Open Company, Ltd. -Sun, Sun Microsystems, the Sun logo, -the Solaris logo, the Java Coffee Cup logo, docs.sun.com, &sun-trademarks;Java, and -Solaris are trademarks or registered trademarks of Sun Microsystems, Inc. or its subsidiaries in the U.S. -and other countries. All SPARC trademarks are used under license and are trademarks -or registered trademarks of SPARC International, Inc. in the U.S. and other countries. -Products bearing SPARC trademarks are based upon an architecture developed by Sun -Microsystems, Inc. &other-trademarks; -The OPEN LOOK and Sun Graphical User Interface was developed by Sun Microsystems, Inc. for -its users and licensees. Sun acknowledges the pioneering efforts of Xerox in researching -and developing the concept of visual or graphical user interfaces for the computer -industry. Sun holds a non-exclusive license from Xerox to the Xerox Graphical User -Interface, which license also covers Sun's licensees who implement OPEN LOOK GUIs -and otherwise comply with Sun's written license agreements. -Products covered by and information contained in this publication are controlled by U.S. Export Control -laws and may be subject to the export or import laws in other countries. Nuclear, -missile, chemical or biological weapons or nuclear maritime end uses or end users, -whether direct or indirect, are strictly prohibited. Export or reexport to countries -subject to U.S. embargo or to entities identified on U.S. export exclusion lists, -including, but not limited to, the denied persons and specially designated nationals -lists is strictly prohibited. -DOCUMENTATION IS PROVIDED “AS IS” AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY -IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, -ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. + + + +Sun Microsystems, Inc. has intellectual property rights relating to technology embodied in the product that is described in this document. In particular, and without limitation, these intellectual +property rights may include one or more U.S. patents or pending patent applications in the U.S. and in other countries.U.S. Government Rights – Commercial software. Government users are subject to the Sun Microsystems, Inc. standard license agreement and applicable provisions of the FAR and its supplements. +This distribution may include materials developed by third parties. +Parts of the product may be derived from Berkeley BSD systems, licensed from the University of California. UNIX is a registered trademark in the U.S. and other countries, exclusively +licensed through X/Open Company, Ltd. +Sun, Sun Microsystems, the Sun logo, +the Solaris logo, the Java Coffee Cup logo, docs.sun.com, &sun-trademarks;Java, and +Solaris are trademarks or registered trademarks of Sun Microsystems, Inc. or its subsidiaries in the U.S. +and other countries. All SPARC trademarks are used under license and are trademarks +or registered trademarks of SPARC International, Inc. in the U.S. and other countries. +Products bearing SPARC trademarks are based upon an architecture developed by Sun +Microsystems, Inc. &other-trademarks; +The OPEN LOOK and Sun Graphical User Interface was developed by Sun Microsystems, Inc. for +its users and licensees. Sun acknowledges the pioneering efforts of Xerox in researching +and developing the concept of visual or graphical user interfaces for the computer +industry. Sun holds a non-exclusive license from Xerox to the Xerox Graphical User +Interface, which license also covers Sun's licensees who implement OPEN LOOK GUIs +and otherwise comply with Sun's written license agreements. +Products covered by and information contained in this publication are controlled by U.S. Export Control +laws and may be subject to the export or import laws in other countries. Nuclear, +missile, chemical or biological weapons or nuclear maritime end uses or end users, +whether direct or indirect, are strictly prohibited. Export or reexport to countries +subject to U.S. embargo or to entities identified on U.S. export exclusion lists, +including, but not limited to, the denied persons and specially designated nationals +lists is strictly prohibited. +DOCUMENTATION IS PROVIDED “AS IS” AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY +IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, +ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. diff -r 4a3a17ce4334 -r 37317ca76af3 src/gui/help/C/other-trademarks.xml --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/src/gui/help/C/other-trademarks.xml Thu Apr 09 19:33:26 2009 +0100 @@ -0,0 +1,12 @@ + + + + diff -r 4a3a17ce4334 -r 37317ca76af3 src/gui/help/C/package-manager.xml.in --- a/src/gui/help/C/package-manager.xml.in Thu Apr 09 08:23:57 2009 +0100 +++ b/src/gui/help/C/package-manager.xml.in Thu Apr 09 19:33:26 2009 +0100 @@ -1,6 +1,6 @@ -OpenSolaris 2009.06 Package Manager Online Help +OpenSolaris 2009.06 Package Manager Online Help OpenSolaris Publications @@ -24,46 +24,66 @@ Sun Microsystems, Inc. détient les droits de propriété intellectuelle relatifs à la technologie incorporée dans le produit qui est décrit dans ce document. En particulier, et ce sans limitation, ces droits de propriété intellectuelle peuvent inclure un ou plusieurs brevets américains ou des applications de brevet en attente aux Etats-Unis et dans d'autres pays. Cette distribution peut comprendre des composants développés par des tierces personnes. Certaines composants de ce produit peuvent être dérivées du logiciel Berkeley BSD, licenciés par l'Université de Californie. UNIX est une marque déposée aux Etats-Unis et dans d'autres pays; elle est licenciée exclusivement par X/Open Company, Ltd. -Sun, Sun Microsystems, le logo Sun, le logo Solaris, le logo Java Coffee Cup, docs.sun.com, Java et Solaris sont des marques de fabrique ou des marques déposées de Sun Microsystems, Inc., ou ses filiales, aux Etats-Unis et dans d'autres pays. Toutes les marques SPARC sont utilisées sous licence et sont des marques de fabrique ou des marques déposées de SPARC International, Inc. aux Etats-Unis et dans d'autres pays. Les produits portant les marques SPARC sont basés sur une architecture développée par Sun Microsystems, Inc. +Sun, Sun Microsystems, le logo Sun, le logo Solaris, le logo Java Coffee Cup, docs.sun.com, Java et Solaris sont des marques de fabrique ou des marques déposées de Sun Microsystems, Inc., ou ses filiales, aux Etats-Unis et dans d'autres pays. Toutes les marques SPARC sont utilisées sous licence et sont des marques de fabrique ou des marques déposées de SPARC International, Inc. aux Etats-Unis et dans d'autres pays. Les produits portant les marques SPARC sont basés sur une architecture développée par Sun Microsystems, Inc. L'interface d'utilisation graphique OPEN LOOK et Sun a été développée par Sun Microsystems, Inc. pour ses utilisateurs et licenciés. Sun reconnaît les efforts de pionniers de Xerox pour la recherche et le développement du concept des interfaces d'utilisation visuelle ou graphique pour l'industrie de l'informatique. Sun détient une licence non exclusive de Xerox sur l'interface d'utilisation graphique Xerox, cette licence couvrant également les licenciés de Sun qui mettent en place l'interface d'utilisation graphique OPEN LOOK et qui, en outre, se conforment aux licences écrites de Sun. Les produits qui font l'objet de cette publication et les informations qu'il contient sont régis par la legislation américaine en matière de contrôle des exportations et peuvent être soumis au droit d'autres pays dans le domaine des exportations et importations. Les utilisations finales, ou utilisateurs finaux, pour des armes nucléaires, des missiles, des armes chimiques ou biologiques ou pour le nucléaire maritime, directement ou indirectement, sont strictement interdites. Les exportations ou réexportations vers des pays sous embargo des Etats-Unis, ou vers des entités figurant sur les listes d'exclusion d'exportation américaines, y compris, mais de manière non exclusive, la liste de personnes qui font objet d'un ordre de ne pas participer, d'une façon directe ou indirecte, aux exportations des produits ou des services qui sont régis par la legislation américaine en matière de contrôle des exportations et la liste de ressortissants spécifiquement designés, sont rigoureusement interdites. LA DOCUMENTATION EST FOURNIE "EN L'ETAT" ET TOUTES AUTRES CONDITIONS, DECLARATIONS ET GARANTIES EXPRESSES OU TACITES SONT FORMELLEMENT EXCLUES, DANS LA MESURE AUTORISEE PAR LA LOI APPLICABLE, Y COMPRIS NOTAMMENT TOUTE GARANTIE IMPLICITE RELATIVE A LA QUALITE MARCHANDE, A L'APTITUDE A UNE UTILISATION PARTICULIERE OU A L'ABSENCE DE CONTREFACON. -OpenSolaris 2009.06 Package Manager -About the Package Manager +About the Package Manager Welcome to the OpenSolaris 2009.06 Package Manager online help! Use this help contents to learn how to use the Package Manager. Navigate through this help by clicking the topics displayed in the sidebar. -The OpenSolaris 2009.06 Package Manager application is a graphical user interface for the Image Packaging System (IPS) software. +The OpenSolaris 2009.06 Package Manager application is a graphical user interface for the Image Packaging System (IPS) software. The Package Manager enables you to perform the following tasks: -Search, install, and remove packages. +Search, install, and remove packages -Add and modify repositories. +Update your system -Create, remove, and manage boot environments. +Add and modify repositories + +Create, remove, and manage boot environments -See the for definitions of the terms used in this document. +See the for a definition of the terms used in this document. - -About Image Packaging System (IPS) -An Introduction to IPS -The Image Packaging System software is a network-centric packaging system written in Python. IPS is an attempt to design and implement a software delivery system that interacts with a network repository. The IPS software is a framework which provides for software lifecycle management including installation, upgrade, and removal. +About Image Packaging System +Image Packaging System (IPS) is a software delivery system that interacts with a network repository. The IPS software is a framework which provides for software lifecycle management including installation, upgrade, and removal. The OpenSolaris 2009.06 release uses IPS as its packaging system. -After an initial installation of OpenSolaris 2009.06 operating system, you will find that many of the software applications that you use on a regular basis are not immediately available to you. These software applications are available as packages in a repository for downloading and installing over the internet. A repository is a source for packages. -Users can use IPS to install packages from a repository, create and publish their own IPS packages, set up an OpenSolaris repository, mirror an existing repository, and publish existing packages to a repository. +After an initial installation of OpenSolaris 2009.06 operating system, you will find that many of the software applications that you use on a regular basis are not immediately available to you. These software applications are available as packages in a repository for downloading and installing over the Internet. A repository is a source for packages. +Users can use IPS to install packages from a repository, create and publish their own IPS packages, mirror an existing repository, and publish existing packages to a repository. Once you have installed packages, IPS enables you to search, update, and manage packages on your system. With IPS , you can upgrade your system to a newer build of OpenSolaris, install and update your software to the latest available versions in a repository, and retrieve packages from mirror repositories. +The Package Manager provides a subset of the tasks that can be performed from the command-line. + If the system on which IPS is installed is on the network, IPS can automatically access the OpenSolaris repository. For the OpenSolaris 2009.06 release, your IPS client can access the packages from . -See the Image Packaging System Guide for more information about IPS. +For more information about IPS, see the Image Packaging System Guide and the IPS man pages. Visit the project page on opensolaris.org and subscribe to pkg-discuss@sun.com to get involved with the IPS project. - The Package Manager Window About the Package Manager Window When you start the Package Manager, the following window is displayed. -
Package Manager Main Window - +
Package Manager Start Up Window + + +
+The Start Page provides links to opensolaris.com page where you can get more information about OpenSolaris, subscribe to newsletters and join the OpenSolaris community. +To close the Start Page and see the list of packages , perform any of the following actions in the main window of the Package Manager: +Select a package category + +Switch the top level category + +Switch the Show filter + +Perform a search + +Change the repository + + +Select ViewStart Page to return to the Start Page at anytime. +See the section to turn off the initial display of the Start Page when the Package Manager starts. + +
List of Packages in the Package Manager Window +
The main window of the Package Manager consists of the following elements : @@ -73,15 +93,15 @@ Toolbar -The toolbar contains the icons for a subset of the commands that can be performed by using the menus on the menubar. Additionally, a Search box and a Repositories drop-down menu are also located on the toolbar. +The toolbar contains the icons for a subset of the commands that can be performed by using the menus on the menubar. ASearch box is also located on the toolbar. List of Packages by Category -You can browse the available packages by category in the left hand side drop-down menu. The drop-down menu shows the list of categories available such as Applications-Desktop, Applications Web based, and Operating System. +You can browse the available packages by category in the left hand side drop-down menu. The drop-down menu shows the list of categories available such as Applications-Desktop, Applications –Web—based, and Operating System. List of Packages by Status -The Show drop-down menu enables you to filter the list of packages by the following options : +The Show drop-down menu enables you to filter the list of packages by the following options : All Packages – Shows the list of all packages available in the current repository. Installed Packages – Shows the list of packages installed on your system. @@ -104,14 +124,12 @@ Repository Drop-down Menu -The list of available repositories is shown in the repository drop-down menu. Click a repository name to select it. -Clicking the Reload button reloads the Package Manager and displays the list of packages in the newly selected repository. - +The list of available repositories is shown in the Repository drop-down menu. Click a repository name to select it. Search Box Search for a package is provided in the following contexts : -Search within the current, default repository +Search within the current repository Search across all configured repositories @@ -120,60 +138,50 @@ -Edit Preferences +Start Page Preferences A Start Page is displayed in the main window of the Package Manager when the application is started. The Start Page provides links to opensolaris.com page where you can get more information about OpenSolaris, subscribe to newsletters and join the OpenSolaris community. You can choose to turn off this setting so this page is not displayed when Package Manager starts. -Select Edit Preferences from the menu and uncheck the Show Start Page on startup box to disable the Start Page. +Select EditPreferences from the menu and uncheck the Show Start Page on startup box to disable the Start Page. +Select ViewStart Page to go to the Start Page at anytime. Working With Packages Install a Package -Perform the following steps to install a package: -In the main window of the Package Manager, click the Reload button to view the latest list of packages available to you. +The list of packages is displayed in the main windows of the Package Manager. Perform the following steps to install a package: +To install a single package, click on a package to select it. To install many packages, check the box next to the packages you want to install. -Select a package. - -Click Install/Update in the toolbar to start the package installation process. +Click the Install/Update icon in the toolbar to start the package installation process. You can also choose PackageInstall/Update to start the package installation process. -View the details or cancel the package installation +View the details or cancel the package installation . Click Show Details to view the details. Click Cancel to cancel the package installation. No changes are made and you are returned to the main window. -Review the package installation information and the package dependencies details in the Install Confirmation dialog. -Click Next to proceed with the package installation. - -Click Cancel to cancel the package installation. No changes are made and you are returned to the main window. - - - -Click Cancel to cancel the package installation in the Downloading Packages dialog box. -No changes are made and you are returned to the main window. - -Check the Accept box and click Accept to accept the terms of the license and complete the package installation successfully. - If you reject the license, the installation process is canceled and the packages will not be installed. - +After the installation has completed, click Close on the Installation Completed dialog box to return to the main window. +Installation Error +If an error occurs during package installation, an error dialog box is displayed. An Installation Failed message and the reason for the failure is displayed. Click Close to close the error dialog box and return to the main window of the Package Manager. + Remove a Package Perform the following steps to remove a package: -Select the package or packages that you want to remove. +To remove a single package, click on a package to select it. To remove many packages, check the box next to the packages you want to remove. -Click the Remove button in the toolbar to start the process. +Click the Remove button in the toolbar to start the package uninstallation process. You can also choose PackageRemove to remove a package. -Review the packages to be removed and the package dependencies details in the Remove Confirmation dialog box. +Review the packages to be removed and the package dependencies details in the Remove Confirmation dialog box. Uninstall the package or cancel the uninstallation process. Click Proceed to start uninstalling the packages. Click Cancel to cancel the process. No changes are made and you are returned to the main window. -After you click the Proceed button, you cannot undo the package removal action. - +After you click the Proceed button, you cannot undo the package removal action. However, you can reinstall the package at any time. + @@ -181,15 +189,8 @@ Search for a Package You can search for a package in the following ways : -Search the default repository – The search will be performed on the default repository, http://pkg.opensolaris.org. - -Search the current repository - -Search all repositories– Search for the package across all configured or registered repositories. - - -Type the name of the package that you want to search for in the Search box. -Enter the complete name, description, or a partial name to search for the package. For example, you might type one of the following search terms to search for SUNWgnome-games : +Search the current repository – Search for a package in the repository currently selected in the Repository drop-down menu. The category selection or the Show filter does not affect the search and the search is performed on all packages in the currently selected repository. +Enter a description, or a partial name in the Search box located on the toolbar. For example, you might type one of the following search terms to search for SUNWgnome-games : SUNWgames games @@ -197,9 +198,29 @@ GNOME-games -Use the submenus under the Edit menu to cut, copy, paste, or clear text in the Search tab. +To search for SunStudio compilers, you might type one of the following terms: +compiler + +tools + + -Use the icon on the right side of the Search tab to clear the search results. +Search all repositories – Select the multi-repository icon in the Search box to search for the package across all configured or registered repositories. +The multi-repository search currently supports search based on the package description only. + +Type a description of the package in the box. For example, the SUNWdiveintopython package is a book on Python programming. The description of the package contains book. To search for this package, you might then type one of the following terms: +python + +book + + +If you searched for the term dive in the multi-repository search, the SUNWdiveintopython package will not be displayed as the term is not present in the package description. + + + +Use the submenus under the Edit menu to cut, copy, paste, or clear text in the Search box. + +Use the icon on the right side of the Search box to clear the search results. @@ -209,21 +230,22 @@ Introduction to Boot Environments -The OpenSolaris 2009.06 release is a boot environment. - A boot environment is an image that is bootable. The boot environment consists of a root file system and, optionally, other file systems, such as /usr, /var, or /export. These other file systems are mounted below the root file system. The root file system and all other file systems of the boot environment that contain system software are required to be ZFS datasets. - You can maintain multiple boot environments on your system. Use the command—line interface (CLI) to create, rename, mount or unmount, or destroy these boot environments. The primary reason to have more than one boot environment on your system is to create backups of your existing boot environments before you modify them. Then you have the option of booting a backup boot environment when needed. - See the Upgrading and Managing Boot Environments document to learn more. -The Package Manager creates a clone of the active boot environment when an image is updated. +A boot environment is an image that is bootable. Upon an initial OpenSolaris installation, a boot environment is created. + You can maintain multiple boot environments on your OpenSolaris 2009.06 system. Use the beadm(1) command from the command—line interface (CLI) to create, rename, mount or unmount, or destroy these boot environments. +The Package Manager enables you to manage the boot environments created during the process of updating your image. For more information, see section. +System administrators can maintain multiple boot environments on their systems, and each boot environment can have different software versions installed. +When you use either the Package Manager or the pkg image-update command to update all the packages in your active OpenSolaris boot environment, a clone of that boot environment is automatically created. The packages are updated in the clone rather than in the original boot environment. After successfully completing the updates, the new clone is activated. Then, the clone will become the new default boot environment on system reboot. The original boot environment is also available as an alternate selection. + See the beadm(1) man pages and the Upgrading and Managing Boot Environments document to learn more about boot environments and the beadm(1) command. Update All Packages (Update Your Image) Perform the following steps to update all the packages in your image. -Click the Update All button to start the process of updating all the packages in your image. -You can also choose FileUpdate All to start the process. -The Update All button is enabled when updates are available to the installed packages. +Click the Update All icon located on the toolbar to start the process of updating all the packages installed in your image. +You can also choose PackageUpdate All to start the process. +The Update All icon is enabled when updates are available to the installed packages. -A Create New Boot Environment window is displayed. A name for the new boot environment is automatically generated. +A Create New Boot Environment window is displayed. A name for the new boot environment is automatically generated. -(optional) You can change the name of the new boot environment if you want. +(optional) You can change the name of the new boot environment if you want. Confirm or Cancel the new boot environment. Click Proceed to create a new boot environment and proceed with the Update All process. @@ -234,11 +256,9 @@ During the Update All process, a clone of the active boot environment is created. This clone enables the user to boot into the boot environment state that existed before the Update All process was started. If the Package Manager is unable to create a new boot environment, an error message will be displayed. See the section on how to rectify the error and continue with updating your image. If you chose to proceed with the Update All process, the packages are downloaded and installed. -After a successful completion, the Update All Complete dialog box is shown. +After a successful completion, the Update All Complete dialog box is shown. A link to the Release Notes is provided in the dialog box. Read the before rebooting your system. Click Close. - -Read the Release Notes before rebooting your system. You must reboot your system for the changes to take effect. @@ -246,10 +266,10 @@ Update All Errors A new boot environment clone must be created by the Package Manager for the Update All process to be completed. An error message is displayed if a boot environment clone cannot be created. You might see an error message such as the following : -Not enough disk space: the Update All action cannot be performed. You may choose to return to BE Management to manage your boot environments and free up disk space. +Not enough disk space, the selected action cannot be performed. Click OK to manage your existing BEs and free up disk space or Cancel to cancel the action. Click Cancel to cancel the Update All process and return to the main window. Perform the following steps if you want to rectify the error and continue with the Update All process: -Click OK to display the Boot Environment Management dialog box. +Click OK to display the Boot Environment Management dialog box. Select the boot environments that you want to delete. You cannot delete the currently active boot environment. @@ -259,9 +279,9 @@ -Click OK. The Manage BEs Changes Confirmation dialog is shown. +Click OK. - Review your changes and click OK to delete your boot environments. +The Boot Environment Confirmation dialog is shown. Review your changes and click OK to proceed. Click the Update All icon to restart the process of updating all packages. @@ -269,7 +289,7 @@ Manage Boot Environments Perform the following steps to manage your boot environments: -Click FileManage Boot Environments to open the Manage Boot Environments dialog. +Click FileManage Boot Environments to open the Manage Boot Environments dialog. In this dialog box , you can perform the following actions: Activate a boot environment – Select the boot environment that you want to be active on system reboot. This will be the default boot environment after you have rebooted your system. @@ -277,12 +297,18 @@ Remove old or unused boot environments to free up disk space – Select the boot environments that you want to delete. You cannot the delete the currently active boot environment. -You do not need to reboot your system if you are only deleting some of your boot environments. +If you have selected a boot environment to be renamed, it cannot be deleted. -Rename a boot environment – Double-click the BE name that you want to change. Enter the new name of the BE and click OK. +Rename a boot environment – Double-click the boot environment name that you want to change. Enter the new name of the boot environment and click OK. +If you have selected a boot environment to be deleted, it cannot be renamed. + +The currently active boot environment cannot be renamed. + + + @@ -293,16 +319,15 @@ -The Manage BEs Confirmation dialog box is displayed. -Review the boot environment changes and click OK to proceed. +The Boot Environment Confirmation dialog is displayed. Review your changes and click OK to proceed. After you click OK, you cannot undo any changes that you made to the boot environments. The changes that you made to the default boot environment setting are effective only after system reboot. Click Cancel to cancel the changes and return to the BE Management dialog box. -Reboot your system to see the latest changes. -You do not need to reboot your system if you only renamed a BE and did not make any other changes. +Reboot your system to boot into the newly activated boot environment. +Reboot your system only if you changed the active boot environment. @@ -311,15 +336,25 @@ Managing Repositories Add a Repository Perform the following steps to add a repository: -Choose FileManage Repositories to open the Manage Repositories dialog. +Choose FileManage Repositories. +You can also choose Add... from the Repository drop-down menu in the main window of the Package Manager. + + The Manage Repositories dialog box is displayed. Type the name and the address (URL) of the repository you want to add. Click Add. -Type the name and the address (URL) of the repository you want to add. Click Add + + +Add a Secure Repository +A secure repository requires a SSL key and certificate for access. Perform the following steps to add a secure repository: +Follow the steps in section to add a repository. + +Follow the steps in the section to add a SSL key and certificate. +. Remove a Repository Perform the following steps to remove a repository: -Choose FileManage Repositories to open the Manage Repositories dialog. +Choose FileManage Repositories to open the Manage Repositories dialog. Select a repository from the list. Click Remove. A repository that has been set as preferred repository cannot be removed. To remove a preferred repository, set a nonpreferred repository as preferred, and then remove the repository. @@ -329,7 +364,7 @@ Set a Preferred Repository Perform the following steps to set a preferred repository: -Choose FileManage Repositories to open the Manage Repositories dialog. +Choose FileManage Repositories to open the Manage Repositories dialog. Click the radio button next to the repository that you would like to set as the preferred repository. @@ -339,23 +374,31 @@ Modify a Repository Perform the following steps to modify a repository: -Choose FileManage Repositories to open the Manage Repositories dialog. +Choose FileManage Repositories to open the Manage Repositories dialog. Select the repository that you want to modify. Click the Modify button. - The Modify Repository dialog box is displayed. You can perform the following actions in the Modify Repository dialog box: -Change the name and URL of the repository – Type a valid name for the repository and the URL of the repository. -A repository name is considered valid if it does not exist in the current list of repositories. + The Modify Repository dialog box is displayed. You can perform the following actions in the Modify Repository dialog box: +Change the URL of the repository – Type a valid URL for the repository. +You cannot change a repository name after you have added a repository. To change the repository name, delete the existing repository with the old name and add a repository with the new name. See the section for steps on how to remove a repository. -Add a SSL Key and Certificate – If a repository requires a key or certificate, add the repository name and URL, and then click the Modify button to add additional information such as a key or certificate. +Add a SSL Key and Certificate – A secure repository requires a SSL key and certificate for access. +The Instructions link in the Modify Repository dialog box links to a registration site which provides instructions for downloading the SSL key and certificate +In the Modify Repository dialog box, click the Instructions link to download the key and certificate. Save them on your system. + +Click the Browse button to locate the SSL key on your system. + +Click the Browse button to locate the SSL certificate on your system. + + Add a Mirror – If a repository has a mirror, add the repository name and URL, and then click the Modify button to add the mirror information. Confirm or decline the changes. -Click OK to save the changes and return to the Manage Repositories dialog box. +Click OK to save the changes and return to the Manage Repositories dialog box. Click Cancel to cancel your changes. @@ -364,6 +407,49 @@ +Working With WebInstall +The OpenSolaris 2009.06 Package Manager provides support for users to add new repositories and optionally, install packages from these repositories using a simple one-click WebInstall process. A .p5i file which contains the repositories to be added and optionally, the package or packages that can be installed from these repositories, is required for the WebInstall process. The information contained in the .p5i file is read and used by the WebInstall process. +How to Use WebInstall to Add Repositories and Install Packages +Before You BeginLocate the .p5i file which may be present on your desktop, the Start page in the Package Manager, or on a website. +Start the Package manager in WebInstall mode in one of the following ways: +Click on a .p5i file on your desktop, and the associated application, Package Manager in WebInstall mode, will be launched. + +Start the Package Manager from the command-line along with a path to the .p5i file. For example, type the following command at the command-line: +$ pfexec packagemanager/path_to_pi5_file/file.p5i + +Click on a URL location that contains a link to .p5i file. If you are using this method to start the WebInstall, the .p5i file must be located on a web server that has registered the new mime type. Only then, the web server can manage the .p5i automatically and start Package Manager in WebInstall mode. +If the .p5i is located on a web server that does not have the new mime type registered, save the .p5i file to your desktop and then click on it to launch Web Install. + + + +The following example window that shows a list of repositories that will be added and the packages that will be installed. Review the information. +
Package Manager WebInstaller + + +
+
+Confirm or cancel the WebInstall process. +Click Proceed to add the new repositories and install the packages. +Click Cancel to cancel the process. The Package Manager application exits. + +(Optional) If the repositories that are to be added are secure repositories, an SSL key and certificate is required. An Add New Repositories dialog box is displayed. +Click the Instructions link in the Add New Repositories dialog box to download the SSL key and certificate. + +Click the Browse button to locate the SSL key on your system. + +Click the Browse button to locate the SSL certificate on your system. + +Click OK to proceed. + + +The Adding New Repositories status bar is displayed. + +(Optional) If packages are being installed, the Install/Update dialog box is displayed. Click Cancel to cancel the package installation. +The application will close when all packages are installed. + +
+
+
Working With the Update Manager About The Update Manager The Update Manager is a separate application that starts from the desktop when updates to the installed packages are available in the repository. @@ -372,47 +458,45 @@
You can use the Update Manager application to update the installed packages in your image. -For the OpenSolaris 2009.06 release, the Update Manager updates all installed packages in the image. This action is equivalent to updating the image. +For the OpenSolaris 2009.06 release, the Update Manager updates all installed packages in the image. This action is equivalent to running the pkg image-update command from the command-line.
Using the Update Manager When updates are available to the installed packages, a notification icon is displayed in the notification panel on the OpenSolaris desktop. You can also click SystemAdministrationUpdate Manager to manually launch the Update Manager. -When you are notified of a software update, perform the following steps to begin the process of updating your system : -Click the notification icon on the desktop to display the Update Manager window. +When you are notified of a software update, perform the following steps to begin the process of updating your system: +Click the notification icon on the desktop to display the Update Manager window. -Click the Update All button in the Update Manager window. +Click the Update All button in the Update Manager window. Select a package and click the Details panel if you want to view more information about the package. -The Update All dialog box is displayed. Proceed with the Update All process or cancel the action. +The Update All dialog box is displayed. Proceed with the Update All process or cancel the action. Click Proceed to create a new boot environment and update all packages in the current image. During the Update All process, a clone of the active boot environment is created. This clone enables the user to boot into the boot environment state that existed before the Update All process was started. If the Package Manager is unable to create a new boot environment, an error message will be displayed. See the section on how to rectify the error and continue with updating your image. -A name for the new boot environment is automatically generated. +A name for the new boot environment is automatically generated. You can accept the name generated by the system, or provide your own name for the boot environment. Click Cancel to cancel the process. -If you chose to proceed, the Installing Updates windows are displayed. The package installation process consists of four stages: -Evaluate. +If you chose to proceed, the Installing Updates windows are displayed. The package installation process consists of four stages: +Prepare Download. Install. -Index. - -You can choose to cancel the process only during the Evaluate and Download stages. Click the Cancel button to cancel the installation process. No changes are made and you are returned to the main window of the Update Manager. +You can choose to cancel the process only during the Prepare and Download stages. Click the Cancel button to cancel the installation process. No changes are made and you are returned to the main window of the Update Manager. If an error occurs during any of the stages, the Details panel is expanded and the details of the error are displayed. An error status indicator is shown next to the failed stage. Click the Details panel to view more information about each of the installation processes. -Read the Release Notes before rebooting your system. +Read the before rebooting your system. You must reboot your system for the changes to take effect. @@ -420,7 +504,7 @@ Update All Errors A new boot environment clone must be created for the Update All process to be completed. The following error message is displayed if a boot environment clone cannot be created due to space restrictions : -Not enough disk space: the Update All action cannot be performed. Do you want to launch BE Management to manage your existing BEs and free up disk space? +Not enough disk space, the selected action cannot be performed. Click OK to manage your existing BEs and free up disk space or Cancel to cancel the action. Click No to cancel the Update All process and return to the Update Manager main window. Perform the following steps if you want to rectify the error and continue with the Update All process: Click Yes in the error dialog box to go to the Boot Environment Management dialog. @@ -432,26 +516,33 @@
+Release Notes +The OpenSolaris 2009.06 Release Notes are available at the following locations: +x86 Release Notes + +SPARC Release Notes + + + +Package Manager Screencast +A screencast that shows Package Manager usage for beginners is available. Click the link below to go to the screencast. +OpenSolaris 2009.06 Package Manager Screencast +
Image Packaging System Glossary publisher -A person, group, or corporation that designs, creates, and publishes a package to a repository. - -A location that is configured to point to a repository and might contain additional information about the package, such as the publisher of the package. The repository in turn serves the packages from the (default) authority, for downloading purposes. The developer-quality packages managed by Sun and made available through http://pkg.opensolaris.com is an example of an authority. -Before the 2009.06 release, the term authority was used instead of publisher. - - - +A person, group, or corporation that designs, creates, and publishes a package to a repository. The repository in turn serves the packages from the (default) publisher, for downloading purposes. The developer-quality packages managed by Sun and made available through http://pkg.opensolaris.com/dev is an example of a publisher. +The term authority has been replaced with the term publisher from the OpenSolaris 2009.06 release onwards. boot environment -For an OpenSolaris release, a boot environment is an instance of a bootable OpenSolaris environment. The boot environment consists of a root file system and, optionally, other file systems, such as /usr, /var, or /export. These other file systems are mounted below the root file system. The root file system and all other file systems of the boot environment that contain system software are required to be ZFS datasets. -The active boot environment is the one that is currently booted. Exactly one active boot environment can be booted. An inactive boot environment is not currently booted, but can be in a state of waiting for activation on the next reboot. +For an OpenSolaris release, a boot environment is an instance of a bootable OpenSolaris environment. The root file system and all other file systems of the boot environment that contain system software are required to be ZFS datasets. +The active boot environment is the one that is currently booted. Many boot environments can present on an OpenSolaris system and an inactive boot environment can be in a state of waiting for activation upon system reboot. clone An exact copy. -For installation, a clone could be an exact copy of an operating system, a file system, or a volume. This copy has 100% compatibility with the original. +A clone could be an exact copy of an operating system, a file system, or a volume. This copy has 100% compatibility with the original. dataset @@ -459,7 +550,8 @@ image -A collection of software in a package that comprises an entire operating system. The package is suitable for installation. +A collection of software in a package that comprises an entire or partial operating system. The package is suitable for installation. +An image is a location on your system where packages and their associated files, directories, links, and dependencies can be installed. package @@ -467,13 +559,12 @@ preferred repository -A default repository that is the source for packages. If a user does not explicitly specify a repository when installing and updating packages, the preferred publisher is chosen as the source for packages. -During the creation of an image, the initially specified publisher is marked as the preferred publisher. Any one of the publishers associated with an image can be set as the preferred publisher. +A default repository that is the source for packages. If a user does not explicitly specify a repository when installing and updating packages, the preferred repository is chosen as the source for packages. repository -A location where packages are available for downloading. A repository can contain packages from many authorities. Conversely, many repositories can contain packages from a single authority. Also called the depot server. +A location where packages are available for downloading. A publisher can publish packages to many repositories. -
\ No newline at end of file +
diff -r 4a3a17ce4334 -r 37317ca76af3 src/gui/help/C/sun-trademarks.xml --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/src/gui/help/C/sun-trademarks.xml Thu Apr 09 19:33:26 2009 +0100 @@ -0,0 +1,10 @@ + + + + diff -r 4a3a17ce4334 -r 37317ca76af3 src/gui/help/de/other-trademarks.xml --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/src/gui/help/de/other-trademarks.xml Thu Apr 09 19:33:26 2009 +0100 @@ -0,0 +1,12 @@ + + + + diff -r 4a3a17ce4334 -r 37317ca76af3 src/gui/help/de/sun-trademarks.xml --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/src/gui/help/de/sun-trademarks.xml Thu Apr 09 19:33:26 2009 +0100 @@ -0,0 +1,10 @@ + + + + diff -r 4a3a17ce4334 -r 37317ca76af3 src/gui/help/es/other-trademarks.xml --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/src/gui/help/es/other-trademarks.xml Thu Apr 09 19:33:26 2009 +0100 @@ -0,0 +1,12 @@ + + + + diff -r 4a3a17ce4334 -r 37317ca76af3 src/gui/help/es/sun-trademarks.xml --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/src/gui/help/es/sun-trademarks.xml Thu Apr 09 19:33:26 2009 +0100 @@ -0,0 +1,10 @@ + + + + diff -r 4a3a17ce4334 -r 37317ca76af3 src/gui/help/fr/legal.xml --- a/src/gui/help/fr/legal.xml Thu Apr 09 08:23:57 2009 +0100 +++ b/src/gui/help/fr/legal.xml Thu Apr 09 19:33:26 2009 +0100 @@ -1,37 +1,58 @@ - - - -Sun Microsystems, Inc. has intellectual property rights relating to technology embodied in the product that is described in this document. In particular, and without limitation, these intellectual -property rights may include one or more U.S. patents or pending patent applications in the U.S. and in other countries.U.S. Government Rights – Commercial software. Government users are subject to the Sun Microsystems, Inc. standard license agreement and applicable provisions of the FAR and its supplements. -This distribution may include materials developed by third parties. -Parts of the product may be derived from Berkeley BSD systems, licensed from the University of California. UNIX is a registered trademark in the U.S. and other countries, exclusively -licensed through X/Open Company, Ltd. -Sun, Sun Microsystems, the Sun logo, -the Solaris logo, the Java Coffee Cup logo, docs.sun.com, &sun-trademarks;Java, and -Solaris are trademarks or registered trademarks of Sun Microsystems, Inc. or its subsidiaries in the U.S. -and other countries. All SPARC trademarks are used under license and are trademarks -or registered trademarks of SPARC International, Inc. in the U.S. and other countries. -Products bearing SPARC trademarks are based upon an architecture developed by Sun -Microsystems, Inc. &other-trademarks; -The OPEN LOOK and Sun Graphical User Interface was developed by Sun Microsystems, Inc. for -its users and licensees. Sun acknowledges the pioneering efforts of Xerox in researching -and developing the concept of visual or graphical user interfaces for the computer -industry. Sun holds a non-exclusive license from Xerox to the Xerox Graphical User -Interface, which license also covers Sun's licensees who implement OPEN LOOK GUIs -and otherwise comply with Sun's written license agreements. -Products covered by and information contained in this publication are controlled by U.S. Export Control -laws and may be subject to the export or import laws in other countries. Nuclear, -missile, chemical or biological weapons or nuclear maritime end uses or end users, -whether direct or indirect, are strictly prohibited. Export or reexport to countries -subject to U.S. embargo or to entities identified on U.S. export exclusion lists, -including, but not limited to, the denied persons and specially designated nationals -lists is strictly prohibited. -DOCUMENTATION IS PROVIDED “AS IS” AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY -IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, -ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. + + + +Sun Microsystems, +Inc. détient les droits de propriété intellectuelle relatifs à +la technologie incorporée dans le produit qui est décrit dans +ce document. En particulier, et ce sans limitation, ces droits de propriété +intellectuelle peuvent inclure un ou plusieurs brevets américains ou +des applications de brevet en attente aux Etats-Unis et dans d'autres pays. +Cette distribution peut comprendre des composants développés +par des tierces personnes.Certaines composants de ce produit +peuvent être dérivées du logiciel Berkeley BSD, licenciés +par l'Université de Californie. UNIX est une marque déposée +aux Etats-Unis et dans d'autres pays; elle est licenciée exclusivement +par X/Open Company, Ltd. Sun, Sun Microsystems, le logo Sun, +le logo Solaris, le logo Java Coffee Cup, docs.sun.com, &sun-trademarks; Java +et Solaris sont des marques de fabrique ou des marques déposées +de Sun Microsystems, Inc., ou ses filiales, aux Etats-Unis et dans d'autres +pays. Toutes les marques SPARC sont utilisées sous licence et sont +des marques de fabrique ou des marques déposées de SPARC International, +Inc. aux Etats-Unis et dans d'autres pays. Les produits portant les marques +SPARC sont basés sur une architecture développée par +Sun Microsystems, Inc. &fr-other-trademarks;L'interface d'utilisation +graphique OPEN LOOK et Sun a été développée +par Sun Microsystems, Inc. pour ses utilisateurs et licenciés. Sun +reconnaît les efforts de pionniers de Xerox pour la recherche et le +développement du concept des interfaces d'utilisation visuelle ou graphique +pour l'industrie de l'informatique. Sun détient une licence non exclusive +de Xerox sur l'interface d'utilisation graphique Xerox, cette licence couvrant également +les licenciés de Sun qui mettent en place l'interface d'utilisation +graphique OPEN LOOK et qui, en outre, se conforment aux licences écrites +de Sun.Les produits qui font l'objet de cette publication et +les informations qu'il contient sont régis par la legislation américaine +en matière de contrôle des exportations et peuvent être +soumis au droit d'autres pays dans le domaine des exportations et importations. +Les utilisations finales, ou utilisateurs finaux, pour des armes nucléaires, +des missiles, des armes chimiques ou biologiques ou pour le nucléaire +maritime, directement ou indirectement, sont strictement interdites. Les exportations +ou réexportations vers des pays sous embargo des Etats-Unis, ou vers +des entités figurant sur les listes d'exclusion d'exportation américaines, +y compris, mais de manière non exclusive, la liste de personnes qui +font objet d'un ordre de ne pas participer, d'une façon directe ou +indirecte, aux exportations des produits ou des services qui sont régis +par la legislation américaine en matière de contrôle des +exportations et la liste de ressortissants spécifiquement designés, +sont rigoureusement interdites.LA DOCUMENTATION EST FOURNIE "EN +L'ETAT" ET TOUTES AUTRES CONDITIONS, DECLARATIONS ET GARANTIES EXPRESSES OU +TACITES SONT FORMELLEMENT EXCLUES, DANS LA MESURE AUTORISEE PAR LA LOI APPLICABLE, +Y COMPRIS NOTAMMENT TOUTE GARANTIE IMPLICITE RELATIVE A LA QUALITE MARCHANDE, +A L'APTITUDE A UNE UTILISATION PARTICULIERE OU A L'ABSENCE DE CONTREFACON. + diff -r 4a3a17ce4334 -r 37317ca76af3 src/gui/help/fr/other-trademarks.xml --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/src/gui/help/fr/other-trademarks.xml Thu Apr 09 19:33:26 2009 +0100 @@ -0,0 +1,12 @@ + + + + diff -r 4a3a17ce4334 -r 37317ca76af3 src/gui/help/fr/sun-trademarks.xml --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/src/gui/help/fr/sun-trademarks.xml Thu Apr 09 19:33:26 2009 +0100 @@ -0,0 +1,10 @@ + + + + diff -r 4a3a17ce4334 -r 37317ca76af3 src/gui/help/it/other-trademarks.xml --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/src/gui/help/it/other-trademarks.xml Thu Apr 09 19:33:26 2009 +0100 @@ -0,0 +1,12 @@ + + + + diff -r 4a3a17ce4334 -r 37317ca76af3 src/gui/help/it/sun-trademarks.xml --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/src/gui/help/it/sun-trademarks.xml Thu Apr 09 19:33:26 2009 +0100 @@ -0,0 +1,10 @@ + + + + diff -r 4a3a17ce4334 -r 37317ca76af3 src/gui/help/ja/other-trademarks.xml --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/src/gui/help/ja/other-trademarks.xml Thu Apr 09 19:33:26 2009 +0100 @@ -0,0 +1,12 @@ + + + + diff -r 4a3a17ce4334 -r 37317ca76af3 src/gui/help/ja/sun-trademarks.xml --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/src/gui/help/ja/sun-trademarks.xml Thu Apr 09 19:33:26 2009 +0100 @@ -0,0 +1,10 @@ + + + + diff -r 4a3a17ce4334 -r 37317ca76af3 src/gui/help/ko/other-trademarks.xml --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/src/gui/help/ko/other-trademarks.xml Thu Apr 09 19:33:26 2009 +0100 @@ -0,0 +1,12 @@ + + + + diff -r 4a3a17ce4334 -r 37317ca76af3 src/gui/help/ko/sun-trademarks.xml --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/src/gui/help/ko/sun-trademarks.xml Thu Apr 09 19:33:26 2009 +0100 @@ -0,0 +1,10 @@ + + + + diff -r 4a3a17ce4334 -r 37317ca76af3 src/gui/help/pt_BR/other-trademarks.xml --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/src/gui/help/pt_BR/other-trademarks.xml Thu Apr 09 19:33:26 2009 +0100 @@ -0,0 +1,12 @@ + + + + diff -r 4a3a17ce4334 -r 37317ca76af3 src/gui/help/pt_BR/sun-trademarks.xml --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/src/gui/help/pt_BR/sun-trademarks.xml Thu Apr 09 19:33:26 2009 +0100 @@ -0,0 +1,10 @@ + + + + diff -r 4a3a17ce4334 -r 37317ca76af3 src/gui/help/ru/other-trademarks.xml --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/src/gui/help/ru/other-trademarks.xml Thu Apr 09 19:33:26 2009 +0100 @@ -0,0 +1,12 @@ + + + + diff -r 4a3a17ce4334 -r 37317ca76af3 src/gui/help/ru/sun-trademarks.xml --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/src/gui/help/ru/sun-trademarks.xml Thu Apr 09 19:33:26 2009 +0100 @@ -0,0 +1,10 @@ + + + + diff -r 4a3a17ce4334 -r 37317ca76af3 src/gui/help/sv/other-trademarks.xml --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/src/gui/help/sv/other-trademarks.xml Thu Apr 09 19:33:26 2009 +0100 @@ -0,0 +1,12 @@ + + + + diff -r 4a3a17ce4334 -r 37317ca76af3 src/gui/help/sv/sun-trademarks.xml --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/src/gui/help/sv/sun-trademarks.xml Thu Apr 09 19:33:26 2009 +0100 @@ -0,0 +1,10 @@ + + + + diff -r 4a3a17ce4334 -r 37317ca76af3 src/gui/help/zh_CN/other-trademarks.xml --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/src/gui/help/zh_CN/other-trademarks.xml Thu Apr 09 19:33:26 2009 +0100 @@ -0,0 +1,12 @@ + + + + diff -r 4a3a17ce4334 -r 37317ca76af3 src/gui/help/zh_CN/sun-trademarks.xml --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/src/gui/help/zh_CN/sun-trademarks.xml Thu Apr 09 19:33:26 2009 +0100 @@ -0,0 +1,10 @@ + + + + diff -r 4a3a17ce4334 -r 37317ca76af3 src/gui/help/zh_HK/other-trademarks.xml --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/src/gui/help/zh_HK/other-trademarks.xml Thu Apr 09 19:33:26 2009 +0100 @@ -0,0 +1,12 @@ + + + + diff -r 4a3a17ce4334 -r 37317ca76af3 src/gui/help/zh_HK/sun-trademarks.xml --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/src/gui/help/zh_HK/sun-trademarks.xml Thu Apr 09 19:33:26 2009 +0100 @@ -0,0 +1,10 @@ + + + + diff -r 4a3a17ce4334 -r 37317ca76af3 src/gui/help/zh_TW/other-trademarks.xml --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/src/gui/help/zh_TW/other-trademarks.xml Thu Apr 09 19:33:26 2009 +0100 @@ -0,0 +1,12 @@ + + + + diff -r 4a3a17ce4334 -r 37317ca76af3 src/gui/help/zh_TW/sun-trademarks.xml --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/src/gui/help/zh_TW/sun-trademarks.xml Thu Apr 09 19:33:26 2009 +0100 @@ -0,0 +1,10 @@ + + + + diff -r 4a3a17ce4334 -r 37317ca76af3 src/pkgdefs/SUNWipkg-gui-l10n/prototype --- a/src/pkgdefs/SUNWipkg-gui-l10n/prototype Thu Apr 09 08:23:57 2009 +0100 +++ b/src/pkgdefs/SUNWipkg-gui-l10n/prototype Thu Apr 09 19:33:26 2009 +0100 @@ -6,40 +6,64 @@ d none usr/share/gnome/help/package-manager 755 root bin d none usr/share/gnome/help/package-manager/de 755 root bin f none usr/share/gnome/help/package-manager/de/legal.xml 444 root bin +f none usr/share/gnome/help/package-manager/de/other-trademarks.xml 444 root bin f none usr/share/gnome/help/package-manager/de/package-manager.xml 444 root bin +f none usr/share/gnome/help/package-manager/de/sun-trademarks.xml 444 root bin d none usr/share/gnome/help/package-manager/es 755 root bin f none usr/share/gnome/help/package-manager/es/legal.xml 444 root bin +f none usr/share/gnome/help/package-manager/es/other-trademarks.xml 444 root bin f none usr/share/gnome/help/package-manager/es/package-manager.xml 444 root bin +f none usr/share/gnome/help/package-manager/es/sun-trademarks.xml 444 root bin d none usr/share/gnome/help/package-manager/fr 755 root bin +f none usr/share/gnome/help/package-manager/fr/legal.xml 444 root bin +f none usr/share/gnome/help/package-manager/fr/other-trademarks.xml 444 root bin f none usr/share/gnome/help/package-manager/fr/package-manager.xml 444 root bin -f none usr/share/gnome/help/package-manager/fr/legal.xml 444 root bin +f none usr/share/gnome/help/package-manager/fr/sun-trademarks.xml 444 root bin d none usr/share/gnome/help/package-manager/it 755 root bin f none usr/share/gnome/help/package-manager/it/legal.xml 444 root bin +f none usr/share/gnome/help/package-manager/it/other-trademarks.xml 444 root bin f none usr/share/gnome/help/package-manager/it/package-manager.xml 444 root bin +f none usr/share/gnome/help/package-manager/it/sun-trademarks.xml 444 root bin d none usr/share/gnome/help/package-manager/ja 755 root bin f none usr/share/gnome/help/package-manager/ja/legal.xml 444 root bin +f none usr/share/gnome/help/package-manager/ja/other-trademarks.xml 444 root bin f none usr/share/gnome/help/package-manager/ja/package-manager.xml 444 root bin +f none usr/share/gnome/help/package-manager/ja/sun-trademarks.xml 444 root bin d none usr/share/gnome/help/package-manager/ko 755 root bin f none usr/share/gnome/help/package-manager/ko/legal.xml 444 root bin +f none usr/share/gnome/help/package-manager/ko/other-trademarks.xml 444 root bin f none usr/share/gnome/help/package-manager/ko/package-manager.xml 444 root bin +f none usr/share/gnome/help/package-manager/ko/sun-trademarks.xml 444 root bin d none usr/share/gnome/help/package-manager/pt_BR 755 root bin -f none usr/share/gnome/help/package-manager/pt_BR/package-manager.xml 444 root bin f none usr/share/gnome/help/package-manager/pt_BR/legal.xml 444 root bin +f none usr/share/gnome/help/package-manager/pt_BR/other-trademarks.xml 444 root bin +f none usr/share/gnome/help/package-manager/pt_BR/package-manager.xml 444 root bin +f none usr/share/gnome/help/package-manager/pt_BR/sun-trademarks.xml 444 root bin d none usr/share/gnome/help/package-manager/sv 755 root bin +f none usr/share/gnome/help/package-manager/sv/legal.xml 444 root bin +f none usr/share/gnome/help/package-manager/sv/other-trademarks.xml 444 root bin f none usr/share/gnome/help/package-manager/sv/package-manager.xml 444 root bin -f none usr/share/gnome/help/package-manager/sv/legal.xml 444 root bin +f none usr/share/gnome/help/package-manager/sv/sun-trademarks.xml 444 root bin d none usr/share/gnome/help/package-manager/ru 755 root bin +f none usr/share/gnome/help/package-manager/ru/legal.xml 444 root bin +f none usr/share/gnome/help/package-manager/ru/other-trademarks.xml 444 root bin f none usr/share/gnome/help/package-manager/ru/package-manager.xml 444 root bin -f none usr/share/gnome/help/package-manager/ru/legal.xml 444 root bin +f none usr/share/gnome/help/package-manager/ru/sun-trademarks.xml 444 root bin d none usr/share/gnome/help/package-manager/zh_CN 755 root bin +f none usr/share/gnome/help/package-manager/zh_CN/legal.xml 444 root bin +f none usr/share/gnome/help/package-manager/zh_CN/other-trademarks.xml 444 root bin f none usr/share/gnome/help/package-manager/zh_CN/package-manager.xml 444 root bin -f none usr/share/gnome/help/package-manager/zh_CN/legal.xml 444 root bin +f none usr/share/gnome/help/package-manager/zh_CN/sun-trademarks.xml 444 root bin d none usr/share/gnome/help/package-manager/zh_HK 755 root bin +f none usr/share/gnome/help/package-manager/zh_HK/legal.xml 444 root bin +f none usr/share/gnome/help/package-manager/zh_HK/other-trademarks.xml 444 root bin f none usr/share/gnome/help/package-manager/zh_HK/package-manager.xml 444 root bin -f none usr/share/gnome/help/package-manager/zh_HK/legal.xml 444 root bin +f none usr/share/gnome/help/package-manager/zh_HK/sun-trademarks.xml 444 root bin d none usr/share/gnome/help/package-manager/zh_TW 755 root bin f none usr/share/gnome/help/package-manager/zh_TW/legal.xml 444 root bin +f none usr/share/gnome/help/package-manager/zh_TW/other-trademarks.xml 444 root bin f none usr/share/gnome/help/package-manager/zh_TW/package-manager.xml 444 root bin +f none usr/share/gnome/help/package-manager/zh_TW/sun-trademarks.xml 444 root bin d none usr/share/locale 755 root other d none usr/share/locale/ar 755 root other d none usr/share/locale/ar/LC_MESSAGES 755 root other diff -r 4a3a17ce4334 -r 37317ca76af3 src/pkgdefs/SUNWipkg-gui/prototype --- a/src/pkgdefs/SUNWipkg-gui/prototype Thu Apr 09 08:23:57 2009 +0100 +++ b/src/pkgdefs/SUNWipkg-gui/prototype Thu Apr 09 19:33:26 2009 +0100 @@ -42,9 +42,13 @@ d none usr/share/gnome/help/package-manager/C 755 root bin f none usr/share/gnome/help/package-manager/C/package-manager.xml 444 root bin f none usr/share/gnome/help/package-manager/C/legal.xml 444 root bin +f none usr/share/gnome/help/package-manager/C/other-trademarks.xml 444 root bin +f none usr/share/gnome/help/package-manager/C/sun-trademarks.xml 444 root bin d none usr/share/gnome/help/package-manager/C/figures 755 root bin -f none usr/share/gnome/help/package-manager/C/figures/package_manager.png 444 root bin +f none usr/share/gnome/help/package-manager/C/figures/pm_pkglist.png 444 root bin +f none usr/share/gnome/help/package-manager/C/figures/pm_store.png 444 root bin f none usr/share/gnome/help/package-manager/C/figures/update_all.png 444 root bin +f none usr/share/gnome/help/package-manager/C/figures/wi_start.png 444 root bin d none usr/share/icons 755 root other d none usr/share/icons/hicolor 755 root other d none usr/share/icons/hicolor/48x48 755 root other