Re: Build-Depends-Indep dependencies
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 10/26/2010 12:03 PM, anatoly techtonik wrote:
Ah, you can also look at what other packages does - it's a very good
>> way to learn "how to package".
>
> I'm already trying to understand the packaging of trac-bitten - that's
> why these questions.
>
>>> Now I ought to educate myself about autotools, makefiles and all that
>>> low level stuff that I don't really care about when writing in Python.
>>> There are good chances that I won't do this, and as a result won't be
>>> able to help you in maintaining.
>>
>> ahah nice try - f.e. why would you need to "educate" yourself about
>> autotools? it's a non sequitur from b-d vs b-d-i question: care to
>> explain?
>
> Because from Debian Policy I understand that Build-Depends-Indep
> affects some rules in debian/rules. This file is a Makefile. I
> remember that Makefiles in *nix systems were usually produced with
> some kind of autotools.
>
> Even though the policy doesn't explain what Build-Depends-Indep is, it
> says that Build-Depends-Indep should be present for these Makefile
> targets:
> build, build-indep, binary, and binary-indep
>
> But there are no such targets in trac-bitten debian/rules file, so I
> assume that some kind of autotools is used to execute/supply these
> targets when debian/rules is executed. As a Windows Python user, who
> just want to see new Bitten package in Debian to upload the package to
> production server, I can't really go into the gory details of Debian
> toolchains. It already takes more time than I could allow.
I don't mind that beginners in packaging have write access to our repositories,
assuming that they're willing to learn the necessary details during their work
within the team. But as you're neither willing to learn how packaging software
for Debian works, nor you seem to know the necessary basics like makefiles, I've
removed your write access to the Python teams' repositories.
Of course you are still welcome to update packages, please send the according
patches to me and I'll apply them.
- --
Bernd Zeimetz Debian GNU/Linux Developer
http://bzed.de http://www.debian.org
GPG Fingerprint: ECA1 E3F2 8E11 2432 D485 DD95 EB36 171A 6FF9 435F
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQIcBAEBCAAGBQJMxsVBAAoJEOs2Fxpv+UNfS+kP/21iwx2EwtpfiBX2xXwYSWWL
PqcWTBPFKZoZ7AMmGzOLXVQDtPWPZjJ4P826tE+1j7yeZ9BSP6KaMRjjoh9mRgni
9Vp0e0elkE4D0m0fUOHHro5i9wrvzSttotYtyt4C1ZTU+effAzLAZFzsBSDY5dsJ
WyEFW4/G3ezQ3dz6yUkbJM2QOOnLWOnwX4GtMXW54jl2R3shzwezF4dpRObK+n4x
zk68ma5QrZokZEFhcDX/WhRMwCkAa16w1ap6eiP7QProEdwG5eFqo6TtCjeAahHu
9fkiU0NmPn1eJiVKVdgpTQG4rbOzz7hWejuhnzi0L1biZZHdWQj6Eaw59peQIZnd
924ffDQR4QPNaELZSS5XIP5/GASUY89sHp7CVyPFSKNCOBbxs12+cOqcwAIf5J26
u07o+pP/GfqCkfKAOhA7bhLg19S5e/gXgnKZDPG5Qy3Sh1T0mC++B1EtFXNwnVz+
wPwb7QQtV75jQ0fKIn+S5bww7eKT4lE5GH8rPQoSLIK15r2/rNPwiRmOm3hBX/P8
idia4FFeQ9aTVX/rRm8vg6/jdx+QCm7EOZTFGGvmUSY5ZNzdKxr09Y3jwujOMH7y
37Dq5Dhb+f31tO+ZMccF7C+NP7y7EsiUR/U05AOGi4k+7uPeFxiVdAJz59bW44aP
djVepuWmFcY3FOEnv8eg
=7084
-----END PGP SIGNATURE-----
Reply to: