public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Lemures Lemniscati <lemures.lemniscati@gmail.com>
To: cygwin-apps@cygwin.com
Subject: Re: [ITA] openbabel-3.1.1p32
Date: Thu, 26 Nov 2020 13:24:58 +0900	[thread overview]
Message-ID: <20201126132456.3630.50F79699@gmail.com> (raw)
In-Reply-To: <7db66c1e-75f3-7da5-5435-086c2d1bab1a@cornell.edu>

On Wed, 25 Nov 2020 18:48:00 -0500, Ken Brown via Cygwin-apps
> On 10/25/2020 7:51 AM, Lemures Lemniscati via Cygwin-apps wrote:
> > Hi!
> >
> > ITA for openbabel, which have been maintained by Yaakov [1].
> >
> > Now, the latest upstream version of Open Babel [0] is 3.1.1 [2].
> >
> > A new candidate cygport file is placed at [3] (but it is not tested
> > on Cygwin AppVeyor CI, yet). And, it brings a version at 32 commits
> > after 3.1.1.
> >
> > Generated package files are placed at [4] or [5].
> >
> > These packages depend on rapidjson, schroedinger-maeparser, and
> > schroedinger-coordgenlibs, which are under ITP.
> >
> > * openbabel-3.1.1p32-1
> > * openbabel-doc-3.1.1p32-1
> > * libinchi-devel-3.1.1p32-1
> > * libinchi0-3.1.1p32-1
> > * libopenbabel-devel-3.1.1p32-1
> > * libopenbabel7-3.1.1p32-1
> > * perl-Chemistry-OpenBabel-3.1.1p32-1
> > * python38-openbabel-3.1.1p32-1
> > * ruby-openbabel-3.1.1p32-1
> >
> > * openbabel-3.1.1p32-1-src
> > * openbabel-debuginfo-3.1.1p32-1
> >
> > [0]: http://openbabel.org/
> > [1]: https://cygwin.com/git/?p=git/cygwin-packages/openbabel.git
> > [2]: https://github.com/openbabel/openbabel/releases/
> > [3]: https://github.com/cygwin-lem/openbabel-cygport/tree/n_3.1.1p32
> > [4]: https://cygwin-lem.github.io/openbabel-cygport/
> > [5]: https://github.com/cygwin-lem/openbabel-cygport/tree/n_3.1.1p32_gh-pages
> 
> My only question is whether it really makes sense to add openbabel-doc, which seems to contain only the standard files (AUTHORS, COPYING, etc.).  Did you have a reason for not just including those in openbabel as was done previously.
> 
> Also, you need to add ruby-devel to BUILD_REQUIRES.
> 
> Ken

Thank you, Ken!

I'll fix them.

Lem

  reply	other threads:[~2020-11-26  4:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-25 11:51 Lemures Lemniscati
2020-11-25 23:48 ` Ken Brown
2020-11-26  4:24   ` Lemures Lemniscati [this message]
2020-11-26 14:37     ` Ken Brown
2023-10-21 13:07 ` Jon Turney
2023-10-23 10:09   ` Lemures Lemniscati
2023-10-24 17:11     ` Jon Turney

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20201126132456.3630.50F79699@gmail.com \
    --to=lemures.lemniscati@gmail.com \
    --cc=cygwin-apps@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).