Skip to content

Conversation

@Alloyed
Copy link
Contributor

@Alloyed Alloyed commented Jun 12, 2015

When a versioned rocks tree and a non-versioned rocks tree coexist, prefer the versioned one.

  • On a machine with a single rocks tree, versioned or no, this has no effect.
  • On a machine with both, and the unversioned tree points to the right
    lua version, this has no effect.
  • But on a machine where the unversioned tree points to another version
    of lua, the right manifest file will be read instead of the wrong one.

This patch resolves a problem I posted to the mailing list where datafile wasn't generating the paths needed to find my luarocks-installed templates: Since luarocks installed them to a directory with my package version in it, datafile would have needed the correct manifest to find it, and since it was actually finding a manifest, just not the right one, it gave no outward error.

When a versioned rocks tree and a non-versioned rocks tree coexist,
prefer the versioned one.

* On a machine with a single rocks tree, versioned or no, this has no effect.
* On a machine with both, and the unversioned tree points to the right
  lua version, this has no effect.
* But on a machine where the unversioned tree points to another version
  of lua, the right manifest file will be read instead of the wrong one.
hishamhm added a commit that referenced this pull request Jun 12, 2015
Check for manifest in versioned rocks trees first
@hishamhm hishamhm merged commit 0bbade2 into hishamhm:master Jun 12, 2015
@hishamhm
Copy link
Owner

Good catch! Thank you!!

@hishamhm
Copy link
Owner

I uploaded version 0.2 to luarocks.org, including this patch.

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

Successfully merging this pull request may close these issues.

2 participants