Bumped versions of *nix* and *syslog* dependencies. #1
Conversation
No compatibility issues found.
|
Thanks!
… On 10 Feb 2017, at 03:46, Dawid Ciężarkiewicz ***@***.***> wrote:
Merged #1 <#1>.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#1 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAEF3K0HQo89eR33HpLyNjrccfdca4pTks5ra92kgaJpZM4L89vc>.
|
|
Thank you. :) |
|
(In case anyone is reading this, I found it was necessary because nix 0.6 has a bug where it doesn’t build on FreeBSD.)
… On 10 Feb 2017, at 03:47, Dawid Ciężarkiewicz ***@***.***> wrote:
Thank you. :)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#1 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAEF3EJ_N4vgzqv3FRBfA6i1ltsQVcPIks5ra93igaJpZM4L89vc>.
|
|
I have published 0.8.2 and yanked all the 1.0.0-alpha versions. There was too much trouble with them, and this crate is not 1.0.0 ready. |
|
Fair enough. Hopefully 1.0 before too long though. :) |
|
The thing is - there's noone with real syslog logging requirements to drive the development of it. I just wrote it as a glue between slog and syslog crate, just as a PoC. For |
|
Fair enough. I use it in my project, but I don’t need many advanced features. What’s left unimplemented right now, or buggy?
… On 18 Feb 2017, at 22:24, Dawid Ciężarkiewicz ***@***.***> wrote:
The thing is - there's noone with real syslog logging requirements to drive the development of it. I just wrote it as a glue between slog and syslog crate, just as a PoC. For journald someone just wrote and submit it to scratch their own itch.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#1 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAEF3JiTSAeqzix7I5IU8zf-djipk2_dks5rd2-KgaJpZM4L89vc>.
|
|
The answer is: I don't even know what's left or buggy. :) . It's tiny so I don't expect there are bugs but who knows. :) As long as it works for you, I wouldn't worry too much about it. As long as you pin it to current 0.x version it will keep working. :) The biggest problem with making something 1.0.0 is that you're supposed to keep the API backward compatibilie as long as you don't bump the major version. So if the API is undecided, and you might need to tweek it to accomodate features you didn't know about, you might end up with |
…te' into 'ebee/master' slog-rs#1 - Resolve "Allow setting custom process name for slog-syslog crate" See merge request ebee_smart/third-party/syslog-rust!2
No compatibility issues found.