unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Kristian Lein-Mathisen <kristianlein@gmail.com>, 57361@debbugs.gnu.org
Subject: [bug#57361] Solvespace package re-done
Date: Thu, 01 Sep 2022 19:20:18 +0200	[thread overview]
Message-ID: <5c21f4c8af182f338873abeed90c39f84b3e5add.camel@gmail.com> (raw)
In-Reply-To: <edb3a429f7c209d47b06c941ed6cf2d2fc634faf.camel@gmail.com>

Am Donnerstag, dem 01.09.2022 um 19:18 +0200 schrieb Liliana Marie
Prikler:
> Am Mittwoch, dem 31.08.2022 um 20:51 +0200 schrieb Kristian Lein-
> Mathisen:
> 
> > ;; There is another mimalloc, used in rust-mimalloc. But it's on
> > mimalloc
> > +;; version 1.6.4. TODO: See if it's possible to re-use this
> > package
> > by both.
> > +(define mimalloc-for-solvespace
> Given that this is the upstream mimalloc, there's no reason to make
> this private or only for solvespace.  Note that you should separate
> this into one patch per package.
Oh, and there's no conflict with rust-mimalloc, since that bundles
mimalloc as rust stuff does.  *sigh*

IOW you can name it mimalloc, no need for version suffixes or anything
else.  If at any point you need an old mimalloc as well, you can add it
as mimalloc-1.6 or whatever.

Cheers




  reply	other threads:[~2022-09-01 17:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-23 12:08 [bug#57361] [PATCH] gnu: Add solvespace Kristian Lein-Mathisen
2022-08-31 18:51 ` [bug#57361] Solvespace package re-done Kristian Lein-Mathisen
2022-09-01 17:18   ` Liliana Marie Prikler
2022-09-01 17:20     ` Liliana Marie Prikler [this message]
2022-09-05 19:57 ` [bug#57361] [PATCH] gnu: Add solvespace Kristian Lein-Mathisen
2022-09-06  8:30 ` Kristian Lein-Mathisen
2022-09-06  8:33 ` Kristian Lein-Mathisen
2022-09-08 13:14   ` Ludovic Courtès
2022-09-10 15:27     ` Liliana Marie Prikler
2022-09-11 14:13       ` bug#57361: " Ludovic Courtès
2022-09-10  7:55 ` [bug#57361] " ( via Guix-patches via

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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=5c21f4c8af182f338873abeed90c39f84b3e5add.camel@gmail.com \
    --to=liliana.prikler@gmail.com \
    --cc=57361@debbugs.gnu.org \
    --cc=kristianlein@gmail.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).