SAGE developers,

As you may know, I have been working on building some new spkgs and
have also begun refactoring the spkg build scripts themselves.  A few
ideas that I would like feedback on:

1.  Creating a repository for the spkg makefiles and build scripts

As far as I know, the full spkg infrastructure is not in a repository.
 What do I mean by the "spkg" infrastructure?

- The various makefiles and shell scripts used to build things
- The actual spkg-install scripts in each .spkg
- The contents of the sage subdirectory in each .spkg that contains patches.

I think it would be useful to put these things into a hg repository to
allow everyone to work together in maintaining existing spkgs and
creating new ones.  Here is the structure of the repo that I am
picturing:

toplevel
    makefile
    /spkg
        install-main
        /base
            deps
            install-deps
            other files in base...
        /standard # contains the base core components like python,
readline, etc.
            deps
            install-deps
            python-2.5.1
            ipython-0.8
        /sage   # contains the sage specific stuff
            deps
            install-deps
           ...

For each spkg, there would be a corresponding directory containing the
spkg-install script and the sage subdirectory (but _not_ the source
code for the package itself).  I think it would be a good idea to
create a format for the spkgs that is a little more standardized.
Here is an example:

ipython-0.8
    spkg-install             # existing spkg-install script
    ./spkg-patches       # rename the sage directory to this for clarity
    spkg-fetch.py         # a python script that could be called to
get the source for ipython

I think the spkg-fetch.py script is an important part of this.  It
would allow us to not include the source code for each package in the
repo, but it would make it very easy to write a script that begins
with only the scripts in the repo and builds a full source
distribution of everything.

Some questions about this approach:

Does this seem like the best way to manage the spkg infrastructure?

How should we handle it when the version of an spkg changes - for
example when python goes to 2.5.2?  Should we rename the directory in
the repo?  Is hg friendly with such renames?

2.  Hosting

Could the repo for all of this be hosted somewhere at sage.math?

I would love to get feedback on all of this.

Thanks,

Brian

--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/
-~----------~----~----~----~------~----~------~--~---

Reply via email to