Github messages for voidlinux
 help / color / mirror / Atom feed
From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [no merge] darktable: update to 3.0.0.
Date: Wed, 08 Jan 2020 06:49:28 +0100	[thread overview]
Message-ID: <20200108054928.WyjDoEE617VtVcZsOkjLMzBb9hvT0cR1uTTsFD-bCAM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-17787@inbox.vuxu.org>

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

New comment by lemmi on void-packages repository

https://github.com/void-linux/void-packages/pull/17787#issuecomment-571901288

Comment:
I already mentioned this in IRC: I'm not sure I want to keep `32bit` alive for `darktable`. There is a reason upstream drops the support. To be able to do any sort of meaningful work with `darktable` you need ram (and lots of it) and computing power. And you won't get that anymore with `32bit` plattforms.

If there is someone out there depending on `32bit` `darktable`, I'm willing to keep this alive for a bit. Otherwise I'm going with upstream and remove support now as well.

  parent reply	other threads:[~2020-01-08  5:49 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-26  8:28 [PR PATCH] " voidlinux-github
2019-12-27  2:00 ` voidlinux-github
2019-12-27  2:02 ` voidlinux-github
2019-12-27  2:02 ` voidlinux-github
2019-12-28 18:21 ` voidlinux-github
2019-12-29  1:12 ` voidlinux-github
2020-01-08  5:49 ` voidlinux-github [this message]
2020-01-08  5:57 ` voidlinux-github
2020-01-08  5:57 ` voidlinux-github
2020-01-08  6:04 ` voidlinux-github
2020-02-25 19:42 ` TeddyDD
2020-02-25 20:21 ` lemmi
2020-04-17 19:50 ` [PR PATCH] [Updated] " lemmi
2020-04-18  6:38 ` lemmi
2020-04-18  6:41 ` lemmi
2020-04-18  7:34 ` lemmi
2020-04-18 15:13 ` [PR PATCH] [Closed]: " lemmi

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=20200108054928.WyjDoEE617VtVcZsOkjLMzBb9hvT0cR1uTTsFD-bCAM@z \
    --to=voidlinux-github@inbox.vuxu.org \
    --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).