Unique pkg id for each program versions (e.g. redistributables, VS, etc)

[dtgm]

Currently, some programs have a different package ID for each version.

Examples of multiple packages for programs

dotnet/netfx framework packages

• dotnet3.5
• dotnet4.0
• dotnet4.5
• dotnet4.5.1
• dotnet4.5.2
• dotnet4.6
• dotnet4.6.1

also, (not sure how these are diff from above)

• netfx-4.0.3-devpack
• netfx-4.6-devpack
• dotnet4.6-targetpack

Microsoft Visual C++ redistributables

• vcredist2005
• vcredist2008
• vcredist2010
• vcredist2012
• vcredist2013
• vcredist2015

duplicates?

• msvisualcplusplus2012-redist
• msvisualcplusplus2013-redist

Visual Studio

• visualstudioexpress2008
• visualstudio2012expressweb
• visualstudio2012premium
• visualstudio2012professional
• visualstudiocommunity2013
• visualstudio2013expressweb
• visualstudio2013premium
• visualstudio2013professional
• visualstudio2013ultimate
• visualstudio2013teamexplorer
• visualstudio2015community
• visualstudio2015professional

duplicates?

• vs2012.4
• vs2012.5
• vs2013.1
• vs2013.2
• vs2013.3
• vs2013.4
• vs2013.5
• visualstudio2013-update1
• visualstudioexpress2013windows
• visualstudio2013testprofessional
• many more...

related:

• visualstudio2013-sdk
• visualstudio2012professionalwebtools
• many more...

Why not consolidate?

Disregarding that these are probably unnecessary duplicates, packages like:

• vs2013.1
• vs2013.2
• vs2013.3
• vs2013.4
• vs2013.5

Should definitely be consolidated into a single vs2013 package

But from there, how to handle versions?

Option 1 -- metapackage

• visualstudio == metapackage (not fully implemented yet)
• dynamically choose version and types (community/premium/professional/ultimate) via "undecided method" similar to FOO/FOO.install/FOO.portable

Option 2 -- master pkg

• Single package for all versions and types.
• Choose version and release type via --package-parameters

choco install visualstudio --params '/2013 /professional'
choco install visualstudio --params '/version=2013 /release=professional'

Option 3 -- master type

• Single package for all release types.
• Choose version via --package-parameters

choco install visualstudio-professional --params '/2013'
choco install visualstudio-professional --params '/version=2013'

Option 4 -- master major version

• Single package for all versions.
• Choose release type via --package-parameters

choco install visualstudio2013 --params '/professional'
choco install visualstudio2013 --params '/release=professional'

Standardize package naming

Programs

• visual-studio
• visualstudio
• vs

Examples:

• visual-studio-professional
• visualstudio-professional
• vs-professional

Release type

Also long-hand or short-hand for release types (if used):

long-hand	short-hand
community	comm
express	exp
premium	prem
professional	pro
ultimate	ult

Final question (hard)

Which would be best practice?

• most intuitive
• maximum benefits
• minimal disadvantages

[tunisiano187]

@gep13 , this seems OK in the version 0.10.5+
so i think you can close.
thx

[gep13]

@tunisiano187 this is a good reference issue regarding duplicate packages etc, but I agree, I don't think there is anything to be done here directly.