From f97e374ac7cc2d7b7f6a4dc2ab5ea6989abd93ae Mon Sep 17 00:00:00 2001 From: David Glasser Date: Wed, 29 Oct 2014 18:10:49 -0700 Subject: [PATCH] Remove release methods from catalog.complete They are unused (and were accidentally introduced in 0.9.4 with the sqlite branch). The only thing you're allowed to query for releases is the official catalog, since the complete catalog doesn't actually augment releases with anything. (If we later implement some sort of "local release", we should probably also introduce a new release-specific interface that can be backed either by sqlite or by sqlite-plus-local, analogous to catalog. There's no real reason that it should be the same interface as catalog.) --- tools/catalog.js | 14 -------------- 1 file changed, 14 deletions(-) diff --git a/tools/catalog.js b/tools/catalog.js index acac81ac6f..1dc7bf88c4 100644 --- a/tools/catalog.js +++ b/tools/catalog.js @@ -200,20 +200,6 @@ _.extend(LayeredCatalog.prototype, { return this._returnFirst("getPackage", arguments, ACCEPT_NON_EMPTY); }, - // Returns general (non-version-specific) information about a - // release track, or null if there is no such release track. - getReleaseTrack: function (name) { - return this.otherCatalog.getReleaseTrack(name); - }, - - getReleaseVersion: function (track, version) { - return this.otherCatalog.getReleaseVersion(track, version); - }, - - getSortedRecommendedReleaseVersions: function (track, laterThanOrderKey) { - return this.otherCatalog.getSortedRecommendedReleaseVersions(track, laterThanOrderKey); - }, - getSortedVersions: function (name) { return this._returnFirst("getSortedVersions", arguments, ACCEPT_NON_EMPTY); },