[PATCH 0/2] Some dependencies for julia-setfield

  • Done
  • quality assurance status badge
Details
2 participants
  • Ludovic Courtès
  • King, Spencer
Owner
unassigned
Submitted by
King, Spencer
Severity
normal

Debbugs page

King, Spencer wrote 3 months ago
(name . King, Spencer via Guix-patches via)(address . guix-patches@gnu.org)
CH3PR02MB97465DD08298C8EEC3833AAD90062@CH3PR02MB9746.namprd02.prod.outlook.com
Hello,

This patch series begins adding some of the dependencies necessary for building julia-setfield and running its test cases. There were a couple of test cases I was having issues with so I decided to just submit the dependency patches for now and finalize julia-setfield at a later date.

Best,
Spencer
King, Spencer wrote 3 months ago
[PATCH 1/2] gnu: Add julia-performancetesttools.
(name . 74987@debbugs.gnu.org)(address . 74987@debbugs.gnu.org)
CH3PR02MB97461D8341933028AAEB7F2290062@CH3PR02MB9746.namprd02.prod.outlook.com

King, Spencer wrote 3 months ago
[PATCH 2/2] gnu: Add julia-staticnumbers.
(name . 74987@debbugs.gnu.org)(address . 74987@debbugs.gnu.org)
CH3PR02MB9746CE029DC5145F044D7F5D90062@CH3PR02MB9746.namprd02.prod.outlook.com

Ludovic Courtès wrote 3 months ago
Re: [bug#74987] [PATCH 0/2] Some dependencies for julia-setfield
(name . King, Spencer)(address . spencer.king@wustl.edu)(address . 74987@debbugs.gnu.org)
87ikr93ypt.fsf@gnu.org
Hi,

"King, Spencer" <spencer.king@wustl.edu> skribis:

Toggle quote (6 lines)
> This patch series begins adding some of the dependencies necessary for
> building julia-setfield and running its test cases. There were a
> couple of test cases I was having issues with so I decided to just
> submit the dependency patches for now and finalize julia-setfield at a
> later date.

Nice. Applied as well, thanks!

It’s good to see the Julia package set grow. I must say though that I
wonder about longer-term maintenance.

For example, I gave a first stab at upgrading Julia but then ran out of

The other issue is that of individual package upgrades. So far it seems
to be pretty smooth, but I suspect it won’t last.

What’s your take?

Ludo’.
Ludovic Courtès wrote 3 months ago
control message for bug #74987
(address . control@debbugs.gnu.org)
87h66t3ype.fsf@gnu.org
close 74987
quit
King, Spencer wrote 3 months ago
Re: [bug#74987] [PATCH 0/2] Some dependencies for julia-setfield
(name . Ludovic Courtès)(address . ludo@gnu.org)(name . 74987@debbugs.gnu.org)(address . 74987@debbugs.gnu.org)
CH3PR02MB9746F7E8DDE165D98BEC439990032@CH3PR02MB9746.namprd02.prod.outlook.com
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
Ludovic Courtès wrote 3 months ago
(name . King, Spencer)(address . spencer.king@wustl.edu)(name . 74987@debbugs.gnu.org)(address . 74987@debbugs.gnu.org)(name . Nicolas Graves)(address . ngraves@ngraves.fr)
877c7mwu5s.fsf@gnu.org
Hi Spencer,

"King, Spencer" <spencer.king@wustl.edu> skribis:

Toggle quote (22 lines)
> 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.

Fortunately, Julia is less of a nice today than it was a few years back.
Hopefully we’ll find more people to help.

Regarding long-term maintenance, have you looked at the importer that
was proposed a while back? (Cc’ing Nicolas.)


I think we try and have an importer and updater in place to ease package
maintenance. Maybe the ‘juliahub’ importer (it seemed almost ready to
me), or maybe something else. It’s been instrumental in maintaining
other package sets.

Thanks for your feedback,
Ludo’.
?
Your comment

This issue is archived.

To comment on this conversation send an email to 74987@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 74987
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch
You may also tag this issue. See list of standard tags. For example, to set the confirmed and easy tags
mumi command -t +confirmed -t +easy
Or, remove the moreinfo tag and set the help tag
mumi command -t -moreinfo -t +help