Fix helm build problem.

Check
https://github.com/emacs-helm/helm/commit/0f031b903063deef835aa6767431a7905e63f3d8
and https://github.com/emacs-helm/helm/issues/633 for details.
* recipes/zeal-at-point.rcp: new recipe added.
* recipes/japanese-holidays.rcp: japanese-holidays
* recipes/insert-shebang.rcp: new recipe added
recipes/insert-shebang.rcp: add description/website fields
recipes/japanese-holidays.rcp: add description/website fields
recipes/elscreen.rcp: Change upstream to github
* recipes/quilt.el.rcp (quilt.el): new recipe.
* recipes/sane-term.rcp: new recipe sane-term.
* recipes/names.rcp: names new recipe.
* recipes/aggressive-indent-mode.rcp: new recipe aggressive-indent-mode
* recipes/evil-lisp-state.rcp: new recipe evil-lisp-state
* recipes/emms-netease.rcp: new recipe emms-netease.
* recipes/bf-mode.rcp: new recipe bf-mode
* recipes/orgtbl-show-header.rcp. new recipe orgtbl-show-header.
recipes/darcula-theme.rcp: new recipe added.
* recipes/gotham-theme.rcp: new recipe gotham-theme.
* recipes/shackle.rcp: new recipe shackle.
Create empty dir if no apt-get dir to symlink to

If the apt-get package doesn't contain any elisp files symlinking to the
non-existant /usr/share/emacs/site-lisp/<package> directory will leave
us with a broken link that will raise an error when we attempt to look
for autoloads, clean stale elc files and the like. In this case, simply
create an empty directory instead of a link.

* methods/el-get-apt-get.el (el-get-dpkg-symlink): call `make-directory'
  instead of symlink when `debdir' doesn't exist.
Warn if apt-get package installed no elisp

Using just message makes it too easy to overlook. The warning only
triggers on installation (not update or init) so it shouldn't be too
annoying.

* methods/el-get-apt-get.el (el-get-dpkg-symlink): use lwarn instead of
  message.
Always tell elpa about el-get activated packages

Previously we would only tell elpa about :type elpa packages, but this
doesn't work if some of the dependencies of an elpa package are not
themselves elpa packages. Since we already require all package names to
be unique, there should be no risk in telling elpa about all el-get
packages.

Also, checking for el-get installed :type elpa packages is not needed,
since any :type elpa package implicitly depends on package, so we can
just check the feature.

* el-get.el (el-get-do-init): always add package symbol to
  package-activated-list when (featurep 'package).