On 5/22/07, Brian Granger <[EMAIL PROTECTED]> wrote:
>
> 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

+1
Ideally, I would like having a full hg repository for the spkg
makefiles *and* the source. I have had to patch close to 10 packages
this past weekend and I need to eventually submit patches for all of
them. Having an hg repo for these would make the process much more
easier.

But I would settle for a sage/spkg-patches.txt file that one could
edit and keep track of under an hg repository. Some kind of version
control on packages is necessary.

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

+0
The only problem I see with this is the initial cost of checking out
all these packages from sage.math

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