On Mon, Feb 26, 2007, Josselin Mouette wrote: > > I've just noticed that it erases *.a and *.la built for multiple Python > > versions into a single one, so it's at least important and I think it's > > serious if anybody is relying on these *.a and *.la files. > Surely not. If they are erased, it's because they are exactly the same > across multiple python versions. They are then linked back in all > destination directories.
They are not, the *.la file has: libdir='/usr/lib/python2.4/site-packages/gtk-2.0' And the *.a file has the python2.4 string in it. But I was incorrect in saying that it "erases *.a and *.la built for multiple Python versions into a single one", there's simply only one version of Python for which python-vte is built, hence "all versions" are identical, but they would differ for different python versions. I suppose this makes the problem more closer to being: "non-predictable location depending on the number of python versions for which the package is built" (versus incorrect /contents/, which was incorrect) > It's easy to add an exception for these files, but I think the > appropriate thing to do is to remove them entirely. They are just a side > effect of using libtool and I fail to see for what purpose they could be > useful. Certainly these are not useful in the common case, but I'm almost sure some far-fetched cases could warrant them; it's likely we don't want to support these cases in Debian anyway. -- Loïc Minier <[EMAIL PROTECTED]>
