Don't force Python 2.6

Bug #690555 reported by Martin Pitt on 2010-12-15
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
libindicate
Fix Committed
Undecided
Unassigned
libindicate (Ubuntu)
High
Martin Pitt

Bug Description

bindings/python/Makefile.am:_indicate_la_LDFLAGS = -module -avoid-version -export-symbols-regex init_indicate -lpyglib-2.0-python2.6 -lpython2.6

This is both bad style (you should use pkgconfig), as well as causes an extra "libpython2.6" dependency in our packages; that keeps python2.6 on our CDs, although we moved to Python 2.7 now.

Related branches

Martin Pitt (pitti) wrote :

Also, _LDFLAGS is a bad place to put libraries, they should go into _LIBADD. Attached branch/merge proposal use proper build-time detection instead.

Changed in libindicate:
status: New → Fix Committed
Changed in libindicate (Ubuntu):
assignee: nobody → Martin Pitt (pitti)
Changed in libindicate:
status: Fix Committed → In Progress
Martin Pitt (pitti) on 2010-12-15
Changed in libindicate (Ubuntu):
status: New → Fix Committed
importance: Undecided → High
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package libindicate - 0.4.4-0ubuntu7

---------------
libindicate (0.4.4-0ubuntu7) natty; urgency=low

  * debian/control: Fix Vcs-Bzr: to point to correct branch.
  * Add 04_python_linking.patch: Don't hardcode linking with Python 2.6, get
    the libraries dynamically instead. (LP: #690555)
  * debian/control: Drop support for Python 2.6, so that we don't pull in the
    entire python2.6 package just because of this.
 -- Martin Pitt <email address hidden> Wed, 15 Dec 2010 12:47:08 +0100

Changed in libindicate (Ubuntu):
status: Fix Committed → Fix Released
Ted Gould (ted) on 2011-01-07
Changed in libindicate:
status: In Progress → Fix Committed
milestone: none → 0.4.5
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers