I am packaging the nemiver debugger, which has a new version that has
split some of its functionality into a libnemiver-common library. The
library is probably not very useful without nemiver itself being installed.
Is it ok to avoid splitting out a separate libnemiver-common0 package, and
On Mon, February 19, 2007 1:38 pm, Sam Morris wrote:
I am packaging the nemiver debugger, which has a new version that has
split some of its functionality into a libnemiver-common library. The
library is probably not very useful without nemiver itself being
installed.
Is it ok to avoid
On Mon, 19 Feb 2007 14:10:06 +, Paul Cager wrote:
On Mon, February 19, 2007 1:38 pm, Sam Morris wrote:
I am packaging the nemiver debugger, which has a new version that has
split some of its functionality into a libnemiver-common library. The
library is probably not very useful without
On Mon, Feb 19, 2007 at 02:10:06PM -, Paul Cager wrote:
On Mon, February 19, 2007 1:38 pm, Sam Morris wrote:
I am packaging the nemiver debugger, which has a new version that has
split some of its functionality into a libnemiver-common library. The
library is probably not very useful
Sam Morris wrote:
On Mon, 2007-02-19 at 18:11 +, Paul Cager wrote:
On Mon, February 19, 2007 2:37 pm, Sam Morris wrote:
On Mon, 19 Feb 2007 14:10:06 +, Paul Cager wrote:
On Mon, February 19, 2007 1:38 pm, Sam Morris wrote:
I am packaging the nemiver debugger, which has a new version
On (19/02/07 14:37), Sam Morris wrote:
On Mon, 19 Feb 2007 14:10:06 +, Paul Cager wrote:
On Mon, February 19, 2007 1:38 pm, Sam Morris wrote:
I am packaging the nemiver debugger, which has a new version that has
split some of its functionality into a libnemiver-common library. The
On Mon, Feb 19, 2007 at 12:48:21PM -0800, Steve Langasek wrote:
On Mon, Feb 19, 2007 at 02:10:06PM -, Paul Cager wrote:
On Mon, February 19, 2007 1:38 pm, Sam Morris wrote:
I am packaging the nemiver debugger, which has a new version that has
split some of its functionality into a
On Mon, Feb 19, 2007 at 07:36:13PM -0500, Justin Pryzby wrote:
On Mon, Feb 19, 2007 at 12:48:21PM -0800, Steve Langasek wrote:
On Mon, Feb 19, 2007 at 02:10:06PM -, Paul Cager wrote:
On Mon, February 19, 2007 1:38 pm, Sam Morris wrote:
I am packaging the nemiver debugger, which has a
Justin Pryzby [EMAIL PROTECTED] writes:
On Mon, Feb 19, 2007 at 12:48:21PM -0800, Steve Langasek wrote:
No, you should *not* put libraries into subdirectories of /usr/lib
unnecessarily.
Policy prefers it for this case:
10.2:
| Shared object files (often .so files) that are not public
On Mon, Feb 19, 2007 at 05:03:47PM -0800, Russ Allbery wrote:
Justin Pryzby [EMAIL PROTECTED] writes:
On Mon, Feb 19, 2007 at 12:48:21PM -0800, Steve Langasek wrote:
No, you should *not* put libraries into subdirectories of /usr/lib
unnecessarily.
Policy prefers it for this case:
Justin Pryzby [EMAIL PROTECTED] writes:
On Mon, Feb 19, 2007 at 05:03:47PM -0800, Russ Allbery wrote:
Yes, installing the libraries in /usr/lib.
For such packages with libraries without sonames, one should just make
something up?
If the library is not suitable to being treated like a
11 matches
Mail list logo
