taskSavannah Administration - Tasks: task #4337, Submission of SPS

 
 

task #4337: Submission of SPS

Submitter:  Gregor Richards <gregorr>
Submitted:  Thu 30 Jun 2005 06:13:18 AM UTC
   
 
Should Start On:  Thu 30 Jun 2005 12:00:00 AM UTC Should be Finished on:  Sun 10 Jul 2005 12:00:00 AM UTC
Category:  Project Approval Priority:  * 5 - Normal
Status:  Done Privacy:  Public
Assigned to:  kickino Open/Closed:  Closed
* Mandatory Fields

Add a New Comment Rich Markup
   

Wed 06 Jul 2005 06:36:27 AM UTC, comment #3: 

Hi,

I have approved your project.  You will receive an automated e-mail containing detailed information about the approval.

Regards.

Sebastian Wieseler <kickino>
Thu 30 Jun 2005 08:11:27 PM UTC, comment #2: 

Whoops!  I guess I missed that step ... usually I do that while putting on license notices, guess it slipped my mind..

http://www.codu.org/sps/sps-2005-06-30.tar.bz2


Also, I should mention another dependency.  Once the download-and-install subsystem is complete, it will depend upon GNU wget.

Gregor Richards <gregorr>
Thu 30 Jun 2005 07:50:09 PM UTC, comment #1: 

Hi,
I'm evaluating the project you submitted for approval in Savannah.

Not much to say, but your files lack copyright notices.
"Copyright (C) year1, year2, year3  copyright-holder"
See http://www.gnu.org/prep/maintain/html_node/Copyright-Notices.html in addition.

Please provide us with an updated tarball.
Regards,

Sebastian Wieseler <kickino>
Thu 30 Jun 2005 06:13:18 AM UTC, original submission:  


Site Admin. Approval/Edition URL:
 <https://savannah.nongnu.org/admin/groupedit.php?group_id=7763>


###### ORIGINAL SUBMISSION DETAILS ######

System Group Name:
-----------------
  sps


Full Name:
----------
  SPS


Type:
-----
  non-GNU software & documentation


License:
--------
  GNU General Public License V2 or later


Other License:
--------------



Description:
------------
  SPS (the Segregated Packages System) is a packaging system designed for developers and other users who want absolute control over their environment.  All of the packages are arranged in a directory tree like so:
/sps/pks/<package>/<version>
And there is an
/sps/bin
directory with some SPS tools, a wrapper, and many many symlinks to the wrapper.

This wrapper is where the real power of SPS comes into play.  It adjusts the environment such that you have exactly the tools, and exactly the versions of those tools, that you want, and nothing else.  If a system had Bash 3.0 and Bash 2.05b (as a particularly terrible example), a user could set up SPS in such a way that it would use only Bash 2.05b, and not Bash 3.0, without having to change their PATH.

This is accomplished by editing the ~/.sps_env file, which looks like this:
bash 3
gcc 4
kde 3
gnome 2
gnome 1
(for example).
This would set up my environment such that I have access to bash 3, GCC 4, KDE 3, and GNOME 1 & 2 (2 preferred in name conflicts).  All of these will automatically include their dependencies as well.

Last but certainly not least, you only have the development environment for the tools you want.  If you had a GTK+ tool that was insistant on building against OpenSSL if it could, but you wanted to avoid that so that it could be redistributed under the GPL, but at the same time wanted access to the OpenSSL libraries, you could put this in your ~/.sps_env file:
gtk+ 2 dev
openssl

Because the openssl line doesn't say "dev", you don't have access to the dev libraries in your environment.

That's the summary of everything as of yet developed.  I'm still working on actual download and install of packages, which ought to be relatively easy given this setup.

http://www.codu.org/sps/sps-2005-06-29.tar.bz2


Other Software Required:
------------------------
  Perl, some bourne shell (ash, bash, dash, etc)


Other Comments:
---------------


#########################################

Gregor Richards <gregorr>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

CC list is empty

 

There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

Only logged-in users can vote.

 

Follow 4 latest changes.

Date Changed by Updated Field Previous Value => Replaced by
2005-07-06 kickino StatusWait reply Done
    Open/ClosedOpen Closed
2005-06-30 kickino StatusNone Wait reply
    Assigned toNone kickino

Back to the top

Powered by Savane 3.13-caa5.
Corresponding source code