Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Install specific/older versions #6

Open
jacobsvante opened this issue Apr 12, 2016 · 4 comments
Open

Install specific/older versions #6

jacobsvante opened this issue Apr 12, 2016 · 4 comments

Comments

@jacobsvante
Copy link

It would be nice to be able to install specific versions of the extensions.

For example with the following syntax for the .yml package description:

homepage: http://postgis.net/
latest_version: 2.2.2
versions:
  - 2.2.2:
    url: http://download.osgeo.org/postgis/source/postgis-2.2.2.tar.gz
    sha1: f82fa96c4c73e8a94091b51f2e528a8146b03597
  - 2.2.1:
    url: http://download.osgeo.org/postgis/source/postgis-2.2.1.tar.gz
    sha1: 615f86c34ed4431383432d34f4b6d558c71fb94f

The default would be to use the latest available version when installing. To override you would do:

pex install [email protected]

With above syntax it would be easy to install multiple packages at different versions:

@jacobsvante jacobsvante changed the title pex install specific version Install specific versions Apr 12, 2016
@jacobsvante jacobsvante changed the title Install specific versions Install specific/older versions Apr 12, 2016
@petere
Copy link
Owner

petere commented Apr 18, 2016

The intended way to do that is to maintain a branch of the package description files with exactly the package versions you want.

@jacobsvante
Copy link
Author

So a branch with one file per version? How does one install from a specific branch in an easy way without knowing all the gritty details?

@petere
Copy link
Owner

petere commented May 3, 2016

Think of Homebrew. The master branch only provides the latest (or otherwise vetted) version, but if you want to have a different version or something, you edit the repository and store it in a private branch. The user interface to all this is not terribly elegant, but it's the way in general.

@jacobsvante
Copy link
Author

Yeah I know that's the way it works with homebrew. Personally I don't like their way of working with different versions, and I've run into issues countless of times when software has required different versions. Especially when it comes to PostgreSQL. But it's your project and your man-hours so the final call is obviously yours to make 😊

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants