How to Install and Uninstall texlive-filecontentsdef Package on openSUSE Leap

Last updated: September 20,2024

1. Install "texlive-filecontentsdef" package

Please follow the step by step instructions below to install texlive-filecontentsdef on openSUSE Leap


    
        
            $
        

        
            
                sudo zypper refresh
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo zypper install
            
                        
                texlive-filecontentsdef
            
                    
    
    Copied

2. Uninstall "texlive-filecontentsdef" package

In this section, we are going to explain the necessary steps to uninstall texlive-filecontentsdef on openSUSE Leap:


    
        
            $
        

        
            
                sudo zypper remove
            
                        
                texlive-filecontentsdef
            
                    
    
    Copied

3. Information about the texlive-filecontentsdef package on openSUSE Leap

Information for package texlive-filecontentsdef:
------------------------------------------------
Repository : Main Repository
Name : texlive-filecontentsdef
Version : 2021.189.1.5svn52208-150400.18.1
Arch : noarch
Vendor : SUSE LLC
Installed Size : 6.8 KiB
Installed : No
Status : not installed
Source package : texlive-specs-i-2021-150400.18.1.src
Upstream URL : http://www.tug.org/texlive/
Summary : Filecontents + macro + verbatim
Description :
The package provides two environments called filecontentsdef
and filecontentshere. They are derived from the LaTeX
filecontents environment as provided by Scott Pakin's
filecontents package. In addition to the file creation they
either store the (verbatim) contents in a macro
(filecontentsdef) or typeset them (verbatim) on the spot
(filecontentshere). The author developed the package to display
TeX code verbatim in documentation and the same time produce
the corresponding files during the LaTeX run in order to embed
them in the PDF as file attachment annotations (by using Scott
Pakin's package attachfile).