On Tue, 19 Jun 2012 08:39:40 -0700, Adam Williamson wrote:
> > And again, this is not the full story.
>
> I was trying to keep it simple.
The simplified case/explanation is what encourages packagers to misplace
.so files. For example, -devel packages that contain .so files but no
header files s
On Tue, 2012-06-19 at 09:50 +0200, Michael Schwendt wrote:
> On Mon, 18 Jun 2012 12:25:12 -0700, Adam Williamson wrote:
>
> > On Mon, 2012-06-18 at 18:23 +0100, Nelson Marques wrote:
> > > Hi all,
> > >
> > >
> > > I have a doubt re
On Mon, 18 Jun 2012 12:25:12 -0700, Adam Williamson wrote:
> On Mon, 2012-06-18 at 18:23 +0100, Nelson Marques wrote:
> > Hi all,
> >
> >
> > I have a doubt regarding the '.so's' in devel packages... From my
> > understanding they go in devel p
Adam,
Thanks, this helps a lot understanding a bit more around shared libraries;
NM
2012/6/18 Adam Williamson
> On Mon, 2012-06-18 at 18:23 +0100, Nelson Marques wrote:
>> Hi all,
>>
>>
>> I have a doubt regarding the '.so's' in devel packages...
On Mon, 2012-06-18 at 18:23 +0100, Nelson Marques wrote:
> Hi all,
>
>
> I have a doubt regarding the '.so's' in devel packages... From my
> understanding they go in devel packages to allow the installation of
> several packages with different versioning
On Mon, 18 Jun 2012 18:23:16 +0100, Nelson Marques wrote:
> Hi all,
>
>
> I have a doubt regarding the '.so's' in devel packages... From my
> understanding they go in devel packages to allow the installation of
> several packages with different versioning
&g
Hi all,
I have a doubt regarding the '.so's' in devel packages... From my
understanding they go in devel packages to allow the installation of
several packages with different versioning
Who defined this? Is this part of some standards (ex: LSB, etc) ?
Is there some writte
