On 6/22/22 08:18, Waldek Hebisch wrote:
On Wed, Jun 22, 2022 at 07:46:03AM +0800, Qian Yun wrote:
Hi Waldek,
GitHub allows me to modify the release page to add new binaries.
A few questions:
http://fricas.sourceforge.net/doc/INSTALL-bin.txt stills mentions 1.3.7.
Shall we put that file into git as well? Some other parts need
updating as well.
I update this at each release. Keeping it in version control is
almost no gain. ATM I am waiting for all binaries, this is
part that changes for each release. And of course, we need some
info about how to install new binaries.
Basically I want to officially announce release once all binaries
and documents are in place (I do not want to change Notes-1.3.8.txt
after release as this may cause confusion, and Notes-1.3.8.txt
contains names of binaries).
I have uploaded macOS/windows binaries. And I add a few sentences
at the end of the release page. Feel free to add them to
INSTALL-bin.txt.
Now the tag name and branch name is the same. It is a little
inconvenient to checkout them. Can you rename the branch name
to something else?
Tag is pure Github nonsense, apparently it does not allow
making relase without a tag. IMO, to minimize confusion it
is best to keep them the same. Concerning checkout IIUC
canonical procedure is:
git clone
git checkout
and it seems to work fine. What problem do you see?
Tag and branch are the same name, you will get
warning: refname '1.3.8' is ambiguous.
And when you do checkout, it defaults to tag instead of branch.
- Qian
--
You received this message because you are subscribed to the Google Groups "FriCAS -
computer algebra system" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/fricas-devel/5c4e3ea0-904b-6b93-1a44-5fbe226a0bbc%40gmail.com.
