File: control

package info (click to toggle)
foodcritic 8.1.0-1
  • links: PTS, VCS
  • area: main
  • in suites: stretch
  • size: 7,892 kB
  • ctags: 360
  • sloc: ruby: 7,300; makefile: 10
file content (50 lines) | stat: -rw-r--r-- 1,855 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
Source: foodcritic
Section: ruby
Priority: optional
Maintainer: Debian Ruby Extras Maintainers <pkg-ruby-extras-maintainers@lists.alioth.debian.org>
Uploaders: Stefano Rivera <stefanor@debian.org>
Build-Depends: chef,
               cucumber (>= 1.2.1),
               debhelper (>= 9),
               dpkg-dev (>= 1.18.8~),
               gem2deb,
               rake,
               ruby-aruba (>= 0.4.11),
               ruby-cucumber-core (>= 1.3),
               ruby-erubis,
               ruby-hashery,
               ruby-minitest (>= 3.3.0),
               ruby-nokogiri (>= 1.5.4),
               ruby-ronn,
               ruby-treetop (>= 1.4.10),
               ruby-yajl (>= 1.1.0)
Standards-Version: 3.9.8
Vcs-Git: https://anonscm.debian.org/git/pkg-ruby-extras/foodcritic.git
Vcs-Browser: https://anonscm.debian.org/cgit/pkg-ruby-extras/foodcritic.git
Homepage: http://www.foodcritic.io/
XS-Ruby-Versions: all

Package: foodcritic
Architecture: all
XB-Ruby-Versions: ${ruby:Versions}
Depends: ruby | ruby-interpreter,
         ruby-cucumber-core (>= 1.3),
         ruby-erubis,
         ruby-hashery,
         ruby-nokogiri (>= 1.5.4),
         ruby-treetop (>= 1.4.10),
         ruby-yajl (>= 1.1.0),
         ${misc:Depends},
         ${shlibs:Depends}
Suggests: chef
Description: lint tool for chef cookbooks
 Foodcritic has two goals:
 .
 To make it easier to flag problems in your Chef cookbooks that will cause Chef
 to blow up when you attempt to converge. This is about faster feedback. If you
 automate checks for common problems you can save a lot of time.
 .
 To encourage discussion within the Chef community on the more subjective stuff
 - what does a good cookbook look like? Opscode have avoided being overly
 prescriptive. Having a set of rules to base discussion on helps drive out what
 the community think is good style.