[Savannah-register-public] [task #4337] Submission of SPS

[Gregor Richards]

URL:
  <http://savannah.nongnu.org/task/?func=detailitem&item_id=4337>

                 Summary: Submission of SPS
                 Project: Savannah Administration
            Submitted by: gregorr
            Submitted on: Thu 06/30/2005 at 06:13
         Should Start On: Thu 06/30/2005 at 00:00
   Should be Finished on: Sun 07/10/2005 at 00:00
                Category: Project Approval
                Priority: 5 - Normal
                  Status: None
                 Privacy: Public
             Assigned to: None
        Percent Complete: 0%
             Open/Closed: Open
                  Effort: 0.00

    _______________________________________________________

Details:


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:
---------------
  

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







    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/task/?func=detailitem&item_id=4337>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.nongnu.org/