Re: Library package naming

[Roger Leigh <rl117@york.ac.uk>]

Junichi Uekawa <dancer@netfort.gr.jp> writes:

> Roger Leigh <rl117@york.ac.uk> immo vero scripsit:
> 
> > Would the following scheme be acceptable to you?:
> > 
> > Package: libijs-0.34
> > contains libijs-0.34.so
> 
> In my little testing, if I build a library with 
> -export-dynamic -version-info 0:0:0 -release 1.0.1 
> I get:
> 
> $ ls -1 .libs/
> libdshconfig-1.0.1.so.0
> libdshconfig-1.0.1.so.0.0.0
> libdshconfig.a
> libdshconfig.la
> libdshconfig.so
> 
> 
> With no -version-info:
> 
> libdshconfig-1.0.1.so
> libdshconfig.a
> libdshconfig.la
> libdshconfig.lai
> libdshconfig.so
> 
> 
> Would those examples help ?
> If it does, I'll add this example to libpkg-guide.

Yes, thanks.  I'm happy with the libtool versioning.  I think I'll
just use -release like glibc, since the -version-info data will be
redundant in IJS.

I think it would make a good addition to the guide, to explictly show
what goes in which package.  Will libpkg-guide be packaged, or become
part of Debian Policy?

> > Package: libijs-0.34-dev
> > Provides: libijs-dev
> > Conflicts: libijs-dev
> > contains libijs.a and ijs-config
> > 
> > This will allow versioned Build-Depends.  If there are regular
> > releases, then the numbers of conflicts in the -dev package will get
> > quite long.  Should I keep them indefinitely?
> 
> Why? The only one required is 
> Conflicts: libijs-dev.

Thanks, I can see that now!

Thanks for your help,
Roger

-- 
Roger Leigh
                ** Registration Number: 151826, http://counter.li.org **
                Need Epson Stylus Utilities? http://gimp-print.sourceforge.net/
                GPG Public Key: 0x25BFB848 available on public keyservers


-- 
To UNSUBSCRIBE, email to debian-mentors-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org