| 1 | # Copyright 1999-2008 Gentoo Foundation |
1 | # Copyright 1999-2008 Gentoo Foundation |
| 2 | # Distributed under the terms of the GNU General Public License v2 |
2 | # Distributed under the terms of the GNU General Public License v2 |
| 3 | # $Header: /var/cvsroot/gentoo-x86/eclass/elisp-common.eclass,v 1.49 2008/10/12 19:48:21 ulm Exp $ |
3 | # $Header: /var/cvsroot/gentoo-x86/eclass/elisp-common.eclass,v 1.50 2008/10/16 09:28:58 ulm Exp $ |
| 4 | # |
4 | # |
| 5 | # Copyright 2002-2004 Matthew Kennedy <mkennedy@gentoo.org> |
5 | # Copyright 2002-2004 Matthew Kennedy <mkennedy@gentoo.org> |
| 6 | # Copyright 2003 Jeremy Maitin-Shepard <jbms@attbi.com> |
6 | # Copyright 2003 Jeremy Maitin-Shepard <jbms@attbi.com> |
| 7 | # Copyright 2004-2005 Mamoru Komachi <usata@gentoo.org> |
7 | # Copyright 2004-2005 Mamoru Komachi <usata@gentoo.org> |
| 8 | # Copyright 2007-2008 Christian Faulhammer <opfer@gentoo.org> |
8 | # Copyright 2007-2008 Christian Faulhammer <opfer@gentoo.org> |
| … | |
… | |
| 35 | # An elisp file is compiled by the elisp-compile() function defined here and |
35 | # An elisp file is compiled by the elisp-compile() function defined here and |
| 36 | # simply takes the source files as arguments. The case of interdependent |
36 | # simply takes the source files as arguments. The case of interdependent |
| 37 | # elisp files is also supported, since the current directory is added to the |
37 | # elisp files is also supported, since the current directory is added to the |
| 38 | # load-path which makes sure that all files are loadable. |
38 | # load-path which makes sure that all files are loadable. |
| 39 | # |
39 | # |
| 40 | # elisp-compile *.el || die "elisp-compile failed" |
40 | # elisp-compile *.el || die |
| 41 | # |
41 | # |
| 42 | # Formerly, function elisp-comp() was used for compilation of interdependent |
42 | # Formerly, function elisp-comp() was used for compilation of interdependent |
| 43 | # elisp files. This usage is considered as obsolete. |
43 | # elisp files. This usage is considered as obsolete. |
| 44 | # |
44 | # |
| 45 | # Function elisp-make-autoload-file() can be used to generate a file with |
45 | # Function elisp-make-autoload-file() can be used to generate a file with |
| … | |
… | |
| 57 | # of elisp-install(). The following parameters are the files to be put in |
57 | # of elisp-install(). The following parameters are the files to be put in |
| 58 | # that directory. Usually the subdirectory should be ${PN}, you can choose |
58 | # that directory. Usually the subdirectory should be ${PN}, you can choose |
| 59 | # something else, but remember to tell elisp-site-file-install() (see below) |
59 | # something else, but remember to tell elisp-site-file-install() (see below) |
| 60 | # the change, as it defaults to ${PN}. |
60 | # the change, as it defaults to ${PN}. |
| 61 | # |
61 | # |
| 62 | # elisp-install ${PN} *.el *.elc || die "elisp-install failed" |
62 | # elisp-install ${PN} *.el *.elc || die |
| 63 | # |
63 | # |
| 64 | # To let the Emacs support be activated by Emacs on startup, you need |
64 | # To let the Emacs support be activated by Emacs on startup, you need |
| 65 | # to provide a site file (shipped in ${FILESDIR}) which contains the startup |
65 | # to provide a site file (shipped in ${FILESDIR}) which contains the startup |
| 66 | # code (have a look in the documentation of your software). Normally this |
66 | # code (have a look in the documentation of your software). Normally this |
| 67 | # would look like this: |
67 | # would look like this: |
| … | |
… | |
| 84 | # editor as they are loaded on every startup. When having a lot of Emacs |
84 | # editor as they are loaded on every startup. When having a lot of Emacs |
| 85 | # support files, users may be annoyed by the start-up time. Also avoid |
85 | # support files, users may be annoyed by the start-up time. Also avoid |
| 86 | # keybindings as they might interfere with the user's settings. Give a hint |
86 | # keybindings as they might interfere with the user's settings. Give a hint |
| 87 | # in pkg_postinst(), which should be enough. |
87 | # in pkg_postinst(), which should be enough. |
| 88 | # |
88 | # |
| 89 | # The naming scheme for this site file is "[0-9][0-9]*-gentoo.el", where the |
89 | # The naming scheme for this site-init file matches the shell pattern |
| 90 | # two digits at the beginning define the loading order. So if you depend on |
90 | # "[1-8][0-9]*-gentoo.el", where the two digits at the beginning define the |
|
|
91 | # loading order (numbers below 10 or above 89 are reserved for internal use). |
| 91 | # another Emacs package, your site file's number must be higher! |
92 | # So if you depend on another Emacs package, your site file's number must be |
|
|
93 | # higher! |
| 92 | # |
94 | # |
| 93 | # Best practice is to define a SITEFILE variable in the global scope of your |
95 | # Best practice is to define a SITEFILE variable in the global scope of your |
| 94 | # ebuild (right after DEPEND e.g.): |
96 | # ebuild (e.g., right after DEPEND): |
| 95 | # |
97 | # |
| 96 | # SITEFILE=50${PN}-gentoo.el |
98 | # SITEFILE=50${PN}-gentoo.el |
| 97 | # |
99 | # |
| 98 | # Which is then installed by |
100 | # Which is then installed by |
| 99 | # |
101 | # |
| … | |
… | |
| 376 | ;; Automatically generated by elisp-common.eclass |
378 | ;; Automatically generated by elisp-common.eclass |
| 377 | ;; DO NOT EDIT THIS FILE |
379 | ;; DO NOT EDIT THIS FILE |
| 378 | |
380 | |
| 379 | ;;; Code: |
381 | ;;; Code: |
| 380 | EOF |
382 | EOF |
|
|
383 | # Use sed instead of cat here, since files may miss a trailing newline. |
| 381 | cat "${sflist[@]}" </dev/null >>"${tmpdir}"/site-gentoo.el |
384 | sed '$q' "${sflist[@]}" </dev/null >>"${tmpdir}"/site-gentoo.el |
| 382 | cat <<-EOF >>"${tmpdir}"/site-gentoo.el |
385 | cat <<-EOF >>"${tmpdir}"/site-gentoo.el |
| 383 | |
386 | |
| 384 | (provide 'site-gentoo) |
387 | (provide 'site-gentoo) |
| 385 | |
388 | |
| 386 | ;; Local Variables: |
389 | ;; Local Variables: |
Parent Directory
| 
Revision Log
| 
Patch