Slackware -current ISO's 5.3 gigs?
I was wanting to install slackware current on my box at home and found that the ISO's on http://taper.alienbase.nl/mirrors/slackware/ are 5.3g in size. I am curious why they are so huge.
|
Here is a June 12th ISO without the source's, 2.6GB
http://ftp.df.lth.se/pub/slackware/s...e-current-iso/ |
I think the prudent thing for the next release would be to put all the source on a completely separate DVD iso. That way we can perhaps get LibreOffice and a few other goodies included without killing bandwidth. I know the inclusion of the source is a) for GPL, and b) for fiddlers, but having the iso still available for download solves both. I personally only used the sources a few times for edge cases. Even then it might have been easier just to download
those few packages directly from the web site. |
Member Response
Hi,
Quote:
Quote:
Quote:
HTH! EDIT: Slackware '-current links above are now valid, error due to system regen' |
Gary, Unless I'm misreading it, those two links you've included in the quote above under 'trimmed' both appear to be > 5GB, so I suspect they're the full versions.
|
Member Response
Hi,
Quote:
|
Member Response
Hi,
One other thought would be to create a 'mirror-slackware-current.conf' file by: ./mirror-slackware-current.sh -w then edit the 'mirror-slackware-current.conf' file to; Quote:
EDIT: Or include all info in 'mirror-slackware-current.conf' |
The GPL never has actually stated that a release of a product using GPL code has to have the source code available on the same media. It just has to be available to the public or in the same "package". I agree moving it to a separate ISO might be a good idea to save space. Besides Pat could always include the Slackware Source DVD within the webstore bundle.
|
Alternatively, if one prefers to keep sources and pasture, one can "rm -rf slackware64/kdei source/kdei". English-speakers don't need it, KDE runs just fine without it, and it will save you a little over half a gigabyte in the iso.
|
Member Response
Hi,
Quote:
Quote:
|
Quote:
The GPL simply requires that anyone to whom a GPL'd executable or linkable is distributed, must also have access to the source code. It does not require that the source code accompany the binary files on the same medium, or even with the same media. Distributing binaries on DVD and making the source available online, for instance, is fully GPL-compliant. -- TTK |
As long as the "source" is freely accessible by any means, it's GPL compliant. The only reason I stated putting the Source on a separate DVD was to have an archived static copy.
Slackware could even host a CVS or SVN of the source and it'd still be GPL compliant. |
ttk and ReaperX7 are correct. Many (most?) distros have separate source CDs/DVDs or just host the source on a web or ftp site rather than trying to combine everything on a single CD/DVD. Slackware is actually quite unusual these days in offering both on the same physical media.
Have a look at what some other popular distros offer: Debian FAQ entry on source CDs Download link for Fedora-17 source only DVD (you won't find any source on the regular CD/DVD images) openSUSE page on how to obtain the source P.S. Personally I like having the source so that I can tweak or update the SlackBuilds, so I would probably still download any source CD/DVD. If it was offered bundled as an extra disk with the official binary CD/DVDs when buying from the Slackware store, than so much the better. ;) |
Arch Linux has a single command to fetch or update all of PKGBUILD files (source build scripts equivalent to SlackBuild files) for the distro, you just type 'abs' as root. It just uses svn underneath to sync the latest version of the source and place it in /var/abs/.
Perhaps Slackware could provide something similar? Now sure most of us could do something equivalent using a rsync capable mirror but it might be nice if there was a short single command like this and the script that did it for you (and verified everything with signatures) and that this command was included with the base distro. Granted this would be more useful for users of -current but even for users of the regular distro, the SlackBuilds for patches do change. |
Actually, perhaps the functionality for fetching the official SlackBuilds (and associated files) and placing them in an appropriate directory (e.g. somewhere in /var) could be added to slackpkg?
P.S. I dropped Piter PUNK (Roberto F. Batista) an email to see if it is something he might be interested in. ;) Edit: My mail bounced back, apparently his mailbox is full. :( |
All times are GMT -5. The time now is 11:53 PM. |