[Slackbuilds-users] Why did my SSLeay-SlackBuild get edited?

[Robby Workman]

On Wed, 05 Nov 2008 15:03:07 +0100
"Manuel Reimer" <Manuel.Reimer at gmx.de> wrote:

> some days ago I've uploaded a SlackBuild script to build SSLeay. It
> took me several hours to test the script over and over again until I
> finally published the script.


Thanks for the contribution!


> Today I've recognized the entry in the ChangeLog which shows that my
> package got accepted, but the line where I extract the tar-archive
> got changed and the silly "find ... chmod" waste got added.
> 
> Why did you change this part? Why do you think it's a cleaner way to
> do things, to not tell tar to ignore the permissions in the archive,
> but to allow tar to extract with silly permissions just to be able to
> fix up the crap in a second step?


That's just the way we do it.  Is there a *technical* problem with our
way, or are we going to argue about the best color to paint the bike
shed?


> IMHO if there is no real reason to change the way the author did
> things, then the script shouldn't get changed. It's *my* name which
> is in the header line of the script and so the script should also
> reflect my way of coding things if they don't violate any rules or
> don't cause problems. IMHO it would be also a great idea to ask the
> author first prior changing things and publishing the result in the
> name of the Author. 


From your submission:

# Copyright 2008 Manuel Reimer <manuel.reimer at gmx.de>
# 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.


Is there some part of that by which we did not abide?  If so, please
point it out and we'll correct it. 

If you don't like the idea of someone modifying the script, then you
can release your work with a nonfree license (elsewhere, of course).

-RW
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20081105/dd5de628/attachment.asc>