Table of Contents
Advertisement
Quick Links
Advertisement
Table of Contents
Subscribe to Our Youtube Channel
Related Manuals for Symantec WISE LINUX PACKAGE EDITOR 8.0 - REFERENCE V1.0
Summary of Contents for Symantec WISE LINUX PACKAGE EDITOR 8.0 - REFERENCE V1.0
- Page 1 Wise Linux Package Editor Reference...
- Page 2 Copyright © 2009 Symantec Corporation. All rights reserved. Symantec, the Symantec Logo, and Altiris are trademarks or registered trademarks of Symantec Corporation or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners.
-
Page 3: Technical Support
The Technical Support group also creates content for our online Knowledge Base. The Technical Support group works collaboratively with the other functional areas within Symantec to answer your questions in a timely fashion. For example, the Technical Support group works with Product Engineering and Symantec Security Response to provide alerting services and virus definition updates. - Page 4 Licensing and registration If your Symantec product requires registration or a license key, access our technical support Web page at the following URL: www.symantec.com/techsupp/ Customer service Customer service information is available at the following URL: www.symantec.com/techsupp/ Customer Service is available to assist with the following types of issues:...
- Page 5 Consulting Symantec Consulting Services provide on-site technical Services expertise from Symantec and its trusted partners. Symantec Consulting Services offer a variety of prepackaged and customizable options that include assessment, design, implementation, monitoring, and management capabilities. Each is focused on establishing and maintaining the integrity and availability of your IT resources.
-
Page 6: Table Of Contents
Contents Technical Support ............3 Chapter 1: Introduction to Linux Package Editor . - Page 7 Chapter 5: Using Script Editor..........42 The Script Editor Window .
-
Page 8: Chapter 1: Introduction To Linux Package Editor
Chapter 1 Introduction to Linux Package Editor This chapter includes the following topics: About Linux Package Editor on page 8 Starting Linux Package Editor on page 10 Conventions for Naming Linux Shell Variables on page 10 Product Documentation on page 11 About Linux Package Editor Many system administrators in a primarily Windows environment must also support Linux computers, typically servers. -
Page 9: About The Shell File
Introduction to Linux Package Editor software packages. A package consists of an archive of files along with information about the package, including name, version, and description. Information about all installed packages and the files that they create or change is stored in the RPM database on the Linux computer. -
Page 10: Starting Linux Package Editor
Introduction to Linux Package Editor Starting Linux Package Editor The first time you open Linux Package Editor, no project is open, so you cannot edit any pages. Once you create one or more new projects, Linux Package Editor always opens the last opened project at startup. -
Page 11: Product Documentation
The product release notes cover new features, enhancements, bug fixes, and known issues for the current version of this product. To access the release notes, select Release Notes from the Symantec program group on the Windows Start menu. Linux Package Editor Reference... -
Page 12: Chapter 2: Setting Up Linux Package Editor
Chapter 2 Setting Up Linux Package Editor This chapter includes the following topics: Requirements for setting up Linux Package Editor on page 12 Setting Options on page 12 Linux Environment Settings on page 13 Browsing the Linux File System on page 15 Requirements for setting up Linux Package Editor Before you use Linux Package Editor to create RPM packages: Set global options. -
Page 13: Linux Environment Settings
Setting Up Linux Package Editor The session log is different from the RPM log file, which logs events during RPM installation. Viewing the Session Log and Warnings on page 17. Linux Environment Settings The Linux Environment Settings dialog box, which you access by selecting Tools menu > Linux Environment Settings, lets you: Set up a Linux proxy computer. -
Page 14: Editing The Default User, Group, Package, And Package Group Lists
Setting Up Linux Package Editor Username Enter the user name that you use to log on to the Linux computer. SSH Password Enter an SSH password here and then re-enter it in Verify Password. Click Test to test the connection. A message indicates whether the connection was successful. -
Page 15: Browsing The Linux File System
Setting Up Linux Package Editor Obtain a text file containing users, groups, or package groups from a Linux computer and place the file in a directory that your development computer can access. (The user file is named passwd.) Select Tools menu > Linux Environment Settings. Click Import File and select a type of file to import from the button menu. -
Page 16: Chapter 3: Managing Linux Packages
Chapter 3 Managing Linux Packages This chapter includes the following topics: Building a Linux Installation Package on page 16 Viewing the Session Log and Warnings on page 17 Testing With Preflight Packages on page 18 Checking the Syntax of a Script on page 19 Linux Package Editor Reports on page 19... -
Page 17: Viewing The Session Log And Warnings
Managing Linux Packages File Name Specify the path and file name of the package file to be built. The default is the project name with the extension .sh. If you override the default, be sure to include the extension or a build error will occur. Compiler Variables Any compiler variables that are specified on the Compiler Variables page appear in this list. -
Page 18: Testing With Preflight Packages
Managing Linux Packages Testing With Preflight Packages The preflight capability in Linux Package Editor helps you determine whether a package will succeed or fail by testing it in your production environment before deployment. Preflight packages can perform environmental checks without actually distributing the package payload to the Linux computers. -
Page 19: Checking The Syntax Of A Script
Managing Linux Packages Checking the Syntax of a Script If a Linux computer is accessible to the Windows computer on which you create Linux packages, you can check the syntax of the scripts in a Linux package from within Linux Package Editor. -
Page 20: Building A Linux Archive File
Managing Linux Packages Click the link for the specific report to view. To refresh a report, click in the report pane and click on the toolbar. Building a Linux Archive File You might want to store a group of files in one file for easier backups and transfers. Example: You can create an archive file based on one package and then import it to another package. - Page 21 Managing Linux Packages Importing From a Linux Archive File on page 30 Linux Package Editor Reference...
-
Page 22: Chapter 4: Creating Linux Packages
Chapter 4 Creating Linux Packages This chapter includes the following topics: The Installation Expert Window on page 22 Defining the Version on page 24 Defining the Version on page 24 Files Page on page 25 About Dependency Relationships on page 31 Adding Dependencies on page 32 Adding Capabilities... - Page 23 Creating Linux Packages Installation Expert window in Linux Package Editor Page Groups Page Area View Navigation Build and Troubleshoot Page Groups Pages are organized into page groups. Click the group name to expand or collapse its pages. Click a page name to display that page. Page Area When you click a page name in a page group, this area displays the page’s options.
-
Page 24: General Information
Creating Linux Packages General Information On the General Information page, you enter information about the RPM package. This information appears in the package header. In Linux Package Editor, select Installation Expert > General Information and complete the page: Name Enter the name of the software being packaged. The package name is case sensitive. -
Page 25: Files Page
Creating Linux Packages In Linux Package Editor, select Installation Expert > Version and complete the page: Version Enter the version of the software being packaged. Typically, this information comes from the application’s developer. Do not include hyphens because RPM uses a hyphen to separate the version from the remainder of the package label. - Page 26 Creating Linux Packages Files page in Linux Package Editor Files in the Directories directory selected available to on the left. your computer. Directories to Files to be be installed on installed on the the Linux Linux computer. computer. About Installation Directories The lower-left list box is populated with predefined directories that represent a standard Red Hat Linux system.
-
Page 27: About Directory And File Settings
Creating Linux Packages Drag directories or files to the page from Windows Explorer. Drag directories or files from the upper list boxes to the lower list boxes. Right-click a file in the lower-right list box to open it in the text editor that is specified on the Options dialog box. -
Page 28: Completing The File Details Dialog
Creating Linux Packages default settings. Review the settings and edit them if necessary. Files in that directory inherit the directory’s settings. If you edit the settings for the first directory that you add in this manner, then those settings become the default for directories that you add subsequently. Predefined environment directories typically do not have settings in Linux Package Editor, because those directories already have settings on the Linux computer. - Page 29 Creating Linux Packages Destination Path Read-only. This is the path that the file will be installed to. File Owner Enter or select the owner of this file. File Group Enter or select the group that owns this file. File Class If this is a normal file, enter or select a description of the file.
-
Page 30: Adding Files To A Package
Creating Linux Packages Set Group ID Bit If this is an executable file, mark this to set the file to run with the same privileges as the file group specified above. Sticky Bit When the sticky bit is set on a directory, it restricts write permission by allowing users to delete only files that they own. -
Page 31: About Dependency Relationships
Creating Linux Packages To import files from a Linux archive file If you will import an RPM file, you must be in a new, empty package. However, you can import an archive file into an existing package. Select Tools menu > Import Linux Archive File. The Select Linux Archive File dialog box appears. -
Page 32: Adding Dependencies
Creating Linux Packages Adding Capabilities on page 34. Conflicts. The capabilities of the current package interfere with those in another package. RPM prevents you from installing a package that conflicts with other packages. This typically is used when packages provide similar capabilities. Example: sendmail, vmail, and exim are all mail transfer agents and therefore conflict with each other. -
Page 33: Handling Circular Dependencies
Creating Linux Packages Operator (Optional.) Select the operator to use during the package comparison. Version (Optional.) Enter the version of the above package that is required. If you enter a version number you must enter an operator above. Flags The following options represent bits in the flag RPMTAG_REQUIREFLAGS, which specifies the dependency range and context. -
Page 34: Adding Capabilities
Creating Linux Packages Example: You import an RPM for Application A into Linux Package Editor. The Dependencies page shows a dependency on Application B. During testing, you try to install Application B before you run the Application A installation. The Application B installation fails because it requires Application A. -
Page 35: Adding Conflicts
Creating Linux Packages Version (Optional.) Enter the version of the above package that is provided. If you enter a version number you must enter an operator above. Flags The following options represent bits in the flag RPMTAG_PROVIDEFLAGS, which specifies the capability range and context. These options might be marked in packages that you import. -
Page 36: Adding Obsolete Packages
Creating Linux Packages Operator (Optional.) Select the operator to use during the package comparison. Version (Optional.) Enter the version of the above package that conflicts. If you enter a version number you must enter an operator above. Flags The following options do not apply to this page and are not available: Provides Requires PreReq... -
Page 37: Adding Triggers
Creating Linux Packages Provides Requires PreReq Interpreter Config No Event PreInstall PostInstall PreUninstall PostUninstall Verification Trigger Install Trigger Uninstall Trigger Post-Uninstall Trigger Script Name See also: About Dependency Relationships on page 31 Adding Triggers On the Triggers page, you specify the packages that cause a trigger to occur in the current package. - Page 38 Creating Linux Packages Requires PreReq Interpreter Config No Event PreInstall PostInstall PreUninstall PostUninstall Verification Event Flag Specify the event that will cause the trigger to occur: Trigger Install Runs the trigger script when the trigger package specified above is installed or upgraded, or when that package is already installed, and the current package is installed or upgraded.
-
Page 39: Adding Platforms
Creating Linux Packages If you created another type of script, use the right pane of Script Editor as a basic text editor. The first line in the script must define the command interpreter. Examples: #!/usr/bin/perl #!/usr/bin/sh #!/usr/bin/env python See also: About Dependency Relationships on page 31 Adding Platforms... -
Page 40: Setting Compiler Variables
Creating Linux Packages Use default log filename Mark this to name the log file with the default name (Project-Type-Client- DateTime.txt). To provide a specific name for the log file, clear this check box and enter the name in the Log filename field. Post log file to URL To post a copy of the installation log to a network location, mark this and enter the location in the URL field. -
Page 41: Specifying Build Settings
Creating Linux Packages To add a compiler variable In Linux Package Editor, select Installation Expert > Compiler Variables page, click Add, and complete the Compiler Variables dialog box: Variable Name Enter the name of the compiler variable. You do not need to include the % characters. -
Page 42: Chapter 5: Using Script Editor
Chapter 5 Using Script Editor This chapter includes the following topics: The Script Editor Window on page 42 Viewing Script Code on page 43 Adding an Action to a Script on page 44 Editing Scripts The Script Editor Window Script Editor provides a powerful and easy-to-use scripting environment. You don’t need to memorize commands, because Script Editor supports a point-and-click method of scripting. -
Page 43: Viewing Script Code
Using Script Editor Actions The Actions list displays the actions that you can add to your script. To view a different category of actions, select the category from the Actions drop-down list. The actions that appear in the Actions list are filtered according to the current install event. Installation Script Area The installation script area displays the installation scripts that are run by Linux Package Editor. -
Page 44: Adding An Action To A Script
Using Script Editor Specify the location and name of the shell file, and then click Save. To view the code on the destination Linux computer, use the cat command (example: cat shell_file.sh). To view the code on a Windows computer, open it in Wordpad. -
Page 45: Finding And Replacing Text In A Script
Using Script Editor If you’re copying the lines to another installation, open that installation script in Script Editor. Select a line in the script above which to place the lines you copied, then select Edit menu > Paste. The lines appear above the line you selected. To duplicate or move script lines Select one or more script lines. -
Page 46: Chapter 6: Script Actions
Chapter 6 Script Actions This chapter includes the following topics: Add Text to INSTALL.LOG Add User or Group Call Script Change File Attributes Check File or Directory Check HTTP Connection Check Process Check RPM Database Compiler Variable Actions Copy File(s) Create Directory Delete File or Directory Delete Line From Text File... -
Page 47: Add Text To Install.log
Script Actions Most of the script actions in Script Editor run Linux commands. To view the Linux commands that underly the current Linux Package Editor script, save the script as a shell file. Viewing Script Code on page 43. Add Text to INSTALL.LOG This action adds a line of text to the installation log that is defined in Installation Expert >... -
Page 48: Call Script
Script Actions Leave this field blank and mark System Account to assign this user or group the smallest ID available that is less than 500. (Linux reserves IDs below 500 for system accounts.) Leave this field blank and don’t mark System Account to assign this user or group the next available ID starting with 500. - Page 49 Script Actions Types of Scripts The following scripts are supported: WiseScript (.wsl). This is a special shell script format that allows the use of WiseScript commands. It is converted to a shell script (.sh) file. Perl Script (.pl). Bourne Shell (.sh). Global and Local Scripts Global scripts are accessible by all packages, which lets you re-use them and share them with colleagues.
-
Page 50: Change File Attributes
Script Actions Change File Attributes This action changes the permissions and ownership attributes for a file or directory on the Linux computer. When the action is run, the results are placed in the $RETURNCODE variable: The action ran successfully. non-zero The action was unsuccessful. -
Page 51: Check Http Connection
Script Actions Check HTTP Connection This action uses the Wget downloading tool to determine whether a given URL is valid. When the action is run, the results are placed in the $RETURNCODE variable: The URL was valid. non-zero The action was unsuccessful. Note If the Web server redirects URLs that are not valid to another internal Web page, this action does not detect an error. -
Page 52: Compiler Variable Actions
Script Actions To complete the dialog box: Package Name Enter or select a package on which to perform the query. Operation Specify the check to perform. Each option returns a different value to the variable you define below. Is Package Installed? If the package is installed, 0 is returned to the variable. -
Page 53: Copy File(S)
Script Actions time, and the actions inside a compiler variable If block are added to the script according to the value of the compiler variable. You create compiler variables on the Compiler Variables page. When you create a compiler variable, you specify its default value. Setting Compiler Variables on page 40. -
Page 54: Create Directory
Script Actions non-zero The action was unsuccessful. To complete the dialog box Source File/Path Specify the file or directory to copy. You can use the following wildcards: *, ?, and Destination Specify the path to copy to. Create Directory This action creates a directory on the Linux computer. When the action is run, the results are placed in the $RETURNCODE variable: The action ran successfully. -
Page 55: Delete User Or Group
Script Actions To complete the dialog box File to Modify Specify the file from which to delete a line. Line Enter the text that is in the line to delete. You can use any regular expression. If you enter a substring, the entire line is deleted. Delete All Occurrences Mark this to delete all occurrences of the text in the file. -
Page 56: End If
Script Actions See also: If Statement on page 59 End If This action marks the end of an If block. It takes no parameters, and selecting it from the Actions list inserts it directly into the script with no further dialog boxes or prompts. See also: If Statement on page 59... -
Page 57: Exit Installation
Script Actions Typically, you would use this for a single Linux command or a small number of commands, where it would be easier to type the command than to write a script and assign that script to a Call Script Action. To complete the dialog box Shell command Enter the command to send to the bash shell. -
Page 58: Get Temporary Filename
Script Actions Retrieve Select the information to retrieve: Architecture The type of computer. Linux Package Editor supports i386 computers only. Current Date This includes the time in 24-hour format. Example: Fri Mar 24 14:53:53 UTC 2006. Current Time The time is in 24-hour format. File Group The group owner of the file that is specified in Pathname. -
Page 59: Halt Compile
Script Actions Halt Compile This action immediately stops the compile (build) process. It must be placed between Compiler Variable If and Compiler Variable End statements or the script will never build. Use this to ensure that conditions are met before compiling. To complete the dialog box Enter Message Text Enter a message to display to the user if the build is stopped. -
Page 60: Manage A Service
Script Actions To complete the dialog box Filename Specify the path of the text file to edit. Text to Insert Enter the text to add to the file. Line Number Enter the line number at which to insert the new text. Enter 0 to append to the end of the file. -
Page 61: Post To Http Server
Script Actions Runlevel If you are adding or modifying a service, mark the runlevels in which the service should start. Start Service After Adding or Stop Before Deleting If you clear this option and you are starting a service, the service does not start until Linux is restarted in one of the marked runlevels. -
Page 62: Remark
Script Actions To complete the dialog box Pathname Specify the full path to the text file to be read or written on the Linux computer (example: $INSTALLDIR\File.txt). Variable Specify the variable to write to or read from (example: TEXTLINE). Action Select an action: Read lines of file into variable Reads the contents of the text file into the variable. -
Page 63: Search File For Text
Script Actions Search File for Text This action finds a text string in a file on the Linux computer. When the action is run, the number of occurrences found is placed in the $RETURNCODE variable. To complete the dialog box Search File Specify the file to search. - Page 64 Script Actions Sets the variable to the middle portion of the string in Variable Name (from a specified starting point to the end of the string) In Argument, enter the starting point as the number of characters from the left of the string. Example: If the string is 12345, and you specify 2 as the starting point, this returns 2345.
-
Page 65: Start/Stop Process
Script Actions For a numeric expression, enter a valid Linux bc command. You can use symbols such as + and – for addition and subtraction. For a logical expression, enter a valid Linux Bash test command. You can use -a for an AND operation and -o for an OR operation. - Page 66 Script Actions See also: End While on page 56 Linux Package Editor Reference...
-
Page 67: Index
Index Symbols CGI 61 documentation file 28 Change File Attributes 50 documentation, Wise 11 $INSTALLDIR, value 41 Check button 19 $WISEFOLDER Check File or Directory 50 about 26 edit Linux configuration item 14 circular dependencies 34 Check HTTP Connection 51 Else Statement 55 value 41 Check Process 51... - Page 68 ending 56 LPR file 8, 9, 10 Halt Compile 59 Read/Update Text File 61 help readme about 11 See release notes Manage a Service 60 Installation Expert, Linux 23 Red Hat 8 manual, reference 11 using 11 reference manual 11 HTTP release 25 checking connection 51...
- Page 69 settings directory 27 warnings 17 editing 28 While Statement SH file beginning 65 See shell file ending 56 shell command, executing 56 Wise management directory 39 shell file WiseForLinux.log 17 about 9 building 16 shell variable assigning value 10 naming conventions 10 using 10 source RPM 8 spec file 8...
Need help?
Do you have a question about the WISE LINUX PACKAGE EDITOR 8.0 - REFERENCE V1.0 and is the answer not in the manual?
Questions and answers