LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   Slackware -current ISO's 5.3 gigs? (https://www.linuxquestions.org/questions/slackware-14/slackware-current-iso%27s-5-3-gigs-4175411983/)

tmfizzle 06-17-2012 10:49 PM

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.

SqdnGuns 06-17-2012 11:54 PM

Here is a June 12th ISO without the source's, 2.6GB

http://ftp.df.lth.se/pub/slackware/s...e-current-iso/

Mark Pettit 06-18-2012 01:04 AM

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.

onebuck 06-18-2012 07:40 AM

Member Response
 
Hi,
Quote:

Originally Posted by Mark Pettit (Post 4705826)
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.

From gpl-violations.org Source Code Release FAQ;
Quote:

What kind of source code do I have to publish under the GNU GPL? The GNU GPL demands that as soon as you distribute GPL licensed software in executable format you make available the "complete corresponding source code". The GNU GPL also contains a definition of this term:
“ The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable. ” This is a quite precise definition. For a typical C program, this translates into all the source code (.c files) plus header files (.h files) plus the scripts used to control compilation and installation.
Always keep in mind that it is the purpose of the GPL to enable the users to exercise his freedoms. Specifically, the freedom to make modified versions of the program, and to run such modified versions of the program.
Convenient to package source with the distribution. Not required to distribute but make available.
Quote:

Slackware-Current Trimmed
The ISO below are <2GB + 'ISO images are automatically re-generated within a day if there is an update to the ChangeLog.txt' + These ISOs are created using Alien_Bob's script 'mirror-slackware-current.sh' + Source is not provided on the ISO images below
Slackware-current DVD ISO image <- 'x86' for 32bit
Slackware64-current DVD ISO image <- 'x86_64' for 64bit
So if you need to use '-current' without source then the ISO is available by choosing one of the above for your arch. Alien_Bob has provided this service and legally. You can get the source from any Slackware mirror so the source is made available to the user.
HTH!

EDIT: Slackware '-current links above are now valid, error due to system regen'

GazL 06-18-2012 08:09 AM

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.

onebuck 06-18-2012 09:23 AM

Member Response
 
Hi,

Quote:

Originally Posted by GazL (Post 4706064)
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.

I know. A note to Alien_Bob about the minimum ISO for '-current' ISO has been sent. The original links are no longer valid. Hopefully I can get the corrected links.

onebuck 06-18-2012 09:42 AM

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:

# The value of EXCLUDES is what the script will exclude from the mirroring
# process; there is no parameter for the script to change this value, but you
# can use '-X excludefile' to define more excluded directories/files if you
# wish. Or directly edit the line below of course:
EXCLUDES="--exclude pasture source"
#EXCLUDES="--exclude source"
Of course you would still need to provide your local information within 'mirror-slackware-current.sh'.
EDIT: Or include all info in 'mirror-slackware-current.conf'

ReaperX7 06-18-2012 04:19 PM

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.

ttk 06-18-2012 06:26 PM

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.

onebuck 06-18-2012 06:37 PM

Member Response
 
Hi,

Quote:

Originally Posted by ReaperX7 (Post 4706413)
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.

Not really!
Quote:

From http://gpl-violations.org/faq/sourcecode-faq.html

Please also keep in mind that both distribution on physical storage medium and distribution via data networks such as the Internet count as distribution.

ttk 06-18-2012 07:10 PM

Quote:

Originally Posted by onebuck (Post 4706476)
Not really!

Yes, really. The bit you quoted only states what qualifies as distribution, and does not prescribe the manner by which source must be made available.

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

ReaperX7 06-18-2012 08:53 PM

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.

ruario 06-19-2012 02:49 AM

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. ;)

ruario 06-19-2012 03:04 AM

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.

ruario 06-19-2012 03:14 AM

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.