How to Install and Uninstall R-BiocIO.noarch Package on Fedora 35

Last updated: October 06,2024

1. Install "R-BiocIO.noarch" package

Please follow the guidance below to install R-BiocIO.noarch on Fedora 35


    
        
            $
        

        
            
                sudo dnf update
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo dnf install
            
                        
                R-BiocIO.noarch
            
                    
    
    Copied

2. Uninstall "R-BiocIO.noarch" package

This is a short guide on how to uninstall R-BiocIO.noarch on Fedora 35:


    
        
            $
        

        
            
                sudo dnf remove
            
                        
                R-BiocIO.noarch
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo dnf autoremove
            
                    
    
    Copied

3. Information about the R-BiocIO.noarch package on Fedora 35

Last metadata expiration check: 1:25:52 ago on Wed Sep 7 14:25:02 2022.
Available Packages
Name : R-BiocIO
Version : 1.2.0
Release : 2.fc35
Architecture : noarch
Size : 384 k
Source : R-BiocIO-1.2.0-2.fc35.src.rpm
Repository : fedora
Summary : Standard Input and Output for Bioconductor Packages
URL : http://www.bioconductor.org/packages/release/bioc/html/BiocIO.html
License : Artistic 2.0
Description : Implements `import()` and `export()` standard generics for importing and
: exporting biological data formats. `import()` supports whole-file as well as
: chunk-wise iterative import. The `import()` interface optionally provides a
: standard mechanism for 'lazy' access via `filter()` (on row or element-like
: components of the file resource), `select()` (on column-like components of
: the file resource) and `collect()`. The `import()` interface optionally
: provides transparent access to remote (e.g. via https) as well as local
: access. Developers can register a file extension, e.g., `.loom` for dispatch
: from character-based URIs to specific `import()` / `export()` methods based on
: classes representing file types, e.g., `LoomFile()`.