Viewtier Parabuild 3.1 Administrator's Manual Viewtier Parabuild 3.1: Administrator's Manual Copyright © 2004-2008 Viewtier Systems

Total Page:16

File Type:pdf, Size:1020Kb

Viewtier Parabuild 3.1 Administrator's Manual Viewtier Parabuild 3.1: Administrator's Manual Copyright © 2004-2008 Viewtier Systems Viewtier Parabuild 3.1 Administrator's Manual Viewtier Parabuild 3.1: Administrator's Manual Copyright © 2004-2008 Viewtier Systems Table of Contents Preface .....................................................................................................................ix About This Manual ............................................................................................. ix Audience ..........................................................................................................ix Technical Support .............................................................................................. ix 1. Build Statuses Page .................................................................................................. 1 List View Mode ..................................................................................................1 Detailed View Mode ............................................................................................ 1 Build Control Commands ..................................................................................... 1 2. System Configuration ............................................................................................... 3 General System Settings ....................................................................................... 3 E-Mail Settings ........................................................................................... 3 Appearance Settings .................................................................................... 5 Stability Settings ......................................................................................... 7 Display Groups ................................................................................................... 8 Adding A Display Group .............................................................................. 8 Editing A Display Group .............................................................................. 8 Deleting A Display Group ............................................................................ 8 Built-In Display Groups ............................................................................... 8 Instant Messaging Settings .................................................................................... 8 Jabber Configuration ................................................................................... 9 Entering Parabuild Licenses .................................................................................. 9 Configuring LDAP Authentication ....................................................................... 10 Connection URL ....................................................................................... 10 Connection Principal And Connection Credentials ........................................... 10 Connection Security Level .......................................................................... 10 Processing Referrals .................................................................................. 11 User Distinguished Name Template .............................................................. 11 User Search Template ................................................................................ 11 Base Element For User Searches .................................................................. 11 Search Entire Subtree ................................................................................. 12 User Password Attribute Name .................................................................... 12 Credentials Digest Algorithm ...................................................................... 12 User E-Mail Attribute Name ....................................................................... 12 Add First-Time Users To Group ................................................................... 12 Testing LDAP Configuration ....................................................................... 12 Integrating With Active Directory ................................................................ 12 3. Configuring a Build ............................................................................................... 13 Overview ......................................................................................................... 13 General Settings Form ....................................................................................... 13 Naming A Build ............................................................................................... 13 Selecting Build Type ......................................................................................... 14 Automatic Builds ...................................................................................... 14 Scheduled Builds ...................................................................................... 14 Manual Builds .......................................................................................... 15 Parallel Builds .......................................................................................... 15 Selecting Build Results Access ............................................................................ 15 Detailed Build Configuration ............................................................................... 16 Adding Build Steps ................................................................................... 16 Configuring ClearCase Access ..................................................................... 18 Configuring CVS Access ............................................................................ 20 Configuring Watching For File System Changes ............................................. 25 Configuring Generic Version Control System Access ....................................... 27 Configuring MKS Access ........................................................................... 29 iv Viewtier Parabuild 3.1 Configuring Perforce Access ....................................................................... 30 Configuring Serena Version Manager (PVCS) Access ...................................... 34 Configuring StarTeam Access ..................................................................... 37 Configuring Subversion Access ................................................................... 38 Configuring Surround Access ...................................................................... 40 Configuring Vault Access ........................................................................... 42 Configuring Visual SourceSafe Access .......................................................... 44 Configuring Build Schedule ........................................................................ 46 Configuring Build Labeling ........................................................................ 48 Notification Settings Tab .................................................................................... 49 Setting Notification Policy .......................................................................... 49 Mapping Names of Users of a Version Control System to E-mail ....................... 49 Using E-mails Provided by Version Control System ........................................ 49 Setting Default E-mail Domain .................................................................... 50 Notifying Other Users ................................................................................ 50 Understanding Relative Paths .............................................................................. 51 Build Logs Tab ................................................................................................. 51 Setting Up Build Logs Compression ............................................................. 51 Adding Custom Logs ................................................................................. 51 Adding a Single Text File Log ..................................................................... 52 Adding a Directory with Text File Logs ......................................................... 52 Adding a Single HTML File Log .................................................................. 52 Adding a HTML Directory Log ................................................................... 52 Build Results Tab .............................................................................................. 53 Setting Up Automatic Deleting Of Build Results ............................................. 53 Configuring Single File Result ..................................................................... 53 Configuring Directory Result ...................................................................... 53 Configuring An External URL Result ........................................................... 53 Accessing Externally Stored Build Results ..................................................... 54 Debugging Build Result Path ...................................................................... 54 Release Notes Tab ............................................................................................. 54 Linking Release Notes And Changes ............................................................ 55 Retrieving Release Notes From Bugzilla ........................................................ 55 Parameters Tab ................................................................................................. 57 Version Counter ........................................................................................ 57 Manual Run Parameters ............................................................................
Recommended publications
  • Open Source Used in Personnel 0.501
    Open Source Used In personnel 0.501 Cisco Systems, Inc. www.cisco.com Cisco has more than 200 offices worldwide. Addresses, phone numbers, and fax numbers are listed on the Cisco website at www.cisco.com/go/offices. Text Part Number: 78EE117C99-172189840 Open Source Used In personnel 0.501 1 This document contains licenses and notices for open source software used in this product. With respect to the free/open source software listed in this document, if you have any questions or wish to receive a copy of any source code to which you may be entitled under the applicable free/open source license(s) (such as the GNU Lesser/General Public License), please contact us at [email protected]. In your requests please include the following reference number 78EE117C99-172189840 Contents 1.1 aiocontextvars 0.2.0 1.1.1 Available under license 1.2 aiohttp 3.4.4 1.2.1 Available under license 1.3 aiohttp_cors 0.7.0 1.3.1 Available under license 1.4 alabaster 0.7.12 1.4.1 Available under license 1.5 amqp 2.3.2 1.5.1 Available under license 1.6 argh 0.26.2 1.7 arrow 0.8.0 1.7.1 Available under license 1.8 asn1crypto 0.24.0 1.8.1 Available under license 1.9 async-timeout 3.0.1 1.9.1 Available under license 1.10 attrs 18.2.0 1.10.1 Available under license 1.11 avro-python3 1.8.2 1.11.1 Available under license 1.12 Babel 2.6.0 1.12.1 Available under license 1.13 billiard 3.5.0.4 1.13.1 Available under license 1.14 bleach 3.0.2 Open Source Used In personnel 0.501 2 1.14.1 Available under license 1.15 boto3 1.5.15 1.15.1 Available under
    [Show full text]
  • Python Programming Language
    ภาษาโปรแกรมมิ่งไพธอน Python programming language เอกวิทยาการคอมพิวเตอรì คณะวิทยาศาสตรì มหาวิทยาลัยนเรศวร 2 รายชื่อผูéจัดทำ ชื่อ รหัสนิสิต หนéาที่ดำเนินการ นายฉัตรชัย ดำดี 46320388 แบบฝกหัด นายทรงยศ คชนิล 46320511 จัดทำเอกสารการเรียน นางสาวธัญญากร แกéวประสงคì 46320610 ผูéชèวยสอน นายประจักษì เจตะภัย 46320693 ผูéชèวยสอนและแบบฝกหัด นายมารุต จันทรìบัว 46320818 แบบฝกหัด นางสาวศรินยา อยูèสุขดี 46320925 ผูéชèวยสอน นางสาวณัฐณิชา คงประกอบ 46321097 ผูéชèวยสอน นายอุทิศ ศักดิ์สิทธิ์ 46321139 ผูéชèวยสอนและแบบฝกหัด นายอรรณพ สุวัฒนพิเศษ 46321150 ผูéสอนและจัดทำเอกสารเรียน 3 4 คำนำ ภาษาไพธอนเปนภาษาที่ไดéรับความนิยมอยèางมากในปจจุบันเนื่องจากความสามารถที่สูง, การเรียนรูéที่ รวดเร็ว, การเขียนระบบที่เขéาใจงèาย และสามารถขยายขีดความสามารถในการสรéางโปรแกรมและซอฟตìแวรì ที่สูงมากขึ้นตลอดเวลา ทางทีมผูéจัดทำจึงเล็งเห็นวèาควรนำความรูé ความเขéาใจในการเขียนโปรแกรมดéวยภาษา ไพธอนมาเผยแพรè ดéวยจะไดéผูéอื่นไดéรับความรูéและไดéเขéาถึงภาษาที่เขียนใจงèาย, ทำงานรวดเร็ว และสามารถ สรéางสรรคìงานไดéอยèางมีความสามารถสูง อีกทั้งซอฟตìแวรìที่ใชéสรéางโปรแกรมและซอฟตìแวรìดéวยภาษาไพธอน นั้นมีทั้งแจกฟรี, รหัสเปด และเชิงธุรกิจ ซึ่งมีขีดความสามารถที่แตกตèางกัน แตèถึงแมéจะเปนซอฟตìแวรìที่ใชé เขียนโปรแกรมดéวยภาษาไพธอนจะแจกฟรี หรือเปนรหัสเปด ก็ไมèไดéดéอยไปกวèาเชิงธุรกิจเลย จึงเปนทางเลือก ที่ดีที่จะศึกษาเปนทางเลือกอีกทางหนึ่งนอกเหนือจากภาษาอื่น ๆ ที่ไดéรับความนิยมอยูèแลéว ทางทีมงานจึงหวังวèาทèานผูéที่นำเอกสารนี้ไปใชéในการศึกษาจะไดéรับประโยชนìสูงสุดในการเขียนโปรแกรม และซอฟตìแวรìดéวยภาษาไพธอน ทีมผูéจัดทำ 5 6 สารบัญ 1 แนะนำภาษาไพธอน 13 1.1 ประวัติ . 13 1.1.1 Python 1.0 . 13 1.1.2 Python 2.0 . 14 1.1.3
    [Show full text]
  • Jetbrains Upsource Comparison Upsource Is a Powerful Tool for Teams Wish- Key Benefits Ing to Improve Their Code, Projects and Pro- Cesses
    JetBrains Upsource Comparison Upsource is a powerful tool for teams wish- Key benefits ing to improve their code, projects and pro- cesses. It serves as a polyglot code review How Upsource Compares to Other Code Review Tools tool, a source of data-driven project ana- lytics, an intelligent repository browser and Accuracy of Comparison a team collaboration center. Upsource boasts in-depth knowledge of Java, PHP, JavaScript, Integration with JetBrains Tools Python, and Kotlin to increase the efcien- cy of code reviews. It continuously analyzes Sales Contacts the repository activity providing a valuable insight into potential design problems and project risks. On top of that Upsource makes team collaboration easy and enjoyable. Key benefits IDE-level code insight to help developers Automated workflow, to minimize manual tasks. Powerful search engine. understand and review code changes more efectively. Smart suggestion of suitable reviewers, revi- IDE plugins that allow developers to partici- sions, etc. based on historical data and intel- pate in code reviews right from their IDEs. Data-driven project analytics highlighting ligent progress tracking. potential design flaws such as hotspots, abandoned files and more. Unified access to all your Git, Mercurial, Secure, and scalable. Perforce or Subversion projects. To learn more about Upsource, please visit our website at jetbrains.com/upsource. How Upsource Compares to Other Code Review Tools JetBrains has extensively researched various As all the products mentioned in the docu- tools to come up with a useful comparison ment are being actively developed and their table. We tried to make it as comprehensive functionality changes on a regular basis, this and neutral as we possibly could.
    [Show full text]
  • Documentation for Fisheye 2.8 Documentation for Fisheye 2.8 2
    Documentation for FishEye 2.8 Documentation for FishEye 2.8 2 Contents Getting started . 8 Supported platforms . 8 End of Support Announcements for FishEye . 12 End of Support Announcement for IBM ClearCase . 14 End of Support Announcement for Internally Managed Repositories . 14 Installing FishEye on Windows . 16 Running FishEye as a Windows service . 19 Installing FishEye on Linux and Mac . 23 Starting to use FishEye . 26 Configuring JIRA Integration in the Setup Wizard . 31 Using FishEye . 38 Using the FishEye Screens . 39 Browsing through a repository . 41 Searching FishEye . 44 Viewing a File . 49 Viewing File Content . 50 Using Side by Side Diff View . 51 Viewing a File History . 53 Viewing the Changelog . 54 FishEye Charts . 56 Using Favourites in FishEye . 61 Changeset Discussions . 64 Viewing the commit graph for a repository . 64 Viewing People's Statistics . 68 Using smart commits . 70 Changing your User Profile . 75 Re-setting your password . 79 Antglob Reference Guide . 80 Date Expressions Reference Guide . 81 EyeQL Reference Guide . 82 Administering FishEye . 88 Managing your repositories . 89 Adding an External Repository . 91 CVS . 92 Git . 93 Mercurial . 96 Perforce . 98 Subversion . 101 SVN fisheye.access . 105 SVN tag and branch structure . 106 Adding an Internal Repository . 114 Enabling Repository Management in FishEye . 115 Creating Git Repositories . 117 Forking Git Repositories . 119 Deleting a Git Repository . 122 Setting up a Repository Client . 122 CVS Client . 122 Git Client . 122 Mercurial Client . 122 Perforce Client . 123 Subversion Client . 124 Native Subversion Client . 124 SVNkit Client . 126 Re-indexing your Repository . 126 Repository Options . 128 Authentication . 130 Created by Atlassian in 2012.
    [Show full text]
  • REMOTE Preferredsubmitted to Others Without His Explicit Permission
    For more on Gilbert’s job hunt visit Gilbert’s personal web site Copyright 2021 by Gilbert Healton. Gilbert’s details can not be http://resume.healton.net/ REMOTE PREFERREDsubmitted to others without his explicit permission. Gilbert Healton [email protected] Perl-5, C, Linux with strong mentoring, planning. https://www.linkedin.com/in/ghealton/ Multii-language team software engineer. Now strongest in Perl, C, shell Arenas: commands, SQL. Linux and UNIX. History of Template Toolkit, HTML, Remote work ●●●● JavaScript, Apache, TCP/IP, networking, Git, and SVN. Very strong Back ends ●●●●● design, mentoring, documentation. Great customer support. Telcom ●●●● Net Security ○●●● 2020-08 to Software Developer – SMD Delivery – ESP 2021-06 Hard Skills: bash, zsh, Remote. Coding ●●●● C, perl, lua. Working on cloud based SMTP engine. Analyst ●●●●● AWS (AL1, ✔ Feature improvements written in C and Lua. Perl tests. Design ●●●●● Athena SQL, ✔ Document processes and on boarding processes. Documents ●●●● builds, ...) ✔ Use Circonus graphs to analyze failures. Debugging ●●●● github, git, ✔ Use git and Mercurial tools for reviews and source 2038 Bug fix ●●●● Mercurial management. Networking: (hg, Fisheye, ✔ “Interrupt Team” duties included 24x7 on-call duties, ssh, rsync, ○●●● Bamboo). starting build pipelines, responding to problems & requests. dev/tcp TCP/IP sockets ○●●● 2020-03 to Shell Developer – back end – energy sector Message queues ○●●● 2020-08 EOC Soft Skills: bash, ksh, DXC Technology. Remote multinational. Migrating large distributed AIX applications to Linux. Detail attention ●●●● csh, RHEL Life Learning ●●●● ✔ Quickly migrated scripts from suite with the most scripts. Oracle, perl, Legacy Apps ●●●●● ✔ Writing scripts to scan and automate code changes. AutoSys shell Mentoring ●●●●● Scripts, ✔ Bringing automated tests to environment without any.
    [Show full text]
  • Version Control with Subversion for Subversion 1.4 (Compiled from R2639)
    Version Control with Subversion For Subversion 1.4 (Compiled from r2639) Ben Collins-Sussman Brian W. Fitzpatrick C. Michael Pilato Version Control with Subversion: For Subversion 1.4: (Compiled from r2639) by Ben Collins-Sussman, Brian W. Fitzpatrick, and C. Michael Pilato Published (TBA) Copyright © 2002, 2003, 2004, 2005, 2006, 2007 Ben Collins-SussmanBrian W. FitzpatrickC. Michael Pilato This work is licensed under the Creative Commons Attribution License. To view a copy of this license, visit ht- tp://creativecommons.org/licenses/by/2.0/ or send a letter to Creative Commons, 559 Nathan Abbott Way, Stanford, California 94305, USA. Table of Contents Foreword ................................................................................................................ xi Preface ..................................................................................................................xiii Audience ........................................................................................................xiii How to Read this Book ....................................................................................xiv Conventions Used in This Book .......................................................................xiv Typographic Conventions ........................................................................xiv Icons ...................................................................................................... xv Organization of This Book ..............................................................................
    [Show full text]
  • Collabnet Subversion Edge User Guide 2 | Subversion Edge | TOC
    CollabNet Subversion Edge User Guide 2 | Subversion Edge | TOC Contents Welcome to CollabNet Subversion Edge.............................................................................7 Set up Subversion Edge .......................................................................................................8 Install Subversion Edge ...........................................................................................................................8 Install Subversion Edge on Windows...........................................................................................8 Install Subversion Edge on Linux................................................................................................9 Install Subversion Edge on Solaris.............................................................................................10 Configure the server...............................................................................................................................12 Configure general server settings...............................................................................................12 Configure advanced server settings............................................................................................13 Configure authentication settings...............................................................................................13 Configure a proxy server............................................................................................................14 Configure the mail server...........................................................................................................14
    [Show full text]
  • Integrating Static Code Analysis and Defect Tracking
    MASARYK UNIVERSITY FACULTY}w¡¢£¤¥¦§¨ OF I !"#$%&'()+,-./012345<yA|NFORMATICS Integrating Static Code Analysis and Defect Tracking MASTER THESIS Jakub Papcun Brno, 2014 Declaration Hereby I declare, that this paper is my original authorial work, which I have worked out by my own. All sources, references and literature used or excerpted during elaboration of this work are properly cited and listed in complete reference to the due source. Supervisor: Ing. RNDr. Barbora Bühnová, Ph.D. iv Acknowledgements I would like to thank my supervisor, Barbora Bühnová, for providing valuable feedback and guidance. I would also like to thank Ronny Kolb, for his patient guidance and all the advice he gave me during whole work on the thesis. Last but not least I would like to thank all members of ACT team in Honeywell ACS in Brno for all their help and inputs to my thesis. v Abstract Static code analysis is a powerful way of improving the quality of source code. Using tools such as Klocwork, issues in source code can be automatically detected. Some of those issues represent defects injected during implementation activities or even during earlier develop- ment phases. These issues should be properly tracked and analyzed. The present thesis investigates on how to best integrate static code analysis and defect tracking with the goal of using static code analysis data for project tracking and continuous improvement of the development process used by teams in Honeywell ACS. The thesis in- cludes the analysis of the state-of-the-art and state-of-the-practice regarding defect tracking from static code analysis tools.
    [Show full text]
  • Applying Agile Project Management for Accelerator Controls Software W
    RPPB05 Proceedings of ICALEPCS07, Knoxville, Tennessee, USA APPLYING AGILE PROJECT MANAGEMENT FOR ACCELERATOR CONTROLS SOFTWARE W. Sliwinski, N. Stapley, CERN, Geneva, Switzerland Abstract engineers, who are members of AB-CO group, develop Developing accelerator controls software is a frameworks, core components and complete systems. challenging task requiring not only a thorough knowledge Thus, the users’ community is diverse, the level of of the different aspects of particle accelerator operations, proficiency in programming varies and many people but also application of good development practices and within it work on temporary basis (such as project robust project management tools. Thus, there was a associates, fellows and technical students) for the Large demand for a complete environment for both developing Hadron Collider (LHC) start up. and deploying accelerator controls software, as well as the Requirements of the Process tools to manage the projects. As an outcome, a versatile development process was formulated, covering the Taking into account the needs of the controls controls software life cycle from the inception phase up to community and the specific nature of the controls domain, the release and deployment of the deliverables. In a list of requirements can be formulated which addition, a development environment was created characterize the properties of the anticipated development providing management tools that: standardize the process: common infrastructure for all the concerned projects; help • Maximise ease of use by providing a quick to organize work within project teams; ease the process of comprehension time (particularly significant for versioning and releasing; and provide an easy integration temporary members). of the test procedures and quality assurance reports.
    [Show full text]
  • Release Notes for Debian 7.0 (Wheezy), S/390
    Release Notes for Debian 7.0 (wheezy), S/390 The Debian Documentation Project (http://www.debian.org/doc/) November 20, 2018 Release Notes for Debian 7.0 (wheezy), S/390 This document is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License, version 2, as published by the Free Software Foundation. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA. The license text can also be found at http://www.gnu.org/licenses/gpl-2.0.html and /usr/ share/common-licenses/GPL-2 on Debian. ii Contents 1 Introduction 1 1.1 Reporting bugs on this document . 1 1.2 Contributing upgrade reports . 1 1.3 Sources for this document . 2 2 What’s new in Debian 7.0 3 2.1 Supported architectures . 3 2.2 What’s new for S390? . 4 2.3 What’s new in the distribution? . 4 2.3.1 CDs, DVDs and BDs . 5 2.3.2 Multiarch . 5 2.3.3 Dependency booting . 5 2.3.4 systemd . 5 2.3.5 Multimedia . 5 2.3.6 Hardened security . 5 2.3.7 AppArmor . 6 2.3.8 The stable-backports section .
    [Show full text]
  • TCD65-141111-2205-6028.Pdf
    1. TeamCity Documentation . 3 1.1 TeamCityReference . 4 1.1.1 What's New in TeamCity 6.5 . 4 1.1.2 Getting Started . 10 1.1.3 Concepts . 14 1.1.3.1 Agent Home Directory . 15 1.1.3.2 Agent Requirements . 16 1.1.3.3 Agent Work Directory . 16 1.1.3.4 Authentication Scheme . 16 1.1.3.5 Build Agent . 17 1.1.3.6 Build Artifact . 18 1.1.3.7 Build Chain . 18 1.1.3.8 Build Checkout Directory . 19 1.1.3.9 Build Configuration . 20 1.1.3.10 Build Configuration Template . 21 1.1.3.11 Build Grid . 22 1.1.3.12 Build History . 22 1.1.3.13 Build Log . 23 1.1.3.14 Build Number . 23 1.1.3.15 Build Queue . 23 1.1.3.16 Build Runner . 24 1.1.3.17 Build State . 24 1.1.3.18 Build Tag . 25 1.1.3.19 Build Working Directory . 25 1.1.3.20 Change . 26 1.1.3.21 Change State . 26 1.1.3.22 Clean Checkout . 27 1.1.3.23 Clean-Up . 28 1.1.3.24 Code Coverage . 28 1.1.3.25 Code Duplicates . 29 1.1.3.26 Code Inspection . 29 1.1.3.27 Continuous Integration . 29 1.1.3.28 Dependent Build . 30 1.1.3.29 Difference Viewer . 31 1.1.3.30 Guest User . 32 1.1.3.31 History Build . 32 1.1.3.32 Notifier . 33 1.1.3.33 Personal Build .
    [Show full text]
  • Rancid Server Build and Operation Overview
    Rancid Server Build and Operation Overview Installation The installation will cover the setup and configuration of a RANCID server using Fedora 15 Basic List of software • OS = Fedora15 • Rancid = Really Awesome New Cisco config Differ (http://www.shrubbery.net/rancid/) v2.3.6 • CVS = Concurrent Versions System (http://www.nongnu.org/cvs/) v1.11.23-15 • ViewVC = Front end to CVS (http://www.viewvc.org/ ) v1.1.11-1 • Python = Programming Language (http://www.python.org/ ) v2.7.1-7 • RCS = Revision Control System (http://www.cs.purdue.edu/homes/trinkle/RCS/) v5.7-37 • Apache = Linux Webserver (http://httpd.apache.org/) v2.2.17-10 • MySQL = Database (http://www.mysql.com/) v5.5.13-1 • MySQLdb = Python connector for mysql (http://sourceforge.net/projects/mysql-python) • PHP = Widely-used general-purpose scripting language that is especially suited for Web development and can be embedded into HTML (http://www.php.net/ ) • Pygments – Generic Syntax Highlighter (http://pygments.org/ ) The basic install is as follows. This is in no way a fully locked down system. 1) Install the base OS 2) Run “yum update” - this will do an upgrade of all packages on the OS 3) Reboot 4) Log into the console 5) Run the following commands (some packages may already be installed) • yum -y install expect cvs python httpd mysql mysql-server gcc make autoconf gccc++ kernel-devel mod_python • yum groupinstall “Development Tools” MySQL-python diffutils • yum install php-common php-gd php-mcrypt php-pear php-pecl-memcache phpmhash php-mysql php-xml • yum update 6) Reboot
    [Show full text]