Skip to content
This repository has been archived by the owner on Jan 16, 2025. It is now read-only.

Multiple versions of the same project? #84

Closed
dbr opened this issue Oct 5, 2009 · 6 comments
Closed

Multiple versions of the same project? #84

dbr opened this issue Oct 5, 2009 · 6 comments

Comments

@dbr
Copy link
Contributor

dbr commented Oct 5, 2009

I'd like to create a Python 3.1 formula. It (by default) doesn't interfere with the current stable Python (2.6.x), as it creates a "python3" executable rather than "python"

Would I just name the formula "python3"?

On a related note, although less important, I'd also like to create formulas for older versions of Python (specifically 0.9.1, then a few of the older 1.x and 2.x) to test compatibility with old versions.. I could just create a "python0.9.1" formula, and a "python1.5" formula and so on, but this would get very messy..

How should these by dealt with?

@rrouse
Copy link

rrouse commented Oct 5, 2009

Here are my views on this one.

You could modify the forumla stucture to have one giant forumla file per application that has multiple versions in it that could be called via something like brew install python --version 0.9.1.

The other way, that I like more, is to change the Forumla directory to contain one folder per application. Inside that folder, you'd have multiple forumlas, each containing one version and named after the version (e.g. python/0.9.1.rb). The formula named after the app name (python.rb), would be the default one run when you do brew install python. You could install other versions by doing it like above (brew install python --version 0.9.1).

@dbr
Copy link
Contributor Author

dbr commented Oct 6, 2009

Hmm.. That sounds like it could work nicely, especially because homebrew's Cellar path already containing the version..

Basically, when brew install blah is run, it looks for formula/blah.rb, then foruma/blah/blah.rb. If the --version 0.9.1 flag is used, it looks for a file named formula/blah/0.9.1.rb` ?

I still think Python 3 should be a separate formula for now, as would be extremely common to have both 2.x and 3.x installed a the same time (but the above would be the "correct" way to do multiple versions)

@rrouse
Copy link

rrouse commented Oct 6, 2009

We'll have to wait and see what mxcl has to say about it then :) Hop on the IRC channel (#machomebrew) and point him this way.

@mxcl
Copy link
Contributor

mxcl commented Oct 6, 2009

Our plan is something along the lines of:

  • Homebrew holds the formula for the current stable formula
  • We allow people to easily add formula from other git repositories
  • People host formula for less popular versions or configurations
  • We make web services that make it easy to search for these additional formula

At least for now name the formula python.rb

@mxcl
Copy link
Contributor

mxcl commented Oct 6, 2009

This would also work for other forks of homebrew or other branches on other forks here at github.

@adamv
Copy link
Contributor

adamv commented Jul 20, 2010

There are now "Python" (2.7.x) and "Python3" (3.1.x) formulae. Because Python 3 explicitly identifies itself as such, as specifically does not conflict with Python 2, I've included both versions.

This doesn't solve the problem of using previous versions of either, though. Multi-repo and possible multi-version support are being thought about for future versions.

ClashTheBunny pushed a commit to ClashTheBunny/homebrew that referenced this issue Jan 22, 2015
lumaxis pushed a commit to lumaxis/homebrew that referenced this issue Feb 17, 2015
Python support in Homebrew is tricky to get right, and the way the
most-recent versions of Python 2.7.x and 3.x are handled in core
change over time.

These older versions of Python have not kept up-to-date with these
layout changes, and have installation problems as-is.

In addition, these versions may not be getting important security
updates any more.

Removing these from the versions repo; if they are still needed
by any users they should be handled in a (different) external tap.

Closes Homebrew#84.
Closes Homebrew#62.
Closes Homebrew#229.
Closes Homebrew#167.
Closes Homebrew#27208
@Homebrew Homebrew locked and limited conversation to collaborators Feb 16, 2016
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants