All of lore.kernel.org
 help / color / mirror / Atom feed
From: Seth Forshee <seth.forshee@canonical.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH trace-cmd 2/5] build: Install data files without execute permissions
Date: Fri, 25 Oct 2013 08:05:34 -0500	[thread overview]
Message-ID: <20131025130534.GA24608@thinkpad-t410> (raw)
In-Reply-To: <1382689893.8356.2.camel@pippen.local.home>

On Fri, Oct 25, 2013 at 04:31:33AM -0400, Steven Rostedt wrote:
> On Thu, 2013-10-24 at 14:14 -0500, Seth Forshee wrote:
> > diff --git a/Makefile b/Makefile
> > index 1964949..2423038 100644
> > --- a/Makefile
> > +++ b/Makefile
> > @@ -86,7 +86,8 @@ ifeq ($(shell sh -c "python-config --includes > /dev/null 2>&1 && echo y"), y)
> >  	PYTHON_PLUGINS := plugin_python.so
> >  	BUILD_PYTHON := $(PYTHON) $(PYTHON_PLUGINS)
> >  	PYTHON_SO_INSTALL := ctracecmd.install
> > -	PYTHON_PY_INSTALL := event-viewer.install tracecmd.install tracecmdgui.install
> > +	PYTHON_PY_PROGS := event-viewer.install
> > +	PYTHON_PY_LIBS := tracecmd.install tracecmdgui.install
> >  endif
> >  endif # NO_PYTHON
> >  
> > @@ -506,21 +507,32 @@ define do_install
> >  	$(INSTALL) $1 '$(DESTDIR_SQ)$2'
> >  endef
> >  
> > +define do_install_data
> > +	$(print_install)				\
> > +	if [ ! -d '$(DESTDIR_SQ)$2' ]; then		\
> > +		$(INSTALL) -d -m 755 '$(DESTDIR_SQ)$2';	\
> > +	fi;						\
> > +	$(INSTALL) -m 644 $1 '$(DESTDIR_SQ)$2'
> > +endef
> > +
> >  $(PLUGINS_INSTALL): %.install : %.so force
> > -	$(Q)$(call do_install,$<,$(plugin_dir_SQ))
> > +	$(Q)$(call do_install_data,$<,$(plugin_dir_SQ))
> >  
> >  install_plugins: $(PLUGINS_INSTALL)
> >  
> >  $(PYTHON_SO_INSTALL): %.install : %.so force
> > -	$(Q)$(call do_install,$<,$(python_dir_SQ))
> > +	$(Q)$(call do_install_data,$<,$(python_dir_SQ))
> 
> Hmm, I never realized that shared libraries are not suppose to be
> executable. At first I thought this was a mistake, but looking at other
> shared libraries on my system, it seems a lot are not executable
> (although many are, but those may also be made by people like myself who
> thought there were suppose to be).

I don't know that it's a hard and fast rule, but what guidance I found
from searching online was in favor of them not being executable. That
kind of makes sense, since they can't be executed directly (at least not
the ones that trace-cmd installs).

If you disagree, it won't hurt my feelings if you drop those changes, so
long as you keep the ones which makes sure things like .png files aren't
executable ;-)

Thanks,
Seth

  reply	other threads:[~2013-10-25 13:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-24 19:14 [PATCH trace-cmd 0/5] Miscellaneous fixes for trace-cmd Seth Forshee
2013-10-24 19:14 ` [PATCH trace-cmd 1/5] trace-cmd/listen: Remove use of sighandler_t Seth Forshee
2013-10-24 20:30   ` Seth Forshee
2013-10-28 15:45     ` Seth Forshee
2013-11-01 13:40       ` Steven Rostedt
2013-10-24 19:14 ` [PATCH trace-cmd 2/5] build: Install data files without execute permissions Seth Forshee
2013-10-25  8:31   ` Steven Rostedt
2013-10-25 13:05     ` Seth Forshee [this message]
2013-10-25 13:42       ` Steven Rostedt
2013-10-24 19:14 ` [PATCH trace-cmd 3/5] Add missing libgen.h includes Seth Forshee
2013-10-24 19:14 ` [PATCH trace-cmd 4/5] Documentation: Add kernelshark.1.txt Seth Forshee
2013-11-11  6:54   ` Rob Landley
2013-11-11 13:47     ` Seth Forshee
2013-10-24 19:14 ` [PATCH trace-cmd 5/5] build: Use CFLAGS and LDFLAGS when building python bits Seth Forshee

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=20131025130534.GA24608@thinkpad-t410 \
    --to=seth.forshee@canonical.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    /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.