Project

General

Profile

Actions

User story #3055

closed

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

Added by Nicolas PERRON over 11 years ago. Updated almost 6 years ago.

Status:
Rejected
Priority:
3
Assignee:
-
Category:
Techniques
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 #1

Updated by Matthieu CERDA about 11 years ago

  • Target version changed from 2.3.10 to 2.3.11
Actions #2

Updated by Jonathan CLARKE about 11 years ago

  • Project changed from Rudder to 24
  • Category deleted (Techniques)
Actions #3

Updated by Matthieu CERDA almost 11 years ago

  • Target version changed from 2.3.11 to 2.3.12
Actions #4

Updated by Matthieu CERDA almost 11 years ago

  • Target version changed from 2.3.12 to 2.3.13
Actions #5

Updated by Nicolas PERRON almost 11 years ago

  • Target version changed from 2.3.13 to 84
Actions #6

Updated by Nicolas PERRON almost 11 years ago

  • Target version changed from 84 to 2.4.7
Actions #7

Updated by Nicolas PERRON over 10 years ago

  • Target version changed from 2.4.7 to 2.4.8
Actions #8

Updated by Nicolas PERRON over 10 years ago

  • Target version changed from 2.4.8 to 2.4.9
Actions #9

Updated by Nicolas PERRON over 10 years ago

  • Target version changed from 2.4.9 to 2.4.10
Actions #10

Updated by Nicolas PERRON over 10 years ago

  • Target version changed from 2.4.10 to 2.4.11
Actions #11

Updated by Nicolas PERRON over 10 years ago

  • Target version changed from 2.4.11 to 2.4.12
Actions #12

Updated by Nicolas PERRON over 10 years ago

  • Target version changed from 2.4.12 to 2.4.13
Actions #13

Updated by Vincent MEMBRÉ about 10 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 #14

Updated by Vincent MEMBRÉ about 10 years ago

  • Target version changed from 2.6.11 to 2.6.12
Actions #15

Updated by Vincent MEMBRÉ about 10 years ago

  • Target version changed from 2.6.12 to 2.6.13
Actions #16

Updated by Vincent MEMBRÉ almost 10 years ago

  • Target version changed from 2.6.13 to 2.6.14
Actions #17

Updated by Jonathan CLARKE almost 10 years ago

  • Target version changed from 2.6.14 to 2.6.16
Actions #18

Updated by Jonathan CLARKE almost 10 years ago

  • Target version changed from 2.6.16 to 2.6.17
Actions #19

Updated by Nicolas PERRON over 9 years ago

  • Target version changed from 2.6.17 to 2.6.18
Actions #20

Updated by Matthieu CERDA over 9 years ago

  • Target version changed from 2.6.18 to 2.6.19
Actions #21

Updated by Vincent MEMBRÉ over 9 years ago

  • Target version changed from 2.6.19 to 2.6.20
Actions #22

Updated by François ARMAND about 9 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 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 #23

Updated by Benoît PECCATTE about 9 years ago

  • Project changed from 24 to Rudder
  • Category set to Techniques
Actions #24

Updated by Vincent MEMBRÉ almost 9 years ago

  • Target version changed from 3.1.0~beta1 to 3.1.0~rc1
Actions #25

Updated by Vincent MEMBRÉ almost 9 years ago

  • Target version changed from 3.1.0~rc1 to 3.1.0
Actions #26

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 3.1.0 to 3.1.1
Actions #27

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 3.1.1 to 3.1.2
Actions #28

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 3.1.2 to 3.1.3
Actions #29

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 3.1.3 to 3.1.4
Actions #30

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 3.1.4 to 3.1.5
Actions #31

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 3.1.5 to 3.1.6
Actions #32

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 3.1.6 to 3.1.7
Actions #33

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 3.1.7 to 3.1.8
Actions #34

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 3.1.8 to 3.1.9
Actions #35

Updated by Vincent MEMBRÉ almost 8 years ago

  • Target version changed from 3.1.9 to 3.1.10
Actions #36

Updated by Vincent MEMBRÉ almost 8 years ago

  • Target version changed from 3.1.10 to 3.1.11
Actions #37

Updated by Vincent MEMBRÉ almost 8 years ago

  • Target version changed from 3.1.11 to 3.1.12
Actions #38

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.12 to 3.1.13
Actions #39

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.13 to 3.1.14
Actions #40

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.14 to 3.1.15
Actions #41

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.15 to 3.1.16
Actions #42

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.16 to 3.1.17
Actions #43

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.17 to 3.1.18
Actions #44

Updated by Vincent MEMBRÉ about 7 years ago

  • Target version changed from 3.1.18 to 3.1.19
Actions #45

Updated by Vincent MEMBRÉ almost 7 years ago

  • Target version changed from 3.1.19 to 3.1.20
Actions #46

Updated by Vincent MEMBRÉ almost 7 years ago

  • Target version changed from 3.1.20 to 3.1.21
Actions #47

Updated by Vincent MEMBRÉ almost 7 years ago

  • Target version changed from 3.1.21 to 3.1.22
Actions #48

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 3.1.22 to 3.1.23
Actions #49

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 3.1.23 to 3.1.24
Actions #50

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 3.1.24 to 3.1.25
Actions #51

Updated by Benoît PECCATTE over 6 years ago

  • Target version changed from 3.1.25 to 4.1.9
Actions #52

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 4.1.9 to 4.1.10
Actions #53

Updated by Benoît PECCATTE about 6 years ago

  • Status changed from Discussion to New
  • Assignee deleted (Jonathan CLARKE)
  • Target version changed from 4.1.10 to Ideas (not version specific)
Actions #54

Updated by Alexis Mousset almost 6 years ago

  • Status changed from New to Rejected

Possible in the (not so) new "Packages" technique, closing.

Actions

Also available in: Atom PDF