Re: Package Names Containing Versions
- To: email@example.com
- Subject: Re: Package Names Containing Versions
- From: Chris Baines <firstname.lastname@example.org>
- Date: Thu, 29 Jul 2010 17:32:18 +0100
- Message-id: <1280421138.10526.3.camel@chris-debian-desktop>
- In-reply-to: <1280414766.2745.41.camel@chris-debian-desktop>
- References: <1280414766.2745.41.camel@chris-debian-desktop>
Sorry, replying to my own message, I have just stumbled upon the Debian
Shared Library Packaging guide
(http://www.netfort.gr.jp/~dancer/column/libpkg-guide/libpkg-guide.html#naminglibpkg ). Which explains the solution to my problem.
On Thu, 2010-07-29 at 15:46 +0100, Chris Baines wrote:
> Hello Mentors,
> I am looking at releasing the next upstream version of simgear as this
> is holding back both one of my upcoming packages (fgrun) and the
> upgrading of the FlightGear program.
> The source package (old) currently produces two binary packages
> simgear1.9.1 and simgear-dev. I am wondering why the former package is
> named simgear1.9.1 and not just simgear as 1.9.1 is the version?
> Initially I thought it was because is allows it to be installed
> alongside another version of the package but this is not possible as it
> conflicts with all other versions of simgear.