Skip to content

Improve folder name to reflect on the actual version of the package #4383

@sajjaphani

Description

@sajjaphani

In core-plans, we have some package names which I feel are misleading.

  • boost159
  • postgresql11
  • postgresql93

For example, boost159, which is a pinned version of 1.59. A better folder name could be [email protected].

The idea is to use the pinned version reflect in the name of the package followed by @ sign.
<name>@<major.minor.patch>

Below table shows some suggestions for the old and new folder names:

Old Name New Name
bdwgc7 bdwgc@7
bdwgc8 bdwgc@8
boost159 [email protected]
clang7 clang@7
corretto11 corretto@11
corretto8 corretto@8
curator4 curator@4
elasticsearch5 elasticsearch@5
ffmpeg3 ffmpeg@3
ffmpeg4 ffmpeg@4
ghc710-bootstrap [email protected]
ghc710 [email protected]
ghc80 [email protected]
ghc82-bootstrap [email protected]
ghc82 [email protected]
ghc84 [email protected]
ghc86 [email protected]
ghc88 [email protected]
gnupg2 gnupg@2
gradle4 gradle@4
gradle5 gradle@5
gtk2 gtk@2
haproxy16 [email protected]
haproxy17 [email protected]
haproxy18 [email protected]
haproxy19 [email protected]
haproxy20 [email protected]
haproxy21 [email protected]
icu52 icu@52
icu56 icu@56
kafka2 kafka@2
llvm7 llvm@7
logstash2 logstash@2
node10 node@10
node11 node@11
node12 node@12
node14 node@14
node6 node@6
openssl11 [email protected]
postgresql11-client postgresql-client@11
postgresql12-client postgresql-client@12
postgresql13-client postgresql-client@13
postgresql93-client [email protected]
postgresql94-client [email protected]
postgresql95-client [email protected]
postgresql96-client [email protected]
prometheus1 prometheus@1
prometheus2 prometheus@2
python2 python@2
python34 [email protected]
python36 [email protected]
python37 [email protected]
python38 [email protected]
python39 [email protected]
redis3 redis@3
redis4 redis@4
ruby25 [email protected]
ruby26 [email protected]
ruby30 [email protected]
tomcat7 tomcat@7
tomcat8 tomcat@8

Currently, plan builder does not allow us to use any special characters in the package name. But changing the folder names still improves the clarity of the version of the package on a high level.

Note: This change does not require us to change the contents of the plan file. We only need to update the plan file path in the builder.
Follow a similar pattern for the packages in chef-base-plans org.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions