Re: [Gramps-devel] setup.py

[Serge N. <Ser...@fr...>]

Hi,

currently, I prefer make.
How can we do "make clean" with setup.py ?
When we often do svn up, if some files are renamed or suppressed, make clean is used to remove all *.pyc", ...
If we do "make distclean", we restart as if the gramps tree was new ( remove all config files, ... )


Le 12/03/2012 18:39, jerome a écrit :
> Hi,
>
>
> I suppose I have finished what I planned with the experimental 'setup.py'.
> I tested 'babel' classes[1], but it looks like that there is nothing that we cannot make ourself. So, do not need an other dependency.
>
> Unfortunately, I did not find a multiplatform tool for extracting and merging some specific entries (.glade, .xml, .keys, .desktop).
> This means that extracting messages should be performed with installed intltool[2]. Note, it is only for generating a new template (gramps.pot) and building/installing Gramps does not need it.
>
> I wanted to put this part out of 'setup.py', but I also re-used some available lists (files to install). Otherwise, we may also would like to have an up-to-date 'gramps.pot' with code for people who do not use SVN.
>
> I also modified the common 'build, install' commands!
> Why ? Because of rights issues (user/admin) and some specific Gramps' things that distutils[3] does not use by default! It was also simplier to test without some of these classes... The uninstall class is also inherited from some others 'setup.py'. And these __init__.py everywhere is not very nice! Not certain that 'setuptools' is a good choice...
>
> Anyway, once we know what should be done with some non-python files (glade, css, images, etc ...) and if it should generate multiple packages according to current ecosystem (webbapp, gen, gui, etc ...), then it seems that with minor changes we could have a working 'setup.py'.
>
> I tried to add comments where something has to be fixed or where there is some possible specific behavior. I generated some .rpm packages for Gramps under OpenSuse in the past and I hope that everything is correct on this 'setup.py', but I also know that I tried to use what is currently working under my configuration and that cannot be used for production.
>
> PS: during investigations, I saw some custom strings:
> src/ExportAssistant.py:494:
> src/gramps.py:115
> src/Filters/SideBar/_PersonSidebarFilter.py:131
> src/Filters/SideBar/_PersonSidebarFilter.py:133
> src/cli/clidbman.py:78
> src/gen/db/upgrade.py:81
> src/gen/db/upgrade.py:82
> src/gen/db/upgrade.py:83
> src/gen/db/upgrade.py:84
> src/gen/db/upgrade.py:85
> src/gen/db/upgrade.py:86
> src/gen/plug/utils.py:271
> src/gui/makefilter.py:49
> src/gui/plug/_guioptions.py:844
> src/plugins/gramplet/EditExifMetadata.py:469
> src/plugins/gramplet/Notes.py:100
> src/plugins/lib/libgedcom.py:6414
> src/plugins/mapservices/eniroswedenmap.py:139
> src/plugins/mapservices/eniroswedenmap.py:140
> src/plugins/textreport/DetDescendantReport.py:576
> src/plugins/textreport/IndivComplete.py:208
> src/plugins/textreport/PlaceReport.py:225
> src/plugins/view/geofamily.py:299
> src/plugins/view/geofamily.py:306
> src/plugins/view/relview.py:1180
> src/plugins/view/relview.py:1182
> src/plugins/webreport/NarrativeWeb.py:1511
> src/plugins/webreport/NarrativeWeb.py:6938
> src/plugins/tool/mergecitations.glade:132
>
> I assume they are not conform!
> We could also avoid to translate some strings used fr debbuging/log or some DB things. I will try to remove some translation marks on some of these files.
>
>
> [1] http://babel.edgewall.org/wiki/Documentation/setup.html
> [2] http://freedesktop.org/wiki/Software/intltool
> [3] http://docs.python.org/library/distutils.html#module-distutils
>
>
> regards,
>