Re: [Gramps-devel] URGENT ATTENTION: separate gramps directory structure

[Jérôme <rom...@ya...>]

Tim,


A simple copy of common files should allow us to run on most plateform.
All other things are OS stuff (dependencies, specific behavior, config).

            {
             'gramps': [
             '*.py',
             'DateHandler/*.py',
             'docgen/*.py',
             'Filters/*.py',
             'Filters/*/*.py',
             'Filters/Rules/*/*.py',
             'GrampsLocale/*.py',
             'GrampsLogger/*.py',
             'Merge/*.py',
             'Simple/*.py'],
             'gramps.cli': [
             '*.py',
             'plug/*.py'],
             'gramps.data': [
             '*.txt',
             '*.xml'],
             'gramps.gen': [
             '*.py',
             'db/*.py',
             'display/*.py',
             'lib/*.py',
             'mime/*.py',
             'plug/*.py',
             'plug/*/*.py',
             'proxy/*.py',
             'utils/*.py'],
             'gramps.glade': [
             '*.glade',
             'glade/catalog/*.py',
             'catalog/*.xml'],
             'gramps.gui': [
             '*.py',
             'editors/*.py',
             'editors/*/*.py',
             'plug/*.py',
             'plug/*/*.py',
             'selectors/*.py',
             'views/*.py',
             'views/treemodels/*.py',
             'widgets/*.py'],
             'gramps.images': [
             '*/*.png',
             '*/*.svg',
             '*.png',
             '*.jpg',
             '*.ico',
             '*.gif'],
             'gramps.plugins': [
             '*.py',
             '*/*.py',
             'lib/*.xml',
             'lib/maps/*.py',
             '*.glade',
             '*/*.glade',
             'webstuff/css/*.css',
             'webstuff/images/*.svg',
             'webstuff/images/*.png',
             'webstuff/images/*.gif'],
             'gramps.webapp': [
             '*.py',
             'webstuff/css/*.css',
             'webstuff/images/*.svg',
             'webstuff/images/*.png',
             'webstuff/images/*.gif',
             'grampsdb/fixtures/initial_data.json',
             '*/*.py',
             'sqlite.db',
             'grampsdb/*.py',
             'fixtures/initial_data.json',
             'templatetags/*py'],
             }

Nothing will be compiled, except maybe on bundles/ports, which need a 
binary/certified OS package, right?


Jérôme

Tim Lyons a écrit :
> jerome wrote
>> Step after step, I am just investigating what could be the simplier for
>> maintenance, installation, packaging around translations. I looked at
>> current use of Makefile (building and installation), and I tried a simple
>> transcription into python according to feature request started by Benny.
>>
> 
> I suspect that MacPorts expects to use Makefiles and is designed to
> automatically call them. Also would other ports (e.g. the build of the Mac
> AIO package and the various Windows installations) need to be changed if you
> moved away from Makefiles?
> 
> What is actually the objective of these changes? I note bug 0002621: use
> python-setuptools instead of make, but what do these changes actually
> achieve from the point of view of the user or developer?
> 
> Just asking.
> 
> --
> View this message in context: http://gramps.1791082.n4.nabble.com/URGENT-ATTENTION-separate-gramps-directory-structure-tp4473961p4474560.html
> Sent from the GRAMPS - Dev mailing list archive at Nabble.com.
> 
> ------------------------------------------------------------------------------
> This SF email is sponsosred by:
> Try Windows Azure free for 90 days Click Here 
> http://p.sf.net/sfu/sfd2d-msazure
> _______________________________________________
> Gramps-devel mailing list
> Gra...@li...
> https://lists.sourceforge.net/lists/listinfo/gramps-devel
>