How to Install and Uninstall php74-zephir.noarch Package on CentOS 8 / RHEL 8

Last updated: May 17,2024

1. Install "php74-zephir.noarch" package

This guide covers the steps necessary to install php74-zephir.noarch on CentOS 8 / RHEL 8


    
        
            $
        

        
            
                sudo dnf update
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo dnf install
            
                        
                php74-zephir.noarch
            
                    
    
    Copied

2. Uninstall "php74-zephir.noarch" package

Please follow the guidelines below to uninstall php74-zephir.noarch on CentOS 8 / RHEL 8:


    
        
            $
        

        
            
                sudo dnf remove
            
                        
                php74-zephir.noarch
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo dnf autoremove
            
                    
    
    Copied

3. Information about the php74-zephir.noarch package on CentOS 8 / RHEL 8

Last metadata expiration check: 1 day, 7:26:19 ago on Sun May 9 13:03:46 2021.
Available Packages
Name : php74-zephir
Version : 0.10.16
Release : 1.el8.remi
Architecture : noarch
Size : 418 k
Source : php74-zephir-0.10.16-1.el8.remi.src.rpm
Repository : remi-safe
Summary : Zephir language for creation of extensions for PHP.
URL : https://zephir-lang.com/
License : MIT
Description : Zephir - Ze(nd Engine) Ph(p) I(nt)r(mediate) - is a high level language
: that eases the creation and maintainability of extensions for PHP.
: Zephir extensions are exported to C code that can be compiled and
: optimized by major C compilers such as gcc/clang/vc++. Functionality
: is exposed to the PHP language.
:
: Main features:
: * Both dynamic/static typing
: * Reduced execution overhead compared with full interpretation
: * Restricted procedural programming, promoting OOP
: * Memory safety
: * Ahead-of-time (AOT) compiler to provide predictable performance
:
: Compiler design goals:
: * Multi-pass compilation
: * Type speculation/inference
: * Allow runtime profile-guided optimizations, pseudo-constant propagation
: and indirect/virtual function inlining