Hi Benda,
Benda Xu writes:
> I am packaging a library called "casacore" which provides
>
> libcasa_python3.so.2 and libcasa_python.so.2
>
> with SONAME=2.
>
> How should them be named when the python major version and SONAME could
> cause confusion?
Since noone had a good idea here, I would pr
On 2016-05-11 22:13, Ole Streicher wrote:
> Christian Kastner writes:
>> On 2016-05-11 03:41, Benda Xu wrote:
>>> I am packaging a library called "casacore" which provides
>>> libcasa_python3.so.2 and libcasa_python.so.2
>>> with SONAME=2.
>>> How should them be named when the python major versi
Christian Kastner writes:
> On 2016-05-11 03:41, Benda Xu wrote:
>> I am packaging a library called "casacore" which provides
>> libcasa_python3.so.2 and libcasa_python.so.2
>> with SONAME=2.
>> How should them be named when the python major version and SONAME could
>> cause confusion?
> Accord
On 2016-05-11 03:41, Benda Xu wrote:
> Hi,
>
> I am packaging a library called "casacore" which provides
>
> libcasa_python3.so.2 and libcasa_python.so.2
>
> with SONAME=2.
>
> How should them be named when the python major version and SONAME could
> cause confusion?
>
> I can think of
>
>
Nico Schlömer writes:
> i.e., libraries with some number appended. What's the meaning of that
> number?
Hello Nico!
Those packages are shared libraries, and the number represents the
SOVERSION. Whenever the ABI of the shared library changes, the new
version should be in a binary package that ha
* Nico Schlömer , 2015-09-07, 20:46:
In Debian, I find packages such as
```
libzeep3.0
libzdb9
libzim0
```
i.e., libraries with some number appended. What's the meaning of that
number?
This is explained in Policy §8.1:
Normally, the run-time shared library and its ‘SONAME’ symlink should be
Thank you Julian for that complete summary. I can't think of any other
questions or scenarios to ask about.
Regards,
--
-- Grant Bowman <[EMAIL PROTECTED]>
* Julian Gilbey <[EMAIL PROTECTED]> [011128 16:06]:
> (1) libdb: Shared library packages have the major
Thank you Julian for that complete summary. I can't think of any other
questions or scenarios to ask about.
Regards,
--
-- Grant Bowman <[EMAIL PROTECTED]>
* Julian Gilbey <[EMAIL PROTECTED]> [011128 16:06]:
> (1) libdb: Shared library packages have the majo
On Wed, Nov 28, 2001 at 11:50:11AM -0800, Grant Bowman wrote:
> Hello,
>
> I have seen packages change their package names to include a version
> number. Reading the policy, there is little guidance on this subject.
> It would seem that's what Epochs are designed for. However I am aware
> there
On Wed, Nov 28, 2001 at 11:50:11AM -0800, Grant Bowman wrote:
> Hello,
>
> I have seen packages change their package names to include a version
> number. Reading the policy, there is little guidance on this subject.
> It would seem that's what Epochs are designed for. However I am aware
> ther
On Tue, Jul 03, 2001 at 11:37:33AM +0200, peter karlsson wrote:
> Can a single binary package have a different name than the source package
> it comes from?
Yes, it can.
> I am packaging the LysKOM tty-client, which has the upstream name
> tty-client, but I have received requests for renaming the
On Tue, Jul 03, 2001 at 11:37:33AM +0200, peter karlsson wrote:
> Can a single binary package have a different name than the source package
> it comes from?
Yes, it can.
> I am packaging the LysKOM tty-client, which has the upstream name
> tty-client, but I have received requests for renaming th
On Thu, 15 Feb 2001, Ingo Saitz wrote:
> MoiN
>
> On Mon, Feb 12, 2001 at 04:30:32PM +0100, Ove Kaaven wrote:
> > Are there any docs with guidelines on package naming?
>
> See the packaging manual, Section 11.3.
There's no such section in the packaging manual. But maybe you're
referring to pol
On Thu, 15 Feb 2001, Ingo Saitz wrote:
> MoiN
>
> On Mon, Feb 12, 2001 at 04:30:32PM +0100, Ove Kaaven wrote:
> > Are there any docs with guidelines on package naming?
>
> See the packaging manual, Section 11.3.
There's no such section in the packaging manual. But maybe you're
referring to po
MoiN
On Mon, Feb 12, 2001 at 04:30:32PM +0100, Ove Kaaven wrote:
> Are there any docs with guidelines on package naming?
See the packaging manual, Section 11.3.
> The build process gives me
> libmk4.so.0.0.0, libmk4tcl.so.0.0.0, and optionally libmk4py.so.0.0.0
So your package should be called
MoiN
On Mon, Feb 12, 2001 at 04:30:32PM +0100, Ove Kaaven wrote:
> Are there any docs with guidelines on package naming?
See the packaging manual, Section 11.3.
> The build process gives me
> libmk4.so.0.0.0, libmk4tcl.so.0.0.0, and optionally libmk4py.so.0.0.0
So your package should be called
On Mon, Feb 12, 2001 at 04:21:00PM -0800, Mike Markley wrote:
> IMO the best name is the one that does the best job of expressing what it's
> called without being so generic as to cause potential name conflict. I'd
> personally go with libmetakit, with -dev, -tcl, -python if you split it up.
> In g
On Mon, Feb 12, 2001 at 04:21:00PM -0800, Mike Markley wrote:
> IMO the best name is the one that does the best job of expressing what it's
> called without being so generic as to cause potential name conflict. I'd
> personally go with libmetakit, with -dev, -tcl, -python if you split it up.
> In
IMO the best name is the one that does the best job of expressing what it's
called without being so generic as to cause potential name conflict. I'd
personally go with libmetakit, with -dev, -tcl, -python if you split it up.
In general the version number isn't in the package name unless there's som
IMO the best name is the one that does the best job of expressing what it's
called without being so generic as to cause potential name conflict. I'd
personally go with libmetakit, with -dev, -tcl, -python if you split it up.
In general the version number isn't in the package name unless there's so
20 matches
Mail list logo
