On Saturday 23 August 2008, Adam wrote: > Hi everybody! After considerable effort, I am almost ready to release > my first program for Linux, free to the public, and I'd like to do it > the right way.
First thing you'd probably want to do is post it up on your site; or make a
site to do that with, if you don't have one yet. ;-)
From there you have some more interesting choices; you could offer it as a:
- file download (.sh, .tar.gz, etc)
- source control management download (CVS, SVN, Git, Hg, etc)
- package download (RPM, DEB, etc) [more complicated because it means
learning how to make packages]
You get the idea. Personally I consider these more interesting to talk about
than what license to use.
> Is just putting that boilerplate as a comment near the top of my script
> sufficient? What would you advise? Thanks very much in advance!
Looking at /var/lib/dpkg/info/xserver-xorg.postrm, it contains:
#!/bin/sh
# Debian xserver-xorg package post-removal script
# Copyright 1998--2001, 2003 Branden Robinson.
# Licensed under the GNU General Public License, version 2. See the file
# /usr/share/common-licenses/GPL or <http://www.gnu.org/copyleft/gpl.txt>.
...
So something like the above should be enough; I don't think you need to
necessarily include the more lengthy boilerplate that the FSF recommends.
You can probably find other examples for short scripts for other licenses.
-- Chris
--
Chris Knadle
[EMAIL PROTECTED]
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Mid-Hudson Valley Linux Users Group http://mhvlug.org http://mhvlug.org/cgi-bin/mailman/listinfo/mhvlug Upcoming Meetings (6pm - 8pm) MHVLS Auditorium Jun 4 - Sqeak! and eToys Jul 2 - KVM (Tenative) Aug 6 - Zenos Sep 3 - TBD
