New ebuild for yasnippet. http://code.google.com/p/yasnippet/ yasnippet is yet another implementation of tempo/snippet. It seems to be very simple and very extensible. Reproducible: Always
Created attachment 147235 [details] yasnippet-0.4.4.ebuild
Created attachment 147237 [details] 50yasnippet-gentoo.el
Hi, thank you for contributing this. Please allow me some comments: 1. Is there any way to autoload the package? We made a large effort to get rid of almost all "require" and "load" statements in our site initialisation, and are therefore reluctant to add new ones. 2. The snippets are not elisp files and should therefore go to ${SITEETC}/${PN}/ (maybe omit the "snippets" directory level). 3. src_compile() and the empty DEPEND/RDEPEND assignments are redundant. 4. yasnippet.el says GPL-2, and so does your ebuild. But the homepage says "MIT License". Which one is right? 2.-4. should be easy to fix. Not sure about 1. Maybe we can autoload functions yas/initialize and yas/load-directory, and let the ebuild output a message that the user should initialize it in his .emacs?
Created attachment 147395 [details] yasnippet-0.4.4.ebuild Thanks for comments. I fixed like: 1. Now site file just defines yas/initialize autoload function. An user can use yasnippet according to pkg_postinst messages if necessary. 2. Done except for omitting snippets directory. I think we should keep it. 3. Done. 4. Sorry, I forgot to fix it.
Created attachment 147396 [details] 50yasnippet-gentoo.el
Thanks. But I overlooked: 5. Use ${P} in SRC_URI. (No need to repost the ebuild. I will add it to the Emacs overlay later and fix this small problem myself.)
Committed to Emacs overlay. I have also added a "doc" USE flag that installs the HTML documentation. However, looking at the source I found that it contains a bundled copy of dropdown-list.el (see <http://www.emacswiki.org/cgi-bin/wiki/dropdown-list.el>) which is even included inline in the one elisp file. So we would have namespace collisions if we ever decided to add dropdown-list as a package. So, before yasnippet can go into Portage, you should ask upstream to either unbundle dropdown-list (which I would prefer), or to rename the respective functions of the inlined code. Therefore, resolving as CANTFIX for the time being. Please reopen when the above issue is fixed.
Created attachment 151017 [details] yasnippet-0.5.2.ebuild
Created attachment 151018 [details] dropdown-list-20080316.ebuild
Created attachment 151019 [details] dropdown-list/dropdown-list-20080316.el.bz2
Yasnippet developers still have a intention to include dropdown-list.el. http://code.google.com/p/yasnippet/issues/detail?id=18&can=1 So, I * created a ebuild for dropdown-list.el * made yasnippet-0.5.2 depend on the dropdown-list.el ebuild * add a workaround to avoid namespace collision by cut dropdown-list.el part from yasnippet.el I don't know what is the best way. Please review.
Created attachment 151022 [details] dropdown-list-20080316.ebuild
This looks good, thank you. Committed to Emacs overlay, with minor modifications. I've also added a site-init file for dropdown-menu.
> I've also added a site-init file for dropdown-menu. For dropdown-list, of course.
app-emacs/dropdown-list-20080316 and app-emacs/yasnippet-0.5.5 committed to Portage tree. Thank you for the contribution.
