[Build-common-hackers] Bug#374012: cdbs:
$(cdbs_python_current_version) should always be set
Peter Eisentraut
petere at debian.org
Fri Jun 16 21:11:29 UTC 2006
Marc Dequènes wrote:
> Package: cdbs
> Version: 0.4.41
> Severity: important
Certainly, this doesn't have a "major impact on the usability" of this
package?
> The class is using this variable to fill the
> cdbs_python_build_versions variable for modules (archall packages). I
> thought it would naver be used in extensions, but doko made me
> discover i was wrong. In python-crypto, he needs this variable to
> build the documentation.
>
> Here is an example of a rule which should work:
>
> MKHOWTO =
> /usr/lib/python$(cdbs_python_current_version)/doc/tools/mkhowto
>
> common-build-arch::
> cd Doc && $(MKHOWTO) --ps
Offhand, it seems kind of silly that a Python package needs to ask cdbs
for the current Python version. Perhaps it would make more sense if
the unversioned "python" package provides a link to the current
version? Something like
/usr/lib/python/doc/tools/ -> /usr/lib/python2.4/doc/tools/
or even
/usr/lib/python/ -> /usr/lib/python2.4/
I'm not against this change, but it seems to attack the problem from the
wrong end.
More information about the Build-common-hackers
mailing list