clisp [PSARC/2009/141 FastTrack timeout 03/05/2009]

2009-03-05 Thread zheng he - Sun Microsystems - Beijing China
Jim Walker ??:
 This case was approved at todays PSARC meeting.

 Cheers,
 Jim
Thank you!!!

-Charles He



clisp [PSARC/2009/141 FastTrack timeout 03/05/2009]

2009-03-04 Thread Jim Walker
Rick Matthews wrote:
 Are we supporting a particular version of clisp? The community appears 
 to be very active.

The project team will be delivering the current clisp version 2.47.

I'll update the checklist.

Cheers,
Jim



clisp [PSARC/2009/141 FastTrack timeout 03/05/2009]

2009-03-04 Thread Rick Matthews
Backing up the verbal +1

Jim Walker wrote:
 Rick Matthews wrote:
 Are we supporting a particular version of clisp? The community 
 appears to be very active.

 The project team will be delivering the current clisp version 2.47.

 I'll update the checklist.

 Cheers,
 Jim


-- 
-
Rick Matthews   email: Rick.Matthews at sun.com
Sun Microsystems, Inc.  phone:+1(651) 554-1518
1270 Eagan Industrial Road  phone(internal): 54418
Suite 160   fax:  +1(651) 554-1540
Eagan, MN 55121-1231 USAmain: +1(651) 554-1500  
-




clisp [PSARC/2009/141 FastTrack timeout 03/05/2009]

2009-03-04 Thread Jim Walker
This case was approved at todays PSARC meeting.

Cheers,
Jim



clisp [PSARC/2009/141 FastTrack timeout 03/05/2009]

2009-03-03 Thread Rick Matthews
Are we supporting a particular version of clisp? The community appears 
to be very
active.
--
Rick

James Walker wrote:
 I'm sponsoring this familiarity case for Charles He. The requested
 release binding is minor. The man page has been posted in the
 materials directory.

 Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI
 This information is Copyright 2009 Sun Microsystems
 1. Introduction
 1.1. Project/Component Working Name:
clisp
 1.2. Name of Document Author/Supplier:
Author:  Charles He
 1.3  Date of This Document:
   26 February, 2009
 4. Technical Description
 clisp Check List
 1.0 Project Information
 1.1 Name of project/component
 clisp

 1.2 Author of document
 Zheng.he at Sun.COM

 2.0 Project Summary
   2.1 Project Description
 Common Lisp is a high-level, general-purpose, object-oriented, dynamic,
 functional programming language.

 CLISP is a Common Lisp implementation by Bruno Haible, then of Karlsruhe
 University, and Michael Stoll, then of Munich University, both in Germany.
 It implements the language described in the ANSI Common Lisp standard with
 many extensions.

 CLISP includes an interpreter, a compiler, a debugger, CLOS, MOP, a 
 foreign
 language interface, i18n, POSIX and Perl regular expressions, a socket
 interface, fast bignums, arbitrary precision floats, and more. An X11
 interface is available through CLX, Garnet and CLUE/CLIO. Command line
 editing is provided by readline. CLISP runs Maxima, ACL2 and many other
 Common Lisp packages.  

   2.2 Release binding
   What is is the release binding?
   (see http://opensolaris.org/os/community/arc/policies/release-taxonomy/)
   [ ] Major
   [*] Minor
   [ ] Patch or Micro
   [ ] Unknown -- ARC review required

   2.3 Type of project
   Is this case a Linux Familiarity project?
   [*] Yes
   [ ] No

   2.4 Originating Community
 2.4.1 Community Name
   GNU  CLISP
 2.4.2 Community Involvement
   Indicate Sun's involvement in the community
   [ ] Maintainer
   [ ] Contributor
   [*] Monitoring
   
   Will the project team work with the upstream community to resolve
   architectural issues of interest to Sun?
   [*] Yes 
   [ ] No - briefly explain
   
   Will we or are we forking from the community?
   [ ] Yes - ARC review required prior to forking
   [*] No
   
 3.0 Technical Description
   3.1 Installation  Sharable
 3.1.1S Solaris Installation - section only required for Solaris Software
   (see 
 http://opensolaris.org/os/community/arc/policies/install-locations/ for 
 details)
   Does this project follow the Install Locations best practice?
   [*] Yes 
   [ ] No - ARC review required
   
   Does this project install into /usr under 
 [sbin|bin|lib|include|man|share]?
   [*] Yes
   [ ] No or N/A
   
   Does this project install into /opt?
   [ ] Yes - explain below
   [*] No or N/A
   
   Does this project install into a different directory structure?
   [ ] Yes - ARC review required
   [*] No or N/A
   
   Do any of the components of this project conflict with anything under 
 /usr?
   (see http://opensolaris.org/os/community/arc/caselog/2007/047/ for 
 details)
   [ ] Yes - explain below
   [*] No
   
   If conflicts exist then will this project install under /usr/gnu?
   [ ] Yes
   [ ] No - ARC review required
   [*] N/A
   
   Is this project installing into /usr/sfw?
   [ ] Yes - ARC review required
   [*] No
   
 3.1.1W Windows Installation - section only required for Windows Software
   (see http://sac.sfbay/WSARC/2002/494 for details)
   Does this project install software into a 
   system drive:\Program Files\Sun\product or system 
 drive:\Sun\product
   directory?
   [ ] Yes
   [ ] No - ARC review required
   
   Does the project use the Windows registry?
   [ ] Yes
   [ ] No - ARC review required
   
   Does the project use 
   HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\product\version
   for the registry key?
   [ ] Yes
   [ ] No - ARC review required
   
   Is the project's stored location
   HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\product id\version 
 id\Path?
   [ ] Yes
   [ ] No - ARC review required
   
 3.1.2 Share and Sharable
   Does the module include any components that are used or shared by 
   other projects?
   [*] Yes
   [ ] No
 
   If yes are these components packaged to be shared with the other FOSS?
   [*] Yes
   [ ] No - ARC review required
   [ ] N/A
 
   Are these components already in the Solaris WOS?
   [ ] Yes
   [*] No - continue with next section (section 3.2)
 
   If yes are these newer versions being 

clisp [PSARC/2009/141 FastTrack timeout 03/05/2009]

2009-02-27 Thread Garrett D'Amore
You've indicated that clisp installs setuid programs.  Why?  Please 
provide more detail.

-- Garrett

James Walker wrote:
 I'm sponsoring this familiarity case for Charles He. The requested
 release binding is minor. The man page has been posted in the
 materials directory.

 Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI
 This information is Copyright 2009 Sun Microsystems
 1. Introduction
 1.1. Project/Component Working Name:
clisp
 1.2. Name of Document Author/Supplier:
Author:  Charles He
 1.3  Date of This Document:
   26 February, 2009
 4. Technical Description
 clisp Check List
 1.0 Project Information
 1.1 Name of project/component
 clisp

 1.2 Author of document
 Zheng.he at Sun.COM

 2.0 Project Summary
   2.1 Project Description
 Common Lisp is a high-level, general-purpose, object-oriented, dynamic,
 functional programming language.

 CLISP is a Common Lisp implementation by Bruno Haible, then of Karlsruhe
 University, and Michael Stoll, then of Munich University, both in Germany.
 It implements the language described in the ANSI Common Lisp standard with
 many extensions.

 CLISP includes an interpreter, a compiler, a debugger, CLOS, MOP, a 
 foreign
 language interface, i18n, POSIX and Perl regular expressions, a socket
 interface, fast bignums, arbitrary precision floats, and more. An X11
 interface is available through CLX, Garnet and CLUE/CLIO. Command line
 editing is provided by readline. CLISP runs Maxima, ACL2 and many other
 Common Lisp packages.  

   2.2 Release binding
   What is is the release binding?
   (see http://opensolaris.org/os/community/arc/policies/release-taxonomy/)
   [ ] Major
   [*] Minor
   [ ] Patch or Micro
   [ ] Unknown -- ARC review required

   2.3 Type of project
   Is this case a Linux Familiarity project?
   [*] Yes
   [ ] No

   2.4 Originating Community
 2.4.1 Community Name
   GNU  CLISP
 2.4.2 Community Involvement
   Indicate Sun's involvement in the community
   [ ] Maintainer
   [ ] Contributor
   [*] Monitoring
   
   Will the project team work with the upstream community to resolve
   architectural issues of interest to Sun?
   [*] Yes 
   [ ] No - briefly explain
   
   Will we or are we forking from the community?
   [ ] Yes - ARC review required prior to forking
   [*] No
   
 3.0 Technical Description
   3.1 Installation  Sharable
 3.1.1S Solaris Installation - section only required for Solaris Software
   (see 
 http://opensolaris.org/os/community/arc/policies/install-locations/ for 
 details)
   Does this project follow the Install Locations best practice?
   [*] Yes 
   [ ] No - ARC review required
   
   Does this project install into /usr under 
 [sbin|bin|lib|include|man|share]?
   [*] Yes
   [ ] No or N/A
   
   Does this project install into /opt?
   [ ] Yes - explain below
   [*] No or N/A
   
   Does this project install into a different directory structure?
   [ ] Yes - ARC review required
   [*] No or N/A
   
   Do any of the components of this project conflict with anything under 
 /usr?
   (see http://opensolaris.org/os/community/arc/caselog/2007/047/ for 
 details)
   [ ] Yes - explain below
   [*] No
   
   If conflicts exist then will this project install under /usr/gnu?
   [ ] Yes
   [ ] No - ARC review required
   [*] N/A
   
   Is this project installing into /usr/sfw?
   [ ] Yes - ARC review required
   [*] No
   
 3.1.1W Windows Installation - section only required for Windows Software
   (see http://sac.sfbay/WSARC/2002/494 for details)
   Does this project install software into a 
   system drive:\Program Files\Sun\product or system 
 drive:\Sun\product
   directory?
   [ ] Yes
   [ ] No - ARC review required
   
   Does the project use the Windows registry?
   [ ] Yes
   [ ] No - ARC review required
   
   Does the project use 
   HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\product\version
   for the registry key?
   [ ] Yes
   [ ] No - ARC review required
   
   Is the project's stored location
   HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\product id\version 
 id\Path?
   [ ] Yes
   [ ] No - ARC review required
   
 3.1.2 Share and Sharable
   Does the module include any components that are used or shared by 
   other projects?
   [*] Yes
   [ ] No
 
   If yes are these components packaged to be shared with the other FOSS?
   [*] Yes
   [ ] No - ARC review required
   [ ] N/A
 
   Are these components already in the Solaris WOS?
   [ ] Yes
   [*] No - continue with next section (section 3.2)
 
   If yes are these newer versions being 

clisp [PSARC/2009/141 FastTrack timeout 03/05/2009]

2009-02-27 Thread zheng he - Sun Microsystems - Beijing China
Hi Garrett,

Sorry! My mistake. clisp need not install setuid programs. I'v e updated 
the proposal at http://cr.opensolaris.org/~zhenghe/arc/proposal.txt

Thanks

-Charles He

Garrett D'Amore ??:
 You've indicated that clisp installs setuid programs. Why? Please 
 provide more detail.

 -- Garrett

 James Walker wrote:
 I'm sponsoring this familiarity case for Charles He. The requested
 release binding is minor. The man page has been posted in the
 materials directory.

 Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI
 This information is Copyright 2009 Sun Microsystems
 1. Introduction
 1.1. Project/Component Working Name:
 clisp
 1.2. Name of Document Author/Supplier:
 Author: Charles He
 1.3 Date of This Document:
 26 February, 2009
 4. Technical Description
 clisp Check List
 1.0 Project Information
 1.1 Name of project/component
 clisp

 1.2 Author of document
 Zheng.he at Sun.COM

 2.0 Project Summary
 2.1 Project Description
 Common Lisp is a high-level, general-purpose, object-oriented, dynamic,
 functional programming language.

 CLISP is a Common Lisp implementation by Bruno Haible, then of Karlsruhe
 University, and Michael Stoll, then of Munich University, both in 
 Germany.
 It implements the language described in the ANSI Common Lisp standard 
 with
 many extensions.

 CLISP includes an interpreter, a compiler, a debugger, CLOS, MOP, a 
 foreign
 language interface, i18n, POSIX and Perl regular expressions, a socket
 interface, fast bignums, arbitrary precision floats, and more. An X11
 interface is available through CLX, Garnet and CLUE/CLIO. Command line
 editing is provided by readline. CLISP runs Maxima, ACL2 and many other
 Common Lisp packages.
 2.2 Release binding
 What is is the release binding?
 (see http://opensolaris.org/os/community/arc/policies/release-taxonomy/)
 [ ] Major
 [*] Minor
 [ ] Patch or Micro
 [ ] Unknown -- ARC review required

 2.3 Type of project
 Is this case a Linux Familiarity project?
 [*] Yes
 [ ] No

 2.4 Originating Community
 2.4.1 Community Name
 GNU CLISP 2.4.2 Community Involvement
 Indicate Sun's involvement in the community
 [ ] Maintainer
 [ ] Contributor
 [*] Monitoring
 Will the project team work with the upstream community to resolve
 architectural issues of interest to Sun?
 [*] Yes [ ] No - briefly explain
 Will we or are we forking from the community?
 [ ] Yes - ARC review required prior to forking
 [*] No
 3.0 Technical Description
 3.1 Installation  Sharable
 3.1.1S Solaris Installation - section only required for Solaris Software
 (see 
 http://opensolaris.org/os/community/arc/policies/install-locations/ 
 for details)
 Does this project follow the Install Locations best practice?
 [*] Yes [ ] No - ARC review required
 Does this project install into /usr under 
 [sbin|bin|lib|include|man|share]?
 [*] Yes
 [ ] No or N/A
 Does this project install into /opt?
 [ ] Yes - explain below
 [*] No or N/A
 Does this project install into a different directory structure?
 [ ] Yes - ARC review required
 [*] No or N/A
 Do any of the components of this project conflict with anything under 
 /usr?
 (see http://opensolaris.org/os/community/arc/caselog/2007/047/ for 
 details)
 [ ] Yes - explain below
 [*] No
 If conflicts exist then will this project install under /usr/gnu?
 [ ] Yes
 [ ] No - ARC review required
 [*] N/A
 Is this project installing into /usr/sfw?
 [ ] Yes - ARC review required
 [*] No
 3.1.1W Windows Installation - section only required for Windows Software
 (see http://sac.sfbay/WSARC/2002/494 for details)
 Does this project install software into a system drive:\Program 
 Files\Sun\product or system drive:\Sun\product
 directory?
 [ ] Yes
 [ ] No - ARC review required
 Does the project use the Windows registry?
 [ ] Yes
 [ ] No - ARC review required
 Does the project use HKEY_LOCAL_MACHINE\SOFTWARE\Sun 
 Microsystems\product\version
 for the registry key?
 [ ] Yes
 [ ] No - ARC review required
 Is the project's stored location
 HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\product id\version 
 id\Path?
 [ ] Yes
 [ ] No - ARC review required
 3.1.2 Share and Sharable
 Does the module include any components that are used or shared by 
 other projects?
 [*] Yes
 [ ] No
 If yes are these components packaged to be shared with the other FOSS?
 [*] Yes
 [ ] No - ARC review required
 [ ] N/A
 Are these components already in the Solaris WOS?
 [ ] Yes
 [*] No - continue with next section (section 3.2)
 If yes are these newer versions being delivered?
 [ ] Yes
 [ ] No - ARC review required
 If yes are the newer versions replacing the existing versions?
 [ ] Yes
 [ ] No - ARC review required

 3.2 Exported Libraries
 Are libraries being delivered by this project?
 [ ] Yes
 [*] No - continue with next section (section 3.3)
 Are 64-bit versions of the libraries being delivered?
 [ ] Yes
 [ ] No - ARC review required
 Are static versions of the libraries being delivered?
 [ ] Yes - ARC review required
 [ ] No 3.3 Services and the /etc Directory
 (see