[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#836903: RFS: qevercloud/3.0.2+ds-1 [ITP] -- Unofficial Evernote Cloud API library for Qt



Package: sponsorship-requests
Severity: wishlist

  Dear mentors,

  I am looking for a sponsor for my package "qevercloud"

 * Package name    : qevercloud
   Version         : 3.0.2+ds-1
   Upstream Author : Dmitry Ivanov <dm.vl.ivanov@gmail.com>
 * URL             : https://github.com/d1vanov/QEverCloud
 * License         : MIT
   Section         : libs

  It builds those binary packages:

    libqt4qevercloud3 - Unofficial Evernote Cloud API library for Qt4
    libqt5qevercloud3 - Unofficial Evernote Cloud API library for Qt5
    qt4qevercloud-dev - Development files for libqt4qevercloud
    qt5qevercloud-dev - Development files for libqt5qevercloud

  To access further information about this package, please visit the
following URL:

  https://mentors.debian.net/package/qevercloud


  Alternatively, one can download the package with dget using this command:

    dget -x https://mentors.debian.net/debian/pool/main/q/qevercloud/qevercloud_3.0.2+ds-1.dsc

  Alternatively, one can browse the packaging scripts on GitHub:

    https://github.com/hosiet/QEverCloud

  Alternatively, one can download pre-built deb packages or download
the source package on deb-o-matic:

    http://debomatic-amd64.debian.net/distribution#unstable/qevercloud/3.0.2+ds-1/

This is a new package and will work as the dependency of nixnote2
(RFS: #832704) to replace nixnote2's bundled qevercloud library source
files.

Previous discussions can be found in the nixnote2 RFS, start from Message #70:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832704#70

In order to regenerate some generated cpp source/headers files, the
source code of an extra generator
(https://github.com/d1vanov/QEverCloudGenerator) and the upstream
Thrift IDL files release by Evernote Corporation
(https://github.com/evernote/evernote-thrift) was included, which made
the build system (as written in debian/rules, plus patch in
debian/patches) somehow ugly and hacky.

I am wondering if such instructions are acceptable. Reviews and
suggestions are welcomed.

  Regards,
   Boyuan Yang


Reply to: