From: Simon Tournier <zimon.toutoune@gmail.com>
To: "Nicolas Graves" <ngraves@ngraves.fr>, "Ludovic Courtès" <ludo@gnu.org>
Cc: 61204@debbugs.gnu.org
Subject: [bug#61204] Scilab scientific software
Date: Mon, 03 Apr 2023 17:43:45 +0200 [thread overview]
Message-ID: <877cutezta.fsf@gmail.com> (raw)
In-Reply-To: <87bkkg3ofc.fsf@ngraves.fr>
Hi,
On sam., 25 mars 2023 at 15:17, Nicolas Graves via Guix-patches via <guix-patches@gnu.org> wrote:
> Actually, I've seen that it's possible to compile Suitesparse@3 without
> support for Metis@4. Scilab seems to work correctly, so I'll stop here
> for this version ;)
Cool!
Just a remark about [PATCH v2 3/3] gnu: Add scilab.
+ (source
+ (origin
+ (method url-fetch)
+ (uri
+ (string-append "https://oos.eu-west-2.outscale.com/scilab-releases/"
+ version "/scilab-" version "-src.tar.gz"))
+ (sha256
+ (base32 "1hx57aji5d78brwqcf8a34i1hasm3h4nw46xjg7cgxj09s8yz5kq"))))
Is the URL stable? It looks like the Cloud solution of Dassault
Systèmes, right? Dassault Systèmes being the maintainer, right?
Well, the main development repository seems gitlab.com, right?
https://gitlab.com/scilab/scilab
Why not rely on this gitlab.com URL? Tarball if the Git history of the
repository is too heavy. For example,
https://gitlab.com/scilab/scilab/-/archive/5.5.0/scilab-5.5.0.tar.gz
Although some files are only in the outscale link,
--8<---------------cut here---------------start------------->8---
$ diff -r --no-dereference scilab-5.5.0-{1,2}
Only in scilab-5.5.0-1: ACKNOWLEDGEMENTS
Only in scilab-5.5.0-1: aclocal.m4
Only in scilab-5.5.0-1: bin
Only in scilab-5.5.0-1: build.incl.xml
Only in scilab-5.5.0-1: build.qa.incl.xml
Only in scilab-5.5.0-1: CHANGES_2.X
Only in scilab-5.5.0-1: CHANGES_3.X
Only in scilab-5.5.0-1: CHANGES_4.X
Only in scilab-5.5.0-1: CHANGES_5.0.X
Only in scilab-5.5.0-1: CHANGES_5.1.X
Only in scilab-5.5.0-1: CHANGES_5.2.X
Only in scilab-5.5.0-1: CHANGES_5.3.X
Only in scilab-5.5.0-1: CHANGES_5.4.X
Only in scilab-5.5.0-1: CHANGES_5.5.X
Only in scilab-5.5.0-1: checkstyle
Only in scilab-5.5.0-1: config
Only in scilab-5.5.0-1: configure
Only in scilab-5.5.0-1: configure.ac
Only in scilab-5.5.0-1: contrib
Only in scilab-5.5.0-1: COPYING
Only in scilab-5.5.0-1: COPYING-BSD
Only in scilab-5.5.0-1: COPYING-FR
Only in scilab-5.5.0-1: desktop
Only in scilab-5.5.0-1: etc
Only in scilab-5.5.0-2: git_hooks
Only in scilab-5.5.0-2: .gitignore
Only in scilab-5.5.0-1: GIT_info.incl
Only in scilab-5.5.0-1: libs
Only in scilab-5.5.0-1: license.txt
Only in scilab-5.5.0-1: locale
Only in scilab-5.5.0-1: m4
Only in scilab-5.5.0-1: Makefile.am
Only in scilab-5.5.0-1: Makefile.call_scilab.am
Only in scilab-5.5.0-1: Makefile.in
Only in scilab-5.5.0-1: Makefile.incl.am
Only in scilab-5.5.0-1: Makefile.incl.in
Only in scilab-5.5.0-1: modules
Only in scilab-5.5.0-1: README_Unix
Only in scilab-5.5.0-1: Readme_Visual.txt
Only in scilab-5.5.0-1: README_Windows.txt
Only in scilab-5.5.0-1: RELEASE_NOTES_5.0.X
Only in scilab-5.5.0-1: RELEASE_NOTES_5.1.X
Only in scilab-5.5.0-1: RELEASE_NOTES_5.2.X
Only in scilab-5.5.0-1: RELEASE_NOTES_5.3.X
Only in scilab-5.5.0-2: scilab
Only in scilab-5.5.0-1: Scilab_f2c.sln
Only in scilab-5.5.0-1: scilab-lib-doc.properties.in
Only in scilab-5.5.0-1: scilab-lib-doc.properties.vc
Only in scilab-5.5.0-1: scilab-lib.properties.in
Only in scilab-5.5.0-1: scilab-lib.properties.vc
Only in scilab-5.5.0-1: scilab.pc.in
Only in scilab-5.5.0-1: scilab.properties.in
Only in scilab-5.5.0-1: scilab.properties.vc
Only in scilab-5.5.0-1: Scilab.sln
Only in scilab-5.5.0-2: SEP
Only in scilab-5.5.0-1: SVN_revision.incl
Only in scilab-5.5.0-1: tools
Only in scilab-5.5.0-1: Version.incl
Only in scilab-5.5.0-1: Visual-Studio-settings
--8<---------------cut here---------------end--------------->8---
Ah, weird! :-)
Cheers,
simon
next prev parent reply other threads:[~2023-04-03 16:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-01 1:07 [bug#61204] Scilab scientific software Nicolas Graves via Guix-patches via
2023-02-01 1:12 ` [bug#61204] [PATCH 1/6] gnu: matio: Add header file Nicolas Graves via Guix-patches via
2023-02-01 1:12 ` [bug#61204] [PATCH 2/6] gnu: Add metis-4 Nicolas Graves via Guix-patches via
2023-02-01 1:12 ` [bug#61204] [PATCH 3/6] gnu: Add suitesparse-3 Nicolas Graves via Guix-patches via
2023-02-01 1:12 ` [bug#61204] [PATCH 5/6] gnu: scilab: Update to 5.5.1 Nicolas Graves via Guix-patches via
2023-02-01 1:12 ` [bug#61204] [PATCH 6/6] gnu: scilab: Update to 5.5.2 Nicolas Graves via Guix-patches via
2023-02-10 23:08 ` [bug#61204] Scilab scientific software Ludovic Courtès
2023-02-11 10:11 ` Nicolas Graves via Guix-patches via
2023-02-11 10:09 ` [bug#61204] [PATCH] gnu: Add scilab Nicolas Graves via Guix-patches via
2023-02-15 15:57 ` [bug#61204] Scilab scientific software Simon Tournier
2023-03-16 11:26 ` Ludovic Courtès
2023-03-25 14:17 ` Nicolas Graves via Guix-patches via
2023-04-03 15:43 ` Simon Tournier [this message]
2023-03-25 14:15 ` [bug#61204] [PATCH v2 1/3] gnu: matio: Add header file Nicolas Graves via Guix-patches via
2023-03-25 14:15 ` [bug#61204] [PATCH v2 2/3] gnu: Add suitesparse-3 Nicolas Graves via Guix-patches via
2023-03-25 14:15 ` [bug#61204] [PATCH v2 3/3] gnu: Add scilab Nicolas Graves via Guix-patches via
2023-03-30 20:43 ` bug#61204: " 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=877cutezta.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=61204@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=ngraves@ngraves.fr \
/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).