Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 74909 - mod_lisp for Apache2 ebuild request
Summary: mod_lisp for Apache2 ebuild request
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Linux
: High enhancement (vote)
Assignee: Gentoo Lisp Project
URL: http://common-lisp.net/pipermail/mod-...
Whiteboard:
Keywords: EBUILD
Depends on:
Blocks:
 
Reported: 2004-12-18 22:43 UTC by Mesut Karatas
Modified: 2005-05-01 10:16 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
ebuild for mod_lisp2 (mod_lisp2.tgz,1.86 KB, application/octet-stream)
2005-01-25 15:52 UTC, Chris Austin-Lane
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Mesut Karatas 2004-12-18 22:43:32 UTC
mod_lisp2 for Apache2 has been released:
http://common-lisp.net/pipermail/mod-lisp-devel/2004-November/000044.html


Reproducible: Always
Steps to Reproduce:
1.
2.
3.
Comment 1 Chris Austin-Lane 2005-01-25 15:52:27 UTC
Created attachment 49518 [details]
ebuild for mod_lisp2

I made it www-apache/mod_lisp2 instead of using mod-lisp since the version 2
refers to apache not mod_lisp.	There's not a versioned download on the
maintainers website, so it's just mod_lisp2.c that goes into distfiles.  
I
--Chris @ austin-lane.net
Comment 2 Michael Stewart (vericgar) (RETIRED) gentoo-dev 2005-01-25 22:42:17 UTC
Please do not attach tarballs to bugs.
Comment 3 Matthew Kennedy (RETIRED) gentoo-dev 2005-01-27 10:57:29 UTC
Thanks for going to the trouble of putting this together, Chris.  I think a tar
archive in this instance is perfectly OK.

I think the Common Lisp Herd had better handle this bug as there are several other
ports in dev-lisp and more to come (UCW) which will depend on this.
Comment 4 Benedikt Böhm (RETIRED) gentoo-dev 2005-02-28 09:05:45 UTC
in cvs
Comment 5 Matteo Settenvini 2005-05-01 10:16:31 UTC
emerging mod_lisp always looks for 2.42, while you probably want 1.1 (which is the one for apache2).
can't we use the purposed "mod_lisp2" ebuild name? that would save many people from confusion (and from the need to mask >=mod_lisp-2 when what you want is the apache2 support, too).