How to Install and Uninstall golang-github-hashicorp-errwrap-devel.noarch Package on Fedora 36

Last updated: September 29,2024

1. Install "golang-github-hashicorp-errwrap-devel.noarch" package

In this section, we are going to explain the necessary steps to install golang-github-hashicorp-errwrap-devel.noarch on Fedora 36


    
        
            $
        

        
            
                sudo dnf update
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo dnf install
            
                        
                golang-github-hashicorp-errwrap-devel.noarch
            
                    
    
    Copied

2. Uninstall "golang-github-hashicorp-errwrap-devel.noarch" package

Please follow the instructions below to uninstall golang-github-hashicorp-errwrap-devel.noarch on Fedora 36:


    
        
            $
        

        
            
                sudo dnf remove
            
                        
                golang-github-hashicorp-errwrap-devel.noarch
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo dnf autoremove
            
                    
    
    Copied

3. Information about the golang-github-hashicorp-errwrap-devel.noarch package on Fedora 36

Last metadata expiration check: 2:21:35 ago on Thu Sep 8 08:04:50 2022.
Available Packages
Name : golang-github-hashicorp-errwrap-devel
Version : 1.1.0
Release : 4.fc36
Architecture : noarch
Size : 18 k
Source : golang-github-hashicorp-errwrap-1.1.0-4.fc36.src.rpm
Repository : fedora
Summary : Go library for wrapping and querying errors
URL : https://github.com/hashicorp/errwrap
License : MPLv2.0
Description : Errwrap is a package for Go that formalizes the pattern of wrapping errors and
: checking if an error contains another error.
:
: There is a common pattern in Go of taking a returned error value and then
: wrapping it (such as with fmt.Errorf) before returning it. The problem with this
: pattern is that you completely lose the original error structure.
:
: Arguably the correct approach is that you should make a custom structure
: implementing the error interface, and have the original error as a field on that
: structure, such as this example. This is a good approach, but you have to know
: the entire chain of possible rewrapping that happens, when you might just care
: about one.
:
: Errwrap formalizes this pattern (it doesn't matter what approach you use above)
: by giving a single interface for wrapping errors, checking if a specific error
: is wrapped, and extracting that error.
:
: This package contains the source code needed for building packages that
: reference the following Go import paths:
: – github.com/hashicorp/errwrap