Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/kenhys/dcs-debian
Search debian/ files which contains specific keyword from Debian Code Search (http://codesearch.debian.net).
https://github.com/kenhys/dcs-debian
Last synced: 17 days ago
JSON representation
Search debian/ files which contains specific keyword from Debian Code Search (http://codesearch.debian.net).
- Host: GitHub
- URL: https://github.com/kenhys/dcs-debian
- Owner: kenhys
- License: mit
- Created: 2014-11-08T13:34:38.000Z (about 10 years ago)
- Default Branch: master
- Last Pushed: 2014-11-23T05:22:13.000Z (almost 10 years ago)
- Last Synced: 2024-05-02T01:06:17.329Z (7 months ago)
- Language: Ruby
- Homepage:
- Size: 449 KB
- Stars: 0
- Watchers: 3
- Forks: 1
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# dcs-debian
Dcs-debian is the command line tool which uses Debian Code Search to search debian/ files.
When working on Debian ITP, lintian sometimes reports pile of warnings or errors.
In such a case, I wonder how to fix this issue. How does other packages fix it?This is the reason why I've created dcs-debian as thin wrapper of
Debian Code Search (http://codesearch.debian.net).![Screenshot of dcs-debian](https://github.com/kenhys/dcs-debian/blob/master/screenshot.png)
## Installation
Install it yourself as:
$ gem install dcs-debian
## Usage
Here is the usage of dcs-debian:
$ dcs-debian
Commands:
dcs-debian changelog KEYWORD #
dcs-debian control KEYWORD #
dcs-debian help [COMMAND] # Describe available commands or one specific command
dcs-debian rules KEYWORD #Just type specific keyword like this:
$ dcs-debian rules groonga
$ dcs-debian changelog closed
$ dcs-debian control Standards## Contributing
1. Fork it ( https://github.com/kenhys/dcs-debian/fork )
2. Create your feature branch (`git checkout -b my-new-feature`)
3. Commit your changes (`git commit -am 'Add some feature'`)
4. Push to the branch (`git push origin my-new-feature`)
5. Create a new Pull Request