mudler / mudler/luet

Add feature for lock package version

Open
#101 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

area/funtoo enhancement
Dominant language
Go
Stars
307
Forks
30
PR merge metrics
No merged PRs in 30d

Description

If I want to stick with my libfoo-1 forever, I can do that (the masking action is exactly the opposite, I'm masking >libfoo-1 , but when I pin/lock, I ask to keep libfoo-1 in my system ) through a cli lock command.

$> luet lock cat/libfoo-1.1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the CLI entry point for the proposed luet lock cat/libfoo-1.1 command and compare it with the existing masking action mentioned in the issue. Done should provide a lock command that keeps the requested package version in the system.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
cli
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.