The tarball appears to have different contents than the git tree:

- The file is missing entirely

What's left over isn't ideal:

- The README.html file still claims to be json-c
- The README is entirely blank

I'm not excited that the files in our package are still claiming to be
json-c, a completely different source package, nor do they accurately
reflect the contents of the git tree.

The claims:

> IMPORTANT The current API is not stable and will change until version 
> 1.0.0 is reached. We plan to reach it by summer 2016 at latest. With
> 1.0.0, the API will be stable. Until then, everything may change. Of
> course, we will not deliberatly break things but we need freedom to
> restructure.

I'm worried that we're about to start a five year support release and
include a new-to-us library that is apparently not stabilized. I don't
know if we should be comforted by the fact that it's had no development 
work for five months or worried that it's had no development for five 

It feels like no one's closely inspected this package yet.

I realize it's really late in the cycle to ask the question, but should 
rsyslog and dependencies be moved to universe? We recently enabled the 
systemd persistent journal, and we at one point intended to use the 
systemd-journal-remote package: 1488341.

I'll give the rest of the code in this package a fair shot, but I wanted 
to raise the possibility of a different path entirely just for 


You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

  [MIR] libfastjson

To manage notifications about this bug go to:

ubuntu-bugs mailing list

Reply via email to