[2024-feb-29] Sad news: Eric Layton aka Nocturnal Slacker aka vtel57 passed away on Feb 26th, shortly after hospitalization. He was one of our Wiki's most prominent admins. He will be missed.

Welcome to the Slackware Documentation Project

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
slackbook:package_management [2012/09/17 03:08 (UTC)] – [slackpkg] Added original text and formatting mfillpotslackbook:package_management [2012/09/17 03:12 (UTC)] (current) – [Sources] updated the author list mfillpot
Line 223: Line 223:
 ==== rpm2tgz ==== ==== rpm2tgz ====
  
-One of the most ubiquitous package formats for Linux software is RPM; it's not uncommon to find a developer offering their application for download as either source code or an RPM file, and no more. In this case, you would have three options:+One of the most ubiquitous package formats for Linux software is 
 +RPM; it's not uncommon to find a developer offering their 
 +application for download as either source code or an RPM file, and 
 +no more. In this case, you would have three options:
  
   - Build your own Slackware package.   - Build your own Slackware package.
Line 229: Line 232:
   - Convert and install from RPM.   - Convert and install from RPM.
  
-Building from source code or creating your own Slackware package is usually not as complex as you might think but installing directly from source code is generally discouraged because there is no easy way to track what has been installed on your system after issuing the **make install** command. Building your own Slackware packages is outside the scope of this chapter. So this leaves us with the helpful tool rpm2tgz.+Building from source code or creating your own Slackware package is 
 +usually not as complex as you might think but installing directly from 
 +source code is generally discouraged because there is no easy way to 
 +track what has been installed on your system after issuing the 
 +''make install'' command. Building your own Slackware 
 +packages is outside the scope of this chapter. So this leaves us with 
 +the helpful tool **//rpm2tgz//**. 
 + 
 +**//rpm2tgz//** converts RPM packages into a 
 +Slackware package that can then be installed via 
 +**//pkgtool//** or 
 +**//installpkg//**. This circumvents the need to 
 +create your own Slackware package but grants you the benefit of 
 +being able to remove, update, and track what you've installed.
  
-rpm2tgz converts RPM packages into a Slackware package that can then be installed via pkgtool or installpkg. This circumvents the need to create your own Slackware package but grants you the benefit of being able to remove, update, and track what you've installed. 
  
 <note warning> <note warning>
-While a Slackware package is just a shell script and source code, an RPM package can by comparison be a maze of dependency listings and special instructions. Therefore, rpm2tgz will not always work, especially on very complex applications, and it will never magically resolve dependencies.+ 
 +While a Slackware package is just a shell script and source code, 
 +an RPM package can by comparison be a maze of dependency listings 
 +and special instructions. Therefore, 
 +**//rpm2tgz//** will not always work, 
 +especially on very complex applications, and it will never 
 +magically resolve dependencies. 
 </note> </note>
  
-To try rpm2tgz, download an RPM file from a trusted source and convert it:+To try **//rpm2tgz//**, download an RPM file from 
 +a trusted source and convert it: 
  
 <code> <code>
-  rpm2tgz foo-x.x.xx.rpm+ 
 +rpm2tgz foo-x.x.xx.rpm
 </code> </code>
  
-The result is a .tgz file, so after the conversion is finished, the original RPM can safely be discarded. Use installpkg to install the Slackware package you've just created, provided that you've installed all dependency code for the application to actually function. 
  
 +The result is a .tgz file, so after the conversion is finished, the
 +original RPM can safely be discarded. Use
 +**//installpkg//** to install the Slackware
 +package you've just created, provided that you've
 +installed all dependency code for the application to actually function.
 ====== Chapter Navigation ====== ====== Chapter Navigation ======
  
Line 253: Line 282:
 ====== Sources ====== ====== Sources ======
 <!-- If you copy information from another source, then specify that source --> <!-- If you copy information from another source, then specify that source -->
-  * Original source: [[http://www.slackbook.org/beta]]  \\+  * Original source: [[http://www.slackbook.org/beta]] \\
 <!-- Authors are allowed to give credit to themselves! --> <!-- Authors are allowed to give credit to themselves! -->
-  * Originally written by Alan Hicks +  * Originally written by Alan Hicks, Chris Lumens, David Cantrell, Logan Johnson
 <!-- * Contrbutions by [[wiki:user:yyy | User Y]] --> <!-- * Contrbutions by [[wiki:user:yyy | User Y]] -->
  
 slackbook:package_management ()