Re: Best practice for test(s) directories?

"Sandro Tosi" <[EMAIL PROTECTED]> writes: > Well, since tests are something not needed for the module to work > and they provide a sort of documentation of the module itself, I > usually install them as examples under /usr/share/doc/$pkg/examples I would go further, and recommend that the tests d

Re: Best practice for test(s) directories?

On Tue, Jul 15, 2008 at 12:28 AM, Sandro Tosi <[EMAIL PROTECTED]> wrote: > Hi Kibi! > > On Mon, Jul 14, 2008 at 20:13, Cyril Brulebois <[EMAIL PROTECTED]> wrote: >> Hi folks, >> >> I'm wondering whether there's a preferred place where to drop the >> test(s) directory. I don't really know whether to

Re: Best practice for test(s) directories?

Hi Kibi! On Mon, Jul 14, 2008 at 20:13, Cyril Brulebois <[EMAIL PROTECTED]> wrote: > Hi folks, > > I'm wondering whether there's a preferred place where to drop the > test(s) directory. I don't really know whether to choose >/usr/share/python-support/$package/test(s) > or >/usr/share/$pack

Best practice for test(s) directories?

Hi folks, I'm wondering whether there's a preferred place where to drop the test(s) directory. I don't really know whether to choose /usr/share/python-support/$package/test(s) or /usr/share/$package/test(s). Since it isn't really needed for the module to correctly work, I'd be tempted to

Re: Pyopengl, couple of doubts.

Am Montag, den 14.07.2008, 15:10 +0200 schrieb Andrea Gasparini: > Hi, > i'm looking at pyopengl debian/rules file[1], and I saw a couple of things > that made arise these (stupid?) question: > 1) about > install/python-opengl-doc:: > cd documentation/pydoc/ && PYTHONPATH="../.." python2.5 build

Pyopengl, couple of doubts.

Hi, i'm looking at pyopengl debian/rules file[1], and I saw a couple of things that made arise these (stupid?) question: 1) about install/python-opengl-doc:: cd documentation/pydoc/ && PYTHONPATH="../.." python2.5 builddocs.py won't be better use a $pyvers variable? we're more general, and if (