[Slapt-get-user] updated FAQ

Jason Woodward woodwardj at jaos.org
Mon Jan 10 18:11:16 EST 2005


I updated the FAQ (http://software.jaos.org/BUILD/slapt-get/FAQ.html) to reflect more of how
things are as well as take out some of the non-productive wording =].

The most significant update by far is the FAQ concerning dependencies:
http://software.jaos.org/BUILD/slapt-get/FAQ.html#slgFAQ10

10.  What about package dependencies?

 First of all, slapt-get does not provide dependency resolution for vanilla
 Slackware packages.

 However, slapt-get does provide a framework for dependency resolution for
 packages that follow the Slackware package format, while still being backwards
 compatible.  This information is stored in so called meta files within the
 package.  slapt-get does not parse packages themselves.  It uses the 
 PACKAGES.TXT package database that Patrick Volkerding provides along with his
 packages.  slapt-get uses this file by extending it with optional extra fields.
 This information is stored within the package simply as a means of easy
 transport.  For example, the entry for man within PACKAGES.TXT looks like:

   PACKAGE NAME:  man-1.5l-i386-1.tgz
   PACKAGE LOCATION:  ./slackware/ap
   PACKAGE SIZE (compressed):  166 K
   PACKAGE SIZE (uncompressed):  390 K
   PACKAGE DESCRIPTION:
   man: man (format and display the on-line manual pages)

 It is extended like so:

   PACKAGE NAME:  man-1.5l-i386-1.tgz
   PACKAGE LOCATION:  ./slackware/ap
   PACKAGE SIZE (compressed):  166 K
   PACKAGE SIZE (uncompressed):  390 K
   PACKAGE REQUIRES: groff >= 1.56-noarch-1,man-pages | man-pages-de
   PACKAGE CONFLICTS:  
   PACKAGE SUGGESTS:  
   PACKAGE DESCRIPTION:
   man: man (format and display the on-line manual pages)

 The REQUIRES line is an addition supported by slapt-get, along with CONFLICTS
 and SUGGESTS.  The meta files supporting dependencies, conflicts, and
 suggestions are within the packages inside the ./install/ directory.  The
 REQUIRES information is stored in the slack-required file.  The CONFLICTS
 information is stored within the slack-conflicts file.  The SUGGESTS
 information is stored in the slack-suggests file.  See FAQ #19 for a breakdown
 of the structure of REQUIRES, FAQ #31 for CONFLICTS, and FAQ #44 for SUGGESTS.

 This information is added to the PACKAGES.TXT file by extracting it from the
 meta files within the package.  This is normally done by the provider of the
 packages when they generate the PACKAGES.TXT support file for their package
 source.  See FAQ #17 for an example script to generate an extended PACKAGES.TXT
 file.

 The inclusion of this information within the Slackware package format does not
 inhibit the ability for Slackware pkgtools to install these packages.  This
 information is silently ignored and discarded after the package is installed.

 Packages supporting this framework can be found at linuxpackages.net, along
 with several Slackware derived distributions such as CollegeLinux (starting
 with 2.5) and VectorLinux (starting with 5.0).




take care,
jason

--
Jason Woodward
woodwardj at jaos.org

-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
 
mQGiBDrwHPoRBAC3nDJRLKTcFcJWid9PN08ChMI7tuQevomWoVeZpZZ0zzip2w/E
ts55Mx58eRRGFFmgZZGeP7EhyUPzb668LIsU62gFO7G5/oWCr3U3g3peabZsqRC9
FchdiM8DJqQu/7ryAjbQ4OFCSW+jAsMC3tKXrdaB48WiipiXUcKR/sONGwCgzGPf
yxDgOc7n9xWVH0qbUDC/vZsEAKvbckkhpe9/x2A4E15l6DUbliEmboeHiT9NJaok
vLo3ElSO1o6ld5+VhFIkhRmmovrS8oyttZNv8HjMEYf6L3NdZybTHfcdS5EIpguH
Xx2/IGzJKbgX3vM/qhJ0+F1LPuN20mOT0NO/29AXJn3V7rTKoKf/uOOKD+Eqh4r1
QVMoBAC3ZPF3idmuW3j4tqhOaWe2qHlLwEClwdsTG+KOsVYh1sU4RvyMErDIU6r/
MomkLAJfbtBTXKcknW68Y4Uv4B+UkyopklktRBFiMBffoHLUfkkQk/L9Yg1YG27N
COsECiamylF8hNSTcNIQqYXDpyoRcSi2p7gqkxJZrk7GwrX2ObQjSmFzb24gV29v
ZHdhcmQgPHdvb2R3YXJkakBqYW9zLm9yZz6IVwQTEQIAFwUCOvAc+gULBwoDBAMV
AwIDFgIBAheAAAoJEGu22odUp/oeN2IAoKHS+qH8AenlOTKL0Ifl3q1QSlDBAKDL
bvvgl7HoRTHY2b9n3pEPr+KIh7kBDQQ68Bz9EAQA2Ds/2VKc08qaNIkA1okxITmQ
aaNjUrm/au9jNzm9lyEFXWXBNegzP5Y4A1ESDKUt5RETgVhNKd9mGkP7tgPTs3f6
Z595K6W7xeZWONKbl578RbWwE1CiMqEOuXwr1/q0DzfwmNQLcqDcX3o0DEpWE+uZ
G+5CtpkXYiDmccigDKMAAwUD/iZDxEr1HC4iLnGXUCDpxXEtp7Fx150baFzZITns
4hpKRAbTR65s2tL8rh5d8ThDgqW5C9JQja9fMxI2u7zlyM2ALFXJP1xwgZTSOYvn
sq+x41i5tJpce+pDmMEl8X0wew2Z5ZRPfDLv64kKPIGNgVXsAHirH2KjChZat4VC
qkZciEYEGBECAAYFAjrwHP0ACgkQa7bah1Sn+h7qkQCePz0ds5O/dsZrm450pjLs
2V3BkMAAn2/6alBBC9b9F94svdOf0mGY/G5w
=4p8c
-----END PGP PUBLIC KEY BLOCK-----

my($c, at s)=(0,qw( | / - \ ));$|++;my$p;&{sub{map{$p.=chr$_}
unpack(join('a',('',split(//,$_->[1]))),$_->[0]);}}foreach
[qw/74117115116 2333/],[qw/65110111116104101114 2333333/],
[qw/80101114108 2333/],[qw/729799107101114 222333/];{my$z=
$c<4?$s[$c++]:$s [$c=0];printf"\ec%s%s%s",$z,$p,$z,select*
STDOUT,*STDOUT,*STDOUT,0.1,;redo;}##########JAPH##########



More information about the Slapt-get-user mailing list