File: control

package info (click to toggle)
camping 3.2.6-1
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 1,312 kB
  • sloc: ruby: 5,032; javascript: 2,362; makefile: 29
file content (51 lines) | stat: -rw-r--r-- 1,757 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
51
Source: camping
Section: web
Priority: optional
Maintainer: Debian Ruby Team <pkg-ruby-extras-maintainers@lists.alioth.debian.org>
Uploaders: Paul van Tilburg <paulvt@debian.org>
Build-Depends: debhelper-compat (= 13),
               gem2deb,
               ruby-activesupport,
               ruby-mab,
               ruby-minitest,
               ruby-minitest-reporters,
               ruby-minitest-hooks,
               ruby-minitest-global-expectations,
               ruby-mysql2,
               ruby-rack-test,
               ruby-tilt,
               ruby-rack-session,
               ruby-rackup,
               ruby-kdl,
               ruby-listen,
               ruby-ruby-parser,
               ruby-dry-logger,
               ruby-zeitwerk,
               racc
Standards-Version: 4.7.2
Homepage: https://github.com/camping/camping
Vcs-Git: https://salsa.debian.org/ruby-team/camping.git
Vcs-Browser: https://salsa.debian.org/ruby-team/camping
Testsuite: autopkgtest-pkg-ruby

Package: camping
Architecture: all
Depends: fonts-lato,
         libjs-jquery,
         ruby,
         ruby-kdl,
         ruby-listen,
         ruby-dry-logger,
         ${misc:Depends},
         ${ruby:Depends},
         ${shlibs:Depends}
Recommends: ruby-activerecord,
            ruby-mab | ruby-tilt,
            ruby-sqlite3
Suggests: thin
Description: small Ruby web framework for Model-View-Controller type applications
 Camping is a web framework which consistently stays at less than 4kb of
 code. The idea here is to store a complete fledgling web application
 (written in Ruby) in a single file like many small CGIs, but to organize
 it as a Model-View-Controller application like Rails does. You can then
 easily move it to Rails once you've got it going.