FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian Development

 
 
LinkBack Thread Tools
 
Old 04-14-2008, 06:14 PM
Bradley Smith
 
Default Plib, shared libraries issue.

Hi,

I'm currently in the process of adopting plib and would like some
advice regrading it's shared/static libraries.

Upstream, plib is built as a set of static libraries due to the nature
of it's use, i.e. a set of helper libraries that programs will only use
part of. The Debian package currently has shared libraries that have
been 'hacked' on top, (#475331 and #470503 are relevant to this).

Currently I have fixed the way this has been done by patching the
build system, so that shared libraries are produced properly.

But this presents two questions:

1. Should these shared libraries be built, or should it just stick to
static libraries as upstream intended?

2. If shared libraries /are/ built, should they all be in one package
(there are 13 libraries in total), or should they be separated, and
also what should be done about the sonames of the libraries and the
name of the package(s)?

(I have CC'd this to the maintainers of the packages that currently
rdepend on plib, namely simgear, supertuxcart, stormbaancoureur,
fgfs-atlas, flightgear and torcs. Any feedback from you would be much
appreciated)

Thanks in advance,
Bradley Smith
 
Old 04-15-2008, 12:36 PM
Ove Kaaven
 
Default Plib, shared libraries issue.

Bradley Smith skrev:

1. Should these shared libraries be built, or should it just stick to
static libraries as upstream intended?


There are advantages and disadvantages with either... I don't really
have a strong opinion myself (as long as the result works). But if I had
to choose, I'd probably say static-only, if upstream relations and ease
of package maintenance matter. It might also result in leaner, meaner,
and 0.1% (or something) faster games.



2. If shared libraries /are/ built, should they all be in one package
(there are 13 libraries in total), or should they be separated, and
also what should be done about the sonames of the libraries and the
name of the package(s)?


In my opinion, one package is fine.



--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 04-15-2008, 06:15 PM
Mike Hommey
 
Default Plib, shared libraries issue.

On Tue, Apr 15, 2008 at 02:36:17PM +0200, Ove Kaaven wrote:
> Bradley Smith skrev:
>> 1. Should these shared libraries be built, or should it just stick to
>> static libraries as upstream intended?
>
> There are advantages and disadvantages with either... I don't really
> have a strong opinion myself (as long as the result works). But if I had
> to choose, I'd probably say static-only, if upstream relations and ease
> of package maintenance matter. It might also result in leaner, meaner,
> and 0.1% (or something) faster games.

And then you need to rebuild all reverse dependencies when there is a
security fix for the static library.

Mike


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 04-15-2008, 07:33 PM
Ove Kaaven
 
Default Plib, shared libraries issue.

Mike Hommey skrev:

On Tue, Apr 15, 2008 at 02:36:17PM +0200, Ove Kaaven wrote:

Bradley Smith skrev:

1. Should these shared libraries be built, or should it just stick to
static libraries as upstream intended?
There are advantages and disadvantages with either... I don't really
have a strong opinion myself (as long as the result works). But if I had
to choose, I'd probably say static-only, if upstream relations and ease
of package maintenance matter. It might also result in leaner, meaner,
and 0.1% (or something) faster games.


And then you need to rebuild all reverse dependencies when there is a
security fix for the static library.


In plib? That'd be almost like worrying about security issues in
fortunes-mod, IMO. But sure, if you want to be paranoid... and it's not
my call, I don't really care.




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

Thread Tools




All times are GMT. The time now is 01:13 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org