On Jul 01, 2011, at 01:00 AM, Mitar wrote:
>I will not yet use "dh" as it looks too magical for me for now. I
>would like to understand what is happening. And first have a working
>package. Then I can play with cleaning it up. Or would it be easier to
>just let dh do everything? I doubt it can be
On 06/29/2011 06:58 PM, Mitar wrote:
> I have made a Debian package for Orange:
>
> http://orange.biolab.si/
>
> The idea is that we have a daily snapshot packaged as Debian package.
>
> You can get it here (also source package):
>
> http://orange.biolab.si/debian/
FYI, a separate packaging wa
HELP
--
mauro
mauro [at] majaglug [dot] net
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4e0dc926.3090...@majaglug.net
Hi!
On Fri, Jul 1, 2011 at 3:27 PM, Christian Kastner wrote:
> I don't know how current this is, but there might be some helpful stuff
> in there. Either way, if you indeed will start to provide packaging
> upstream, then the above repo should probably be removed to avoide
> confusion.
Yes. This
On 07/01/2011 05:21 AM, Barry Warsaw wrote:
> On Jul 01, 2011, at 01:00 AM, Mitar wrote:
>
>> I will not yet use "dh" as it looks too magical for me for now. I
>> would like to understand what is happening. And first have a working
>> package. Then I can play with cleaning it up. Or would it be ea
Apologies for the delayed response.
On Jun 15, 2011, at 01:03 AM, Zygmunt Krynicki wrote:
>W dniu 15.06.2011 00:04, Barry Warsaw pisze:
>> On Jun 14, 2011, at 05:53 PM, Zygmunt Krynicki wrote:
>>
>>> Can please we have standardized hooks to build sphinx documentation and run
>>> setup.py test tes
On Jul 01, 2011, at 09:23 AM, Christian Kastner wrote:
>It's definitely preferable for an experienced packager, it can be
>confusing as hell though to the commencing packager because in order to
>understand dh syntax, you must first understand what debian/rules does,
>ie the actual process of buil
On Jun 15, 2011, at 05:07 PM, Éric Araujo wrote:
>Yes, last summer’s GSoC added a test command, which defaults to
>unittest(2) test discovery and can be configured to use any test runner
>on any test suite. It runs tests against the modules in the build
>directory, to be able to work with code co
On Jun 15, 2011, at 02:39 AM, Zygmunt Krynicki wrote:
>I agree in the value but I don't want to assume that it is a default practice
>or requirement. I package/hack on the webapp (django) side of tests and after
>being spoiled with the goodness of python-testtools and python-testscenarios
>I ventu
9 matches
Mail list logo
