Skip to content
This repository
Browse code

Generates 4 diferent debian packages: libonion, libonion-dev, libonio…

…n-examples, libonion-tools.

Still some problems with compilerunloop.
  • Loading branch information...
commit 1f38640beff0763b5e24f05b7afdf254661a3793 1 parent 6a4f53b
David Moreno Montero authored
36 debian/control
@@ -52,3 +52,39 @@ Description: HTTP server library
52 52 plugin to add some functionality. With libonion you have the functionality
53 53 and add the webserver as a plugin.
54 54
  55 +Package: libonion-examples
  56 +Section: libs
  57 +Architecture: any
  58 +Depends: ${shlibs:Depends}, ${misc:Depends}
  59 +Description: HTTP server library -- Examples
  60 + Onion plans to be a lightweight C library that facilitate to create simple
  61 + HTTP servers.
  62 + .
  63 + The use case is an existing application, or a new one, that needs some HTTP
  64 + interconnection with the world. It uses the library to add some handlers for
  65 + specific URLs and generate and serve the dynamic data as needed.
  66 + .
  67 + It also has security goals (SSL support) so that you just concentrate on what
  68 + you want to serve, and serve it.
  69 + .
  70 + Its not a web server per se, as it is not an executable.
  71 + .
  72 + If you want to compare to a web server, a web server would use a module or
  73 + plugin to add some functionality. With libonion you have the functionality
  74 + and add the webserver as a plugin.
  75 +
  76 +Package: libonion-tools
  77 +Section: libs
  78 +Architecture: any
  79 +Depends: ${shlibs:Depends}, ${misc:Depends}
  80 +Description: HTTP server library -- Tools
  81 + Onion plans to be a lightweight C library that facilitate to create simple
  82 + HTTP servers.
  83 + .
  84 + This includes the tools used to help onion developments (and maybe others):
  85 + .
  86 + * opack -- Prepares a file to be embedded into an onion powered server executable
  87 + * crl -- Do the compile/run loop, checking source files; as modified the executable
  88 + is stopped and the loop starts again.
  89 +
  90 +
2  debian/docs
... ... @@ -1,3 +1 @@
1   -CMakeLists.txt
2   -err.txt
3 1 README.rst
1  debian/libonion-dev.install
... ... @@ -1,4 +1,3 @@
1 1 usr/include/*
2 2 usr/lib/lib*.a
3   -usr/lib/lib*.so
4 3 usr/share/cmake/*
4 debian/libonion-examples.install
... ... @@ -0,0 +1,4 @@
  1 +usr/bin/interactive
  2 +usr/bin/fileserver
  3 +usr/bin/oterm
  4 +usr/bin/otop
2  debian/libonion-tools.install
... ... @@ -0,0 +1,2 @@
  1 +usr/bin/opack
  2 +#usr/bin/crl
1  debian/libonion1.install → debian/libonion.dirs
... ... @@ -1 +1,2 @@
1 1 usr/lib/lib*.so.*
  2 +usr/lib/lib*.so
1  debian/libonion.install
... ... @@ -0,0 +1 @@
  1 +usr/lib/lib*.so
1  debian/libonion1.dirs
... ... @@ -1 +0,0 @@
1   -usr/lib
6 tools/compilerunloop/CMakeLists.txt
... ... @@ -1,5 +1,5 @@
1   -ADD_CUSTOM_TARGET(TARGET clr ALL DEPENDS ${CMAKE_CURRENT_SOURCE_DIR}/compilerunloop.sh
2   - COMMAND cp ${CMAKE_CURRENT_SOURCE_DIR}/compilerunloop.sh ${CMAKE_CURRENT_BINARY_DIR}/clr
  1 +ADD_CUSTOM_TARGET(TARGET crl ALL DEPENDS ${CMAKE_CURRENT_SOURCE_DIR}/compilerunloop.sh
  2 + COMMAND cp ${CMAKE_CURRENT_SOURCE_DIR}/compilerunloop.sh ${CMAKE_CURRENT_BINARY_DIR}/crl
3 3 )
4 4
5   -INSTALL(FILES clr DESTINATION bin PERMISSIONS OWNER_WRITE OWNER_READ GROUP_READ WORLD_READ OWNER_EXECUTE GROUP_EXECUTE WORLD_EXECUTE)
  5 +#INSTALL(FILES crl DESTINATION bin PERMISSIONS OWNER_WRITE OWNER_READ GROUP_READ WORLD_READ OWNER_EXECUTE GROUP_EXECUTE WORLD_EXECUTE)

0 comments on commit 1f38640

Please sign in to comment.
Something went wrong with that request. Please try again.