unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: zimoun <zimon.toutoune@gmail.com>
Cc: 53656-done@debbugs.gnu.org
Subject: bug#53656: [PATCH 0/2] 2 Julia packages
Date: Sun, 13 Feb 2022 12:23:19 +0200	[thread overview]
Message-ID: <YgjcF2phHg5KUsng@3900XT> (raw)
In-Reply-To: <87r18a8zee.fsf_-_@gmail.com>

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

On Thu, Feb 10, 2022 at 05:22:33PM +0100, zimoun wrote:
> Hi Efraim,
> 
> Both patches look good to me.
> 
> 
> I notice this warning:
> 
> --8<---------------cut here---------------start------------->8---
> ┌ Warning: Package OptimTestProblems does not have LinearAlgebra in its dependencies:
> │ - If you have OptimTestProblems checked out for development and have
> │   added LinearAlgebra as a dependency but haven't updated your primary
> │   environment's manifest file, try `Pkg.resolve()`.
> │ - Otherwise you may need to report an issue with OptimTestProblems
> └ Loading LinearAlgebra into OptimTestProblems from project dependency, future warnings for OptimTestProblems are suppressed.
> --8<---------------cut here---------------end--------------->8---

It ends up not being a problem, but I'm left wondering if we should
extend the #:julia-package-foo arguments to add more fields or if we
should just add a custom phase to build a Package.toml that includes all
the fields needed.

> and...
> 
> 
> On Mon, 31 Jan 2022 at 12:40, Efraim Flashner <efraim@flashner.co.il> wrote:
> 
> > * gnu/packages/julia-xyz.scm (julia-optim): New variable.
> 
> [...]
> 
> > +  #:use-module (guix gexp)
> 
> [...]
> 
> > +       #:phases
> > +       #~(modify-phases %standard-phases
> > +           (add-after 'unpack 'adjust-tests
> > +             (lambda _
> > +               ;; TODO: Figure out why this test fails.
> > +               (substitute* "test/runtests.jl"
> > +                 ((".*l_bfgs.*") "")))))))
> 
> ...I am thinking loudly if this gexp is required.  There are other many
> similar patter without a gexp.  Therefore, for consistency with the
> rest, I would be in favor to switch to regular modification of phases.
> Or let me know if this is becoming the new patter and I would adapt for
> the others.

It's definitely the new pattern we're using now. I suppose it's not
really necessary here, but having more instances of it throughout the
codebase also makes it easier to search for examples when others are
looking to use or modify gexps.

-- 
Efraim Flashner   <efraim@flashner.co.il>   רנשלפ םירפא
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2022-02-13 10:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-31 10:38 [bug#53656] [PATCH 0/2] 2 Julia packages Efraim Flashner
2022-01-31 10:40 ` [bug#53656] [PATCH 1/2] gnu: Add julia-linesearches Efraim Flashner
2022-01-31 10:40 ` [bug#53656] [PATCH 2/2] gnu: Add julia-optim Efraim Flashner
2022-02-10 16:22   ` [bug#53656] [PATCH 0/2] 2 Julia packages zimoun
2022-02-13 10:23     ` Efraim Flashner [this message]

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=YgjcF2phHg5KUsng@3900XT \
    --to=efraim@flashner.co.il \
    --cc=53656-done@debbugs.gnu.org \
    --cc=zimon.toutoune@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).