[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnumed-devel] Re: Packaging (Was: Naming convention)
From: |
Karsten Hilbert |
Subject: |
Re: [Gnumed-devel] Re: Packaging (Was: Naming convention) |
Date: |
Tue, 8 Sep 2009 17:28:31 +0200 |
User-agent: |
Mutt/1.5.20 (2009-06-14) |
On Tue, Sep 08, 2009 at 01:02:30AM -0700, Jim Busser wrote:
> bitmaps
>
> into --> /usr/share/gnumed/
>
> ... but why not into /usr/share/gnumed/Gnumed/
Why should it ?
> business
> exporters
> pycommon
> wxGladeWidgets
> wxpython
> __init__.py
> __init__.pyc
>
> above ends up in --> /usr/share/gnumed/Gnumed/
>
> is the second Gnumed dir needed?
Yes. It represents the Python package directory top which
allows for:
from Gnumed.pycommon import gmPG2
etc.
> would it be better named /client ?
It could be named /python-client-source, if felt needed.
> gm_ctl_client.1
> gnumed.1
/usr/share/man/1/
> gnumed.conf.example # it's just gm-from-cvs.conf
below /usr/share/doc/gnumed-client/
> hook_script_example.py
> --> into /home/jbusser/.gnumed/scripts
> (as hook_script.py)
if desired
> but there also resides
> hook_script.pyc
> which originated from ??
compiled from hook_script.py
> tarball etc/
> gnumed/
> egk+kvk-demon.conf.example # future use?
yes
> gnumed-client.conf.example
> # above is derived from gm-from-cvs.conf ?
yes
> # in future will drop the .example suffix?
no
> gnumed-client-init_script.sh # future use?
yes
> mime_type2file_extension.conf
> (derived from
> mime_type2file_extension.conf.example ?
yes
> gm_ctl_client.conf # seemingly from connectors dir
yes
> gnumed-backup.conf # seemingly from cvs else from server?
> gnumed-restore.conf # .example found in cvs else from server?
from server
--
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346
- [Gnumed-devel] Re: Re: Packaging (Was: Naming convention), (continued)
- Re: [Gnumed-devel] Re: Re: Packaging (Was: Naming convention), Jim Busser, 2009/09/09
- Re: [Gnumed-devel] Re: Re: Packaging (Was: Naming convention), Jim Busser, 2009/09/09
- Re: [Gnumed-devel] Re: Packaging (Was: Naming convention), Jim Busser, 2009/09/08
- Re: [Gnumed-devel] Re: Packaging (Was: Naming convention), Karsten Hilbert, 2009/09/08
- Re: [Gnumed-devel] Re: Packaging (Was: Naming convention), Jim Busser, 2009/09/09
- Re: [Gnumed-devel] Re: Packaging (Was: Naming convention), Jim Busser, 2009/09/08
- [Gnumed-devel] Re: Re: Packaging (Was: Naming convention), Andreas Tille, 2009/09/09
- Re: [Gnumed-devel] Re: Re: Packaging (Was: Naming convention), Jim Busser, 2009/09/09
- Re: [Gnumed-devel] Re: Packaging (Was: Naming convention),
Karsten Hilbert <=
- Re: [Gnumed-devel] Re: Packaging (Was: Naming convention), Jim Busser, 2009/09/09
- Re: [Gnumed-devel] Re: Packaging (Was: Naming convention), Jim Busser, 2009/09/09
- Re: [Gnumed-devel] Re: Packaging (Was: Naming convention), Karsten Hilbert, 2009/09/09
- Re: [Gnumed-devel] Re: Packaging (Was: Naming convention), Karsten Hilbert, 2009/09/09
- Re: [Gnumed-devel] Re: Packaging (Was: Naming convention), Jim Busser, 2009/09/09
- Re: [Gnumed-devel] Re: Packaging (Was: Naming convention), Karsten Hilbert, 2009/09/13
- [Gnumed-devel] Re: Packaging (Was: Naming convention), Andreas Tille, 2009/09/08
- Re: [Gnumed-devel] Packaging (Was: Naming convention), Karsten Hilbert, 2009/09/08
- Re: [Gnumed-devel] Naming convention (Was: Choice of programming language and project management), Jim Busser, 2009/09/08
- Re: [Gnumed-devel] Naming convention (Was: Choice of programming language and project management), Jim Busser, 2009/09/08