On Thursday 23 March 2006 21:35, tvali wrote:
>
> BINSLOT is a new word for me.
Ok BINSLOT is normally slot. However in some cases packages are in the
same slot, but not binary compatible (like their libraries having a
different SONAME e.g. openssl-0.9.6 and 0.9.7 (iirc)).
>
> I dont see any me
On Thursday 23 March 2006 21:38, Gustavo Sverzut Barbieri wrote:
> Ok... this discussion is missing my initial point that is how to
> provide binary dependency and avoid many crashes we have now with
> almost no effort.
>
> My initial proposal was to, after compile and before install is done,
> we
On 24/03/06, Paul de Vrieze <[EMAIL PROTECTED]> wrote:
> On Thursday 23 March 2006 21:35, tvali wrote:
> >
> > BINSLOT is a new word for me.
>
> Ok BINSLOT is normally slot. However in some cases packages are in the
> same slot, but not binary compatible (like their libraries having a
> different S
On 24/03/06, Paul de Vrieze <[EMAIL PROTECTED]> wrote:
> On Thursday 23 March 2006 21:38, Gustavo Sverzut Barbieri wrote:
> > Cons:
> > - it's not the final solution to the problem, as said, interfaces
> > would be better... but interfaces would demand much more effort and
> > not being automatica
On Fri, Mar 24, 2006 at 01:40:01PM +0200, tvali wrote:
> On 24/03/06, Paul de Vrieze <[EMAIL PROTECTED]> wrote:
> > On Thursday 23 March 2006 21:38, Gustavo Sverzut Barbieri wrote:
> > > Cons:
> > > - it's not the final solution to the problem, as said, interfaces
> > > would be better... but inte
On 24/03/06, Brian Harring <[EMAIL PROTECTED]> wrote:
> Checking the interfaces/symbols sucks however, because you can only do
> it _after_ you've built whatever you're building (packages do adjust
> the defines/typedefs/structs dependant on configure/build options).
>
> As I stated earlier, bincom
On Friday 24 March 2006 12:33, tvali wrote:
>
> I meant headers as .h or .hpp files, which contain function headers.
> They're needed, but they are in many cases, included in pack which
> uses them, even if that means putting some .h's into all libs.
Headers are in the linux/unix world normally no
On 24/03/06, Paul de Vrieze <[EMAIL PROTECTED]> wrote:
...
is there any good text about sonames and other unix-specific things i
should know about headers and including?
>
> Paul
>
> ps.
>
> > Theory is when you know something, but it doesn't work. Practice is
> > when something works, but you do
On Friday 24 March 2006 12:40, tvali wrote:
>
> Interface can be made somewhat automatically checkable.
>
> For example:
> void a(int);
> void b(int, int);
> void b(int, char);
>
> Is compatible with:
> void a(int);
> void b(int, int);
>
Unfortunately, your wrong. This only makes sure that you have
On Friday 24 March 2006 13:10, Brian Harring wrote:
> As I stated earlier, bincompat (not binslot paul :P) is the route to
If you want to call it bincompat, I'd have to insist to make it
BINCOMPAT ;-).
> go- it gives you up front information so a resolver can plan out what
> has to be rebuilt au
On 24/03/06, Paul de Vrieze <[EMAIL PROTECTED]> wrote:
> On Friday 24 March 2006 12:40, tvali wrote:
> >
> > Interface can be made somewhat automatically checkable.
> >
> > For example:
> > void a(int);
> > void b(int, int);
> > void b(int, char);
> >
> > Is compatible with:
> > void a(int);
> > vo
On 24/03/06, tvali <[EMAIL PROTECTED]> wrote:
> On 24/03/06, Paul de Vrieze <[EMAIL PROTECTED]> wrote:
> > On Friday 24 March 2006 12:40, tvali wrote:
> > Perhaps you should read up your knowledge of the C language. After you
> > found that the C language is a mess, try C++, it makes things worse.
12 matches
Mail list logo
