[openbeosnetteam] Re: libnet fix

> guys, at the risk of suggesting something useful, have you considered 
> using a different name than 'libnet.so' for your target lib? 

Yep, I think it should be a good idea in our current state.
Creating a symlink to lie to Net+ for example to test his 
binary compatibility will be easy enough...

> I had this 
> conversation with David Reid over a year ago and made the same 
> suggestion, but he didn't feel like it was a big issue. But from my 
> point of view, trying to actively develop a lib with the SAME NAME 
> and 
> the EXACT SAME SET OF EXPORTED SYMBOLS as a standard existing lib 
> (and 
> being loaded from the same set of standard search paths) is just 
> asking 
> for brain frying troubles.

Agreed.

> Why not use 'libobosnet.so'? Or something distinctive. You can *
> always*
>  change it to the standard name later, once the thing has matured, 
> and 
> test against that. In the mean time, sanity is preserved. Is this 
> absolutely necessary? No. But isn't it worth keeping things straight 
> and not spending hours (days) tracking down non-existent problems 
> because of linking against the wrong lib?
> 
> Just a kooky suggestion.

I'll update the libnet.so Jamfile, as soon as SF CVS is up again...
 
-Philippe

--
Fortune Cookie Says:

Mencken and Nathan's Sixteenth Law of The Average American:
        Milking a cow is an operation demanding a special talent that
is possessed only by yokels, and no person born in a large city can
never hope to acquire it.

Other related posts: