Hello Yaroslav,
you wrote:
* once I had wrote a little helper for myself
http://anonscm.debian.org/viewvc/pkg-exppsy/tools/dh_wraporig?view=markup
which I had used for many cases like this, it was also autogenerating
README.Debian-source
which summarized the changes
That looks interesting, I will try it if the outcome is that a repacking
still is what I should do.
* custom get-orig-source rule in debian/rules -- most popular way to
automate things of this kind ;)
That's just where to put it, not what to put there?
since you are using git, you might also like simply to tune up
.gitattributes to exclude undesired pieces from the generated by git
archive tarball
I am using "distutils" to provide the "sdist" and not git. That has the
advantage to provide other targets as well. I think that idea is also
from a tutorial of the team somehow, as dh_python2 uses it too.
I think so too... meanwhile, here
http://www.onerussian.com/tmp/nuitka-logs.tgz
fetch build logs for your most recent package (fails everywhere
now -- thanks to tests ;) )
it would be great if for every upload you verify that package builds
fine in a clean chroot ;-)
Yeah yeah. :-)
I had installed the "pbuilder" stuff and things, but honestly, normally
I don't see much point, once it will be working again. Mostly because
the binary package contains no binaries and the tame dependencies.
And I even predicted it, but couldn't fix it anymore. I knew it was
flawed, but "mentors.debian.net" won't let me upload any "-2" ever,
presumably due to the changed "orig" source.
I might make a new "pre4" minor release later today with it included,
once I understood what to do with the "+dfsg" suffix. Changing that
suffix may also be enough I figured.
AFAIK (would be great if someone corrects me) -- besides some
somewhat over-engineered ways to generate debian/control from
debian/control.in or smth like that, there is no good way, so specifying
them both in depends and build-depends is what I have been doing.
OK, I just didn't want to miss it if there was an easy way. I saw things
like "${misc:Depends}" and thought there could be a way to express it.
But it's totally not worth it with only 2 of them.
Yours,
Kay
--
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/4f023f23.6050...@gmx.de
