Hi! On Jan 4, 2012, at 1:46 PM, BJ Dierkes wrote:
> As discussed in #drizzle, having errors print to stderr rather than /dev/null > is fine, for now, but ideally should be removed before GA. I believe we have syslog now by default. Before we fork I believe sending critical errors to stderr makes sense, after we fork,... well the daemon should have stdout/stderr closed (I believe). If they are closed, syslog is a good default. >> http://bazaar.launchpad.net/~drizzle-trunk/drizzle/development/revision/2465 >> > > Right on… I think I was unclear as well. I thought that libdrizzle.so.* is > the current libdrizzle, where libdrizzle-1.0* is for backward compat and > should be packaged separately. Might need clarification from krow on that. Should we publish both libdrizzle and libdrizzle-1.0? I am of two minds about this. I believe that creating sensible defaults, like libdrizzle.so is a good idea. I also like giving developers an easy way to protect themselves when it comes to versioning. The basic mechanisms of .so should handle versioning, but my experience is that they don't. > Currently, I think Fedora and RHEL 6 should be the only primary focus for RPM > distros… once we get that squared away, and consistently building every > release… then can work toward fixing EL5 if we want to (I personally don't > care to support anything less than RHEL 6). I completely agree. Cheers, -Brian
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
