LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 06-06-2015, 11:33 AM   #76
a4z
Senior Member
 
Registered: Feb 2009
Posts: 1,727

Rep: Reputation: 742Reputation: 742Reputation: 742Reputation: 742Reputation: 742Reputation: 742Reputation: 742

Quote:
Originally Posted by ivandi View Post
The dumbest copyright claim can be found in the header of thousands of scripts at SBO or Slackware.

A few posts ago I said that I see no point to maintain this stuff along with Slackware (keeping up with the ChangeLog and so on). That didn't mean that I would stop playing with it. I redirected the url above to point to the PAM folder of my home setup that I shared in another thread.

I removed the scripts because I refuse to play your silly copyright games.

And yes, its a pity to call someone "full of spite" just because you aren't agree with him.


Cheers
you start to become childish, very sad.

if your write your own script, take whatever license you want.
if you use others and improve/change it, keep the license and add a note.
you can also invent your own style of build scripts with whatever license if you want
it is really not that hard and you have a lot of options, no need to stress this topic that much
 
Old 06-06-2015, 11:47 AM   #77
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-15.0
Posts: 11,048

Rep: Reputation: Disabled
Quote:
Originally Posted by a4z View Post
no need to stress this topic that much
Ivandi is the OP and is not the one who does. Not to repeat myself.
 
Old 06-06-2015, 07:31 PM   #78
ReaperX7
LQ Guru
 
Registered: Jul 2011
Location: California
Distribution: Slackware64-15.0 Multilib
Posts: 6,554
Blog Entries: 15

Rep: Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097
We honor the license by honoring the contribution. We honor the contribution by honoring the license.

When you contribute, and you license your stuff, the community will honor it. There are no thieves in Slackware. We are Slackware for we are its community, and the community honors itself by honoring all licenses of each controbution.
 
Old 06-06-2015, 08:26 PM   #79
ivandi
Member
 
Registered: Jul 2009
Location: Québec, Canada
Distribution: CRUX, Debian
Posts: 528

Original Poster
Rep: Reputation: 866Reputation: 866Reputation: 866Reputation: 866Reputation: 866Reputation: 866Reputation: 866
Please, tell me what exactly is unique in this script. What exactly you think is your IP and has to be copyrighted. According to the year there were already several thousands similar scripts out there. What someone will eventually steal from you. How will you prove that you are the author of this script.

Code:
#!/bin/sh
# Slackware build script for libclc

# Copyright 2015 James Powell james4591@hotmail.com Tulare, CA, 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.
#
#  THIS SOFTWARE IS PROVIDED BY THE AUTHOR "AS IS" AND ANY EXPRESS OR IMPLIED
#  WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
#  MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.  IN NO
#  EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
#  SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
#  PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
#  OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
#  WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
#  OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
#  ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

PRGNAM=libclc
VERSION=${VERSION:-20150524-svn}
BUILD=${BUILD:-1}
TAG=${TAG:-_SBo}

if [ -z "$ARCH" ]; then
  case "$( uname -m )" in
    i?86) export ARCH=i486 ;;
    arm*) export ARCH=arm ;;
       *) export ARCH=$( uname -m ) ;;
  esac
fi

CWD=$(pwd)
TMP=${TMP:-/tmp/SBo}
PKG=$TMP/package-$PRGNAM
OUTPUT=${OUTPUT:-/tmp}

if [ "$ARCH" = "i486" ]; then
  LIBDIRSUFFIX=""
elif [ "$ARCH" = "i686" ]; then
  LIBDIRSUFFIX=""
elif [ "$ARCH" = "x86_64" ]; then
  LIBDIRSUFFIX="64"
else
  LIBDIRSUFFIX=""
fi

set -e

rm -rf $PKG
mkdir -p $TMP $PKG $OUTPUT
cd $TMP
rm -rf $PRGNAM-$VERSION
tar xvf $CWD/$PRGNAM-$VERSION.tar.gz
cd $PRGNAM-$VERSION
chown -R root:root .
find -L . \
 \( -perm 777 -o -perm 775 -o -perm 750 -o -perm 711 -o -perm 555 \
  -o -perm 511 \) -exec chmod 755 {} \; -o \
 \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \
  -o -perm 440 -o -perm 400 \) -exec chmod 644 {} \;

./configure.py \
  --prefix=/usr \
  --libexecdir=/usr/lib${LIBDIRSUFFIX}

make -j3 
make install DESTDIR=$PKG

find $PKG -print0 | xargs -0 file | grep -e "executable" -e "shared object" \
  | grep ELF | cut -f 1 -d : | xargs strip --strip-unneeded 2> /dev/null || true

mkdir -p $PKG/usr/doc/$PRGNAM-$VERSION
cp -a \
  *.TXT \
  $PKG/usr/doc/$PRGNAM-$VERSION
cat $CWD/$PRGNAM.SlackBuild > $PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild

# Copy the slack-desc (and a custom doinst.sh if necessary) into ./install
mkdir -p $PKG/install
cat $CWD/slack-desc > $PKG/install/slack-desc
[ -f $CWD/doinst.sh ] && cat $CWD/doinst.sh > $PKG/install/doinst.sh

cd $PKG
/sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$VERSION-$ARCH-$BUILD$TAG.${PKGTYPE:-tgz}
Cheers
 
4 members found this post helpful.
Old 06-06-2015, 09:40 PM   #80
ReaperX7
LQ Guru
 
Registered: Jul 2011
Location: California
Distribution: Slackware64-15.0 Multilib
Posts: 6,554
Blog Entries: 15

Rep: Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097
The whole damn thing, because I edited the public template and wrote the whole damn build and packaging instructions after testing it myself, retesting it after several instructions didn't work as intended, and reedited it again several times before it worked correctly. I don't need to imply anything. If someone steals my work, they will be found out eventually.

Plus, the Slackware community does not steal from each other. Why do you think SBo exists on a git server? Why does my work exist on a git server? My works even has a license on the frontpage that says:

Quote:
Originally Posted by https://bitbucket.org/ReaperX7/slackworks/raw/f52304ddb1fcb7cadec8a9294bd0f40e05793d1d/LICENSE
Copyright (c) 2015, James Powell <james [at] hotmail [dot] com>

Permission to use, copy, modify, and/or distribute this software for any
purpose with or without fee is hereby granted, provided that the above
copyright notice and this permission notice appear in all copies.

THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
If you find another libclc package, please by all means find the author, have him contact me, and maybe we can share notes on what you find is wrong with two separate packages with comparable work.

It's under a BSD/MIT license so anyone can take and edit it as needed as long as they show the original work effort done by your highlighting.

Just because you don't observe copyright law doesn't mean I have to do the same. I observe it because I edit my scripts up as needed on my PUBLIC repository for public usage and redistribution.

Are you that blatantly disrespectful to copyright law, or are you just that ignorant?

Plus there's one other reason if you were so thoughtless to notice...

Code:
#  THIS SOFTWARE IS PROVIDED BY THE AUTHOR "AS IS" AND ANY EXPRESS OR IMPLIED
#  WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
#  MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.  IN NO
#  EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
#  SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
#  PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
#  OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
#  WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
#  OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
#  ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Guess what this license says... I redistributed the software and I can not be held liable for what it does.

If you do NOT include this in your license specifically, guess what... if you f--k up someone's computer from your package, and you do not include this license agreement, you CAN be held liable.

Also, why don't you read this:

http://opensource.org/licenses

This might give you a better understanding of why the OSI compliant licenses exist and why such works conceived, derived, etc. of open source natures require licenses. This might also be an eye opener:

http://www.law360.com/articles/54445...y-is-expanding

and this:

http://en.wikipedia.org/wiki/Disclaimer

Last edited by ReaperX7; 06-06-2015 at 10:11 PM.
 
Old 06-06-2015, 10:26 PM   #81
ReaperX7
LQ Guru
 
Registered: Jul 2011
Location: California
Distribution: Slackware64-15.0 Multilib
Posts: 6,554
Blog Entries: 15

Rep: Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097
And if you really want to complain about a script, complain about who owns this one:

Code:
#!/bin/sh

# Copyright 2006, 2008, 2009, 2010, 2011, 2012, 2013  Patrick J. Volkerding, Sebeka, MN, USA
# Copyright 2014 Didier Spaier Paris, France
# Copyright 2015 James Powell Tulare, CA, USA
# All rights reserved.
# Adapted to build a package for eudev-1.6 by Didier Spaier 2014, from 
# udev.SlackBuild included in Slackware64-14.1 that builds a package for
# udev-182 build 7.
# Readapted to build package for eudev-3.1 by James Powell 2105.
#
# 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.
#
#  THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR IMPLIED
#  WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
#  MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.  IN NO
#  EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
#  SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
#  PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
#  OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
#  WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
#  OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
#  ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
# 
# 

VERSION=${VERSION:-3.1}
BUILD=${BUILD:-1}

# Be kind with low specs building boxes, anyway building this package
# doesn't take long - Didier
NUMJOBS=${NUMJOBS:-" -j3 "}

# Automatically determine the architecture we're building on:
if [ -z "$ARCH" ]; then
  case "$( uname -m )" in
    i?86) export ARCH=i486 ;;
    arm*) export ARCH=arm ;;
    # Unless $ARCH is already set, use uname -m for all other archs:
       *) export ARCH=$( uname -m ) ;;
  esac
fi

if [ "$ARCH" = "x86_64" ]; then
  LIBDIRSUFFIX="64"
else
  LIBDIRSUFFIX=""
fi

CWD=$(pwd)
TMP=${TMP:-/tmp}
PKG=$TMP/package-eudev

rm -rf $PKG
mkdir -p $TMP $PKG/lib/eudev
cd $TMP
rm -rf eudev-$VERSION
# I didn't repack the gzipped source archive - Didier
tar xvf $CWD/eudev-$VERSION.tar.?z || exit 1
cd eudev-$VERSION || exit 1
chown -R root:root .
find . \
 \( -perm 777 -o -perm 775 -o -perm 711 -o -perm 555 -o -perm 511 \) \
 -exec chmod 755 {} \; -o \
 \( -perm 666 -o -perm 664 -o -perm 600 -o -perm 444 -o -perm 440 -o -perm 400 \) \
 -exec chmod 644 {} \;

# Patch 60-cdrom_id.rules to create a full set of symlinks.
# This is needed for a hotplugged optical device since the generated
# rules will not be used until the second time the device is plugged.
# Patch edited because in eudev-1.6, c60-cdrom_id.rules has moved from
# $PKG/src/cdrom_id to $PKG/rules - Didier
zcat $CWD/60-cdrom_id.rules.diff.gz | patch -p1 --verbose || exit 1

# Some new options started to get added recently to eudev from 3.0 including
# the new cache feature. Currently, we will not be using the documentation as
# the instalaltion for these seem to be hard coded and tends to create unwanted
# directories in /tmp that shouldn't exist.
# - James

LDFLAGS="$LDFLAGS -lrt" \
./configure \
  --prefix=/usr \
  --bindir=/sbin \
  --sbindir=/sbin \
  --libdir=/usr/lib${LIBDIRSUFFIX} \
  --sysconfdir=/etc \
  --libexecdir=/lib \
  --with-rootprefix= \
  --with-rootlibdir=/lib${LIBDIRSUFFIX} \
  --enable-split-usr \
  --with-firmware-path=/lib/firmware/updates:/lib/firmware \
  --enable-introspection=yes \
  --mandir=/usr/man \
  --docdir=/usr/doc/udev-$VERSION \
  --enable-static \
  --enable-rule_generator \
  --enable-libkmod \
  --enable-cache \
  --disable-gtk-doc-html \
  --build=$ARCH-slackware-linux || exit 1

make $NUMJOBS || make || exit 1
make install DESTDIR=$PKG || exit 1

find $PKG | xargs file | grep -e "executable" -e "shared object" | grep ELF \
  | cut -f 1 -d : | xargs strip --strip-unneeded 2> /dev/null || true

# scsi_id is needed by multipath
( cd $PKG/sbin ; ln -s ../lib/udev/scsi_id scsi_id )

mkdir -p \
  $PKG/run \
  $PKG/{etc,lib}/modprobe.d \
  $PKG/etc/udev/rules.d \
  $PKG/lib/firmware

# Yes, these will clobber existing config files.
cp -a $CWD/config/udev.conf $PKG/etc/udev/udev.conf

# Copy Slackware custom rules
cp -a $CWD/config/rules.d/* $PKG/lib/udev/rules.d/

# Now the init script and module-init-tools stuff
# First we'll check for Slackware's rc-init system, otherwise we'll build for OpenRC
# and avoid the need for the boot script and the traditional init /etc/rc.d directory.
if [ -d /etc/rc.d ]; then
  mkdir -p $PKG/etc/rc.d
  cp -a $CWD/config/rc.d/rc.udev.new $PKG/etc/rc.d/rc.udev.new
fi
cp -a $CWD/config/modprobe.d/*.conf $PKG/lib/modprobe.d/
cp -a $CWD/config/modprobe.d/README $PKG/etc/modprobe.d/

chown -R root:root $PKG/etc $PKG/lib/modprobe.d
find $PKG/etc $PKG/lib/modprobe.d -type f -exec chmod 644 {} \;
find $PKG/etc -type d -exec chmod 755 {} \;
chmod 0755 $PKG/etc/rc.d/rc.udev.new
chown -R root:root $PKG/lib/udev
chmod 0755 $PKG/lib/udev/*

mkdir -p $PKG/usr/doc/eudev-$VERSION
cp -a \
  COPYING* README* \
  $PKG/usr/doc/eudev-$VERSION

# Compress and fix manpage symlinks:
if [ -d $PKG/usr/man ]; then
  ( cd $PKG/usr/man
    for manpagedir in $(find . -type d -name "man*") ; do
      ( cd $manpagedir
        for eachpage in $( find . -type l -maxdepth 1) ; do
          ln -s $( readlink $eachpage ).gz $eachpage.gz
          rm $eachpage
        done
        gzip -9 *.?
      )
    done
  )
fi

# We need to name that symlink as expected by the binaries linked to
# udev-182 in Slackware 14.1 - Didier
mv $PKG/lib${LIBDIRSUFFIX}/libudev.so.1 $PKG/lib${LIBDIRSUFFIX}/libudev.so.0

mkdir -p $PKG/install
zcat $CWD/doinst.sh.gz > $PKG/install/doinst.sh
cat $CWD/slack-desc > $PKG/install/slack-desc

cd $PKG

/sbin/makepkg -l y -c y $TMP/eudev-$VERSION-$ARCH-$BUILD.txz
Patrick, Didier, and myself all contributed to the evolution of this script.

Funny thing is, a while back, Robby Workman also had a systemd-udev package that extracted udev out of systemd directly using a different method with a script that was also based on Patrick's.

*sarcasm alert*
Gee... did Robby steal from Patrick???!!! GASP!!!

Last edited by ReaperX7; 06-06-2015 at 10:37 PM.
 
Old 06-07-2015, 03:53 AM   #82
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-15.0
Posts: 11,048

Rep: Reputation: Disabled
Quote:
Originally Posted by ReaperX7 View Post
And if you really want to complain about a script, complain about who owns this one:

Code:
#!/bin/sh

# Copyright 2006, 2008, 2009, 2010, 2011, 2012, 2013  Patrick J. Volkerding, Sebeka, MN, USA
# Copyright 2014 Didier Spaier Paris, France
# Copyright 2015 James Powell Tulare, CA, USA
# All rights reserved.
# Adapted to build a package for eudev-1.6 by Didier Spaier 2014, from 
# udev.SlackBuild included in Slackware64-14.1 that builds a package for
# udev-182 build 7.
# Readapted to build package for eudev-3.1 by James Powell 2105.
#
# Redistribution and use of this script, with or without modification, is
# permitted provided that the following conditions are met:
...
Patrick, Didier, and myself all contributed to the evolution of this script.

Funny thing is, a while back, Robby Workman also had a systemd-udev package that extracted udev out of systemd directly using a different method with a script that was also based on Patrick's.

*sarcasm alert*
Gee... did Robby steal from Patrick???!!! GASP!!!
Well actually I never claimed a copyright on that script.. Here is the beginning of eudev.SlackBuild in the tarball from which you started:
Code:
#!/bin/sh

# Copyright 2006, 2008, 2009, 2010, 2011, 2012, 2013  Patrick J. Volkerding, Sebeka, MN, USA
# All rights reserved.
# Adapted to build a package for eudev-2.1.1 by Didier Spaier 2014, from 
# udev.SlackBuild included in Slackware64-14.1 that builds a package for
# udev-182 build 7.
# /etc/rc.d/rc.udev patched to create /dev/shm thanks to metaschima @ LQ 
#
# Redistribution and use of this script, with or without modification, is
# permitted provided that the following conditions are met:
...
Unless you actually started with another version?

EDIT: I see now that you used as a basis this older version. But I didn't claim a copyright in it either. I would prefer that you remove the line you added that mentions it in your repository.

Last edited by Didier Spaier; 06-07-2015 at 04:17 AM. Reason: EDIIT modified to request the removal of "Copyright Didier Spaier..."
 
Old 06-07-2015, 04:14 AM   #83
ReaperX7
LQ Guru
 
Registered: Jul 2011
Location: California
Distribution: Slackware64-15.0 Multilib
Posts: 6,554
Blog Entries: 15

Rep: Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097
Yeah, I grabbed the 1.6 copy as it was the only one I could dig up. I think you had taken the 2.x one down already.

I could always edit it to say 1.6 ~ 2.1.1 for your contribution and get it correct, if needed. After all, you did work on it from those versions.

Last edited by ReaperX7; 06-07-2015 at 04:18 AM.
 
Old 06-07-2015, 04:20 AM   #84
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-15.0
Posts: 11,048

Rep: Reputation: Disabled
Quote:
Originally Posted by ReaperX7 View Post
Yeah, I grabbed the 1.6 copy as it was the only one I could dig up.
The 2.1.1 tarball expands to a directory that includes both the build stuff and the source tarball.

Last edited by Didier Spaier; 06-07-2015 at 07:56 AM.
 
Old 06-07-2015, 07:22 AM   #85
ReaperX7
LQ Guru
 
Registered: Jul 2011
Location: California
Distribution: Slackware64-15.0 Multilib
Posts: 6,554
Blog Entries: 15

Rep: Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097
Hmmm... I wonder which copy I grabbed then. Regardless I can always fire up the editor and check stuff as I go. Rather get it right than wrong.

I'm out and about, but I'll fix it later today. Regardless I still wish to credit you Didier.

Last edited by ReaperX7; 06-07-2015 at 07:23 AM.
 
Old 06-07-2015, 07:47 AM   #86
Darth Vader
Senior Member
 
Registered: May 2008
Location: Romania
Distribution: DARKSTAR Linux 2008.1
Posts: 2,727

Rep: Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247
WTF?

Amazing!

So, the (almost official?) encouraged Slackware Copyright System can make you to own a Copyright even beyond your willing... OMG! WTF?

I just wonder, WHEN the Copyright Madness will reach the Supernova Level?

Last edited by Darth Vader; 06-07-2015 at 07:52 AM.
 
Old 06-07-2015, 08:18 AM   #87
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-15.0
Posts: 11,048

Rep: Reputation: Disabled
Quote:
Originally Posted by Darth Vader View Post
So, the (almost official?) encouraged Slackware Copyright System can make you to own a Copyright even beyond your willing... OMG! WTF?
No. This is just a tiny mistake made believing do well and that can be easily repaired.

@ReaperX7: just keeping "modified by Didier Spaier ..." is more than enough to give me credit for the few minutes I spent on that.

I am sorry to make readers waste their time reading such uninteresting details, so let's move on.

Last edited by Didier Spaier; 06-07-2015 at 08:19 AM.
 
Old 06-07-2015, 08:22 AM   #88
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 8,559

Rep: Reputation: 8105Reputation: 8105Reputation: 8105Reputation: 8105Reputation: 8105Reputation: 8105Reputation: 8105Reputation: 8105Reputation: 8105Reputation: 8105Reputation: 8105
The old sage and his young adept sat together in front of the cave, pondering life. The adept asked what the strange noises in the back of the cave were all about. The sage explained to the young adept: "You can enter the cave and look for yourself, but... Do Not Feed The Troll".
The young adept heeded the sage's advice and all becam eclear. He then set out into the world to attain wisdom of himself, and the troll in the cave died.
 
6 members found this post helpful.
Old 06-07-2015, 09:48 AM   #89
ReaperX7
LQ Guru
 
Registered: Jul 2011
Location: California
Distribution: Slackware64-15.0 Multilib
Posts: 6,554
Blog Entries: 15

Rep: Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097
Quote:
Originally Posted by Didier Spaier View Post
No. This is just a tiny mistake made believing do well and that can be easily repaired.

@ReaperX7: just keeping "modified by Didier Spaier ..." is more than enough to give me credit for the few minutes I spent on that.

I am sorry to make readers waste their time reading such uninteresting details, so let's move on.
No prob Didier. I've edited it in a way that removes the unclaimed copyright, but keeps the modification information as you requested with a special notation that the work was continued after 1.6 until 3.1 was reworked to at least acknowledge and show the efforts from versions such as 2.1.1.

If ever needed I can merge the 2.1.1 license info at your discretion for completeness.

Last edited by ReaperX7; 06-07-2015 at 09:59 AM.
 
Old 06-26-2015, 10:43 PM   #90
ivandi
Member
 
Registered: Jul 2009
Location: Québec, Canada
Distribution: CRUX, Debian
Posts: 528

Original Poster
Rep: Reputation: 866Reputation: 866Reputation: 866Reputation: 866Reputation: 866Reputation: 866Reputation: 866
The url in the beginning of the thread has been redirected to a subfolder of SlackMATE
You have to comment out the stuff you don't need in SlackMATE.SlackBuild
For example:
Code:
# Start the build
export TMP=/tmp/pam
export OUTPUT=/tmp/pam/txz
export TAG=_pam
export PKGTYPE=txz
build_dir pam

export TMP=/tmp/mate
export OUTPUT=/tmp/mate/txz
export TAG=_mate
export PKGTYPE=txz
# build_dir libs
# build_dir multimedia
# build_dir mate
# build_dir apps
# build_dir virt
# build_dir scientific
Cheers
 
2 members found this post helpful.
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Managing multiple kerberos/ADS realms edgood1 Linux - Software 0 06-09-2009 02:44 PM
ADS / winbind / samba / kerberos HELP!!! jsheffie Red Hat 5 08-16-2006 09:01 AM
Samba, Kerberos and ADS problems deadlock Linux - Networking 0 01-26-2006 11:27 AM
suse9.1client W2k ADS kerberos and pam fatcake Linux - Networking 1 06-09-2005 01:27 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 07:20 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration