Your Python ctypes wrapper for libarchive is development code, by
definition, if it requires the .so symlink. Either work around the
problem by other means, or accept that there is a dependency on
libarchive-dev.
For background, examine how other packages are doing this:
$ for f in
[Expired for libarchive (Ubuntu) because there has been no activity for
60 days.]
** Changed in: libarchive (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
$ dpkg -c libarchive-dev_3.1.2-7ubuntu2_amd64.deb | grep .so
lrwxrwxrwx root/root 0 2013-12-14 13:51
./usr/lib/x86_64-linux-gnu/libarchive.so - libarchive.so.13.1.2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
And yet, how do you reconcile that with the following from 13.10?
$ ls -l /usr/lib/i386-linux-gnu/libarchive.so*
lrwxrwxrwx 1 root root 20 Feb 9 20:28
/usr/lib/i386-linux-gnu/libarchive.so.13 - libarchive.so.13.1.2
-rw-r--r-- 1 root root 699252 Apr 4 2013
Hello Dustin Oprea!
You're looking at the wrong package. Development files are in the
libarchive-dev package. Please make sure you have it installed if you
want the development files on your system.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
What makes you think that I need development files? I just need the
library. If I have to install the development package to get the library,
then what's the point of the libarchivex package?
Dustin
On Tue, Apr 22, 2014 at 10:07 AM, Andreas Henriksson andr...@fatal.sewrote:
Hello Dustin
On Tue, Apr 22, 2014 at 02:25:13PM -, Dustin Oprea wrote:
What makes you think that I need development files?
The topic of the bug report made me think that.
You said: libarchive.so is not symlinked
This development file is shipped in the development package!
Also you said:
In Ubuntu 12.04
I've never considered the .so to be a development library.
So, when you add a function and move to ABI 14 and the corresponding
.so.14, it's your expected behavior that all current applications will
break?
I don't understand your logic.
Dustin
On Apr 22, 2014 10:55 AM, Andreas Henriksson
Unless you're saying that it'll become 13.1, and 14 will only be introduced
when it's backwards-incompatible with 13.
Dustin
On Apr 22, 2014 11:07 AM, Dustin Oprea myselfasun...@gmail.com wrote:
I've never considered the .so to be a development library.
So, when you add a function and move to
... will have better luck in the other places already mentioned.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1310765
Title:
libarchive.so is not symlinked
To manage notifications about this bug
Hello Dustin Oprea!
This seems to have moved from a bug report to a general discussion on
how so versioning is handled in unix. Please try the ubuntu forums,
ubuntu irc channels or some other form of medium for support. You could
also try reading up on existing documentation available on the web,
And yet you had time for that. I'll assume a yes from the implications
that I cited previously.
Thanks, Andreas.
Dustin
On Apr 22, 2014 11:31 AM, Andreas Henriksson andr...@fatal.se wrote:
... will have better luck in the other places already mentioned.
--
You received this bug notification
I'm finding it very difficult to have software that works in multiple
environment (Mac and Ubuntu), as well as multiple versions of Ubuntu, using
your model. Since each repository generally only provides one version of
*libarchive*, wiring the library to 12 (for Ubuntu 12.04), 13 (for Ubuntu
13 matches
Mail list logo
