[Gnumed-devel] Packaging (Was: Naming convention)

[Jim Busser]

On 7-Sep-09, at 2:17 PM, Karsten Hilbert wrote:

> The ~/.gnumed/ is IMO created
> by the first run of gnumed.py as well as the gnumed.conf therein.

Thanks, it is hard to reverse engineer such things when one already  
did multiple steps (install and run) while not yet knowing so well the  
insides of the code... :-)

The above is good news, because if it is the gnumed.py which takes  
care of the instantiation of the user's files it means less for the OS  
(distro) - specific package to have to do,

Is the same true of ~/gnumed which contains

        export
        logs
        xdt

??

Also, Debian apparently copies from tarball the shell script

        client/gnumed --> /usr/bin/gnumed

and several directories of client code and resources, which appear  
under Debian to get copied into

        /usr/share/gnumed

and these get referenced by virtue of decommenting
# export PYTHONPATH
and adding an "export PATH" line as follows in /usr/bin/gnumed

# packages which install the GNUmed python modules into a path not
# already accessible for imports via sys.path (say, /usr/share/gnumed/)
# may need to adjust PYTHONPATH appropriately here
export PYTHONPATH="${PYTHONPATH}:/usr/share/gnumed/"
export PATH="${PATH}:/usr/share/gnumed/bin"

... but there is no "bin" in my /usr/share/gnumed/bin in which case is  
the above needed for some other purpose?