Seriously? First of all, who cares?! Why would you even bother changing that? Second of all, I'm not sure it's correct, doesn't gdb only load executable extensions?
-- Tom. On 24/09/14 09:55, Cedric BAIL wrote: > cedric pushed a commit to branch master. > > http://git.enlightenment.org/core/efl.git/commit/?id=c9fe6d64a8a3a88631777107fbf89aa5824163c8 > > commit c9fe6d64a8a3a88631777107fbf89aa5824163c8 > Author: Cedric BAIL <[email protected]> > Date: Wed Sep 24 10:26:35 2014 +0200 > > eo: use the "EXTRA_DIST" macro to install .py files > > Summary: > The SCRIPTS macro will add the executable flag (+x) to the Python > scripts ; but as > these do not have a shebang (#!/bin/python) and we are executing them > explicitly with > "python ...", it is useless. Plus, some build environments will issue a > warning about > this. > > Reviewers: tasn, JackDanielZ > > Subscribers: mbachmann > > Projects: #efl > > Differential Revision: https://phab.enlightenment.org/D1469 > > Signed-off-by: Cedric BAIL <[email protected]> > --- > data/Makefile.am | 6 ++++-- > 1 file changed, 4 insertions(+), 2 deletions(-) > > diff --git a/data/Makefile.am b/data/Makefile.am > index c36f3b2..af969da 100644 > --- a/data/Makefile.am > +++ b/data/Makefile.am > @@ -48,14 +48,16 @@ EXTRA_DIST += $(efreetfiles_DATA) > ######################################################################## > # Eo > eogdbdir = $(datadir)/eo/gdb > -eogdb_SCRIPTS = eo/eo_gdb.py > +eogdb_DATA = eo/eo_gdb.py > +EXTRA_DIST += $(eogdb_DATA) > > # Borrowed from gobject > libeo.so.@VMAJ@.@VMIN@.@[email protected]: eo/libeo-gdb.py.in > $(AM_V_GEN) $(SED) -e "s|\@datadir\@|$(datadir)|" > $(srcdir)/eo/libeo-gdb.py.in > > $(builddir)/libeo.so.@VMAJ@.@VMIN@.@[email protected] > > eogdbloaddir = $(datadir)/gdb/auto-load/$(libdir) > -eogdbload_SCRIPTS = libeo.so.@VMAJ@.@VMIN@.@[email protected] > +eogdbload_DATA = libeo.so.@VMAJ@.@VMIN@.@[email protected] > +EXTRA_DIST += $(eogdbload_DATA) > > CLEANFILES += libeo.so.@VMAJ@.@VMIN@.@[email protected] > > ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
