Skip to content

Commit 383f6b4

Browse files
committed
Remove outdated Vagrantfile
It mentions Debian 10 (released in 2019) and Centos 7.9 (released in 2020). To put it mildly: it is unlikely to have been used recently.
1 parent 4eb62f5 commit 383f6b4

2 files changed

Lines changed: 0 additions & 175 deletions

File tree

CONTRIBUTING.rst

Lines changed: 0 additions & 37 deletions
Original file line numberDiff line numberDiff line change
@@ -101,43 +101,6 @@ Within the project, create a file: .vscode\\launch.json like below.
101101
]
102102
}
103103

104-
Building RPM and DEB packages
105-
-----------------------------
106-
107-
You will need Vagrant 1.7.2 or higher. In the project root there is a
108-
Vagrantfile that is setup to do multi-vm provisioning. If you're setting things
109-
up for the first time, then do:
110-
111-
::
112-
113-
$ version=x.y.z vagrant up debian
114-
$ version=x.y.z vagrant up centos
115-
116-
If you already have those VMs setup and you're merely creating a new version of
117-
DEB or RPM package, then you can do:
118-
119-
::
120-
121-
$ version=x.y.z vagrant provision
122-
123-
That will create a .deb file and a .rpm file.
124-
125-
The deb package can be installed as follows:
126-
127-
::
128-
129-
$ sudo dpkg -i pgcli*.deb # if dependencies are available.
130-
131-
or
132-
133-
$ sudo apt-get install -f pgcli*.deb # if dependencies are not available.
134-
135-
136-
The rpm package can be installed as follows:
137-
138-
::
139-
140-
$ sudo yum install pgcli*.rpm
141104

142105
Running the integration tests
143106
-----------------------------

Vagrantfile

Lines changed: 0 additions & 138 deletions
This file was deleted.

0 commit comments

Comments
 (0)