From: Christophe Pisteur <christophe.pisteur@fsfe.org>
To: Sergiu Ivanov <sivanov@colimite.fr>
Cc: help-guix@gnu.org
Subject: Re: Appimage: cannot run binary file
Date: Thu, 11 Feb 2021 15:43:24 +0100 [thread overview]
Message-ID: <d6a809d5f82c128ec7af907c077696191a11c112.camel@fsfe.org> (raw)
In-Reply-To: <87sg624rta.fsf@colimite.fr>
Le jeudi 11 février 2021 à 15:12 +0100, Sergiu Ivanov a écrit :
> Hi Christophe,
> > I don't understand all the nuances of this discussion (I'm sorry),
> > butit seems to me that the problem is, in the case of the
> > developmentversion of freecad, that the sources are not published
> > regularly. Thesources were last published in 2019 (1), while
> > freecad offers anAppimage almost every week. So building something
> > from the sources ofthe development code doesn't add much value to
> > the stable version. Imust certainly be missing something, so once
> > again sorry.Christophe(1)
> > https://github.com/FreeCAD/FreeCAD/releases/tag/0.19_pre: "
> > Note:The development binaries are built regularly (You may need to
> > expandthe assets tab) . The release date indicates the beginning of
> > the devcycle. The commits indicates how many commits in the dev
> > cycle. Thesource archives (tar.gz and .zip) do not get updated, so
> > they match thecommit of the tag (34a083b) and are therefore
> > obsolete. You can get thelatest source here:
> > https://github.com/FreeCAD/FreeCAD/archive/master.zip"
>
> I don't know or use FreeCAD, but it looks like the source code
> isupdated quite regularly on their GitHub repository:
> https://github.com/FreeCAD/FreeCAD/
>
> The latest changes seem to date back to several hours.
> I'd say these are the sources from which the development binaries
> arebuilt (at least this is what is usually done).
> My understanding of the sentence
> > The source archives (tar.gz and .zip) do not get updated, so
> > theymatch the commit of the tag (34a083b) and are therefore
> > obsolete.
>
> is that the FreeCAD team don't bother archiving the sources
> bythemselves, given that one can always access the latest versionon
> GitHub.
> -Sergiu
Sorry for the confusion and thank you for the explanation.
Christophe
next prev parent reply other threads:[~2021-02-11 14:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-10 18:08 Appimage: cannot run binary file Christophe Pisteur
2021-02-10 18:59 ` Tobias Geerinckx-Rice
2021-02-11 4:25 ` raingloom
2021-02-11 12:53 ` Christophe Pisteur
2021-02-11 14:12 ` Sergiu Ivanov
2021-02-11 14:43 ` Christophe Pisteur [this message]
2021-02-12 5:12 ` raingloom
2021-02-15 9:56 ` Efraim Flashner
2021-02-11 6:11 ` Christophe Pisteur
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=d6a809d5f82c128ec7af907c077696191a11c112.camel@fsfe.org \
--to=christophe.pisteur@fsfe.org \
--cc=help-guix@gnu.org \
--cc=sivanov@colimite.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.
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).