Re: Package Names Containing Versions

[Goswin von Brederlow <goswin-v-b@web.de>]

Chris Baines <cbaines8@gmail.com> writes:

> 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.
>
> Chris
>
> 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.
>> 
>> Thanks,
>> 
>> Chris

But then you have to fix the package so it can be installed alongside
another version. Otherwise having different names is pointless.

MfG
        Goswin