Opened 8 years ago
Last modified 4 years ago
#145 assigned enhancement
improve setupv step for docker
Reported by: | Bruno Cornec | Owned by: | Bruno Cornec |
---|---|---|---|
Priority: | critical | Milestone: | |
Component: | pb | Version: | 0.13.2 |
Keywords: | Cc: |
Description
In order to have LTS pb containers, we need to be able to upgrade pb without having to reinstall all the deps of it + the one of the project (this allows not maintained distro to still build SW with recent pb)
Current method is that setupv restart from step 1 to rebuild step 2 whereas it should restart from step 3 and overwrite it.
Change History (11)
comment:2 by , 8 years ago
Milestone: | 0.14.1 → 0.14.2 |
---|
comment:3 by , 7 years ago
Milestone: | 0.14.2 → 0.14.3 |
---|
comment:4 by , 7 years ago
Status: | new → assigned |
---|
in 0.14.3, sbx2vx now calls prepvx to avoid redoing prep separately when it's very long (particularly when debugging a new package build)
However, that doesn't solve fully the management of pb itself.
comment:5 by , 7 years ago
Milestone: | 0.14.3 → 0.14.4 |
---|
comment:6 by , 7 years ago
Milestone: | 0.14.4 → 0.14.5 |
---|
comment:7 by , 7 years ago
Milestone: | 0.14.5 → 0.14.6 |
---|
comment:8 by , 7 years ago
Milestone: | 0.14.6 → 0.15.1 |
---|
comment:9 by , 5 years ago
Milestone: | 0.15.1 → 0.15.2 |
---|
comment:10 by , 5 years ago
Milestone: | 0.15.2 → 0.15.3 |
---|
comment:11 by , 4 years ago
Milestone: | 0.15.3 |
---|
This should also help avoiding to redo the prepve step which is mandatory before sbx2ve. When going directly from sbx2setupve to sbx2ve, in fact lacjing the prepve create a wrong build env !