public inbox for gentoo-science@lists.gentoo.org
 help / color / mirror / Atom feed
From: "François Bissey" <fbissey@slingshot.co.nz>
To: gentoo-science@lists.gentoo.org
Subject: Re: [gentoo-science] Future of the packaging of SuiteSparse
Date: Mon, 7 Nov 2022 16:04:40 +1300	[thread overview]
Message-ID: <dcaac7d1-f64d-d614-4ec0-166ef7f6f1b0@slingshot.co.nz> (raw)
In-Reply-To: <0d763dc1-b2c7-0079-532b-c0b38e68ced4@slingshot.co.nz>



On 7/11/22 14:55, François Bissey wrote:
> I am very of the mind that we should stop the splitting. Versionning of 
> the individual packages is a bit in the air but following the meta 
> package versioning is the easiest maintenance wise.

Writing down stuff and posting it helps to think about it. Following the 
meta packaging versioning may break tracking with repology, so best to 
avoid it.

Other stuff that I should mention:
doc building will not happen with the current cmake implementation. Meta 
building is still handled by a makefile with some options and docs are 
still built by the generic makefiles.

Same with test suites. We currently use "Demo" as test suites. They can 
be built from cmake (at least in some of the packages) but they are not 
currently executed and tested by cmake.

openmp: is currently automagic for most packages supporting it. Used if 
found. I can work with upstream to turn it off if necessary.y

Upside: cuda is handled fairly well by cmake compared to autoconf.

François


  reply	other threads:[~2022-11-07  3:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-07  1:55 [gentoo-science] Future of the packaging of SuiteSparse François Bissey
2022-11-07  3:04 ` François Bissey [this message]
2022-11-08 22:58   ` François Bissey
2022-11-09 22:46     ` François Bissey

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=dcaac7d1-f64d-d614-4ec0-166ef7f6f1b0@slingshot.co.nz \
    --to=fbissey@slingshot.co.nz \
    --cc=gentoo-science@lists.gentoo.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