ChannelRepositoryTools
A Sublime Text package for working with channels and repositories
Details
Installs
- Total 7K
- Win 3K
- Mac 2K
- Linux 1K
| Dec 21 | Dec 20 | Dec 19 | Dec 18 | Dec 17 | Dec 16 | Dec 15 | Dec 14 | Dec 13 | Dec 12 | Dec 11 | Dec 10 | Dec 9 | Dec 8 | Dec 7 | Dec 6 | Dec 5 | Dec 4 | Dec 3 | Dec 2 | Dec 1 | Nov 30 | Nov 29 | Nov 28 | Nov 27 | Nov 26 | Nov 25 | Nov 24 | Nov 23 | Nov 22 | Nov 21 | Nov 20 | Nov 19 | Nov 18 | Nov 17 | Nov 16 | Nov 15 | Nov 14 | Nov 13 | Nov 12 | Nov 11 | Nov 10 | Nov 9 | Nov 8 | Nov 7 | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Windows | 0 | 1 | 1 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 1 | 3 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 |
| Mac | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 2 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 |
| Linux | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 1 |
Readme
- Source
- raw.githubusercontent.com
ChannelRepositoryTools
A Sublime Text package for working with channels and repositories. Functionality includes:
- Testing the default channel
- Testing a local repository JSON file
- Testing a remote repository JSON URL
- Upgrading a local repository JSON file
Installation
Installation is performed via Package Control.
Usage
This package was designed to work with the default Package Control channel. Before using this package, it is necessary to:
- Fork https://github.com/wbond/package_control_channel
- Clone your fork of package_control_channel using Git
- Open package_control_channel in Sublime Text
Testing the Default Channel
Most users will want to open the command palette and type:
ChannelRepositoryTools: Test Default Channel
This will test the channel and the main repository.
Testing the Default Channel with Remote Repositories
If you are working on cleaning up the default channel and making sure everything
is in good shape, you‘ll want to run the full test suite on the channel and
all remote repositories that are schema_version 2.0 or newer:
ChannelRepositoryTools: Test Default Channel (including Remote Repositories)
Repositories running an older version of the schema will not be tested, but should be upgraded to the newest version by following the instructions in the Upgrading a Repository JSON File section.
Testing a Repository via URL
To test a repository hosted on a publicly-accessible URL, run the command:
ChannelRepositoryTools: Test Remote Repository
You will be prompted to enter the URL of the repository. The JSON file will be downloaded and tested against the test suite.
Testing a Repository via a File
To test a repository JSON file on your machine, open it in Sublime Text and run the command:
ChannelRepositoryTools: Test Local Repository (Current File)
Upgrading a Repository JSON File
If you open a repository JSON file in Sublime Text, you can upgrade it from
schema_version 1.0, 1.1 or 1.2 by running the command:
ChannelRepositoryTools: Upgrade Repository Schema (Current File)
This will update the JSON to schema_version 2.0. You may be prompted with
some additional information, such as instructions to create a tag via GitHub
or BitBucket.
You very likely will also be told that your package information should be moved
into the default repository which is part of the default channel. The repository
is made up of the JSON files in the /repository/ folder of the
package_control_channel.
Most users who has custom packages.json files did so because of limitations to
older versions of Package Control. With schema_version 2.0 it is now
possible to limit packages to specific operating system and more without
maintaining your own packages.json file.
The new method has all details located in the repository, and new releases are
created by you making tags in your repository. As long as a tag is in the form
MAJOR.MINOR.PATCH (a SemVer verison number), Package
Control will automatically find it the next time your repo is crawled. It will
then be made available to users.
Whenever possible, please take the time to move your package into the default repository so that the crawler can more efficiently check packages for updates.