Open schultyy opened 9 years ago
TODO:
Not wanting to annoy you here, but also: aliases of packages in different distributions, e.g. vim-full
or emacs-nox
:)
@bascht I already stumbled upon the vim-full
, vim-extended
, etc. packages. I figured, just run yum install vim
works fine, but when I check if vim is installed, the check doesn't work. My workaround for now is to explicitly name the package without the alias when installing.
@schultyy Yip. To make things worse: Especially Debian likes to ship "Meta" packages that just depend on other packages. E.g.
$ dnf repoquery --whatrequires vim-common --alldeps
Last metadata expiration check performed 0:02:16 ago on Wed Oct 21 15:26:55 2015.
beakerlib-vim-syntax-0:1.10-2.fc22.noarch
nesc-0:1.3.5-2.fc22.x86_64
parrot-devel-0:6.10.0-2.fc22.i686
parrot-devel-0:6.10.0-2.fc22.x86_64
smaclient-0:1.1-4.fc22.x86_64
vim-X11-2:7.4.640-4.fc22.x86_64
vim-X11-2:7.4.827-1.fc22.x86_64
vim-clustershell-0:1.6-6.fc21.noarch
vim-command-t-0:1.10-6.fc22.x86_64
vim-enhanced-2:7.4.640-4.fc22.x86_64
vim-enhanced-2:7.4.827-1.fc22.x86_64
vim-go-0:1.1-1.fc22.noarch
vim-javabrowser-0:2.03-6.fc22.noarch
vim-jedi-0:0.7.0-7.fc22.noarch
vim-latex-0:1.8.23-14.20141116.812.gitd0f31c9.fc22.noarch
vim-nerdtree-0:4.2.0-11.fc21.noarch
vim-rnv-0:1.7.11-7.fc22.noarch
vim-taglist-0:4.6-9.fc22.noarch
@bascht How do other provisioners handle that?
@schultyy You don't wanna know. You really don't wanna know.
ORR ne, ne? What a mess @bascht ^
Welcome to my world.
Users can provide a list of packages they wish to have installed on the target system. In the easiest scenario, a user only provides the package name. Then it is installed with the latest available version. If a version is provided, it is installed in that version. Before a package is installed, there needs to be a check to see if it is already installed in the desired version or not. If yes, then no further action is required.