On Mon, Feb 25, 2008 at 02:14:54PM -0800, Mike Sullivan wrote: > Nicolas Williams wrote: > > >Hmmm, I don't quite buy it. SFW components are a lot more discrete than > >ON components. And many will install library and executable content > >both. > > Like I said, that can happen in ON too - it's just that it's easier to > make people split their code between lib and cmd in such cases, and it's > not easy or friendly to have folks in sfw split that code up. But > it still can be a useful split, or at least useful enough it's not worth > changing to me.
I guess it can happen in ON, but I think it's unlikely -- we've taken major pains to avoid this for, e.g., krb5, ssh, and other things in ON of external procedence. But I've moved it to $SRC/lib/sqlite3, and I've generated a new webrev: http://cr.opensolaris.org/~nico/webrev-sqlite3-sfw-2nd/ (which includes the tar.gz and zip archives too) BTW, my approach to reducing symbol scope for libsqlite3 causes warnings to be issued by ld(1) when linking with libsqlite3, so I may do without symbol scope reduction for now. First I'll talk to the linker folks though. (The warning is about having local symbols in the global symbol table. The warning is plainly harmless, and, IMO, shouldn't be issued _at all_ -- otherwise elfedit(1)ing objects loses value. Nico --
