[SOLVED] Chances of getting sued-fined for editing slackbuilds?

Holering · 02-07-2014, 01:42 PM

Noticed in v4l-utils.SlackBuild, there is no indication of the right to modify the SlackBuild in any way. It only says it's ok to redistribute it, but no indication of anything beyond.

So what are the chances of getting sued-fined if someone wishes to change things in Slackware's official SlackBuilds? What if someone hosts modified SlackBuilds, or SlackBuilds derived from the originals (with Patrick, Eric or others still in the credits)?

Regards

dugan · 02-07-2014, 01:45 PM

I don't think SlackBuilds.org would accept a script whose license didn't allow modification. Code that cannot be modified is not open source.

genss · 02-07-2014, 01:48 PM

# Copyright 2009 Eric Hameleers, Eindhoven, NL
# Copyright 2009, 2010, 2011, 2013 Patrick J. Volkerding, Sebeka, MN, USA
# All rights reserved.

# Redistribution and use of this script, with or without modification, is
# permitted provided that the following conditions are met:
#
# 1. Redistributions of this script must retain the above copyright
# notice, this list of conditions and the following disclaimer.
#
# some_other_text

what do you mean there is no indication ?
"...with or without modification,..."

Didier Spaier · 02-07-2014, 01:57 PM

Quote:

Originally Posted by Holering

Noticed in v4l-utils.SlackBuild, there is no indication of the right to modify the SlackBuild in any way.

Yes there is:

Code:

[...]
# Redistribution and use of this script, with or without modification, is
# permitted provided that the following conditions are met:
[...]

I think it's good practice, if one distribute it with modification to state it somewhere, so that user finding a bug can address a support request to the good person.

EDIT Slow typer...

Holering · 02-07-2014, 02:01 PM

Yeah you're right... Wonder if Patrick accepts slackbuild updates from anyone; some slackbuilds are very outdated like dev86. What if a fork of the slackware-current slackbuilds tree existed?

ReaperX7 · 02-07-2014, 02:41 PM

A SlackBuild is simply a script used to build and install packages. Example: if GCC vanished tomorrow and all we were left with was LLVM/Clang, the SlackBuild would have to be modified to switch the compiler and add any needed patches. If it wasn't able to be modified, we'd be screwed.

Plain and simple, outside the source or binary shareware package, a SlackBuild is completely separate and free open source.

Some of my scripts I've posted over in the LFS section are open source licensed. I don't care what you do to them, just acknowledge the original source and author.

55020 · 02-07-2014, 03:23 PM

Quote:

Originally Posted by Holering

Wonder if Patrick accepts slackbuild updates from anyone; some slackbuilds are very outdated like dev86.

To the extent that those updates are useful, yes. Let's just say that dev86 gets all the attention it requires.

Quote:

Originally Posted by Holering

What if a fork of the slackware-current slackbuilds tree existed?

The Slackware-derived distributions are legally and technically pretty much in that situation already. It all adds to the world's majesty. It's fine.

You should understand how Slackware got started. AIUI, Patrick was producing fixed-up versions of SLS, and trying to feed the fixes back upstream. Instead, upstream chose to be un-cooperative. The laid-back give-and-take of the Slackware project is the obvious consequence. Patrick is not suddenly going to get heavy with terms and conditions, unless some total knobhead comes along and completely takes the piss in an unforeseen and innovative way.