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 #2531] [CLOSED] Move LLM library extraction to stable location #10924

New Issue
Closed
opened 2026-04-12 23:15:40 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-12 23:15:40 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/ollama/ollama/pull/2531
Author: @dhiltgen
Created: 2/16/2024
Status: ❌ Closed

Base: main ← Head: idempotent_llm_libs

📝 Commits (1)

  • 2bf0f02 Move LLM library extraction to stable location

📊 Changes

5 files changed (+69 additions, -32 deletions)

View changed files

📝 llm/llm.go (+6 -6)
📝 llm/payload_common.go (+25 -21)
📝 llm/utils.go (+32 -0)
📝 server/modelpath.go (+4 -1)
📝 server/routes.go (+2 -4)

📄 Description

This refines where we extract the LLM libraries to by adding a new OLLAMA_HOME env var, that defaults to ~/.ollama
The logic was already idempotenent, so this should speed up startups after the first time a new release is deployed. It also cleans up after itself.

I thought there was an issue tracking this but maybe it was just discussed in discord. (users seeing lots of orphaned ollamaXXX temp dirs)

🔄 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/2531 **Author:** [@dhiltgen](https://github.com/dhiltgen) **Created:** 2/16/2024 **Status:** ❌ Closed **Base:** `main` ← **Head:** `idempotent_llm_libs` --- ### 📝 Commits (1) - [`2bf0f02`](https://github.com/ollama/ollama/commit/2bf0f02b85593202a9ff5b0982c91da02cac7079) Move LLM library extraction to stable location ### 📊 Changes **5 files changed** (+69 additions, -32 deletions) <details> <summary>View changed files</summary> 📝 `llm/llm.go` (+6 -6) 📝 `llm/payload_common.go` (+25 -21) 📝 `llm/utils.go` (+32 -0) 📝 `server/modelpath.go` (+4 -1) 📝 `server/routes.go` (+2 -4) </details> ### 📄 Description This refines where we extract the LLM libraries to by adding a new OLLAMA_HOME env var, that defaults to `~/.ollama` The logic was already idempotenent, so this should speed up startups after the first time a new release is deployed. It also cleans up after itself. I thought there was an issue tracking this but maybe it was just discussed in discord. (users seeing lots of orphaned ollamaXXX temp dirs) --- <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-12 23:15:40 -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#10924
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?