github-starred/ollama
2
0
Fork 0
mirror of https://github.com/ollama/ollama.git synced 2026-05-07 00:22:43 -05:00
Code Issues 14.5k Packages Projects Releases 120 Wiki Activity

[PR #2647] [CLOSED] Adding '--tag' to install.sh to simplify pre-release or specific version install locally #57648

New Issue
Closed
opened 2026-04-29 12:20:27 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-29 12:20:27 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/ollama/ollama/pull/2647
Author: @cyrusradfar
Created: 2/21/2024
Status: ❌ Closed

Base: main ← Head: main

📝 Commits (4)

  • 69a97bb Added --tag based install for pre-release branches
  • e1303ed Fixed typo in status output, corrected 'e.' to 'e.g.'
  • 9a04ad9 Merge branch 'ollama:main' into main
  • 780a521 Merge branch 'ollama:main' into main

📊 Changes

1 file changed (+43 additions, -2 deletions)

View changed files

📝 scripts/install.sh (+43 -2)

📄 Description

Adding a 'feature' to the install script for Linux users that allows specifying the --tag on installation.

Why

There will be times where we'll want to allow early-adopters to quickly access and test new features; however, they're not stable enough for a release.

Solution

Allow the user to specify a dynamic tag on the install.sh script. The script is 100% backwards compatible with current functionality and acts exactly the same without the 'tag' argument.

Error Handling

In the case the user doesn't specify a tag or specifies 'latest' they'll get the exact same functionality today.

If they specify a tag which is semantically invalid based on historical tag scheme, e.g. v[number].[number].[number] then the system will exit in an error. This can easily be removed if the scheme changes.

If the user specifies a valid tag name that doesn't exist, the download can't be found, or github is down then the script fails and provides an error to specify that the download failed.

In both cases, trying again with the 'latest' release would provide the user a potentially confusing understanding of their local state where they may miss the error output and think they're running a newer or different version of the tool.

Follow on Work

If this PR is accepted, we may want to consider documenting in the core readme where we discuss this process

curl -fsSL https://ollama.com/install.sh | sh

To share how to download a specific tag. I wouldn't think removing the existing simple script is a good idea bc it complicates the experience for new users.
curl -fsSL https://ollama.com/install.sh | sh -s -- --tag "$TAG"

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/ollama/ollama/pull/2647 **Author:** [@cyrusradfar](https://github.com/cyrusradfar) **Created:** 2/21/2024 **Status:** ❌ Closed **Base:** `main` ← **Head:** `main` --- ### 📝 Commits (4) - [`69a97bb`](https://github.com/ollama/ollama/commit/69a97bb8aa5e9a814d066005cfb8edfb2434d58a) Added --tag based install for pre-release branches - [`e1303ed`](https://github.com/ollama/ollama/commit/e1303ed670ec1b99cf3d96343d0916225df4fee4) Fixed typo in status output, corrected 'e.' to 'e.g.' - [`9a04ad9`](https://github.com/ollama/ollama/commit/9a04ad9dcc848ba837c0889d26a38b21f0d7a121) Merge branch 'ollama:main' into main - [`780a521`](https://github.com/ollama/ollama/commit/780a5211429789f035c6cebc25a2555e8f7b6e0d) Merge branch 'ollama:main' into main ### 📊 Changes **1 file changed** (+43 additions, -2 deletions) <details> <summary>View changed files</summary> 📝 `scripts/install.sh` (+43 -2) </details> ### 📄 Description Adding a 'feature' to the install script for Linux users that allows specifying the `--tag` on installation. ### Why There will be times where we'll want to allow early-adopters to quickly access and test new features; however, they're not stable enough for a release. ### Solution Allow the user to specify a dynamic tag on the `install.sh` script. The script is 100% backwards compatible with current functionality and acts exactly the same without the 'tag' argument. ### Error Handling In the case the user doesn't specify a tag or specifies 'latest' they'll get the exact same functionality today. If they specify a tag which is semantically invalid based on historical tag scheme, e.g. v[number].[number].[number] then the system will exit in an error. This can easily be removed if the scheme changes. If the user specifies a valid tag name that doesn't exist, the download can't be found, or github is down then the script fails and provides an error to specify that the download failed. In both cases, trying again with the 'latest' release would provide the user a potentially confusing understanding of their local state where they may miss the error output and think they're running a newer or different version of the tool. ### Follow on Work If this PR is accepted, we may want to consider documenting in the core readme where we discuss this process ```curl -fsSL https://ollama.com/install.sh | sh``` To share how to download a specific tag. I wouldn't think removing the existing simple script is a good idea bc it complicates the experience for new users. ```curl -fsSL https://ollama.com/install.sh | sh -s -- --tag "$TAG"``` --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-04-29 12:20:27 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
amd
api
app
bug
build
cli
cloud
compatibility
context-length
create
docker
documentation
embeddings
feature request
feedback wanted
good first issue
gpt-oss
gpu
harmony
help wanted
image
install
intel
js
launch
linux
macos
memory
mlx
model
needs more info
networking
nvidia
ollama.com
performance
pull-request
Mirrored from GitHub Pull Request
 python
question
registry
rendering
thinking
tools
top
vulkan
windows
wsl
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#57648
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?