Github messages for voidlinux
 help / color / mirror / Atom feed
From: tornaria <tornaria@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: igraph: update to 0.10.2.
Date: Thu, 03 Nov 2022 03:16:13 +0100	[thread overview]
Message-ID: <20221103021613.9A4dhftu1-4-lV1PG0ZM5PgxK2vm1XCM7ZJQaelprhU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40224@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1286 bytes --]

New comment by tornaria on void-packages repository

https://github.com/void-linux/void-packages/pull/40224#issuecomment-1301569125

Comment:
> Note that SuiteSparse is no longer a dependency of igraph since version 0.10.
> 
> flex and bison are only needed if you are trying to build the development version from the git repo. If you build from the release archive, as you are doing now, they are not needed.
> 
> python3 is only needed if building the docs. The docs are already included in the release archive, so if you want to install them, you can just copy the `doc` folder directly, no need to build anything.
> 
> Regarding rankwidth: igraph 0.10 is not API-compatible with 0.9. Some very significant changes have been made, so basically every dependency will need source changes. rankwidth seems to be lucky in that a single very minor change allows it to build, see https://sourceforge.net/p/rankwidth/tickets/2/
> 
> A short upgrade guide for package maintainers is here: [igraph/igraph#2134 (comment)](https://github.com/igraph/igraph/issues/2134#issuecomment-1220427403)

Thanks for the info, it will be very useful. I'm fighting with sage-on-python 3.11 with a deadline right now, but I will come back to this PR later and make sure igraph + rankwidth work ok.

  parent reply	other threads:[~2022-11-03  2:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-29 17:30 [PR PATCH] " tornaria
2022-10-30 19:06 ` classabbyamp
2022-10-30 23:17 ` tornaria
2022-10-31 15:08 ` szhorvat
2022-10-31 15:11 ` szhorvat
2022-11-03  2:16 ` tornaria [this message]
2022-11-12 19:19 ` [PR PATCH] [Updated] " tornaria
2022-11-13  2:52 ` tornaria
2022-11-15 19:14 ` [PR PATCH] [Updated] " tornaria
2022-11-16  2:47 ` tornaria
2022-12-03 22:36 ` [PR PATCH] [Merged]: " Piraty

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=20221103021613.9A4dhftu1-4-lV1PG0ZM5PgxK2vm1XCM7ZJQaelprhU@z \
    --to=tornaria@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /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 NNTP newsgroup(s).