User story #3055: Add a technique for local packages installation (not via repos) - Rudder - Issue Tracker

Actions

Copy link

User story #3055

closed

Add a technique for local packages installation (not via repos)

Added by Nicolas PERRON about 12 years ago. Updated over 6 years ago.

Status:

Rejected

Priority:

Assignee:

Category:

Techniques

Target version:

Ideas (not version specific)

Pull Request:

UX impact:

Suggestion strength:

User visibility:

Effort required:

Name check:

Fix check:

Regression:

Description

It is not always possible to define a repository with all the packages that should be installed.

A Technique which could use dpkg or rpm to install a package specified by its path on the Node or from shared-files from Rudder Server should be sufficient.

This Technique could force to install the package if another version (early or latest) is already installed but the version of the package installed on the Node must be verified.

Actions

Copy link

Updated by Matthieu CERDA almost 12 years ago

Target version changed from 2.3.10 to 2.3.11

Actions

Copy link

Updated by Jonathan CLARKE almost 12 years ago

Project changed from Rudder to 24
Category deleted (~~Techniques~~)

Actions

Copy link

Updated by Matthieu CERDA over 11 years ago

Target version changed from 2.3.11 to 2.3.12

Actions

Copy link

Updated by Matthieu CERDA over 11 years ago

Target version changed from 2.3.12 to 2.3.13

Actions

Copy link

Updated by Nicolas PERRON over 11 years ago

Target version changed from 2.3.13 to 84

Actions

Copy link

Updated by Nicolas PERRON over 11 years ago

Target version changed from 84 to 2.4.7

Actions

Copy link

Updated by Nicolas PERRON over 11 years ago

Target version changed from 2.4.7 to 2.4.8

Actions

Copy link

Updated by Nicolas PERRON over 11 years ago

Target version changed from 2.4.8 to 2.4.9

Actions

Copy link

Updated by Nicolas PERRON about 11 years ago

Target version changed from 2.4.9 to 2.4.10

Actions

Copy link

#10

Updated by Nicolas PERRON about 11 years ago

Target version changed from 2.4.10 to 2.4.11

Actions

Copy link

#11

Updated by Nicolas PERRON about 11 years ago

Target version changed from 2.4.11 to 2.4.12

Actions

Copy link

#12

Updated by Nicolas PERRON about 11 years ago

Target version changed from 2.4.12 to 2.4.13

Actions

Copy link

#13

Updated by Vincent MEMBRÉ almost 11 years ago

Target version changed from 2.4.13 to 2.6.11

Since Support for 2.4 branch is over, retargeting this issue to 2.6

Actions

Copy link

#14

Updated by Vincent MEMBRÉ almost 11 years ago

Target version changed from 2.6.11 to 2.6.12

Actions

Copy link

#15

Updated by Vincent MEMBRÉ almost 11 years ago

Target version changed from 2.6.12 to 2.6.13

Actions

Copy link

#16

Updated by Vincent MEMBRÉ over 10 years ago

Target version changed from 2.6.13 to 2.6.14

Actions

Copy link

#17

Updated by Jonathan CLARKE over 10 years ago

Target version changed from 2.6.14 to 2.6.16

Actions

Copy link

#18

Updated by Jonathan CLARKE over 10 years ago

Target version changed from 2.6.16 to 2.6.17

Actions

Copy link

#19

Updated by Nicolas PERRON over 10 years ago

Target version changed from 2.6.17 to 2.6.18

Actions

Copy link

#20

Updated by Matthieu CERDA about 10 years ago

Target version changed from 2.6.18 to 2.6.19

Actions

Copy link

#21

Updated by Vincent MEMBRÉ about 10 years ago

Target version changed from 2.6.19 to 2.6.20

Actions

Copy link

#22

Updated by François ARMAND almost 10 years ago

Subject changed from Packages should be able to be installed by other way than package manager to Add a technique for local packages installation (not via repos)
Status changed from New to Discussion
Assignee set to Jonathan CLARKE
Priority changed from 1 (highest) to 3
Target version changed from 2.6.20 to 3.1.0~beta1

Jon, I would love to have your idea of the importance for that, given that now, we have ncf builder that make it possible. What do you thing ? So standard that should be proposed anyway ? If so, for which package managers ?

More fondamentally, it asks the question about what we adresse with the defaults techniques. Do we want to support "anything standard to manage Debian/Redhat/Suse", or is it just an overview about what is possible, or something else.

(my personnal feeling being that: we are in an open world, the "standard" things is highly dependant of the person talking about the standard, so there is a high risk in spending a lot of time in things that should be done by the community, and so our role as Rudder lead is two provide the tool to make these addition easier to do and discover and use from Rudder - so yes, that is a "low importance for that one" :)

Actions

Copy link

#23