[caffe-contrib] 05/09: README.Debian: temporarily remove

[Zhou Mo]

This is an automated email from the git hooks/post-receive script.

cdluminate-guest pushed a commit to branch master
in repository caffe-contrib.

commit 45119dc5920175d317a97853da3865072debbbcc
Author: Zhou Mo <cdluminate at gmail.com>
Date:   Mon Jul 4 13:36:36 2016 +0000

    README.Debian: temporarily remove
---
 debian/README.Debian | 126 ---------------------------------------------------
 1 file changed, 126 deletions(-)

diff --git a/debian/README.Debian b/debian/README.Debian
deleted file mode 100644
index 9094c05..0000000
--- a/debian/README.Debian
+++ /dev/null
@@ -1,126 +0,0 @@
-                   Caffe for Debian
-                   ================
-
- In short, package "Caffe" for Debian is compiled as 2 sets of packages,
- but the two sets are not co-installable. [1]
-
-  + Caffe-CPU: (configured as CPU_ONLY)
-
-    * caffe-cpu          -- command line utilities
-    * libcaffe-cpu*      -- core library
-    * libcaffe-cpu-dev   -- development files
-    * python-caffe-cpu   -- python2 interface
- 
-  + Caffe-CUDA: (compiled with CUDA)
-
-    * caffe-cuda
-    * libcaffe-cuda*
-    * libcaffe-cuda-dev
-    * python-caffe-cuda
-
- Happy Deep Learning ! :-)
-
-
-                   Custom Build of Caffe
-                   =====================
-
- If you'd like to build Caffe by yourself, I suggest that you build it
- with the `custom-*` targets instead of the standard `dpkg-buildpackage`
- process, so that you can avoid compiling Caffe twice. Besides, Compiling
- caffe locally may potentially bring a better machine performance.
- Inspired by Debian's OpenBLAS packaging, I provid 2 custom targets for
- users to build customized caffe Packages for local use:
-
-  * custom-cpu
-  * custom-cuda
-
- Following is instruction for doing such a custom build:
-
-  1. Install Build-Dependencies, including Debian packaging utils.
-
-     * Packaging helpers:
-
-        $ apt install build-essential debhelper devscripts
-
-     * Build-Dependencies:
-
-        $ apt-get build-dep caffe
-
-    Or install build-dependencies manually, the dependency information
-    is stored at the top part of `debian/control`.
-
-  2. [Optional] Read the configuration template at the top part of
-     debian/rules, then have a look at the bottom part of this file. 
-     Tweak some options as long as you need. (`debian/rules` is a Makefile)
-     Here are some hints:
-
-     * CUSTOM_JOBS   := "-j5"
-
-       Parallel compiling jobs, i.e. make -j5
-
-     * CONFFLAG_CPU_CUSTOM = ...
-
-       Tweak this when you like to compile the caffe-cpu set,
-       and this variable stores cmake options.
-
-     * CONFFLAG_CUDA_CUSTOM = ...
-
-       Tweak this when you like to compile the caffe-cuda set,
-       and this variable stores cmake options.
-
-  3. Choose a configuration and start compiling.
-     (make sure you are in the root of source tree)
-
-     To compile caffe-cpu set:
-
-       $ debian/rules custom-cpu
-
-     To compile caffe-cuda set:
-
-       $ debian/rules custom-cuda
-
-     The default custom configuration is tested by me, however
-     there's no promise that the custom build will always work.
-     Suggestion is welcome :-)
-
-  4. Installing freshly cooked Caffe Packages
-
-     * Check the resulting packages
-
-        $ ls ../*.deb
-
-     * If nothing went wrong, install them. [2]
-
-        $ sudo dpkg -i libcaffe-*.deb
-        $ sudo dpkg -i <others>
-
-  5. Grab some datasets, set up your network and have fun.
-
-                   Notes for Package Maintainer
-                   ============================
-
-1. Testing whether the program works, apart from the test programs?
-
-     $ caffe time -model examples/mnist/lenet.prototxt
-
-   or with gpu
-
-     $ caffe time -model examples/mnist/lenet.prototxt -gpu 0
-
-   Well, testing caffe in this way (using deploy version of network)
-   requires no dataset, which may be useful for some maintainers
-   who are not familiar with Caffe.
-
-                   Footnotes
-                   =========
-
-[1] It's nonsence to install caffe-cpu and caffe-cuda together.
-    caffe-cuda can work under CPU_ONLY mode.
-
-[2] Make sure to firstly install libcaffe-* which includes libcaffe.so.*,
-    the shared object file of caffe, or you will get some error messages
-    from dpkg (dependency unsatisfied). However that would NOT be hurt
-    if you didn't follow.
-
-[A]
- -- Zhou Mo <cdluminate at gmail.com>  Sun, 16 Apr 2016 00:00:00 +0000

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/debian-science/packages/caffe-contrib.git