Dear Boyuan, Dmitry, On Thu, Sep 08, 2016 at 12:52:29PM +0300, Dmitry Ivanov wrote: > I am the upstream developer of QEverCloud library. Sorry for the > interference, I'd just like to clarify a bit what QEverCloudGenerator > is and how it is intended to work. Please don't apologise -- there's a reason Debian has these discussions in public. Thank you for your very valuable input. (I won't CC you after this message, so if you want to follow subsequent discussion please subscribe to the Debian bug report.) On Thu, Sep 08, 2016 at 06:36:48AM +0800, Boyuan Yang wrote: > He just told me it is not possible, since the generator needs to be > updated. Update in Evernote thrift files will simply leads to FTBFS > without the update in the generator. > [...] > Take a look at Evernote official SDK) and the backward compatibility > of the API. Not updating API will not cause problems, ^^ This is the most important part of your message. If an Evernote API change would cause qevercloud to become useless, it would make sense to package the Thrift IDL files separately. When those were updated, qevercloud would FTBFS, and that would be a good thing because it would alert us that the package was broken. However, as you say, it turns out that the Evernote API is backwards compatible. Even if qevercloud lagged behind other Debian packages using the Thrift IDL, we would want to keep qevercloud in Debian alongside those other packages, becauae QEverCloud would remain useful. So, in conclusion, it's okay to have multiple copies of the Thrift IDL files in the archive. > > I had some discussions to the current maintainer of QEverCloud about > > the possibility of updating thrift IDL files and regenerate again. > > https://github.com/d1vanov/QEverCloud/issues/5 In that GitHub thread, there is mention of a parsing tool called 'lemon'. Dmitry suggests packaging that separately, but you say it's not necessary. Could you explain why? Where can I find out about that tool? Please don't be afraid of increasing the number of packages in Debian. One of Debian's strengths, compared to other distributions, is binary package granularity. This is good for both package maintainers and users, for all sorts of reasons. > Are we talking about the same package? :p > > I ran `apt-get source ebib' and got ebib v4.5.2. The debian/rules is > nothing more > than one line of `dh $@ --parallel --with elpa'. Are you sure? There has never been ebib version 4.5.2. The version I meant was 2.6.3-1 in unstable. Try `debcheckout ebib`. * * * To summarise our discussion so far: - qevercloudgenerator should not be packaged separately because it is not useful for anything other than building qevercloud. - the source package containing qevercloudgenerator should embed a copy of the latest Thrift IDL that it is compatible with - ideally qevercloudgenerator will be run during the qevercloud package build, though a promise that it can be run is sufficient for the ftpmasters - status of lemon parser currently unclear Please let me know if I've misunderstood anything in writing this summary, and thanks again for the work you've both done. -- Sean Whitton
Attachment:
signature.asc
Description: PGP signature