unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "King, Spencer via Guix-patches" via <guix-patches@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: "74987@debbugs.gnu.org" <74987@debbugs.gnu.org>
Subject: [bug#74987] [PATCH 0/2] Some dependencies for julia-setfield
Date: Tue, 24 Dec 2024 21:38:36 +0000	[thread overview]
Message-ID: <CH3PR02MB9746F7E8DDE165D98BEC439990032@CH3PR02MB9746.namprd02.prod.outlook.com> (raw)
In-Reply-To: <87ikr93ypt.fsf@gnu.org>

Hi Ludo, 

Thank you for being so prompt when it comes to reviewing my patches, I really do appreciate it. I'm happy to help the Julia package set grow. All of my Julia contributions so far have been working towards packaging some of the larger machine learning packages that I use, which have pretty deep dependency trees.

I agree that longer-term maintenance is a point of concern. Perhaps that will change if Julia begins to see more widespread adoption. I think one of the biggest issues facing Julia packaging is that there currently isn't the same level of interest as languages like Python. I also know that there have been some issues with packages not building reproducibly due to upstream issues with the internals of the Julia compiler, but I'm not going to pretend I have an in-depth understanding of that issue.

I have seen your thread about your efforts to package a new version of Julia. It looks pretty complex and is definitely a major step up in complexity from any packages I've written so far. I think this comes back to the issue of interest, Julia just doesn't have the same level of interest as other languages in scientific computing so it can be challenging to find collaborators.

Like you said, individual package upgrades have gone fine so far. I've done a few myself without issues. I agree that it probably won't last as the package set grows and we end up with more complex dependency trees. However, I imagine that is a similar issue faced by other package sets in Guix.

Best,
Spencer



  reply	other threads:[~2024-12-24 21:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-19 23:12 [bug#74987] [PATCH 0/2] Some dependencies for julia-setfield King, Spencer via Guix-patches via
2024-12-19 23:30 ` [bug#74987] [PATCH 1/2] gnu: Add julia-performancetesttools King, Spencer via Guix-patches via
2024-12-19 23:31 ` [bug#74987] [PATCH 2/2] gnu: Add julia-staticnumbers King, Spencer via Guix-patches via
2024-12-24 15:08 ` [bug#74987] [PATCH 0/2] Some dependencies for julia-setfield Ludovic Courtès
2024-12-24 21:38   ` King, Spencer via Guix-patches via [this message]
2024-12-26 11:38     ` Ludovic Courtès

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=CH3PR02MB9746F7E8DDE165D98BEC439990032@CH3PR02MB9746.namprd02.prod.outlook.com \
    --to=guix-patches@gnu.org \
    --cc=74987@debbugs.gnu.org \
    --cc=ludo@gnu.org \
    --cc=spencer.king@wustl.edu \
    /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).