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.

Sign up for GitHub

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

Jump to bottom

Specifying Julia version dependency for packages #2315

Closed
dirk opened this issue Feb 15, 2013 · 3 comments
Closed

Specifying Julia version dependency for packages #2315

dirk opened this issue Feb 15, 2013 · 3 comments
Labels
domain:packages Package management and loading status:priority This should be addressed urgently

Comments

@dirk
Copy link
Member

dirk commented Feb 15, 2013

Currently there is no way to specifying the version of Julia on which a package depends. Should this be introduced as a special line in each package's REQUIRES or in a different file?
@JeffBezanson
Copy link
Sponsor Member

I think this issue will be urgent very soon. As julia starts to diverge for v0.2, package maintainers will want to update packages while keeping some version of them working with v0.1. cc @StefanKarpinski

@ViralBShah
Copy link
Member

This is already urgent right now, as we already have two versions - users who will be on 0.1 as soon as binaries are released, and developers who are on master. 0.1 users need to be able to pull packages that are compatible with the released version, whereas people on master will want to pull the latest and greatest.

I am already running 0.1 and master on ubuntu 13.04.

timholy referenced this issue Feb 23, 2013
@timholy
Bait someone into fixing dev/release branch version testing
52fa877 
Because it's presumably too late to get this into Ubuntu's
release-0.1, package authors should define the following function:

function branch()
  local jbranch
  try
      jbranch = Base.branch()
  catch
      jbranch = VERSION
  end
  jbranch
end

Alternatively, bumping the VERSION file to 0.2.0-pre (or whatever
syntax it needs) seems like a better approach. But currently both
release-0.1 and master claim to be 0.1.0, which seemingly makes it
impossible to know what branch you're on.
This was referenced Feb 26, 2013
Closed
Closed
@StefanKarpinski
Copy link
Sponsor Member

Close by a97bf76.

@ViralBShah ViralBShah mentioned this issue Mar 3, 2013
Closed
StefanKarpinski added a commit that referenced this issue Mar 7, 2013
@StefanKarpinski
Pkg: don't rely on submodule for determining which are packages [#2315].
7d62cc3 
This is a small, hopefully non-invasive step towards relegating submodules
to a snapshotting mechanism, rather than a first-class part of the way Pkg
works. Hopefully this cures some of what's ailing us.
StefanKarpinski added a commit that referenced this issue Mar 7, 2013
@StefanKarpinski
Pkg: don't rely on submodule for determining which are packages [#2315].
52bc1e4 
This is a small, hopefully non-invasive step towards relegating submodules
to a snapshotting mechanism, rather than a first-class part of the way Pkg
works. Hopefully this cures some of what's ailing us.

Conflicts:
	test/Makefile
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
domain:packages Package management and loading status:priority This should be addressed urgently
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@dirk @StefanKarpinski @ViralBShah @JeffBezanson