wbond/sublime_package_control — pull request #122 by rivy (2012-04-23 06:04:57+00:00)
Title: Added support for GitHub/BitBucket sub-repos in 'packages.json' files

* added optional use of GitHub or BitBucket single package providers as the source URL for individual packages within a generic package repository (packages.json)
* additionally, when using a GitHub or BitBucket package provider, 'version' becomes an optional parameter

RATIONALE: This modification adds an additional level of indirection which, if used while avoiding the optional 'version', allows for the creation of a more general 'packages.json' description file. This more generic 'packages.json' file would only need to be modified to add or remove package references; otherwise, it can remain unchanged while continuing to develop the individual packages.

In addition to the RATIONALE points, this set of modifications allows easier use of personal package forks (via the simpler 'packages.json' with decreased maintainence). And it helps avoid problematic repo base name collisions (as happens frequently when using a straight fork of a package for personal modifications). As the package names are set within 'packages.json', no 'package_name_map' is needed to accomplish the name disambiguation.

I was able to use this methodology to fork personal copies of a few Sublime Text packages and use them with the Package Manager simply by adding "https://raw.github.com/rivy/ST2.package-repo/master/packages.json" to "repositories" in the user settings.

For your evaluation...

Thanks for all the hard work getting this setup and working!

Roy Ivy III