mirror of
git://slackware.nl/current.git
synced 2024-12-27 09:59:16 +01:00
e100944d49
Hey folks, my first order of business here needs to be a huge thank you to everyone who has donated at https://paypal.me/volkerdi to help keep this project going. As most of you are already aware by now, the financal situation here at Slackware HQ has not been great for many years, including not getting any pay for the last two years and forcing me (and my family) to live very frugally while I continued to work on the project hoping I'd figure out a way to actually monitize it by the time that Slackware 15.0 is ready for release. I'm not trying to cast any blame regarding the situation. Really, I can only blame myself for not trying to build my own ship years ago when things began to not really work out. I'm still looking into sustainable funding options such as Patreon or Liberapay (or perhaps both), and I'm open to other ideas. I'm no longer in immediate danger of going broke, and I'm no longer entertaining the notion of joining my friends at the local potato chip factory in order to pay my bills. :) My family is grateful and humbled by the support we've received. Hope we'll be able to keep this project going for a long time. Also, I realize that the website lacks updates and needs attention and I will need to find some time to devote to that. I've never been much of a website designer, and the slackware.com site is basically left over from work done by former Walnut Creek / BSDi employees. I've never seen able to make much sense of the SQL backend. The interface to edit and post articles is clunky (and I'm not sure the PHP for that even works any more). When I've posted articles in recent years, I've done so by editing the main page already processed from PHP into HTML, which is pretty darn messy as I'm sure you can imagine. I tend to prioritize the distribution itself over other demands on my time - that's clearly a lot to do with how things ended up the way they did. So, I guess that's the report for now. Lots more work to do and not enough time to do it in... that part I don't see changing moving forward. :) Thanks very much again. I'll do my best to keep you all posted. - Pat a/file-5.34-x86_64-1.txz: Upgraded. a/kernel-firmware-20180727_b01151b-noarch-1.txz: Upgraded. a/kernel-generic-4.14.58-x86_64-1.txz: Upgraded. a/kernel-huge-4.14.58-x86_64-1.txz: Upgraded. a/kernel-modules-4.14.58-x86_64-1.txz: Upgraded. d/gcc-8.2.0-x86_64-1.txz: Upgraded. d/gcc-brig-8.2.0-x86_64-1.txz: Upgraded. d/gcc-g++-8.2.0-x86_64-1.txz: Upgraded. d/gcc-gfortran-8.2.0-x86_64-1.txz: Upgraded. d/gcc-gnat-8.2.0-x86_64-1.txz: Upgraded. d/gcc-go-8.2.0-x86_64-1.txz: Upgraded. d/gcc-objc-8.2.0-x86_64-1.txz: Upgraded. d/kernel-headers-4.14.58-x86-1.txz: Upgraded. d/libtool-2.4.6-x86_64-9.txz: Rebuilt. Recompiled to update embedded GCC version number. k/kernel-source-4.14.58-noarch-1.txz: Upgraded. CRASH_DUMP n -> y KEXEC n -> y +KEXEC_JUMP y +PROC_VMCORE y l/babl-0.1.54-x86_64-1.txz: Upgraded. l/gegl-0.4.6-x86_64-1.txz: Upgraded. l/libart_lgpl-2.3.21-x86_64-2.txz: Removed. This actually hasn't been needed by any Slackware package since koffice in KDE3, and this particular version won't work with the Trinity Desktop Environment, which is essentially a fork of KDE 3.5 updated to compile and run with modern libraries and development tools. I can't see much point in keeping it around. Thanks to _gin. n/NetworkManager-1.12.2-x86_64-1.txz: Upgraded. n/dhcpcd-7.0.7-x86_64-1.txz: Upgraded. x/libinput-1.11.3-x86_64-1.txz: Upgraded. extra/tigervnc/tigervnc-1.9.0-x86_64-1.txz: Upgraded. isolinux/initrd.img: Rebuilt. kernels/*: Upgraded. usb-and-pxe-installers/usbboot.img: Rebuilt. |
||
|---|---|---|
| .. | ||
| a | ||
| ap | ||
| d | ||
| e | ||
| f | ||
| installer | ||
| k | ||
| kde | ||
| kdei | ||
| l | ||
| n | ||
| t | ||
| tcl | ||
| x | ||
| xap | ||
| xfce | ||
| y | ||
| buildlist-from-changelog.sh | ||
| make_world.sh | ||
| README.TXT | ||
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: fuzzy:~# grep bin/cp /var/log/packages/* /var/log/packages/cpio-2.4.2.91-i386-1:bin/cpio /var/log/packages/fileutils-4.1-i386-2:bin/cp /var/log/packages/gcc-2.95.3-i386-2:usr/bin/cpp /var/log/packages/gnome-applets-1.4.0.5-i386-1:usr/bin/cpumemusage_applet From this, you can see that 'cp' came from the fileutils-4.1-i386-2 package. The source will be found in a corresponding subdirectory. In this case, that would be ./a/bin. Don't be fooled into thinking that the _bin.tar.gz in this directory is the package with the source code -- anything starting with '_' is just a framework package full of empty files with the correct permissions and ownerships for the completed package to use. Many of these packages now have scripts that untar, patch, and compile the source automatically. These are the 'SlackBuild' scripts. Moving back to the example above, you can figure out which package the bin/cp source came from by examining the SlackBuild script. Have fun! --- Patrick J. Volkerding volkerdi@slackware.com