[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

From: Jim Busser
Subject: Re: [Gnumed-devel] Re: Packaging (Was: Naming convention)
Date: Wed, 09 Sep 2009 00:01:55 -0700

On 8-Sep-09, at 8:28 AM, Karsten Hilbert wrote:

On Tue, Sep 08, 2009 at 01:02:30AM -0700, Jim Busser wrote:


into --> /usr/share/gnumed/

... but why not into /usr/share/gnumed/Gnumed/

Why should it ?

Because in cvs, the directory hierarchy in the same level includes


and so as far as establishing the top of the Python packages tree, when gnumed-client would get installed on a machine, it would have seemed to me less confusing to establish


Even if we had seemed to saddle ourselves with


with an import method

from Gnumed.pycommon import

it could be replaced with

from client.pycommon import
But the other thing is it remains in my mind opaque why to place the tarball's (client) bitmaps in


when in cvs they are at the same level as pycommon and other stuff, therefore why not into

/usr/share/gnumed/client (oops!)

reply via email to

[Prev in Thread] Current Thread [Next in Thread]