Firstly, thank you for the replies: it's the response to even the daftest 
question which keeps the community flourishing. To those who've replied: you 
have reinforced my faith in Debian and Python.

This mail is just to say that I've successfully created a native source tree 
and accompanied notes for building, installing and removing a minimal Python 
sdist, egg or "Debian package using dh_python2".

Barry, thanks for the pointer to flufl.enum and its package files. Prior to 
your guidance I was stuck on an unexpected blocker: all my other hand-created 
Debian packages have had a Makefile and to start with this one did too. At the 
time it was sans install target and my Debian package was built "successfully" 
- though it never contained my Python source text!? The root cause of my 
frustration was that my package build was silently successful with rules "dh @ 
--with python2". I twigged the cause at 04:30 this morning. What got me past my 
sticking point was the absence of a Makefile from flufl.enum. Honestly, I 
thought I was doing something seriously wrong - I wasn't expecting the presence 
of a simple Makefile to be the answer!

So, thank you for the replies and sorry for the exposure to my bluster.

I will live up to my promise to document what I've done step-by-step to 
complement what's already out there. Pls bear with me.

Br.,
David

--
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/fa3385de-2460-4d21-b302-ed4ee6983...@roughsketch.co.uk

Reply via email to