Index of /slackware/slackware64-current/source

[ICO]NameLast modifiedSizeDescription
[PARENTDIR]Parent Directory  -  
[ ]CHECKSUMS.md5.asc2024-11-21 00:10 195  
[ ]CHECKSUMS.md52024-11-21 00:10 611K 
[ ]FILE_LIST2024-11-21 00:10 856K 
[ ]MANIFEST.bz22024-11-21 00:10 29M 
[DIR]n/2024-11-18 21:25 -  
[DIR]a/2024-11-17 21:16 -  
[DIR]k/2024-11-17 19:55 -  
[DIR]l/2024-11-10 19:34 -  
[DIR]ap/2024-10-23 03:14 -  
[DIR]xap/2024-10-21 21:33 -  
[DIR]d/2024-10-19 22:07 -  
[DIR]x/2024-09-28 21:21 -  
[DIR]installer/2024-09-18 21:36 -  
[DIR]tcl/2024-09-18 02:04 -  
[DIR]e/2024-04-23 21:54 -  
[DIR]t/2024-04-09 20:15 -  
[DIR]kde/2024-01-09 22:32 -  
[ ]make_world.sh2022-06-07 06:16 14K 
[TXT]README.TXT2022-02-02 06:43 828  
[DIR]xfce/2022-01-06 22:35 -  
[ ]buildlist-from-changelog.sh2021-10-08 04:36 12K 
[DIR]y/2020-12-30 23:23 -  
[DIR]f/2018-02-27 08:13 -  

This is the source used for Slackware.

To look for a particular bit of source (let's say for 'cp'), first you would
look for the full path:

fuzzy:~# which cp
/bin/cp

Then, you grep for the package it came from. Note that the leading '/'
is removed, and ^ and $ mark the beginning and end of the pattern to match:

fuzzy:~# grep ^bin/cp$ /var/lib/pkgtools/packages/*
/var/lib/pkgtools/packages/coreutils-9.0-x86_64-3:bin/cp

From this, you can see that 'cp' came from the coreutils-9.0-x86_64-3 package.
The source will be found in a corresponding subdirectory. In this case, that
would be ./a/coreutils/.

All of these packages have scripts that extract, patch, and compile the source
automatically. These are the 'SlackBuild' scripts.

Have fun!

---
Patrick J. Volkerding
volkerdi@slackware.com