[Pkg-xfce-devel] libthunar package name

Yves-Alexis Perez corsac at corsac.net
Wed Mar 8 08:02:52 UTC 2006

On Wed, 2006-03-08 at 09:16 +0200, Jani Monoses wrote:
>         I've commited to svn changes that reflect this proposal, as
>         I'm ratter
>         ok that having only "libthunar-vfs" in the name can be
>         confusing. I've 
>         also bumped the so version in package name.
> I did not actually say that libthunar-vfs in the name is confusing :)
> So the change should just be libthunar-vfs-1-2 from current
> libthunar-vfs-1

Hmh, yes, it was a personal initiative :p
> Upstream library names are libthunar-vfs-1 and libthunarx-1,
> presumably because
> they are part of the thunar 1.0 API. So the 1 here is part of the name
> not the
> library soname. Just like with libbind9-0 where 9 is the upstream
> version but 0 is the soname. 
> I couldn't find a better example :)

Hmh yes you're right, so at least libthunar1-2 / libthunar1-dev
> Now for debian packaging we need to append the soname to the package
> name so we
> can have multiple versions of the lib installed if we wish, even if
> that's not a good idea
> now since libthunar is not in wide use to need older libs for legacy
> apps.
> So right now the pkg name change only keeps lintian happy. But indeed
> also makes
> depends in packages easier. Instead of depending on libthunar-vfs-1
> (>= 02.2+svnXXXX)
> you can just dep on libthunar-vfs-1-2 if you want to make sure you get
> the right library with
> the right soname.

*if* they bump the soname between each release, right ?
> As for thunarx when (if) it starts diverging from vfs regarding
> sonames we can spilt it 
> to libthunarx-1-soname and libthunarx-1-dev. Another reason to do this
> is if apps start
> to appear that would provide thunar plugins but which do not mess with
> vfs, but need
> the plugin API. For instance new xfdesktop now uses thunarx at least
> it builds against it 
> but it is ok even if it comes from a separate package as the pkg is
> small.

If current xfdesktop svn is using thunarx but not thunarvfs i'd prefer
splitting now so we don't have to do it when we start packaging 4.4
> So it would be better imho to stick with upstream library names in our
> package names
> or else we'll need to do a conflicts and such if we want to revert the
> change. 

Yes, I'm ok.

> Jani
> PS: also libgamin-dev and libhal-storage-dev are needed as depends of
> libthunar-vfs-1-dev

ok, thank you.

huggie, ema, (and others), what are you thinking of splitting
libthunar-vfs-1 in libthunar-vfs-1-2/-dev and libthunar-x-1-2/-dev ?
Yves-Alexis Perez

More information about the Pkg-xfce-devel mailing list