From: Ryan McCabe <rmccabe@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Cluster Project branch, master, updated. cluster-2.99.02-27-gd1d2954
Date: Thu, 29 May 2008 10:13:05 -0400 [thread overview]
Message-ID: <20080529141305.GA153998@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0805290535530.5892@trider-g7>
On Thu, May 29, 2008 at 05:39:32AM +0200, Fabio M. Di Nitto wrote:
> >
> > - Clarify copyright notice so that GPLv2 is specified explicitly.
>
> Is there any reason why it's not LGPL? I thought all our shared libraries
> should be LGPL to make life simpler for other people to use...
It is LGPL. I just made a typo in the commit message. I specified the
version of the LGPL.
> > - Use the full path to ssh and telnet when executing the binaries.
>
> It's generally better to avoid harcoding paths if we can avoid it. Custom
> builds would require extra patching if for example ssh is in
> /usr/local/bin..
From a security point of view, I think it's bad practice to be using a
relative path in an exec-type call as root. It'd be better to have the
makefile system fill in (or change) the paths if we want to allow for
builds with ssh and telnet in non-standard places.
> This change is not respected by the Makefile system. Everything between
> #BEGIN and #END is virtually ignored. Do we need to respect this spacing?
> If so, i will just change the build system to do it.
Not a big deal either way, really. It can be ignored.
Ryan
next prev parent reply other threads:[~2008-05-29 14:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-28 20:31 [Cluster-devel] Cluster Project branch, master, updated. cluster-2.99.02-27-gd1d2954 rmccabe
2008-05-29 3:39 ` Fabio M. Di Nitto
2008-05-29 14:13 ` Ryan McCabe [this message]
2008-05-29 20:44 ` Fabio M. Di Nitto
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080529141305.GA153998@redhat.com \
--to=rmccabe@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.